After a few sleep cycles my tab pro gets stuck at 300mhz maximum cpu level until reboot. Anyone else having this issue? It has been doing it on CM11 and the CM12 build. Not sure what to blame other than the CM kernel.
Haven't had this issue on my 8.4 after many CM11 nightly flashes, and now a couple CM12 builds.
Try to change governors?
They're is a thread like 3 posts up from yours will the same question and an answer.
Its a bug with mpdecision. Someone in that other thread posted a modified mpdecision file to fix this.
No, this is a different issue. In the other issue, the cpu is locked to MAX frequency and it won't go down to 300 or shut off. The solution is to use mpdecision from CM. this issue is like the opposite, and he's already on CM.
I completely turned off mpdecision with a kernel app and I haven't seen it happen again. Good call.
Related
Hi Everyone,
As the thread title states, I'm currently using an OC kernel (Flippy's 1.9GHz, to be exact) and I'm noticing that I have to press the power button many times in order to get the screen to turn on. Does anyone know why this happens? I asked in the kernel thread and someone replied that this happens with all OC kernels, although no explanation was given.
I also read that this issue may be due to the screen off frequency being set too low. I currently have that set to 768MHz and this should be sufficient given the Desire Zs normal clock of 800MHz.
Does anyone have any insight about this? Thanks in advance
I'm using a pershoot OC kernel and haven't met that problem yet. My cpu is set at a 386mhz minimum. Try Pershoot?
Make sure that in CM settings, screen on/off animation is turned off.
From what I can recall, its a problem with a combination of overvolting the CPU for overclocking, and having the animations turned off that results in not enough voltage to turn on the screen.
CPU stepping is also related, so you can try changing the governor and see if that helps also.
This is a common issue, and has been well covered in the CM7 thread, so just do a search in that thread for suggested settings.
redpoint73 said:
Make sure that in CM settings, screen on/off animation is turned off.
From what I can recall, its a problem with a combination of overvolting the CPU for overclocking, and having the animations turned off that results in not enough voltage to turn on the screen.
CPU stepping is also related, so you can try changing the governor and see if that helps also.
This is a common issue, and has been well covered in the CM7 thread, so just do a search in that thread for suggested settings.
Click to expand...
Click to collapse
Thanks for replying I've disabled the screen on/off animations and the screen wakes up with no issues now.
Hopefully this issue will be fixed soon as I'm missing those animations already!
Ok so for the past 2 AOKP builds (the latest nightly and M1 both Jellybean) i have had this weird issue where upon boot, the CPU would be capped at 700Mhz. so i went into ROM control, set it to 1200 and made sure "set on boot" was on.
eventually, even without a reboot, it woud revert back to 700 MHZ. so i checked my other apps that can controll OC/UC. Franko kernal app, and ROM toolbox were both set at 1200 and not set on boot. so ROM control was in charge of the CPU.
yet, no matter what i do, after about 4 hours on use it reverts back to 700 mhz.
this happened on the included Faux kernel and Franko's latest milestone kernel.
anyone else experiencing this? know what causes it?
On CNA and get the same thing. It's horrible because it will lock up my phone.
Bumping Cuz it happened again. This is the most annoying thing I have come across.
Some of these phones are really picky. Try another rom and see if the problem persists.
tgyberg said:
Some of these phones are really picky. Try another rom and see if the problem persists.
Click to expand...
Click to collapse
*whimpering* b...b....but... I.. like this rom...
BTW, I am on CNA with popcorn kernel which is different than the op so I feel like it's a deeper issue.
CNA kangs literally everything from everyone (not saying that in a derogatory sense).
AOKP has this bug as well, and I'm sure it's being worked on on their side...which CNA will then cherry pick.
I had this before,Download nofrills cpu from play store and set the desired freq,your problem will
Be solved.
Sent from my Galaxy Nexus using Tapatalk 2
I've been using CNA 3.5 and had no problem with the max CPU setting to 700Mhz until i started playing around with all of the settings in the start-up tweaks, Kernel controls, color hack presets, and color gamma tuning. I changed all of the settings back to default and have not had the issue since then (18 hours). I have slowly started enabling all of the tweaks one at a time to see what was causing the max CPU to set at 700MHz.
max boot speed to 700mhz is defined in init.tuna.rc, if i recall it correctly.
Sent from my i9250
tried changing the kernel !
I used CNA 3.5 and 3.6.6 Still the same issue.
Tried Trinity Kernel too it did help for sometime but still it reverts back to 700mhz..
Is there any fix yet.... I really Love CNA so i prefer to stay on this rom.
My friend using PARANOID ANDROID has never experienced such an issue.
Hope it is fixed soon
Thanks
I'm having the same issue on CNA 3.6.6. Even when I set it back to 1200mhz it still never goes above 700 mhz.
I'm having the same problem. On CNA 3.8 right now, but have had the same problem on other custom rooted ROMs based off of cm. I finally figured out that it reverts back to 700 MHz during phone calls--or maybe not every phone call, not sure on that part. All my calls recently have bumped it down. At least now I know when it's switching. Just installed the no frills cpu--hopefully that'll help until this bug gets fixed.
Hey there,
i am using Cyanogenmod 11 ROM on my Optimus G E975 since day one i got the phone. I was using the Nightlie from 22nd of April and it was on the whole very satisfying. I was updating to M8 respectively NIGHTLY_20140718, hoping for a few bugfixes and 4.4.4 functions.
After M8 was not keeping my statusbar setting and crashed sometimes i flashed the NIGHTLY superior mentioned. Unfortunately i am experiencing a few issues/bugs. I always wipe everything, flash ROM and Gapps, then i restore my apps and setting with Titanium Backup.
NFC Problem
When i turn NFC on in the Setting, NFC is ticked and greyed out. Do i have to copy some lib-files like in houstonn's old ROM to get it working, or what is the problem ? It was present on old NIGHTLY, too.
Push Problem
In daily use, apps like Facebook, Hangouts and WhatsApp are not pushing anymore, i only get Facebook Message Notification when i open the app manually. Maybe this has something to do with restoring an Titanium Backup ? But, i never had this kind of problem in my "flashing career".
Camera Problem
When i try to make a photosphere or panorama with the google camera app, it shows only black in the display and does not take a pic.
Here is a screenshot : https://db.tt/MbsC6hrO
As the Optimus G is kind of a "sister model" of the Nexus 4, shouldnt Photosphere by usable ? This problem was present on old NIGHTLY, too.
Power Button Response
I'm not sure, but i think after flashing new NIGHTLY i have to press the Power Button with more force or longer to wake up the device.
After doing an hour of research in the forums, i did not figure out any solutions.Is anyone of you sharing my experiences ? If there are solutions aviable for the problems mentioned above, would you please be so kind, to guide my to the corresponding links ?
Thanks a bunch,
Christian
I'm only using the CM11 M8 Snapshot, not the nightly but I'm having the same NFC and Photosphere/panorama issues you're having too.
Regarding the power button and push problems, I don't seem to be having those issues.
Hope there's a fix for them.
I guess there's also another issue with CM11 M8: the "Processor" CPU clock controller on "Perfomance" menu is completely unreliable. The Maximum CPU Frequency just doesn't get saved. It doesn't mean which CPU governor you're currently using.
For example, I set max CPU frequency as 594 Mhz and "ondemand" profile, but some time later, I touch the phone and notice it's really hot. When I check the max CPU freq value again, I see it reverted to the default 1512 MHz, which explains the heat. It also reverts to the max CPU freq when rebooting the phone, even if "Set on boot" box is ticked. And it also happens with SetCPU app, but does not with stock firmware.
Just wondering if anyone else has run into this issue. I made a post a few days back about it but have since found out that the problem is fixed by setting the minimum CPU frequency to a couple settings below the max allowed. Is this normal?
Happened on stock ROM and FreedomOS both running ElementalX kernel and Franco Kernel. Both ROMs and kernels suffering this massive slowdown.
Anyone else having or have had this happen?
As the title says, I have this problem where the big cluster frequency stays at 2361MHz and doesn't drop down to its idle frequency. It occasionally goes down to about 2000MHz, but rises back to its max frequency within a second.
I tried clean flashing OOS 5.0.3 (zip from OP website), I'm not rooted, no custom kernel (all stock basically). It seems to happen after a few hours and not as soon as the device is turned on.
I'm wondering if it's a kernel problem/bug or something else (play services for example). I'd really like to know if anyone else experienced it and if anyone got it fixed.
are you using a custom kernel or root?
if so download elementalx or any kernel editing tool and change the cluster back to 300mhz
i find i have to do this for the cluster to scale back down
You can try New Kernel by @jgcaap.
It's probably the best kernel for this phone with amazing performance/smoothness/battery.
In the latest build the idle freqs are back to normal after OnePlus mess/faulty optimisation in OB2.
https://forum.xda-developers.com/oneplus-5t/development/newkernel-t3710363
If your CPU doesn't idle it can also be an app running in background and hogging cpu time.