deep idle not working - Nexus S Q&A, Help & Troubleshooting

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

Related

[Q] WiFi turning on by itself?

Hi All,
Having a strange issue with my Sensation wheras the WiFi is switching itself on at night.
Normally I will switch it off using the 'power bar' when I go to bed and then switch it back on when I wake up but since the Twitter update (on Orange which seems to have updated my market as well) it comes on by itself. If I turn it off again it stays off.
I know that both nights the phone has been about 7% battery and is in power save mode but this doesn't switch the WiFi off, just the sync. I then press the WiFi off and plug it into the mains.
Any ideas on why this is happeneing and if it is a known bug? Also if there is a way to fix it?
Thanks
Darren
Details??
Is your phone S-OFF?? rooted? If so, which ROM are you using? Please post all the details.
I had this bug twice with ICS, ma battery starts screaming at 21% while it was 80% just 2 hours before,it was wifi that was ON by itself
retardedrockstar said:
Is your phone S-OFF?? rooted? If so, which ROM are you using? Please post all the details.
Click to expand...
Click to collapse
Sorry, standard Orange ROM, not rooted or anything
Android 2.3.4
Sense 3.0
Software 1.50.61.1
Kernel 2.6.35.13-gle13373
Baseband 10.58.9035.00U_10.15.9035.02_2
Seems to only have done it since the twitter update on saturday which also updated my marketplace.
Darren
Hi,
I have the same problem. In my case, I am using ICS4.0.3 on my Telstra HTC Velocity (rooted but stock ROM ).
I think it might be Juice Defender , but I'll confirm that in couple of days time.
I have used it once, and uninstalled it, but I think it might have left behind the settings (network scheduled to be turned on at night to sync).
I installed it again, and by default that option was turned on. I have now turned it off and uninstalled it again.
I shall let you know the outcome soon
i have this issue on my previous ARHD 6.6.0
i tried to flash with different kernel,it wont fix
all i do is flashed to New leedroid 7.3.0 the issue gone.
So i assume is ROM problem.not quite sure about this.
I think it was a problem with a specific base that was used (either in the stock or making the rom),
I had it on IC5.2 I think, but then updated my rom and it went away, it presented itself on all the roms that used that base (I believe) it should be gone now with the updated base that was released. Not sure of the specifics and version numbers, maybe a dev can provide if needed, but the updates shouldn't have that issue anymore

Milestone XT701 CM9 Problem T_T

Hello everyone it has been a long time since I've posted here. I really refrained from posting here since I know everyone else is dealing with the XT720 which is different, but I have tried everything. I am so close to it finally working perfectly.
I'm currently running this CM9 ROM: http://115.com/file/c2c50r7v#updatecm9.0.0RC0umts-sholesUNOFFICIALsigned-NIGHTLY-20120605.zip
from this link: http://www.anzhuo.cn/thread-293117-1-1.html
It seems to be the godsend for my phone. Mainly cause It has been a long time since I've ran a stable ROM that can be clocked at 1.0Ghz. I don't know about the XT720 but all the ROMs that has been released can only be overclocked to 800Mhz.
I flashed the CM9 ROM and then flashed the "gapps-gb-20111216-signed" for the Google apps. For the first time in months (before I was using a CM9 and CM7 before) I finally had wifi working. I don't really use much wifi (other than updating apps) so it didn't bother me back then. Everything else was working (cept for panoramic in the camera APP which NEVER works ever). But its like Motorola was playing a sick joke on me; I couldn't download/update my apps. I loaded everything fine but when I clicked download, I just see the download bar moving, but it never finishes. Weirdly, I reflashed everything and I suddenly got the error 921 (which I proceeded to search for a solution), but then after when I tried again, the error was gone and it was back to idle download bar. I did not change anything to the phone during that period.
So now I finally have XT701 clocked at 1.0 (like back in the day) with smartass/lagfree governors, working wifi, phone, audio and everything but I can't update/download apps.
I have tried:
-clearing data/cache for google play
-clearing data/cache for download manager
-reflashing with the 3 wipes for every step
What is the problem? Does it have to do with the bands? When I first flashed the ROM i had to change the network settings to Canada(Telus) cause it was set at somewhere else. Is that the problem?
Thanks in advance

