Originally Posted by trevoroni (Post 2170546)

Finally got around to updating to the new LK and recovery and getting my CID. So here it is.
CID: TELUS001

Edit: And my phone is a Rhod500 with a Rhod400 keymap

Originally Posted by mbellot (Post 2170825)

Maybe. But I also honestly think there is something fundamentally messed up with the charge/discharge logic.

This still makes me wonder what was so special about that particular day and a half...

I haven't ever replicated a run that long, but I have gone 24+ hours at times. Typical seems to be 14-16 hours, but lately it's closer to 10-12.

Forcing regular "calibrations" appears to help temporarily, but things always degrade within 3-5 days, and it "seems" to be tied to how often I connect a charger (more connections = faster decline of apparent battery life).

Originally Posted by argenisaz (Post 2170863)

2. I was on a call, and while talking I noticed the screen off and a solid green light. The call finished and the phone wouldn't come back to life. I let it settle for 10 min and nothing, I didn't respond to the press of any button (solid green light all the time). I wanted the ADB into it, but as soon as I connected the usb cable it restarted, I'm posting my last_kmsg.

Originally Posted by [ACL] (Post 2170941)

This is beyond the regular troubleshooting im willing to do because you have alot of apps in there. Looks like you are trying to go to sleep but something is preventing it. Since you have GPS enabled and some Hotmail thing, im not sure where to begin troubleshooting.

Look at all this ..

[29369.275909] Restarting tasks ... done.
[29369.294860] suspend: exit suspend, ret = -11 (2012-02-28 12:05:04.040000000 UTC)
[29369.328002] suspend: enter suspend(2012-02-28 12:05:04.080000000 UTC)
[29369.328033] PM: Syncing filesystems ... done.
[29369.330261] PM: Preparing system for mem sleep
[29369.330291] Freezing user space processes ... <6>active wake lock alarm, time left 500
[29369.375946]
[29369.375946] Freezing of user space aborted
[29369.376159] __eas(Hotmail)
[29369.376220] Thread-10
[29369.376251]

This goes on for a while .. Try disabling data before going to sleep, if that helps then at least we know where to dig in.

Originally Posted by argenisaz (Post 2170946)

It happened again, here's the last kmsg

Originally Posted by [ACL] (Post 2170944)

Actually no, its not just the charge discharge logic. The whole batt code is broken and needs love. Do a text search on the batt code and you will find the word "hack often. I've been so busy at work i havent had time to do anything lately. If anyone wants to dive in, just study the htc_battery_smem.c file and you will see why its so broken.

:thumbleft:

Originally Posted by [ACL] (Post 2170950)

Ahh I think arrggg told me about this in the past. So the phone tries to go to sleep when you are in a call right? So when your call is over, the phone probably doesnt realize it should be awake instead of napping. This actually happens to native devices as well. My friend's OG droid for example had very similar issue. Wonder how they solved it.

Originally Posted by [ACL] (Post 2170944)

Actually no, its not just the charge discharge logic. The whole batt code is broken and needs love. Do a text search on the batt code and you will find the word "hack often. I've been so busy at work i havent had time to do anything lately. If anyone wants to dive in, just study the htc_battery_smem.c file and you will see why its so broken.

:thumbleft:

Originally Posted by mbellot (Post 2170954)

Against my better judgment... I pulled the file off of git.

Assuming I got the right one, it seems like none of the kernel messages are being printed other than the "Initialized" one, so it's hard to see what (if anything) might be getting determined/set up.

Even more against my better judgment... I'm going to ask if there is a "dummy's" guide to getting up and running with a dev system. I'm on Windows (XP), but should be able to set up a dev environment in a virtual PC if it "must" be done under linux.

I guess four hours of sleep a day is simply too much. :oops:

Originally Posted by arrrghhh (Post 2170951)

This!!!!



Or if they solved it...

I thought the ARM11 side was allowed to sleep during a call, but ARM9 is obviously still up and functioning. But the green LED indicates ARM11 state, so it would go green while in a long call...

However, the real issue is why it doesn't wake back up. I've had it happen before, but usually the phone wakes back up... So AFAIK it's "normal" for the phone to sleep in a call. What's not normal is the not waking afterwards ;).

Originally Posted by mbellot (Post 2170954)

Against my better judgment... I pulled the file off of git.

Assuming I got the right one, it seems like none of the kernel messages are being printed other than the "Initialized" one, so it's hard to see what (if anything) might be getting determined/set up.

Even more against my better judgment... I'm going to ask if there is a "dummy's" guide to getting up and running with a dev system. I'm on Windows (XP), but should be able to set up a dev environment in a virtual PC if it "must" be done under linux.

I guess four hours of sleep a day is simply too much. :oops: