Related
Since CM7 already has over and underclocking abilities in the settings, I use SetCPU for profiles, particularly to lower the speed when the screen is off and not in use.
I'm wondering if this is redundant considering that Tegra 2 devices are totally different from other chipsets and if they already have some feature that lowers clock speed (or some equivalent) when not in use. Or in other terms, is there some kind of "CPU governor" (I'm aware Tegra 2 doesn't regulate like more traditional chipsets do) that when the screen is off, battery is being conserved in some way.
Anyone care to shed some light on the subject?
jamadio said:
Since CM7 already has over and underclocking abilities in the settings, I use SetCPU for profiles, particularly to lower the speed when the screen is off and not in use.
I'm wondering if this is redundant considering that Tegra 2 devices are totally different from other chipsets and if they already have some feature that lowers clock speed (or some equivalent) when not in use. Or in other terms, is there some kind of "CPU governor" (I'm aware Tegra 2 doesn't regulate like more traditional chipsets do) that when the screen is off, battery is being conserved in some way.
Anyone care to shed some light on the subject?
Click to expand...
Click to collapse
Good point!, I too would like to know more about this.
I believe anything short of ICS does not use dual core - it'd be great to POWER DOWN on of the cores.
I am not convinced screen off profiles make a huge difference. Certain tasks run when the screen is off. It is open to debate if running at a high speed and finishing the task quickly is better than running at a slower speed and taking longer to complete the task.
I did not like the lag created by screen off profiles and in call profiles so I ditched all that stuff a while back. I have better battery life now than then.
---------- Post added at 09:59 AM ---------- Previous post was at 09:57 AM ----------
namklak said:
I believe anything short of ICS does not use dual core - it'd be great to POWER DOWN on of the cores.
Click to expand...
Click to collapse
I am not sure this is 100% correct. I thought GB made use of dual cores but not to the extent the ICS can.
namklak said:
I believe anything short of ICS does not use dual core - it'd be great to POWER DOWN on of the cores.
Click to expand...
Click to collapse
Froyo and Gingerbread do, but not to a level where its a huge difference. ICS is built around dual core, so its optimized for them.
I will recommend not overclocking to 1400mhz and charging it while your about to goto sleep. Lets say that the heat didnt need to be on to warm my bedroom.
After weeks of usage, I believe I have answered my own question. I do not use SetCPU anymore because I believe it is redundant.
Doing several tests, it is clear to me that when I am not using my phone it is setting itself to the lowest CPU clock speed. Even when the screen is on and I'm using a non-CPU-extensive app, it'll lower itself to 216 Mhz (my lowest clock speed).
Both my wife and I have VZW galaxy s3, mine is rooted and I have an extended battery, hers is stock. My battery, however, drains insanely fast, with very little usage. I installed the app 'cool tool' (monitors cpu usage/frequency) on both of our phones, and noticed that while hers changes from 200-384-1512MHz constantly, mine is locked on 1512MHz. First of all, why is mine locked on 1512 MHz? Secondly, could this be what is draining my battery so rapidly?
Thanks.
Yes, that is why your batt is draining quickly. If your CPU tool can't tell you what app is using the most CPU then find another that will (I use System Panel). So, causes...It could be an app or it could be something you have done to your phone.
Have you used SETCPU or some other CPU setting app to change your CPU governor and/or min/max clock rate? If your governor is set at "Performance" that will lock your CPU rate to max.
Are you running a non-stock ROM? If the ROM has CPU/governor settings, did you mess with them?
If it is an app, a good CPU monitor app will tell you which one and then you can get rid of it.
---------- Post added at 09:02 AM ---------- Previous post was at 08:53 AM ----------
Oh, and you can also go to Settings...Battery and see what is using a lot of battery.
Only for i9505.
Hey guys!
I've been experimenting a lot with my S4 and I figured out why many games lag...
The reason is that my gpu clock drops from max clock I set, to 320mhz once the temperature reaches 68C!
Some may say, this doesn't happen because the gpu doesn't thermal throttle on the S4 like on the HTC One...
Well...I used performance governor which is supposed to keep the gpu clock to the max at all times, and guess what?
When the temperature reached 68C my gpu clock went down to 320mhz even with performance governor!
How is that possible...?
Performance governor can't throttle down!
Thermal throttling is to blame. (or something else, that doesn't care about governors? )
It's not a coincidence this happened at exactly 68C like before.
(If anyone wants to argue with me about this I'd appreciate if he/she doesn't spam my thread for the love of god and pm me.)
Anyway, enough with the prologue..
This was a royal pain in the ass for me because I almost regret selling my silky smooth S3.
After tons of random searching and messing with the system of my phone I found the solution!
Here it is!
Sell your S4!
Nah, I'm just joking!
It's a great phone.
Here's the real solution:
I set
/sys/devices/platform/kgsl-3d0.0/kgsl/kgsl-3d0/min_pwrlevel
to 0 out of curiosity, which controls the lowest power level, or clock, that the gpu will use.
By default it's set at 4.
Since max was already 0 which means it's the highest value I set min to 0 too, and guess what?
The gpu clock remained at my set max, 504mhz, all the time, even after 68C!
Tried three games I know this problem happened and all three worked at 504mhz!
(for pure information, it was Modern Combat 4, Gangstar, and Asphalt 8)
How can you try it?
I've attached two scripts, one that sets the value to 0 and uses max gpu frequency all the time and one that sets the value to 4 so that the gpu can use the lower clock states again!
For Script Manager Users, free
Use script manager as root to run these widgets and I'd recommend you put two widgets on the home screen!
One for the first script enabling this tweak, and one for the second that disables it.
For Tasker Users, need to pay
If you have tasker you could use it too and set it to run the content of the first script as root at every heavy game and enable the tweak automatically, after that use tasker again to run the content of the second script when you go to your home screen (or anything else you want to set) and disable the tweak automatically!
Beware!I will not responsible if you damage your hardware!
Recommended prerequisites:
- Custom kernel preferably ktoonsez's or ausdim's, but any kernel with undervolt and thermal throttling control support will do.
Increased heat may be produced after doing this, so I recommend you to undervolt at least a little to reduce the overall heat, plus increase the thermal throttling limits too to prevent the cpu throttling down.
I use 85 as start limit and 82 as stop limit but you don't have to use my values.
I just find them safe enough and high enough so that they don't interfere with my games.
Try it and report back, many games are way smoother now, at least for me.
I'll be waiting for your results!
Have a nice day guys!
P.S. If you need to tune even more your device, take a look at my personal settings found here:
http://forum.xda-developers.com/showpost.php?p=45103847&postcount=1106
The gaming profiles are set at 1242mhz min now, not 1458mhz like before, because the gpu clocks work properly now the cpu doesn't need that much boost to avoid lag.
And the gpu clock I use now is 504mhz instead of the stock 450mhz in the link.
That's it!
You said that the gpu clock remained at my set max, 504mhz, all the time, even after 68C, but you didn't say how hot it got.
Did it get hotter than that? I'm a bit wary of frying the board to squeeze out a few extra frames on my device, but that's just me.
Haw much does it take you to reach 68° ? I have the 9500 version and i didnt face that problem yet.. it s going warm but doesnt lag
Envoyé depuis mon GT-I9500 en utilisant Tapatalk 4
donalgodon said:
You said that the gpu clock remained at my set max, 504mhz, all the time, even after 68C, but you didn't say how hot it got.
Did it get hotter than that? I'm a bit wary of frying the board to squeeze out a few extra frames on my device, but that's just me.
Click to expand...
Click to collapse
You won't don't worry.
Both the cpu and gpu have a tolerance up to 100C, plus the system automatically shuts down before reaching critical high temperature.
For me it didn't get much hotter, only a few degrees.
You can monitor the frequencies and temperature with the Qualcomm Trepn Profiler which is an advanced free monitoring app for Qualcomm devices:
https://developer.qualcomm.com/mobile-development/performance-tools/trepn-profiler
or
you can use this app by senior member @rlorange which is much simpler and gets the job done just right:
http://forum.xda-developers.com/showpost.php?p=44953638&postcount=3547
3ayachi said:
Haw much does it take you to reach 68° ? I have the 9500 version and i didnt face that problem yet.. it s going warm but doesnt lag
Envoyé depuis mon GT-I9500 en utilisant Tapatalk 4
Click to expand...
Click to collapse
Sorry but this is not for the i9500, this is the first thing I wrote.
I don't even know if this happens on your device mate.
Anyway, it doesn't take much, play a heavy game for a few minutes an you'll reach 68C.
Updated link with my settings, now it's correct.
Sorry about that.
Is it possible to change this value without a reboot ? Like in a small app for example ?
Hey buddy...juz chk yu are having any thermald file under /system/etc...??
thanks mate!! It's working perfectly
So this won't work with a rooted s4 on stock rom and kernel?
If not I'm returning my phone. I played vice city today and the lag was terrible. I've only had this phone for two days and I'm dissatisfied with verizon and samsung for gimping it and then locking it down.
imo, companies advertising the power of their chips is false advertising when they set temperature throttle so low
crazysoccerman said:
So this won't work with a rooted s4 on stock rom and kernel?
If not I'm returning my phone. I played vice city today and the lag was terrible. I've only had this phone for two days and I'm dissatisfied with verizon and samsung for gimping it and then locking it down.
imo, companies advertising the power of their chips is false advertising when they set temperature throttle so low
Click to expand...
Click to collapse
No mate, I'm sorry.
But good news is Samsung WILL fix your phone no matter knox 0x0 or 0x1.
(confirmed)
So flash your device and try again!
I must agree, companies are full of crap when advertising their products, it's so furstrating!
This throttling issue happens with any device, including iDevices.
Bootloader is locked. Most likely forever.
Don't have MDK so I cant loki.
Even with safestrap (which doesn't work for my MJ7) you can't flash custom kernels.
This phone is going back :good:
I'm going back to my trusty gnex for now. It would probably play GTA better at s4 resolution because I overclocked it and disabled thermal throttling.
Maybe I'll get a g2 with loki support...
Either way, I would like to give a Linus Torvalds Salute™ to samsung and verizon.
Too bad. :/
Wait for some exynos device or anyone with custom cpu/gpu because qualcomm imho isn't good enough.
I got this to work on my s4. Are there similar settings I can modify to prevent cpu throttling?
Edit: cpu throttling settings exist. But it wasn't throttling... it was changing governer and minimum frequency.
I set the governer to performance with root explorer and it's working perfectly.
Thanks op for the location of the gpu settings. There was no way I would have found it without your post.
I've tested it (works fine) but I have the feeling that somehow the phone is too warm
crazysoccerman said:
I got this to work on my s4. Are there similar settings I can modify to prevent cpu throttling?
Edit: cpu throttling settings exist. But it wasn't throttling... it was changing governer and minimum frequency.
I set the governer to performance with root explorer and it's working perfectly.
Thanks op for the location of the gpu settings. There was no way I would have found it without your post.
Click to expand...
Click to collapse
btmz said:
I've tested it (works fine) but I have the feeling that somehow the phone is too warm
Click to expand...
Click to collapse
Glad it worked guys!
Well, the temperature will definitely increase because of the increased gpu clock speed, but as long as cpu throttling temp is <=85 you should be fine.
That's what I've been searching for all day, I knew this device can handle those games, but the random stuttering was painful.
It lowers the GPU to 128 MHz, I measured that when I played Apshalt 8 and got my TricksterMod set in background. When the game dropped massive FPS I switched to Trickster and saw that the GPU is running 128 MHz, shocking. Ktoon's kernel has a touch boost which works nicely but Asphalt 8 is a racing game that uses the sensors to steer and so I did not touch my screen so often and I need that.
You sir deserve a medal.
GlossGhost said:
That's what I've been searching for all day, I knew this device can handle those games, but the random stuttering was painful.
It lowers the GPU to 128 MHz, I measured that when I played Apshalt 8 and got my TricksterMod set in background. When the game dropped massive FPS I switched to Trickster and saw that the GPU is running 128 MHz, shocking. Ktoon's kernel has a touch boost which works nicely but Asphalt 8 is a racing game that uses the sensors to steer and so I did not touch my screen so often and I need that.
You sir deserve a medal.
Click to expand...
Click to collapse
Thanks man!
I knew something was off the minute I started playing modern combat 3 and saw the same performance as my S3.
I researched quite a bit and found this in the end.
I even got in an argument with a guy at ausdim's kernel thread about this because he was saying I was talking nonsense and he wanted proof in order to believe me.
Well, here it is.
nfsmw_gr said:
Thanks man!
I knew something was off the minute I started playing modern combat 3 and saw the same performance as my S3.
I researched quite a bit and found this in the end.
I even got in an argument with a guy at ausdim's kernel thread about this because he was saying I was talking nonsense and he wanted proof in order to believe me.
Well, here it is.
Click to expand...
Click to collapse
Ah, yeah no one can say to me that the games run buttery smooth without any modification.
A game does not run smooth on 128 MHz.
And all those amateur reboot your device and etc... They are complete nonsense.
I want ask a thing before flashing... Is this only an unlock and gpu scales the frequencies as it needs or I have always gpu freq at max on depending on what I'm doing? I hope this only unlock the max frequency otherwise became e battery drainer hack! Tell me guy!
From universe with my gs4 snapdragon powered!
will try it, nice work!
Hi,
I've just install Mahdi ROM 2.7 with Franco Kernel r63. Then I overclock CPU frequency with TrickesterMOD app and I change frequency to 3 Ghz, device reboots immediately , so change it to 2.88 again reboots but when I put frequency on 2.8 it works good without problem. I play with device , get benchmark and it works normally. But after a few hours I see a small dead pixel on my screen as you see in attachment!! Can this happen because of overclocking or that several reboots?! and is there any way to fix this dead pixels?
Shouldn't do.
Sent from my Nexus 5 using Tapatalk
rootSU said:
Shouldn't do.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Sorry I misunderstood! you mean I Shouldn't do overclock or overclock Shouldn't do this with pixels?
Creative9170 said:
Sorry I misunderstood! you mean I Shouldn't do overclock or overclock Shouldn't do this with pixels?
Click to expand...
Click to collapse
I can't think of any way that overclock could cause dead pixels.
Sent from my Nexus 5 using Tapatalk
rootSU said:
I can't think of any way that overclock could cause dead pixels.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks for reply, Yes its also strange to me that overclock cause dead pixel! I also didn't find any person that has dead pixel because of overclock! I tried several ways include pressure and using app to fix it with no luck, do you know any ways that can fix dead pixel?
dead pixels i cant fix, but if you want to overclock higher, then play with your voltages for those cpu speeds. adjust them slightly up or down, to get higher cpu speeds stable.
Dead pixels cant be restored, just stuck pixels. Im pretty sure it was there, you just noticed it now. I noticed mine a month after i had bought it.
rootSU said:
I can't think of any way that overclock could cause dead pixels.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
If the CPU gets hot enough you could theoretically cause heat damage to the LCD which could appear like in his image. What he has isn't a "proper" dead pixel (ie, control-board based) since the damage runs over into the nearby pixels and isn't entirely covering one pixel. It looks more like what you see from physical or heat damage to a display.
raptir said:
If the CPU gets hot enough you could theoretically cause heat damage to the LCD which could appear like in his image. What he has isn't a "proper" dead pixel (ie, control-board based) since the damage runs over into the nearby pixels and isn't entirely covering one pixel. It looks more like what you see from physical or heat damage to a display.
Click to expand...
Click to collapse
True but throttling shouldn't let it get anywhere near the temperatures required for heat damage.
Sent from my Nexus 5 using Tapatalk
simms22 said:
dead pixels i cant fix, but if you want to overclock higher, then play with your voltages for those cpu speeds. adjust them slightly up or down, to get higher cpu speeds stable.
Click to expand...
Click to collapse
So If I do this until I find stable voltage device will reboot again and again, can these reboots harm device?
iSplassh said:
Dead pixels cant be restored, just stuck pixels. Im pretty sure it was there, you just noticed it now. I noticed mine a month after i had bought it.
Click to expand...
Click to collapse
Did you send phone for warranty and did they change it for you?
raptir said:
If the CPU gets hot enough you could theoretically cause heat damage to the LCD which could appear like in his image. What he has isn't a "proper" dead pixel (ie, control-board based) since the damage runs over into the nearby pixels and isn't entirely covering one pixel. It looks more like what you see from physical or heat damage to a display.
Click to expand...
Click to collapse
While I'm using device the upper part of device and LCD is hot and it means CPU locates in upper part of device, but this dead pixel is near nav bar buttons! As I compare this small black dot of dead pixel its smaller than last night! does it mean that device is fixing itself?!!
Creative9170 said:
So If I do this until I find stable voltage device will reboot again and again, can these reboots harm device?
Did you send phone for warranty and did they change it for you?
While I'm using device the upper part of device and LCD is hot and it means CPU locates in upper part of device, but this dead pixel is near nav bar buttons! As I compare this small black dot of dead pixel its smaller than last night! does it mean that device is fixing itself?!!
Click to expand...
Click to collapse
na, wont hurt your device. i cant tell you how many times ive done it to my device, hundred? and im one of the few that can run 3014mhz stable. the worst that will happen is a reboot. about the heat, your device doesnt get hot enough with no use when ocing to do any kind of damage. when you do use your cpu heavily, first itll slow down the cpu speed when reaching a certain temp, then if your device still keeps getting warmer, itll hit the safety shutdown temp of 105C and just turn itself off.
I didn't bought the phone for google play, i bought it from a reseller in my country. So i must live with that dead pixel
simms22 said:
na, wont hurt your device. i cant tell you how many times ive done it to my device, hundred? and im one of the few that can run 3014mhz stable. the worst that will happen is a reboot. about the heat, your device doesnt get hot enough with no use when ocing to do any kind of damage. when you do use your cpu heavily, first itll slow down the cpu speed when reaching a certain temp, then if your device still keeps getting warmer, itll hit the safety shutdown temp of 105C and just turn itself off.
Click to expand...
Click to collapse
Thanks for reply I'm worry about giving higher voltage to CPU!! Because now its on 1150 for 2880mhz, I change it to 1225 but still reboots! Now I'm worry about using higher voltage! Where I can find how much higher voltage this CPU can handle?!
iSplassh said:
I didn't bought the phone for google play, i bought it from a reseller in my country. So i must live with that dead pixel
Click to expand...
Click to collapse
Yes, same here! I can also live with this small black dot!
Creative9170 said:
Thanks for reply I'm worry about giving higher voltage to CPU!! Because now its on 1150 for 2880mhz, I change it to 1225 but still reboots! Now I'm worry about using higher voltage! Where I can find how much higher voltage this CPU can handle?!
Yes, same here! I can also live with this small black dot!
Click to expand...
Click to collapse
every phone is different and needs different voltages. your phones bin number will help. as higher binned numbers need less voltage. try going down slightly in voltage as well, not just up. anyways, your voltages should be all under 1200mV, for me 3014mhz is stable at 1150mV. and my phone is a 3(bin).
---------- Post added at 02:33 PM ---------- Previous post was at 02:31 PM ----------
when adjusting voltage, adjust by 5 or 10mV at a time, up and down.
simms22 said:
every phone is different and needs different voltages. your phones bin number will help. as higher binned numbers need less voltage. try going down slightly in voltage as well, not just up. anyways, your voltages should be all under 1200mV, for me 3014mhz is stable at 1150mV. and my phone is a 3(bin).
---------- Post added at 02:33 PM ---------- Previous post was at 02:31 PM ----------
when adjusting voltage, adjust by 5 or 10mV at a time, up and down.
Click to expand...
Click to collapse
My Phone bin is 2 and I think this is the reason that I can't reach even 2.88mhz with 1150mV! :|
Creative9170 said:
My Phone bin is 2 and I think this is the reason that I can't reach even 2.88mhz with 1150mV! :|
Click to expand...
Click to collapse
try 1160-1190mV. some phones wont be able to run 3014mhz no matter what.
simms22 said:
try 1160-1190mV. some phones wont be able to run 3014mhz no matter what.
Click to expand...
Click to collapse
Mine doesn't like 2.7
Sent from my Nexus 5 using Tapatalk
Creative9170 said:
My Phone bin is 2 and I think this is the reason that I can't reach even 2.88mhz with 1150mV! :|
Click to expand...
Click to collapse
i know bin 0 and 1 phones that run at 3014mhz for a certain period of time. binning only has to do with your voltages and thats all. they dont say anything about how the device performs.
---------- Post added at 03:13 PM ---------- Previous post was at 03:11 PM ----------
rootSU said:
Mine doesn't like 2.7
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
mine really likes 2880mhz.. and at 2880/300, battery isnt that far off 2265/300.
You should get the screen replaced and check if dead pixels are still there...
dead pixel in nexus5
Hello everyone I have nexus 5 in my nexus ,there is very Small dead pixel on display.before 34 day of purchasing phone I seen that, I don't want that very small black point. What can I do..
Is Lg customer care services replaced or repaired that small pixel??? Any one any idea plz suggest me
Must be rooted.
Install kernel adiutor.
Start Kernel Adiutor. You'll be met immediately with four graphs showing the load on all four cores.
Select "CPU"
What you will notice by looking at the CPU frequency graphs, is that the head unit spends most of it's time at a low clock frequency, typically 800MHz or so.
Select "governor". The default setting is probably "interactive". This is not a phone. Any governor setting that favors low energy consumption is not appropriate for an automotive head unit. The kernel governor's job is to throttle the clock speed up or down to meet demand. So when the device isn't doing anything, it can run at a lower speed and conserve battery.
Scroll down to and select "performance". This will lock the CPU at 1.6GHz.
Use the "apply on boot" switch to make kernel adiutor start up and apply the setting at every boot.
You will notice dramatically improved responsiveness (immediately) overall.
This should also work with MTCB units or other (non-Joying) units. You must be rooted.
If someone can provide screenshots of the CPU frequency graphs (before/after) I will add them. I am too lazy to run mine in the old state just for getting a picture of before/after, but in a couple of days I will try to add some pictures.
I don't know if the chip will eventually burn up. If it was designed properly, it won't. The Rockchip is used in millions of tablets and other devices, I suspect it is robust by now. It is also advertised on Joying's website as a 1.6GHz quad core, so why is it running at 800 MHz or lower all the time?
There may be a tradeoff, perhaps using ondemand? Would be worth playing around with the other governors and settings to find a way to get max speed only when it is needed. But then again, there may not be any reason to mess with this at all.
This is *not* overclocking and the kernel governor is not a secret. The performance governor will force the processor to run at its maximum advertised speed. I have been running mine this way for >1 week now with no ill effects.
Following these instructions is at your own risk, like almost everything on XDA.
@da_anton
wskelly said:
Must be rooted.
Install kernel adiutor.
Start Kernel Adiutor. You'll be met immediately with four graphs showing the load on all four cores.
Select "CPU"
What you will notice by looking at the CPU frequency graphs, is that the head unit spends most of it's time at a low clock frequency, typically 800MHz or so.
Select "governor". The default setting is probably "interactive". This is not a phone. Any governor setting that favors low energy consumption is not appropriate for an automotive head unit. The kernel governor's job is to throttle the clock speed up or down to meet demand. So when the device isn't doing anything, it can run at a lower speed and conserve battery.
Scroll down to and select "performance". This will lock the CPU at 1.6GHz.
Use the "apply on boot" switch to make kernel adiutor start up and apply the setting at every boot.
You will notice dramatically improved responsiveness (immediately) overall.
This should also work with MTCB units or other (non-Joying) units. You must be rooted.
If someone can provide screenshots of the CPU frequency graphs (before/after) I will add them. I am too lazy to run mine in the old state just for getting a picture of before/after, but in a couple of days I will try to add some pictures.
I don't know if the chip will eventually burn up. If it was designed properly, it won't. The Rockchip is used in millions of tablets and other devices, I suspect it is robust by now. It is also advertised on Joying's website as a 1.6GHz quad core, so why is it running at 800 MHz or lower all the time?
There may be a tradeoff, perhaps using ondemand? Would be worth playing around with the other governors and settings to find a way to get max speed only when it is needed. But then again, there may not be any reason to mess with this at all.
This is *not* overclocking and the kernel governor is not a secret. The performance governor will force the processor to run at its maximum advertised speed. I have been running mine this way for >1 week now with no ill effects.
Following these instructions is at your own risk, like almost everything on XDA.
Click to expand...
Click to collapse
There is already a thread here on xda discussing this. Actually that thread started at that time discussing if some sort of overclocking is possible. I'm not so sure if setting the soc to performance Governor and therefore always 1,6 GHz is a good idea. I agree with you that it definitely is an improvement and the unit feels more responsive. But as there is no heat spreader on the soc and the cooling is not very good where the unit is usually placed I'm not so sure if this does not reduce the lifetime or even kills it as someone said that the Rk3188 has no temp management.
I would instead recommend to try tuning the interactive Governor settings instead. The default settings almost never scales up to 1,6 ghz as you found out. But if you set the following two tunables with kernel audiutor the soc will scale up to max as soon as 60 percent load occurs on a core. This at least improved my unit while still keeping the advantages of dynamic frequency scaling. Here are the two variables
/sys/devices/system/cpu/cpufreq/interactive/go_hispeed_load 60
/sys/devices/system/cpu/cpufreq/interactive/hispeed_freq 1608000
I already did some programming to set this variables as early as possible in the boot process without the need of kernel audiutor. But so far it is only active on my unit.
da_anton said:
There is already a thread here on xda discussing this. Actually that thread started at that time discussing if some sort of overclocking is possible. I'm not so sure if setting the soc to performance Governor and therefore always 1,6 GHz is a good idea. I agree with you that it definitely is an improvement and the unit feels more responsive. But as there is no heat spreader on the soc and the cooling is not very good where the unit is usually placed I'm not so sure if this does not reduce the lifetime or even kills it as someone said that the Rk3188 has no temp management.
I would instead recommend to try tuning the interactive Governor settings instead. The default settings almost never scales up to 1,6 ghz as you found out. But if you set the following two tunables with kernel audiutor the soc will scale up to max as soon as 60 percent load occurs on a core. This at least improved my unit while still keeping the advantages of dynamic frequency scaling. Here are the two variables
/sys/devices/system/cpu/cpufreq/interactive/go_hispeed_load 60
/sys/devices/system/cpu/cpufreq/interactive/hispeed_freq 1608000
I already did some programming to set this variables as early as possible in the boot process without the need of kernel audiutor. But so far it is only active on my unit.
Click to expand...
Click to collapse
I am willing to try this ROM out if can post it,
SirOrigami said:
I am willing to try this ROM out if can post it,
Click to expand...
Click to collapse
As you already posted in the ROM builder thread: do you know how to build a ROM with that tool by yourself? Because the code is already on github but disabled.
If not I build you a new one this evening.
da_anton said:
As you already posted in the ROM builder thread: do you know how to build a ROM with that tool by yourself? Because the code is already on github but disabled.
If not I build you a new one this evening.
Click to expand...
Click to collapse
Yeah I do. But I am not really friendly with the choices, and what I Must include and what not.
SirOrigami said:
Yeah I do. But I am not really friendly with the choices, and what I Must include and what not.
Click to expand...
Click to collapse
OK, I'll build you one
Someone around here was discussing possible heat problems on these rockchip units, being why the manufacturer chooses to set the CPU governor this way.
I don't know if this tweak is really advisable unless you add hardware mod like passive heatsink or fan to the chip. I couldn't find any temperature data or sensors from the chip.
da_anton said:
There is already a thread here on xda discussing this. Actually that thread started at that time discussing if some sort of overclocking is possible. I'm not so sure if setting the soc to performance Governor and therefore always 1,6 GHz is a good idea. I agree with you that it definitely is an improvement and the unit feels more responsive. But as there is no heat spreader on the soc and the cooling is not very good where the unit is usually placed I'm not so sure if this does not reduce the lifetime or even kills it as someone said that the Rk3188 has no temp management.
I would instead recommend to try tuning the interactive Governor settings instead. The default settings almost never scales up to 1,6 ghz as you found out. But if you set the following two tunables with kernel audiutor the soc will scale up to max as soon as 60 percent load occurs on a core. This at least improved my unit while still keeping the advantages of dynamic frequency scaling. Here are the two variables
/sys/devices/system/cpu/cpufreq/interactive/go_hispeed_load 60
/sys/devices/system/cpu/cpufreq/interactive/hispeed_freq 1608000
I already did some programming to set this variables as early as possible in the boot process without the need of kernel audiutor. But so far it is only active on my unit.
Click to expand...
Click to collapse
Thanks for the info, didn't know about the other thread.
I wonder if... They just forgot? Has anyone actually experienced a thermal. failure? Is there a data sheet for this thing? The Rockchip is by nature a low power device and they made a design decision not to include thermal management (or even temperature measurement?) ... To me it all points to "should be fine" but your solution is definitely more conservative/safer.
I have an infrared temp gun, but I need to pull apart the dash again, disassemble the unit, remove the DVD transport, and then drive around like that taking measurements... Probably not going to happen.
I did see some photos where a guy added some heatsinks...? On the Joying website maybe?
Sent from my Moto G using Tapatalk
wskelly said:
I did see some photos where a guy added some heatsinks...? On the Joying website maybe?
Click to expand...
Click to collapse
I don't know about the Joying website. But ptclabs and I did this and we posted it here: http://forum.xda-developers.com/showpost.php?p=68899885&postcount=22
As I have a heatsink on my SoC I don't mind having it at 1,6Ghz most of the time. But publishing this for everybody as part of a public ROM is maybe not a good idea without being able to measure the CPU temp. That RT3188 is really a cheap piece of electronics.
I don't think you have to drive around to measure this. I guess you could just use a generic 12V power supply and power the unit on your desk. The correct wiring should be written on the unit. Then you can just use any CPU burn app from the Play Store and measure the temp of the SoC with your infrared thermometer. Would definitely be a nice project!
Those of you interested in doing this, I'd recommend you taking a look at this thread regarding overheating:
http://forum.xda-developers.com/and...overclock-mtcd-mtcb-rk3188-quad-core-t3462513
ptclabs said:
being 3188 do not have a temp sensor. none. It will run till it burns or errors out
Click to expand...
Click to collapse
Good to see people steal other members information then try to hide it in another thread....
http://forum.xda-developers.com/and...5-1-1-mtcb-t3394209/post68721156#post68721156
So been working to make this ROM a bit faster. I changed the boot animations to the stock Audi one and shaved 5 seconds off boot. Then I went into developer options and turned off the animations. If you want the transition 0.5x works great too. Next I deleted all the launchers I wasn't using since they have a startup at boot. Now I got a little more in depth. I installed Kernal Adiutor (ROOT) and watched the CPU. I ran a bunch of programs in the background, starting maps, changing menus and noticed the CPU rarely went above 816 Mhz. So I went to adjust the Governor. The performance CPU Governor made everything snappy but running the 1.6 Ghz constantly can't be good for the CPU. I went back to Interactive and adjusted hispeed_freq to the maximum 1.6Ghz and go_hispeed_load to 80% (was originally 96% so 1.6 Ghz would never come on) Finally opening apps would trigger the 1.6 Ghz but it would still go down to the minimum even with Here weGo Maps. I didn't want to mess with the other settings cause I don't quite understand it well. If someone here know how to tweak this CPU more please let me know!!
Everything you need to know about Governors http://forum.xda-developers.com/gene...ors-o-t3048957
---------- Post added at 03:47 PM ---------- Previous post was at 03:45 PM ----------
DO NOT LOCK YOUR CPU ON MAX SPEED. YOU WILL BURN YOUR STEREO UP. Read my research above to speed up your system, without burning up the CPU. Been running those setting for a month.
shawndak said:
Good to see people steal other members information then try to hide it in another thread....
http://forum.xda-developers.com/and...5-1-1-mtcb-t3394209/post68721156#post68721156
So been working to make this ROM a bit faster. I changed the boot animations to the stock Audi one and shaved 5 seconds off boot. Then I went into developer options and turned off the animations. If you want the transition 0.5x works great too. Next I deleted all the launchers I wasn't using since they have a startup at boot. Now I got a little more in depth. I installed Kernal Adiutor (ROOT) and watched the CPU. I ran a bunch of programs in the background, starting maps, changing menus and noticed the CPU rarely went above 816 Mhz. So I went to adjust the Governor. The performance CPU Governor made everything snappy but running the 1.6 Ghz constantly can't be good for the CPU. I went back to Interactive and adjusted hispeed_freq to the maximum 1.6Ghz and go_hispeed_load to 80% (was originally 96% so 1.6 Ghz would never come on) Finally opening apps would trigger the 1.6 Ghz but it would still go down to the minimum even with Here weGo Maps. I didn't want to mess with the other settings cause I don't quite understand it well. If someone here know how to tweak this CPU more please let me know!!
Everything you need to know about Governors http://forum.xda-developers.com/gene...ors-o-t3048957
---------- Post added at 03:47 PM ---------- Previous post was at 03:45 PM ----------
DO NOT LOCK YOUR CPU ON MAX SPEED. YOU WILL BURN YOUR STEREO UP. Read my research above to speed up your system, without burning up the CPU. Been running those setting for a month.
Click to expand...
Click to collapse
I haven't stolen anything! My MTCD unit is my first unit at all of this kind and I have never seen your post/thread or any other post before regarding the governors on MTCx units. Believe it or not but I've spent hours in my garage playing with the governors. I deeply apologize if it looks like anything has been stolen from you.
da_anton said:
I haven't stolen anything! My MTCD unit is my first unit at all of this kind and I have never seen your post/thread or any other post before regarding the governors. Believe it or not but I've spent ours in my garage playing with the governors. I deeply apologize if it looks like anything has been stolen from you.
Click to expand...
Click to collapse
Keep doing what you are doing!
[/COLOR]
da_anton said:
I haven't stolen anything! My MTCD unit is my first unit at all of this kind and I have never seen your post/thread or any other post before regarding the governors on MTCx units. Believe it or not but I've spent hours in my garage playing with the governors. I deeply apologize if it looks like anything has been stolen from you.
Click to expand...
Click to collapse
Talking about the person who started this thread WSKELLY, unless you two are the same person. I find it hard to believe, out of the 1000's of cpu governor apps, the same one I listed had been chosen.
shawndak said:
Good to see people steal other members information then try to hide it in another thread....
http://forum.xda-developers.com/and...5-1-1-mtcb-t3394209/post68721156#post68721156
So been working to make this ROM a bit faster. I changed the boot animations to the stock Audi one and shaved 5 seconds off boot. Then I went into developer options and turned off the animations. If you want the transition 0.5x works great too. Next I deleted all the launchers I wasn't using since they have a startup at boot. Now I got a little more in depth. I installed Kernal Adiutor (ROOT) and watched the CPU. I ran a bunch of programs in the background, starting maps, changing menus and noticed the CPU rarely went above 816 Mhz. So I went to adjust the Governor. The performance CPU Governor made everything snappy but running the 1.6 Ghz constantly can't be good for the CPU. I went back to Interactive and adjusted hispeed_freq to the maximum 1.6Ghz and go_hispeed_load to 80% (was originally 96% so 1.6 Ghz would never come on) Finally opening apps would trigger the 1.6 Ghz but it would still go down to the minimum even with Here weGo Maps. I didn't want to mess with the other settings cause I don't quite understand it well. If someone here know how to tweak this CPU more please let me know!!
Everything you need to know about Governors http://forum.xda-developers.com/gene...ors-o-t3048957
---------- Post added at 03:47 PM ---------- Previous post was at 03:45 PM ----------
DO NOT LOCK YOUR CPU ON MAX SPEED. YOU WILL BURN YOUR STEREO UP. Read my research above to speed up your system, without burning up the CPU. Been running those setting for a month.
Click to expand...
Click to collapse
Can you be sure? I missed your post too as helpful as it is.
marchnz said:
Can you be sure? I missed your post too as helpful as it is.
Click to expand...
Click to collapse
Only person that can be sure is the thread starter. Of course we both could have stumbled upon the same idea to speed up a laggy system with a background of CPU governor work. We would then set out to pick the exact same program to set the governor. Just seems odd to me.
Anyways hope my governor adjustments suite y'all. Would highly recommend not running the CPU at max capacity especially when cars can easily get to 150 + in the summer. My xtrons unit has a fan and very large heat sink and I'm still nervous about it.
shawndak said:
Only person that can be sure is the thread starter. Of course we both could have stumbled upon the same idea to speed up a laggy system with a background of CPU governor work. We would then set out to pick the exact same program to set the governor. Just seems odd to me.
Anyways hope my governor adjustments suite y'all. Would highly recommend not running the CPU at max capacity especially when cars can easily get to 150 + in the summer. My xtrons unit has a fan and very large heat sink and I'm still nervous about it.
Click to expand...
Click to collapse
Actually I did exactly that about 2 weeks before this thread was created... It's the most logical thing to do for a noob...go into playstore, type kernel and this app is first result. Go in the app, scroll the options and obviously "performance" sounds promising... Very ordinary I think
Reminds me I need to add on a heatsink to the RK3188 in my unit. It couldn't hurt.
Mighty_X said:
Actually I did exactly that about 2 weeks before this thread was created... It's the most logical thing to do for a noob...go into playstore, type kernel and this app is first result. Go in the app, scroll the options and obviously "performance" sounds promising... Very ordinary I think
Click to expand...
Click to collapse
Thats what i did also.