or do I just suck?
I've been flashing NBs ICS roms since the initial release and have been nothing but impressed at the development and overall quality; however, there's one thing that seems amiss. Generally, it seems that whenever the option to OC exists (which I assume is due to the kernel but I have the foggiest on how these things work), my phone refuses to go into deep sleep. I've always written this off as something wonky with the specific build and whatever crap I install afterwards. After all, it's still in the beta.
After flashing Beta v10 -which does not have OC by default- my phone had no problem going into deep sleep after all my apps were restored. After spending the day enjoying my ICS goodness, I decided to flash the new custom kernel mostly because I'm a sheep and will do whatever the rom dev tells me to do.
My phone now won't drop below 100Mhz; this is with the kernel change being the ONLY difference. I assume that this must be culprit. Excuse the short monitor time on my screenshot, it was taken after a "trouble-shooting" reboot.
I use the included 'CPUMaster' app to set the clock settings and I've run the diagnosis app but don't understand anything it displays.
Has anyone else experienced this and what should my next troubleshooting step be?
NB set the Rom to not go into Deep sleep while being charged.
So, after charging your phone, and unplugging, you need to reboot your phone
before it will be able to go into deep sleep.
Hopefully this helps.
Deep sleep problems for me too, rebooting doesn't always solve
I got the same issue as the above guy. I'm on 10.6 with eugene373's streamline kernel. The rom is awesome, but this issue is a pain on my battery. I notice at least once a day my battery starts dropping rapidly. I check cpuspy and sure enough i'm stuck at 100 mhz. Rebooting only solves the problem about half the time and even when it does after a few hours sometimes i get stuck at 100 mhz again. This happens later in the day as well, after unplugging from charger and a reboot or two. What is going on? Any suggestions as to how to find the culprit would be much appreciated.
Xenoism said:
NB set the Rom to not go into Deep sleep while being charged.
So, after charging your phone, and unplugging, you need to reboot your phone
before it will be able to go into deep sleep.
Hopefully this helps.
Click to expand...
Click to collapse
Is this a compile time flag? Or something that can be turn on/off some other way?
InstigatorX said:
Is this a compile time flag? Or something that can be turn on/off some other way?
Click to expand...
Click to collapse
I'm curious about this too
---------- Post added at 01:16 AM ---------- Previous post was at 01:10 AM ----------
Xenoism said:
NB set the Rom to not go into Deep sleep while being charged.
So, after charging your phone, and unplugging, you need to reboot your phone
before it will be able to go into deep sleep.
Hopefully this helps.
Click to expand...
Click to collapse
I tried this and deep sleep still wasn't available.
Use BetterBatteryStats to track down what is preventing deep sleep. I ended up turning off background updates for everything except gmail to get reliable deep sleep. Turning on GPS also caused problems. Can't use GPS right now anyway, since flashing Kiss 4.1 kernal. I'd rather have 911 than GPS.
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.
Hi guys. While i was sleeping and my phone was just waiting on my desk, it magically went to %35 battery, and since this is clearly a failure to deep sleep, i've used betterbatterystats to diagnose the problem. It's probably not because of apps because i've been using these apps for a long time and i've uninstalled the short-term ones. Now as far as i know vbus is the usb part, might be a damaged port from bad charging, and nlpwakelock is googleservices? As you can see from processor times, its never on deep sleep but always on 300-600 mhz, something is not making it sleep and what im asking is for someone to make a connection between these (because i have no idea). Otherwise, ill just wipe it and see if my usb board is faulty.
Dakura said:
Hi guys. While i was sleeping and my phone was just waiting on my desk, it magically went to %35 battery, and since this is clearly a failure to deep sleep, i've used betterbatterystats to diagnose the problem. It's probably not because of apps because i've been using these apps for a long time and i've uninstalled the short-term ones. Now as far as i know vbus is the usb part, might be a damaged port from bad charging, and nlpwakelock is googleservices? As you can see from processor times, its never on deep sleep but always on 300-600 mhz, something is not making it sleep and what im asking is for someone to make a connection between these (because i have no idea). Otherwise, ill just wipe it and see if my usb board is faulty.
Click to expand...
Click to collapse
yes nlpwakeckocks is google service location, deactivate location of g+ and restart.
the phone was not charging?
Nope, it wasn't charging,i deliberately didn't charge it in order to see what the problem is. Ok, ill try.
Hmm, still couldn't test enough, even tho the battery life is better, i still think there is a problem with deep sleeping. Ill try updating to todays nightly for today.
If you are using a custom rom i suggest clean install instead of updating the nightly, it may keep the same problem.
Dakura said:
Hmm, still couldn't test enough, even tho the battery life is better, i still think there is a problem with deep sleeping. Ill try updating to todays nightly for today.
Click to expand...
Click to collapse
Try a diff 'Kernel' and see if it resolves ur issue
Sun90 said:
Try a diff 'Kernel' and see if it resolves ur issue
Click to expand...
Click to collapse
Different kernel and rom didn't work. But i remembered that i've used my friends charger (who has a S3) sometime before, that might did something to my board. Got no guarantee but i guess i need to find a repair shop..
After I press the power button to turn off the screen and leave it like that for a certain period of time (sometimes several hours, sometimes an hour), the screen won't turn back on and I'm forced to hold the power button to restart the device.
It started doing this half a year ago, I first thought that it was somehow caused by my ROM (Archidroid 3.1.4), but I flashed LineageOS 14.1 last night and the problem still persists.
It seems to happen most often while it's charging, and after rebooting it, the battery is never at 100% percent (despite being plugged in the entire time before the reboot), it usually sits at around 92% or lower than that.
On Archidroid, the battery menu showed that during the period of... it being frozen I guess, only WiFi is on, stuff like cellular data is labeled as not active and the phone never wakes up either. On LineageOS, the battery graph just shows the device during that time period as if it was turned off.
If there's any LED that's been flashing before the device "freezes", it sometimes stops flashing or is permanently on until I reboot the device. For whatever reason, enabling touch to wake and setting it to be permanently active makes the device function for longer before having to be rebooted. Also, at times, the phone works for a day or two perfectly before freezing again. Also, the phone is usually hot when I grab it and try to turn on the screen and see that I can't.
I'm starting to believe that it's a hardware failure, maybe something related to the screen?
The problem is custom roms/kernels in general. Even the stock roms suffer to some extent but not as bad and you can wake the phone up by covering the proximity sensor.
Beamed in by telepathy.
shivadow said:
The problem is custom roms/kernels in general. Even the stock roms suffer to some extent but not as bad and you can wake the phone up by covering the proximity sensor.
Beamed in by telepathy.
Click to expand...
Click to collapse
Hmm, how exactly does the ROM/Kernel cause this issue? I'm curious.
Also, where exactly is the proximity sensor and how do I cover it up? By hand or something?
Thanks.
I'd love to be able to tell you exactly why but I honestly don't know. All I know is I had the exact same issues with custom roms and kernels on my s3 but now it's stock rooted and only has that issue in phone calls.
The proximity sensor is 1 of the 2 dots between the earpiece and the front facing camera lens. Just cover them up for a few seconds with a fat finger or thumb and when you let go the screen "should" jump back into life. If it doesn't then you have to reboot the device.
I think you were halfway there with "hardware bug" but I think it's a "software interfacing with the hardware bug", not necessarily a hardware bug on its own.
Beamed in by telepathy.
shivadow said:
I'd love to be able to tell you exactly why but I honestly don't know. All I know is I had the exact same issues with custom roms and kernels on my s3 but now it's stock rooted and only has that issue in phone calls.
The proximity sensor is 1 of the 2 dots between the earpiece and the front facing camera lens. Just cover them up for a few seconds with a fat finger or thumb and when you let go the screen "should" jump back into life. If it doesn't then you have to reboot the device.
I think you were halfway there with "hardware bug" but I think it's a "software interfacing with the hardware bug", not necessarily a hardware bug on its own.
Beamed in by telepathy.
Click to expand...
Click to collapse
The problem started happening a few months after I flashed Archidroid, so I'm guessing something in the meantime managed to mess it up.
I tried covering the proximity sensor with my thumb, but it didn't work. It didn't even work while the phone was working normally. :/
Is the problem maybe caused by Kernel settings?
Have you changed the cpu clockspeeds?. The minimum the cpu can scale down to is 200mhz. If you haven't changed the cpu clockspeeds then the problem is the same one that I encountered that did my head in for months trying to find a fix, to no avail, so much that it put me off custom roms and kernels completely for any device.
The only "fix" is to use a stock rom/firmware and stop at rooting it, that's all. If you change to another custom rom or kernel all you'll do "is plaster over the cracks".
So your choice is put up with it or go back to stock.
Beamed in by telepathy.
shivadow said:
Have you changed the cpu clockspeeds?. The minimum the cpu can scale down to is 200mhz. If you haven't changed the cpu clockspeeds then the problem is the same one that I encountered that did my head in for months trying to find a fix, to no avail, so much that it put me off custom roms and kernels completely for any device.
The only "fix" is to use a stock rom/firmware and stop at rooting it, that's all. If you change to another custom rom or kernel all you'll do "is plaster over the cracks".
So your choice is put up with it or go back to stock.
Beamed in by telepathy.
Click to expand...
Click to collapse
I've messed with clockspeeds only AFTER I started experiencing the issue, I even tried setting the minimum clockspeed to 1000 MHz to make sure the Kernel doesn't somehow "sleep" because of the low CPU frequency, but it didn't help.
But if that's the case, then I guess I'll just put up with it. I'm way too used to Android 5.1.1 and 7.1 by now to make the change back to Android 4.3. Shame that nothing can be done to fix this though.
Thanks for your help, appreciate it.
No problem, it is definitely the issue I experienced with my s3 that I couldn't solve for months on end. It's not worth chasing shadows.
Underclocking will make the problem worse but eventually you'll get to a point where every single time the phone turns the screen off it'll immediately crash and you'll find it unresponsive, needing a reboot.
I remember conferring with a dev of a certain kernel to attempt to resolve the issue but even the dev was perplexed by it. That's why I say it's a halfy half hardware/software issue.
It's a shame though, the s3 is a good phone even by today's standards but due to the lack of ram it struggles with newer versions of Android. Anything past 4.3 has issues, probably because they're not stock.
Beamed in by telepathy.
shivadow said:
No problem, it is definitely the issue I experienced with my s3 that I couldn't solve for months on end. It's not worth chasing shadows.
Underclocking will make the problem worse but eventually you'll get to a point where every single time the phone turns the screen off it'll immediately crash and you'll find it unresponsive, needing a reboot.
I remember conferring with a dev of a certain kernel to attempt to resolve the issue but even the dev was perplexed by it. That's why I say it's a halfy half hardware/software issue.
It's a shame though, the s3 is a good phone even by today's standards but due to the lack of ram it struggles with newer versions of Android. Anything past 4.3 has issues, probably because they're not stock.
Beamed in by telepathy.
Click to expand...
Click to collapse
I personally never had many problems with 5.1.1 or 7.1.2 ROM's, the 7.1.2 ROM I flashed a few days ago actually made my phone faster.
Unfortunately, as of last night, my phone is officially dead. Left it to charge and when I came back, the screen had millions and millions of colors scattered on it, as if someone smashed it with a hammer. Rebooted, screen turned into this white and grey zig-zag pattern and the only way to shut it down is to remove the battery. Can't boot it into recovery or download mode and my computer does not recognize the phone when I plug it in using USB.
My S3 has served me well for the last 5 years, but I think it's time for me to put it to rest and look for a new phone. Again, thanks for your help, at least now I know that the issue I had was unfixable and now it doesn't even matter anymore
The device is now dead but it is not related. That is now hardware failure of the gpu.
If you're looking for an easily moddable device you should stick with Samsung but get an international variant of whatever model if available. If you want a nice phone that is cheap nowadays go for an htc m9. If you want an outright monster of a device take a look at the new htc's. Sense launcher is just awesome once you get used to it as it makes the phone too easy to navigate.
Beamed in by telepathy.