So recently here I've been having an issue with my G2. After hitting the unlock button to wake the G2 up, the screen struggles to light up and sometimes it doesn't at all!
When this happens I have to hit the unlock button multiple times just to get the screen to wake itself up, is this happening to anyone else?
Thank god my 3rd G2 is on its way, I should have it tomorrow.
I'm having the same issue also. I think the issue is from setting the CPU down while the screen is off.
Could this be because we've got out G2 oc to 1.42ghz+?
Sent from my T-Mobile G2 using XDA App
My G2 is stock and has this problem.....
Sent from my T-Mobile G2 using XDA App
EdTeach1680 said:
My G2 is stock and has this problem.....
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Well that answers that question lol
Sent from my T-Mobile G2 using XDA App
also have this problem, i usually just open the keyboard.
My stock phone did this...I was under the impression it was some issue with the unlock button. Tmo sent a new one and my replacement hasn't had any issues.
Sent from my T-Mobile G2 using XDA App
This started happening to me when I ran that app that blinked the notification lights when you got a text/voicemail/whatever. (sorry, can't remember what it was called...) When I uninstalled it, it went back to working properly.
[edit - NoLED is the app that was causing it for me.]
Having this same problem, and its extremely frustrating. Sometimes it goes away for a few mins, but most of the time I have to keep pressing the power button till the screen stays on. For some reason, it registers almost every press of the power button as 2. As someone said in one of the above posts, it might have to do with setcpu's screen off profile, but turning that off doesn't solve it for me =(
Sent from my HTC Vision using XDA App
I have this same problem. I was wondering if it was maybe baconbits or setcpu. It never really happened before I got perma root and installed baconbits. Sometimes flipping out the keyboard doesnt even unlock the phone.
I don't know about stock. But this def happened with baconbits for me. I flashed the 2 different sense roms and whenever i applied the baconbits kernel for those roms i had the issues, once i flashed a different kernels I was fine again. So I'll have to pass on bb for now. I hope they can fix this issue because the setcpu settings were great with it.
It happened with my first stock G2. At first I just dealt with it, but then I checked out my wife's G2 (purchased together) and her's worked perfectly. I eventually decided to go though the hassle of getting a replacement from Wirelfy. The replacement's been working fine after perm root & OC.
Install ota and you won't have this problem.
[G2/HTC Vision]
Try removing the setcpu widget from your screen, it seems to have fixed it for me
This was happening to me too. If you have baconbits and setcpu installed, do not use the on demand governor. I changed mine to interactive and my problem went completely away. Conservative works fine as well. On demand was giving me problems though. Even before baconbits on demand was not working properly.
xeduran said:
This was happening to me too. If you have baconbits and setcpu installed, do not use the on demand governor. I changed mine to interactive and my problem went completely away. Conservative works fine as well. On demand was giving me problems though. Even before baconbits on demand was not working properly.
Click to expand...
Click to collapse
Going to give this a try. Do you happen to know what the difference between interactive and on demand are?
Phawkes said:
Going to give this a try. Do you happen to know what the difference between interactive and on demand are?
Click to expand...
Click to collapse
trying this too. The problem seemed to start when I overclocked the cpu. very annoying
Phawkes said:
Going to give this a try. Do you happen to know what the difference between interactive and on demand are?
Click to expand...
Click to collapse
Interactive ramps up to your max speed faster and ramps down from the max slower. So you basically get a little faster performance than ondemand, but at the cost of a little more battery usage. I do not think the battery usage is very significant though.
Related
Anyone else having issues with the phone shutting itself off at random intervals? It is happening on mine and I have to pull the battery in order to power it back on.
So far have rooted, installed su file browser, and system panel. Only other thing I have done is removed Amazon mp3.
Thanks in advanced, just want to know if I need to exchange my phone or not.
Sent from my SGH-T959 using XDA App
kopykatkiller said:
Anyone else having issues with the phone shutting itself off at random intervals? It is happening on mine and I have to pull the battery in order to power it back on.
So far have rooted, installed su file browser, and system panel. Only other thing I have done is removed Amazon mp3.
Thanks in advanced, just want to know if I need to exchange my phone or not.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
This happen to me yesterday 3 times after the phone's screen was off for more than 10 min
I uninstalled setcpu and it never happened again so far.
Ok maybe it is a setcpu setting that is defaulting wrong. Anyone with setcpu installed that is not experiencing this? If so, what are your settings?
Sent from my SGH-T959 using XDA App
i also had this happen to me w/ setcpu active, i have yet to have it happen w/o setcpu
Happened with setcpu to me to. Removed it no problem since.
Same as everyone else. W/ SetCPU it happens. W/o SetCPU it doesn't.
Just sent the dev a message to let him know of the situation. http://twitter.com/MINUS_Stl/status/18719463969
Are you guys changing the scaling governor? From early reports, the Galaxy S phones can't take ondemand, you have to stick it to conservative.
You can "simulate" ondemand by changing freq step in Advanced to 100%.
Ya know. I did actually change it to ondemand seeing as that's what I always used on my G1. Gonna reinstall and see how we do. Will definitely report back. Thanks.
UPDATE: 1 hour in on 'conservative' and all is good.
I probably have to put a warning or something for Galaxy S for ondemand. It's probably a kernel flaw for that.
For now, it looks like conservative is 100% stable, haven't had reports of crashes on it.
Yeah, I'd say conservative is it. Thanks, bro.
Yes, before the reply about the conservative setting I had messed with it and set to that. Wanted to verify before posting, but as stated that appears that is the key. Thanks guys.
Loving this phone by the way.
Sent from my SGH-T959 using XDA App
coolbho3000 said:
Are you guys changing the scaling governor? From early reports, the Galaxy S phones can't take ondemand, you have to stick it to conservative.
You can "simulate" ondemand by changing freq step in Advanced to 100%.
Click to expand...
Click to collapse
I had SetCPU set to Conservative since I installed it. Yesterday it randomly powered off 6 times. I found this post and deleted SetCPU and am currently using Overclock widget. So far I haven't had it power off.
Has anyone else had this issue while having it set to conservative?
Yes! I changed my charger and it hasn't happened ever since.
Sent from my SGH-T959 using XDA App
i have also noticed that if i set a profile so that the cpu has a max of 400mhz while screen is off it will crash on me randomly. i have to keep it at at least 800mhz. It has just started doing this.
also does anybody know if it is dangerous to run in performance mode at a constant 1000mhz? it makes my phone super fast(obviously) but sounds dangerous making it run at maximum power constantly while the screen is on.
I've never used or installed SetCPU and my phone was shutting down by itself as well and had to do the battery pull to get it back on. I found it to be the "Power saving mode" in the display setting. Ever since I turned it off it has not shut down.
I also experienced this once when I try to install setcpu on my vibrant running bionix-v 1.2. Uninstalled it and it never happend again. =)
Just use the stock kernel.
Sent from my SGH-T959 using XDA App
this used to happen to me all the time so I got a replacement from tmobile but it continued to happen. It finally stopped when i rooted and flashed my phone
This thread is quite old, and while I do appreciate the contributions, it was long ago when this was posted and was dealing with a very early version of the over-clocked kernel. Please let this thread die, so that current ones maintain priority.
Sent from my SGH-T959 using XDA App
at least you guys are getting something. My phone shuts down 1-3 times a day. it is whether its rooted or not, customized rom or not. It just like to go to deep sleep really bad. Hopefully I can exchange it. But i just get my gps fixed, i dont know if i will get a new one with crappy gps.
So i have been going crazy! I started with ACS Frozen 1.1.0 and it was suffering from the "not waking up" problem. I assumed it was the overclocking so i went through all the crap with playing with the volts and settings. Well i never got the problem to go away so i switched roms to 1.1.1 (I think) and i got the same thing! So i wend to Bonsai v4.1.1 then to Emerald envy. Now im on SRF 1.2 final. All do the same thing!! The phone will go to sleep and not wake up with out a battery pull. Some roms make it take longer than others but at the most i get like 5-6hours before the lock screen (on 1.1.0). On this 1.2final i am getting almost immediate shut down!!! Non of them work!! I thought because the 1.2 final was pretty much a stock kernel i would not have a problem... i was wrong. The phone other wise runs great! So should i go back to stock? any suggestions??
Does it start doing it right after you flash a rom? Or does happen after you've installed all your favorite apps?
Sent from my SPH-D700 using Tapatalk
Either stop using SetCPU's ondemand setting and switch it to conservative, or just don't use the application at all.
The minimum for your phone seems to be higher than 100mhz, so adjust accordingly. Just remember, the ondemand setting doesn't maintain the minimum you set, so that's why you have to use conservative.
Or switch kernels and that might do it for you as well. Genocide kernel is a popular choice, but even that dev suggests using conservative, not ondemand, even though it does maintain the minimum when you set it on his newest kernel.
Hope that made sense.
I dont know if it happens before or after.. i always set it up... ill try flashing it now and not setting anything up. But if i cant use my apps then what the point?
I stooped over clocking it about 4 flashes ago. The last few times i did not even let voltage control get root access to see if that was the problem and is still freeze's! Also i read up and tried every configuration i could for overclocking before giving up on it.
Maybe its my apps? Or awd launcher? But that seems doubtful to me.
Anybody point me in the direction for returning it back to complete stock? If running it for some time with non of my apps does not work then i am going back to stock.
This will get you back to stock.
http://forum.xda-developers.com/showthread.php?t=1052813
I would try flashing a rom again without apps then as things look good start installing stuff. For me there was a battery widget that would lock up my nook color and on my Epic I had music stutters.
Sent from my SPH-D700 using Tapatalk
I flashed the 1.2final rom and have been adding 1 app every 4 hours. I have not has any freezing. Hard to believe a app would crash my phone... I will let you guys know what app ends up crashing it.
But now that I know its a app I will try over clocking again... and recommendations for a kernel for this frozen 1.2final rom?
Sent from my SPH-D700 using XDA App
Using setcpu?
Sent from my Epic 4G via Tapatalk
Some phones can't handle certain clock speeds. Sounds like your CPU may be biting the dust, or just got the bad end of the silicon.
Sent from my SPH-D700 using XDA Premium App
Well the phone has worked all night! I loaded youmail and that seems to be what crashed it. But now i am thinking it was not a app at all... it was my backup. When it crashed after loading youmail i reinstalled the rom and just loaded app.. I did not use Mybackup pro to load my data. The phone seems fine as of right now. I have not overclocked it once yet. I hope it was my backed up data because at this point i just want a phone that does not need to be reloaded every few hours.
hayzooos said:
Either stop using SetCPU's ondemand setting and switch it to conservative, or just don't use the application at all.
The minimum for your phone seems to be higher than 100mhz, so adjust accordingly. Just remember, the ondemand setting doesn't maintain the minimum you set, so that's why you have to use conservative.
Or switch kernels and that might do it for you as well. Genocide kernel is a popular choice, but even that dev suggests using conservative, not ondemand, even though it does maintain the minimum when you set it on his newest kernel.
Hope that made sense.
Click to expand...
Click to collapse
NissanNick said:
Well the phone has worked all night! I loaded youmail and that seems to be what crashed it. But now i am thinking it was not a app at all... it was my backup. When it crashed after loading youmail i reinstalled the rom and just loaded app.. I did not use Mybackup pro to load my data. The phone seems fine as of right now. I have not overclocked it once yet. I hope it was my backed up data because at this point i just want a phone that does not need to be reloaded every few hours.
Click to expand...
Click to collapse
I wasn't saying don't use any apps, I was saying not to use SetCPU with ondemand. Maybe it was youmail, maybe you just had some corrupt data. Who really knows.
Google doesn't go through the verification/testing process like Apple does, so you'll get some rogue apps out there that just plain suck, and can cause issues with your phone. Maybe that was the case.
Either way, it sounds like you got it pretty much figured out. If I ever restore a backup (not a nandroid), I usually only put data back to games, not any other apps, as there's no real need. Maybe for an email app to keep the settings, but even that's not hard to set back up.
Hello everyone...
I have 2 issues with my Transformer
the first one is that whenever i leave my Transformer for couple hours it shuts down !! doesn't occur when charging but it does when it's not.. even when the battery is around 80% !! i had this problem with ALL kernels except the stock kernel which i don't wanna use !! also had this problem for around 2 months...
the second one happened today when i left my Transformer "Charged" at 100%.. and after couple of hours i found it shut down but when i powered it on again i found the battery 27% !!
i went to the battery stats and found that battery was decreasing slowly and there was a gap (which means that it turned off) and after the gap it shows the battery low !! it happened within 6 hours !!
Please help me if you can... !! I'm using Revolver ROM 3.9.5 and "Blades Kernel 3" that comes in the Revolver Parts...
UPDATE : The problem occurs with the stock kernel !!
This sounds very familiar to the problem I had with my Galaxy S2 a month ago.
It kept shutting down every few hours, and it was driving me mad. Then one day I uninstalled the app greenpower, and it was fine afterwards. You don't have the greenpower app by any chance? If not, maybe it can be caused by some other app you normally use?
The battery might be hosed. Have you ever let it hit 0 before? A lot of batteries never fully recover after being fully depleted once or twice.
Cernunnoz said:
This sounds very familiar to the problem I had with my Galaxy S2 a month ago.
It kept shutting down every few hours, and it was driving me mad. Then one day I uninstalled the app greenpower, and it was fine afterwards. You don't have the greenpower app by any chance? If not, maybe it can be caused by some other app you normally use?
Click to expand...
Click to collapse
I never heard of this app... Just like i said it doesn't happen with the stock kernel !!
But the reason I'm using other kernels is because i wanna Overclock !!
a.mcdear said:
The battery might be hosed. Have you ever let it hit 0 before? A lot of batteries never fully recover after being fully depleted once or twice.
Click to expand...
Click to collapse
No i never let it hit 0%... but i don't think that the problem is in the battery
However I'll try it and see what happens !
sounds like a silly question but i have seen it alot. Are you charging through a computer(USB) or wall?
It could be related to setCPU and the according profiles. Just recently I saw that my profiles were messed up after updating ROM and kernel. Might be worth a shot.
Reinstall stock kernel Issue #1 fixed.
Issue 2 sounds like charger shut off and left TF on not charging.
You've pretty much explained to yourself why the thing is shutting down.. It works fine on the stock kernel but not one that is letting you overclock.. Sounds to me like you are either overclocking more than it can handle or undervolting to much or both.
I can almost bet that its not shutting down completely and its just going into a state that the screen is off but the OS is hung up, so its not responding to you turning the screen on.. This would explain why the battery seems to be dieing when its sitting idle.
Not sure about it dieing while its plugged in other than maybe a fluke.
I don't wanna use the stock kernel.. it's really slow !!
and i over clock to 1.4 ghz only since i can't overclock more than that because it restarts itself endlessly if i overclocked more than 1.4 ghz !! i undervolted about -25 or -50.. not much !!
Yes i charge it on a wall or anything but NOT on my computer...
How can i change profiles in setcpu ??
xMini said:
No i never let it hit 0%... but i don't think that the problem is in the battery
However I'll try it and see what happens !
Click to expand...
Click to collapse
No no you misunderstood! DONT let the battery hit 0.
First, you need to use more exclamation points !!!!
sounds like you are suffering from deep sleep issues. What rom are you running? also, have you tried running a custom kernel and not overclock it? You have several variables that can be influencing your issues, start isolating what may be causing your problems. the kernel seems the must likely of culprits, I would clear the overclock and install setcpu and run it for a but and see if you can replicate your issue.
Sent from my GT-I9000 using XDA App
Just try the non stock kernel, oc it but dont uv it, not all devices can handle uv, even if it is only a little bit. Even take it back too 1000mhz and try to increase the uv and oc by little bits at a time to see exactly what your transformer can handle. I think its the uv thats causing the problems. Experiment a bit and youll find the sweet spot.
I'm using Revolver ROM and i mentioned that...
I've never undervolted till yestersay.. maybe it caused the second problem
I set the clock speed at 1ghz and i'm waiting to see if anything changes..
Yeah... the problem still occurs even after setting the clock speed at 1ghz and default voltage !! using clemsyn kernel ver 22...
Every device is different. Differences in manufacturing etc. You might have a picky device. Plus these are mobile platforms. No fans, just convection cooling. They are not meant to be tweaked and oc'ed they way we do. The stock kernel is very fast. What is it that you cannot do on the stock kernel that the extreme oc let's you do?
Sent from my DROID X2 using Tapatalk
colonel187 said:
Every device is different. Differences in manufacturing etc. You might have a picky device. Plus these are mobile platforms. No fans, just convection cooling. They are not meant to be tweaked and oc'ed they way we do. The stock kernel is very fast. What is it that you cannot do on the stock kernel that the extreme oc let's you do?
Sent from my DROID X2 using Tapatalk
Click to expand...
Click to collapse
I'm guessing my device is bad and it's Asus' problem ! i tried setting the clock speed at normal 1Ghz but the problem still occurs !! the reason i overclock is that because with the stock kernel i get slower web browsing and slower flash playback and slower overall performance!! however I'm back on the stock kernel to check out if the problem is gone or not...
I doubted my device couple months ago... because I've seen everyone overclock their devices at 1.6 GHz Without any issues !! but when i try to overclock a little bit more than 1.4 GHz it restarts itself endlessly !!
Had the same issue a few months ago. Be prepared to wake up to a dead TF.
I sent it back to ASUS and they replaced main board and battery. Under warranty of course. I suggest you unroot and use a stock rom for now.
Sent from my GT-I9100 using XDA App
ropaisoft said:
Had the same issue a few months ago. Be prepared to wake up to a dead TF.
I sent it back to ASUS and they replaced main board and battery. Under warranty of course. I suggest you unroot and use a stock rom for now.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
What do you exactly mean by "for now" ??
and how can i even send it to ASUS ??! i don't live in the USA
xMini said:
I'm guessing my device is bad and it's Asus' problem !!!
Click to expand...
Click to collapse
You stated in an earlier post that the problem does not show up in the stock ASUS setup, but only with a custom ROM and Kernel. How does that make it ASUS' problem. If you buy a car that says it runs on 87 octane fuel and you put 100% nitro methane in the tank and it blows up it is not the manufacturers fault.
Hi!
I'm experiencing random turn-offs when I put my note to sleep. When it turns off I need to hold the power button for 10 seconds or so to turn it on - which means it's not just turned off but in the deep sleep state but unresponsive. I'm on Cassie's 2.0 ROM (flashed it twice suspecting a bad flash). Tried FM Kernel 1.3 , Abyss Kernel 1.4 and now FM Kernel 1.3.1 and it's still the same. It seems to happen more often when overclocking/undervolting but still happens sometimes on stock voltages too. Anybody else having similar problem?
yes and am on stock exact same issue
Sent from my GT-N7000 using xda premium
Never happened to me yet and I've had my note for 3 weeks.
Sent from my GT-N7000 using xda premium
Same issue on German stock, i even have to pull the battery out for it to restart, just did a master reset, and i hope that will resolve the issue.
are you guys using SetCPU & have a screen off profile? if so, then that's the case. I experienced this & had to delete the profile.
I've been having the same issues for about a week. Phone shuts down when in sleep for some reason. I thought I had a defective unit. I I'm in process for a replacement
Sent from my GT-N7000 using xda premium
Had this happen once but my phone has the Abyss 1.4 kernel with lowered voltages (no profiles).
RMXO said:
are you guys using SetCPU & have a screen off profile? if so, then that's the case. I experienced this & had to delete the profile.
Click to expand...
Click to collapse
Nope, I'm using SetCPU but never had any profiles set. Same happened when I used Voltage Control (or something...) instead of SetCPU.
It's too early to say it for sure but it seems that this thing happens to me only when I've got the WiFi on. I'll keep on checking.
pjm77 said:
Nope, I'm using SetCPU but never had any profiles set. Same happened when I used Voltage Control (or something...) instead of SetCPU.
It's too early to say it for sure but it seems that this thing happens to me only when I've got the WiFi on. I'll keep on checking.
Click to expand...
Click to collapse
ok, I had the screen off profile & when removing it, my issue went away.
Galaxy Note 2 shuts down by itself
This happens to the Note 2 as well and is not software related. The problem is hardware related. The phone is flawed and shuts off on it's own under various conditions, all hardware related. Take a look at this video: http://www.youtube.com/watch?v=SjLn2yikYnI
Also, take a look at this site I built that goes in to more detail regarding the issue: www.GalaxyNote2ShutsOff.com
One look at that short video and I am sure there will be some light bulbs going off. Be sure to read the details I provided on that site as well. They go in to detail about the problems that I have had and the lack of proper support that Samsung is willing to provide.
Apologies if this is covered elsewhere, but I have been struggling to trawl through all 1000 pages on the relevant thread as I can't get the search terms to get the info!
Basically, when I leave the phone overnight charging, in the morning I cannot turn it on unless I press and hold the power button and volume down to reset the device.
Other than this it is great in terms of being able to adjust the colours and the battery life seems better.
I have tried both the nightly and stable versions..
What ROM are you using?
Sent from my Nexus 4 using xda premium
murtezahu said:
What ROM are you using?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I am currently using the stock ROM but could change to a custom... (I am learning as I go at the moment...)
Sounds like your phone is having trouble to wake after a deep sleep. I'm guessing it's caused by a (probably: too) low cpu frequency.
Did you use any app to change the cpu frequencies while asleep, or did you undervolt your cpu?
Also, which version of the kernel are you using? I suggest you stick to M1 for more stable results.
And after all, it might be a bug in the kernel. The people in franco's thread are more than willing to help you if you supply as much information as you possibly can. Kernel version, your adjustments to it if any, etc. I haven't seen this problem happen to anyone before in the last days (oh yea, I read every page of that thread...), so don't be afraid to ask for some help. But for now, I suggest you update to M1. If you're already on M1, feel free to ask your question in the thread.
LOL
Sent from my Nexus 4 using xda premium
sounds like a classical case of sod. do you undervolt?
and rolmply
simms22 said:
sounds like a classical case of sod. do you undervolt?
Click to expand...
Click to collapse
No, I do not undervolt. The only changes I made were to gamma settings. Having said that I did change the power setting but changed it back. I have rebooted the phone so I will see if it happens after the next deep sleep.
Thanks for the help so far, much appreciated!
vindikleuk said:
Sounds like your phone is having trouble to wake after a deep sleep. I'm guessing it's caused by a (probably: too) low cpu frequency.
Did you use any app to change the cpu frequencies while asleep, or did you undervolt your cpu?
Also, which version of the kernel are you using? I suggest you stick to M1 for more stable results.
And after all, it might be a bug in the kernel. The people in franco's thread are more than willing to help you if you supply as much information as you possibly can. Kernel version, your adjustments to it if any, etc. I haven't seen this problem happen to anyone before in the last days (oh yea, I read every page of that thread...), so don't be afraid to ask for some help. But for now, I suggest you update to M1. If you're already on M1, feel free to ask your question in the thread.
Click to expand...
Click to collapse
Thanks for the reply.
I am currently using milestone 1.
As far as I am aware I only made changes to the colour as I am still learning the controls as I go. I have restarted the phone to see if it helps.
The only app that I am using that could be to blame is battery guru, so if it persists, I could try disabling that.
goldeneye243 said:
No, I do not undervolt. The only changes I made were to gamma settings. Having said that I did change the power setting but changed it back. I have rebooted the phone so I will see if it happens after the next deep sleep.
Thanks for the help so far, much appreciated!
Click to expand...
Click to collapse
do you use the pgm slide to wake app?
simms22 said:
do you use the pgm slide to wake app?
Click to expand...
Click to collapse
No, I don't - Should I, or is it possibly what is could have caused the problem?
goldeneye243 said:
No, I don't - Should I, or is it possibly what is could have caused the problem?
Click to expand...
Click to collapse
its a possible cause of sod if you had it installed.
goldeneye243 said:
Thanks for the reply.
I am currently using milestone 1.
As far as I am aware I only made changes to the colour as I am still learning the controls as I go. I have restarted the phone to see if it helps.
The only app that I am using that could be to blame is battery guru, so if it persists, I could try disabling that.
Click to expand...
Click to collapse
You're using the exact same set-up I am, and I'm haven't had any of the trouble you talk of. Disabling battery guru might be a good idea. As it's an app from Qualcomm itself, I wouldn't be surprised if it's set to mess around with the stock kernel's settings. If that's the case, then your kernel is obviously not the kernel that Battery Guru was programmed to mess with! Uninstalling it to see what happens next would be a good step :highfive:. From my experience, you wouldn't need any battery management apps when you're on franco's M1 anyway - using common sense to save your battery should suffice.
vindikleuk said:
You're using the exact same set-up I am, and I'm haven't had any of the trouble you talk of. Disabling battery guru might be a good idea. As it's an app from Qualcomm itself, I wouldn't be surprised if it's set to mess around with the stock kernel's settings. If that's the case, then your kernel is obviously not the kernel that Battery Guru was programmed to mess with! Uninstalling it to see what happens next would be a good step :highfive:.
Click to expand...
Click to collapse
I will do that if I have not already got it fixed with the reboot. Battery guru is still in learning mode so possibly isn't messing with the kernel yet but is the next thing to try...
Alrighty, let's hope it'll get figured out.
vindikleuk said:
Alrighty, let's hope it'll get figured out.
Click to expand...
Click to collapse
Well, it turned on OK this morning, so hopefully fixed...
I guess I will only know in a few days time when I have got more confidence...
I had another SOD so I have reset all settings (installed nightly version 110) and started again -
The only changes I have made are to the gamma settings and changing the governer to conservative to see if that gives me a longer battery life.
Will see how it goes....
I had some more SODs with 110/111 so I changed to 121 and the battery life did not seem as good.
Takes a while to work out what is going on when it only happens once a day...
I still get occasional SODs with battery guru disabled so i guess it is either the kernel or possibly the ROM... I will try on the support thread....