I have done some research into it and contacted nvidia support and got them to confirm that setting a limit to the CPU speed does not currently work, they claim it will be fixed in a future update. I tried to fix it myself but I can't seem to figure out how to get settings in files to stick on boot, some script files seem to be changing the settings on every boot so i can't get get any changes to take place (though I know where the settings are found for each of the profiles, optimized battery saving and max performance)
That makes sense... No wonder why the battery drained equally no matter what..
if you have root though it seems like trickster mod works to limit the CPU speed
Related
I've found this neat tool: http://www.nuerom.com/BlogEngine/page/nueDynamicClock.aspx
Has anyone used this on their X1 and did you notice any changes? I don't think you can use it for overclocking an X1. But I'm thinking about setting clock frequency to 19 MHz on Suspend, to get more out of my battery.
I've got this tool, not sure if it made much of a diff when I overclocked it to 528
( or just set it to the base clock speed since they have it underclocked @ 400 mhz ), wanna try the lower speeds, but not sure whether it will have a negative effect.
I uninstalled it..
found that any apps (such as gps cycle computer, audiomanager etc) that played with the screen on didn't work very well when the speed was lowered. Also had quite a lot of instances when the screen was corrupted after coming out of suspend..
I use it since yesterday, so i can't say anything about changed battery lifetime. But i got it working only after setting min-clock to 384MHz. With lower settings the phone got frozen in standby mode after a while. I'll try it for a few days for testing a (hopefully) enhanced standby time...
PS: i use 384MHz in suspend mode and after idle time of 5s, didn't change max clock or voltage settings (all to "auto"). Maybe setting idle time to 2s would care more battery life, but i don't know how the cpu will stand changing the clock so much often...
Been using it since v1.0. Seems to have some battery gain (10% over 8 hours better) - set to default 528MHz, down to 256MHz idle and 122.98MHz on suspend and screen off. Needed 123MHz for clean audio playback in standby.
Only screen corruption (inversion) issues I had was when set too low (19MHz) at standby. Now using these settings for a few days and no issues so recommended for use with TFlo3D2.
Unless you're running WM6.5 with WM7 titanium - makes it very slow to respond out of standby.
And it doesn't overclock - 528MHz is default clock speed.
I wanted to try this but my X1 says no, here is the screen shot, due to security, I press yes and my X1 does a soft reset, then I try the program again and get the same thing.
View attachment 180763
Has anyone with a standard Official Rom 2 got this to work, and how ?
Mark A Cilenti said:
I wanted to try this but my X1 says no, here is the screen shot, due to security, I press yes and my X1 does a soft reset, then I try the program again and get the same thing.
View attachment 180763
Has anyone with a standard Official Rom 2 got this to work, and how ?
Click to expand...
Click to collapse
I have a standard R2A ROM and it works for me. Can't tell you what's the problem with your installation, though.
Anyway, I found since I installed the tool my device is worse than before. It sometimes interrupts audio playback when display is off (ALthough frequency in that case is still at 3xx MHz!) and sometimes it takes very long (5 secs +) to suspend and to wake up again. So I think I'm gonna remove it.
I only turned down the voltage to 1.1 instead of 1.325 running on 528MHz.
I feel like the settings never stick. I will set them both for 51MHz minimum but then after saving I will go back and they will either say 102 or 340MHz.
I assume I have to make them say the same thing to prevent issues, but whats the point if NEITHER seem to stick?
Depending on the kernel, those frequencies may only be activated when the screen is off.
I tried to search for a thread relating to this but couldn't find anything, if anyone knows of one a link would be appreciated.
OK, so I flashed Motleys kernel 2 days ago. Everything was running fine, I had it OC'd to 1.6 and it was super fast and smooth. I had set the governor to "on-demand" to try and save some battery life(over "performance"), and also because it seemed like the CPU would run at full 1.6 constantly if it was set to performance (I don't know if that's how it should be or not, but this isn't the issue). I used System Tuner to OC it like he recommended in his thread.
Yesterday I set it to performance to run some benchmarks, and then continued using it on performance to see how it felt. About an hour and a half later I also started messing with my home screen and apps and ended up accidentally using Quick Boot to take me to the bootloader. After powering it back on I checked System Tuner to set the governor and once I did I noticed, according to System Tuner, that 2-4 of the cores are running at full 1.6 and the CPU usage is from 25%-100% even though I have nothing open.
I flashed my recovery via Clockworkmod Recovery, Motleys kernel is now replaced by the stock kernel, however I'm still having the same issue, but just at 1.3. Any idea why the CPU is running so high, for apparently no reason?
.....
OK, so I just checked System Tuner again and the CPU doesn't seem to be doing as bad now, but it's still all over the place and I don't have anything else open. Here are the times:
Offline - 77%
340MHz -11%
475Mhz 1%
1.2Ghz - 5%
1.3Ghz - 1%
Compared to yesterday when it had said 1.3GHz 79% or something like that (and was running nothing but system tuner).
So, yeah, that does seem a lot better but one thing remains; the CPU usage still jumps up to almost 50% and once again, I am running nothing but System Tuner, so something still doesn't feel right.
I think ondemand governor is causing the CPU to shoot up so often and quickly.(That's all I can think of.) I always use interactive and it's usually the preferred governor. Ondemand is more for people who play lots of games and they need the extra boost. If you game a lot then I guess you should still to it.
Sent from my Nexus 4 using Tapatalk 2
is anybody else having an issue when you underclock? i usually set it to 1.4Ghz but the phone overrides the setting i put up using Atuntu CPU master. i feel that the phone is still fluid when underclocked, so i tend to under clock to save battery life(and stop if from overheating to 105.1 degrees farenheit).i need to get full usage out of my phone as the day starts at 5 AM till 5PM with heavy usage
any luck with this issue?
Kernel on forums if you have compatible phone. Inteli and trickster with thermald disabled. Lock freq. While your at it, look up your soc bin and and start trialling undervolts.
42 8996883
Steamer86 said:
Kernel on forums if you have compatible phone. Inteli and trickster with thermald disabled. Lock freq. While your at it, look up your soc bin and and start trialling undervolts.
Click to expand...
Click to collapse
in English please? o dont get what wou mean by the SOC Bin and the part after that. i did the trickster, but it still overrides it.
You can't make it stick with default kernel. You need a modified one with inteli so thermald doesn't auto override. SOC bin is details on your "CPU" quality for base volt values, better SOC means better overclock, underclock, and undervolting. If you're serious in doing this, search and learn. This isn't simple modification, and you will not be able do this in simple way. Make sure you have set on boot checked in trickster. Well work somewhat better, but still not a permanent solution.
Hi everyone,
Thanks for reading this . As specified above, my phone has a rather serious problem of overheating. To try and reslove the issue I tried modifying the CPU frequency, to set it low enough. And a very bizarre thing just happend.
Opening Kernel Adiutor, I saw that 4 out of my 8 cores (the 2.5 ones) were running normally. No overclock, stock settings, stock governor and so on. The issue seems to be in the other 4 (the 2.3 ones). Both the minimum and highest frequency allowed is set up to the same parameter (1556 mHz), forcing it to stay at maximum clock all the time. I tried modyfing via Kernel Adiutor the settings, lowering the minimum frequency allowed to stock one (which should be around 300 or something), but it had no effects: it immediatly comes back to 1556 and just won't come down.
All of this started happening after i removed Franco Kernel from my system, flashing another ROM (Chroma) with a different kernel altogether. I'm currently on Cataclysm ROM and after doing a clean install, formatting internal storage as well as every other partition, i couldn't resolve the issue. Moreover, Kernel Adiutor sometimes won't even show my CPU settings, stuck on an infinite loading. If anyone could help me, it would be much appreciated. It's really important. I'm by no means Android expert but i do have a rather basic understanding of ADB and so on.
Thanks a lot for your time.
-LVBNR5
I used to own a n7 and that allowed me to set min and max freq. with apps fine but i am also seeing this on my 6p, i don't notice any "overheating" although it may be due to me being used to it always running hot since i run a lot of heavier programs and also you know... SD810 but i guess it does the frequency thing as a way that frequency is actually controlled on this platform or something, because it sticks fine to the limits you set while flashing a kernel but no app can get it to stick. Then again this is just me sharing my experience with it as it is my first phone with this platform, so maybe someone who knows more about this could offer some help.
ml11ML said:
I used to own a n7 and that allowed me to set min and max freq. with apps fine but i am also seeing this on my 6p, i don't notice any "overheating" although it may be due to me being used to it always running hot since i run a lot of heavier programs and also you know... SD810 but i guess it does the frequency thing as a way that frequency is actually controlled on this platform or something, because it sticks fine to the limits you set while flashing a kernel but no app can get it to stick. Then again this is just me sharing my experience with it as it is my first phone with this platform, so maybe someone who knows more about this could offer some help.
Click to expand...
Click to collapse
Thanks anyway, i really appreciate it!