HTC ChaCha battery drain on CyanogenMod7.2

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:

[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.

[Q] The GPS is driving me nuts...

To begin with, I got my phone rooted with CM10 on it - I don't remember how well (or if at all) the GPS worked under that one, because I found it laggy as all crap. I went back to Gingerbread and have LOVED the increased responsiveness, but the GPS is now flaky as all-git-out.
Here is what I have tried:
Old baseband plus...
Eagle's Blood
CM7 7.2 "Stable"
CM7 7.2 Latest nightly (2013 march something, iirc)
I dropped it back to stock and let it update to the new baseband, then...
CM7.2 Latest nightly (ye gods that sounded awful. Oh, and the GPS didn't work.)
HellFire Phoenix reborn/reloaded/whatever the latest one was - I followed all of the "THIS ONE IS DEPRECATED, FOLLOW THIS LINK INSTEAD" links.
I have used the following kernels, more or less randomly, in addition to the ones that came wrapped into each ROM...
MazKrnl v1.0 rc2
Trinity T15
Trinity ELP
MazKrnl and ELP gave me sleeps of death in addition to the GPS not working.
Now, my first GPS lock after loading HFP (my latest ROM - and I am just trying T15 with it as I type this) took about five seconds and held solid. I was SO FREAKING HAPPY! But that was yesterday.
This morning, according to "GPS Toolbox" it can see anywhere from 9-11 satellites - and has a lock on all of them - but won't give me coordinates at all. This is true even after about 30 minutes sitting by a 7th-floor window.
IT'S MADDENING.
I've been googling. I tried messing with the GPS.CONF file, adding and replacing north-america ntp servers. I've tried downloading and re-downloading AGPS info from the GPS toolbox app. I flashed the "for_old_bb.zip" that I found somewhere - even though that's supposed to only affect audio - and GOOD LORD THAT WAS A MISTAKE, given that I'm now on the new bb. (The "new_baseband.zip" which is its alternative seems to have vanished utterly from the internet, sigh.) So yes, I'm down to grasping at straws.
Did I mention the maddening part?
I'm aiming to put together a for-real, once-and-for-all solution to the GPS issues here, because everywhere else it's 2-3 years old and nothing referenced anywhere has worked for me. I know this phone is a little long in the tooth, and dev has basically stopped, but am I really the only one still in this boat?
Thanks - seriously - for ANY help with this.
Update:
T15 kernel (?) caused a sleep of death over lunch.
Completely eliminating the GPS info (App "GPS Status & Toolbox" -> Settings -> Reset) and letting it sit with no internet access for oh, about an HOUR led to a post-reboot fix in a reasonable amount of time.
Oh, also I removed the "SUPL" info - per this post.
Of course, then my battery was wasted, so I'm recharging to test again later.
Honestly people - is this phone worth it? I only "upgraded" from my HTC Thunderbolt for the 4G - which, I admit, is nice when I'm not on wifi...
This phone has always had GPS issues.
The last baseband helped a bit, but it was never fully resolved.
I still use this phone, and still use the GPS on it nearly daily for tracking my hikes and bike rides.
My steps:
Run GPS Test.
If locked, great, done.
If not, wait about 10-15 seconds.
If it doesn't lock within that time, it will never lock without a reboot, no matter how long you wait.
Reboot.
Run GPS Test again.
<Repeat the above steps>
Generally I have noticed that 95% of the time, that a lock will happen after a reboot.
The other 5% of the time, you will have to reboot again.
The other annoyance for me is that during runtime, while you are using the GPS, it will just lose lock.
If that happens, you are toast. It will never come back without a reboot.
I don't even bother waiting, hoping it will come back.
As soon as it loses lock, I do a reboot.
On reboot, it generally locks right away again.

Categories

Resources