Related
Hello all. Kinda new here, but I've been flashing my hero with roms from here for a while now. My latest attempt at a good rom is the VillainROM 12.0.0, this is my first time with a VillainROM, and I don't know if this bug exists in previous versions. In my opinion it is a very minor issue, but maybe not for someone else. I'm not a developer, so I don't know what could be causing it, and I don't know if I should be reporting bugs on the VillainROM site, or here, so I'm going to start here...
I downloaded the ROM from the VillainROM12.0.0 thread...
Install was flawless, worked perfectly.
The ROM runs extremely well in all functions, so no complaints there.
The only issue is a slight (10+ seconds) hang when I press the power button to turn on the screen to unlock it and the WiFi connection has timed out. Other ROMs I've used, including the stock ROM would come out of this sleep mode, and then try to reconnect to the WiFi, and they've done so with flawless success. However, this ROM does not, at least not for a minute or so.
This is how I can reproduce the problem, and it takes a while. I usually plug my phone into a charger at night and let it charge over night, and unplug it in the morning to head off to work or whatever. Once the screen turns on on its own after the external power source is disconnected (which all ROMs have done) the screen is unresponsive, and all buttons are unresponsive. The screen remains lit up on the lock screen stuck for at least 10 seconds, then goes black, then pressing the power button to turn the screen back on will restore the phone to an unlocked state (assuming it remembered the swipe action from when the screen was locked and stuck) but takes about another 5 seconds to come back on. This only happens if I have the WiFi radio on while the phone is sitting idle for an extended period of time (long enough for the radio to automatically go into its sleep mode perhaps?).
Here's the info from my phone...
Firmware Version: VillainROM9.0.0
Baseband Version: 63.18.55.06JU_6.35.09.26
Kernel Version: 2.6.29-ninpo-freqtwk{AT}titan-dirty-b7a296faninpo{AT}titan #39
Build Number: VillainROM12.0.0
Software Number: 3.32.405.1
Browser Version: 3.1
I'm not sure if this is just a fluke, if I should reflash and see if the problem persists. Anyone else able to reproduce this?
Again, if this is the wrong forum, please feel free to move it, and thanks XDA, this site is an awesome resource!
PS... I had to replace the at sign with {AT} in the Kernel Version due to Forum restrictions (It thinks it's an outside URL and I'm too green to be able to do that...)...
Are you running setCPU or OC Widget?
It look likes the lower CPU frequency is too low. Open SetCPU or Overclock Widget and increase it a little.
If you use profiles, in SetCPU:
> Check if you have a "Sleep Profile"
> Check if its frequences are too low.
> If yes, increase it.
It normaly happens when you have a 19Mhz - 2XXMhz on-demand sleep profile.
Increasing that 2XXMhz to 3XX or 4XX may solve the issue.
If not, try to reflash, or use VillainROM IRC at their website.
First your radio is a bit old. Try upgrading to the latest radio from here:
http://villainrom.co.uk/viewtopic.php?f=24&t=323
Second, especially regarding the wakeup issues, try my kernel for VR12 from here:
http://villainrom.co.uk/viewtopic.php?f=97&t=1928
It has no wake-up problems even @ 691/160 (what I used) as well as better battery life and performance....
Turn up your minimum set cpu speed.
erasmux said:
It has no wake-up problems even @ 691/160 (what I used) as well as better battery life and performance....
Click to expand...
Click to collapse
Pulser has no problems waking up at 19MHz with my kernel. Stable Min/Max frequencies are unique to each phone it has nothing to do with the kernel.
In theory I agree with you completely. But in practice with each kernel I get a different wakeup "performance" using the exact same frequencies. I always prefer setting the min to 160Mhz, but like many many others, in most kernels - including your kernel which comes with VR12 I get heavy wakeup issues which disappear only @ min 480. In other kernels (such as those by Radu) these wakeup issues still exist but are less pronounced (very very rare).
For me and others which have given my kernel a shot there have been no wake up issues @ min 160Mhz. Battery life and responsiveness also improved according to those who have tried my kernel (and optimizations).
BTW "my" kernel is just the HTC official kernel release + OC enable, so its more HTC's kernel than mine.
Like you said it is device dependent, ROM dependent, user dependent, everything.... I am just saying that until now I have not gotten any negative feedback on my kernel, and I think people should give it a shot and decide for themselves. Hopefully they will also be kind enough to share their experiences with me, so if there are problems I can try to fix them.
Thank you all for the suggestions. I do not use any OC utilities, it's the ROM as it was when I downloaded it. Barely any applications installed (some games, auto task killer, handcent...).
I've updated the radio to a version I found in a SenseHero 2.1 thread, but that radio broke MMS and some other data network features. I am in the US, on AT&T (I know, no 3G, but I'm ok with that ), will the radios listed work propperly on this network?
I was also able to reproduce the hanging issue by turning on the WiFi, browsing around the Market, and then exiting the market and turing off the WiFi. It seems that during the switch to the mobile network from WiFi is when something funky happens. Is there a way to get logs to show what might be going on?
First of all try the newest radio from here:
http://villainrom.co.uk/viewtopic.php?f=24&t=323
If 6.35.15.14 does not work well for you, try either 6.35.15.11 or 6.35.15.01 - If I am not mistaken they are all from the latest HTC release from different parts of the world, so one of them should work well for you.
If you want to get a log for the problem, use the adb logcat. Another simpler option to try and isolate the problem is check if reflashing the ROM (after a backup and a full wipe) solves the problem. Also check if the problem exists in other ROMs.
I have flashed the radio with the latest from the site as suggested (6.35.15.01 was no good when I flashed with that one before, caused all kinds of problems with MMS/SMS, and other network fuctions, but I didn't try that radio with the VillainROM). MMS and such still work, so that is good. I'm going to try to reproduce the other issue tonight, but that may have fixed the issue... I'll update the thread with the results.
Looks like the new radio did not solve the problem. Is the next step the new Kernel?
Sorry for the long delay in response...
The problem is still happening. I have now flashed with a different ROM (Chronos Droid 2.1.2) and the problem persists. However, the lockup doesn't seem to be as bad... Am I the only one with this problem? Should I change my wireless network settings to GSM only? Or leave it on Auto? I'll play around with that and see what happens. It just seems that changing from the mobile network to the WiFi network (and vise versa) is when the problem happens...
Nope, that didn't help. When I went to GSM only, I had no data network connection, and when I went to WCDMA only I had no connection at all. On GSM/WCDMA Only I have both... I wonder if it is something with this phone and the .29 kernel? But then wouldn't everyone here have this problem?
I have this issue too, using ninpo's kernel. I am going to increase my min freq but it's already at 3xx - fingers x'd
I don't see this being a kernel issue, I have a feeling its just a wifi issue on the new rom bases.
m4rk84 said:
I have this issue too, using ninpo's kernel. I am going to increase my min freq but it's already at 3xx - fingers x'd
Click to expand...
Click to collapse
Please let me know what happens.
I did not have these problems using the SenseHero ROMs (older Kernel), only Villain and now Chronos... :S I don't use any OC apps, just leave it all stock from the ROM. If I use one and increase the speed at sleep, (probably an obvious answer) will this drain the battery faster?
Still hanging. Does this have anything to do with wifi's android default sleep behaviour?
I'm having all kinds of lag issues when network queries are starting, especially during MMS/SMS operations. Could be a Handcent update, but the default messager thinger is also quite slow. I'm tempted to go back to an older ROM, this is getting frustrating...
I searched for Sleep Mode and GPS problems, and of course since those are very common words in most posts, I was having a hard time actually finding if anyone else has my problem.
I am running the most current kernel of FRX03. I have a sprint Rhod400. This problem pre-dates the current kernel, and I am not sure how long it has gone on, because I was having a lot more issues with sleep mode back in the earlier kernels anyway, as I think all people were. I am running with sleep mode set to 1.
Whenever I start a GPS program, usually it is foursquare, when I kill all the apps including foursquare using Advanced Task Killer, the phone will not go back to sleep. I have also looked at the "running services" setting and nothing is running besides Android. It seems to me the GPS stays active even though the GPS icon and all hints that it is actually running ceases to be found. I am guessing this is causing the phone not to go back to sleep. I have not really tested it out with navigation or maps to see if it happens there also, but if my memory serves me right it does.
Any suggestions on possible fixes?
Disable GPS. It's a known bug, which has already been filed on the bugtracker.
If GPS is enabled, phone will not sleep - and I don't mean enabled in that there's the GPS icon in your notification bar, I mean enabled (checked) in Location & Security. Uncheck it there, and the phone will sleep.
This is all interesting, because my RHOD400 seems to sleep just fine (much of the time) with GPS enabled!
gnnash said:
This is all interesting, because my RHOD400 seems to sleep just fine (much of the time) with GPS enabled!
Click to expand...
Click to collapse
Enable GPS, then open an app that uses it. Leave GPS enabled, but close the app. Now try to put your phone to sleep .
I've definitely seen intermittent issues with sleep and GPS. Not sure if it's every time, but I noticed when the phone doesn't sleep, I disable GPS in loc&sec and it'll go to sleep.
The only other serious sleep-related problems I've had is with rogue apps stealing processor cycles and keeping the phone awake.
I'm running NAND were pm.sleepmode = 1.
Yesterday I left my GPS enabled and I seemed to be getting better battery life? Maybe it is just a fluke... But you never know!
I will try it on my other phone running HARET.
Lmiller1708 said:
I'm running NAND were pm.sleepmode = 1.
Yesterday I left my GPS enabled and I seemed to be getting better battery life? Maybe it is just a fluke... But you never know!
I will try it on my other phone running HARET.
Click to expand...
Click to collapse
Well better battery life is probably related to usage.
However, that would be interesting if on NAND the GPS no sleep bug is non-existent...
I honestly haven't tested it in a while. No one has specifically looked at fixing it. I guess it's possible a commit happened to fix it - just usually doesn't work like that .
I use the 11/22/10 XDAndroid build from the .cab and the bug is present. LED doesn't turn from orange to green until I turn off GPS in settings and turn off the screen.
He probably thought that it was sleeping because the screen turned off (I used to think the same thing).
gallahad2000 said:
I use the 11/22/10 XDAndroid build from the .cab and the bug is present. LED doesn't turn from orange to green until I turn off GPS in settings and turn off the screen.
He probably thought that it was sleeping because the screen turned off (I used to think the same thing).
Click to expand...
Click to collapse
No I knew it wasn't sleeping. I know the purpose of the LED being on always(sleep mode debugging). I was just trying to figure out why, and if there was a fix, which there isn't. In the earlier version of XDAndroid builds it was more than just GPS that was causing sleep issues, so back then I didn't think much of it not going to sleep, as I couldn't get more than about 4 hours of battery life out of those builds anyway. Now I am getting at least 12 with heavy usage and way more than that with light usage. So things have improved indeed.
slickdaddy96 said:
No I knew it wasn't sleeping. I know the purpose of the LED being on always(sleep mode debugging). I was just trying to figure out why, and if there was a fix, which there isn't. In the earlier version of XDAndroid builds it was more than just GPS that was causing sleep issues, so back then I didn't think much of it not going to sleep, as I couldn't get more than about 4 hours of battery life out of those builds anyway. Now I am getting at least 12 with heavy usage and way more than that with light usage. So things have improved indeed.
Click to expand...
Click to collapse
Indeed! So that is the fix - disable GPS. It sucks, but it's on the punchlist of things to fix. Unfortunately I don't know of anyone looking at it specifically at the moment, but I'm sure it'll get addressed.
Hello,
I’m looking for help with a rather strange problem. I’m getting a lot of awake time in Android OS. I installed BetterBatteryStats and noticed it was the service BTLowPower that was doing a lot of kernel wakelocks.
I turned bluetooth off a couple of days (and have rebooted in the meantime even) but still the top service in kernel wakelocks is BTLowPower by a very large margin ... how can this be if bluetooth is turned off ?
Stats are in BetterBatteryStats Kernel Wakelocks
Unplugged 12h47min.
BTLowPower 9h33min, 74.7%
I've attached a screenshot
I have a Galaxy Nexus which is running stock Jellybean.
Thanks in advance for any advice !
Same here.
Please help.
My battery drains out because of this in 12h and 1.5h of screentime
Sent from my Galaxy Nexus
bat0nas said:
Same here.
Please help.
My battery drains out because of this in 12h and 1.5h of screentime
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Do you guys have other Bluetooth devices around? I have a Motorola S805 headset as well as a cheapo BT2.0 dongle from DealExtreme.
I typically don't have the headset turned on unless it's connected to the computer, but what I'm finding is that if I just leave my phone with the dongle turned off and the headset turned off then I don't get the BTLowPower battery drain.
If I turn the dongle on, and turn on the headset then I typically get the BTLowPower battery drain in my GNex. I have to reboot the phone for it to go away. I'm not really sure the exact sequence of events to cause the drain to occur, but I feel like it's definitely related to turning on and off my S805 headset or being around the dongle.
There might be other bluetooth devices around (such as phones of a colleague or something), however the bluetooth on my phone is turned OFF and I still keep getting the BTLowPower in kernel wakelocks Today for example it kept my phone awake for over 10 hours
Anyone ? I keep having this problem ...
Same problem here. BTLowPower keeps draining my battery.
I have bluetooth and Jabra headset off...
It usually happends when I unplug my GNex from charging.
Please help....
-----------
sorry for my bad english.
Same issue
I'm running a Toro Gnex with the Vanir AOSP ROM. It's buttery smooth, and I've had no problems at all, other than this specific kernel wakelock. Same scenario as the OP.
If anyone finds out more about it, I would be grateful!
Airplane Mode
NicholasFarseer said:
I'm running a Toro Gnex with the Vanir AOSP ROM. It's buttery smooth, and I've had no problems at all, other than this specific kernel wakelock. Same scenario as the OP.
If anyone finds out more about it, I would be grateful!
Click to expand...
Click to collapse
I've been reading about this all morning. I run Automateit Pro and have it go into airplane mode at night. After losing 25% battery overnight, the investigation began. BTlowpower was keeping the phone awake. It looks like airplane mode can be the culprit, possibly in combination with Wifi set to always on. I am set up to turn Bluetooth off a couple of minutes after going into airplane model tonight, I'll follow up with my findings over the weekend.
bigknowz said:
I've been reading about this all morning. I run Automateit Pro and have it go into airplane mode at night. After losing 25% battery overnight, the investigation began. BTlowpower was keeping the phone awake. It looks like airplane mode can be the culprit, possibly in combination with Wifi set to always on. I am set up to turn Bluetooth off a couple of minutes after going into airplane model tonight, I'll follow up with my findings over the weekend.
Click to expand...
Click to collapse
Great, keep us posted. I also turn airplane mode on at night, but my Bluetooth is always off.
Did anyone try to hard reset their phone ? I called Samsung but I got the standard reply to hard reset my phone, I haven't tried it yet because I doubt it would work and I have a lot of authenticators on it and it's a bit of a hassle. But if any of you guys already tried it I would love to hear if it worked ! Thanks !
BTlowpower solved
Darthy1980 said:
Great, keep us posted. I also turn airplane mode on at night, but my Bluetooth is always off.
Did anyone try to hard reset their phone ? I called Samsung but I got the standard reply to hard reset my phone, I haven't tried it yet because I doubt it would work and I have a lot of authenticators on it and it's a bit of a hassle. But if any of you guys already tried it I would love to hear if it worked ! Thanks !
Click to expand...
Click to collapse
BTlowpower issue solved by turning Bluetooth on and then off again after Airplane mode activated. However, that caused another issue - modem_usb_gpio_wake to crush my battery. Doing more testing today to resolve that one - will post again when that one is solved.
BTlowpower and modem_usb_gpio_wake resolution
bigknowz said:
BTlowpower issue solved by turning Bluetooth on and then off again after Airplane mode activated. However, that caused another issue - modem usb gpio wake to crush my battery. Doing more testing today to resolve that one - will post again when that one is solved.
Click to expand...
Click to collapse
After testing different configurations this weekend, it looks like turning off sync causes these 2 kernel wakelocks. I tested 2 states: Airplane mode + no Wi-fi, and no data (no Wi-fi + no Wireless data, voice signal on). In either instance, the wakelock occurs with sync off. Leaving sync on finally achieved the low overnight battery drain (< 5%) I've been looking for. Regardless, to avoid battery drain after shutting data off:
Turn Bluetooth On and then Off again. If you are using airplane mode (this may be overkill), also turn Wireless Data On and then Off again.
Let me know if this helps.
bigknowz said:
After testing different configurations this weekend, it looks like turning off sync causes these 2 kernel wakelocks. I tested 2 states: Airplane mode + no Wi-fi, and no data (no Wi-fi + no Wireless data, voice signal on). In either instance, the wakelock occurs with sync off. Leaving sync on finally achieved the low overnight battery drain (< 5%) I've been looking for. Regardless, to avoid battery drain after shutting data off:
Turn Bluetooth On and then Off again. If you are using airplane mode (this may be overkill), also turn Wireless Data On and then Off again.
Let me know if this helps.
Click to expand...
Click to collapse
Hi thanks for posting !
Just to make sure I understand, you say the solution is to turn bluetooth on and off again after turning off airplane mode ?
Just for completeness sake, this is my situation: overnight I turn on airplane mode and I sometimes have the wakelock draining my battery during the day (but not always). Draining doesn't occur during the night as while it's on airplane mode I'm also charging it.
I will try every morning when I turn airplane mode off to turn bluetooth on and off again afterwards for a few days and see if that helps. Let me know if I misunderstood.
Thanks,
Jorn
Just found a kind of workaround at another thread, this might be helpful (if it works ).
It doesn't, the drain still occurs >_<
gwindlord said:
Just found a kind of workaround at another thread, this might be helpful (if it works ).
It doesn't, the drain still occurs >_<
Click to expand...
Click to collapse
I actually have a workaround that works for me. During the night I turn off my phone instead of using airplane mode. I no longer have BTLowPower and I also am able to successfully connect every time very quickly with bluetooth to my carkit, which previously was very flaky. It's definitely a standard issue though with the galaxy nexus, I can reproduce it on 2 other galaxy nexi as well.
I just installed BetterBatteryStats two days ago, and I'm seeing the exact same results. I can't help but wonder if the issue is at all related to the kernel I'm using (LeanKernel v4.7), or if perhaps a resolution to the problem could be solved by a modification within the kernel code. The ROM I'm running is BAMF Paradigm v2.4, which is based on AOSP v4.1.2. Like the rest of you, I'd really like to get this fixed.
trestevenson said:
I just installed BetterBatteryStats two days ago, and I'm seeing the exact same results. I can't help but wonder if the issue is at all related to the kernel I'm using (LeanKernel v4.7), or if perhaps a resolution to the problem could be solved by a modification within the kernel code. The ROM I'm running is BAMF Paradigm v2.4, which is based on AOSP v4.1.2. Like the rest of you, I'd really like to get this fixed.
Click to expand...
Click to collapse
Anyone have any updates on this? My GNex just started doing this randomly after being stable for a long time.
the7thson said:
Anyone have any updates on this? My GNex just started doing this randomly after being stable for a long time.
Click to expand...
Click to collapse
After three days or so, the issue seemed to go away on its own. I didn't make any changes to any of the apps I was running, nor did I update the kernel. I really have no clue what took care of it for me, but I haven't seen it since.
trestevenson said:
After three days or so, the issue seemed to go away on its own. I didn't make any changes to any of the apps I was running, nor did I update the kernel. I really have no clue what took care of it for me, but I haven't seen it since.
Click to expand...
Click to collapse
Weird, mine went away as well after toggling BT a couple times. Guess we'll file this one under unsolved mysteries
Hi, I saw many posts related to this topic Wi-Fi turns off when phone in deep sleep but not able to find a single working solution.
My phone runs on 4.2.1 with wi-fi sleep policy set to NEVER ( that means always on ideally ) , and tried turning on / off wifi optimization, avoid poor connections is not ticked.
Even after doing everything the wifi is turned off after sometime and when i turn on Screen it turns it back! How to do I solve this?? I am using STOCK rom, with just root.. No other battery saver etc. app installed.
emptyragnarok said:
Hi, I saw many posts related to this topic Wi-Fi turns off when phone in deep sleep but not able to find a single working solution.
My phone runs on 4.2.1 with wi-fi sleep policy set to NEVER ( that means always on ideally ) , and tried turning on / off wifi optimization, avoid poor connections is not ticked.
Even after doing everything the wifi is turned off after sometime and when i turn on Screen it turns it back! How to do I solve this?? I am using STOCK rom, with just root.. No other battery saver etc. app installed.
Click to expand...
Click to collapse
Set it to Never instead of Always. Its ass backwards.
scottx . said:
Set it to Never instead of Always. Its ass backwards.
Click to expand...
Click to collapse
OP stated its already set to never
Sent from my Vivid 4G using Tapatalk 2
well i have this problem too on every jelly bean rom. the only rom without this problem in cm10 stable. now i'm with cm10.1 hoping they'll fix it like in cm10.
when that problem comes out just toggle on and off airplane mode and it should disappear until next wifi toggle off and on.
I hope google will solve it in key lime pie
CM 10.1 has only just started doing this in the last week or so, it was fine before. Was wondering if it was just me with this issue or not...
emptyragnarok said:
Hi, I saw many posts related to this topic Wi-Fi turns off when phone in deep sleep but not able to find a single working solution.
My phone runs on 4.2.1 with wi-fi sleep policy set to NEVER ( that means always on ideally ) , and tried turning on / off wifi optimization, avoid poor connections is not ticked.
Even after doing everything the wifi is turned off after sometime and when i turn on Screen it turns it back! How to do I solve this?? I am using STOCK rom, with just root.. No other battery saver etc. app installed.
Click to expand...
Click to collapse
Am i correct in understanding that you don't want it to disconnect? The option in the settings is "Keep wifi on during sleep". If you have it at Never, then it will disconnect when the phone goes into sleep. It should be placed on Always because you want it to be on even during sleep
Flowed and Tapped from my Nexus
fixed the wifi problem
Heya! My first post!!!
So, i had the same problem on my Allview P5 Quad.
The guys from Allview released an update for my phone based on 4.2.1 and i thought the problem was from them. I had WiFi turned on and after a few minutes from entering sleep mode, the WiFi got disconnected, both WiFi and data. I have installed the last update again and again, rooted, unrooted, tried every option from WiFi and i still had the same problem.
So i timed the time when the WiFi disconnects and it was exactly 6 minutes. So i thought that it must be an option that does this. So i unchecked the Quick Power Saving icon from Switches and ... SURPRISE! My WiFi stays on continuously. So, the problem is from the system power saving settings. I hope this helps all of you.
P.S. Love this forum! Thanks for all your help!
I believe I found the problem, some how it is not the phone but my wifi router (and all routers) is the problem. Go into your router settings and look for the "Beacon Interval" and set that number to 50. I'm not going to explain what the beacon interval is, go google it and you will see. I switched mine and now the wifi on my phone does not switch off when in deep sleep.
I have read allot about problems relating to deep sleep, but failed to find a solution.
my device wont go to deep sleep after I am using my Bluetooth headset, for example, in the morning while i'm at home everything is ok and then I turn my headset on, drive to work, and turn the headset off. the device fails to deep sleep from the moment I turn the headset on and it keep even after I turn the headset off.
i see in betterbetterystats that the "suspend_backoff" is keeping the device on.
I don't have allot of knowledge about kernels and wakelock so I need help finding the solution.
if needed I can provide log files from betterbetterystats and wakelock doctor.
current ROM: KitKatComet / Halley (v1.0)
kernel: the one provided with ROM
the problem is on all ROMs since 4.3 and up...
THANK YOU
Known issue on JB and above ROMs, no fix has been found so far.