I have read a few people having the same issue but no solution. my light on my tilt 2 constantly stays lit orange. It dies overnight too i tried to set the alarm and overslept so that us why im looking for a solution. Thank in advance, again i never found a solution just others with the same issue so i apologize if this has already been solved.
P.s. gps is off and app killer is killing all apps that autostart.
Thanks in advance
MDavisiw said:
I have read a few people having the same issue but no solution. my light on my tilt 2 constantly stays lit orange. It dies overnight too i tried to set the alarm and overslept so that us why im looking for a solution. Thank in advance, again i never found a solution just others with the same issue so i apologize if this has already been solved.
P.s. gps is off and app killer is killing all aps that autostart.
Thanks in advance
Click to expand...
Click to collapse
Don't use any 'app killers'... It's probably constantly just killing apps that are relaunching, then killing that app that relaunched, then the app re-relaunches... You get the idea.
Also, FRX06 is no longer supported. Shouldn't have anything to do with the phone not sleeping, but if you want to pursue this further I'd like you to be on the newest build. Thanks.
I was under the assumption that froyo is the most stable build and that the latest doesn't support gps. If i misread will add the latest tonight.
How do i stop it from launching apps i dont want then? i have no need for news to keep popping up like it does, we have the same issue on my gfs android phone all this stuff she doesnt want loading always loads up.
MDavisiw said:
I was under the assumption that froyo is the most stable build and that the latest doesn't support gps. If i misread will add the latest tonight.
How do i stop it from launching apps i dont want then? i have no need for news to keep popping up like it does, we have the same issue on my gfs android phone all this stuff she doesnt want loading always loads up.
Click to expand...
Click to collapse
When he says FRX06 is old, that's because FRX07 is out, not because of Gingerbread, start over from scratch with FRX07, disable GPS, verify it sleeps properly (green light), then install apps slowly and make sure it sleeps after you install one, once it stop sleeping remove the last app you installed. Voila.
Thank you for clarifying that. I put FRx07 on just now shut off gps/wifi and the orange light by my ear speaker comtinues to stay lit, no apps are opening aside from "stock" apps those that were included with the os
MDavisiw said:
I have read a few people having the same issue but no solution. my light on my tilt 2 constantly stays lit orange. It dies overnight too i tried to set the alarm and overslept so that us why im looking for a solution. Thank in advance, again i never found a solution just others with the same issue so i apologize if this has already been solved.
P.s. gps is off and app killer is killing all apps that autostart.
Thanks in advance
Click to expand...
Click to collapse
well so you wont over sleep..keep the phone plugged in all night then you will hear your alarm...dont worry nothing will happen to your phone. i have done this many times...as for the orange light,i had this happen to me on frx06 but not on frx07..
MDavisiw said:
I have read a few people having the same issue but no solution. my light on my tilt 2 constantly stays lit orange. It dies overnight too i tried to set the alarm and overslept so that us why im looking for a solution. Thank in advance, again i never found a solution just others with the same issue so i apologize if this has already been solved.
P.s. gps is off and app killer is killing all apps that autostart.
Thanks in advance
Click to expand...
Click to collapse
Make sure BlueTooth is off in WinMo before launching XDAndroid. That was keeping my phone from sleeping initially.
Lol I learned my lesson that night, i still use winmo until I get this figured out. I love the ability to put this on my phone just hope I can figure out whats causing it. The battery drains to fast to consider using it full time for now though.
Thanks for the suggestion on the bt, It is off when switching over.
BTW I am on FRX 07 now as requested
Thanks in advance for any assistance
MDavisiw said:
Lol I learned my lesson that night, i still use winmo until I get this figured out. I love the ability to put this on my phone just hope I can figure out whats causing it. The battery drains to fast to consider using it full time for now though.
Thanks for the suggestion on the bt, It is off when switching over.
BTW I am on FRX 07 now as requested
Thanks in advance for any assistance
Click to expand...
Click to collapse
The only things to my knowledge that kill sleep (now) are:
BT being on in WinMo (put WinMo in airplane mode, soft reset and let WinMo boot back up in airplane mode, then hit HaRET.exe...)
GPS being enabled (disable thru Settings -> Location & Security) - this is an issue even when the GPS icon is not in the notification bar. Just trying GPS and having it enabled will cause sleep problems.
Stupid apps not working correctly. Not sure what we can really do about those long-term, but sometimes apps do not give up wakelocks correctly and prevent the phone from sleeping. I actually got the WeatherBug Pro app for free from the Amazon store one day, and used it for a little while... then realized it was killing sleep on my device and promptly removed it.
If there's anything else killing sleep, let me know - I'm not aware of anything else that could kill sleep assuming you're on FRX07.
Lots of stupid apps. Facebook, anything that does background autosync (like gmail, gcalendar, etc. - I turn off all the autosync options whenever I see them.)
highlandsun said:
Lots of stupid apps. Facebook, anything that does background autosync (like gmail, gcalendar, etc. - I turn off all the autosync options whenever I see them.)
Click to expand...
Click to collapse
This forum should have the "+1" or "Like" button
MDavisiw said:
Lol I learned my lesson that night, i still use winmo until I get this figured out. I love the ability to put this on my phone just hope I can figure out whats causing it. The battery drains to fast to consider using it full time for now though.
Thanks for the suggestion on the bt, It is off when switching over.
BTW I am on FRX 07 now as requested
Thanks in advance for any assistance
Click to expand...
Click to collapse
I too had major battery drain issues and it really seems to be down to certain components. I have a RHOD100 running FRX07
In particular, I tried rootfs 20110721 last night with a full battery at about 21:00 and i'd swear it would have been dead by 02:00. So I have gone back to rootfs-20110716-245f68a. I am using this with kernel 20110718_223029-package. My battery was 100% at 08:15 this morning so three hours later, it's now at 80% so I'm very happy with this.
C
Ok now im curious if I may have "misrepresented" the issue. So here goes..
The orange light that while in WINMO that indicates the phone is charging. That light is constantly on while I am using android. After having upgraded to the FRX07 I clicked the lock button and the light went green but again stayed lit. I guess the major issue here (to me) is that these lights are not shutting off at all. in winmo if I unplug the phone the orange light goes off, the green light stays lit only temporarily. Is this an issue that is common?
I still notice a faster drain on the battery then one might expect thought I dont know how to quantify it as I dont know how to tell what % the battery is at only have the graphic up in the menu bar.
Regarding the Kernels and all in the above post you have lost me, I dont know what is meant by running something under a different Kernel, are you saying you reverted back to FRX06 and the battery issue is fixed?
MDavisiw said:
Ok now im curious if I may have "misrepresented" the issue. So here goes..
The orange light that while in WINMO that indicates the phone is charging. That light is constantly on while I am using android. After having upgraded to the FRX07 I clicked the lock button and the light went green but again stayed lit. I guess the major issue here (to me) is that these lights are not shutting off at all. in winmo if I unplug the phone the orange light goes off, the green light stays lit only temporarily. Is this an issue that is common?
I still notice a faster drain on the battery then one might expect thought I dont know how to quantify it as I dont know how to tell what % the battery is at only have the graphic up in the menu bar.
Regarding the Kernels and all in the above post you have lost me, I dont know what is meant by running something under a different Kernel, are you saying you reverted back to FRX06 and the battery issue is fixed?
Click to expand...
Click to collapse
I don't see any issue here at all, whatsoever. Simply a misunderstanding on your part, probably because you haven't taken the time to read and research how this port works.
Orange = wake
Green = sleep
The LED should always be on while in Android, representing the above conditions. It's really that simple. When the phone is plugged in / charging in Android, it cannot sleep - so the orange LED will be on, representing the device is awake.
I'm not talking about when the phone is plugged in, that is expected as you say, but when I have it unplugged and am using it the light continues to stay on.
just like the other thread of mine you commented in (video playback) for what you feel is not appropriately educating myself before asking the question I did read up on this issue before asking same result no concrete answer. If I overlooked it due to either to broad of a search or to narrow then I apologize. I am not trying to offend anyone here but I feel like your being a bit harsh towards me for not knowing all the answers to the questions i am asking.
I apologize again as I may be misreading you or this is just how you come off but your posts have had somewhat of a negative tone at least to me when I read them ever since I asked a question in the rhobuntu thread.
MDavisiw said:
I'm not talking about when the phone is plugged in, that is expected as you say, but when I have it unplugged and am using it the light continues to stay on.
Click to expand...
Click to collapse
The light is always on in Android. Green light always on means it's sleeping properly. Don't compare it to WM, it is not programmed to operate the same way at the present time.
MDavisiw said:
I'm not talking about when the phone is plugged in, that is expected as you say, but when I have it unplugged and am using it the light continues to stay on.
just like the other thread of mine you commented in (video playback) for what you feel is not appropriately educating myself before asking the question I did read up on this issue before asking same result no concrete answer. If I overlooked it due to either to broad of a search or to narrow then I apologize. I am not trying to offend anyone here but I feel like your being a bit harsh towards me for not knowing all the answers to the questions i am asking.
I apologize again as I may be misreading you or this is just how you come off but your posts have had somewhat of a negative tone at least to me when I read them ever since I asked a question in the rhobuntu thread.
Click to expand...
Click to collapse
The only reason I'm being harsh is you're not getting something very simple.
LED is always on in Android. Always always always.
Orange = wake
Green = sleep
The LED will never be off in Android, and these are the only things that the LED currently represents in Android - sleep state. Nothing more, nothing less. As was stated above, don't compare the LED to WinMo - it's not even close to how that is programmed at this stage of the game.
If the light stay's orange, then that's Bad and means that the phone is not sleeping and so is likely to be the cause of the battery drain.
Can I suggest that you download "Battery Indicator" from the Market. It gives you a number in the top bar so easy to read the battery level at any time.
On your microSD Card, you will see three files - rootfs.img and the kernel files zImage and module.... try downloading and replacing these with updated versions. Rename the rootfs and zImage files but do NOT rename the module file. You can see the links in my earlier post.
C
championc said:
If the light stay's orange, then that's Bad and means that the phone is not sleeping and so is likely to be the cause of the battery drain.
Can I suggest that you download "Battery Indicator" from the Market. It gives you a number in the top bar so easy to read the battery level at any time.
On your microSD Card, you will see three files - rootfs.img and the kernel files zImage and module.... try downloading and replacing these with updated versions. Rename the rootfs and zImage files but do NOT rename the module file. You can see the links in my earlier post.
C
Click to expand...
Click to collapse
Sage advice.
See Incremental Updates if you want more info on updating individual pieces within the project.
MDavisiw said:
I have read a few people having the same issue but no solution. my light on my tilt 2 constantly stays lit orange.
Click to expand...
Click to collapse
Does your wifi work? I have the same problem and it seems it appeared along with a wifi problem on my frx7.
With a fresh install everything worked fine. after a couple of days (without modifying system) wifi was broken (gives an error if I try to turn it on) and the phone didn't sleep.
Related
So I got my x10 like 3 weeks ago, and I usually leave it to charge overnight, but the last 2 nights It had sufficient charge left so I kept it besides my bed, the first time it happened I didn't get up on time and was late for work cause my alarm couldn't go off cause my battery was dead! I remember clearly when I went to bed at 12:30 it was at 55 or so percent, and when I woke at 9 it was dead. (My alarm was set at 7:30 so it was dead before that). This was quite surprising to me as otherwise it runs fine throughout the day. The next day i kept it at 80% charge at 1 am and when I woke up at 7:30 it was at 66.so it did drain a lot but not as much. I had installed juiceplotter and according to that, there was some network usage around 2:30 to 3:15 or so (i'm guessing the yellow line indicates data usage?) and one thing I noticed was from 4:30 to 7:30 the SCREEN WAS ON! (Acc to the blue line). So I'm wondering what could be the cause of this rude awakening . I looked into the partial wake status and it showed facebook as the highest since boot. Could it be that? I'm using the latest facebook app. Also is there any app that can monitor the systems activity? Say what started when, for how long, how much cpu, screen on etc so I could determine that if it happens again.
I read about others having this problem. I'm sure what the conclusion to that thread was but for me my screen only comes on when I have a scheduled back up with backup and restore. It comes on and stays on until the back up is complete, unless of course I turn it off manually. I think this is also the case for Titanium Backup but don't quote me on that.
Well it could not be the backup app doing it because I don't have any backups scheduled... I dont have titanium backup installed too...
I have the same problem. Not so much a problem though as I charge the phone @ night anyway. What causes it however, I don't know. I don't have scheduled backups running. Come to think of it.. I only had this problem when I had a live wallpaper set (I think). Since a few days I'm running froyo 2.2 rom/static wallpaper and didn't have this problem so far. So perhaps it's (live)wallpaper related (which I seriously doubt), or ROM related. I was running Nordic ROM 2.1 before.
I've also noticed this. No apps running and randomly the screen comes on. Sorry I can't be of any help but it's not just you...
Well I do have a feeling that it could be the facebook app doing it, can't be certain though. I'm judging by the partial wake usage stats, well It could also be 'Android system' but I don't know what would be waking the phone up from sleep like this and leaving the screen on for hours!
Like I asked earlier, is there any app that can monitor all activity on android?Like apps starting at what time and ending etc, so I could use his in conjunction with juiceplotter to narrow down the culprit?
wow guys, not sure what this is. but i did a google search and heres what turned up.
http://androidforums.com/incredible-support-troubleshooting/141868-screen-randomly-turns.html
http://forum.androidcentral.com/motorola-droid-x/49298-screen-randomly-turns.html ; this ones interesting to say the least
x10 specific:
http://androidforums.com/sony-ericsson-xperia-x10/240479-screen-wont-time-out-comes-randomly.html
And I think this program might help you:
http://www.androlib.com/android.application.com-eolwral-osmonitor-xxxt.aspx
Mentioning what Android (1.6, 2.1) version you have and what model of x10(i,a) might help as well.
Hope that helps. Can anyone with this problem confirm if its just stock or also rooted and flashed devices?
i got no idea when it comes screen randomly turns on. but the facebook app might be the cause (im still guessing). because data traffic consume alot of your battery, considering retreive and send data too much. i have my data traffic turned off in case i want to go bed, and take it easy just turn on when you need to use internet
kindred7 said:
Mentioning what Android (1.6, 2.1) version you have and what model of x10(i,a) might help as well.
Hope that helps. Can anyone with this problem confirm if its just stock or also rooted and flashed devices?
Click to expand...
Click to collapse
Well went through those threads earlier, but they didn't seem very helpful.
I'm on android 2.1 btw on an x10i. Well I can safely say that it didn't happen last night so I'll check again tonight to see if it does, if not then its just a random occurrence
Hi all!
One thing drives me nuts about my wife tab - it turns screen on in the middle of the night, I guess when battery is completely charge.
Is there any way to disable or completely remove this behavior?
I use AutomateId to disable sounds, but there is nothing to turn off screen completely.
I checked few custom roms and do not see one fixing this problem. So, any suggestions will be appreciated!
Keep the tab switched off while charging
ansonantonym said:
Keep the tab switched off while charging
Click to expand...
Click to collapse
Uh, yeah. That'dprobably do it. ;-)
On a somewhat related note... Is there a danger of overcharging? It always says, "Device fully charged. Please unplug charger." Is it unreasonable to expect smart charge capability?
Sent from my GT-P7510 using xda premium
That is an option, unless you need it on for something else, like an alarm in the morning ;-)
However, sumsung phones developers let say, were able to work around in custom roms, so I was in hope, that may be I missed something...
JM_I said:
Uh, yeah. That'dprobably do it. ;-)
On a somewhat related note... Is there a danger of overcharging? It always says, "Device fully charged. Please unplug charger." Is it unreasonable to expect smart charge capability?
Sent from my GT-P7510 using xda premium
Click to expand...
Click to collapse
the message to unplug is purely an energy saving measure. It doesn't mean unplug from the tab, it means unplug from the wall to prevent "vampire power drain".
I agree about it being sodding annoying, though; the point of charging overnight is that it's fully charged come morning not fully charged at, say, 1am and partially drained by morning! /rant
chaosdefinesorder said:
the message to unplug is purely an energy saving measure. It doesn't mean unplug from the tab, it means unplug from the wall to prevent "vampire power drain".
I agree about it being sodding annoying, though; the point of charging overnight is that it's fully charged come morning not fully charged at, say, 1am and partially drained by morning! /rant
Click to expand...
Click to collapse
Ah, well... Aside from being somewhat econazi-ish, that makes sense. The "wake-up-on-full-charge" thing doesn't really annoy me too much because it's in the case almost all the time. Closed cover = no problems.
CNemo7539 said:
Hi all!
One thing drives me nuts about my wife tab - it turns screen on in the middle of the night, I guess when battery is completely charge.
Is there any way to disable or completely remove this behavior?
I use AutomateId to disable sounds, but there is nothing to turn off screen completely.
I checked few custom roms and do not see one fixing this problem. So, any suggestions will be appreciated!
Click to expand...
Click to collapse
Wow! I thought I was the only one. This drives me nuts! I just thought it was one of those random custom ROM bugs. I'd love a fix because then I could just set my setCPU profile to clock down when the screen is off, but since it comes on, I have to make more complicated settings (or else it overheats inside the case!).
I think I figured it out by a chance...
There setting "Never turn screen off when charging" or something like this. I do not have tab in front of me.
Removed that check and didn't see screen on this night.
If it help to anybody else please post here to confirm.
CNemo7539 said:
I think I figured it out by a chance...
There setting "Never turn screen off when charging" or something like this. I do not have tab in front of me.
Removed that check and didn't see screen on this night.
If it help to anybody else please post here to confirm.
Click to expand...
Click to collapse
If you figure out where the setting is will you update this thread? Also, update the OP to make it useful to others (including me!)
settings>applications>developments>stay awake, unmark the box, I hope your problem will end. I unmarked it as soon as I got my P7500 while checking settings and never experience this.
I have this option unchecked as well. I can confirm that the tablet turns on when it is completely charged and then goes back to sleep after a short while again.
Regards
Achim
Yeap, it does that. But like you said it shut the display in a short while, if it the option unchecked.
It's usually disabled in custom roms but if you have the skills and time try to make it yourself, although it's annoying that at 4am you hear the tablet buzzin' you that it's fully charged...
I had the same screen switching on over night problem with stock 3.1 ROM.
The tab switched on automatically, and never switched off.
It happened while it was charged and while was not charged, or after rebooted.
I work in front of the tab, and it switched on more and more often.
Once I set the screen off time to another, shorter value, it solved the problem for that afternoon, but in the morning the screen was on again.
Finally I removed 50 rarely used apps, and the problem is almost fixed. It happened only once since then. I think I permitted some app to administer the device in the menu, and those caused this.
sedward said:
I had the same screen switching on over night problem with stock 3.1 ROM.
The tab switched on automatically, and never switched off.
It happened while it was charged and while was not charged, or after rebooted.
I work in front of the tab, and it switched on more and more often.
Once I set the screen off time to another, shorter value, it solved the problem for that afternoon, but in the morning the screen was on again.
Finally I removed 50 rarely used apps, and the problem is almost fixed. It happened only once since then. I think I permitted some app to administer the device in the menu, and those caused this.
Click to expand...
Click to collapse
I think my screen problem is also related to the multimedia dock. When the tab is in the dock and the dock is NOT connected to the charger, then few times it switches on the screen after some time.
I put my tab into silent mode and close the cover.
No noise no light.
Alarm still makes noise even in silent.
But there really should be an option to turn this off.
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've had my phone for a few months now and up until recently it had no issues. It's unlocked but not s-off and I had been running cyanogenmod 10.1. When the 10.2 nightlies came out I began using them and until around 9/15 these worked great. I didn't suffer from the flickering or radio issues at all. Around that time I started noticing that my phone would occasionally shut off on its own. I thought that it was an overheating issue at first but as the problem worsened it became clear that it would happen cold. It's now at the point where it predictably happens within a minute of the phone being on, leaving the phone essentially useless. I've tried narrowing the CPU frequency range and going back to the stock ROM, neither of which has resolved the problem. Investigating logcat and bugreport didn't reveal any hints to me as to what was happening. I'm worried that it's a hardware issue but recovery and bootloader seem to be able to stay on indefinitely which gives me some hope. Does anybody have some input on additional things that I could try?
Start simple... Battery good? Battery contacts good?
j13smiley said:
Start simple... Battery good? Battery contacts good?
Click to expand...
Click to collapse
Yeah, I'm fairly sure that it's not a battery issue. The same thing happens when it's plugged into a charger and the phone will stay on in recovery regardless of me moving it around or letting it sit for long periods of time.
I have noticed something new though. If I don't enter my Google account information (doing so starts app syncing) then the phone is much more stable. It seems that I can do a simple task like turning on wireless tethering and then if I don't do anything else the phone will be stay on for hours. If I open the browser, the play store, or start moving icons around then I only have a minute or two before it will shutdown.
Removed
foobster said:
Yeah, I'm fairly sure that it's not a battery issue. The same thing happens when it's plugged into a charger and the phone will stay on in recovery regardless of me moving it around or letting it sit for long periods of time.
I have noticed something new though. If I don't enter my Google account information (doing so starts app syncing) then the phone is much more stable. It seems that I can do a simple task like turning on wireless tethering and then if I don't do anything else the phone will be stay on for hours. If I open the browser, the play store, or start moving icons around then I only have a minute or two before it will shutdown.
Click to expand...
Click to collapse
Updating to a newer 10.2 nightly might fix the problem. Otherwise get the last_kmsg file when it shuts down next time and post it here. Someone might be able to diagnose the problem.
durgis said:
Updating to a newer 10.2 nightly might fix the problem. Otherwise get the last_kmsg file when it shuts down next time and post it here. Someone might be able to diagnose the problem.
Click to expand...
Click to collapse
Thanks for the input. I'll give a newer 10.2 nightly a shot but I am seeing the issue on builds that had previously worked fine (stock and 10.1). I have no /proc/last_kmsg after an unplanned shutdown. Based on what I'm reading this might mean that it's locking up before there's a kernel panic?
two options
j13smiley said:
Start simple... Battery good? Battery contacts good?
Click to expand...
Click to collapse
Flexcard usb or your mainmotherboard is or going out
First off, I'm rooted and have already patched my Omate TrueSmart Developer Edition with Lokifish Marz's security patch.
Device: 1900 1/8 TrueSmart Dev Edition
ROM/Firmware version: Latest
Changes made to stock firmware (if any): A few Xposed mods
Issue: See below, freeze, drain, screen not functioning.
Steps Taken: Restart, antivirus check
One day I turned my TrueSmart on (while off my wrist), went back about 15 minutes later to it and the screen wouldn't turn on. I though "Ahh, that's strange. I thought I turned this on." I pressed the power button multiple times to try to turn it on. It was already on, but the display would not turn on. The battery was charged already and at about 85%. I held the power button and felt the haptic feedback - no screen on.
Earlier that week, I'd noticed that the TrueSmart's battery was draining a bit faster than usual on WiFi alone, no SIM or GPS on. When the screen wouldn't work, I held down the power button for about 10-16 seconds (some Android Devices will restart, but not all, so I gave that a shot). - Nothing. I then left it alone for a day (didn't feel like playing with it after a long and busy work day). I tried to turn on the screen - nothing. I still got haptic feedback so I knew it was on. "Crap - now I have to void the warranty by doing a battery pull." Removed the screws, found the crappy water seal, did a battery pull, and turned the device back on. Screen worked - phew. The past two days it had been draining rather fast and the watch was overheating even though I kept it in about room temperature conditions.
I thought something was up so I ran avast! Anti-virus (I'm not playing the Linux OS' don't need antivirus software game - so let's not go there.) and the definitions/database took over two minutes to update (usually just 15 seconds) on a strong WiFi connection - strange. I ran the scan - nothing showed up but the scan mysteriously kept going away and I had to restart the scan a few times. Finally it worked even though I had to turn my WiFi on the watch off.
My question is - am I being completely paranoid or has my watch been hacked? Fast battery drain, connection issues, screen not responding, overheating - those are signs of spying and wiretapping, am I wrong? For the time being I removed the battery so that way if I am being spied on or hacked, the watch can't be powered on.
I've had the watch for only a few weeks, never installed any strange apps - all legit stuff. Am I crazy :silly: or is this something to be worried about?
deedscreen said:
First off, I'm rooted and have already patched my Omate TrueSmart Developer Edition with Lokifish Marz's security patch.
One day I turned my TrueSmart on (while off my wrist), went back about 15 minutes later to it and the screen wouldn't turn on. I though "Ahh, that's strange. I thought I turned this on." I pressed the power button multiple times to try to turn it on. It was already on, but the display would not turn on. The battery was charged already and at about 85%. I held the power button and felt the haptic feedback - no screen on.
Earlier that week, I'd noticed that the TrueSmart's battery was draining a bit faster than usual on WiFi alone, no SIM or GPS on. When the screen wouldn't work, I held down the power button for about 10-16 seconds (some Android Devices will restart, but not all, so I gave that a shot). - Nothing. I then left it alone for a day (didn't feel like playing with it after a long and busy work day). I tried to turn on the screen - nothing. I still got haptic feedback so I knew it was on. "Crap - now I have to void the warranty by doing a battery pull." Removed the screws, found the crappy water seal, did a battery pull, and turned the device back on. Screen worked - phew. The past two days it had been draining rather fast and the watch was overheating even though I kept it in about room temperature conditions.
I thought something was up so I ran avast! Anti-virus (I'm not playing the Linux OS' don't need antivirus software game - so let's not go there.) and the definitions/database took over two minutes to update (usually just 15 seconds) on a strong WiFi connection - strange. I ran the scan - nothing showed up but the scan mysteriously kept going away and I had to restart the scan a few times. Finally it worked even though I had to turn my WiFi on the watch off.
My question is - am I being completely paranoid or has my watch been hacked? Fast battery drain, connection issues, screen not responding, overheating - those are signs of spying and wiretapping, am I wrong? For the time being I removed the battery so that way if I am being spied on or hacked, the watch can't be powered on.
I've had the watch for only a few weeks, never installed any strange apps - all legit stuff. Am I crazy :silly: or is this something to be worried about?
Click to expand...
Click to collapse
As long as the apps that you have installed are legit, you should be fine.
I guess my only concern would be...how long did you use the device before installing Loki's patch? Did you connect to any network prior? It's your BT on? Is it set correctly?
As far as the overheating and other issues...I had the same. When I went to the latest Operative 20140318v2, most of the issues fixed themselves. Now, the overheating happens only if I am on a call for more than 10min.
Battery issues have become almost not existent when I patched up. However, I did find that of you upgrade to SL PRO...the juice seems to run out quicker....
I would install a good battery app that monitors ALL processes and hardware using power. I was able to solve a few issues this way.
But, overall, I really don't think you're being watched.
Good luck....
Sent from my HTC One using Tapatalk
Well I already know you're crazy but...
Even with Ensec or Operative the firmware is still unstable. I randomly get greatly increased battery drain yet even when connected to WiFi with full packet logging nothing stands out as odd. The screen not waking up happens from time to time as well as soft locks are being caused by some apps. I suggest you install a system monitor app and see if a particular app is to blame. On one TS, G+ randomly sits there and updates the feed for hours without ever actually updating. One another, it's weather, then on yet another, no issues at all yet all three are on the same firmware and same patch version and option.
The probability that your TS is hacked is fairly low and I suggest looking at the more likely causes first.
Perfectly normal behavior of Android device
BTW - force (hard) restart on many Android device is vol up + power.
Vol down + power will take screen shot.
Of course, there's many Android devices so maybe that combo also works...
TS is half finished device and we are all lucky we have Loki here...
If we were depending on Omate that wouldn't be good...
I'm still waiting my October 2100 1/8 release and I'm quite sure I won't even open it...
I'll sell that and develop for something else...(don't like when someone treat me like idiot)
Sent from my C6903 using Tapatalk
funky0308 said:
I'll sell that and develop for something else...(don't like when someone treat me like idiot)
Click to expand...
Click to collapse
Hopefully another Android based smartwatch. Idea man has ideas.
Lokifish Marz said:
Hopefully another Android based smartwatch. Idea man has ideas.
Click to expand...
Click to collapse
Absolutely another smartwatch...
I was really patient with Omate but this is too much...
If I have to wait almost eight months for Xperia Z2 I would f***ed them off and that's device that will work fantastic from the box.
But to wait something eight months to have 30% finished device (in a hardware and software way) - naaah...I'm (probably) out...
That's too bad, I really liked that idea and specifications but, if anyone wants to be honest - it just don't worth all that "hype"...
To completely relay on XDA devs to fix tethering and paring, to patch their incapacities and mistakes...to found their company and then wait for them while they are selling watch (newer and better) for a months...
Way tooooo much for me...
Sorry guys for spamming thread
Sent from my C6903 using Tapatalk
@funky0308 - Totally hear you. Maybe the Neptune Pine (quite a bit larger but still) may be better when it's finally released. The TrueSmart is unstable in some ways.
Sent from my SGH-T999 using Tapatalk
deedscreen said:
@funky0308 - Totally hear you. Maybe the Neptune Pine (quite a bit larger but still) may be better when it's finally released. The TrueSmart is unstable in some ways.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Lokifish Marz said:
Well I already know you're crazy but...
Even with Ensec or Operative the firmware is still unstable...
Click to expand...
Click to collapse
Haha, we all are a bit crazy. Could make sense.
@mghtymse007 - I used it for a few days before the patch but I should do a factory reset and try to re-patch just to be extra safe.