Database Develop

SetCPU usage/benefits?

I was thinking about installing SetCPU but I have heard stories of it not working very well on the Captivate. Does anyone use this, and if so what kind of battery life improvement are you seeing? Post config settings too please!

Its working just fine. I have a live background so my battery usage isnt very great so long as the screen is on. I had some trouble with the system being slow to respond every time I turned the screen back on when I had "screen off" profile set to max 200 and min 100. then it dawned on me that it would always just underclock to 100 I set it to max 200 and min 200 when the screen is off and also started using launcher pro and it is no longer sluggish at all.
This has saved me a gratuitous amount of battery life when the phone is idle.
Default profile
Max 1Ghz
Min 800Mhz
scaling Conservative
Charging/full profile
Same as default but scales on performance
Battery <50%
Max 800Mhz
Min 400Mhz
scaling Ondemand
screen off
Max 200
Min 200
Scale powersave

kenjindomini said:
Its working just fine. I have a live background so my battery usage isnt very great so long as the screen is on. I had some trouble with the system being slow to respond every time I turned the screen back on when I had "screen off" profile set to max 200 and min 100. then it dawned on me that it would always just underclock to 100 I set it to max 200 and min 200 when the screen is off and also started using launcher pro and it is no longer sluggish at all.
This has saved me a gratuitous amount of battery life when the phone is idle.
Default profile
Max 1Ghz
Min 800Mhz
scaling Conservative
Charging/full profile
Same as default but scales on performance
Battery <50%
Max 800Mhz
Min 400Mhz
scaling Ondemand
screen off
Max 200
Min 200
Scale powersave
Click to expand...
Click to collapse
Thanks for these, I was looking for a some decent settings. Mine were close to that to start, but I had no idea what I was doing, haha

I had some stability problems with it that I am now fairly certain are related to adjusting the polling frequency in advanced settings. After disabling setting advanced settings on boot, and a reboot, it has not caused the phone to hang once. I am also fairly sure that the phone boots with the conservative governor enabled and min/max frequencies set to 100MHz and 1GHz, even without SetCPU - so the main benefit here is profiles to force lower clocks with screen off, or during overheat or low battery.

CPU throttles itself. Any effects of setCPU is placebo effect

Err if you set the clocks yourself, you can produce a difference depending on what it's catered towards. I'm sure if I set the max clock to 200 (assuming the app works) for all situations there will be a difference.

Does the stock ROM have a perflock like the EVO that we need to disable?
Also, does the stock ROM automatically underclock at times, or???

I've now verified after clearing user data, the stock firmware already sets the conservative governor and allows it the full range of frequencies supported by the CPU. Only benefit from SetCPU should be profiles - reduce max clock when hot or low battery, that sort of thing.
Sent from my Samsung Captivate

I was going to make a screen off profile of 200mhz, to save battery. Should I bother doing this?
Edit: Nevermind, I'm just going to uninstall it. It's locked up my phone twice already

Default Profile: 800 MHz
Profiles:
Temp > 46 C -- 400 Max 100 Min Conservative
Battery < 40 -- 400 Max 100 Min Conservative
Screen Off -- 400 Max 100 Min Conservative
This now gives my phone life of about 2 days with moderate use (1 hour calls, 1 hour browsing and another 30-45 mins of using apps that need screen on like games, etc)

brandonb81 said:
I was going to make a screen off profile of 200mhz, to save battery. Should I bother doing this?
Edit: Nevermind, I'm just going to uninstall it. It's locked up my phone twice already
Click to expand...
Click to collapse
One thing u got to keep in mind, CPU scales up when woken from low speeds (like when u set for 200 n this takes a second or two). After some R&D i realized 400 MHz when sleeping is optimal with hardly noticeable lag.

Unhelpful said:
I had some stability problems with it that I am now fairly certain are related to adjusting the polling frequency in advanced settings. After disabling setting advanced settings on boot, and a reboot, it has not caused the phone to hang once. I am also fairly sure that the phone boots with the conservative governor enabled and min/max frequencies set to 100MHz and 1GHz, even without SetCPU - so the main benefit here is profiles to force lower clocks with screen off, or during overheat or low battery.
Click to expand...
Click to collapse
well, i have tried playing heavy games like asphalt 5, dungeon hunter, assasin's creed... these all games seemed to work with no lag even at 400 MHz when my battery was less than 40. Most apps I have or used or saw were very comfortable even at 400 MHz. But with multiple apps open, sometimes there was lag, so i set the max at 800 MHz, instead of 1 GHz.
Also, I set my connection to EDGE from 3G. This helped reduce phone from getting heated up with long calls.

I tried using this app myself but uninstalled it after a week. While I'm sure there was some underlying cause, it made my phone never wake up from sleep mode when it turned off.
Honestly thou, I know several android phone owners with s lot of phones That didn't see any real change in their battery life as s result. And based on my experiences, I'd say stay away from it.
Just my 2 cents thou
Sent from my SAMSUNG-SGH-I897 using XDA App

[Q] Proper setup for Set CPU on Captivate

Hi fellow androiders......have loaded Set CPU and would like to know what if any is the optimum profile(s) setup for the Captivate.....Thanks

I turn my CPU back to 1 ghz if temp > 50
I also go 600mhz max when the screen is off.
I don't see much need for the rest, but I'm curious to see what others add.

What is the lowest the CPU can go on the Captivate?
Sent from my iPhone with the bigger Gee Bees.

Pretty nice app, although I can't seem to be able to go above 1ghz in cognition 2.3B2... But I have set to.
Temp>60 400mgz (I live in the desert)
Temp>50 800mhz(totally nessicary)
screen off= 100-400
charging= 800-1000
and some other little battery things thrown in.

notasimpleway said:
What is the lowest the CPU can go on the Captivate?
Sent from my iPhone with the bigger Gee Bees.
Click to expand...
Click to collapse
lowest is 100mhz... would NOT recommend setting MAXCPU on anything to that!!
It will idle at 100, but if it can't clock up, you'll never be able to use it. 400 is functional for call/txt.

I never have heat issues with my Captivate, and I don't do any oc-ing/uv-ing. I personally use:
Screen off: Max 200, Min 100, Scaling Conservative, Priority 100
Charging/Full: Max 100, Min 400, Scaling Performance, Priority 75
Battery<101%: Max 800, Min 100, Scaling Conservative, Priority 50
With Darky's ROM and Speedmod K12N kernel, 800MHz cap gives plenty of performance. 200MHz while the screen is off is just fine for playing music in PowerAMP with headset controls.

[Q] Optimal CPU settings

Hello, I tried searching but didn't find a thread about this. Sorry if there is one that I didn't find. I'm playing around with SetCPU and trying to figure out optimal settings. I know its a matter of preference but I wanted to see what everyones opinion is and what they have theirs set as. I have:
CheckROM Revo noteHD v5
Abyss Kernel
On Demand governor set
Max 1500MHz
Min 200MHz
I want a happy medium between battery life and performance.
I set a profile for screen off to min 200 and max 500.
I've been reading mixed reviews as to whether or not lower speeds actually increase battery life. I originally had the min at 50 but increased it to 200.
Another question is what would be a good temperature to set the temp profile to? Not sure when the phone begins to get too hot.
Thanks in advance

I used FM kernel with ondemand with min of 500Mhz and max of 1400Mhz with 2nd core always enabled, didnt notice that much of a battery loss.

go for rocket rom v22 with abbys note 4.2 kernel
set cpu min 50 max 800
on demand (if u want both cores active)
abbysnote (if u want single core running and 2nd to be used only if required otherwise 2nd would be off)
i got normal usage batt backup of 3 days least

Help for OC and UV!!!

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] [KERNEL][D5803&D5833] AndroPlusKernel

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.