Hi,
So, I was wondering if anyone had any experiences with this governor on FroyoPro v2.5. Having experimented with basically everything there is on the phone, this is one of the last things I would like to try.
Currently I'm using 245MHz-600MHz ondemand governor, and was experimenting a bit with the performance one. I loved how performance worked, but I did notice some adverse effect on battery life (somewhat 30% lower), so I switched back.
What I would like to have is a somewhat snappier phone without sacrificing the battery too much. Performance governor, after all, took a too big of a chunk of the battery for me to handle.
What are your opinions/experiences with this governor? Also, is it v1 or v2 that is included in FroyoPro?
Well, I tried it today.
At times it worked okay, but most of the time there was lag.
AnTuTu score dropped a spectacular 1000 points.
Quadrant score dropped 100 points.
Naturally there is possibility that I perhaps did something wrong. However I followed the instructions correctly. Perhaps it would work better on some other device, but mine apparently doesn't like it.
Back to ondemand then
U should use smastass its good both with battery life and performance...
sent from my phone using hands and brain...
dagger said:
U should use smastass its good both with battery life and performance...
sent from my phone using hands and brain...
Click to expand...
Click to collapse
But the performance was horrible! Is there something else I should do besides insmod and echoing to activate it? Perhaps tweaking with its parameters a bit? Because ondemand currently appears to be a much better choice for my device.
xWhiskey said:
But the performance was horrible! Is there something else I should do besides insmod and echoing to activate it? Perhaps tweaking with its parameters a bit? Because ondemand currently appears to be a much better choice for my device.
Click to expand...
Click to collapse
Try adding these settings in hw_config.sh:
Code:
echo 12000 > /sys/devices/system/cpu/cpu0/cpufreq/smartass/up_rate_us
echo 60000 > /sys/devices/system/cpu/cpu0/cpufreq/smartass/down_rate_us
echo 999999 > /sys/devices/system/cpu/cpu0/cpufreq/smartass/ramp_up_step
echo 0 > /sys/devices/system/cpu/cpu0/cpufreq/smartass/ramp_down_step
And just to be completely sure that everything is in place, the other required lines should look like these:
Code:
insmod /system/lib/modules/ax8_smartass.ko
echo "smartass" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
Fortun said:
Try adding these settings in hw_config.sh:
Code:
echo 12000 > /sys/devices/system/cpu/cpu0/cpufreq/smartass/up_rate_us
echo 60000 > /sys/devices/system/cpu/cpu0/cpufreq/smartass/down_rate_us
echo 999999 > /sys/devices/system/cpu/cpu0/cpufreq/smartass/ramp_up_step
echo 0 > /sys/devices/system/cpu/cpu0/cpufreq/smartass/ramp_down_step
And just to be completely sure that everything is in place, the other required lines should look like these:
Code:
insmod /system/lib/modules/ax8_smartass.ko
echo "smartass" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
Click to expand...
Click to collapse
Ok. I edited all of this in so we'll see how it goes through the day. Will report back in a day or two.
If the performance is horrible with smartass v2 then ate the min frequency to a little higher value...
I suggest 245 or 320...
Then report here..
sent from my phone using hands and brain...
Tried both of your methods. It seems that with Fortun's parameter changes and by ramping up the minimum frequency a notch the governor was a bit more stable. However, there was still lag. Not constant, but in spikes. The battery might have been a bit more durable in this run, but not that much more durable taking into account the performance issues I've been having. You could see frequent spikes in games, while surfing the internet, sometimes even on the UI. IMHO the ondemand governor seems what works best for this device. I might give this governor a shot in the near future again, but for now he'll be asleep.
I'm not into kernels that much, since I cannot unlock the bootloader for free without risking a hardbrick, but might it be possible that stock kernels react badly to things like this? I mean, this governor doesn't work that well, the overclock module slows down the phone, minfree setting changes don't stick. Do you guys run stock or custom kernels?
I use custom kernel...
Btw what's your phone's manufacturing date...
sent from my phone using hands and brain...
dagger said:
I use custom kernel...
Btw what's your phone's manufacturing date...
sent from my phone using hands and brain...
Click to expand...
Click to collapse
11w39, and if I remember correctly, you can unlock safely only until 11w28. I would most certainly attempt to unlock the bootloader and flash a custom kernel if that wouldn't have been an issue. But it's no big deal. I'm liking the device so far. Much better than stock now.
Also, I have a question related to governors. When I reboot, and for example echo the ondemand governor to the scaling governor, do its parameters reset to default? Or do I have to echo the custom parameters for the governor at every boot?
Are you completely sure that the lags dissapear when using ondemand as opposed to smartass? The X8 over here is running with the settings I suggested on stock kernel, it's heavily used for gaming and no problems with the performance.
By the way, the smartass governor from the module is different from the version found in the custom kernels. Then it should be treated differently.
As for your last question, I'm not sure I get it. Anyway, the values set in hw_config.sh are loaded each time the phone boots.
Fortun said:
Are you completely sure that the lags dissapear when using ondemand as opposed to smartass? The X8 over here is running with the settings I suggested on stock kernel, it's heavily used for gaming and no problems with the performance.
By the way, the smartass governor from the module is different from the version found in the custom kernels. Then it should be treated differently.
As for your last question, I'm not sure I get it. Anyway, the values set in hw_config.sh are loaded each time the phone boots.
Click to expand...
Click to collapse
Absolutely. The problems disappeared just after I applied ondemand as the governor. I'm not sure which ROM are you running, but it seems to me most of these things don't quite work that well on mine. None of the modules I applied so far didn't work well.
I was referring to governor parameters. Sampling rate, down differential and the like. Do they return to their default states when the phone is rebooted (assuming I didn't echo anything to their parameters in hw_config)? If I was, for example, change their parameters while the phone is running, does that change stick permanently or does it reset at reboot? I'm asking this because I would try to experiment with SetCPU and parameter tweaks while the phone is running.
Running a slightly modified version of the latest GingerDX right now. Could you post the name of the game that can replicate the lags?
And, yes. The parameters reset at each boot if not put directly in hw_config.sh (not the only where you can put them). And for good reason. If you configure it badly you could be put in a situation where you enter a bootloop (specially true when overclocking). Don't ever commit to some changes before testing stability.
By the way, SetCPU has an option to load settings at boot if those settings are set using the program. In other words, if you choose to set the settings using the echo parameter with the terminal, for instance; these settings will be reset next time you reboot the phone.
Fortun said:
Running a slightly modified version of the latest GingerDX right now. Could you post the name of the game that can replicate the lags?
And, yes. The parameters reset at each boot if not put directly in hw_config.sh (not the only where you can put them). And for good reason. If you configure it badly you could be put in a situation where you enter a bootloop (specially true when overclocking). Don't ever commit to some changes before testing stability.
By the way, SetCPU has an option to load settings at boot if those settings are set using the program. In other words, if you choose to set the settings using the echo parameter with the terminal, for instance; these settings will be reset next time you reboot the phone.
Click to expand...
Click to collapse
The launcher is ADW. I playtested the governor on Tilt Arena, Missile Defense, Racing Moto, Radio Ball 3D. At normal circumstances, RMoto lags here and there, but with smartass it was unplayable. Tilt Arena usually has a spike here and there, but also unplayable with smartass. RBall worked ok, but usually worked flawlessly. Missile Defense tends to slow down when the cpu stress is high, but smartass didn't do much to help.
OK. Tried with Racing Moto and no problems with it. For the sake of completion I tried playing it with the CPU clock capped at 320 MHz and still no problems.
Something looks definitely wrong. Maybe you should try getting the smartass module from the original thread: http://forum.xda-developers.com/showthread.php?t=1159899 .
Maybe you could post the whole contents of you hw_config.sh to take a look at it.
Fortun said:
OK. Tried with Racing Moto and no problems with it. For the sake of completion I tried playing it with the CPU clock capped at 320 MHz and still no problems.
Something looks definitely wrong. Maybe you should try getting the smartass module from the original thread: http://forum.xda-developers.com/showthread.php?t=1159899 .
Maybe you could post the whole contents of you hw_config.sh to take a look at it.
Click to expand...
Click to collapse
I'll try that. But I won't bother you further with the hw_config.sh What you've done so far was enough, and I'm thankful. Over the course of the next few days I'll try the smartass module from the original thread. For some reason, there's a 50KB size difference between the two.
Thanks for your help.
Tried the smartass governor again today, and played with its parameters a bit. It seems it works ok for a while (about 3-4) hours, but then it screws everything up. UI starts lagging, games become unplayable, some apps start force closing, etc. It's a shame because I really wanted it to work, especially after investing so much time into it.
However, taking this post into account:
http://forum.xda-developers.com/showthread.php?t=1369817
... and the tweaks posted there, I made some tweaks to the ondemand governor. Here they are:
echo "60" > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold
echo "100000" > /sys/devices/system/cpu/cpufreq/ondemand/sampling_rate
echo "4" > /sys/devices/system/cpu/cpufreq/ondemand/sampling_down_factor
echo "15" > /sys/devices/system/cpu/cpufreq/ondemand/down_differential
echo "50" > /sys/devices/system/cpu/cpufreq/ondemand/freq_step
CPU is clocked at 245/600, stock kernel. I've noticed that with these parameters AnTuTu scores drop about 100 points, but the results are VERY consistent. They don't oscilate in a ~400 point interval anymore. Also, games are very stable, only with very minor lags here and there on some harder games. Battery seems more or less the same. I might theoretically get 2-3 hours less, but that's hard to quantify at this point. Wake-up speed is also very good.
Could anyone try these out and see how it goes? Perhaps we could conjure up even better settings?
EDIT: Also, interesting thing to note is that setCPU shows about 40% time on 245MHz, 54% on 600MHz, and the rest on in-between freqs. However, I don't think the app recognizes deep sleep states, which means these frequency percentages are used only when the phone is active, which is great! If you look at it, it also makes perfect sense. When CPU reaches 60% of load, frequency is ramped up. However, one freq step is 50% of the max = 300MHz, and because the system uses round-up states, frequency jumps from 245MHz to 600MHz instantly, spending time on in-between frequencies only when ramping down.
Also, I've read somewhere that having a CPU set on e.g. 245MHz on full load is much worse for battery saving than having it set on e.g. 600MHz until it is done working, and then ramp down to min. These settings might actually be a bit beneficial for the battery.
EDIT2: CPU Spy recognizes sleep states, which are at 86% of the time.
Stock Kernel:
Smartassv2 Min CPU freq 245 Max 729
Custom:
Smartassv2 min cpu freq 480 max 768.
Sent from my iPhone using Tapatalk
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.
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
Because both the ViperDHD and Team Venom beta forums are being used by people like us to discuss battery life, kernel tweaking and smoothness, I decided to change this into a universal Viper/Sense discussion thread. ANyone from the family of devices which include DHD, Desire Z, Desire S, IncS, dinc2, mt4g etc are welcome here. ACtually, everyone is.
The discussion was sort of started here
http://forum.xda-developers.com/showthread.php?p=37246862#post37246862
Feel free to post settings and everything. We are trying to get the most of our old devices!
Reserved
Reserved for something else
CyanVivo X, default kernel.
Screen off: 245 min/max
Screen on: 245min, 1228 max.
2 hours of screen on time, 3 hours when I'm lucky, 3G is killing my battery...
Frequencies: 61-1200 MHz redux kernel.
With ondemandx governor and deadline scheduler
Undervolted consolidatedly by -25
I manage to get a battery life of 14-16 hours.
Main usage: voice calls- 1-1.5 hrs
The only problem is... Battery never reaches 100%.
Any suggestions?
Sent from my oc'd viper vivo
Using tricksterMOD, you can see that governors like interactive and ondemand have their own settings. I have been playing around with these settings, and I am still not finished with what I like yet. However you can use this post as a guide:
http://forum.xda-developers.com/showpost.php?p=36743252&postcount=3113
With Interactive, you can set your go_highspeed_load to 806 or 768MHz. I have set my min to be 245MHz, max 1200MHz but highspeed load is 806MHz. This results in a kind of even split between the times that 245, 806 and 1200MHz are used. With ondemand or another governor, it generally spikes up to 1200MHz (your max freq) a lot, rather than scaling between the lower freqs. This results in more battery usage because you are staying at a higher freq for longer than needed. Performance is generally the same with interactive and ondemand if configured right.
What do these mean? Basically, with my device now when I touch the screen, it will ramp up to 806MHz. If the process is more than just moving something on the screen and more processing power is needed, it will automatically go to 1200MHz, and when its done and I am still touching the screen, it will go back down to 806MHz. When all I am doing is browsing xda or something, when I scroll it ramps up to 806MHz and when I leave it to read something, it will go down to 245MHz. Then obviously when its sleeping it goes into deep sleep (hopefully)
My battery life suckss.
Sent from one of the few remaining Incredible S'
markj338 said:
Using tricksterMOD, you can see that governors like interactive and ondemand have their own settings. I have been playing around with these settings, and I am still not finished with what I like yet. However you can use this post as a guide:
http://forum.xda-developers.com/showpost.php?p=36743252&postcount=3113
With Interactive, you can set your go_highspeed_load to 806 or 768MHz. I have set my min to be 245MHz, max 1200MHz but highspeed load is 806MHz. This results in a kind of even split between the times that 245, 806 and 1200MHz are used. With ondemand or another governor, it generally spikes up to 1200MHz (your max freq) a lot, rather than scaling between the lower freqs. This results in more battery usage because you are staying at a higher freq for longer than needed. Performance is generally the same with interactive and ondemand if configured right.
What do these mean? Basically, with my device now when I touch the screen, it will ramp up to 806MHz. If the process is more than just moving something on the screen and more processing power is needed, it will automatically go to 1200MHz, and when its done and I am still touching the screen, it will go back down to 806MHz. When all I am doing is browsing xda or something, when I scroll it ramps up to 806MHz and when I leave it to read something, it will go down to 245MHz. Then obviously when its sleeping it goes into deep sleep (hopefully)
Click to expand...
Click to collapse
I am gonna try nodding the governors now!
Sent from my Incredible S using xda app-developers app
Mark r these settings good?.... Btw what nr i should put to boost?
janarp said:
Mark r these settings good?.... Btw what nr i should put to boost?
Click to expand...
Click to collapse
Looking good to me
Smooth or not? Maybe post a screenie of cpuspy or something to see what you're running at
See here for more info
http://forum.xda-developers.com/showpost.php?p=19846297&postcount=2
Are you finding any slowdown and major battery drainage where android os keeps the device awake?
markj338 said:
Looking good to me
Smooth or not? Maybe post a screenie of cpuspy or something to see what you're running at
See here for more info
http://forum.xda-developers.com/showpost.php?p=19846297&postcount=2
Are you finding any slowdown and major battery drainage where android os keeps the device awake?
Click to expand...
Click to collapse
It feels really smooth right now.. i cant tell for battery because i flashed patcha kernel right now... Lets see how good my battery is after few days of using... Thanks for link i read it later... Dont have that time right now... And here is pic ... If u mean this offcourse..
or u can suggest me better kernel tuning app...
janarp said:
It feels really smooth right now.. i cant tell for battery because i flashed patcha kernel right now... Lets see how good my battery is after few days of using... Thanks for link i read it later... Dont have that time right now... And here is pic ... If u mean this offcourse..
or u can suggest me better kernel tuning app...
Click to expand...
Click to collapse
Not that one
The screen that shows how long you've been at what freq
probably i flash new Beast Mode MOD kernel if it release today... it looks more interesting..=)
---------- Post added at 03:57 PM ---------- Previous post was at 03:56 PM ----------
markj338 said:
Not that one
The screen that shows how long you've been at what freq
Click to expand...
Click to collapse
with this kernel tuner app i cant see that i guess..=)
hey all i m using advenced-sense-kernel-r1
i would like to set governors like markj338 posted.
"Using tricksterMOD, you can see that governors like interactive and ondemand have their own settings. I have been playing around with these settings, and I am still not finished with what I like yet. However you can use this post as a guide:
http://forum.xda-developers.com/show...postcount=3113
With Interactive, you can set your go_highspeed_load to 806 or 768MHz. I have set my min to be 245MHz, max 1200MHz but highspeed load is 806MHz. This results in a kind of even split between the times that 245, 806 and 1200MHz are used. With ondemand or another governor, it generally spikes up to 1200MHz (your max freq) a lot, rather than scaling between the lower freqs. This results in more battery usage because you are staying at a higher freq for longer than needed. Performance is generally the same with interactive and ondemand if configured right.
What do these mean? Basically, with my device now when I touch the screen, it will ramp up to 806MHz. If the process is more than just moving something on the screen and more processing power is needed, it will automatically go to 1200MHz, and when its done and I am still touching the screen, it will go back down to 806MHz. When all I am doing is browsing xda or something, when I scroll it ramps up to 806MHz and when I leave it to read something, it will go down to 245MHz. Then obviously when its sleeping it goes into deep sleep (hopefully)"
is there an easy way
right now i have these cpu stats and these oc settings
do i have to remove oc deamon and cpu stats to use tricksterMOD
mkdsa said:
hey all i m using advenced-sense-kernel-r1
i would like to set governors like markj338 posted.
"Using tricksterMOD, you can see that governors like interactive and ondemand have their own settings. I have been playing around with these settings, and I am still not finished with what I like yet. However you can use this post as a guide:
http://forum.xda-developers.com/show...postcount=3113
With Interactive, you can set your go_highspeed_load to 806 or 768MHz. I have set my min to be 245MHz, max 1200MHz but highspeed load is 806MHz. This results in a kind of even split between the times that 245, 806 and 1200MHz are used. With ondemand or another governor, it generally spikes up to 1200MHz (your max freq) a lot, rather than scaling between the lower freqs. This results in more battery usage because you are staying at a higher freq for longer than needed. Performance is generally the same with interactive and ondemand if configured right.
What do these mean? Basically, with my device now when I touch the screen, it will ramp up to 806MHz. If the process is more than just moving something on the screen and more processing power is needed, it will automatically go to 1200MHz, and when its done and I am still touching the screen, it will go back down to 806MHz. When all I am doing is browsing xda or something, when I scroll it ramps up to 806MHz and when I leave it to read something, it will go down to 245MHz. Then obviously when its sleeping it goes into deep sleep (hopefully)"
is there an easy way
right now i have these cpu stats and these oc settings
do i have to remove oc deamon and cpu stats to use tricksterMOD
Click to expand...
Click to collapse
You can't edit the governor settings with the daemon controller app. That's why we use the trickster mod app to edit things
By governor settings I don't mean switching governors, I mean the actual settings of it.
That stuff should disable itself but its best to remove them to avoid conflicts
Sent from my HTC Incredible S
My results on ViperIncS with z13boot.img, redux_0.8 kernel, daemon controller, 3G always On, 7 hours of sleepmode (0.8%/hour), sync ON, loged on on every account on my phone but with disabled updates for accounts.. only IM+pro is working all the time inpush mode.
hey markj338 i m new to this,so if i understand i should remove oc deamon and cpu stats but can u walk me trough setup trickstermode
removed oc deamon and cpu stats and installed trickster i have these screenshots
mkdsa said:
hey markj338 i m new to this,so if i understand i should remove oc deamon and cpu stats but can u walk me trough setup trikstermode
Click to expand...
Click to collapse
Delete them
Download an app from play store called trickster MOD kernel settings or something
Download busybox installer by stericsson
Install busybox using the app
open trickster, then you can set whatever you like.
screnshoots
ok removed oc deamon and cpu stats
installed busybox and Trikster got these settings..what should go_highspeed_load be now is 99...noticed when i restart dhd governor goes back to ondemand
tnx man
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.