Hi
I was wondering why this was happening and what exactly is happening? I'm a noob at this flashing roms and kernel and duno why this would happen or what is it called?
See that major drop?. MY phone randomly reset for no reason and went from 9x% to 7x%?
Why?
Sent from my Nexus 4 using XDA Premium 4 mobile app
sai.nissankula said:
Hi
I was wondering why this was happening and what exactly is happening? I'm a noob at this flashing roms and kernel and duno why this would happen or what is it called?
See that major drop?. MY phone randomly reset for no reason and went from 9x% to 7x%?
Why?
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This could be because a lot of things, you should provide a little more information about what you did to flash ROM or kernel, and would be nice some details about what you were doing when this happened.
Sometimes it is kernel related or because too much undervolting.
:good:
battery drain
I am currently using Paranoid Android 3.99.
I flashed franco 1.74.
I underclocked my cpu to 1000mghz
And i undervolted 75volts across all frequencies.
I wasnt doing anything processor intensive. I was locked my phone and tried unlcoking it and then it rebooted and drastically dropped my battery %. Since you told me it might be voltage issues i put the voltages back to previous stock voltage see what that does for me.
But do you have any suggestions on voltages to optimize battery life?
I just followed what I saw someone else said on a different post.
Galaxo60 said:
This could be because a lot of things, you should provide a little more information about what you did to flash ROM or kernel, and would be nice some details about what you were doing when this happened.
Sometimes it is kernel related or because too much undervolting.
:good:
Click to expand...
Click to collapse
sai.nissankula said:
I am currently using Paranoid Android 3.99.
I flashed franco 1.74.
I underclocked my cpu to 1000mghz
And i undervolted 75volts across all frequencies.
I wasnt doing anything processor intensive. I was locked my phone and tried unlcoking it and then it rebooted and drastically dropped my battery %. Since you told me it might be voltage issues i put the voltages back to previous stock voltage see what that does for me.
But do you have any suggestions on voltages to optimize battery life?
I just followed what I saw someone else said on a different post.
Click to expand...
Click to collapse
Well, it looks like and UV problem. Most of the UV related problems are easily identified because it seems that phone goes into deep sleep and then it cannot wake back, so the reboot happens. When you say that you locked phone and then tried to unlocked and rebooted, is clearly a symptom of this.
I would adivce that you first know which type of processor you have, there are 4 types I think:
http://forum.xda-developers.com/showthread.php?t=2052496
It depends so much in which type you have, because fastest processors can UV more. I have had UV -150mV with no problems, but again, it depends so much about your CPU's type.
Also, you said you flashed Franco 174, I think there is a newer version, and flash a JWR kernel because PA is now JWR based.
Related
After reading through the Thread for the Pre Release of FuguMod Ultra in the development section of this forum I thought I would post some info up for people who are wondering why it doesn't work with their phone, and just some general info on overclocking.
- First off, not all phones will be able to run at 1366MHz. Every CPU made has a range of freuqencies it will work at, and it is different for every single one. So some may be able to handle 1366MHz and above, others may max out at 900MHz. If you are getting black screens, freezes, or random behaviour, then your CPU doesn't like the frequency you have it at, try a lower frequency.
- Always keep an eye on the temp of the CPU when testing overclocking, if the CPU gets too hot, and fail safes don't work, there is a chance you could fry your CPU.
- With the FuguMod Ultra kernel, you must also be aware that gpu bus frequencies have been changed, so if your phone is not happy with that it will black screen. (as bus speeds are like cpu speeds, every different device can handle different clock speeds)
- plls values have been changed, and these may cause problems on your phone.
So if you want to have a go at overclocking your phone, back it up, and then give it a go. Select a frequency, and test with something pretty cpu intensive (3d game, multiple quadrant passes) and see if there are any bugs/overheating during a 15min time period. If you notice any problems/too much heat, try a lower frequency, and try again. And if for some reason your phone doesn't like the kernel, you can reflash with your previous kernel or a new ROM as you have already backed up your data.
If you have any other questions about overclocking, feel free to post here and I will try my best to answer them.
--- Samsung G3, InDroid 4.3, FuguMod 2.4 B3 800MHz ---
How can you check the CPU temperature? I thought it was only battery temperature.
Sent from my GT-I5800 using XDA App
dilzo said:
How can you check the CPU temperature? I thought it was only battery temperature.
Sent from my GT-I5800 using XDA App
Click to expand...
Click to collapse
The battery temp is a good representation of how hot the processor is getting as it is right next to the battery (only a thin sheet of metal seperating it) If the battery rises in temperature by a few degrees, then you can summize that the cpu is probably getting a few degrees hotter than that. I really wouldn't recommend letting the battery get above 55degrees (celcius) as this means the CPU may be getting up close to 65degrees (celcius) which is a very bad thing.
Good post.
Note that if you want to make some stress-tests, you have to put "PERFORMANCE" governor and set the max freq you want to test.
marcellusbe said:
Good post.
Note that if you want to make some stress-tests, you have to put "PERFORMANCE" governor and set the max freq you want to test.
Click to expand...
Click to collapse
Yes, Very true!!
Must also say, Your kernels are pretty legendary! Waiting patiently for the offical release of your FuguMod Ultra
m not able to see time in state with both setcpu and cpuspy and it seems deep sleep is also not working.
Piyush Rawal said:
m not able to see time in state with both setcpu and cpuspy and it seems deep sleep is also not working.
Click to expand...
Click to collapse
How have you got your phone set up? i.e. what ROM are you using etc.
I am using stock jpq with app2sd, swap, zipalign, ramhack and stuff. Setcpu is installed with default min/max freakquency, No profiles in use and undervolt a bit.
Ok,
This may be an issue caused by XXJPQ, as it is a new release there may be some sort of conflict. Have you tried asking if anyone else has this issue in this thread? http://forum.xda-developers.com/showthread.php?t=1132697
I haven't played around with JPQ yet so don't know what the bugs are yet.
Also, are you running a stock kernel? Have you confirmed that the phone has been rooted properly as well?
It's definitely a bug in Kernel. I tried three different roms and i wasn't able to check time in state in any of them (I am talking about fugumod ultra prerelease kernel here).
With previous versions of fugumad kernel everything is fine. So definatly a bug in kernel.
Piyush Rawal said:
It's definitely a bug in Kernel. I tried three different roms and i wasn't able to check time in state in any of them (I am talking about fugumod ultra prerelease kernel here).
With previous versions of fugumad kernel everything is fine. So definatly a bug in kernel.
Click to expand...
Click to collapse
Ok cool, I'll report the bug to the developer so that he can have a look into it. Thanks for testing and proving to the kernel.
Little bit of info some might find helpful. After some recent testing, I have found that some people might experience a black screen freeze when phone is in standby for a while with 83MHz min setting and on demand governor. I am not sure of the exact reason for this, whether it is a bug, or that the processor just doesn't like going that low for extended periods of time. If you experience this type of error, just hard reset the phone then open setcpu after phone has loaded and change the "standby" profile minimum to at least the next step up on the slider. Personally I use 223 setting as it provides a smoother lock screen animation, and no significant difference in battery drain.
Sent from my super smooth GT-I5800 using XDA App
I'm currently running turl1's v8 with the kernel that comes with it. I've read about people having this issue with faux'd kernel and that they fixed it by using the one is turl's build. I've attached a pic of the Time in State screen from SetCPU.
Sent from my MB860 using XDA
I am using jokersax 0.3.1. Same issue.
do you guys have profiles set?
Only based on temperature. Do you?
I have profiles set when the screen turns off and such.
I still have idle problems, but its masked a little if you underclock to 912. and with hardware acceleration you can hardly notice it.
I I did have the idling problem with previous builds so I switched to turls1's. When the new 0.3.1 came out I switched back. I also changed from setcpu to antutu cpu master pro, and now it idles correctly.
I'm using turl1's V8 Kang with faux123 025 beta kernel (1.0Ghz), and here is my CPU freq for something like a week.
I use a profile for screen off- 216-608.
Now mine looks a lot better. But I didn't change anything..??
I'm not using a profile on mine either. I think I'm going to try faux's kernel and see if it improves any. I think I would get fairly great battery life if I could resolve this issue. I got down to only 84% after moderate screen time and video and music playback today with over 8 hours off of the charger. Most time was spent in 312Mhz with 608Mhz being the next highest and 216Mhz as the third.
Sent from my MB860 using XDA
My cpu seems to be working great on turl's v8 with the default kernel. I was getting pretty poor battery life on joker's ROM, but on Turls v8 I'm getting the best I've ever had; stock or not.
Sent from my MB860 using XDA
Running Jocker's latest with the latest Faux 1.3GHz kernel.
Idles mostly at 456MHz.
Something wrong there.
After flashing faux's 1Ghz kernel and setting a profile for screen off @216Mhz it has greatly improved. Although it seems any time the screen is on it never hits 216. My battery life didn't seem to get any better either which I find odd.
Sent from my MB860 using XDA
another vote for turl fixing batt life.
No idea why some people are so good on faux's but a large proportion have these massive problems.
I switched to turls v8 with the kernel it comes with and now my battery life and cpu usages are great!
told ya, mine looks around the same
tried to feed it back in jokersax forum, not sure if he's picked up on it or not, theres plenty of people saying 'great batt life' but theres enough of us out there who aren't getting that (and whom get decent results with turl). Maybe there are subtle hw differences in certain batches or revisions of the SoC or something like that.
rmkilc said:
I switched to turls v8 with the kernel it comes with and now my battery life and cpu usages are great!
View attachment 936522
Click to expand...
Click to collapse
I've never seen my atrix idle like that.
are you sure? Mine idled similar to that in CM7, now CM9 turl build.
In jokersax build (stock kernel) 0.2 I never got below 456Mhz consequently heat and battery died in ~10% an hour increments even if I didn't touch it
I am experiencing lag on real racing 3, on high graphics. If I overclock to say 2ghz on cpu, will the tablet be stable enough? Should I undervolt ( and does it actually make any difference on temps)? I want to overclock but not at the cost of huge battery drain, can some1 recommend me a good kernel and some stable oc steps?
Sent from my Nexus 10 using Tapatalk HD
lvnatic said:
I am experiencing lag on real racing 3, on high graphics. If I overclock to say 2ghz on cpu, will the tablet be stable enough? Should I undervolt ( and does it actually make any difference on temps)? I want to overclock but not at the cost of huge battery drain, can some1 recommend me a good kernel and some stable oc steps?
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
Are you running a custom ROM and kernel? I play RR3 daily and have NO lag. AOKP PUB ROM with ktmanta kernel, at 1.7mhz CPU and GPU OC to 720. Runs great.
Most OC is safe, issues are really with battery and overheating. I've run for long periods at 1900 just fine.
So there's no way the tablet will melt down because of the heat? Does warranty cover that? Assuming they don't know it was overclocked, which they couldn't because the device would be dead, right? I guess they don't bother to repair it and see if it was rooted.
LE: btw did you manage to safely undervolt? Even a -5 gives me reboots on most freqs.
Any time I try to use the app from the store to set the graphics mode it causes problems. Running RR3 without it works fine.
lvnatic said:
So there's no way the tablet will melt down because of the heat? Does warranty cover that? Assuming they don't know it was overclocked, which they couldn't because the device would be dead, right? I guess they don't bother to repair it and see if it was rooted.
LE: btw did you manage to safely undervolt? Even a -5 gives me reboots on most freqs.
Click to expand...
Click to collapse
Take a look at the KTmanta thread. KTmanta is a great option for what you are after, he notes and codes distinctions between clocking and thermal protection, plus unless you lock the settings, they will reset at reboot!
If you tell Google you messed it up from some sort of tinkering, no - they won't help you.
lvnatic said:
So there's no way the tablet will melt down because of the heat? Does warranty cover that? Assuming they don't know it was overclocked, which they couldn't because the device would be dead, right? I guess they don't bother to repair it and see if it was rooted.
LE: btw did you manage to safely undervolt? Even a -5 gives me reboots on most freqs.
Click to expand...
Click to collapse
I am assuming you must be using the KTmanta kernel right? I thought it was the only kernel right now that allows for user control undervolting. Trinity has a static -50mv value set on all frequencies by default. You should be able to undervolt just about everything. Getting lockups at -5mv lets me think there is something you are not doing correctly
EDIT: threw the quote in so its less confusing
EniGmA1987 said:
I am assuming you must be using the KTmanta kernel right? I thought it was the only kernel right now that allows for user control undervolting. Trinity has a static -50mv value set on all frequencies by default. You should be able to undervolt just about everything. Getting lockups at -5mv lets me think there is something you are not doing correctly
Click to expand...
Click to collapse
Yes, the kernel
Edit: oops thought you were asking me, I see now I was confused.
I have big battery problems whit my Find5.
Big battery drains overnight even on WiFi.
http://i.imgur.com/1IrrD2L.png
I flashed lastest 4.1 modem via fastboot from http://forum.xda-developers.com/showthread.php?t=2428241 Q_V1_P14_M9615A-CEFWMAZM-2.0.1213_130815.bin
But it doesnt help
Can anyone help me out?
I really hate msm thing since i expirienced it on my N4.
Did you try to change the governor to conservative? That worked for me in CM. The ondemand kernel went to full clock speed all the time...
uishido said:
Did you try to change the governor to conservative? That worked for me in CM. The ondemand kernel went to full clock speed all the time...
Click to expand...
Click to collapse
I switched to CM10.1.3 RC2.
Gonna test for a day and will post results here.
uishido said:
Did you try to change the governor to conservative? That worked for me in CM. The ondemand kernel went to full clock speed all the time...
Click to expand...
Click to collapse
The problem that I'm talking starts after battery goes below 90%. As I seen the faux kernel helps a bit but stock rom kernels doesn't help anything.
Sent from my Find 5 using Tapatalk 4
Karlo666 said:
The problem that I'm talking starts after battery goes below 90%. As I seen the faux kernel helps a bit but stock rom kernels doesn't help anything.
Sent from my Find 5 using Tapatalk 4
Click to expand...
Click to collapse
Just try out some other ROMs, maybe 4.3 ROMs I have no battery draining with maxwens AOKP and Kernel:
Hey guys.
I have a clean Mahdi ROM (the latest from like 1 week ago) and have the feeling that the battery drains slightly faster than in stock. Apart from other things I started trying different kernel tweaks and I discovered the following:
The governor, although showing explanations for a whole 7 different modes, only allows me to either pick "interactive" or "performance".
Since I never really need the CPU settings from interactive mode, I actually want to use conservative.
How can I realise that now?
Please feel free to post your battery life stats, I'm really curious.
Sidenote: I have "transparent weather clock" on my homescreen and it seems to need a lot of battery. Does anyone have a recommendation for a lightweight & goodlooking homescreen widget?
The kernel for that ROM only contains two governors, please do not use performance because it only uses your max frequency, which is bad for temp & battery life.
Ace42 said:
The kernel for that ROM only contains two governors, please do not use performance because it only uses your max frequency, which is bad for temp & battery life.
Click to expand...
Click to collapse
Ok, thanks for the info. I wondern why it only contains those two though.
I'd never use performance, interactive already provides more power than I need.
I'm just looking for a way to actually use the conservative mode.
Something weird just happened to me: my phone was at about 38% and when I looked 1h later, it was pretty warm and powered off 1min later because battery had dropped to 1%.
I think this is pretty weird. I did not use the phone in that hour and had no apps running.
As illogical it might sound, my first suspect was the energy saving mode I enabled. I dont know why but I think it messed something up.
Does anyone have similar issues or any useful advice for me?
w00ZzL said:
Ok, thanks for the info. I wondern why it only contains those two though.
I'd never use performance, interactive already provides more power than I need.
I'm just looking for a way to actually use the conservative mode.
Click to expand...
Click to collapse
The developer believes those to be the best choices, I have no clue why. Interactive mostly stays near the max freq & makes my phone uber hot like an oven. Feel free to use Render kernel, its in the general section.
w00ZzL said:
Something weird just happened to me: my phone was at about 38% and when I looked 1h later, it was pretty warm and powered off 1min later because battery had dropped to 1%.
I think this is pretty weird. I did not use the phone in that hour and had no apps running.
As illogical it might sound, my first suspect was the energy saving mode I enabled. I dont know why but I think it messed something up.
Does anyone have similar issues or any useful advice for me?
Click to expand...
Click to collapse
I've never experienced that, are you on the latest nightly?
Transmitted via Geass
Ace42 said:
The developer believes those to be the best choices, I have no clue why. Interactive mostly stays near the max freq & makes my phone uber hot like an oven. Feel free to use Render kernel, its in the general section.
Click to expand...
Click to collapse
Do you have Render kernel? If yes which governor mode are you using?
Ace42 said:
I've never experienced that, are you on the latest nightly?
Click to expand...
Click to collapse
I'm on the version from 6-28 and patch V6 which should be the latest?!
w00ZzL said:
Do you have Render kernel? If yes which governor mode are you using?
I'm on the version from 6-28 and patch V6 which should be the latest?!
Click to expand...
Click to collapse
That is the latest, I'm currently using Render kernelon 6-28 with ondemand.
http://forum.xda-developers.com/lg-g2/development/kernel-render-kernel-aosp-lg-roms-t2803929/page5
Ace42 said:
That is the latest, I'm currently using Render kernelon 6-28 with ondemand.
http://forum.xda-developers.com/lg-g2/development/kernel-render-kernel-aosp-lg-roms-t2803929/page5
Click to expand...
Click to collapse
Thanks for bringing that kernel up, I've flashed it yesterday and am delighted. Will try the release from today now.
BTW my low battery life is gone now so thanks again.