I just installed this Rom on my Kindle Fire but my Cpu always stays over 800Mhz and I can't get it any lower even with SetCpu or in the performance options menu.
Is that a known problem? Cause it heats a lot!
Related
Hi guys,
i tried CM7 but it was really laggy at my device, a lot of you guys said it is a very fast release !? so how can i get it working smooth ? when i wanted to get into the cpu settings i had a force close every time, jit was enabled..
do i have to get setcpu ? when yes where? which frequencies run smooth and stable ?
thanks in advance
eichl0r said:
Hi guys,
i tried CM7 but it was really laggy at my device, a lot of you guys said it is a very fast release !? so how can i get it working smooth ? when i wanted to get into the cpu settings i had a force close every time, jit was enabled..
do i have to get setcpu ? when yes where? which frequencies run smooth and stable ?
thanks in advance
Click to expand...
Click to collapse
Wipe EVERYTING, install CM7 then install HCDR.Kernal 4.1 (4.2 doesn't work as well) then use another overclock program, not setcpu, it doesn't work well with CM7. Hope that helps you!
* First, try flashing Kernel v4.1. CM7 comes with Kernel 4.2 by default, and, because it is clocked at 768 max, it leads to a lot of stability problems for everyone. Look for the HCDR.Kernel Topic in Wildfire Android Development Zone
* After that, you can install SetCPU. The SetCPU Dev has a thread here on XDA where he has posted the APK of SetCPU for download. Just enter SetCPU in the search bar and you should be able to find the thread with no issues. Here, you can set the max (Upto 710 recommended) and min (upto 245 recommended)
This should solve your lag and stability issues. If it still doesn;t, two more apps which can cause lag are (Note: This affects only a small %age of members with CM7)
* SetCPU (Alternative: OverclockWidget)
* ADW.Launcher (Alternative: Any other Launcher)
Oh, and CPU Settings FC's for everyone, from the time it was implemented. Looks like it is not ready yet.
Good Luck
hey 3xeno, thanks for your tipps!
with kernel 4.1 + setcpu + adw.launcher ex it finally works good!
the only thing thats a little strange is that i couldnt use my overclock setup from the openfire rom i had before, i have your suggested settings + screen of profile (352 max 245 min)+ tmep > 46° profile (352 max 245min), with openfire it was possible to have it at 691 mhz max and 245mhz min for normal mode, now i had to put it on 614 max 245min to not get the battery too warm, but anything else works great
eichl0r said:
hey 3xeno, thanks for your tipps!
with kernel 4.1 + setcpu + adw.launcher ex it finally works good!
the only thing thats a little strange is that i couldnt use my overclock setup from the openfire rom i had before, i have your suggested settings + screen of profile (352 max 245 min)+ tmep > 46° profile (352 max 245min), with openfire it was possible to have it at 691 mhz max and 245mhz min for normal mode, now i had to put it on 614 max 245min to not get the battery too warm, but anything else works great
Click to expand...
Click to collapse
That is rather weird, because, many are keeping it at 710 MHz Max and having no issues. What is your battery temperature when you keep it at 691? (And at idle. It is normal for the phone to get warm when you continuously run a heavy app like a game on it, also, I am sure you know this, but dont measure during charging, it does get pretty warm then )
hmm i played around with the phone a little and then put it in my pants pocket, after wa while when i put it back out it has restarted i guess and i was very warm at the back...hmm ill test it a little perhaps it was a one time thing
Hello,
I'm using N7 16GB with rooted stock 4.1.2 and Trinity Seven Kernel (from alpha 160 to 180).
My problem occured on all kernels so far. I've used different tools to change the CPU frequency like (SetCPU, System tuner and others).
After I OC the CPU to anything from 1.4 to 1.6 after some time it allways fallback to 1.3 after a random time period, without any faults, resets, SoD's or anything. Does anyone knows why is this happening? How can I solve this issue?
The same for me..
I found it!
Recently I was using smartassV2 at 1 Ghz then overclocked to 1.8 without changing the governor and suddenly the screen turned off, rebooted the phone, boot animation appeared then black screen and the phone turned off so I knew that the rom had been corrupted therefore I installed it again. Everything was normal I went again and overcolcked to 1.8 Ghz with smartassV2 governor and the same; the rom had been corrupted so I installed it again. This time I overcolcked to 1.8 Ghz but with ondemand governor and there was no problem.
Now I knew why overclocking to 1.8 is good sometimes and bad another; it has a relation with the governor and I found that ondeman governor is working fine at 1.8 Ghz for .32 kernel.
So try to overclock your phone to 1.8 with ondemand governor or other governors and tell us your experience but be sure to backup your rom, app, data...
I don't know if there is any further problems of overclocking to 1.8 Ghz so do it at your own responsibility.
A couple of notes:
1) Not all chips are created equal; there is slight variance, which means that not all processors found inside U8800 phones can be overclocked to 1,8 GHz.
2) When changing your clock frequency, do not, at first, check the "Set at boot" box. This could send your device into a bootloop, if the setting is not functional.
3) Overclocking and governor functionality may be kernel-specific.
4) I, personally, will not overclock my device to 1,8 GHz, as 1,2 GHz is good enough, in my opinion, but knock yourselves out.
Question: I don't quite understand how overclocking can corrupt a ROM by itself. Could it be that you allowed the non-functional frequency to be set at boot time? (See note #2)
I am using the original U8800 and running dzo's Aurora ICS version 4,1 update 1.
Tonttunator said:
A couple of notes:
1) Not all chips are created equal; there is slight variance, which means that not all processors found inside U8800 phones can be overclocked to 1,8 GHz.
2) When changing your clock frequency, do not, at first, check the "Set at boot" box. This could send your device into a bootloop, if the setting is not functional.
3) Overclocking and governor functionality may be kernel-specific.
4) I, personally, will not overclock my device to 1,8 GHz, as 1,2 GHz is good enough, in my opinion, but knock yourselves out.
Question: I don't quite understand how overclocking can corrupt a ROM by itself. Could it be that you allowed the non-functional frequency to be set at boot time? (See note #2)
I am using the original U8800 and running dzo's Aurora ICS version 4,1 update 1.
Click to expand...
Click to collapse
Thanks for your notes.
No I didn't check the "Set at boot" box and there was no bootloop, the boot animation appeared but in the end the phone turned off.
★HUAWEI IDEOS X5 U8800H★
GT-P1000
CM10
Tried to find out if anyone else has this problem but no luck. I have voltage control set to start the CPU at 1ghz on boot, as well as settings. Sys Tuner Pro isn't set to do anything. I don't have any other o/c apps. Seemingly randomly, while using my phone my CPU sets itself to 800mhz. I can tell when everything starts to slow down, then when I check it, it has gone down to 800mhz. Any idea what is causing this?
Hi guys!!
I am running Stock ROM on my GT-I9301, with @sev3n1985 kernel. I have overheating problems! Sometimes it's very hard to hold my phone. How can I solve it? Btw, I'll leave my Kernel Settings down bellow
Regards :*
Settings (I use Kernel Adiutor):
- CPU Max Freq: 1401Mhz
- CPU Min Freq: 300Mhz
- CPU Governor: smartmax
- Multicore Power Saving: Disabled
- CPU Hotplug: MSM Hotplug (MPDecision desactivates)
- CPU Boosted: 1
- Max Cores Screen Off: 1
- Thermal: Temperature Throttle
Sent from my S3 Neo+ (GT-I9301I) running Custom Made StockROM with @sev3n1985 kernel
Have you already done a factory reset?
Perhaps it's just a bad app.
Jhnsn said:
Have you already done a factory reset?
Perhaps it's just a bad app.
Click to expand...
Click to collapse
I use Greenify even on some system apps, so no background apps. And my ROM is deodexed. So I think that's not the problem. But thank you
Sent from my S3 Neo+ (GT-I9301I) running Custom Made StockROM with @sev3n1985 kernel
S3 Neo is familiar with overheating problems even on stock, but I'm trying to understand, do you have that problem even if you are not using your phone that much?
Sometimes hot plug & governors (more tied to the interactive than ondemand) logic simply bricks hot plug & then you have all cores running all the time. Their is also a conflict tied to additional bust frequency logic. All this is actually cased by Samsung & it's never been corrected in this kernel (it is corrected only in official CM12.1 repo). Simple reset resolve this until it happens again.
Regarding Smart max try like this:
Also go with mpdecision hot plug & use simple on demand GPU governor.
It should save some juice keep consumption under control & device cooler.
Zola III said:
Sometimes hot plug & governors (more tied to the interactive than ondemand) logic simply bricks hot plug & then you have all cores running all the time. Their is also a conflict tied to additional bust frequency logic. All this is actually cased by Samsung & it's never been corrected in this kernel (it is corrected only in official CM12.1 repo). Simple reset resolve this until it happens again.
Regarding Smart max try like this:
Also go with mpdecision hot plug & use simple on demand GPU governor.
It should save some juice keep consumption under control & device cooler.
Click to expand...
Click to collapse
Thanks for your time, dude
You can also try like this to keep it more in green line frequency range even more during the light tasks, performance for the light tasks is not stellar but it's more than good enough this way.
Note: Ideal awake frequency (targeted one) for this SoC should actually be 600MHz considering power voltage and DRAM frequency dependencies but on Samsung firmware this is not fast enough so it actually produces contra effects; jumps to higher frequencies more often along with waking up additional cores so 787 is advised minimum. On the other hand peple who love & use Smart max on other light wait roms such as CM's (without of heap load Samsung bull****s) can actually try with 600MHz. Still interactive governor is possible to be tuned better.
Best regards.