Related
Seems like a lot of people are facing problem waking up the phone resulting in getting black screen and nothing else.
I faced the same problem too that is why I decided to create a new thread specifically on this.
Let's share what caused our phone to go into coma based on our observations so that in time, the root of the problem can be traced.
Based on my observation, when my phone is left idle for some time, say 1-2hrs, it tends to become sluggish and setcpu will stuck at max or min value (Yes! sluggish even when stuck at max value!). Given long enough idle time, it will fail to wake up (e.g. every morning when i wake up after 7-8hrs of idle time).
I was using OpenDesire v4.0.10 and just changed to v4.0.15 to see if it still exist. I have setcpu set on 1075max 245min (ondemand) and 245max 245min (ondemand) when screen off. Also, using task manager.
Please share your observations and phone settings (ROM, versions, setcpu, task manager and others)
have you tried removing setcpu?
cgrec92 said:
have you tried removing setcpu?
Click to expand...
Click to collapse
Nope, but in OpenDesire thread, people without setcpu experienced the same thing. Do you have such problem?
I noticed using setcpu does make the phone sluggish. when uninstalled problem was solved.
Installed undervolt & got better batt life.
Sent from my HTC Desire using XDA App
Perhaps, a more tailored topic title will help all readers understand what you're talking about.
However, HAVS kernels is the only common factor and SetCPU is not the cause.
And, my two cents, I don't think this issue deserves a dedicated thread since is specific to a single kernel flavor.
shai.bosse said:
I noticed using setcpu does make the phone sluggish. when uninstalled problem was solved.
Installed undervolt & got better batt life.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
what is this undervolt you talking about? mind elaborating a little?
@ngel said:
Perhaps, a more tailored topic title will help all readers understand what you're talking about.
However, HAVS kernels is the only common factor and SetCPU is not the cause.
And, my two cents, I don't think this issue deserves a dedicated thread since is specific to a single kernel flavor.
Click to expand...
Click to collapse
I created a specific thread on this topic because there are many people out there experiencing this bug and there is no dedicate thread to discuss it. I assume you are not facing this problem because otherwise you would understand the pain and frustration of encountering this problem repeatedly
webber2109 said:
what is this undervolt you talking about? mind elaborating a little?
Click to expand...
Click to collapse
Undervolt is a kernel mod that you install and it lowers the cpu drain by setting it to use lower volt values on each cpu freq. This cause it to stay cooler too.
Look for it in this forum. [Kernel] undervolt
Sent from my HTC Desire using XDA App
I am suffering from this once per day on Defrost and OD so I suspect its kernal related. I am running the default HAVS kernel at the stock 998 frequency. I uninstalled SetCPU yesterday and had a lock this morning ( Defrost 4.1 ). The notification LED was flashing orange. So SetCPU is not causeing the problem. I have swapped over to SVS so I will report back on how that goes.
webber2109 said:
Nope, but in OpenDesire thread, people without setcpu experienced the same thing. Do you have such problem?
Click to expand...
Click to collapse
I use OpenDesire 4.0.10, then 4.0.15, then 4.0.16, each release for at least 3 days, and not for once have I encountered such "black death"....no setCPU of course.
Care to elaborate what apps you have there ?
webber2109 said:
I created a specific thread on this topic because there are many people out there experiencing this bug and there is no dedicate thread to discuss it. I assume you are not facing this problem because otherwise you would understand the pain and frustration of encountering this problem repeatedly
Click to expand...
Click to collapse
That issue is relative to OpenDesire and DeFroST ROMs only, and when they use a particular kernel version (HAVS) on selected CPUs, so I continue to think that it'll be eventually sorted out by the respective developers and/or Kali- and the kernel team; those guys do monitor the ROMs threads so they're already aware of the issue.
And yes, I suffered the issue twice, as I wrote more times in the DeFroST thread. "Pain" (panic?) and "frustration" sound a bit strange to me, when dealing with overclocked, custom, highly tweaked cooked ROMs. If a reboot scares you, head for a stock HTC ROM and you'll be fine.
I was worried I was the only one who had this. Thread title isn't that helpful for people seeking advice on it though. Get this after every reboot for about a minute until everything is back to normal.
Had the sluggish issue when using YouTube after about 20/30 mins, other than that I've had no lags.
Using 4.0.16
Sent from my HTC Desire
Double post
I got this on a svs kernal, so its not just restricted to havs. I had 1300 svs installed. With setcpu. Done the same with 1267 svs.
I've also had this issue on SVS kernels, was also having a series of hard resets last night - have rolled back to an earlier version of my favourite ROM flavour for now.
Never experienced anything like that...Although there are times that my Desire's performance would remind me of the bad old Diamond days,where patience was a virtue(well,not a virtue,but a money saving method!throwing your phone to the wall with your full strength after it frustrates you with being slow is known to be a costly process! ).Seems to be some apps running in the background...Maybe if your phone recovers after it without a reboot you can check if any apps use a larger than normal amount of ram.Other than that...Well,god is almighty and people experiencing epiphanies are known to work wonders through the ages!
And something completely off-topic(sorry about that).When using an undervolted rom/kernel you are not able to overclock to values as high as when using a normal-volted(is the word right?I dunno...) rom/kernel,right?I mean,what would happen if someone tried to overclock to 1382MHz(I know,I like the limits) using an undervolted kernel?And finally,how does this all apply to the hardware?Does UV affect the CPU's health like overclocking or something like that?
Thanks a lot!
I've had it on OpenDesire 4.0.10 and 4.0.15 a few times. Stopped happening when I stopped using profiles and defaulted back to to 998/ondemand.
Will try running it on 998/interactive for a while and see what happens.
No lockups after SetCPU to ondemand. OD 4.0.15.
Sent from my HTC Desire using XDA App
Separate thread IS useful, otherwise replies get lost in ROM threads where the focus is not specifically on this problem.
I too had this issue three times. DeFroST on all occasions, versions 3.x iirc. Never tried the HAVS kernels, just plain default what is shipped with the ROM (SVS @ 12xx Mhz?). Also SetCPU'd it, have not yet bothered to try and turn that off yet. SetCPU keeps it at 995 Mhz max, interactive governor, while switching to powersave while asleep.
Issue happened twice while browsing (possibly with Flash ads on the page by accident) and the power state switching (i.e. turn the device off quickly while running for train, afterwards reading for 2 minutes again, etc). Third time it happened while tethering my internet connection to my laptop.
Hth
I had this problem few times a day when I upgraded OD to .10 and the new ADW on the same day.
Then I restore back the old OD with old ADW, then no problem.
This is stock ROM.
Every time I flash bacon bits to overclock my phone I always noticed that my screen flickers when I turn off the phone's screen or press the button to wake up.
Sometimes it just gets stuck and it stats flickering like crazy and I can't unlock my phone because of it.
This only happens when I OC my phone. When I wipe the phone it works fine but no OC which is what I want.
Any way to fix this issue?
I don't use Bacon Bits, but I have experienced the flickering you speak of. It seems that happen when you go too far with the OC process. What happens if you were to lower your clockspeed a bit? Does it continue to happen for you?
dustrho said:
I don't use Bacon Bits, but I have experienced the flickering you speak of. It seems that happen when you go too far with the OC process. What happens if you were to lower your clockspeed a bit? Does it continue to happen for you?
Click to expand...
Click to collapse
Actually I OC my phone, but it's still set on 806MHz so even at lower clockspeed it still flickers. It's bugging the hell out of me.
EDIT:
Switched over to pershoot's kernel: http://forum.xda-developers.com/showthread.php?t=847672 I can now overclock to 1.5 gHz with no problems anywhere. Aweseome.
I have this same problem and am bumping this thread.
I'm running stock rom with bacon bits v 0.3 - and my screen flickers when turning off so much that it won't turn off fully and opens the lock screen. I have to just try and try repeatedly to get it to work.
Any suggestions?
captainreynolds said:
EDIT:
Switched over to pershoot's kernel: http://forum.xda-developers.com/showthread.php?t=847672 I can now overclock to 1.5 gHz with no problems anywhere. Aweseome.
I have this same problem and am bumping this thread.
I'm running stock rom with bacon bits v 0.3 - and my screen flickers when turning off so much that it won't turn off fully and opens the lock screen. I have to just try and try repeatedly to get it to work.
Any suggestions?
Click to expand...
Click to collapse
Yeah, I have flashed all the kernels even pershoot's and it still flickers. I'm using the original ROM that came with the phone not the original one posted on the forums. Maybe if I use the one posted on the forums that will work?
I have the stock rom as well - I first flashed baconbits kernel, but when that flickered, I flashed pershoots most recent kernel in recovery. No flickering anymore - sorry to say I don't know what's wrong. Try posting in the thread of the kernel you are currently running!
Sent from my T-Mobile G2 using XDA Premium App
captainreynolds said:
I have the stock rom as well - I first flashed baconbits kernel, but when that flickered, I flashed pershoots most recent kernel in recovery. No flickering anymore - sorry to say I don't know what's wrong. Try posting in the thread of the kernel you are currently running!
Sent from my T-Mobile G2 using XDA Premium App
Click to expand...
Click to collapse
Well you know what I flashed an older version of pershoot mayeb I should try the newer one. I'll let you know what happens...
I had trouble flashing it with ROM Manager. Clockworkmod it. Here's the link to pershoots blog with the latest update links: http://droidbasement.com/db-blog/
Good luck!
Sent from my T-Mobile G2 using XDA Premium App
Just tried it and nope... it's still doing it maybe it's just my phone.
Bring it up in this thread:
http://forum.xda-developers.com/showthread.php?t=847672&page=103
Pershoot is always monitoring it along with a bunch of other smart devs. Maybe they'll have a better idea - don't give up hope!
what app are you guys using to manage your OC?
if it's setCPU, set your scaling to Interactive on the main screen and in any profiles you're using.
also, if you are using any screen on/off animations, disable them (just to see, for troubleshooting purposes, if that might be the culprit)
pmcqueen said:
what app are you guys using to manage your OC?
if it's setCPU, set your scaling to Interactive on the main screen and in any profiles you're using.
also, if you are using any screen on/off animations, disable them (just to see, for troubleshooting purposes, if that might be the culprit)
Click to expand...
Click to collapse
Yeah, it's set on Interactive and so are the profiles. As for the screen on and off animation I believe that's in the CM7 RC1 ROM. I'm using the stock ROM so there's no option for that.
jjuice525 said:
Yeah, it's set on Interactive and so are the profiles. As for the screen on and off animation I believe that's in the CM7 RC1 ROM. I'm using the stock ROM so there's no option for that.
Click to expand...
Click to collapse
hehe, didn't even read what rom you were using. my bad.
kernels aside, it is very possible, as you mentioned earlier, that you guys got the chips in the stash that don't take to overclocking very well. even on a device like the G2/DZ that seems to take to higher clock speeds relatively easily, there are bound to be some that aren't as happy with the increased workload.
if I think of any other bright ideas, I'll let you know. I haven't played with baconbits a lot.
pmcqueen said:
hehe, didn't even read what rom you were using. my bad.
kernels aside, it is very possible, as you mentioned earlier, that you guys got the chips in the stash that don't take to overclocking very well. even on a device like the G2/DZ that seems to take to higher clock speeds relatively easily, there are bound to be some that aren't as happy with the increased workload.
if I think of any other bright ideas, I'll let you know. I haven't played with baconbits a lot.
Click to expand...
Click to collapse
Actually, after installing Pershoot's most recent kernel, I have no problems. Maybe I just got lucky here.
With stock 4.1 and franco r210 for jb,
When I use setCPU to set cpu frequency max 1600 min 350, it can apply this setting.
see attached picture 1
But after screen off and on, I open setCPU to see that the max frequency setting is restored to 1200MHz...
see attached picture 2
Is that Project Butter side effect ?
How can I keep max cpu frequence on 1600 after screen on from screen off ?
ilu73224 said:
With stock 4.1 and franco r210 for jb,
When I use setCPU to set cpu frequency max 1600 min 350, it can apply this setting.
see attached picture 1
But after screen off and on, I open setCPU to see that the max frequency setting is restored to 1200MHz...
see attached picture 2
Is that Project Butter side effect ?
How can I keep max cpu frequence on 1600 after screen on from screen off ?
Click to expand...
Click to collapse
Same F**KING THING HAPPENS TO ME with franco.kernel for JB... Very annoying problem.... Please someone help us with THIS!!! :crying::crying::crying::crying:
mcreokhan said:
Same F**KING THING HAPPENS TO ME with franco.kernel for JB... Very annoying problem.... Please someone help us with THIS!!! :crying::crying::crying::crying:
Click to expand...
Click to collapse
No need with the shouting. (I always highly recommend swearing however )
JB itself is still technically a preview, franco hasn't had much time since release for everything to be working 100%. I'd stick with stock JB if I were you if you wanted to use JB right now
OP should be asking this question in Franco's thread as well or at least read it to find out if its a common problem. Not everyone is going to spoon feed.
moe6 said:
No need with the shouting. (I always highly recommend swearing however )
JB itself is still technically a preview, franco hasn't had much time since release for everything to be working 100%. I'd stick with stock JB if I were you if you wanted to use JB right now
OP should be asking this question in Franco's thread as well or at least read it to find out if its a common problem. Not everyone is going to spoon feed.
Click to expand...
Click to collapse
I thought it is a bug of JB instead of the Franco.kernel.. thanks for the info anyway... And I did search and found only one result and that is this thread itself.. Thanks
Hi,
Take a look at this:
TunedFish said:
I flashed dev15, confirmed to frequencies did not reset after screen off, but after some benches, I decided to flash back to 210. Here's the strange part: NOW THE FREQUENCIES DO NOT RESET AFTER SCREEN OFF. As a matter of fact, when I flashed neck to 210, the frequency was set at 1600. Anyway, if someone wants to confirm this please report back.
Sent from my Galaxy Nexus using Tapatalk 2
Update: frequencies stick after screen off, but after reboot, it boots at 1600, headset volume resets to 0, hi performance audio resets to OFF, and gamma values reset to 0 (even though Franco app says otherwise).
Click to expand...
Click to collapse
jenicekk said:
I confirmed that. Flash imoseyon kernel and back to franco 210, frequencies do not reset afrer screen off. GREAT!
Click to expand...
Click to collapse
jnr21 said:
I can confirm that too! Now this is strange
Click to expand...
Click to collapse
And I just tested ... I also confirm.
In the meantime it may help...
viking37 said:
Hi,
Take a look at this:
And I just tested ... I also confirm.
In the meantime it may help...
Click to expand...
Click to collapse
Is it tested on a JellyBean? Because Fransisco Franco have created a Kernel only for JellyBean thats what we are talking about...
Yes for Jelly Bean, I'm not blind or idiot here.
Take the Imoseyon test kernel on his twitter (the "dev15"), flash, reboot then reflash Fransico's kernel.
And I personnaly tested, it works.
Sent from my HTC Sensation Z710e using xda premium
viking37 said:
Yes for Jelly Bean, I'm not blind or idiot here.
Take the Imoseyon test kernel on his twitter (the "dev15"), flash, reboot then reflash Fransico's kernel.
And I personnaly tested, it works.
Sent from my HTC Sensation Z710e using xda premium
Click to expand...
Click to collapse
Thank you very much for the info.
My N2 makes me crazy when it gets warm.
When it reaches about 36 celsius degrees it starts with frequency limit of 800MHz.
The second step is making 2 cores offline and at last my gadget becomes limited to 2 cores at a max. of 500MHz.
It becomes almost unusable for me when in car. I use two navis in multiwindow (Waze and Sygic) and AutoGuard recording in background with FullHD and in about 5 minutes it's restricted hardly.
I know it's for safety reasons but I think it's too strict.
Is there a possibility to raise the thresholds of these by a few degrees?
What kernels support this?
There is a nice app called Android Tuner which is able to set these tresholds but it is for Qualcomm CPU-s only...
Thanks for any answers in advance!
le_vente said:
My N2 makes me crazy when it gets warm.
When it reaches about 36 celsius degrees it starts with frequency limit of 800MHz.
The second step is making 2 cores offline and at last my gadget becomes limited to 2 cores at a max. of 500MHz.
It becomes almost unusable for me when in car. I use two navis in multiwindow (Waze and Sygic) and AutoGuard recording in background with FullHD and in about 5 minutes it's restricted hardly.
I know it's for safety reasons but I think it's too strict.
Is there a possibility to raise the thresholds of these by a few degrees?
What kernels support this?
There is a nice app called Android Tuner which is able to set these tresholds but it is for Qualcomm CPU-s only...
Thanks for any answers in advance!
Click to expand...
Click to collapse
You can change a value in a file under system, but it is not so safe..
Mate996 said:
You can change a value in a file under system, but it is not so safe..
Click to expand...
Click to collapse
Very helpful...
Sent from my GT-N7100 using XDA Premium 4 mobile app
Mate996 said:
You can change a value in a file under system, but it is not so safe..
Click to expand...
Click to collapse
Not exactly understand...
There must be a safe setting for it as with Perseus kernel the thresholds are higher, but not too much. I forgot to edit my question according my experiences with Perseus.
At least with Perseus I get a max of 1000MHz at most cases but it is not enough for me cause I use apps needing high resources.
Would You be so kind to write about the value to be changed in order to get higher thresholds?
If I understand you correctly. Then you could try trickster mod.
Or try saber kernel. I use this baked into the Jedi rom.
Sent from my GT-N7105 using xda app-developers app
3vo3d said:
If I understand you correctly. Then you could try trickster mod.
Or try saber kernel. I use this baked into the Jedi rom.
Sent from my GT-N7105 using xda app-developers app
Click to expand...
Click to collapse
Thank You for the advice!
Now I had some time so I'm on Saber kernel and just testing.
The testing is awesome till now: the phone is working more powerful with this kernel and doesn't get hot so soon. :good:
Oh, now there is something strange, the programs get FC-s...
The phone is on charger, I ran AutoGuard in the background in FullHD, Sygic and Waze in MultiWindow, VideoPlayer in popup with a FullHD video and SuperPlayer in popup with another FullHD video. It was extremely fine but after a few minutes the players collapsed and AutoGuard had an error. The system is stable anyway. It seems I have to restart phone now...
Edit: After restart I got an old problem back: Dropbox is unable to run again... I loved Perseus because of this, on Perseus this problem was away... I hope that I won't get the other issue back with my WiFi... And it seems, AutoGuard became stupid too... :crying:
I don't give up and keep on trying to make them ok.
But I can't find the thermal control feature in Trickster Mod Donation altough I have just a minute for it.
I am reading Trickster webpage to get ahead...
Question: Are You using Jedi ROM and have no thermal problems?
In that case I'm going to try that ROM, cause I'm on hunting for a ROM that works with no problems for me.
I tried some lately and till now Omega v18 was the best amongst them. I tried MIUI, ProBam, Hawkish in the last days and I get problems with all of them or had non-working applications and/or features which ones are essentials for me...
Edit: mmmmmmmm, as see there is no Jedi ROM for international N7100...
hey bro,
wow you seem to be a bit more advanced than me so maybe ive reached the limit of the advice i can give you.
However, if you inform me how to check for thermal problems i will surely do that and then report back.
the saber kernel to the best of my knowledge is underclocked so if you try to o/c it maybe that will prevent your fc's. I have read in the various threads, of which the community is very helpful, of some issues for heavy users due to the u/c.
Regarding the jedi rom i am a uk 7105 user and to the best of my knowledge i thought it would also work for international 7100 users?!?!
Here is the thread i use.
http://forum.xda-developers.com/showthread.php?t=1987634
reading the op of that thread it would appear you are correct. I do know they are working on version 18 so maybe that will work for you. fingers crossed.
3vo3d said:
hey bro,
wow you seem to be a bit more advanced than me so maybe ive reached the limit of the advice i can give you.
However, if you inform me how to check for thermal problems i will surely do that and then report back.
the saber kernel to the best of my knowledge is underclocked so if you try to o/c it maybe that will prevent your fc's. I have read in the various threads, of which the community is very helpful, of some issues for heavy users due to the u/c.
Regarding the jedi rom i am a uk 7105 user and to the best of my knowledge i thought it would also work for international 7100 users?!?!
Here is the thread i use.
http://forum.xda-developers.com/showthread.php?t=1987634
reading the op of that thread it would appear you are correct. I do know they are working on version 18 so maybe that will work for you. fingers crossed.
Click to expand...
Click to collapse
Thank You for Your effort!
I'll keep on investigating for a solution.
Unfortunately the real test was horrible with Saber kernel, when I tested it in car the temperature got high soon and the thersholds were low again.
But it's a good idea to try o/c thank You very much!
I'll try it tomorrow, now I have to go to play Cod4... :laugh:
And I found that TWRP is recommended for Saber and a few minutes untouching after the restart so I'll try again.
Have a nice day!
you too bro, sorry i couldnt help more.
but if you post in the saber kernel thread there are some helpful and intelligent folks in there that may have a better solution for you.
enjoy cod
3vo3d said:
you too bro, sorry i couldnt help more.
but if you post in the saber kernel thread there are some helpful and intelligent folks in there that may have a better solution for you.
enjoy cod
Click to expand...
Click to collapse
Thank You again!
I got some experiences with the newest Saber kernel and I like it 'cause the first kernel I can use 100MHz step with and using 300MHz step too.
It seemes to be good at battery consumption too. My only problem that this kernel doesn't support STweaks so I can't regulate charging voltages like I used to. Perhaps only Perseus kernel makes it possible as I can't get any other programs for it till now. Or NEAK kernel and the new versions of AGNi pureSTOCK kernel as I read their pages. I'll try them some day. But Perseus is my favourite.
I think it's important to say that the kernel isn't UC/OC by default so this doesn't make any problems and it's not UV-ed too.
I set min. to 100MHz and max. to 1920MHz to test and it's stable till now. I tried to Overvolt slightly and had no change on media programs behavior they don't like each other as I see.
Trickster Mod is nice 'cause it shows the CPU temperature which was helpful to understand this regulations of thermal control are needed.
When I tested it turned out that CPU is below 70 degrees while the battery temparuture is 'only' about 40 degrees.
So thanks for Your kind advises!
wow. Ok i think i understood most of your post. probably a little bit over my head but i need to learn.
I really like the new kernel im getting 1% battery drain an hour with the screen off which truly is unheard of for me,
The kernel runs real smooth apart from when i play asphalt 8. Or i should say it runs smooth playing the game until the phone tries to do something else. For example if it attempts to update a programme or if a message/email comes through. then the game just lags and i have to wait for the phone to stop multi tasking before the car starts to move normally again.
So im surprised to read you say the kernel isn't uc/uv by default??? I was pretty positive it was. But i dont know for sure and im probably not clever enough to figure it out lol.
I wonder what settings i would need to increase to aid the phone in its multi tasking? Also there must be some kind of programme we could use that would test our specific phone/cpu and tell us which settings it would prefer. As i believe each phone will run slightly different?
You are right i remember reading the kernel does not work with stweaks.
I wish i could work with you and figure out how to optimise our settings but i simply dont have the skill set.
I presume you used trickster to overvolt slightly?
3vo3d said:
wow. Ok i think i understood most of your post. probably a little bit over my head but i need to learn.
I really like the new kernel im getting 1% battery drain an hour with the screen off which truly is unheard of for me,
The kernel runs real smooth apart from when i play asphalt 8. Or i should say it runs smooth playing the game until the phone tries to do something else. For example if it attempts to update a programme or if a message/email comes through. then the game just lags and i have to wait for the phone to stop multi tasking before the car starts to move normally again.
So im surprised to read you say the kernel isn't uc/uv by default??? I was pretty positive it was. But i dont know for sure and im probably not clever enough to figure it out lol.
I wonder what settings i would need to increase to aid the phone in its multi tasking? Also there must be some kind of programme we could use that would test our specific phone/cpu and tell us which settings it would prefer. As i believe each phone will run slightly different?
You are right i remember reading the kernel does not work with stweaks.
I wish i could work with you and figure out how to optimise our settings but i simply dont have the skill set.
I presume you used trickster to overvolt slightly?
Click to expand...
Click to collapse
No, I didn't overvolt at last. But once I tried and didn't helped on my problems.
Unfortunately now I'm back on Perseus kernel again 'cause some issues with Saber. It became crazy every time and locked my CPU on 160MHz only and only reboot helped.
The other issue was the stuck system server process what was active all night and didn't stop hard work.
Now I'm on reading the kernel's page till I get cleverer on it... then I perhaps try it again 'cause I liked it.
http://forum.xda-developers.com/showthread.php?t=2260397&page=5
Hello, I think I have an issue with the kernel. I can't post in the development thread because I don't have 10 posts. Ok, so here's my problem, in the general section, on the frequency slider, the mhz is in read and reads (chrg override) so it would be max: 1512 (chrg override). What does it mean and what can I do to maybe stop it?
Thanks in advance
coollkidd said:
Hello, I think I have an issue with the kernel. I can't post in the development thread because I don't have 10 posts. Ok, so here's my problem, in the general section, on the frequency slider, the mhz is in read and reads (chrg override) so it would be max: 1512 (chrg override). What does it mean and what can I do to maybe stop it?
Thanks in advance
Click to expand...
Click to collapse
I had a similar problem but it said battery override i go rid of it by taking root from du battery saver app must be something similar an app not letting you be able to use that feature try uninstalling apps that have root access and reboot so that the changes happen
philliedbz said:
I had a similar problem but it said battery override i go rid of it by taking root from du battery saver app must be something similar an app not letting you be able to use that feature try uninstalling apps that have root access and reboot so that the changes happen
Click to expand...
Click to collapse
Thanks! I found an app was doing it.