HTC ChaCha battery drain on CyanogenMod7.2 - HTC ChaCha

Hello,
the forum rules do not allow to post in "Development" section, so I am posting here.
I've installed CM 7.2 ROM for ChaCha from this Thread. (Build date: 20120824).
After reboot everything looked normal, there were minor lags, but since this was my first custom ROM, I assumed that it could be related to my performance settings (Governor: conservative CPU: 245 - 800Mhz). I've switched off all data connections (gps, mobile network, wifi) and disabled all animations to see how much battery it will consume in first 24 hours. To my surprise, the phone was off and battery was completely empty in the next morning.
I've installed CPU+Temp system widget to monitor CPU load. The widget showed that on idle system CPU usage was 98%-100% on maximum allowed frequency. After reboot the idle system CPU was normal - 1-10% on 245Mhz. Then I switched on Wifi and noticed that CPUusage started to increase. I've disabled wifi but CPU usage was up to maximum and didn't drop until reboot. I found that the same problem occurs with mobile network connection.
I opened Terminal and typed "top -m 6" to see which process is using the CPU. I found that system_server.so was taking up to 90% of CPU when the problem occured. "top -m 6 -t" showed that GPSLocationProvider thread of system_server.so was using all the CPU, in despite that GPS was always off.
I've started to search the solution of this problem and found this thread, which described that the problem is that librpc.so is not compatible with HTC gps drivers.
Then I've tried SuperOSR ROM and CM9 ROM. Both did not have this problem, which was interesting since SuperOSR is very similar to CM7.2. I've returned to CM7.2 and tried to solve the problem.
I updated the HTC drivers to the latest level (gps.chacha.so and others from the latest stock rom), but it did not affected the problem.
Then I did the binary compare of /lib/*.so between CM7.2 and SuperOSR and found that just a few libs was different. One of them was above mentioned librpc.so. I've installed librpc.so from SuperOSR to CM7.2 and the problem was gone.
The CPU usage now is 0%-4% when system is idle.
I hope that it will help others which is affected by this problem and I also wish that this bug could be solved in CM7.2.

can we use this metode for CM9?
HTC Chacha with CM9

This problem is not reproduceable on CM9 on my device. I believe you have different problem with similar symptoms. If you are experiencing 100% CPU load on idle device, open terminal and run "top -m 6" to find which process is using CPU and "top -m 6 -t" to find specific thread.
More likely you are running some widget which causes hang.

Thanks for the info! CPU usage was fixed to %100 before I did what you said! Thanks again :cyclops:

Related

deep idle not working

hi everyone, I have the ICS 4.0.3 (manual install) on my NS plus Matr1x kernel v13.
With NStools I enabled Didle but the counter leeps saying "0ms" under deep idle (both top=on and top=off rows).
I tried to search within the forum (google didn't help...) and all I've found is a ezekieel post faq where he suggested to kill gtalk app and service (or something similar) to stop camera service from blocking didle. Did it. Nothing changed.
I only saw once "Didle top=on" active (had matr1x v12.5) and it suddenly crashed.. so I installed v13, everything is working perfectly except deep idle...
halp

[Q] Some questions (Plz help)

I have got HTC Sensation XE.(it is rooted,revolutionary s-off,super CID,unlocked).
My old ROM was ARHD 3.6.9 and i was really satisfied except it was a bit laggy so after witnessing people's admirations of this new ROM (ARHD 6.6.3) i decided to upgrade.
After all i installed the ARHD 6.6.3 but i have these new problems now:
1.My mobile screen turns on and off involuntarily what should i do?
2.Battery drains too fast in comparison to my previous ROM(ARHD 3.6.9) e.g today with only 3 calls and no other actions(no video and audio usage and no internet browsing)2 P.M in the afternoon i had only 23 percent juice.
Of course i think one of the main causes is that screen turn-on and off.
3.Wireless doesn't work at all sometimes it finds the wirelss networks and sometimes not.
After finding the net it can not connect and shows this message "not in range"
4.Before installing this ROM i succeeded to connect to my mobile through Adb and make it SuperCID but now adb does not recognize my mobile what has happened?
So i couldn't install the Radio.But in "About" option my Radio version reads 11.69..... is it still necessary to install it?
5.There is not any options in menus and settings for enabling GPS or i could not find the one.Of course after opening Maverick program ,GPS started but it is very laggy and after about 8 mins it found the location .Before this it was very speedy about 2 mins it could connect.So what should i do to bring that speed back?
6.Maps program does not work and steadily a message shows up "unfortunately Maps stopped"
What's the problem?
Some of my other programs does not work as well and this message shows up after trying to open them.
7.After these all i am really regretful and disappointed of this ROM.Why should i upgrade and face these all problems even i thought to sell my phone and change it.
8.Is there any way to downgrade or use main kernels from HTC to solve all of these?
I tried to downgrade my HBOOT from 1.27 to 1.17 and bring my old ROM back but i couldn't.
After flashing the old firmware(1.17 HBOOT) the system hung and couldn't start and only 4EXT recovery touch removed and Clockwork recovery recovered but the HBOOT version was still 1.27 and the system could not start.
Excuse i really bothered you people with my long questions.
1. Settings > Display. What does it say under sleep?
2. It take a few days for the battery to reach its full charge after flashing a new ROM.
5. Setting > Location > GPS Satellites or put a toggle widget on your homescreen.
6. Update maps?
7. If you really dont like it go back to your old ROM.
Personally ARHD 6.6.3 works perfectly for me.
i am a noob but i think i have answers to your questions
2) kernel problem? if you're using faux123 kernel, download System Tuner by 3c from market and make sure governor is intellidemand (it was ondemand by default for me for some reason), or reflash faux123 kernel
havent test with sebastianFM yet, sorrry
3) ICS WiFi bug?
5) Setting > Location > GPS Satellite, install GPS fix tweak?
based on my experience, gps lock speed varies by apps
for example, Sygic locate gps fast than HTC location most of the time
6) clear ur old map from ur SD card
Settings > Storage > (under SD card) Make more space > Maps

[Q] RILJ wakelock - are you affected?

Hi all 7.7 users - Im a long time 7.7 owner and XDA lurker - having recently moved to Paranoid Android's CM10 based build for our tabs, ive noticed that the dreaded RILJ mobile network wakelock is back in full effect.
i have gone through the regular troubleshooting steps of enable Airplane mode, turn off, turn on, disable Airplane mode - this has no effect. other forums recommend using GETRIL to set up RIL properly, but that app does not support the 7.7 tab yet.
i am running a HK based p6800, which i had flashed the Austrian LQ2 stock rom on, before upgrading to PA 2.16. i do NOT have a sim card fitted at the moment, so i only use it on wifi - which confuses me more when i see the RILJ wakelock, because how is it locking on to a carrier signal without guidance from a sim card???
previous to this, Honeycomb stock was slow, but battery lasted for ever on standby, which was awesome. on ICS, performance decreased, but RILJ was not a problem. now on JB 4.1.1, RILJ never lets the tab sleep, and it remains on 200mhz until its battery dies a few hours later.
what are your experiences and suggestions? i have heard that some builds of CM10 fixed the RILJ issue, and i know PA has reached version 2.18 on other devices, but still waiting for it to be updated for our tab - however does anyone know if newer CM10 builds (supposedly android 4.1.2???) fix the RILJ wakelock?
thanks all

[BUG] system_server boot loops

I'm relatively new here...and to rooting... I do a heckuva lot more reading than posting here...and searching this problem brings a wide variety of other people's similar experiences and the solutions they've tried...but most of them are not exactly what I'm experiencing. The one case that matches exactly, never found a solution...
So here's my case... Every time I reboot my phone, it boots normally...and 3-7 minutes later, system_server begins hogging up CPU%...freezes...then reboots the phone. This cycle goes on forever. I have successfully used several different solutions, but the fix is not repeatable...it works once, but if I need to use the fix again, it won't work...
My current setup: Inspire 4g, Viper 1.2.3, BeastMode v0.5, oc 1497 interactive gov. (set on boot NOT checked)(no additional CPU or voltage tweaks)...I also had this problem with TrickDroid, before I ever tried overclocking...although my gut tells me the problem is related to oc, it occurs whether or not max speed is the stock 1024 or faster...
Here's what I've tried that has worked at least once, but failed to work ever since:
Turn off data and wifi connections
Turn off data, wifi, autosync, gps
Wipe cache and dalvic
Wipe cache, dalvic, fix permissions
Wipe cache, dalvic, dirty flash rom
Turn off data, wifi, autosync, gps, autorotate
Wipe data, cache, dalvic
Wipe data from setCPU and uninstall it
Install kernel BeastMode v. 0.5
And the only solution that works every time is....full wipe, reflash rom...once I do this and system is stable, I can build everything back up....flash BeastMode kernel, restore apps and home screens, even overclock...everything stays stable and works perfectly...
...but, you know... It's impossible to resist the urge to tweak something, flash something...or do SOMETHING that requires a reboot...and that's when the problem occurs...
Every. Single. Time.
Is there anyone here that can share some knowledge, or point me to some buried thread I haven't found after weeks of searching??
One more bit of info that may or may not be related...I dunno... I've tried overclocking with both setCPU and Juice Defender Ultimate...set on boot is always left UNCHECKED...however, the settings seem to stick anyway...randomly...sometimes it does, sometimes not...
Please...if you can help me, or educate me, or point me in the right direction, or have any thoughts or some personal experience with this bug...post here... I'm very interested in your ideas...
Sent from my Inspire 4G using xda-developer's app
This sucks...
Here's a possible solution...but it sounds complicated... I guess setCPU changes something...
http://forum.xda-developers.com/showthread.php?t=983524&page=2
I'm probably just going to screw up the phone if I go trying to edit files...if I can even find this file.
*frustrated*
I've reset permissions to 700 for /sys/devices/system/0cpu/cpu/cpufreq/stats/time_in_state... My phone stayed stable for about the same amount of time...4 days...then it rebooted and went into the boot loop again.
Nothing fixes anymore except fullwipe/reflash...but I can restore my tweaks settings, overclock, restore apps and homescreens, etc pretty quick now, and it stays stable for a few days...so once every four or five days isn't THAT bad I guess...
Sent from my Inspire 4G using xda-developer's app
RuggedHunter said:
I've reset permissions to 700 for /sys/devices/system/0cpu/cpu/cpufreq/stats/time_in_state... My phone stayed stable for about the same amount of time...4 days...then it rebooted and went into the boot loop again.
Nothing fixes anymore except fullwipe/reflash...but I can restore my tweaks settings, overclock, restore apps and homescreens, etc pretty quick now, and it stays stable for a few days...so once every four or five days isn't THAT bad I guess...
Sent from my Inspire 4G using xda-developer's app
Click to expand...
Click to collapse
Just for ****z and grinz, have you tried wiping and just installing a plane Jane ROM and not tweaking anything other than installing most used apps? My suspicion is that the kernel you are using or one of your power/super teaks are messing with your hardware and causing the issue. Try just using a base ROM for a week and resist tweaking it during that time. Then add addition tweaks on a weekly bases till it becomes unstable again. The you know what is causing it. I suspect the kernel since it is according to you used on all your ROM installs. Might try a different kernel if you must tweak from the get go.
Thanks man, that's great advice! I've had this problem with TrickDroid (and whatever kernel that came with), Viper 1.2.3 (and whatever kernel that came with), and same Viper with BeastMode v0.5 kernel. I haven't tried any other roms, but I don't think I can blame this on the rom...
I've tried a lot of things that I haven't posted yet, and I think I have it pretty much 100% narrowed down to overclocking...this problem never started until I started using JuiceDefender to overclock...then SetCPU...
Through process of elimination I've been able to rule out just about everything else...after a fullwipe, I can reflash the rom and let it settle...then reboot, and it does not loop...then flash new kernel, no bootloop...retweak some personalization stuff, still no loop...then restore all apps, still no loop...open SetCPU and set max speed to ANY speed...if I reboot it'll loop...if I just leave it alone, it'll stay stable for days...when it reboots, while watching Diagnosis I see system_server running at 65-95% CPU for about 90 seconds and the phone severely lags or freezes, then hot reboots...
Also, in the past, before I had this bootloop problem but after I started overclocking...I could still reboot my phone and everything would be fine, but the maxspeed was still set to oc, even though 'Set On Boot' was not checked and no profiles were used. This was true with all 3 kernels and both roms, and the app I used to overclock made no difference...SetCPU or JuiceDefender...even setting everything back to original settings before uninstalling both apps...oc settings always stick...
Last week, I read about someone thinking this issue was related to something about the relationship between mbuffer and time_in_state...one is 256 bytes, and the other 280 which recreates the problem...someone found a solution by changing the permissions of time_in_state back from 777 to 700...my phone rebooted and looped on Thursday, so that didn't work...
I've downloaded another rom to try, so when my phone goes on the fritz again in a couple days and I have to wipe anyways, I'll try a couple out and see if a different rom/kernels work...Thanks!
Sent from my Inspire 4G using xda-developer's app
Well, I got another random reboot then loop last Sunday, so I switched things up and flashed Pipeliner's cm10 on jellybean. So far, so good... I've overclocked with the rom's internal settings instead of setcpu, and I can reboot normally every time...
Thanks again for the help...
*edit* for... not get...
Sent from my Inspire 4G using xda-developer's app

[HELP] AlarmManager Wakelock -[com.android.internal.telephony.gprs]

friends i am cm10.1 and i have this wake locks "com.android.internal.telephony.gprs-data-stall".
i search lot but did not find any solutions for that wake locks.this wakelocks drain my battery like hell.
i reboot my phone wait for 10min and i have 30 com.android.internal.telephony.gprs-data-stall wakelocks.
i already disable gprs.and i never use gprs in my phone
i see this https://android-review.googlesource.com/#/c/40690/ and i think its need to fix in build.
I found this (same problem but in nexus s):
#7 tadejkol.. @gmail.com
I've found the solution for this, actually quite some time ago.
I noticed when I flashed CyanogenMod 10 ROM (and ROM's with commits from it), that the Phone drain and Data Stall wakelocks didn't persist. I moved to Codename Android ROM completely because of this www.codenameandroid.com . I was discussing this with a developer on xda-developers knzo, who posted his AOSP compiled crespo ROM, which had the same symptoms. He experimented with CM telephony and RIL support from codenameandroid Github (https://github.com/knzy/platform_frameworks_base/commit/e6a4f7c28f343ffe30e325350595f139820a3261, https://github.com/knzy/platform_frameworks_base/commit/5adbed5fb3e5572888a9de8c9905b677d2b95c56) and it worked perfectly, there was no Phone process showing in the battery stats and also no Data Stall wakelocks in the BetterBattery stats application.
I hope this will be fixed in coming release (4.2?).
in here http://code.google.com/p/android/issues/detail?id=35856
grigtm said:
I found this (same problem but in nexus s):
#7 tadejkol.. @gmail.com
I've found the solution for this, actually quite some time ago.
I noticed when I flashed CyanogenMod 10 ROM (and ROM's with commits from it), that the Phone drain and Data Stall wakelocks didn't persist. I moved to Codename Android ROM completely because of this www.codenameandroid.com . I was discussing this with a developer on xda-developers knzo, who posted his AOSP compiled crespo ROM, which had the same symptoms. He experimented with CM telephony and RIL support from codenameandroid Github (https://github.com/knzy/platform_frameworks_base/commit/e6a4f7c28f343ffe30e325350595f139820a3261, https://github.com/knzy/platform_frameworks_base/commit/5adbed5fb3e5572888a9de8c9905b677d2b95c56) and it worked perfectly, there was no Phone process showing in the battery stats and also no Data Stall wakelocks in the BetterBattery stats application.
I hope this will be fixed in coming release (4.2?).
in here http://code.google.com/p/android/issues/detail?id=35856
Click to expand...
Click to collapse
so there is no solution until google fix this.

Categories

Resources