Has there been any resolution to the 1 - 2 second wake up lag yet? I've seen several "fixes" like reducing the resolution of the lock screen wallpaper etc but none of these work for me. I've experienced the lag on KE7 stock ROM, Cognition ROM, Villain ROM and now on Lite'ning ROM.
Not sure if I agree that it's being caused by the CPU clocking down when the phone is asleep either. When I use SetCPU to set the minimum clock speed to 1.2Ghz the wake up lag is still there.
Also the lag does not occur when the phone is plugged in and SetCPU is telling me that the phone still clocks down to 200Mhz when asleep and plugged in.
Someone must have some idea what is causing this #$%$## lag.
I use Softlocker Free for this.. Works perfect for me, a bit reduced battery life but not enough to stop me from using it..
Thanks for the reply. I tried Softlocker a while back and found the battery drain pretty heavy. Might give it another go. I was thinking there must be a permanent fix for this lag problem though. Hopefully it's just a matter of someone finding it.
I also noticed the lag on my old i9000 as soon as I updated to GB so know this is across the different samsung models on GB in addition to SGS2. I really do think its the clock going down despite your setcpu settings. Use cpuspy free from market and you will see what I mean. Once its in standby it goes into deep sleep which I believe is lower than 200? But set it to 1200 min and see if cpuspy logs it as going below that just to see
It will happen on every rom right now since they are all based on the firmware. I really think it saves battery going into that clock mode and if someone comes up with a fix the cpu will have to run at a higher clock rate and battery loss will be significantly higher
Sent from my GT-I9100 using XDA App
Mines instant with No Lock.
Sent from my GT-I9100 using Tapatalk
Tell us what you did to stop the wake lock. Is it plugged in though?
Sent from my GT-I9100 using XDA App
I am using Lite'ning rom 1.4 right now, when I press the home button til the screen on take around 0.5 second, is it normally?
I've tried this app,and it did seem work. I'll try to see how about the drain of power.
I was using No Lock and it didn't make any difference. What is really annoying me about this is that some users are seeing the lag and others apparently aren't. The lag on my phone is probably about 1 second. This isn't a really big deal unless this sort of thing annoys you. My iPhone didn't have the lag, my Desire didn't have the lag and I feel a high end phone like this shouldn't have the lag either.
blue265 said:
Once its in standby it goes into deep sleep which I believe is lower than 200? But set it to 1200 min and see if cpuspy logs it as going below that just to see
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
I'll have a play and see.
do you guys get lag when using the power button? I get a small lag when using the home button, but if use the power button its instant.
djsaad1 said:
do you guys get lag when using the power button? I get a small lag when using the home button, but if use the power button its instant.
Click to expand...
Click to collapse
There seems to be nearly as many combinations of symptoms as there are phones. Mine has the same 1s or so lag regardless of how I wake it up. I tried SoftLocker again. Not only does it chew the battery, it was randomly causing my phone not to wake up at all, which then required a reboot. Softlocker has since been uninstalled.
The lag definitely doesn't show itself if the phone is plugged in or if music is playing in the background. Also if the phone has only been asleep for 5 or 10 seconds the lag is generally not there.... but not always. This seems to be inconsistent.
Then there are the fortunate users who aren't seeing the lag at all..... unless of course they are failing to mention that they have something running in the background like the music player that is stopping the phone going into deep sleep.
All I know for sure is that it's a PITA that Samsung needs to address. Given that I've read it was an issue with the S, I'm not holding my breath on that one though.
appro77 said:
There seems to be nearly as many combinations of symptoms as there are phones. Mine has the same 1s or so lag regardless of how I wake it up. I tried SoftLocker again. Not only does it chew the battery, it was randomly causing my phone not to wake up at all, which then required a reboot. Softlocker has since been uninstalled.
The lag definitely doesn't show itself if the phone is plugged in or if music is playing in the background. Also if the phone has only been asleep for 5 or 10 seconds the lag is generally not there.... but not always. This seems to be inconsistent.
Then there are the fortunate users who aren't seeing the lag at all..... unless of course they are failing to mention that they have something running in the background like the music player that is stopping the phone going into deep sleep.
All I know for sure is that it's a PITA that Samsung needs to address. Given that I've read it was an issue with the S, I'm not holding my breath on that one though.
Click to expand...
Click to collapse
Don't want to fork/derail the thread, but are you guys experiencing only the "Wake Up Lag" or also the lag when pressing the Home button while unlocked. I see some lag when using the home button to go back to Homescreen 1 for example. In case you folks are seeing lag in both the cases like me, could it be that both have the same underlying cause.
There is this other theory about the bundled Voice Talk app from Vlingo having the shortcut of Home button double tap, which causes any Home button tap to wait until the double tap window before doing its thing. I don't see that mentioned in this thread, but it kind of makes sense for the Home button lag, but perhaps not so much for the Wake lag (at least I could not think of a reason for that to happen). What do you guys think about both these problems?
appro77 said:
Then there are the fortunate users who aren't seeing the lag at all..... unless of course they are failing to mention that they have something running in the background like the music player that is stopping the phone going into deep sleep.
All I know for sure is that it's a PITA that Samsung needs to address. Given that I've read it was an issue with the S, I'm not holding my breath on that one though.
Click to expand...
Click to collapse
Well well finally users are reporting this problem, good to see its not only me.
Anyway, I don't think the Phone goes to any underclocked frequency when it goes to sleep. Cause if you can test SetCPU by setting it to 200 MHz then you will notice that in 200 MHz the phone turns itself off, you have to turn it on manually. So the problem is related with firmware definitely. And there are no fortunate users, some users don't take this as a problem, some don't notice it and some notice but doesn't agree, but here or there everyone has the bug. I hope the issue will be fixed in future firmware upgrade.
Regards.
Sent from GT-I9100
It may seem crazy but...
The delay depends heavily on the lock image you choose for lock screen.
With stock image it's instant, with custom background it slows down significantly.
My theory is that custom image is being resized while low Cpu frequency, it takes a while.
Sent from my GT-I9100 using XDA Premium App
rdy2go said:
It may seem crazy but...
The delay depends heavily on the lock image you choose for lock screen.
With stock image it's instant, with custom background it slows down significantly.
My theory is that custom image is being resized while low Cpu frequency, it takes a while.
Sent from my GT-I9100 using XDA Premium App
Click to expand...
Click to collapse
I've just tested that, it's the same no matter what background I use.
Wow..
Seems like the thread I can finally count on! Lots of behavior that I experience as well. I have the home button lag and the wake up lag and it's bugging me.
One thing to note.. The wake up lag is worse when you have an SD card inserted -> This scenario was the same for the SGS1 too. Anyone can confirm this?
I'm using No Lock as personal preference but the lag is always there. All behavior you guys mention (abt headphones plugged in, charging, within 5-10secs) are all being observed.
Eagerly waiting for a fix!
I had lag on my first SGS2, but it was worse that yours, at about 9-10 seconds (that's no exaggeration) plus high battery drain (Only getting about 6-7 hours battery at normal use). Went and got a new S2, no lag, and battery lasts 36 hours now.
It may not be the case with yours that its faulty, but I think I fixed the first SGS2 by flashing a newer rom, then doing hard reset and clearing cache's. I now have 2 shiny new SGS2's working as normal.
TheBishopOfSoho said:
I had lag on my first SGS2, but it was worse that yours, at about 9-10 seconds (that's no exaggeration) plus high battery drain (Only getting about 6-7 hours battery at normal use). Went and got a new S2, no lag, and battery lasts 36 hours now.
It may not be the case with yours that its faulty, but I think I fixed the first SGS2 by flashing a newer rom, then doing hard reset and clearing cache's. I now have 2 shiny new SGS2's working as normal.
Click to expand...
Click to collapse
I did flash a newer ROM, but didn't do a hard reset.. all my apps were intact. Perhaps I will spend sometime on it this weekend. By the way, which ROM did you flash on your first SGS2 that fixed the problem?
Also, I tried SoftLocker and it works!! The only downside is the battery life. I loose about 4-5% per hour while I was asleep. That bring me to say that the delay is not caused by the voice input function, but rather due to the device going into deep sleep (which may be normal). But it's the waking up that's taking long.
Still seeking for more ideas...
MasK said:
Also, I tried SoftLocker and it works!! The only downside is the battery life. I loose about 4-5% per hour while I was asleep.
Click to expand...
Click to collapse
Yes, I found that SoftLocker is not really a solution because of the battery drain and some other bugs it introduced.
Anyone who is experiencing this lag should be contacting Samsung. I contacted Samsung Australia and they told me they had not heard of the problem. If everyone who is experiencing the problem reported it to Samsung, I think there may be a far better chance of a fix. Anyone who is annoyed by this bug, please email Samsung via the link on their website. If they are flooded with complaints they "may" act and provide a fix.
Related
I think something's gone wrong with my player, but I'm not sure because I'm new to these types of devices. In any event, here goes: three days ago I got a brand new Samsung Galaxy player. Because it was new, I basically used it to death on the first day exploring all the features, setting up accounts, downloading a few apps, etc. With that amount of heavy usage, I got 5 hours worth of battery life-- YouTube, Angry Birds, GPS, wifi, typing, browsing the net, radio station, downloading apps, snapping pictures, transferring/playing media files, etc.
Then the battery went low, so I recharged. Having gotten everything out of my system, I started using the player casually. I thought, "If I used the player insanely the first day and got 5 hours of it, I'm bound to get at least 8-10 hours now."
Nope. Battery drain became massive-- at the most I got 2 1/2 hours before the battery went low. Charged it again. Not only was the massive drain still there, but now something new developed-- the unit started becoming hot to the touch after a few minutes. I hoped it was just a temporary problem, but nope, the problem remained, getting worse when I would type.
I also had some weird stuff happen the second day I used the player. I got a "bootup screen" when powering the unit back on. Later that same day I got the "Downloading... please do not turn off target!" screen with the yellow Android robot sign.
On my third day, things seemed to go from bad to worse, to the point where at times I would lose 1% of battery power every 1-2 minutes just playing one mp3 song or switching on radio. In fact, in one instance just 3 minutes after powering up the device I would go from 100%-97%.
I Googled myself silly about this and tried everything to no avail--uninstalled all 3rd party apps, factory reset, turned syncing off and avoided wifi like the plague (stats for battery usage never went above 5%). I double and tripled checked my stats. Battery stats would only show a handful of about 6 basic apps running at any given time, each having between 1-10% of usage at the most, with the display always using the battery the most (between 55-89%).
I don't know if this means that the display is the culprit, but if it is, something's wrong because it's set to "automatic brightness" and I also have "power save mode" on.
In any event, no matter what I do now, I'm lucky to get 2 hours on this player. Remember, it's only a few days old. I'm wondering if there's something I missed in troubleshooting this issue or maybe there's something faulty and I need to return it?
Thanks.
Download easy battery saver from google play i had the same problem and my battery increased alot my settings are
Advance mode: lock & unlock is checked WiFi is checked brightness and battery saving brightness is checked and sleep schedule is also checked
You should also install easy task manager and use the widget both combined work great
Sent from my GT-I9000 using XDA
I suppose you haven't rooted your device or installing any custom ROM, right? If that's correct, seeing download mode when rebooting sound odd to me.
When your device is heating up, that means some apps are running wild and using lots of cpu. What I can suggest is to boot into recovery (power+vol up+home) and perform a factory reset there.
If that still doesn't work, you may need to return it.
Thanks for your response, guys...
j21098, I'll try what you suggested and come back later with the results. But I can't download any apps right now because the battery has once again gone low... it only lasted around 2.15 hours this time. *sigh*
WT Ho... No, I did not root the player and I did the factory reset both ways-- in the player itself and the Vol+Power Button thing. That's why I was unnerved by the Downloading Target thing... I hadn't downloaded or done anything.
Incidentally, after making my post, I tried using the player with head phones in the entire time and that seemed to have resolved some of the heating issues. That's weird, because it's not like I've been using the speakers to play hours and hours of music at 100 decibels. I had them on just to navigate through the screens/ surf the web, play Angry Birds (now uninstalled), and type.
And the entire first day I had the player I used speakers to play an hour or so of YouTube with no heating issues. But now just five minutes of merely clickity clacking on the keyboard and the thing turns into a toaster. Is it normal for speakers to cause that much overheating?
In any event, I'm currently waiting for the player to charge up so I can download the apps that j21098 and let you know what happened. Thanks for your responses once again. I'll be back.
Thanks!
Hi, guys! I'm back!
I wound up figuring out the problem. A lot of the overheating seemed to have come from the little vibration the player makes when you tap the screen or use the keyboard. Using the speakers too much seems to contribute to battery drain but not as badly as the vibration. I turned off that setting and now everything seems to be okay.
P.S. Thanks for the great advice about managing energy levels/ factory resetting, anyway. I definitely will be using the app to manage CPU usage and now know how to "factory reset" using the buttons (as opposed to using the menu).
minababe said:
Hi, guys! I'm back!
I wound up figuring out the problem. A lot of the overheating seemed to have come from the little vibration the player makes when you tap the screen or use the keyboard. Using the speakers too much seems to contribute to battery drain but not as badly as the vibration. I turned off that setting and now everything seems to be okay.
P.S. Thanks for the great advice about managing energy levels/ factory resetting, anyway. I definitely will be using the app to manage CPU usage and now know how to "factory reset" using the buttons (as opposed to using the menu).
Click to expand...
Click to collapse
You should disable the unnecessary
vibrations it wastes more battery im a heavy user i play hd games, listen to music,and watch movies
Sent from my GT-I9000 using XDA
I make it short:
Yeah another wifi/ battery thread. But the only one with an actual solution for pi poor battery life after 21 update. Some people reported it helped also with the sod.
Wifi sucks battery dead.
Some people let all sorts of juice sucking bat-control apps running to find out that stock app reading is not lying: The bloody wifi never turns off even set to do so in the settings and just kills the battery of the device.
If this is your workaround you owe me a thanks . If you are an Asus employee testing poor battery issue give me credits in the fixing OTA by repairing the 'never' settings:
Go to
settings, w-lan,advanced (click on the three dots in the upper right corner, there it is), keep_wifi_on_during_sleep:
Instead of setting it to 'never', set it to 'only when plugged in'.
Now put your machine in sleep, wake it after 30min or even much less and BOOOOOOM! here we go:
You will see in the battery settings, that your wifi just has stopped pausing. Depending on how long ago the battery cycle has started you will see two shorter bricks instead of a long one as before. While waking your machine concentrate on the battery icon and you will notice the wifi-icon popping up just a second after you have woken the screen.
Of course this works also with shorter breaks but I'm not sure what is the shortest interval. Longer sleep period opens the gap in between two wifi-sessions wider. So this makes the working proof easier visible for the eye.
Sort of really a shame that Asus, Google and Nvidia have hybrid, wrongly programmed and even forgotten settings in their setup. (see my thread about the multitasking of the HTC1X http://forum.xda-developers.com/showthread.php?t=1599214 Maybe helps your multitasking issue.
But as we know, nobody is perfect .... except for xda!!
And then, many report, they don't have this problem at all. Very strange that not everybody is affected by this blind setting.
If this solution doesn't help your device,I am sorry for you. Maybe you have to stick to the bat-control app and learn how to read it, or RMA your device.
Did the job for me.
So I am ready for summer to join in, got enough juice for the IPS+ screen to stun the sun the whole day lun . Rock'n Roll
Edit 121002:
JellyBeans workaround as well.
Edit 120616:
Thank you Asus that the .28 firmware makes my workaround obsolet. Now get rid of this arm5 coding and let the bugger run !!
Edit 2:
Title changed from 'Asus you owe me a blowjob' to something less attractive for trolls.
Should be an obvious solution for everyone. But took me a hell of time to use the next best (second) obvious setting for my w-lan and get the battery saving.
Edit:
Please don't abuse my thread to flame, blame or mob your boss, retailer, dog or whomever. Only confirmation or non-confirmations welcome. If you find another or better or additional solution in the future or the past please feel free to post it. I did not have the time yet to check for the actual amount of powersafe but regarding my normal readings we are gaining the whole lost lot back and don't need to throttle down or ruin our eyes. I reckon the bat is gonna be better because now some of the ASUS optimisation hits some ground.
If you want me to fled off, I have stolen your ideas or you are an ASUS employee with no job-offer, don't PM me.
Thanks
I have been using this setting for a while and while I do get better battery life using the "when plugged in" setting than the newer "disconnect during sleep" setting, in general battery life is still worse in .21 than in previous builds and for me WiFi alone still accounts for more than 60% of my average battery usage according to the battery settings menu. For all of my other Android devices the screen is the largest single user of battery.
It does not happen to everyone. I have it on "never" and as soon as i click the power button, wifi turns off... if i wake the tablet right away (2 or 3 seconds later), i see the wifi reappearing and reconecting. So, for me, the wifi turns off instantly.
In the battery graph my wifi line is nonexistant whenever the tablet is sleeping.
I believe the wifi options are implemented correctly (sort of). But for some reason, it doesnt seem to work for some users.
Another way to save battery is to increase the wifi scanning interval... but that is for when you are using wifi.
I guess, for those experiencing the battery drain, it may be a good temporary workaround to use the solution mentioned by the OP.
eddymonti said:
It does not happen to everyone. I have it on "never" and as soon as i click the power button, wifi turns off... if i wake the tablet right away (2 or 3 seconds later), i see the wifi reappearing and reconecting. So, for me, the wifi turns off instantly.
In the battery graph my wifi line is nonexistant whenever the tablet is sleeping.
I believe the wifi options are implemented correctly (sort of). But for some reason, it doesnt seem to work for some users.
Another way to save battery is to increase the wifi scanning interval... but that is for when you are using wifi.
I guess, for those experiencing the battery drain, it may be a good temporary workaround to use the solution mentioned by the OP.
Click to expand...
Click to collapse
another way to MAKE SURE you save battery is turn the darn thing off and shutdown and then when you need it's ready to go. I been doing this more recently and it defeats the purpose of tablet, but hey, when i need to use it, after the boot up its on. not trying to be funny.
Let's not get carried away. While a good suggestion it's far from a real solution for all the people that are encountering this issue. It's kind of like suggesting just turning off your tablet when your not using it to prevent battery drain.
prettyboy85712 said:
Let's not get carried away. While a good suggestion it's far from a real solution for all the people that are encountering this issue. It's kind of like suggesting just turning of your tablet when your not using it to prevent battery drain.
Click to expand...
Click to collapse
you got me laughing. that was a good one. Op meant well but this tip has been known for a long time.
im still laughing.
demandarin said:
you got me laughing. that was a good one. Op meant well but this tip has been known for a long time.
im still laughing.
Click to expand...
Click to collapse
What's even funnier is that the OP is serious about his discovery. Guy probably thinks ASUS owes him something.
Nonetheless, thanks for the redundant tip OP.
Auto flight mode
I always install an auto flight mode program that will turn off the wifi when the screen turns off since most widgets prevents the system from turning it off and going into deep sleep.
almightywhacko said:
I have been using this setting for a while and while I do get better battery life using the "when plugged in" setting than the newer "disconnect during sleep" setting, in general battery life is still worse in .21 than in previous builds and for me WiFi alone still accounts for more than 60% of my average battery usage according to the battery settings menu. For all of my other Android devices the screen is the largest single user of battery.
Click to expand...
Click to collapse
Thanks for confirming,
eddymonti said:
It does not happen to everyone. I have it on "never" and as soon as i click the power button, wifi turns off... if i wake the tablet right away (2 or 3 seconds later), i see the wifi reappearing and reconecting. So, for me, the wifi turns off instantly.
In the battery graph my wifi line is nonexistant whenever the tablet is sleeping.
I believe the wifi options are implemented correctly (sort of). But for some reason, it doesnt seem to work for some users.
Another way to save battery is to increase the wifi scanning interval... but that is for when you are using wifi.
I guess, for those experiencing the battery drain, it may be a good temporary workaround to use the solution mentioned by the OP.
Click to expand...
Click to collapse
Nice you confirm as well . Unfortunately solutions tend to be temporary, sighh.
flipper2006 said:
another way to MAKE SURE you save battery is turn the darn thing off and shutdown and then when you need it's ready to go. I been doing this more recently and it defeats the purpose of tablet, but hey, when i need to use it, after the boot up its on. not trying to be funny.
Click to expand...
Click to collapse
Your way takes far too much time for me to act spontaneous. With my changed settings it's doing it automatically again, just as was intended the 'never' setting. Unless you charge the tablet by cord, the wifi turns off while you put the tablet asleep. I say settings are messed up.
prettyboy85712 said:
Let's not get carried away. While a good suggestion it's far from a real solution for all the people that are encountering this issue. It's kind of like suggesting just turning off your tablet when your not using it to prevent battery drain.
Click to expand...
Click to collapse
Don't think you got my point, surely I am not getting yours. you quote your preposter who obviously disagrees with you.
But we both think it sucks, thanks.
demandarin said:
you got me laughing. that was a good one. Op meant well but this tip has been known for a long time.
im still laughing.
Click to expand...
Click to collapse
Glad you are having fun and proud you are tolling my thread as well vely sholt time
ungraph said:
What's even funnier is that the OP is serious about his discovery. Guy probably thinks ASUS owes him something.
Nonetheless, thanks for the redundant tip OP.
Click to expand...
Click to collapse
You are welcome. You bet I am and I do and please show me the redundance, maybe demandarin can help you while I get a little nap now.
XXRay said:
I always install an auto flight mode program that will turn off the wifi when the screen turns off since most widgets prevents the system from turning it off and going into deep sleep.
Click to expand...
Click to collapse
Yeah I seen you mentioning this, but I get rid of bloatware so why would I fill up with supposed stock apps. As I said, worked best for me
Thanks guys for the the exchange, keep on rowing fellas ..
ill be the first one to Thank the OP as no one has. At least he is trying to help and find a solution. Even if it was something already known for the longest time. Sorry if the humor wasn't funny to you. Maybe he didn't know people already knew about this. which is totally fair.
to the OP, have you noticed that when you put wifi to stay on only when plugged in, when in sleep, that it takes a little while for wifi to come back online? meaning if you use the setting you said, then put the prime to sleep unplugged, then wake it back up, wifi doesn't connect back immediately. it takes a few seconds to come back online. that's the only thing I personally don't like about it.
demandarin said:
ill be the first one to Thank the OP as no one has. At least he is trying to help and find a solution. Even if it was something already known for the longest time. Sorry if the humor wasn't funny to you. Maybe he didn't know people already knew about this. which is totally fair.
to the OP, have you noticed that when you put wifi to stay on only when plugged in, when in sleep, that it takes a little while for wifi to come back online? meaning if you use the setting you said, then put the prime to sleep unplugged, then wake it back up, wifi doesn't connect back immediately. it takes a few seconds to come back online. that's the only thing I personally don't like about it.
Click to expand...
Click to collapse
yeah but personally this means to me it's working correctly. For the wifi to come back on instantly it would have to keep a connection and just not transfer data, when in deep sleep it completely turns off the wifi radio. When you wake it back up the radio turns back on, and it needs to connect to the AP all over again. This means the wifi was in a deep sleep (actually turned off the tab is in deep sleep) and it is working correctly.
I really wonder why every thread in this forum sooner or later becomes a trolling/flaming thread....
So guys, as usual (*sigh*) please stay on topic.
Trolling and flaming won't be tolerated but will be rewarded by other gifts like infractions and bans.
@OP: You might think about stoping posting in red: It usually implies a high rate of aggressivity towards other members.
Even if this might not be actually true in your case, other members still might missunderstand you.
On topic: This "fix" is really known since like, dunno, Froyo times? At least this setting is there already for ages.
Apart from that it should be obvious that turning off the Wifi drains less power.
However, you had good intentions so don't destroy them by flaming other members.
If you feel attacked by any post, just report it (obviously this goes for all members)
Thanks for clearing up, Diamondback,
What has been known since Froyo x.x is still worth mentioning. Many user have just started their android career because nowadays the hardware and the software are worth it. And once in a while talking about an old known tip is worthwhile especially since nobody else did.
@ demandarin ;-)
Edit on topic (referring to Diamondback):
This was no flame.
Asus shoot themselves in the foot, some people in my thread the same!
Obviously both the feet and so I call trolls by name,
themselves they should blame.
Right? Obviously not, which is a shame.
My only wrong the color of which I was ignorant,
shame on me!
I will change the teasing thread title
from Asus gets busted in Asus will get the game
I've been using this option since day 1. The problem is not that the wifi doesn't sleep. It's more so that it sucks way too much power when it is on.
I have an iPad2 3g as well which I received as a birthday gift so I kept it and with wifi and 3g always on, I still get 5-7 days of use.
On the Prime its dead under 2 days if always on and 3-4 days if off when asleep.
So it's most likely an optimization issue or driver issue.
Maybe the transmit power should go to low when asleep rather than staying strong.
Who knows. Regardless this can be fixed by Asus if they really look into it.
Sent from my GT-I9100 using Tapatalk 2
Elisha said:
I've been using this option since day 1. The problem is not that the wifi doesn't sleep. It's more so that it sucks way too much power when it is on.
I have an iPad2 3g as well which I received as a birthday gift so I kept it and with wifi and 3g always on, I still get 5-7 days of use.
On the Prime its dead under 2 days if always on and 3-4 days if off when asleep.
So it's most likely an optimization issue or driver issue.
Maybe the transmit power should go to low when asleep rather than staying strong.
Who knows. Regardless this can be fixed by Asus if they really look into it.
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
Actually the iPad has it's SW architecture on the plus side. I think the high battery drain on the TFP (and/or Android in general) is also strongly linked to the number of apps synching in background.
Maybe it can be fixed with drivers. Lowering transmit power sounds good. Could be that Asus optimized to much for the folks complaining about wifi performance....
The setting to turn off wifi while the tablet sleeps makes no sense for my use case. I mean for a wifi only device, it makes not much sense to turn it's connection to the outside off. How will I then receive notifications on gtalk, mail and so on? If I would like to safe power that way, I rather turn it completely off.
For a phone with 3g / edge data connection it might make sense. This applies for the 3g iPad as well.
I agree, it got a bit worse with .21 but for me battery life is still awesome.
Thanks anyway for bringing it to the mind of new users. Although I wouldn't call this a fix but a workaround.
Sent from my Transformer Prime TF201
Elisha said:
I've been using this option since day 1. The problem is not that the wifi doesn't sleep. It's more so that it sucks way too much power when it is on.
I have an iPad2 3g as well which I received as a birthday gift so I kept it and with wifi and 3g always on, I still get 5-7 days of use.
On the Prime its dead under 2 days if always on and 3-4 days if off when asleep.
So it's most likely an optimization issue or driver issue.
Maybe the transmit power should go to low when asleep rather than staying strong.
Who knows. Regardless this can be fixed by Asus if they really look into it.
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
Yes, I agree about the drain but isn't it probably because of the stylish casing! So nothing we can change there, but Asus could clock it down while asleep as you suggest.
tobi01001 said:
Actually the iPad has it's SW architecture on the plus side. I think the high battery drain on the TFP (and/or .....
I agree, it got a bit worse with .21 but for me battery life is still awesome.
Thanks anyway for bringing it to the mind of new users. Although I wouldn't call this a fix but a workaround.
Sent from my Transformer Prime TF201
Click to expand...
Click to collapse
You are right I have already changed the op from fix to workaround.
tobi01001 said:
Actually the iPad has it's SW architecture on the plus side. I think the high battery drain on the TFP (and/or Android in general) is also strongly linked to the number of apps synching in background.
Click to expand...
Click to collapse
My iPad2 goes ding ding ding all night. Lots of apps syncing. 3 email accounts. CNN app, and multiple other apps.
But I think iOS uses a very low power state for background sync while in sleep compared to Android.
Sent from my GT-I9100 using Tapatalk 2
Solved my problem.
thank you
Not sure if it's relevant because this was posted for the GS2 but it could also help with wifi drain on the prime.
from this thread: http://forum.xda-developers.com/showpost.php?p=25876666&postcount=3
"FAQ
Q: Wakelocks "wlan_rx_wake" wake up my device constantly what I can do about it?
A: The problem is neither Android nor the kernel, but the router and the (Windows7) network. In the network properties, uncheck "IPv6", disable the service "IP Helper", "Shell Hardware Detection" and "Windows Media Player Network Sharing Service", which provide ongoing Traffic. Then they scored again 98% of deep sleep."
And how you disable ipv6 on your phone/tablet is with a script but the value in the file gets recreated everytime you turn wifi on and off. So if you disable ipv6 then turn wifi off, then back on, ipv6 will be enabled again. I got around this by a tasker profile that will run every time my tablet connects to a wifi network. So it disables ipv6 right away again. You could do this in an init.d script(or in sysctl) as well but then you have the issue of it resetting itself if you turn wifi off/on
If you have tasker create a new profile for when wifi is connected, then run a shell script task, and check run as root. This is the command echo 1 > /proc/sys/net/ipv6/conf/wlan0/disable_ipv6
to enable it just replace the 1 with a 0. You can also run the command in a terminal window if you just want to test it. I did it for my phone, and I just set it for my prime so I'll see if it drains less battery with it off..
131313 said:
Yes, I agree about the drain but isn't it probably because of the stylish casing! So nothing we can change there, but Asus could clock it down while asleep as you suggest.
You are right I have already changed the op from fix to workaround.
Click to expand...
Click to collapse
I would just like to say thanks and let you know that I had SOD problems on my prime (as bad as up to once every day in frequency) for a very long time since .21 came out, after trying your work around (several weeks ago) ever since I have not had a single SOD sleep of death issue whatsoever.
I always suspected it was dock recharging causing the SOD fault but maybe it was a bum wifi stack or something, so thank you very much my tab is much more stable because the suggestion you've shared with me.
Unfortunately it does not help any flickering or GPU bugs I tend to get on occasion. I truly hate .21 it is so god awful for GPU, SOD and storage I/O.
I should just man up and downgrade but meh, sif i have the time do it
But yeah, thanks heaps, your workaround is an awesome suggestion.
I am having an issue with my MoPho severely overheating and shutting off. But strangely it only seems to happen when I am outside. The first time I noticed it was when I went fishing. My phone had about 80% charge, and when I picked it up maybe 30 mins later is was scorching hot. To the point that it burnt me. And it had shut off. I didn't have it in the sun or anything. It was in the shade inside a bag. I was not able to get it to turn on even with a battery pull even after it had cooled down. The battery completely drained in a matter of minutes. I couldn't even get it to charge in the truck on the car charger, either. It got too hot on the charger to the point it wouldn't even get a charge. This has happened about 3 or 4 times since. It will go from a full battery, get super hot, and completely drain within minutes. This never used to happen in the house, it was only an issue outside. until today. Went fishing, phone had full charge. It managed to hold the battery for a couple hours, unlike the other times, but eventually got hot and died. Then when I got home, plugged it into the charger and went to sleep, woke up a couple hours later and it was burning hot, and had no charge. Other things on it are acting weird now, as well. The screen keeps turning on and off every few seconds by itself. I don't know what the issue is, but I might have to switch back to stock if I can't find a solution. Because eventually this is going to fry my phone. And I don't want that to happen. It is also a huge inconvenience for your phone battery to drain in a matter of minutes and become a useless paperweight when you are in the middle of nowhere and need a form of communication in an emergency.
Has anyone else had this issue and found a solution?
Galaxy_S_ said:
I am having an issue with my MoPho severely overheating and shutting off. But strangely it only seems to happen when I am outside. The first time I noticed it was when I went fishing. My phone had about 80% charge, and when I picked it up maybe 30 mins later is was scorching hot. To the point that it burnt me. And it had shut off. I didn't have it in the sun or anything. It was in the shade inside a bag. I was not able to get it to turn on even with a battery pull even after it had cooled down. The battery completely drained in a matter of minutes. I couldn't even get it to charge in the truck on the car charger, either. It got too hot on the charger to the point it wouldn't even get a charge. This has happened about 3 or 4 times since. It will go from a full battery, get super hot, and completely drain within minutes. This never used to happen in the house, it was only an issue outside. until today. Went fishing, phone had full charge. It managed to hold the battery for a couple hours, unlike the other times, but eventually got hot and died. Then when I got home, plugged it into the charger and went to sleep, woke up a couple hours later and it was burning hot, and had no charge. Other things on it are acting weird now, as well. The screen keeps turning on and off every few seconds by itself. I don't know what the issue is, but I might have to switch back to stock if I can't find a solution. Because eventually this is going to fry my phone. And I don't want that to happen. It is also a huge inconvenience for your phone battery to drain in a matter of minutes and become a useless paperweight when you are in the middle of nowhere and need a form of communication in an emergency.
Has anyone else had this issue and found a solution?
Click to expand...
Click to collapse
Many people have experienced overheating problems on our cm9. Some people including self have fixed it by just doing a fresh install of cm9 as it seems like just a fluke. Im sure the fact that were running a gingerbread kernel on ics doesnt help. Also, try dropping the battery down to 1200 from the stock 1300, see if that helps.
Sent from my MB855 using XDA
Acvice said:
Many people have experienced overheating problems on our cm9. Some people including self have fixed it by just doing a fresh install of cm9 as it seems like just a fluke. Im sure the fact that were running a gingerbread kernel on ics doesnt help. Also, try dropping the battery down to 1200 from the stock 1300, see if that helps.
Sent from my MB855 using XDA
Click to expand...
Click to collapse
Someone mentioned changing the overclock from the stock 1300 down to 1000 in another thread. Is that the same thing as what you're talking about? Or is there a separate setting for the battery? I did try dropping it down to 1000 but that's when the screen started turning on and off by itself. And LWP's stopped working properly. They would get stuck and seizure. Even after I changed it back to the default 1300. So I went into CWM and just reflashed the ROM. No more screen turning on and off or LWP's acting weird. But as far as the overheating problem I can't be sure I guess until I go fishing again or put it in another situation in which it's done it previously.
Galaxy_S_ said:
Someone mentioned changing the overclock from the stock 1300 down to 1000 in another thread. Is that the same thing as what you're talking about? Or is there a separate setting for the battery? I did try dropping it down to 1000 but that's when the screen started turning on and off by itself. And LWP's stopped working properly. They would get stuck and seizure. Even after I changed it back to the default 1300. So I went into CWM and just reflashed the ROM. No more screen turning on and off or LWP's acting weird. But as far as the overheating problem I can't be sure I guess until I go fishing again or put it in another situation in which it's done it previously.
Click to expand...
Click to collapse
I work outside every day and its bout 100 degrees out consistantly now... I'm not running cm9 anymore but I've noticed I still get the occasional overheat while its in my pocket, it most definitely gets annoying sometimes having to pull the battery and let everything cool down but I think the benefits outweigh the annoyance level a million to one. I guess what I'm saying is you're not alone friend, it definitely happens to me as well. I have my CPU set to 1k though and messed around with undervolting as well and feel like I get a little better results this way. Keep playing with your settings until you find the one that works best for you is the advice I can give. Good luck!
Sent from my MoPho running MIUI.us official port!
Party Spock is in the house, everybody have a logical time!
Galaxy_S_ said:
Someone mentioned changing the overclock from the stock 1300 down to 1000 in another thread. Is that the same thing as what you're talking about? Or is there a separate setting for the battery? I did try dropping it down to 1000 but that's when the screen started turning on and off by itself. And LWP's stopped working properly. They would get stuck and seizure. Even after I changed it back to the default 1300. So I went into CWM and just reflashed the ROM. No more screen turning on and off or LWP's acting weird. But as far as the overheating problem I can't be sure I guess until I go fishing again or put it in another situation in which it's done it previously.
Click to expand...
Click to collapse
Yeah its the same thing. Remember, our processor is technicallynot supposed to be over 1000 per core for a reason. People just like to push things to the edge. The whole lwp problem is expected and everyone experiences this with the our ice roms. That also is due to lack of proper 2d libs. But I'm glad most of your problems have subsided. Run your processor at 1000 and I'm sure the overheating will lessen. On a powerful dualcore phone like the photon 1300 from 1000 is miniscule anyway.
Acvice said:
Yeah its the same thing. Remember, our processor is technicallynot supposed to be over 1000 per core for a reason. People just like to push things to the edge. The whole lwp problem is expected and everyone experiences this with the our ice roms. That also is due to lack of proper 2d libs. But I'm glad most of your problems have subsided. Run your processor at 1000 and I'm sure the overheating will lessen. On a powerful dualcore phone like the photon 1300 from 1000 is miniscule anyway.
Click to expand...
Click to collapse
Alright. I will try it again. But I just love my LWP's =[ I always have a lwp on. I have never experienced the problem with the lwps until I set the processor to 1000. But I guess it comes down to sacrificing my wallpaper to stop it from overheating. If that's what it takes to fix the problem. Hopefully once the stable version is released everything will work like it should without having to sacrifice anything.
It did overheat again the other day. I did have Watchdog on my phone and I was on facebook messenger the other morning and it started acting up, I had my phone in my hand and within a couple minutes it got burning hot, and then right after, Watchdog popped up with a notification that messenger was above threshhold. It was running at 49% CPU or something. And come to think of it I would always get notifications about fb messenger "misbehaving". So I came to the conclusion that it could be either messenger or watchdog causing most of my problems. I deleted watchdog to see if it fixes my problems. I'm hoping it isn't messenger. Because I need my FB. lol. But I haven't really used messenger on my phone since I deleted watchdog. So we'll see. If that didn't solve it, then I will sacfrifice my lwp and set the processor back to 1000.
Galaxy_S_ said:
Alright. I will try it again. But I just love my LWP's =[ I always have a lwp on. I have never experienced the problem with the lwps until I set the processor to 1000. But I guess it comes down to sacrificing my wallpaper to stop it from overheating. If that's what it takes to fix the problem. Hopefully once the stable version is released everything will work like it should without having to sacrifice anything.
It did overheat again the other day. I did have Watchdog on my phone and I was on facebook messenger the other morning and it started acting up, I had my phone in my hand and within a couple minutes it got burning hot, and then right after, Watchdog popped up with a notification that messenger was above threshhold. It was running at 49% CPU or something. And come to think of it I would always get notifications about fb messenger "misbehaving". So I came to the conclusion that it could be either messenger or watchdog causing most of my problems. I deleted watchdog to see if it fixes my problems. I'm hoping it isn't messenger. Because I need my FB. lol. But I haven't really used messenger on my phone since I deleted watchdog. So we'll see. If that didn't solve it, then I will sacfrifice my lwp and set the processor back to 1000.
Click to expand...
Click to collapse
Fb messenger gets a lot of hate, i cant say thats your problem but you never know. Try out a chat client called imo from the play store instead. It supports fb as well as others and is leaps and bounds better than fb messenger.
Sent from my MB855 using XDA
Acvice said:
Fb messenger gets a lot of hate, i cant say thats your problem but you never know. Try out a chat client called imo from the play store instead. It supports fb as well as others and is leaps and bounds better than fb messenger.
Sent from my MB855 using XDA
Click to expand...
Click to collapse
Thank you. I will definitely try that =] Thank you. I really hope it fixes the problem. I can't wait for the stable release. haha
Hi guys,
My Atrix 4G is acting weird for the past 2 days. I was running Nov 25 CM7 nightly with faux 1GHZ kernel when the issue first occurred. The phone got too hot suddenly, it shot up from 32C to 58C in a few seconds and the charge started decreasing from 38% to 15% in 2 to 3 seconds. Before I could realize what happened, the phone turned off. I plugged in my charger after letting it to chill, and the phone started charging.
After sometime, I saw that the phone had charged till 25%. So I booted into CM7. Within no time, the phone got extremely hot and turned off again. It did not start charging till it came to normal temperature.
I somehow managed to flash the stock CM7 kernel, assuming that the issue was with the Faux kernel. After that, the phone was operating at normal temperature for a couple of hours. I thought that the Faux kernel was the culprit and thought that my issue is resolved. But after a couple of hours, I again felt the phone getting too hot in my pocket and before I could react, it turned off.
Please help me. Is the battery dead and needs a replacement? Or is it with the ROM? I've been running CM7 with stock/Faux kernel for many months and never faced such an issue.
Note: The issue started happening some time after I installed two apps. One is the Koi Live Wallpaper and one is the Xperia S launcher. Now both are uninstalled but the issue still persists.
Thanks in advance for your help.
It does sound similar to how a PC would react to an overheating CPU/GPU. In that case, you want it to shut off before permanent damage. Heat does not play well with electronics.
See if you can go under Performance Settings and set it to "powersave" and lower the clock speed to the next lowest setting (912 or 800). If it continues, try to backup everything and do a clean install. If the problem persists, it's not related to software.
Are you having the same issue in recovery? It might prove to be a challenge if it does.
Other suggestions: Remove any case you have on there along with the backing to get more air flow. Try to use it in a cold area, or in front of a fan or something. People have tried linking busted display digitizers with excess heat, might want to be careful.
Sent from my MB860 using xda app-developers app
I have that problem but with ICS/JB roms, the phones gets hot because my cpu is stucked at 750 MHz for some reason i don't know
Normally i don't have those problems with cm7, but when i had it i solve it by just installing another faux kernel. right now i'm running v023 at 1Ghz and it's working properly.
Maybe you can try to fix the permissions under CMW, sometimes that correct some problems
Try CPU spy and see if your phone is running at high clock speed all the time.
Sent from my MB860 using xda app-developers app
Thanks guys for the ideas.
The issue doesn't seem to be related to the ROM or kernel. It is with the hardware, because the phone is heating up even while it is switched off. The battery needs to be removed and after it is cooled, the phone works normally for some hours before it starts heating up again.
If it is getting heated up even while switched off, the issue has to be with the battery or the phone's circuit. Not sure which one is affected and I dont have a replacement battery to test.
Any ideas?
gkarthik16 said:
Thanks guys for the ideas.
The issue doesn't seem to be related to the ROM or kernel. It is with the hardware, because the phone is heating up even while it is switched off. The battery needs to be removed and after it is cooled, the phone works normally for some hours before it starts heating up again.
If it is getting heated up even while switched off, the issue has to be with the battery or the phone's circuit. Not sure which one is affected and I dont have a replacement battery to test.
Any ideas?
Click to expand...
Click to collapse
Are you saying it's overheating while completely powered down or just when screen is off? Is it still under warranty?
エイトリックス から 送ります
thesummoner101 said:
Are you saying it's overheating while completely powered down or just when screen is off? Is it still under warranty?
エイトリックス から 送ります
Click to expand...
Click to collapse
It's overheating when the phone itself is off. It's weird. Looks like the battery is leaking charge. And it is not under warranty
gkarthik16 said:
It's overheating when the phone itself is off. It's weird. Looks like the battery is leaking charge. And it is not under warranty
Click to expand...
Click to collapse
That is weird. Sorry, I can't be further help. Good luck.
エイトリックス から 送ります
Okay, I am having issues with my Note 3. I can run my phone as hard as i want and no problem until i get to about 50-60%. Then, my phone screen will just go black like the battery just died. Now if i plug it in for 1 second and hit the power button it starts booting up and i can immediately unplug it and it returns to 50-60% battery and continues to run fine. But it will not power up without plugging it in for a second. I even have a friend that is having the same issue with his att&t note 3 that has never been rooted ever. Just weird. I am currently running Vision-x vpucnc5 rom with calm kernal. I have tried multiple other roms and the problem still persist. I have even purchased another battery thinking that was the problem. I will include a screen shot of my battery info screen and all you see is a black line when it happened. Please help! Thanks in advance. .
When you run the device hard, is the phone getting hot? Do you have a big case on it? It sounds like the overheating sensor is kicking off the device. On my note 3, when running WiFi Tether Router app and it is downloading a big file say a movie. On 4g LTE at a download speed of 2MB+ the phone has gotten to hot and shut down. My solution is to take it out of the case when downloading.
Maybe plugging the charger into the device resets the overheating sensor?
Here is what I would do, here is a link to the Galaxy tool app http://forum.xda-developers.com/not.../app-one-click-hotspot-enabler-menus-t2816159 download and install. Now you test all the sensors, and check the logcats to see what happened at the black line. Your phone has record of it in the logcats, either in the IOTHIDDENMENU, or SYS_DUMP !!!
jimzweb1 said:
When you run the device hard, is the phone getting hot? Do you have a big case on it? It sounds like the overheating sensor is kicking off the device. On my note 3, when running WiFi Tether Router app and it is downloading a big file say a movie. On 4g LTE at a download speed of 2MB+ the phone has gotten to hot and shut down. My solution is to take it out of the case when downloading.
Maybe plugging the charger into the device resets the overheating sensor?
Here is what I would do, here is a link to the Galaxy tool app http://forum.xda-developers.com/not.../app-one-click-hotspot-enabler-menus-t2816159 download and install. Now you test all the sensors, and check the logcats to see what happened at the black line. Your phone has record of it in the logcats, either in the IOTHIDDENMENU, or SYS_DUMP !!!
Click to expand...
Click to collapse
Not really sure how to test the temp sensor. It seems from that app that my phone was at about 29 deg Celsius.
MRBULLRED said:
Not really sure how to test the temp sensor. It seems from that app that my phone was at about 29 deg Celsius.
Click to expand...
Click to collapse
There is a free app in the Google play store called the "Cpu Temperature" it gives you CPU temp and Battery temp in C/F. You might install it and run the device hard up to 50-60% and see what your temp is.
Don't forget to scroll through those logcats to see what happened at the black line.
Also I noticed your Screen is using some Battery, what is the preset on display time? Mine is 2 minutes then shuts off, I know if you run the display constantly they get hot.
jimzweb1 said:
There is a free app in the Google play store called the "Cpu Temperature" it gives you CPU temp and Battery temp in C/F. You might install it and run the device hard up to 50-60% and see what your temp is.
Don't forget to scroll through those logcats to see what happened at the black line.
Also I noticed your Screen is using some Battery, what is the preset on display time? Mine is 2 minutes then shuts off, I know if you run the display constantly they get hot.
Click to expand...
Click to collapse
Mine is set to 1 minute. The cpu temperature seems to stay around 100°F most of the time. However, after a random shutdown I noticed the temp was 140°F while booting it up right after the shutdown. Also. I uprooted and went back to stock NC5 yesterday. Still had the same problem today.
MRBULLRED said:
Mine is set to 1 minute. The cpu temperature seems to stay around 100°F most of the time. However, after a random shutdown I noticed the temp was 140°F while booting it up right after the shutdown. Also. I uprooted and went back to stock NC5 yesterday. Still had the same problem today.
Click to expand...
Click to collapse
My CPU temp is about 115F with WiFi Tether Router running pretty much all day. My Battery temp is 86F. My device feels cool to the touch, except just under the camera flash where the CPU is. What is your Battery temp at 50-60% ? Maybe you have a short in your Battery that creates excessive temp at the half way discharge point? Do you have access to another Battery to swap out and see if that has any effect?
jimzweb1 said:
My CPU temp is about 115F with WiFi Tether Router running pretty much all day. My Battery temp is 86F. My device feels cool to the touch, except just under the camera flash where the CPU is. What is your Battery temp at 50-60% ? Maybe you have a short in your Battery that creates excessive temp at the half way discharge point? Do you have access to another Battery to swap out and see if that has any effect?
Click to expand...
Click to collapse
First of all thanks so much for all your help.
My device feels cool to the touch all the time. Running candy crush seems to make it run at about 120f. Still feels cool to the touch. It happened with the battery that came with the phone so I bought another one thinking that was the problem. Do I buy a third?
MRBULLRED said:
First of all thanks so much for all your help.
My device feels cool to the touch all the time. Running candy crush seems to make it run at about 120f. Still feels cool to the touch. It happened with the battery that came with the phone so I bought another one thinking that was the problem. Do I buy a third?
Click to expand...
Click to collapse
No, I think two is enough. Check out this video https://www.youtube.com/watch?v=fls4NIRJ1IQ maybe this is the fix.
If not here is Sprint.com's suggestion, here is the link http://support.sprint.com/support/a...expectedly/WTroubleshootingGuide_542_GKB59231
jimzweb1 said:
No, I think two is enough. Check out this video https://www.youtube.com/watch?v=fls4NIRJ1IQ maybe this is the fix.
If not here is Sprint.com's suggestion, here is the link http://support.sprint.com/support/a...expectedly/WTroubleshootingGuide_542_GKB59231
Click to expand...
Click to collapse
Do you think this looks normal?
MRBULLRED said:
Do you think this looks normal?
Click to expand...
Click to collapse
NO, anything with Kim Kardashian in it is not normal. Lol As for the device that temp seems a little high, right now I am running 114F CPU and the Battery is 84F. The deivce is running WiFi Tether Router, plus a half dozen other apps, and charging. Let me hunt up the specs on the average operating temp on your CPU.
Hey if you get a chance try this. Go to settings/device/call and uncheck " Turn off screen during calls" the screen will stay on during calls. But if it doesn't go black then its the proximity sensor. It may be defective or may not deactivating because of a case.