Related
Hey everyone, there is an overclocking app in the market, anyone care to give it a try?
Edit: So I downloaded it lol. Here are some screenshots. BTW, is there anyway I can verify that the cpu freq is actually being adjusted?
*Just for fun I ran neocore to see if it would raise my FPS. lol.
just notice the difference in speed. If you notice please post. And its not overclocking its just clocking. Overclocking will be beyond 528 MHz
Gameloft said:
just notice the difference in speed. If you notice please post. And its not overclocking its just clocking. Overclocking will be beyond 528 MHz
Click to expand...
Click to collapse
The app is called Overclock, you can argue with the developer about the name not me.
Anyways, I do notice a very nice speed increase.
For example, atrackdog would take me at least 20-30 seconds to load my full app list (184 apps)
After installing overclock, it loaded in under 5 seconds.
i'll run other programs, and post my results.
I ran droidgear (game gear emulator) before and after, and I can honestly say it was faster (not a placebo affect).
-Before: droidgear would take over 4 minutes just to get to the menu screen
-After: i was actually able to load a game in under 1 and a half minutes, I even let it sit to run the demo, and it is the fastest ive ever seen an emulator run on this device (compared to NesEmu, and GB emu)
It would probably actually be playable if tweaks were made to the application codebase, and android Open GL stack.
Also, the camera loads instantly after pressing the camera button and via the icon in the home screen.
well, i was too, and then i downloaded it and said "aahh, what the hell, if i break mine, ill just take my wifes haha..." probably not the best of plans but i installed it anyway
sooo i havnt burnt up my phone yet, but here is my issue with the app, does the app only work untill you reboot your phone?
because when i reboot my phone, it goes back to the default speed according to the app
also, my phone tends to hang up (stuck on the apps screen, no buttons work, screen wont rotate, power button wont shut screen off) when using the 528MHz
so far, i havnt found a reason to pay a dollar for it, but ill keep testing
[UPDATE]
resolution for all below tests is 320 x 480
i tried neocore like posted above, using the mid level setting, and i actually did raise my fps from
DEFAULT CPU (248 MHz): 20.5 (with sound off)
384 MHz: 25.0! (with sound off)
DEFAULT CPU (248 MHz): 14.5 (with sound on)
384 MHz: 20.8 (with sound on)
still havnt gotten the fast speed to work yet, but im still trying to figure that out, on another note, sweeter home does seem to load a little faster
[UPDATE]
Incase you didnt see my sig, im not running on a ADP1 phone, so that might by why the fastest setting doesnt work for me, but so far 384MHz is making a noticeable difference with NEOCORE and SWEETER HOME
andonnguyen said:
The app is called Overclock, you can argue with the developer about the name not me.
Anyways, I do notice a very nice speed increase.
Also, the camera loads instantly after pressing the camera button and via the icon in the home screen.
Click to expand...
Click to collapse
i use snap photo, which used to take FOREVER to load up on my g1 using the camera button, its significantly faster using the 384MHz setting, good observation
Ok, so so far here is a list of things ive noticed (using 384MHz vs 248MHz):
-FPS in NEOCORE increased on adverage 5 to 6 fps
-Sweeter Home doesnt lag NEARLY as much as it used to (ALOT less force closes)
-Snap Photo doesnt take a month to load using the camera button
-G1 Wakes up properly which was a issue my g1 (and others on this forum) had
-Even though the app says it will "kill" the battery, using 384MHz during normal use of the phone isnt "killing" my battery, however, doom (while runs better (even with sound on)) seems to be dropping my battery level faster, but the game is running faster, which is the trade off id expect when running these apps together
At this point is there really a need? My phone doesnt lag that much that I need to over clock not to mention my battery life sucks already.
speoples20 said:
At this point is there really a need? My phone doesnt lag that much that I need to over clock not to mention my battery life sucks already.
Click to expand...
Click to collapse
all of our battery life sucks unless you have the extended battery, im not getting THAT big of a battery drain according to the system monitor app, and it DOES make a difference on g1's that have lag issues (running tons of apps like i do)
in other threads, people have complained about the g1 not waking up quickly sometimes, ive yet to have that issue since ive clocked mine up to the 384MHz setting
@woot, you do know that the default cpu freq on the G1 is ~384mHz. So you might want to change in your sig that you're overclocked to 384mHz lol.
The program installs a script on your sd card called ocx_tmp.sh and adjusts it that way, it'll write to /system as -rw (from what I've discussed with someone) would probably cause instability.
The program will reset the cpu freq back down to 384mHz after the phone sleeps. You can verify this in terminal emulator by typing:
$su
#cat /proc/cpuinfo
Try it before and after setting the cpu freq in overclock and you'll see what I mean =)
I thought the the CPU ran at 528 MHz by default? Or is it clocked dynamically and this forces it?
Gameloft said:
just notice the difference in speed. If you notice please post. And its not overclocking its just clocking. Overclocking will be beyond 528 MHz
Click to expand...
Click to collapse
andonnguyen said:
@woot, you do know that the default cpu freq on the G1 is ~384mHz. So you might want to change in your sig that you're overclocked to 384mHz lol.
Click to expand...
Click to collapse
im not as familiar with clocking/overclocking so i wasnt sure if i was clocking it to 384, overclocking it to 384, or what, so what would be the proper thing to put in my sig? lol because according to my first quote, true overclocking wouldnt be untill i went beyond 528, so from the view of my first quote, im not OVERclocking, im clocking, wheras your saying im overclocked
andonnguyen said:
The program will reset the cpu freq back down to 384mHz after the phone sleeps. You can verify this in terminal emulator by typing:
$su
#cat /proc/cpuinfo
Click to expand...
Click to collapse
so is it infact the program thats changing the cpu freq or is it the phone? if its the program, is this to avoid overworking the cpu without the demand?
andonnguyen said:
.
The program will reset the cpu freq back down to 384mHz after the phone sleeps.
Click to expand...
Click to collapse
by sleep do you mean turning the screen off using the power button? because i saw no change in my cpu freq when doing so using your commands
ivanmmj said:
I thought the the CPU ran at 528 MHz by default? Or is it clocked dynamically and this forces it?
Click to expand...
Click to collapse
dont know, but i found this over at the android community:
Technical Features
Supports WCDMA/HSUPA and EGPRS networks
Multimedia Broadcasting Multicast Service (MBMS)
Integrated ARM11™ applications processor and ARM9™ modem
QDSP4000™ and QDSP5000™ high-performance digital signal processors (DSP)
528 MHz ARM11 Jazelle™ Java® hardware acceleration
Support for BREW® and Java applications
Qcamera™: Up to 6.0 megapixel digital images
Qtv™: Playback up to 30 fps VGA
Qcamcorder™: Record up to 24 fps QVGA
Up to 4 million triangles per second, and 133 million depth-tested, textured 3D pixels per second fill rate
gpsOne® position-location assisted-GPS (A-GPS) solution
Support for third-party operating systems
Digital audio support for MP3, aacPlus™ and Enhanced aacPlus
Integrated Mobile Digital Display Interface (MDDI), Bluetooth® 1.2 baseband processor and Wi-Fi® support
maybe that info will help? if not sorry
I remember reading somewhere by someone that it runs at 384 by default, and I think the post above confirms that...
ivanmmj said:
I thought the the CPU ran at 528 MHz by default? Or is it clocked dynamically and this forces it?
Click to expand...
Click to collapse
no, it runs at 384 by default, and clocks down even lower in the idle loop.
i am curious how this program works, as the normal cpufreq interfaces are not compiled in the kernel.
i've been running my phone for several months now at 528mhz, at a fairly minimal detriment to battery life.
i did however notice that without modifying the idle loop, the amount of cpu frequency switches even while the phone is not sleeping drops your average clock within a 10 second period to somewhere closer to 400mhz.
after modifying the idle loop to not switch frequency so often, i was able to get 27.4fps out of neocore w/o sound, and 22.7fps w/ sound.
my overall caffeine benchmark score was 582.
battery life impact is there, but fairly small. phone lasts for about a day and a half now where it used to last for sometimes 2. under heavy use, this is of course dramatically reduced.
gui fluidity is definitely increased, and sluggishness between app switches and when the translucent app drawer opens up is gone. i like it, but to the average person there probably is no need to do it.
keep in mind this is also not overclocking the cpu, it's clocking it to its default spec. as it is an embedded arm, it is designed to run hot, so i guarantee you are in no danger of hurting your phone.
also, do not listen to people that claim there could be no gain from overclocking, just because the bus speed is slower than the cpu speed does NOT mean there will be no improvement in system performance. if that were the case, there'd be no use for 4ghz desktop processors.
cache still runs full speed, and common execution paths stay in cache meaning no prefetch from system memory, meaning BIG improvement in many cases. (that's why cache exists.)
damnoregonian said:
no, it runs at 384 by default, and clocks down even lower in the idle loop.
i am curious how this program works, as the normal cpufreq interfaces are not compiled in the kernel.
i've been running my phone for several months now at 528mhz, at a fairly minimal detriment to battery life.
i did however notice that without modifying the idle loop, the amount of cpu frequency switches even while the phone is not sleeping drops your average clock within a 10 second period to somewhere closer to 400mhz.
after modifying the idle loop to not switch frequency so often, i was able to get 27.4fps out of neocore w/o sound, and 22.7fps w/ sound.
gui fluidity and responsiveness is greatly improved. sluggishness if app switching and the translucent app drawer are completely gone.
for many i imagine this means there isn't really any reason to clock the cpu up to its stock speed, but to each their own.
my overall caffeine benchmark score was 582.
battery life impact is there, but fairly small. phone lasts for about a day and a half now where it used to last for sometimes 2. under heavy use, this is of course dramatically reduced.
Click to expand...
Click to collapse
care to write up a how-to for getting the 582 consistantly and changing the idle loop?
Holy crap. Used this @528MHz with Haykuro's version 4.5 apps to sd ROM and the osk works SO MUCH BETTER!!!! Also I got 25.6 fps on neocore... very smooth
wootroot said:
care to write up a how-to for getting the 582 consistantly and changing the idle loop?
Click to expand...
Click to collapse
writeup? no. it's a big process involving the android dev environment, a modified version of mkbootimg and unyaffs.
i will gladly post the kernel modifications for those who want to recompile the kernel to do so.
the bootloader sets the clock speed, and the idle loop simply clocks down to a preset and back up to whatever it was previously after x milliseconds of inactivity (not to be confused with sleep) it's kind of a poor man's cpufreq arbitrator.
so on top of tweaking the idle loop to not drop down as often, you also have to explicitly set the frequency in the kernel upon bootup, or it will bet set at what it thinks is full speed, which is 384.
A modded version of JF's ROM would ROM.
I DO notice the sluggishness and it bugs the heck out of me. (I switched from a WING with a 200MHz CPU, and although it IS faster than the wing, it doesn't seem significantly faster and seems to much slower when I open up the camera...
damnoregonian said:
writeup? no. it's a big process involving the android dev environment, a modified version of mkbootimg and unyaffs.
i will gladly post the kernel modifications for those who want to recompile the kernel to do so.
the bootloader sets the clock speed, and the idle loop simply clocks down to a preset and back up to whatever it was previously after x milliseconds of inactivity (not to be confused with sleep) it's kind of a poor man's cpufreq arbitrator.
so on top of tweaking the idle loop to not drop down as often, you also have to explicitly set the frequency in the kernel upon bootup, or it will bet set at what it thinks is full speed, which is 384.
Click to expand...
Click to collapse
that involved eh?
thanks for this post though, now i understand more about the idle loop and why the cpu freq resets with each reboot
maybe someone can take this stuff further like he said, that kind of stuff would be worth the dollar, imo more than a dollar
well... i don't mind providing basic procedure and source, i just don't want to get dragged into level 1 support of the procedure.
i'll go ahead and package up some source, prebuilt boot images based on JF's RC33 (which is what i run) and a basic procedure.
Q&A for [KERNEL][D5803&D5833] AndroPlusKernel
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [KERNEL][D5803&D5833] AndroPlusKernel. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Thanks
Very nice kernel, fast and smooth - great work and port.
Anyone knows if it's possible to use any third party kernel app to boost the headset volume?
Working
Hi this is my first post, infact I joined so I could report my findings.
I would just like to confirm so far that V5 working on my Z3C using the .93 firmware. I didn't need to wipe cache/dalvik/data partitions either.
For purposes of settings configuration, I'll be using TricksterMod
For stress testing purposes I'll be using Stability Test 2.7
Overclocking
Overclocking seems to work, I'll stress test and report back with the results.
I was wrong, it is unstable when overclocking and stress testing, with the phone force rebooting 1-5 seconds in to the stability test which loaded all 4 cores. Tried 2899Mhz and 2880Mhz (were both unstable and didn't try 2.72, 2.75, 2.57 either - I might try stability testing them.) Was completely stable at 2.47GHz, and it actually stuck there, no throttling in place! I stopped the stress test when the CPU temp was around 77-80C as my hand was getting burnt! The battery temp reached about 46C. It took 10 mins of stress testing for this to be reached. When the stock kernel was in place it would begin throttling after about 1-20 seconds under full load. First 2.2GHz, then 2 then 1.7 then 1.5 and eventually 1.25 after about 2-4mins.
I couldn't do a single core test though. I suspect as most games use single core or dual cores it wouldn't get overly hot.
My opinion is that fast clocked phones should be marketed with 2 speeds. The highest it'll reach under a boost mode (turbo for Intel's i5 and i7 series), and a slower speed that it'll average out at under thermal pressure. The Z3Cs would be turbo: 2.5GHz and normal: 1.5GHz.
Governors
These are quick tests I'm performing here to provide a quick look at responsiveness and potential unnecessary CPU jump ups.
Wheatley - most of the time it's hovering at top speed when approx CPU usage is 9%, it'll occasionally hunt down to 300Mhz but then right back up to 2899MHz. This one is speedy though. Governor tunables available.
Lagfree - idles at 300MHz - 960MHz then hunts up to 2.2-2.9Ghz when needed and turns on the second core. It seems to slow back down to idle. This one seems to have fast scrolling, sliding notifications pane quickly). No governor tunables.
SmartassV2 - idles at 300Mhz, speeds up to 422-960 on core 0, and turns on core 1 at 1.2-1.5GHz for a few seconds under fast scrolling and notification pane opening. Seems quite responsive. Probably good for battery life hopefully with the responsiveness of Interactive. No governor tunables.
Lionheart - Idles at 960 MHz for a few seconds then slows down to 300MHz with the odd increase to 729MHz. Core 0 and Core 1 reaches 1.26GHz under scrolling, notification pane opening. As fast as the others. Governor tunables available.
Hotplugging
Intelliplug appears to work better than MP-Decision - now only one core is on during idle, instead of 2.
MP-Decision was disabled to avoid conflicts.
Undervolting
I've only undervolted 300MHz to 675MHz from 775MHz as of writing this post.
Tried quickly undervolting in trickstermod by setting them all about -75mV, stability tested it, appears stable. I'll tweak the voltages a bit better when I do a scaling stability test.
Issues I've experienced
Sound Control is the only thing so far that causes a reboot. However music still plays over the speakers and headphones. Equaliser works too.
Upon rebooting, the CPU top speed will set itself to 2.2GHz, despite being set higher and saved at a higher speed in Trickstermod. Certainly trivial though.
Strange thing I've noticed: On the undervolt part I've noticed that there is a freq called 3033MHz, but no 2899MHz freq. Just an observation.
Misc
Force Fast Charge confirmed working! Before flashing new kernel charge went up 5% in about half an hour. It's now up another 5% in a matter of 5-10mins. This is when plugged to my PC.
Vibrator strength - set to 20 from 31, much quieter on table and can still feel it.
I'd like to say a huge thank you to DooMLoRD and AndroPlus for developing this stable kernel. Now my Z3C is worth the £28 a month I'm paying for again. Since this silly lad decided to bork the camera, Bravia functionality etc by rooting it on the first day. I'll report back and edit the post with my findings.
Max won't go beyond 2.266 GHz, Min won't change.
Hi All,
Firstly, great job with the kernel. Our Z3C is such a capable piece of kit and this just makes it that much better.
I'm running stock, 23.0.A.2.93, unlocked, rooted.
Problem:
I've tried using both SetCPU and No-Frills and while both show frequencies that are supposedly selectable above 2.266 GHz, neither app would actually respond. Meaning the max frequency will still only be 2.266 GHz even if I tried selecting something like 2.458 GHz (which should be selectable given that stock is 2.458 GHz.) See caps.
In addition, the Min value just won't change at all from 300 MHz. The frequencies scale up and down as the load changes but I can't raise the Min (again using both SetCPU and No-Frills) from 300 MHz.
Tried: I've tried turning off stamina mode and frozen apps that could control CPU activity (e.g. I use DS Battery Saver). I changed up Governors and Schedulers. I've tried re-flashing the kernel and it still doesn't change these behaviors.
Question/Need help: Just wanted to ask if anybody else have any problems setting the max frequency beyond 2.266 GHz and/or changing the minimum frequency from 300 MHz? Would appreciate any help resolving this behavior.
Thanks in advance!
pjmanalo said:
Hi All,
Firstly, great job with the kernel. Our Z3C is such a capable piece of kit and this just makes it that much better.
I'm running stock, 23.0.A.2.93, unlocked, rooted.
Problem:
I've tried using both SetCPU and No-Frills and while both show frequencies that are supposedly selectable above 2.266 GHz, neither app would actually respond. Meaning the max frequency will still only be 2.266 GHz even if I tried selecting something like 2.458 GHz (which should be selectable given that stock is 2.458 GHz.) See caps.
In addition, the Min value just won't change at all from 300 MHz. The frequencies scale up and down as the load changes but I can't raise the Min (again using both SetCPU and No-Frills) from 300 MHz.
Tried: I've tried turning off stamina mode and frozen apps that could control CPU activity (e.g. I use DS Battery Saver). I changed up Governors and Schedulers. I've tried re-flashing the kernel and it still doesn't change these behaviors.
Question/Need help: Just wanted to ask if anybody else have any problems setting the max frequency beyond 2.266 GHz and/or changing the minimum frequency from 300 MHz? Would appreciate any help resolving this behavior.
Thanks in advance!
Click to expand...
Click to collapse
Try installing TricksterMod (from Google Play store, trust me, you'll love it!) Then go to General and set the max speed to 2.46GHz or higher, and try using the Ondemand Governor too. I noticed that it wouldn't stick properly sometimes when using Interactive governor. If it doesn't stick for you then turn Frequency Lock on. Then check in the info tab that it's hitting the higher speed. Personally I'd recommend leaving the min speed on 300MHz. If you need constant high speeds, select the performance governor.
DBCJoey said:
Try installing TricksterMod (from Google Play store, trust me, you'll love it!) Then go to General and set the max speed to 2.46GHz or higher, and try using the Ondemand Governor too. I noticed that it wouldn't stick properly sometimes when using Interactive governor. If it doesn't stick for you then turn Frequency Lock on. Then check in the info tab that it's hitting the higher speed. Personally I'd recommend leaving the min speed on 300MHz. If you need constant high speeds, select the performance governor.
Click to expand...
Click to collapse
Thanks! That did the trick!
Odd that my usual app for the job across 4 other phones - SetCPU - doesn't work on what should essentially be the same job. [emoji55]
Please make sound_control drivers work so its possible to boost headphone volume on the Xperia Z3 Compact... Thanks
Nice work, a lot of updates I like it!
Is it possible to add a change log?
Thanks!
kernel for d5803 with the .93 but not .105
i search a kernel for the d5803 with the last .93 french version of phone
.5.77
Works great! Thanks a lot
Link for Z3C_D5803_AndroPlusKernel_v10.zip is dead
Pls upload in another location.
Yay sound control is working, thank you so much you're the best!
How to make this?
Hi AndroPlus,
I'm trying to figure out how one would go about building this boot.img that you've created.
What platform and compiler are you using?
Where are you getting sources the for the kernel? This file?
c9af6fc647060fb85dd646798453ec8f 23.0.A.2.105.tar.bz2
How do you construct boot.img from zImage + recovery?
Sorry if these are dumb questions.
Edit: never mind, I figured this out.
http://developer.sonymobile.com/kno...evices/how-to-build-and-flash-a-linux-kernel/ contains most of the information I needed.
The arm version of gcc that ships with Ubuntu 14.04 worked fine - arm-none-eabi-gcc (4.8.2-14ubuntu1+6) - no need to track down any mystery binaries. I did have to make several modifications to the kernel source to get it to build. Interestingly, some of the cpufreq stuff contained code that was incorrect. Someone at Samsung needs to go look up what "sequence point" means.
The hardest part was figuring out how to turn the zImage + ramdisk into something I could boot.
This: https://github.com/sonyxperiadev/mkqcdtbootimg was the correct tool to use - again, no need to track down any mystery mkbootimg or dtbTool binaries.
Hope this is helpful to someone. As someone new to Xperia dev, I found most of the information out there worse than useless.
Hello, I'm using Titan Stock ROM and it was working quite OK, but I noticed that with high CPU usage during longer periods of time (Like when you are calling on Skype with both webcams on) after like 5 minutes (depending on ambient temperature) the CPU throtling kicks in and you can barely end the call because the whole GUI of Android gets completely unresponsive.
Quick questions:
- What is the maximum "safe temperature" for the CPU to not break? 60ºC is way too less.. as it gets easily to that temperatures.
Now in hope of getting this a bit fixed I recently installed the "Stellar Kernel". I set the CPU settings as recomended on its kernel page (Undervolted to Min Freq. 98MHz and Max Freq. to 1190MHz). Now its just a nightmare. It overheats even quicker.. and when it throttles you can just pray to do anything.. (I changed finally to Min Freq to 385MHz but that doesn't helps much).
And on the other hand thanks to the underclocking the phone doesn't wants to wake up during minutes.. which is quite unpractical when somebody is calling you.. you can hear the phone ringing but you cannot accept the call because the phone doesn't want's to wake up. But that got somehow fixed putting it back to the Min Freq. +300Mhz.
Just want to know if somebody knows about some magic setting which allows the phone to function properly during longer time.. as far as I'm aware 1190MHz is the original maximum Freq. of this phone so no overclicking is done here. So it looks that the only way to have it working somehow decently is to underclock the maximum frequency and leave the minimum frequency high enough to work properly. I don't really care about battery anymore, as I just need the phone to be functional, and as it is now it's just not. Any advices? Thanks for any reply.
You probably have a hardware problem
rhp07 said:
Hello, I'm using Titan Stock ROM and it was working quite OK, but I noticed that with high CPU usage during longer periods of time (Like when you are calling on Skype with both webcams on) after like 5 minutes (depending on ambient temperature) the CPU throtling kicks in and you can barely end the call because the whole GUI of Android gets completely unresponsive.
Quick questions:
- What is the maximum "safe temperature" for the CPU to not break? 60ºC is way too less.. as it gets easily to that temperatures.
Now in hope of getting this a bit fixed I recently installed the "Stellar Kernel". I set the CPU settings as recomended on its kernel page (Undervolted to Min Freq. 98MHz and Max Freq. to 1190MHz). Now its just a nightmare. It overheats even quicker.. and when it throttles you can just pray to do anything.. (I changed finally to Min Freq to 385MHz but that doesn't helps much).
And on the other hand thanks to the underclocking the phone doesn't wants to wake up during minutes.. which is quite unpractical when somebody is calling you.. you can hear the phone ringing but you cannot accept the call because the phone doesn't want's to wake up. But that got somehow fixed putting it back to the Min Freq. +300Mhz.
Just want to know if somebody knows about some magic setting which allows the phone to function properly during longer time.. as far as I'm aware 1190MHz is the original maximum Freq. of this phone so no overclicking is done here. So it looks that the only way to have it working somehow decently is to underclock the maximum frequency and leave the minimum frequency high enough to work properly. I don't really care about battery anymore, as I just need the phone to be functional, and as it is now it's just not. Any advices? Thanks for any reply.
Click to expand...
Click to collapse
acquire kernels and other que rooms have different governors Study on them and the Best That was enough pro you and your needs .
I think this will help you , give will take this need to manually change the clock all, the governor will operate according to its governor preferably .
Read
http://androidforums.com/threads/android-cpu-governors-explained.513426/
:good::good::good::good::good::good:
Thanks if helped :highfive:
I really need to stop making so many threads.
Anyways, my latest issue is actually with baybutcher's custom kernel built into RR.
I have my CPU settings set to the performance governor, 2496MHz for the max frequency, and 1036MHz for the minimum frequency.
I noticed, however, that in certain apps (mostly Tumblr) I get a lot of visual lag, and when I check my kernel settings, the maximum CPU frequency is adjusting itself, jumping around all the different frequency speeds. If I attempt to set the frequency, it ignores it and continues adjusting. I have to adjust another setting to get it to stay at the frequency I set it at.
Is this normal or is there something I can do to solve it?
Latiken said:
I really need to stop making so many threads.
Anyways, my latest issue is actually with baybutcher's custom kernel built into RR.
I have my CPU settings set to the performance governor, 2496MHz for the max frequency, and 1036MHz for the minimum frequency.
I noticed, however, that in certain apps (mostly Tumblr) I get a lot of visual lag, and when I check my kernel settings, the maximum CPU frequency is adjusting itself, jumping around all the different frequency speeds. If I attempt to set the frequency, it ignores it and continues adjusting. I have to adjust another setting to get it to stay at the frequency I set it at.
Is this normal or is there something I can do to solve it?
Click to expand...
Click to collapse
Try setting the thermal limits just a little higher, in Kernel Aduitor. Try 70 degrees instead of the default 60, 65 (or whatever the default is, I forget). With one of the thermal controls, especially Intellithermal -- maybe one you are on? -- it gets very aggressive and actually starts throttling 10 degrees sooner than the limit. So, by raising the limit a little it won't throttle the frequencies too soon.
I not only raised the limit to 70 degrees (that's Celsius by the way), I also switched to one of the other thermal controls.
ChazzMatt said:
Try setting the thermal limits just a little higher, in Kernel Aduitor. Try 70 degrees instead of the default 60, 65 (or whatever the default is, I forget). With one of the thermal controls, especially Intellithermal -- maybe one you are on? -- it gets very aggressive and actually starts throttling 10 degrees sooner than the limit. So, by raising the limit a little it won't throttle the frequencies too soon.
I not only raised the limit to 70 degrees (that's Celsius by the way), I also switched to one of the other thermal controls.
Click to expand...
Click to collapse
I'm not sure where I change that. Under the Thermal tab, all I get are options to toggle Core Control, VDD Restriction, and Temperature Throttle.
Latiken said:
I'm not sure where I change that. Under the Thermal tab, all I get are options to toggle Core Control, VDD Restriction, and Temperature Throttle.
Click to expand...
Click to collapse
Once you turn one of those on , and set on boot you should see temperature slider in that same section.
]
ChazzMatt said:
Once you turn one of those on , and set on boot you should see temperature slider in that same section.
Click to expand...
Click to collapse
http://imgur.com/Md4rxMG[/IMG
It doesn't seem to be there, not sure if I'm doing something wrong.
I also noticed that it will bring the maximum CPU frequency down to match the minimum frequency, and they will both lock so I can't change it. It's getting really annoying, especially when it happens when I need it most, like while typing and watching videos at the same time.
Let me come straight to the point-- Whenever I do any CPU intensive task for long like playing heavy games, CPU heats up and automatically throttles down to like 998 or 784MHz and games start lagging. Everything starts lagging. This phone heats up pretty quickly. I have no problem with handling a hot phone but I DO NOT want the CPU to throttle down. What's the use of Snapdragon 400 when it can't handle the heat?
How can I prevent it from throttling down? (anything to do with that "thermal" section in kernel adiutor?)
Are you using custom kernel?
In kernel auditor you can set the max temp to start throttling.
JD154 said:
Are you using custom kernel?
In kernel auditor you can set the max temp to start throttling.
Click to expand...
Click to collapse
I am using decipher kernel. Where is the temperature setting?
nilanko said:
I am using decipher kernel. Where is the temperature setting?
Click to expand...
Click to collapse
In Thermal screen you should able to set a maximum temperature to start throttling (I didn't used decipher) extended kernel allow this feature
JD154 said:
In Thermal screen you should able to set a maximum temperature to start throttling (I didn't used decipher) extended kernel allow this feature
Click to expand...
Click to collapse
Decipher doesn't have this setting. Can I just turn it off? Titan heats up very quickly so CPU starts getting throttled.
nilanko said:
Decipher doesn't have this setting. Can I just turn it off? Titan heats up very quickly so CPU starts getting throttled.
Click to expand...
Click to collapse
You can't do it because heat will damage the cpu, try changing kernel to extended kernel and try.
JD154 said:
You can't do it because heat will damage the cpu, try changing kernel to extended kernel and try.
Click to expand...
Click to collapse
I was just playing NOVA 3 and it started lagging after a while and saw the CPU ramped down to 784MHz! This is really stupid! What's the use of quad core then?! If I can't even utilize it's potential just due to heat then what's the use? Is there no way to stop it from heating up so much? I switched off all the controls on thermal page but it did nothing. CPU still loves to ramp down.
Is extended kernel available for CM12.1? I can't find it.
nilanko said:
I was just playing NOVA 3 and it started lagging after a while and saw the CPU ramped down to 784MHz! This is really stupid! What's the use of quad core then?! If I can't even utilize it's potential just due to heat then what's the use? Is there no way to stop it from heating up so much? I switched off all the controls on thermal page but it did nothing. CPU still loves to ramp down.
Is extended kernel available for CM12.1? I can't find it.
Click to expand...
Click to collapse
Disable data connection, location, Bluetooth and reduce brightness to the minimum while gaming.
Maybe you have a lot of background process and the cpu load is high. You can try also changing ROM to MM (some optimization and stuff).
Extended kernel is available for 6.0/7.0 AOSP/CM
JD154 said:
Disable data connection, location, Bluetooth and reduce brightness to the minimum while gaming.
Maybe you have a lot of background process and the cpu load is high. You can try also changing ROM to MM (some optimization and stuff).
Extended kernel is available for 6.0/7.0 AOSP/CM
Click to expand...
Click to collapse
Did all that and now I can play a bit more without CPU being throttled down. I also installed halogen kernel that allows to set the temps. I set them to 100 degrees Celsius. No improvement! CPU still throttles down on reaching the default 70 degrees. This phone is totally stupid! We actually can't even use the full potential of the CPU unless we are sitting inside a refrigerator!
A very quick and easy way to fix throttling is flashing a kernel with UnderVolt support.
The only one available for Titan is Halogen Kernel
http://forum.xda-developers.com/moto-g-2014/development/kernel-halogenkernel-r1-t3133042
But be aware that some values still need optimizations, such as 1.4 and 1.5 ghz. They consume more energy than it should, making the phone more warm, but nothing compared to the stock moto values.