Welcome to Myrt Torture Tester.
As always, this app is BETA, expect bugs. Tested on Stock GB/HP Extreme & guestekrnL, CM7/Etana, CM9/HP ICS & Harsh.
Will only work on OC/UV-kernels.
It's primarily intended as a tester to find your stable frequencies and voltages, but can also be used as a battery-life tester and a rough benchmark.
This app comes with no more support than the 2nd post. If you don't know how to use it after reading that you don't need it.
Using this app, you will be capable of causing actual damage to your device. I take no responsibility for any consequences.
This app shall under NO CIRCUMSTANCES be included in any ROM, or uploaded any other place than this post.
Changelog
0.5.6 - Fixes crash when system is unresponsive for long periods.
0.5.5 - Keeps reading the current cpu-frequency throughout the test. (Some beta kernels unexpectedly change frequencies during the test, this allows you to see it.)
0.5.4 - CM7-compatability-fix.
0.5.3 - Fixes frequency not being set on guestekrnL.
0.5.2 - Fixed links on about page.
0.5.1 - Plays nice on non-oc kernels.
0.5.0 - First BETA-release
HOW TO USE:
In its simplest form, the app is a benchmark. You start a CPU-test at a specific frequency for a specific time-period and get the average Mflops-result. If you are going to compare different kernels, it will give you a normalized to 1Ghz result as well. Different kernels usually have different frequency-tables, so test them at the closest steps you can find, then compare the normalized result.
The more useful aspect of it is to test if a specific frequency is stable at a specific voltage. The app only allows to test the frequencies in the voltage table - because if it is stable at those frequencies it will be stable at all other frequencies which fall within those voltage-steps. If you have undervolted too much, the phone will usually reboot pretty quickly. If you have undervolted "on-the-edge", the phone will likely freeze. If you have undervolted so that it is basically stable, but sometimes fails, you'll either get a crash to the desktop or MTT will inform you of a calculation error. If you are testing for stability you need to test for at least 60 minutes to have any confidence in the result, I've had several tests fail after 45-50 minutes.
It can also be used to see what impact, if any, undervolting has on the processors' power-consumption. After you have made sure a frequency/voltage-pair is stable, you can run a battery-test and compare it to an identical test at stock voltage. This will simply run from a full(ish) battery to a certain battery percentage, and give you how long it was able to run. Since the battery-percentage is pretty loosely coupled to the actual battery-charge, it will also give figures for consumption per minute or second. This kind of test should also be run over a long a period as possible to get accurate results. Measuring from 100% to 90% will only give you an indication, prone to error. You can not compare a test between, say 100->50 and 100->20, because the discharge rate varies with the charge-level.
For most accurate testing and benchmarking: enable flightmode, unplug the device, freeze any apps which may run in the background, uninstall everything you don't need, wait 3 minutes after booting before testing, do not touch the screen or move the device while a test is running. Even then there are Android quirks which will cause some variation in the results. Therefore the same test should be repeated as many times as you can afford.
The major enemy of stability, assuming you have enough voltage, is heat. Make sure to test the device under the same conditions as it will be used. If you're going to overclock on a hot summer's day, test it on a hot summer's day. MTT dims the screen to minimize the impact it has on the battery and heat-generation, be aware that your device will be hotter when the screen is at normal brightness.
Stability tests should also be performed at different battery-levels. If your device is stable when the battery is fully charged, it does not automatically mean it will be stable when it is almost discharged.
MTT logs all succesfull tests (max 200 lines.) If you enable "Store log on sdcard" in preferences the log will be saved to /sdcard/MTT_Log.txt.
Known issues:
o Sometimes the device will give you half the score you should get. I do not know if this is a kernel or android-bug, but it seems that both test threads get scheduled to run on the same core, and the second core goes unused, even when it is active. Exiting the app and starting it again does not help usually, but killing it sometimes does. Rebooting is always an option.
o Not a "known issue", but this app lets you under- and overvolt in 5mV steps. Different kernels may handle this differently, either not undervolting at all, or adjusting it to the nearest 25mV step. It has worked on the kernels I have tried, but there are too many kernels out there to be sure.
TrymHansen said:
HOW TO USE:
In its simplest form, the app is a benchmark. You start a CPU-test at a specific frequency for a specific time-period and get the average Mflops-result. If you are going to compare different kernels, it will give you a normalized to 1Ghz result as well. Different kernels usually have different frequency-tables, so test them at the closest steps you can find, then compare the normalized result.
The more useful aspect of it is to test if a specific frequency is stable at a specific voltage. The app only allows to test the frequencies in the voltage table - because if it is stable at those frequencies it will be stable at all other frequencies which fall within those voltage-steps. If you have undervolted too much, the phone will usually reboot pretty quickly. If you have undervolted "on-the-edge", the phone will likely freeze. If you have undervolted so that it is basically stable, but sometimes fails, you'll either get a crash to the desktop or MTT will inform you of a calculation error. If you are testing for stability you need to test for at least 60 minutes to have any confidence in the result, I've had several tests fail after 45-50 minutes.
It can also be used to see what impact, if any, undervolting has on the processors' power-consumption. After you have made sure a frequency/voltage-pair is stable, you can run a battery-test. This will simply run from a full(ish) battery to a certain battery percentage, and give you how long it was able to run. Since the battery-percentage is pretty loosely coupled to the actual battery-charge, it will also give figures for consumption per minute or second. This kind of test should also be run over a long a period as possible to get accurate results. Measuring from 100% to 90% will only give you an indication, prone to error. You can not compare a test between, say 100->50 and 100->20, because the discharge rate varies with the charge-level.
For most accurate testing and benchmarking: enable flightmode, freeze any apps which may run in the background, uninstall everything you don't need. Even then there are Android quirks which will cause some variation in the results. Therefore the same test should be repeated as many times as you can afford.
The major enemy of stability, assuming you have enough voltage, is heat. Make sure to test the device under the same conditions as it will be used. If you're going to overclock on a hot summer's day, test it on a hot summer's day. MTT dims the screen to minimize the impact it has on the battery and heat-generation, be aware that your device will be hotter when the screen is at normal brightness.
Stability tests should also be performed at different battery-levels. If your device is stable when the battery is fully charged, it does not automatically mean it will be stable when it is almost discharged.
MTT logs all succesfull tests. If you enable "Store log on sdcard" in preferences the log will be saved to /sdcard/MTT_Log.txt.
Click to expand...
Click to collapse
Really interesting! Big thanks
Sent by LG Optimus 2x
Doesn't seem to work for me, always goes to my max set freq of 1.1ghz, no matter if i set it higher or lower in the program. Same mflops result too. Changing the max freq in guesteoc results in that new max freq being used all the time in the program.
kfallz said:
Doesn't seem to work for me, always goes to my max set freq of 1.1ghz, no matter if i set it higher or lower in the program. Same mflops result too. Changing the max freq in guesteoc also results in that new max freq being used all the time in the program.
Click to expand...
Click to collapse
Ok, thanks for the feedback. Which version of guestekrnL? I'm mainly using that myself, works here on 1.7.
EDIT: Ok, I've found the reason. I had disabled the 00cpufreqenabler script (to simulate other kernels), but it didn't work after I enabled it. Will release a fix as soon as I can override the permission properly.
kfallz said:
Doesn't seem to work for me, always goes to my max set freq of 1.1ghz, no matter if i set it higher or lower in the program. Same mflops result too. Changing the max freq in guesteoc results in that new max freq being used all the time in the program.
Click to expand...
Click to collapse
App updated to 0.5.3 - fixes the issue where frequency is not set on guestekrnL.
TrymHansen said:
App updated to 0.5.3 - fixes the issue where frequency is not set on guestekrnL.
Click to expand...
Click to collapse
Giving the new version a try, and not that it matters now but I'm using 1.7.0t2
Yea working fine now
Updated to 0.5.4 - Now the sliders behave properly on CM7.
Myrt, do you think that we have more than one different hardware inside our phones? Because the results are way to different from one ppl to another, for example, Temasek can't OC even to 1.1GHz, and Vadonka puts at 1.4GHz without the burn, with the tests, I get to 70ºC in 2min with 1.1GHz, but the strange thing, is that the phone doesn't lags or anything to show that it haves an high-temp. Did you have some screen of the test in your own phone? I have exchanged my first phone because it always get too hot for me, my second gets hot always when I try to play any game.
chaozbr said:
Myrt, do you think that we have more than one different hardware inside our phones? Because the results are way to different from one ppl to another, for example, Temasek can't OC even to 1.1GHz, and Vadonka puts at 1.4GHz without the burn
Click to expand...
Click to collapse
No, we have pretty much the same hardware, specification-wise. It is very common to have different tolerances for speeds and voltages. I'm pretty sure that the moment Vadonka tries my app at 1.4Ghz, he too will get a hot CPU.
, with the tests, I get to 70ºC in 2min with 1.1GHz, but the strange thing, is that the phone doesn't lags or anything to show that it haves an high-temp.
Did you have some screen of the test in your own phone? I have exchanged my first phone because it always get too hot for me, my second gets hot always when I try to play any game.
Click to expand...
Click to collapse
I didn't take a screenshot, if that is what you ask, I have the app abort the test at 72C, and the temp falls quickly back to normal. I don't even have vadonkas kernel installed anymore, I'm a stock man, installed CM7 just to make the app compatible.
However, I guess we can encourage people to post their temps and frequencies here, in this thread. If anyone manages to run 1.4Ghz for more than 5 minutes and not reach 70C I'll be impressed. (I do all my temp-testing when plugged in though, probably easier when unplugged.)
TrymHansen said:
No, we have pretty much the same hardware, specification-wise. It is very common to have different tolerances for speeds and voltages. I'm pretty sure that the moment Vadonka tries my app at 1.4Ghz, he too will get a hot CPU.
I didn't take a screenshot, if that is what you ask, I have the app abort the test at 72C, and the temp falls quickly back to normal. I don't even have vadonkas kernel installed anymore, I'm a stock man, installed CM7 just to make the app compatible.
I had these temps in Spica HP kernel, so stock rom, CM7 with Vadonka, I saw an 84ºC (leave my brother playing in the phone, and he said to me that the phone was hot haha)
Click to expand...
Click to collapse
TrymHansen said:
However, I guess we can encourage people to post their temps and frequencies here, in this thread. If anyone manages to run 1.4Ghz for more than 5 minutes and not reach 70C I'll be impressed. (I do all my temp-testing when plugged in though, probably easier when unplugged.)
Click to expand...
Click to collapse
If we can't run 1.4GHz for me than 5min without reaching 70ºC, and 70ºC is the maximum temp, we can't play or let the phone in the frequency for daily use?
chaozbr said:
If we can't run 1.4GHz for me than 5min without reaching 70ºC, and 70ºC is the maximum temp, we can't play or let the phone in the frequency for daily use?
Click to expand...
Click to collapse
Well, no, I'm not saying that, there are too many unknowns.
1) We don't know if the reported temp is correct.
2) We dont' really know the max temp for tegra2. (The 70C figure is not from an official source.)
3) This app is meant to test stability, so temps will get as hot as possible. A game will most likely not stress the CPUs quite as much.
But, all that taken into consideration, 1.4Ghz is probably too high for sustained operation. It will probably be fine for normal use, where the CPUs get to rest once in a while, but not for prolonged CPU-heavy tasks (which this app demonstrates.) That being said, this app is designed to produce as much heat as possible to test stability.
It took me 41sec till the CPU reached 70°C from 40°C on 1408MHz using latest beta 3.0.y etana.
Tapatalk 2-vel küldve az én Optimus 2X-ről
Thanks for this, this app looks great!
I usually don't UV as it introduces some instability to my device even at low -UV values which isn't worth the rather small gain in battery life - but it's still good to know that this app existis if I'll change my mind someday
tonyp said:
Thanks for this, this app looks great!
I usually don't UV as it introduces some instability to my device even at low -UV values which isn't worth the rather small gain in battery life - but it's still good to know that this app existis if I'll change my mind someday
Click to expand...
Click to collapse
Yeah, I don't usually undervolt either, I carry spare batteries, and the fear of unstability was always lurking when I did. (I did make an undervolt app afterall, had to test it.)
So with this app my hope is that many myths will be dispelled - using this people should be able to find out what they need.
(A few weeks ago I had forgotten the batteries in a bag in a hotellroom, far away. I really, really, really needed 20 extra minutes of battery-life then. So now I will probably undervolt to voltages I know are safe, just in case something similar should happen. Sometimes 5 minutes make all the difference in the world.)
I cannot set any other V (no UV or OV) using Temasek 99 with latest Vadonka Beta 11.05. Kernel. The program always crash after the 2sec warmup.
Gesendet von meinem Optimus 2X mit Tapatalk 2
kennbo82 said:
I cannot set any other V (no UV or OV) using Temasek 99 with latest Vadonka Beta 11.05. Kernel. The program always crash after the 2sec warmup.
Gesendet von meinem Optimus 2X mit Tapatalk 2
Click to expand...
Click to collapse
Ok, I need some more info I think. First of all, is the app the latest version? If yes, do you get a superuser message the first time you start the app after a reboot? Which values do the bottom sliders show right after starting the app for the first time?
Tried it myself today on temasek 100 with both 3.0.31 OC and the latest beta (OC-only of course), worked on both for me. One installation however failed, and I had to repair the system-partition before the app would work again. (Superuser pretended to give access, but /system wasn't really writable, so it failed.) Check which apps are listed in superuser, if you see the same app listed a lot of times, that's your problem.
TrymHansen said:
Ok, I need some more info I think. First of all, is the app the latest version? If yes, do you get a superuser message the first time you start the app after a reboot? Which values do the bottom sliders show right after starting the app for the first time?
Tried it myself today on temasek 100 with both 3.0.31 OC and the latest beta (OC-only of course), worked on both for me. One installation however failed, and I had to repair the system-partition before the app would work again. (Superuser pretended to give access, but /system wasn't really writable, so it failed.) Check which apps are listed in superuser, if you see the same app listed a lot of times, that's your problem.
Click to expand...
Click to collapse
Sooorry I'm too stupid, tried the 216 Mhz only which is too slow for the total phone use and test. Program works fine!
Again sorry and thanks for the tool
kennbo82 said:
Sooorry I'm too stupid, tried the 216 Mhz only which is too slow for the total phone use and test. Program works fine!
Again sorry and thanks for the tool
Click to expand...
Click to collapse
Ok, good to know, thanks. I will have to look into it anyway, it shouldn't crash even at 216Mhz, but I'll take that as low-priority, in other words tomorrow ;-)
I have just updated to Cyanogenmod 7.2 stable on my P990 Optimus 2x (Fido Canadian version).
When I go to the CPU settings I cannot change the min/max frequencies or select a CPU governor.
I have done some research and found kernels like Vork and FauxDS, but they are for 7.1 nightlies so I am not sure if it is a good idea to flash them.
What I am most afraid about is the possibility of getting the black screen of death while my phone sleeps (it happened once already but it stopped after I changed to a different charger and reflashed CM7.2).
The reason why I want to change the settings is that there tends to be scrolling lag (my old HTC Desire Z was faster!) and there is also a bit of lag waking up the phone (lockscreen does not appear instantly when pressing power button).
Does anyone know what is the best kernel I can flash to enable frequency/governor changes in CM7.2 stable? I would prefer not to change the ROM if possible as I am kinda nooby in comparison to the XDA community in general. Thanks for any help.
I suggest you try Etana kernel. It has the things you need. Also use CPU master to set profiles and minimum CPU frequencies. I used something like min freq 352 MHz when asleep (don't worry doesn't drain battery) and I had no lag whatsoever.
heavencanwait said:
I suggest you try Etana kernel. It has the things you need. Also use CPU master to set profiles and minimum CPU frequencies. I used something like min freq 352 MHz when asleep (don't worry doesn't drain battery) and I had no lag whatsoever.
Click to expand...
Click to collapse
Are you referring to http://forum.xda-developers.com/showthread.php?t=1427646 ?
If so, do I just flash the zip off the sd card using ClockworkMod? And what are the differences between lite and DS?
Thanks.
All right, after reading, I determined I don't need LOC/HOC/DS as I don't intend to raise the max frequency, I just want to raise min frequency.
Installed the Etana kernel via CWM and it works. I can raise minimum frequency, though I still cannot see a governor option! Any idea how to get my governor setting back?
You can use CPU master and set some profiles. It's not exactly the same as governors but it's as close as it gets and it gets the job done pretty well. As far as I remember there were two governors for O2X - powersave and performance. I've always used performance and I can't tell if there's a HUGE difference in battery usage. I guess performance utilizes higher CPU frequencies when the device is asleep and somehow scales faster to even higher frequencies when needed to. But this might be complete crap as I am not too much into how CPUs work...
And please use the THANKS button (right below the user name), it kind of forum etiquette and it keeps people motivated to help others. Thank the Etana developer too.
heavencanwait said:
You can use CPU master and set some profiles. It's not exactly the same as governors but it's as close as it gets and it gets the job done pretty well. As far as I remember there were two governors for O2X - powersave and performance. I've always used performance and I can't tell if there's a HUGE difference in battery usage. I guess performance utilizes higher CPU frequencies when the device is asleep and somehow scales faster to even higher frequencies when needed to. But this might be complete crap as I am not too much into how CPUs work...
And please use the THANKS button (right below the user name), it kind of forum etiquette and it keeps people motivated to help others. Thank the Etana developer too.
Click to expand...
Click to collapse
Thanks for letting me know, I didn't realize there was a thanks button at first haha.
Fixed!
As for now CPU Master in his profiles let's you choose governor. We have only 2. Power save nd Performance.
Sent from LG 2X using Tapatalk 2 Elite
hey i needed some help on overclocking and changing some voltages on my device!!
1.i have read threads and guides on other forums before which explain how to OC and what are governers and schedulers etc.
2. most threads on this topic are from different devices' forums
so i thought their frequencies voltages must vary as they have different CPUs and hence started a new thread!!
3. What i want to know is, what voltages should i choose at different frequencies??
or it is completely not important to set voltages??
4. Earlier i used setCPU but it doesnt stick to frequencies i set and resets default 1024 after reboot.
how do i avoid this??
Currently i am using AnTuTu CPU master PRO for doing all this
please guide me if possible provide specific values on which htc incS performs good!!!
my system details are in my signature
any help is appreciated!!
prunzzz said:
hey i needed some help on overclocking and changing some voltages on my device!!
1.i have read threads and guides on other forums before which explain how to OC and what are governers and schedulers etc.
2. most threads on this topic are from different devices' forums
so i thought their frequencies voltages must vary as they have different CPUs and hence started a new thread!!
3. What i want to know is, what voltages should i choose at different frequencies??
or it is completely not important to set voltages??
4. Earlier i used setCPU but it doesnt stick to frequencies i set and resets default 1024 after reboot.
how do i avoid this??
Currently i am using AnTuTu CPU master PRO for doing all this
please guide me if possible provide specific values on which htc incS performs good!!!
my system details are in my signature
any help is appreciated!!
Click to expand...
Click to collapse
+1
Sent from my HTC Incredible S using Tapatalk 4 Beta
I've commented on this 100 times before but I can't search on mobile. So there are a few threads out there explaining this in this forum. If you can search and find them they'll go into a little more detail than I'm about to.
OK so the OC controller you're using I'm unfamiliar with however they all do the same thing. What you should do is find out which governers your kernel supports and than use Google to figure out what their perimeters are. Generally speaking you're going to want to have different profiles set up for "screen on"and "screen off" for your basic set up. Later once you understand why you're doing you can set the governers for gaming, charging etc.
Set your screen off for around 200 min and 400 max. This will keep your phone from running high frequencies that will drain your battery while you are not using your phone. Set the governer to smart ass or on demand, read about them and see what's best for you.
Screen on set to max 1200 - 1400 if you want high performance and the low to whatever you like just not above 400 as it will not allow your CPU to idle. Set governer to smartass. You don't really need to be running above 1100 for most I stances however you will notice it is a bit peppier. While running at higher freqs you will notice your phone heating up... I have never heard of an incs over heating and frying in every case your phone will shut itself off or freeze. If you're afraid of overheating there's a profile for that too to change your freqs at certain temps.
Do NOT choose "set at boot" until you are certain that your set freqs will not hang your phone, doing this will cause your phone to freeze as soon as your ROM boots up causing a boot loop and you will have to revert to a backup to fix the situation.
As for uv'ing the premise of this is to save battery life, running at lower freqs than intended. I recommend not bothering but if you do want to try and save battery I generally suggest -10 for all values. Be aware it is very common for this to hang your phone. You have to tinker with it to get it right for your ROM.
Hope this helps any other questions just ask.
Sent from my Incredible S using xda premium
itsbeertimenow said:
I've commented on this 100 times before but I can't search on mobile. So there are a few threads out there explaining this in this forum. If you can search and find them they'll go into a little more detail than I'm about to.
OK so the OC controller you're using I'm unfamiliar with however they all do the same thing. What you should do is find out which governers your kernel supports and than use Google to figure out what their perimeters are. Generally speaking you're going to want to have different profiles set up for "screen on"and "screen off" for your basic set up. Later once you understand why you're doing you can set the governers for gaming, charging etc.
Set your screen off for around 200 min and 400 max. This will keep your phone from running high frequencies that will drain your battery while you are not using your phone. Set the governer to smart ass or on demand, read about them and see what's best for you.
Screen on set to max 1200 - 1400 if you want high performance and the low to whatever you like just not above 400 as it will not allow your CPU to idle. Set governer to smartass. You don't really need to be running above 1100 for most I stances however you will notice it is a bit peppier. While running at higher freqs you will notice your phone heating up... I have never heard of an incs over heating and frying in every case your phone will shut itself off or freeze. If you're afraid of overheating there's a profile for that too to change your freqs at certain temps.
Do NOT choose "set at boot" until you are certain that your set freqs will not hang your phone, doing this will cause your phone to freeze as soon as your ROM boots up causing a boot loop and you will have to revert to a backup to fix the situation.
As for uv'ing the premise of this is to save battery life, running at lower freqs than intended. I recommend not bothering but if you do want to try and save battery I generally suggest -10 for all values. Be aware it is very common for this to hang your phone. You have to tinker with it to get it right for your ROM.
Hope this helps any other questions just ask.
Sent from my Incredible S using xda premium
Click to expand...
Click to collapse
thanks a lot
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.
Hi there,
really sorry if this has already been around, but i've been searching this forum up and down and didn't find a thing.
Anyways, i was wondering how i could enable overclocking under cm11 nightly? Could anyone point me towards a solution? Thanks
Well ...
http://forum.xda-developers.com/droid-4/development/5-0-custom-oc-kernel-t3041512
It should work (in the past it works)
Install it on your Cyanogenmod Rom
Fervi
ferviverus said:
Well ...
http://forum.xda-developers.com/droid-4/development/5-0-custom-oc-kernel-t3041512
It should work (in the past it works)
Install it on your Cyanogenmod Rom
Fervi
Click to expand...
Click to collapse
There's a guy who said that that kernel doesnt work on cm11...it work's for you in the past?
For CM11 and other AOSP 4.4 ROMS, the most fully-featured and overclockable kernel is JBX. You can use the one intended for the RAZR.
Joojoobee's is good, and certainly the best for Lollipop, but due to its extra voltage management stuff the JBX kernel has a higher overclock ceiling.
Use the newest kernel from here.
Boot into Safestrap, make a backup in case something goes horribly wrong, then flash the package to start up the installer. In the installer, don't install any of the tweaks, at least a couple of them cause instability for our phone, and don't bother with the init.d stuff. Just install the kernel itself and Trickster Mod. Trickster, FYI, is probably the best app for managing JBX, but other apps can as well.
Done. Reboot phone, hopefully it won't bootloop, once back up increase speed until it starts freezing when you try to use it, bump voltage 10-20mv, find ceiling again. I think the JBX thread has better/more detailed instructions, but that's about the gist of it.
Maximum advised voltage is 1490mv iirc, don't try to even approach that unless you want to cook eggs on the back of your phone.
Thanks a bunch!
After messing around with both solutions, Jojobee's solution gave me a bootloop but the other one worked.
However i can't seem to get past 1300mhz when overclocking, that seems to be the limit. I was aiming to try to reach 1400, any idea how i could go about that? I can't seem to find an option to set the max frequency higher than 1300.
Well i was playing a little with JBX kernel..these are my conclusions:
- Kernel install/works fine if you don't install 10% battery mode..otherwise you are goingo to have android crashes
- Kernel performance it's below than current cm11 m13 stock kernel...i believe is due to full scale freq that it has...cpu spend a lot time switching from one freq to another...if you overclocked you will have almost the same performance than NON-OC stock kernel..that's why stargo applied and later reverted full scale on stock months ago...meaby if JBX kernell would have support to boost driver (like cm12 OC kernel) it would be better...but it hasnt...
So my conclusions...dont waste time on JBX kernel...sorry my 4 my english
Enviado desde mi XT894 mediante Tapatalk
Milp said:
However i can't seem to get past 1300mhz when overclocking, that seems to be the limit. I was aiming to try to reach 1400, any idea how i could go about that? I can't seem to find an option to set the max frequency higher than 1300.
Click to expand...
Click to collapse
I don't think you can set the CPU higher than 1.3ghz, at least not in the way you're thinking.
In the case of the JBX kernel, you overclock the Main Processor Unit (MPU) speed. I don't remember what tab it's under in Trickster, but it should be the same one as the voltage settings. I couldn't even begin to guess where it'd be as far as other apps.
The default is 100mhz. This is multiplied by each frequency step; e.g. 1.3ghz is actually a 13x multiplier of the base 100mhz.
So to obtain 1.4ghz(ish), simply increase the MPU clock from 100mhz to 108mhz, since 108*13=1404.
If you're lucky, you'll be be able to do this without needing to touch the voltage, if not...read the FAQ in the JBX post, because I don't remember offhand exactly how to set voltages :v
Once you know how, I would think a 5-10mv bump would be all that'd be needed to stabilize most CPUs for 1.4ghz.
fyi, ignore if you already have stuff for these:
Antutu is a decent app for both testing stability and checking to make sure you're not hitting the heat throttle.
Cooltool isn't a bad thing to use either, if configured to show CPU speeds, since it'll show you if the CPU has been forcefully throttled back (if the CPU gets too hot, it'll forcefully change the maximum multiplier to 10x/11x to protect itself from baking; if it does, back your voltage off and be happy with whatever speed you've attained).