[TESTING] - NAND OMGB (1.2.3)

[milda25]

Originally Posted by arrrghhh

My battery could be close to death, but I don't get nearly that...



Well it definitely worked with the flashed zip. Took a little while to lock, and certainly did take going outside. For the record mbellot, I have definitely gotten locks inside - but again, only after using QuickGPS. With no assistance, the radio takes quite a long time to get a fix.

The other bugs you mention are pretty much status quo - although GPS doesn't seem to kill sleep, you think it still does despite the indicator going green? I haven't had a problem with the phone sleeping, but I haven't used GPS a whole lot. Just got a speedo app to see how accurate my speedo is in my truck on the way home from work... worked great! I don't think I used it for even 20 minutes.... maybe 10. That lockup bug sounds like the same thing that happens in HaRET... Not sure anyone has even captured logs from such a crash.

Yes, I'm waited very long time (about 20minutes) in my garden and GPS not locked

With sleep state I have no problem. LED goes orange/green exactly as I expect.

[milda25]

Originally Posted by mbellot

I'm getting 24+ hours of light use with OMGB. Not quite as good as FRX07.1, but darn close.

How did you do? Talking you about NAND OMGB? I tried everything - battery calibration, turn off BT, wifi, mobile data. But I don't get over 9 hours. Should I buy new battery?

[milda25]

Originally Posted by milda25

Yes, I'm waited very long time (about 20minutes) in my garden and GPS not locked

With sleep state I have no problem. LED goes orange/green exactly as I expect.

So, back step - after 30min wait using the GPS status app I fixed to sattelites. Battery goes to hell during gps using 30min consume 45% of battery, but in car I have auto adapter

[argenisaz]

Originally Posted by arrrghhh

Well you can easily confirm if it's dying or not... Do you have this problem in WinMo? Flash back and see.

I flashed WinMo and screen calib was off from the start. I calibrated but I still notice that near the lower part of the screen (close to the zoom bar) it's a little off.

Seem like the end of the road for my TP2.

[mbellot]

Originally Posted by arrrghhh

That lockup bug sounds like the same thing that happens in HaRET... Not sure anyone has even captured logs from such a crash.

I captured it (a hard lock-up) twice (/proc/last_kmsg recovered after reboot). It appears to me that "SurfaceFlinger" crashed, but I'm no expert at reading logs.

Logs were originally posted here.

[mbellot]

Originally Posted by milda25

How did you do? Talking you about NAND OMGB? I tried everything - battery calibration, turn off BT, wifi, mobile data. But I don't get over 9 hours. Should I buy new battery?

I'm not sure "how" I did it, but my phone is set up like this:

Latest OMGB w/o GPS update (I manually installed gps.rhodium.so from 1.2.2 originally and haven't updated yet)
Stock launcher replaced with ZEAM
Wi-Fi off
BT off
Wireless data ON
Google syncing contacts at whatever interval it uses (don't know)
K-9 email polling three POP3 accounts @ 15 minute intervals
Battery Calibration was run after everything was installed and stabilized.
Battery Left widget "calibrated" and running to monitor battery status
ClockSync installed but only run manually (about 2x per day)
Network location and GPS both turned off
Stock analog clock widget on home screen
Stock toggle widget (WiFi, BT, GPS, Sync and brightness) on alternate home screen
No wallpaper at all, just a black background
No GMail syncing

I'm not running any other widgets than those listed above.

Light usage (for me) is around 30 minutes of calls, ~ 10 text messages and ~ 30 emails. Also some goofing off time playing games (30-60 minutes per day).


I'm on a CDMA provider (Boost), so I don't know how the radio plays into battery usage.

[mbellot]

Originally Posted by arrrghhh

although GPS doesn't seem to kill sleep, you think it still does despite the indicator going green? I haven't had a problem with the phone sleeping, but I haven't used GPS a whole lot.

Sorry, missed this...

I'm definitely getting into sleep mode (according to the status LED), but it "feels" like something isn't being completely turned off.

If I use GPS and then turn it off (via Settings or the toggle widget) the battery seems to die quicker (even after a full recharge) until I reboot the phone.

I've worked on ultra low power electronics in the past (solar powered), so I know it can be something as silly as an output pin left in the wrong state that's leaking current into a part of the circuit that should be "off".


EDIT: Just as a quick test, I turned GPS on briefly (about one minute) and then turned it back off (no location lock). We'll see where my battery life goes throughout the day, but I should (according to prior data) be able to run ~ 20 more hours from now.

[[ACL]]

Originally Posted by mbellot

I captured it (a hard lock-up) twice (/proc/last_kmsg recovered after reboot). It appears to me that "SurfaceFlinger" crashed, but I'm no expert at reading logs.

Logs were originally posted here.

thanks. I got a test patch for this in the new kernel. Classic mdp bug

[[ACL]]

Sorry for not releasing the update this weekend. Detule is helping on merging the userland acoustic back to a single source. Just got another patch yesterday and it looks good for us, so just give me a few more days.

Thanks fellas

[mbellot]

Originally Posted by [ACL]

Sorry for not releasing the update this weekend. Detule is helping on merging the userland acoustic back to a single source. Just got another patch yesterday and it looks good for us, so just give me a few more days.

Thanks fellas

Take your time, it's us who should be thanking you!