I've recently been able to revive my Nexus 6p which had suffered the BLOD a couple months ago. Long story short, a few members of xda had created custom boot imgs that turned off the bug cluster (4/8 cores) so that the device could function normally. It turned out that there was something wrong with the big cluster that prevented the phone from booting normally.
Now that I have my phone in working condition, I was wondering if anyone knew of a cpu governor that focused on the little cluster only (since my big cluster is disabled). I'm starting to miss the smoothness that this phone originally had before the BLOD. Thanks.
Follow the guide on how to make your phone faster while on four core. Use a custom kernel.
mattrb said:
Follow the guide on how to make your phone faster while on four core. Use a custom kernel.
Click to expand...
Click to collapse
I've already followed the guide. I'm running the modified ex kernel, but I know that optimizations can be done to the CPU governor as well. I was just wondering if anyone had any knowledge in this topic.
Related
Hi all,
I have been browsing this forum for a while now and finally decided to register.
After getting incredibly frustrated waiting for HTC and T-mobile to get their act together and release 2.1 I followed the guides on here and rooted my G2.
I originally flashed VillainROM10.3 and then upgraded to VillainROM12. Both of which are great!
I have since been playing with the CPU speed. I see many people on here claiming CPU speeds of ~750Mhz, however the most I seem to be able to get out of my phone is ~650Mhz (I'm using OverclockWidget from the market to set the frequencies). Is this a problem anyone else has experienced? If so is it down to my phone having a duff CPU or could the problem be with the ROM or the widget I'm using. Whenever I set the phone to anything higher than 650 it either just freezes or reboots itself.
Thanks Guys (and girls?)
hopoffbaby said:
Hi all,
I have been browsing this forum for a while now and finally decided to register.
After getting incredibly frustrated waiting for HTC and T-mobile to get their act together and release 2.1 I followed the guides on here and rooted my G2.
I originally flashed VillainROM10.3 and then upgraded to VillainROM12. Both of which are great!
I have since been playing with the CPU speed. I see many people on here claiming CPU speeds of ~750Mhz, however the most I seem to be able to get out of my phone is ~650Mhz (I'm using OverclockWidget from the market to set the frequencies). Is this a problem anyone else has experienced? If so is it down to my phone having a duff CPU or could the problem be with the ROM or the widget I'm using. Whenever I set the phone to anything higher than 650 it either just freezes or reboots itself.
Thanks Guys (and girls?)
Click to expand...
Click to collapse
It's as simple as; some phones simply can't handle higher MHz
So if I flash for example SuperHero which is supposed to be clocked by default at 691Mhz will my phone freeze on boot or is it smart enough to figure out its max speed.
hopoffbaby said:
So if I flash for example SuperHero which is supposed to be clocked by default at 691Mhz will my phone freeze on boot or is it smart enough to figure out its max speed.
Click to expand...
Click to collapse
It will probably freeze but there are kernels the isn't overclocked that high by default
So I don't mean to keep going on about it but when I flashed VR12 the description said:
...
- 19MHz to 748MHz OC kernel
...
However when I run it the default speed its using is 619? Is that normal?
hopoffbaby said:
So I don't mean to keep going on about it but when I flashed VR12 the description said:
...
- 19MHz to 748MHz OC kernel
...
However when I run it the default speed its using is 619? Is that normal?
Click to expand...
Click to collapse
Yes. Many ROMs aren't set to the highest available clock speed by default because there are phones like yours that can't handle it
I found a solution to fix the Doom kernel reboots for those who are unable to download stock roms from HTC (Rogers Customers). Requires CWM Recovery.
1. Download stock kernel here - http://www.box.com/s/7dc3bf2adc9e2f05b717
2. Unzip archive
3. Move Zip file to SD card
4. Reboot into bootloader fastboot reboot-bootloader
5. Flash the img file fastboot flash boot name.img
6. Go into CWM and install the zip.
This solved my problem, hopefully it works for you guys too.
This should work on ALL devices not just Rogers
it doesn't actually solve the kernel issues...
your just replacing him.
i still think his kernel has a lot more potential than the stock.
It fixed my issue.
I care more about having a functional tablet than a kernel that may have more potential but is buggy as hell.
i agree. and i'm running the stock as well.. just wished the doomlord one would work as well.
Hi there,
Noob user here.
I got HTC JetStream from previous owner with doomlord Kernel on it.
Tablet is constantly crashing for no logical reason which leads me to believe that the kernel is causing this issue.
I would like to flash back to the stock kernel only as my device (Rogers) is running a stock image.
I am having difficulties to follow your instructions.
Wold somebody be so kind to post more detailed process steps to complete this kernel flashing back to stock.
Thank you very much.
I had the same random reboots using Doom's kernel until i overclocked it to the maximum. It's been almost 2 weeks since i experienced any reboots....
Sent from my Inspire 4G using xda premium
could you be more specific?
did you set both the minimum and the maximum to the maximum?
did u change the voltage?
Yes I changed the min & max all the way to max.. not sure if it will have some long term effects on my tablet, but it's been working great for a while now.
Sent from my HTC PG09410 using xda premium
lol... so the "solution" to the DooM kernel reboots is to not use the DooM kernel. Brilliant.
If I find some time this weekend, I'll try maxing out the O/C though and see how it goes, as I do find the DooM kernel snappier, even at stock speeds.
craig0r said:
lol... so the "solution" to the DooM kernel reboots is to not use the DooM kernel. Brilliant.
If I find some time this weekend, I'll try maxing out the O/C though and see how it goes, as I do find the DooM kernel snappier, even at stock speeds.
Click to expand...
Click to collapse
You do realize that by doing that you are running your kernel at max speed constantly which means additional heat, stress and wear on all systems?
ATT Intruder said:
You do realize that by doing that you are running your kernel at max speed constantly which means additional heat, stress and wear on all systems?
Click to expand...
Click to collapse
No, it won't run at max speed constantly unless I set the governor to "performance" mode. In "interactive" mode, which I believe is the default, it will still clock the CPU at its minimum value until the tablet needs more CPU resources, such as when scrolling, loading a webpage, playing a game, etc.
But yes, I'm aware of the risks of overclocking. I've overclocked every HTC device I've had very few problems (my One XL has exhibited some bootloops, so I've stopped O/C'ing it.)
craig0r said:
No, it won't run at max speed constantly unless I set the governor to "performance" mode. In "interactive" mode, which I believe is the default, it will still clock the CPU at its minimum value until the tablet needs more CPU resources, such as when scrolling, loading a webpage, playing a game, etc.
But yes, I'm aware of the risks of overclocking. I've overclocked every HTC device I've had very few problems (my One XL has exhibited some bootloops, so I've stopped O/C'ing it.)
Click to expand...
Click to collapse
I'm running 1.83 ghz ondemand with also the lowest setting for the min freq setting. I will increase it to 1.944ghz ondemand as the max setting and increase my min setting to 756Mhz on deadline, and see if the reboots stop, otherwise I will have to install the stock kernal.
I am just wondering if I install the stock kernel on top of my OziMood rom, if this will cause Rom problems?
Any thoughts on this?
globalgpj said:
I'm running 1.83 ghz ondemand with also the lowest setting for the min freq setting. I will increase it to 1.944ghz ondemand as the max setting and increase my min setting to 756Mhz on deadline, and see if the reboots stop, otherwise I will have to install the stock kernal.
I am just wondering if I install the stock kernel on top of my OziMood rom, if this will cause Rom problems?
Any thoughts on this?
Click to expand...
Click to collapse
I have mine on max: 1.62 ghz , min: 594 onDemand and it hasn't crashed in two or three days. So we'll see. Now to answer your question, if you want to flash back to stock on that Rom you'll have to install the stock WiFi modules from recovery. After that everything should work normally.
AlexFG said:
I have mine on max: 1.62 ghz , min: 594 onDemand and it hasn't crashed in two or three days. So we'll see. Now to answer your question, if you want to flash back to stock on that Rom you'll have to install the stock WiFi modules from recovery. After that everything should work normally.
Click to expand...
Click to collapse
Thanks for that.
So far, I haven't had anymore reboots.
Increasing the minimum seems helpful.
I get plenty of battery life, so I am really happy about this for now.
Just a quick update.
I've been running 1.944 GHz as my high setting and 756 GHz as my low setting for some time now and I have to say, no reboots, no lag, super fast and stable.
Sent from my HTC Jetsream using xda premium
Nice, I'll try those frequencies on mine. Thanks for sharing.
Sent from my Galaxy Nexus using xda app-developers app
Hello all
I have a bit of a small problem. I like to run my phone using the Performance Governor but after a while it goes to 1Ghz on all 4 cores despite me running it at 1.8Ghz. Setting it back seems to correct the issue but in time it goes down again.
I believe it is getting a bit warm and thus it hits a limit and the system auto slows to 1Ghz.
Can anyone confirm this behaviour? It never happened to me before but I have had a few kernel updates and updates to the Omega ROM that could be the cause but I am not sure. Is there a setting where I can tell my phone what temps to throttle at?
Also, I assume all this is down to the Kernel and not the ROMs?
Would like some imput regards where to start my search to return my phone to its previous state as a pocket heater.
Many Thanks
Syl
. I like to run my phone using the Performance Governor
Click to expand...
Click to collapse
Don't use it. Pegasusq is the only one really working for multi-core CPU's with hotplugging and so on.
but after a while it goes to 1Ghz on all 4 cores despite me running it at 1.8Ghz.
Click to expand...
Click to collapse
1.8Ghz is not healthy for the CPU in the long run and will cause overheating which is exactly what you are currently seeing.
Especially since you keep the phone on 100% CPU power all the time (performance governor) which should drain battery like hell as a side effect.
Also, I assume all this is down to the Kernel and not the ROMs?
Click to expand...
Click to collapse
This is down to your settings. Neither rom nor kernel.
- Don't overclock (much)
-Use a good kernel such as Siyah
-Undervolt if the phone remains stable
-Use pegasusq Governor
-Enjoy
d4fseeker said:
Don't use it. Pegasusq is the only one really working for multi-core CPU's with hotplugging and so on.
1.8Ghz is not healthy for the CPU in the long run and will cause overheating which is exactly what you are currently seeing.
Especially since you keep the phone on 100% CPU power all the time (performance governor) which should drain battery like hell as a side effect.
This is down to your settings. Neither rom nor kernel.
- Don't overclock (much)
-Use a good kernel such as Siyah
-Undervolt if the phone remains stable
-Use pegasusq Governor
-Enjoy
Click to expand...
Click to collapse
Hi buddy and thanks for your response.
I am not sure about what you said regarding it working correctly, it gets the best results for any benchmark compared to others so I would be interested in more detail about the specifics of how its not working correctly as I have never been told that. It would be appreciated.
I dont mind the battery drain although I do heed your warning about about longevity of the CPU.
I have been using Siyah Kernel for some time now and I find undervolting a little unstable, for now I am forced to use pegasusq.
Can you or anyone else answer the original question as I still wish to pursue this to a resolve other than not using it.
Many thanks for your time and efforts non the less!
Syl
SyLvEsTeR20007 said:
Hi buddy and thanks for your response.
I am not sure about what you said regarding it working correctly, it gets the best results for any benchmark compared to others so I would be interested in more detail about the specifics of how its not working correctly as I have never been told that. It would be appreciated.
I dont mind the battery drain although I do heed your warning about about longevity of the CPU.
I have been using Siyah Kernel for some time now and I find undervolting a little unstable, for now I am forced to use pegasusq.
Can you or anyone else answer the original question as I still wish to pursue this to a resolve other than not using it.
Many thanks for your time and efforts non the less!
Syl
Click to expand...
Click to collapse
it´s samsung´s based roms related: when the battery temp hits 41C the cpu will throttle. Nothing related with de cpu temp (can be at 80C before throttles).
try CM10.1 and you´ll see what im talking about.
We need a solution for this throttling with samsung based roms
So i've rooted my sgs3 and installed siyah kernel, and today i have overclocked my cpu to 1,6 GHz and my gpu steps are 1. 160MHz, 2. 275MHz, 3. 400MHz, 4. 533MHz, 5. 640 MHz, is this safe in long terms or should i lower those values? I've ran the stress test in set cpu and it showed no errors and i havent experienced any so far, my governor is pegasusq and my scheduler is row, i just want to know what more experienced users think about the values i've set and is there any posibility that i damage my hardwer? Thank you for your response in advance
Sent from my GT-I9300 using xda app-developers app
personally think any overclock is not good thing for hardware. unless you really really need it and doesn't even care about hardware lifetime.
just like human body , if you make some sport slowly and smoothly , your muscles won't be harmed. otherwise , like you have done some sport which is very heavy, you know you will feel your whole body is ache all over in next day, or something like that.
the only different is that your body will recover itself if the damage is not too serious , but phone's hardware does NOT ...
overclocking is never 100% safe
Glebun said:
overclocking is never 100% safe
Click to expand...
Click to collapse
and you will get bad battery time - my experience...
obviously
Hello folks!
This thread is intended for sharing, please be kind. Any suggestions would be appreciated
A few days ago I was tired of having my Mi3 running on stock global dev MIUI 8, it was inefficient system with really bad memory management. On my experience, the MIUI tend to run out of memory. In some case, after a few hours of usage the system cannot reclaim the occupied RAM, thus making the system lags a lot and generate excessive heat!
Yes, MIUI is a feature-rich ROM, and the Mi ecosystem is a pretty mature ecosystem. However, those all greatness needs a lot of power to run on our 3 year old device. After a few research I decided to switch to CM13 ROM.
With efficiency in mind, I do my research and tinkering with my device to get the best setup possible without losing performance. The results are AMAZING! I can use my phone for a whole day without recharge in the mid day. All of this with huge improvement on performance, Real Racing 3 highest graphic setting without any noticeable lag! CPU and battery temperature are now significantly lower (43-47C idle / light tasks, 55-57C heavy gaming). Now that I've found the best setup, I want to share it with you folks! Here we go:
Mi3W 64GB
CM13 ROM snapshot build
CM kernel (automatically flashed while flashing CM13 zip through TWRP)
Screen resolution changed to 720x1280 use this guide
Modded interactive CPU governor (see screenshot below)
Undervolt (see screenshot below, this one really helps reduce CPU working temperature)
Noop I/O scheduler
Reduce aggresiveness of LMK (see screenshot below)
Thats all folks, hope this guide will get our Mi3 having another year of flagship-grade experience! Cheers! :highfive:
How did u undervolt
kingnikpic said:
How did u undervolt
Click to expand...
Click to collapse
It depends on the kernel used. Cm kernel that he used supports undervolt. Careful when undervolting though as too much of it can cause cpu instability and reboots.
kingnikpic said:
How did u undervolt
Click to expand...
Click to collapse
Yes, it depends on the kernel used. Some kernel support undervolting while others don't. You need to flash kernel that support undervolt.
solazz said:
It depends on the kernel used. Cm kernel that he used supports undervolt. Careful when undervolting though as too much of it can cause cpu instability and reboots.
Click to expand...
Click to collapse
While testing CPU voltage value, don't tick "apply on boot" option until you find the most stable voltage without causing system reboot or crashes. Every CPU has different limit on how far you can undervolt, but you can use the values on my screenshot as guidance (Snapdragon 801 / MSM8974-AB only)
Wow!! Thanks a lot bro. I'll fiddle now with my phone.
miui8polska，i cant root it .can you give me a supersu.zip?
Sent from my MI 4LTE using XDA Labs
Random reboot after setting undervolt just likes yours
z1d4n21 said:
Random reboot after setting undervolt just likes yours
Click to expand...
Click to collapse
Undervolting (and clock adjustment, in general) pretty much is a case-per-case basis, so different handsets (even if it's the same type of device) may have different setup. Try lowering it first incrementally and test it, until you have it stable enough.
rxl.noir said:
Undervolting (and clock adjustment, in general) pretty much is a case-per-case basis, so different handsets (even if it's the same type of device) may have different setup. Try lowering it first incrementally and test it, until you have it stable enough.
Click to expand...
Click to collapse
Ok thanks i will test it later