What is the 1Ghz Bug I keep hearing about?
The phone just keeps running at maximum CPU frequency, no matter what you are doing at the moment. It most commonly happens when you are using the abyssplug governor.
Sent from my GT-I8190 MaclawStudio CM 11 using Tapatalk
it drains battery very high too
GXGOW said:
The phone just keeps running at maximum CPU frequency, no matter what you are doing at the moment. It most commonly happens when you are using the abyssplug governor.
Sent from my GT-I8190 MaclawStudio CM 11 using Tapatalk
Click to expand...
Click to collapse
Thanks GXCOW. The next question(s) is, what do you do when it happens? and how do you change your governor?
johnporter29 said:
Thanks GXCOW. The next question(s) is, what do you do when it happens? and how do you change your governor?
Click to expand...
Click to collapse
turn off wifi and reboot
change governor with no frills cpu for example
johnporter29 said:
Thanks GXCOW. The next question(s) is, what do you do when it happens? and how do you change your governor?
Click to expand...
Click to collapse
you can find it in faq by mauam
you can change governor in settings/performance/processor
I/o scheduler in settings/performance/I/o scheduler
Don't know why, but as I tried a different governor, my CPU is now stuck at 1ghz, unless I chose "powersave". I used to go with "conservative" and it was working just fine. :crying:
I've tried to change to other settings, but they all stick at 1ghz. Wi-fi off, data connection off, reboot after reboot, changing setting after setting.
Is there anything I can do, beside re-flash my ROM, to correct this? Yes, I've googled answeres but found none that works.
Currently I'm using Virginity V7 with setCPU.
broman.m said:
Don't know why, but as I tried a different governor, my CPU is now stuck at 1ghz, unless I chose "powersave". I used to go with "conservative" and it was working just fine. :crying:
I've tried to change to other settings, but they all stick at 1ghz. Wi-fi off, data connection off, reboot after reboot, changing setting after setting.
Is there anything I can do, beside re-flash my ROM, to correct this? Yes, I've googled answeres but found none that works.
Currently I'm using Virginity V7 with setCPU.
Click to expand...
Click to collapse
I have exacly the same problem. sounds like a ROM problem to me, but I'll try to switch off wifi and governators to see if I can find the problem because I remember that in V6 I had no problem with 1ghz bug
Related
im using serendipity 4.0.1, and rGB-v.4-Voodoo #10, im new to UV the phone, but i search in the post and found a template, i applied it and save it as boot setting, when i pressed the back button and open the app again, the values reseted, how do i maintain them?
The values reset because you didn't hit "Apply for now".
"Apply for now" applies the values until you reboot the phone and "Save as boot setting" saves your settings for everytime the phone boots up.
So, either put everything back in and hit "Apply for now" or restart the phone. I recommend erasing your bootup settings and hitting "Apply for now" so you don't end up in a boot loop if your settings are not stable.
how do i erase my bootup settings?
i dont know how to set up my voltage control app, it keep crashing on me
also consider the battery life for normal usage when oc ...
im not trying to over clock, i just want to save on battery but i cant seem to set up Voltage Control without crashing, i dont know what to do anymore, i cant set it up!!
hernan078 said:
im not trying to over clock, i just want to save on battery but i cant seem to set up Voltage Control without crashing, i dont know what to do anymore, i cant set it up!!
Click to expand...
Click to collapse
Try going to adb shell and removing it, and then reinstalling it. If that doesn't work you might just need to reflash Serendipity.
Auridran said:
Try going to adb shell and removing it, and then reinstalling it. If that doesn't work you might just need to reflash Serendipity.
Click to expand...
Click to collapse
i think the problem is not the app, is the values im using, i dont know what to do, i was pumped to using voltage control to save battery!
hernan078 said:
i think the problem is not the app, is the values im using, i dont know what to do, i was pumped to using voltage control to save battery!
Click to expand...
Click to collapse
Have you tried lower values? Does it do the same thing?
I lower the values and it works, for a while, when i press the lock button i wait 2 minute or less and the phone crashes and i have to do a battery pull out!
hernan078 said:
I lower the values and it works, for a while, when i press the lock button i wait 2 minute or less and the phone crashes and i have to do a battery pull out!
Click to expand...
Click to collapse
What values are you using? Not all the processors in the phones are created equal, and some don't like to be run very far out of spec.
I would recommend to start conservatively.
Note: If u r using OC based kernels, try not to reduce much voltage from any step over 1200. I think I read in some post there (probably glitterballs' kernel related one) that 1200 and 1280 both use same voltage levels. So its best to be conservative on that end.
Values I regarded as safe are 100, 100, 75, 50, 50, 50 (bottom to top), and the ones I am currently using are 125, 125, 100, 75, 75, 50 (bottom to top), and I have my speed capped at 1000 (since this is sufficient for my needs).
diablo009 said:
I would recommend to start conservatively.
Note: If u r using OC based kernels, try not to reduce much voltage from any step over 1200. I think I read in some post there (probably glitterballs' kernel related one) that 1200 and 1280 both use same voltage levels. So its best to be conservative on that end.
Values I regarded as safe are 100, 100, 75, 50, 50, 50 (bottom to top), and the ones I am currently using are 125, 125, 100, 75, 75, 50 (bottom to top), and I have my speed capped at 1000 (since this is sufficient for my needs).
Click to expand...
Click to collapse
Im using rGB-v.4-Voodoo #10 Kernel, and i put the values you posted, but it crashes on me, do i need to change my kernel or something like that?
hernan078 said:
Im using rGB-v.4-Voodoo #10 Kernel, and i put the values you posted, but it crashes on me, do i need to change my kernel or something like that?
Click to expand...
Click to collapse
Your phone may just not be quite capable of those undervoltages. It might not be capable of any undervolting at all. Remember, undervolting is running the processor out of spec. It's all luck of the draw if you get a processor that is from the top of the bin or a processor that is from the bottom of the bin.
Auridran said:
Your phone may just not be quite capable of those undervoltages. It might not be capable of any undervolting at all. Remember, undervolting is running the processor out of spec. It's all luck of the draw if you get a processor that is from the top of the bin or a processor that is from the bottom of the bin.
Click to expand...
Click to collapse
but it doesnt matter what kernel im running? if i use a kernal that dont support UV, i cant UV? The kernel im using, support undervolt?
hernan078 said:
but it doesnt matter what kernel im running? if i use a kernal that dont support UV, i cant UV? The kernel im using, support undervolt?
Click to expand...
Click to collapse
As far as I know, every kernel that supports overclocking for the Captivate supports undervolting. I know for a fact the kernel you're using does.
Auridran said:
As far as I know, every kernel that supports overclocking for the Captivate supports undervolting. I know for a fact the kernel you're using does.
Click to expand...
Click to collapse
And what you suggest is the problem? :S
hernan078 said:
And what you suggest is the problem? :S
Click to expand...
Click to collapse
Like I said, your CPU probably can't handle the level of undervolting you're trying to give it. Also, some peoples' phones can't even reach 1.28GHz (the stock clock of the kernel you're using) without undervolting at all, so your problem could easily lie there, unless you've limited the clock to 1GHz in Voltage Control.
hernan078 said:
Im using rGB-v.4-Voodoo #10 Kernel, and i put the values you posted, but it crashes on me, do i need to change my kernel or something like that?
Click to expand...
Click to collapse
Is it crashing for the values in green too? They were supposed to be very conservative, and the ones I regard as "safe".
And like "Auridran" quoted, try limiting speed to 1000.
Edit: I would recommend u starting with 25 for lower speeds, and try not reducing voltage at speeds over 800.
I recently flashed the aospCMod-20110123 (gingerbread) on my sprint HTC hero. The upgrade has been awesome so far except for one really annoying issue. My pandora app hasn't been playing properly (I uninstalled and reinstalled the app). The music becomes choppy when the screen turns off. Reactivating the screen fixes the sound most of the time but it's really annoying. I haven't had this issue before with CM6.1 (froyo). Did anyone else see this issue ? I would greatly appreciate for any possible solution to this problem.
Thanks.
prashm said:
I recently flashed the aospCMod-20110123 (gingerbread) on my sprint HTC hero. The upgrade has been awesome so far except for one really annoying issue. My pandora app hasn't been playing properly (I uninstalled and reinstalled the app). The music becomes choppy when the screen turns off. Reactivating the screen fixes the sound most of the time but it's really annoying. I haven't had this issue before with CM6.1 (froyo). Did anyone else see this issue ? I would greatly appreciate for any possible solution to this problem.
Thanks.
Click to expand...
Click to collapse
If you are using the kernel that comes with the ROM:
Go into CM Settings and then performance.
Within CPU Settings, change the governor to ONDEMAND.
You'll have to reboot. If that alone doesn't fix your problem then bump you MIN CPU setting to 256.
What is your min set to? Probably needs to be bumped up to 264 or whatever.
poashll said:
If you are using the kernel that comes with the ROM:
Go into CM Settings and then performance.
Within CPU Settings, change the governor to ONDEMAND.
You'll have to reboot. If that alone doesn't fix your problem then bump you MIN CPU setting to 256.
Click to expand...
Click to collapse
Thanks for quick reply. However, I don't find the CPU settings option under Settings->CyanogenMod settings -> Performance. Is that enabled by a separate app that I may be missing ?
prashm said:
Thanks for quick reply. However, I don't find the CPU settings option under Settings->CyanogenMod settings -> Performance. Is that enabled by a separate app that I may be missing ?
Click to expand...
Click to collapse
If you flashed a different kernel, you will not see the option. If that is the case, you will need to use Setcpu or Deca's battery tweak.
Sent from my HTC Hero CDMA using XDA App
poashll said:
If you flashed a different kernel, you will not see the option. If that is the case, you will need to use Setcpu or Deca's battery tweak.
Sent from my HTC Hero CDMA using XDA App
Click to expand...
Click to collapse
Thanks poashll. I installed cputuner free app and restarted ph. That completely jacked my ph. I kept on getting "The process com.android.phone has stopped unexpectedly.." error. Nothing seemed to fix it. So I restored my cm6 backed up rom. Thank God that I had backed up my prev ROM. Then I downloaded and flashed the latest CM7 nightly build. This one had the CPU Settings option. Before I mess with it, I backed up my current configurations (it's a real pain in the butt to re-install all the lost apps and configurations). And then changed the governor to ONDEMAND. Now my pandora works great and battery life is still good!
Thanks a ton for all the help! I appreciate that.
hmmmm... I have been having the same problem since I installed ASOP gingerbread. and still have it with CM 7. adjusting the cpu settings work fine for me as long as I don't let the phone's screen go to sleep. but if the screen stays awake it's fine....
any other setting you suggest? kind of a waste of battery to be running pandora AND have the screen awake all the time.
noriyori said:
hmmmm... I have been having the same problem since I installed ASOP gingerbread. and still have it with CM 7. adjusting the cpu settings work fine for me as long as I don't let the phone's screen go to sleep. but if the screen stays awake it's fine....
any other setting you suggest? kind of a waste of battery to be running pandora AND have the screen awake all the time.
Click to expand...
Click to collapse
What settings are you using?
Sent from my HTC Hero CDMA using XDA App
poashll said:
What settings are you using?
Sent from my HTC Hero CDMA using XDA App
Click to expand...
Click to collapse
I set the governor to ONDEMAND and the MIN to 264. But like a dummy, I didn't set the 'Set on boot' option so my settings reverted when I rebooted...
How is the ondemand governor different than the standard interactive governor?
Mine is still on interactive, but the min is on 352. Anything lower than that for my phone, and it will skip when the screen turns off.
Hi folks,
I am using the latest (20140908) omni rom nightly build and I have the following issues:
I am getting called (ringtone) but the screen stays black for 5-10 seconds
Alarmclock: when it goes off, the screen stays black and i can't switch it off (very annoying)
Screen takes 2-3 seconds or more to light up after I press the power button
Any ideas on that?
Thanks!
adam recommends (well, used to, not sure if it's still the case) that you use a custom kernel, and he mentioned iodak's few times. remember to set max screen off frequency to 1ghz or so via trickstermod, so the device won't lag (default is 475 mhz which isn't quite enough) with wake-up when screen is off
Thanks, I'll try the frequency fix first (I have no modifications there whatsoever) and if it's not helping go with mourta kernel.
aktentasche said:
Thanks, I'll try the frequency fix first (I have no modifications there whatsoever) and if it's not helping go with mourta kernel.
Click to expand...
Click to collapse
you're only able to change screen off frequency on iodak-based kernels (mourta, iodak, cyodak, mahdi), not stock omni. good luck
I personally use Tasker to set performance governor for 5 seconds when a call comes.
That is also an interesting idea. I'll see how the phone performs with the next incoming call and if the problem still occurs I'll try it.
Until now I installed mourta 02/09 and I'm using abyssplugv2 governor. It does not have a max screen off frequency but the smoothness is much better already.
aktentasche said:
That is also an interesting idea. I'll see how the phone performs with the next incoming call and if the problem still occurs I'll try it.
Until now I installed mourta 02/09 and I'm using abyssplugv2 governor. It does not have a max screen off frequency but the smoothness is much better already.
Click to expand...
Click to collapse
I've the same problem on cyanogenmod with stock cm kernel. When i install another kernel such as iodak my 4x is faster and smoother. Try to install iodak and set the min cpu freq to 475mhz.
When battery goes low and 2 cores are shutted off, when they come back on they will be stuck to max freq, it happens even with thermal throttling, I have not the solution to this problem, if someone more capable of me may help me I will be glad
fedef12evo said:
Nexus 6 is a good phone, but there are lot of small glitches, one of them is the freq stucked to max (2649000) for 2 cores, it happens when phone goes thermal throttling, and thermal manager shut down 2 cores, then when temperature goes down to safe, mpdecision will push online the 2 cores shutted down and 90% they will get stucked to max freq,to avoid this annoying bug I modified thermalconfig for shamu to avoid shutting down cores in hot situations,thermal manager will work anyways by lowering max freq but it will no longer disable cores.
https://www.dropbox.com/s/802p4kr0kqcj7g0/thermal-engine-shamu.conf?dl=0
here the thermal engine modified, if anyone is able to make a flashable zip post here. Push thermal engine to system/etc, and set permission 0644 or rw-r--r--
Click to expand...
Click to collapse
lol, you went about it the LOOOOOOOOOONG way around. i just turn off thermal throttling when i boot. but thats not the main kicker, i also use a different cpu system. i change my governor to ondemand, and it all functions better.
anyways, this is how you disable thermal throttle via a terminal emulator app..
su(press enter)
echo N > /sys/module/msm_thermal/parameters/enabled/(press enter)
simms22 said:
lol, you went about it the LOOOOOOOOOONG way around. i just turn off thermal throttling when i boot. but thats not the main kicker, i also use a different cpu system. i change my governor to ondemand, and it all functions better.
anyways, this is how you disable thermal throttle via a terminal emulator app..
su(press enter)
echo N > /sys/module/msm_thermal/parameters/enabled/(press enter)
Click to expand...
Click to collapse
with ondemand, power consumption is more than interactive, also I need thermal throttling, because when cpu temp is more than 50 degrees is very hard to touch the screen
fedef12evo said:
with ondemand, power consumption is more than interactive, also I need thermal throttling, because when cpu temp is more than 50 degrees is very hard to touch the screen
Click to expand...
Click to collapse
lol, 50? seriously? i guess mobile computers are not for you then, as 50C is a normal temperature, before thermal throttle kicks in. and no, ondemand is much better for battery consumption. i see 5.5-7 hours sot every single day.
Interactive works quite well
lol, all the governors work well, just how they are supposed to.
simms22 said:
lol, you went about it the LOOOOOOOOOONG way around. i just turn off thermal throttling when i boot. but thats not the main kicker, i also use a different cpu system. i change my governor to ondemand, and it all functions better.
anyways, this is how you disable thermal throttle via a terminal emulator app..
su(press enter)
echo N > /sys/module/msm_thermal/parameters/enabled/(press enter)
Click to expand...
Click to collapse
Interesting! Does this work on stock+root?
toastgodsupreme said:
Interesting! Does this work on stock+root?
Click to expand...
Click to collapse
yes
simms22 said:
yes
Click to expand...
Click to collapse
Seems mine was disabled by default. So no effort needed by me then.
Didn't Franco try this awhile ago but abandon it because it was so unstable??
toastgodsupreme said:
Seems mine was disabled by default. So no effort needed by me then.
Click to expand...
Click to collapse
fsync is always enabled. the reason for this is if you crash, and fsync is disabled, you can lose data(or not boot up after). so, its ALWAYS enabled unless you disable it manually.
simms22 said:
fsync is always enabled. the reason for this is if you crash, and fsync is disabled, you can lose data(or not boot up after). so, its ALWAYS enabled unless you disable it manually.
Click to expand...
Click to collapse
fsync? i was talking about echo N > /sys/module/msm_thermal/parameters/enabled/(press enter)
fedef12evo said:
Nexus 6 is a good phone, but there are lot of small glitches, one of them is the freq stucked to max (2649000) for 2 cores, it happens when phone goes thermal throttling, and thermal manager shut down 2 cores, then when temperature goes down to safe, mpdecision will push online the 2 cores shutted down and 90% they will get stucked to max freq,to avoid this annoying bug I modified thermalconfig for shamu to avoid shutting down cores in hot situations,thermal manager will work anyways by lowering max freq but it will no longer disable cores.
https://www.dropbox.com/s/802p4kr0kqcj7g0/thermal-engine-shamu.conf?dl=0
here the thermal engine modified, if anyone is able to make a flashable zip post here. Push thermal engine to system/etc, and set permission 0644 or rw-r--r--
Click to expand...
Click to collapse
Well.... I've never seen that happen, or even heard of it. You running some kind of hacked up "custom" junk rom or something? That certainly is NOT normal behavior. Its also the wrong way to fix that kind of issue if you did happen to have a problem like that.
The proper solution is to get rid of whatever brokenness you have that is causing it, or diving into the code to fix whatever is broken. Disabling critical features is not a solution.
doitright said:
Well.... I've never seen that happen, or even heard of it. You running some kind of hacked up "custom" junk rom or something? That certainly is NOT normal behavior. Its also the wrong way to fix that kind of issue if you did happen to have a problem like that.
The proper solution is to get rid of whatever brokenness you have that is causing it, or diving into the code to fix whatever is broken. Disabling critical features is not a solution.
Click to expand...
Click to collapse
It happens in alla Roms, even stock ROM, only with interactive governor.
toastgodsupreme said:
fsync? i was talking about echo N > /sys/module/msm_thermal/parameters/enabled/(press enter)
Click to expand...
Click to collapse
sorry, i was having a conversation in another thread about fsync.. i mistook which thread i was in :angel:
fedef12evo said:
It happens in alla Roms, even stock ROM, only with interactive governor.
Click to expand...
Click to collapse
Definitely not present on stock, so if you're experiencing it, its something you did to yourself.
doitright said:
Definitely not present on stock, so if you're experiencing it, its something you did to yourself.
Click to expand...
Click to collapse
then it is hardware problem of my device
Forgive my newish question: how do we monitor cpu frequencies to know if they're stuck?
electricpete1 said:
Forgive my newish question: how do we monitor cpu frequencies to know if they're stuck?
Click to expand...
Click to collapse
there are many google play and non play store apps that do this. many!
fedef12evo said:
then it is hardware problem of my device
Click to expand...
Click to collapse
I really don't see how a hardware problem could have that kind of a side-effect.
Hey guys so I got this problem I'm wondering if anyone else has gotten it because it is a little frustrating.
OK so my nexus 6 when I game it drops to 1ghz all 4 cores. I have chroma and elementalx. I've tried turning off thermal in kernel auditor and I have used core CPU control and system monitor and it goes fine for fee few seconds then drops down to 1ghz .
Its really annoying I really wish someone could help me. Thanks I'd advance.
Power2daplayer said:
Hey guys so I got this problem I'm wondering if anyone else has gotten it because it is a little frustrating.
OK so my nexus 6 when I game it drops to 1ghz all 4 cores. I have chroma and elementalx. I've tried turning off thermal in kernel auditor and I have used core CPU control and system monitor and it goes fine for fee few seconds then drops down to 1ghz .
Its really annoying I really wish someone could help me. Thanks I'd advance.
Click to expand...
Click to collapse
change how your CPU is set up(by changing your governor/scheduler), and disable mpdecision. its very simple to get your CPU to work as you want it to, just learn what the different governors and their option do.
simms22 said:
change how your CPU is set up(by changing your governor/scheduler), and disable mpdecision. its very simple to get your CPU to work as you want it to, just learn what the different governors and their option do.
Click to expand...
Click to collapse
I have it on elemental governor, I heard you need busybox for it to stick but i dont know.
Sometimes I try to change the max frequency but it just won't change, the frequency's go all over the place haha.
Do you know which kernel is best for gaming on the nexus 6 ?
Power2daplayer said:
I have it on elemental governor, I heard you need busybox for it to stick but i dont know.
Sometimes I try to change the max frequency but it just won't change, the frequency's go all over the place haha.
Do you know which kernel is best for gaming on the nexus 6 ?
Click to expand...
Click to collapse
elemental is fine, probably do need busybox. but it sounds as you need to disable mpdecision.
BCL driver.
Check it out HERE.
You can even follow the instructions there to disable it.
Or you can install singularity kernel and the singularity kernel app with it. Singularity kernel has a option to disable it, along with a TON of other features.
The frequency drops because the CPU ***TEMPERATURE*** gets too high. Don't mess with it unless you like instability and "random" reboots.
doitright said:
The frequency drops because the CPU ***TEMPERATURE*** gets too high. Don't mess with it unless you like instability and "random" reboots.
Click to expand...
Click to collapse
funny, i disable thermal throttle every single time i boot up, since nov 2014, i my n6 doesnt get instability, and doent reboot.
simms22 said:
funny, i disable thermal throttle every single time i boot up, since nov 2014, i my n6 doesnt get instability, and doent reboot.
Click to expand...
Click to collapse
We've already gone over this and confirmed that your observations are incomplete.