While ago I posted a reply on a thread on how to control the CPU speed and override Tegra 3 controlling it and setting it to dual core mode. I forgot to reply back on that thread, but instead I thought it would be better to create a new thread, since not much people would read it (Credit to k0rner for reminding me... (k0rner thread)
/sys/kernel/debug/tegra_hotplug/max_cpus
This is not touched by the Android OS, and will remain in whatever state we set until reboot (back to 4).
Set this to "1" will make the phone only use 1 core (Doesn't work, only 2,3,4 does)
Set this to "2" will use 2 core
Set this to "3" will use 3 core
Set this to "4" will use 4 core (default)
1) Use Root_Browser (Free) or Root Explorer
2) Go to /sys/kernel/debug/tegra_hotplug/
3) Hold max_cpus
4) 'Open With', Text Editor
5) Change Value (Default 4) to how many cores you want (ie 2 = dualcore)
6) Download Tegrastats and see the result
EDIT: http://forum.xda-developers.com/showpost.php?p=26056320&postcount=48 (Control Core, via App, credit Meltus)
EXTRA: http://forum.xda-developers.com/showpost.php?p=25637797&postcount=10 (credit kolargol)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://forum.xda-developers.com/showthread.php?t=1627517
not sure if this is the same mate but if you access the powersave settings there is an option as well were you can switch only one core on and drop the cpu clock speeds to 1GHz. Just check the thread out that i gave the link to
NoobTerminator said:
http://forum.xda-developers.com/showthread.php?t=1627517
not sure if this is the same mate but if you access the powersave settings there is an option as well were you can switch only one core on and drop the cpu clock speeds to 1GHz. Just check the thread out that i gave the link to
Click to expand...
Click to collapse
Thats only when you reach to lower than 10%, thats when it clicks in, correct me if im wrong.
MrPhilo said:
While ago I posted a reply on a thread on how to control the CPU speed and override Tegra 3 controlling it and setting it to dual core mode. I forgot to reply back on that thread, but instead I thought it would be better to create a new thread, since not much people would read it (Credit to k0rner for reminding me... (k0rner thread)
/sys/kernel/debug/tegra_hotplug/max_cpus
This is not touched by the Android OS, and will remain in whatever state we set until reboot (back to 4).
Set this to "1" will make the phone only use 1 core (Single Core Mode + Low Companion Core)
Set this to "2" will use 2 core
Set this to "3" will use 3 core
Set this to "4" will use 4 core (default)
1) Use Root_Browser (Free) or Root Explorer
2) Go to /sys/kernel/debug/tegra_hotplug/
3) Hold max_cpus
4) 'Open With', Text Editor
5) Change Value (Default 4) to how many cores you want (ie 2 = dualcore)
6) Download Tegrastats and see the result
Now enjoy your phone with less heat
NOTE: I will edit later on how to change clockspeed without Tegra 3 controlling it through SetCPU.
Click to expand...
Click to collapse
Sorry for the obvious question, but I am orientating for buying X or S.
Is the heating problem that serious to go back to 2 cores?
JacoA said:
Sorry for the obvious question, but I am orientating for buying X or S.
Is the heating problem that serious to go back to 2 cores?
Click to expand...
Click to collapse
It is a bit of an overkill having four cores, I find than two cores is enough for me and games don't lag on it. It does get quite warm, depending what you do, alot less with two cores.
I wouldn't recommend the One S at all. I would just wait for the S3.
All good great too lol I will add that tegra stats is a massive battery drain.
Also controling the speed will be nice ill be sure to let the setcpu dev know once you let us know
Sent from my HTC One X using xda premium
Do I need to root my phone for this?
luba6ky said:
Do I need to root my phone for this?
Click to expand...
Click to collapse
yes
Hello,
Further to Kolargol's post here : http://forum.xda-developers.com/showthread.php?t=1633245
i set up the tasks in tasker but it's not working
Checking, I don't have tegra_hotplug folder in sys/kernel =(
I'm using root explorer.
What am I doing wrong ?
Thanks for your help
My sys/kernel/debug folder is empty too. I'm on Android Revolution 5.0.
It's there on leedroid have you tried adding the folder to see if it works?
Sent from my HTC One X using xda premium
I also tried with sys/devices/cpu/cpuX/online with 4 commands per task (1 per CPU) but it's not working either =(
treebill said:
It's there on leedroid have you tried adding the folder to see if it works?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Getting "new folder creation failed" in bought root explorer with su right and r/w enabled. Think I'll install LeeDrOiD tonight.
SAme here
Sure you checked carefully? I've been on both Leedroid and ARHD and they do exist.
/sys/kernel/debug/tegra_hotplug
MrPhilo said:
Sure you checked carefully? I've been on both Leedroid and ARHD and they do exist.
/sys/kernel/debug/tegra_hotplug
Click to expand...
Click to collapse
Quite sure. Nothing there. And can't be created.
Flashed Leedroid and the folder is there, trick with tasker working perfectly well !
ARHD 5.X.X
Originally Posted by mike1986.
ok, my fault this time, sorry!
Open root explorer, go to system/etc/ and open init.post_boot.sh
navigate to line 115 and remove:
umount /sys/kernel/debug
save and reboot!
sorry! BTW what does it allows you to do?
---------- Post added at 08:07 PM ---------- Previous post was at 08:06 PM ----------
rahan95 said:
Flashed Leedroid and the folder is there, trick with tasker working perfectly well !
Click to expand...
Click to collapse
can you share wht you did?
Well, I flashed Leedroid too, and now I'm able to change it no problem. However it doesn't really obey my 1 CPU rule and activates a 2nd core whenever it feels it really needs it. That's ok I guess. Really smooth, though. No lag at all.
I've also played around a bit with the throttle settings in the CPU-tegra folder. It has a throttle_table where you can set individual frequency settings, but so far no matter what I set it to, it seems to throttle to 340Mhz which is slooow.
A reboot sets everything straight. Hopefully this'll be able to save us some sweet battery time.
Little bit where it all comes from:
Code:
mount debugfs debugfs /sys/kernel/debug
is inside init.endeavoru.common.rc in ramdisk
init.endeavoru.common.rc contains also following code:
Code:
write /sys/module/cpu_tegra3/parameters/no_lp 0
write /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor ondemand
write /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor ondemand
write /sys/devices/system/cpu/cpu2/cpufreq/scaling_governor ondemand
write /sys/devices/system/cpu/cpu3/cpufreq/scaling_governor ondemand
chown system /sys/devices/system/cpu/cpufreq/ondemand/sampling_rate_min
chown system /sys/devices/system/cpu/cpufreq/ondemand/sampling_rate
chown system /sys/devices/system/cpu/cpufreq/ondemand/sampling_rate_max
chown system /sys/devices/system/cpu/cpufreq/ondemand/sampling_down_factor
chown system /sys/devices/system/cpu/cpufreq/ondemand/io_is_busy
chown system /sys/devices/system/cpu/cpufreq/ondemand/up_threshold
chown system /sys/devices/system/cpu/cpufreq/ondemand/touch_poke
chown system /sys/htc/power_save
write /sys/devices/system/cpu/cpufreq/ondemand/sampling_rate_min 10000
write /sys/devices/system/cpu/cpufreq/ondemand/sampling_rate 50000
write /sys/devices/system/cpu/cpufreq/ondemand/sampling_down_factor 4
write /sys/devices/system/cpu/cpufreq/ondemand/io_is_busy 1
write /sys/devices/system/cpu/cpufreq/ondemand/up_threshold 90
write /sys/devices/system/cpu/cpu1/online 0
write /sys/devices/system/cpu/cpu2/online 0
write /sys/devices/system/cpu/cpu3/online 0
[COLOR="Red"]write /sys/kernel/debug/tegra_hotplug/max_cpus 1[/COLOR]
write /sys/module/cpuidle/parameters/lp2_in_idle 1
So changing /sys/kernel/debug/tegra_hotplug/max_cpus is not permanent, it will be back to the default value each reboot.
Also keep in mind that /sys/kernel/debug contains details about kernel settings, I don't think that changing it can reflect in anything.
I may not be right of course, please feel free to correct me if I'm wrong
Related
I take no responsibility for ANY damage / data loss may occur. Use this at your own risk. Beta quality software!/Alpha quality features!
The news:
4.9 - THIS IS HIGLY TEST RELEASE
+ Profiles support
+ Bus frequency switching for Siyah kernel
+ Widget with profile switcher and app launcher (passive!)
+ Recovery instructions: lets you place CWM flashable boot settings deleter
+ CPU history: now can reset and refresh graphs
+ Root detection improvement (I hope...)
Voltage Control Extreme unlock Key on Android Market!
For now features exclusive to Extreme version are:
+ More than two profiles
+ CPU History page
+ overvolting capability (max +50mV, 1500mV absolute maximum)
+ increased uv range (max -250mV)
Click to expand...
Click to collapse
Sources available, project on google code:
http://code.google.com/p/voltage-control/
Look for kernels with this label:
Kernel developers who added VC support please show this image in your topic
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Uploaded with ImageShack.us
Features:
- minimum/maximum CPU frequency choosing
- selecting IO scheduler
- selecting CPU governor
- changing voltage per frequency
- chosing which frequencies should be used and which shouldnt
- saving settings to be automatically applied at boot (init.d script)
- saving/loading a OC profile
- well designed and highly optimised UI (I hope..)
- robust kernel detection, support of not-so-well-working kernels
- Siyah kernel interfaces (Charging current and GPU OC/UV)
- device info page
- (extreme) CPU usage history page
About donations:
This software is available free of charge.
It cooperates with OC kernel by raspdeep.
It uses some code from: MarketEnabler (Fool your market to make all apps visible!)
If you find this software useful, please consider funding a beer and pizza. There is a "Donate to me" link just over my avatar.
Donator list:
nitr8
kalpik
laststufo
glitterballs
screwyluie
Gembol
Coreym
Thanks!
How to?
Generally idea is simple: make changes to one tab and hit apply. If any changes have been made apply/discard buttons appear on bottom.
The first tab, "General" allows to change Scheduler,Governor/min and max frequencies.
Make changes and click apply
So, you want to pick a maximum/minimum frequency?
Just chose from slider and hit apply.
Governor/scheduler can be choosen by picking from the list, then hitting apply.
You can always discard changes before applying if you want start from loaded settings.
The "Advanced" tab has sliders to control undervolting settings and green/red icons, representing enabled/disabled state.
(green = enabled, red = disabled)
Pick your settings and hit apply, or discard and start over.
Profile support:
If you want to save as boot or as profile, you need to make adjustments and on "General" or "Advanced" tab and then apply them where applicable.
To save as boot -> press menu key, then select "Save as boot settings".
To save as profile -> press menu key, then select "Save profile".
Boot settings are automatically loaded on every device boot.
Profile settings can be loaded by pressing menu -> "Load profile"
Both "boot" and "profile" settings can be deleted from menu.
RECOVERY
If Your device freezes after boot because of too agressive boot settings:
Flash Voltage Scheduler Remover by user Coreym, via CWM. Don't forget to press thanks under one of his posts!
FAQ:
Q: Extreme version?
Yes, I wanted to give some extras for people that support my work.
For now features exclusive to Extreme version are:
+ overvolting capability (max +50mV, 1500mV absolute maximum)
+ increased uv range (max -250mV)
Q: What is it?
Its voltage control app for undervolt and overclocking kernels providing sysfs interface, designed and implemented by raspdeep (thank You!) It is being tested on his kernel releases and I can guarantee (kind of) its functionality on those kernels.
The idea of the app is to keep all simple as possible, not adding any startup services and reusing existing solutions (such as init.d support).
Q: What does it mean to undevolt, and what is overclocking?
Read more in "OC / UV 101" section That is a detailed(sort of) explanation what UV/OC means.
Check this great overclocking/undervolting guide by shaolin95 (thanks!) and discussion topic!
Prerequisites:
-root (superuser + su)
-busybox
-OC kernel supporting either UVLF and UVHF (Version 1.61) or UV_mV_table (1.97 and up)
-init.d scripts support for apply on boot
3.0.1 - OLD version;
Thank's, this app is awesome.
Now i've Super Optimized JPM-JP6 Kernel v.3.7 and this run with -50 Low -25 High scheduler anticipatory (Lagfix NO RFS overkill JFS Bind=false)
and all works great.
Thanks for this app! it's a nice tool. Once feature request for the OP would be an explanation of the different schedulers. I'm using noop after some research.
Edit: I guess it would be an OP request, not a feature request.
curious, may i ask what is the difference between noop, anticipatory, deadline, and cfq?
Just search it on wikipedia.
It seems noop is the best with flash memory.
Sent from my GT-I9000 using XDA App
E: doesnt work for me anymore. Blank screen only.
Just reflashed jpo yesterday and oc kernel 2.1 by rasp.
Doesn't seem to work with YA-OK kernel (which supposably implements rasdeeps oc 1.1). Black screen same as above poster.
Might be a kernel problem, so I'll wait for the next version, hopefully it works
oswade said:
Doesn't seem to work with YA-OK kernel (which supposably implements rasdeeps oc 1.1). Black screen same as above poster.
Might be a kernel problem, so I'll wait for the next version, hopefully it works
Click to expand...
Click to collapse
YA-OK is not using my UV code hence this app wont work. he hardcoded the UV values if im not wrong
Lio78 said:
Thank's, this app is awesome.
Now i've Super Optimized JPM-JP6 Kernel v.3.7 and this run with -50 Low -25 High scheduler anticipatory (Lagfix NO RFS overkill JFS Bind=false)
and all works great.
Click to expand...
Click to collapse
I use the same kernel and same settings but all i get when i open this app is a black screen and the su popup. Is there something else i have to setup so that app will work?
May it have something to do with setcpu?
An recommendations for stable UV on 1200MHz OC kernel? Specifically for the 1000-1200MHz range? I have the 100-800MHz range at -50mV.
ggonzalez7777 said:
An recommendations for stable UV on 1200MHz OC kernel? Specifically for the 1000-1200MHz range? I have the 100-800MHz range at -50mV.
Click to expand...
Click to collapse
I've been on 0, 25, 50, 75, 100, 100 on 1.2 Ghz - its been stable for "normal" use - but i dont stress it out with video/ 3D etc - so YMMV.
New version posted, first post updated.
nice bro!
one suggestion: add checks so it wont show blank screen if the values are not read properly or folders/file not found and display messages
sometimes peeps run a wrong kernel and expect your app to work
Which version is better for SetiroN's 1.2 kernel?
Will look into it, most of checks are there, but I might have forgotten about some
MikeyMike01 said:
Which version is better for SetiroN's 1.2 kernel?
Click to expand...
Click to collapse
As of today: 1.61. Both use old UVLF and UVHF implementation.
0 50 100 75 75 125 seems to be working here
Alright... I wont upgrade then.
Sent from my SAMSUNG-SGH-I897 using XDA App
Cant get over this "blank screen issue". I've *almost* isolated the issue, it lies in these lines:
DataInputStream osRes = new DataInputStream(process.getInputStream());
BufferedReader br = new BufferedReader(new InputStreamReader(osRes));
res.add(br.readLine() + "");
br.close();
Click to expand...
Click to collapse
Cat command returns under 64 chars when file is found, when it isnt output is >64 chars.
Thats the reason for block, somewhere in these lines.
xan said:
Cant get over this "blank screen issue". I've *almost* isolated the issue, it lies in these lines:
Cat command returns under 64 chars when file is found, when it isnt output is >64 chars.
Thats the reason for block, somewhere in these lines.
Click to expand...
Click to collapse
Glad you know of this issue, on my captivate the older version works fine but when upgrading to the new one it is stuck on the black screen forever. It says SU permission granted but just stays on the black screen. I tried uninstalling the old first, rebooting, then installing and also just overwriting the old with new. Nothing but black.
Good luck on the fix, this is a very handy app
loco- said:
Just search it on wikipedia.
It seems noop is the best with flash memory.
Click to expand...
Click to collapse
I agree, here are a couple of comments that convinced me:
You want to use noop scheduler on devices where there are no seeking penalty, such as flash drives. That's why USB stick wants noop. Unfortunately, harddisks are very mechanial beasts and their performance is highly controlled by their seeking abilities. All these schedulers above are really trying to figure out how to extract maximum performance off the harddisk without causing bad behaviour in other cases.
noop is often the best choice for memory-backed block devices (e.g. ramdisks) and other non-rotational media (flash) where trying to reschedule I/O is a waste of resources.
http://www.linuxhowtos.org/System/iosched.htm
http://stackoverflow.com/questions/1...-i-o-scheduler
Click to expand...
Click to collapse
E: doesnt work for me anymore. Blank screen only.
Just reflashed jpo yesterday and oc kernel 2.1 by rasp.
Click to expand...
Click to collapse
When I installed the new version 1.97beta, it too sat at a black screen for an unusually long time, then after almost a minute, the supperroot permission screen poped up, I granted it root rights, and then voltage control came up fine.
Hm, read first post.
xan said:
Hm, read first post.
Click to expand...
Click to collapse
Umm, what post is this comment directed to?
Unclear what topic, and what in the first post we are looking for?
I'm kinda new at the whole flashing kernel thing. i just downloaded and flashed the Tiamat_Evo (v4.0.6) on my GB 2.3.3 with CyanogenMad-7.0.3.1.
What are the ways to check the max/min speeds now and what are recommend ranges for long battery life and or fast performance on the EVO
+1 in advance
There's an app called CPU Spy Beta out...I couldn't find it in the market. Try Google...they seem to have everything. I'm underclocked with interactiveX 128/768. Runs great on battery with freedom kernal
HTC EVO 4G running MIKG 2.45
slimno19 said:
There's an app called CPU Spy Beta out...I couldn't find it in the market. Try Google...they seem to have everything. I'm underclocked with interactiveX 128/768. Runs great on battery with freedom kernal
HTC EVO 4G running MIKG 2.45
Click to expand...
Click to collapse
is this it?
https://market.android.com/details?id=com.bvalosek.cpuspy
If you use Setcpu to set frequencies it also has a feature that does the same thing. Go to the info tab then select time in state. Tells you everything that app does and more.
Sent from my PC36100 using Tapatalk
Cm7 has a built in CPU setting.
Settings - cyanogenmod settings - performance - CPU settings
I run min 128 Max 614, still speedy no reboots (unless I undervolt too much)
Also check out vipermod, it was designed around the tiamat kernel to allow you to change the voltages to your CPU. This also helps battery life!
Sent by Supersonic!
imheroldman said:
Cm7 has a built in CPU setting.
Settings - cyanogenmod settings - performance - CPU settings
I run min 128 Max 614, still speedy no reboots (unless I undervolt too much)
Also check out vipermod, it was designed around the tiamat kernel to allow you to change the voltages to your CPU. This also helps battery life!
Sent by Supersonic!
Click to expand...
Click to collapse
I'm undervolted by 100 and I get get more and more battery life the longer I condition my battery. I'm also set at min 691 and max 921
The more that your phone spends time that it's switching clock speeds (drastic changes) seems like a waste of power.
imheroldman said:
Cm7 has a built in CPU setting.
Settings - cyanogenmod settings - performance - CPU settings
I run min 128 Max 614, still speedy no reboots (unless I undervolt too much)
Also check out vipermod, it was designed around the tiamat kernel to allow you to change the voltages to your CPU. This also helps battery life!
Sent by Supersonic!
Click to expand...
Click to collapse
Awesome, ill try that. is it best to reboot after applying the new settings?
If you just changed clock frequencies then no need to reboot as It's done on the fly. If you change voltages then you need to reboot. Vipermod is an excellent script. I have used it on sense kernels even though it wasn't made for them.
After looking closer at the vipermod script it doesn't say a reboot is required unless going back to factory defaults.
Sent from my PC36100 using Tapatalk
@civicboy, no real need to reboot, make sure the settings don't cause your phone to reboot on its own before checking set at boot. Same goes for undervolting, and, you are more likely to get reboots with undervolting. I have seen peoples phones that wont accept any undervolting... be cautious... do it in 25mv increments to find what your phone can handle... have the reset file on your sdcard at all times. Sounds scary but its really not that bad once you figure it out.
Check back with your results or if you need more info.
Sent by Supersonic!
imheroldman said:
@civicboy, no real need to reboot, make sure the settings don't cause your phone to reboot on its own before checking set at boot. Same goes for undervolting, and, you are more likely to get reboots with undervolting. I have seen peoples phones that wont accept any undervolting... be cautious... do it in 25mv increments to find what your phone can handle... have the reset file on your sdcard at all times. Sounds scary but its really not that bad once you figure it out.
Check back with your results or if you need more info.
Sent by Supersonic!
Click to expand...
Click to collapse
here are my values. i went down to 100, however, i dont know what the factory values are so I cant confirm that it worked, or that the values stuck after reboot
Can anyone confirm by looking at these numbers?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
those numbers look too high. after you changed the value, did you enter "10" to save the changes and re-write to the init.d file?
alaman68 said:
those numbers look too high. after you changed the value, did you enter "10" to save the changes and re-write to the init.d file?
Click to expand...
Click to collapse
probably not, since i cant say yes right away lol
EDIT: I am just going to reset to factory, do the reboot, and start over.... making sure i save changes
Why am I getting this error at the bottom of the screen?
[/IMG]
Are you typing SU before you start vipermod? You have to give TU root for vipermod to work.
I think i got it figured out. i reflashed and restarted process and works great now, keeping all values. i went down -50. dont want to push my luck. Thanks for all the help!
Be sure to get vipers zip for reseting to default. This allows you to push the voltages and if you get boot looping you can just flash the reset from recovery.
And I gave you a "thanks" for actually thanking those that help out.
BuddaBelly said:
Be sure to get vipers zip for reseting to default. This allows you to push the voltages and if you get boot looping you can just flash the reset from recovery.
And I gave you a "thanks" for actually thanking those that help out.
Click to expand...
Click to collapse
lol awesome. thanks man.
You are talking about the original zip file right? can i just creat a folder called vipermod and store it in that incase of emergency?
ha, i was going to pop his "thanks" cherry too.
there is restore defaults .zip you can flash. Put it on your sd for safe keeping wherever you like and remember.
Terminal emulator is fun to learn too
alaman68 said:
ha, i was going to pop his "thanks" cherry too.
there is restore defaults .zip you can flash. Put it on your sd for safe keeping wherever you like and remember.
Terminal emulator is fun to learn too
Click to expand...
Click to collapse
Where can i get that?
http://bit.ly/nNN1P6
That's the file you need. Just put it on the root of the sdcard or wherever you know it's at and if you get into trouble going to crazy on voltages just flash it from recovery. It will reset your voltages back to defaults.
·:*¨¨*:·..·:*¨☆Jame Bond☆·:*¨¨*:·..·:*¨
straight from The Land of Smiles
Jame Bond kernels have always been about battery efficiency without sacrificing speed...
-latest version-v3.4.6
that thae
-linaro gcc
-some debugging disabled
-undervolted
-interactive governor (default) is recommended
-GPU set to 307MHz
-boots to 1.2 (oc to 1.3)
khlang
-color control
-sound control
-gamma control
new mobile app
Goo-inside.me beta
-Browse Files...
/devs/ogdobber/gnex/kernel
-installation/Tweaks
Click to expand...
Click to collapse
-uv settings
Click to expand...
Click to collapse
-protips
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
note: please "rate" the thread
Thank you to those that have! If you are new to this thread, browse through the pages. I always try to answer questions quickly and thoroughly, as well as provide a stable kernel. If this kernel doesn't have the "features" you are looking for, or you have seen a cool new mod, just ask and I will try to accommodate (or at least give a reason why not)
thanks for your time -og
acronyms, notes, etc.
deprecated kernels
***************************************************************************************************************************************
4.1.x kernel(s)
that thae
1.2/3.5GHz◊GPU 307MHz
☆Jame Bond☆ v3.4
1.2/3.5GHz◊GPU 307MHz
☆Jame Bond☆ v3.3
mirror
khlang
1.2/3.5GHz◊GPU 307MHz
☆Jame Bond☆ v3.4.6
Click to expand...
Click to collapse
_____________________________________________________________________
thanks to coolbho3000 for his patches
support setcpu
» kernel source
» additional source
Control your Android phone's CPU! SetCPU for Root Users
installation
-download to sd card and flash from recovery
tweaks
version 3.1.7 has several "tweaks" that are controlled in system/etc/init.d/007tweaks
-color and v1 control
-vibration control
-volume boost
-high performance sound
-fast charge
everything boots to stock settings, make adjustments at your leisure.
included is system/etc/init.d/007tweaks.bkk which are the settings I use (just rename to 007tweaks)
of course with cm9 and aokp the colors can be adjusted with sliders in rom settings
007tweaks
Code:
echo "60" > /sys/class/misc/samoled_color/red_v1_offset
echo "60" > /sys/class/misc/samoled_color/green_v1_offset
echo "60" > /sys/class/misc/samoled_color/blue_v1_offset
#default 60 60 60
echo "2004318071" > /sys/class/misc/samoled_color/red_multiplier
echo "2004318071" > /sys/class/misc/samoled_color/green_multiplier
echo "2004318071" > /sys/class/misc/samoled_color/blue_multiplier
#default 2004318071 2004318071 2004318071
echo "1450" > /sys/vibe/pwmduty
#default 1450
echo "0" > /sys/class/misc/soundcontrol/volume_boost
#default 0 max 3
echo "0" > /sys/class/misc/soundcontrol/highperf_enabled
#default 0 on 1
echo "0" > /sys/kernel/fast_charge/force_fast_charge
#default 0 on 1
permissions are set on flashing, but if changed with "es explorer" they need to be reset to
for roms that don't have "color slider adjustments" to have the changes take affect without rebooting, open a terminal and run....
Code:
su <enter>
run-parts /etc/init.d/ <enter>
kernels are preset
don't drop more than 75mV under default
one more......
ahh you beat me to it blassilando
oh well, 2 extra should do the trick anyways. hopre you guys enjoy
ogdobber said:
another one jic...
Click to expand...
Click to collapse
YES YES YES.... i cant wait for it! ive always got my device a few months older, so getting it day 1 (actually 2) is pretty crazy seeing the thread slowly build.. thanks for this kernel man!!!!
Just flashed and so far so good
Sent from my Transformer Prime TF201 using XDA Premium HD app
Thanks! Heard nothing but good things about your kernel.
Just a question, does this make the lte radio inoperable? And can someone verify either way. I know that most of the lte towers are locked down but since I live in the Dallas area I would hate to loose the capability of using lte.
Nazrac79 said:
Just a question, does this make the lte radio inoperable? And can someone verify either way. I know that most of the lte towers are locked down but since I live in the Dallas area I would hate to loose the capability of using lte.
Click to expand...
Click to collapse
It shouldn't make lte inoperable. You would have to try and see. I haven't gotten an lte signal in atl yet even though this is suppose to be a city that first gets it. If your really worried, you can backup your rom before you flash and that way there's no worries.
I did a backup as this isn't my first rodeo, but yeah I haven't found a lte signal yet as well. Didn't think it would change the radio settings but really don't know that much.
Hi, just like to say thanks for the amazing kernel.....my battery's loving it.
Nazrac79 said:
I did a backup as this isn't my first rodeo, but yeah I haven't found a lte signal yet as well. Didn't think it would change the radio settings but really don't know that much.
Click to expand...
Click to collapse
OVERLAND PARK, Kan. (BUSINESS WIRE), February 08, 2012 - Sprint (NYSE: S) today announced that Baltimore and Kansas City are expected to receive 4G LTE and upgraded 3G service by mid-2012. Sprint recently announced that 4G LTE and enhanced 3G service are also expected by mid-2012 in Atlanta, Dallas, Houston and San Antonio. Sprint 4G LTE will enable faster speeds for data applications, and the enhanced 3G service promises better signal strength, faster data speeds, expanded coverage and better in-building performance.
PSA. Don't know if anyone has experienced this, but I thought it was worthy of posting http://www.androidpolice.com/2012/0...tion-problems-sprintsamsung-working-on-a-fix/
Sent from my Galaxy Nexus using xda premium
ogdobber said:
PSA. Don't know if anyone has experienced this, but I thought it was worthy of posting http://www.androidpolice.com/2012/0...tion-problems-sprintsamsung-working-on-a-fix/
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Oh yeah, lot's of us have. Sprint keeps telling everyone different stories. I've been told within the same 24hrs that there are no known network issues in my area, that they *are* working on a tower in my area and that I need to return the device as it's probably a hardware issue. Lol, good old Sprint
v3.1.9.4j posted on my twitter https://twitter.com/#!/ogdobber/status/197711450398134275
Added one new feature at the last minute...gamma control. this is different than gamma V1 and color control.
to adjust, change value in 007tweaks and reboot.
or to see an immediate result open terminal emulator on the phone
type su <enter>
echo "1-10" > /sys/devices/platform/omapdss/manager0/gamma
so....
Code:
echo 6 > /sys/devices/platform/omapdss/manager0/gamma
-will slightly darken the screen
protip- because typing in the terminal is tedious, create a file in google drive and name it "gamma"
enter the text echo 6 > /sys/devices/platform/omapdss/manager0/gamma
and save
then when you want to change the gamma value, it is easy to edit in drive, select all and copy and paste to terminal
on a side note, I see that some coward gave my thread a 1 star. pretty disappointed in that
ogdobber said:
on a side note, I see that some coward gave my thread a 1 star. pretty disappointed in that
Click to expand...
Click to collapse
Lol gave it a 5 star vote
bumped it back up to 4 stars total thanks for the kernel bro
Anyone who rated this thread 1 star is a dip****. Does this latest release on twitter have any OC or just stock 1.2?
Also you may have answered this, but why not just have all kernels have an option to overclock. Those who don't want to, leave it at 1.2 those you do can crank it up?
Again I have no clue about anything of this dev stuff besides flashing, just curious as that seems like the best one size fits all type of release.
ferris2375 said:
Anyone who rated this thread 1 star is a dip****. Does this latest release on twitter have any OC or just stock 1.2?
Also you may have answered this, but why not just have all kernels have an option to overclock. Those who don't want to, leave it at 1.2 those you do can crank it up?
Again I have no clue about anything of this dev stuff besides flashing, just curious as that seems like the best one size fits all type of release.
Click to expand...
Click to collapse
The latest does have oc.
Really the only ones that don't have oc are "that thae" , pretty much everything else as of late does
Sent from my Galaxy Nexus using xda premium
Thanks, I thought I was in the GSM forum though. lol New release for that phone as well?
***THIS APP NEEDS A ROOT PHONE***
This app includes root tools that you can use with a simple click. Its currently under development, this means that it will get new things added.
***INCLUDES***
Reboot
Reboot in Recovery Mode
Reboot in Bootloader Mode
Quick Reboot
Power off your device
Wipe cache and dalivk-cache
Wipe dalvik-cache
Wipe battery stats
wipe cache
Free up RAM
backup bootanimation
install bootanimation
Save a LogCat
Save App specific LogCat
Turn On/Off CPU2
Kernel mods:
1. Overclock
2. Select Governor
3. Governor Settings for:
---EVERY GOVERNOR (PLEASE REPORT IF IT DOESN'T WORK)
***ONLYE FOR GALAXY NEXUS AND GALAXY SIII***
CPU temperature notification.
I will add more and more features.
Download now from PLAY STORE!!!
Looks good thanks. Will helping testing as much as possible.
Sent from my Galaxy Nexus using Tapatalk 2
Really nice stuff! If I were you, I'll add extra features that no other competitors have
Swyped on my Galaxy Nexus running AOKP with Franco Kernel
very good work, compliments!!
Version 1.5
Changed orientation to portrait. Added a bootanimation preview button. Easier file chooser for bootanimation. Completely different look for kernel mods. App more user friendly. Fixed some minor bugs. Removed some unused toast messages.
Need some test for bootanimaton preview. Please report back
Updated to latest, Version 1.6, with many fixes
unforgivenmercy said:
Looks good thanks. Will helping testing as much as possible.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Could you try the cpu temp notification, just turn it on and off like 10 times and tell me if you get any FC or if its not showing.
Thanks
Version 1.7
A lot of bug fix. Fixed governor settings not applying, added a check box to set governor at boot, fixed clear cache for ROMs that doesn't support it, fixed crash for CPU temp notification, fixed loop when device can't reboot, clear cache, etc. Added GSF id and System id info, (Will just show it to you).
Click to expand...
Click to collapse
If anyone get any other FC when enabling CPU temperature read, please report it again, since it should be fixed. Thanks.
New version with Rom management. Only available for CWM Recovery!!
I think you have a minor typo in OP 'turn off CPU 2' should be 'turn off CPU 1' as cores are CPU 0, CPU 1 (duel core) then CPU 2 and CPU 3 (for quad core device)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Galaxy Nexus
The Gingerbread Man said:
I think you have a minor typo in OP 'turn off CPU 2' should be 'turn off CPU 1' as cores are CPU 0, CPU 1 (duel core) then CPU 2 and CPU 3 (for quad core device)
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Yes I know that, but for not developers people seeing a number 1 is like the first CPU will be off. Since you normally start counting with the number 1. I did name it number 1 in one of the tests and I received a lot of e-mails asking me if its safe to turn off the first CPU and why I'm not doing it with the second CPU. So I decided to change the number so that way people wont get confused.
So basically you are right, but I did it on purpose.
Rotary Heart said:
Yes I know that, but for not developers people seeing a number 1 is like the first CPU will be off. Since you normally start counting with the number 1. I did name it number 1 in one of the tests and I received a lot of e-mails asking me if its safe to turn off the first CPU and why I'm not doing it with the second CPU. So I decided to change the number so that way people wont get confused.
So basically you are right, but I did it on purpose.
Click to expand...
Click to collapse
I see and no worries I was just checking, I don't intend on using this but just wanted to make sure you knew the correct labeling for the cores
Sent from my Galaxy Nexus
The Gingerbread Man said:
I see and no worries I was just checking, I don't intend on using this but just wanted to make sure you knew the correct labeling for the cores
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Thanks anyway
Hello there!
I had Motorola Milestone before S3, and I developed this app. Since it seems that there were few users that found it use full, I rewrite it to suport multi-cores and S3 phone.
In short:
This app will show info and details about your phone CPU, like active governor, active cores, total system uptime, wake time, deep sleep time and frequency details. It auto refreshes every one second, and on my S3 it takes less than 8% of cpu...
I tested it on stock XELLA rom with siyah kernel, but it should work on any rom/kernel versions _IF_ kernel has cpufreq_stats enabled and loaded.
If some values are 0 or -1 it means that it cannot read those values, either because file doesn't have read-all permissions or cpufreq_stats is not enabled/loaded, and would be nice if you'd report that back.
Also, this file _should_ work with almost any android device, but I only have S3 to test it, so if you have another device, please test it and report back result, with info about phone/rom/kernel.
Any comments and suggestions are welcome!!
updates:
v0.21 - added temperature reading. Temperature is from CPU directly and not from battery! This will almost certainly work only on S3 (and maybe device with similar SoC)...
P.S.
Version starts from 0.2 because I reused lot of code from old app...
P.P.S.
Original thread is here.
P.P.S.
I hope that I posted this to correct forum section!
Screenshot attached.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Nice work, but I really wish it could tell more information such as CPU temperature...
Sent from my GT-I9300 using xda premium
qtwrk said:
Nice work, but I really wish it could tell more information such as CPU temperature...
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
thx!
that is in TODO list, first after few minor code fixes... anything else?
amossam said:
thx!
that is in TODO list, first after few minor code fixes... anything else?
Click to expand...
Click to collapse
2 small things, please take look at screenshot
1. The core 3 is position shifted... I guess because both core 1 and 2 are off, and double off took 2 more spaces than double on so...
2. could you hide unused frequencies? I am using Siyah, which is able to use 200 to 1800 but I set maximum to 1400, so you may consider don't show those unused frequency so occupy less place?
By the way, could you explain what "frequency transition " means?
Sent from my GT-I9300 using xda premium
qtwrk said:
2 small things, please take look at screenshot
1. The core 3 is position shifted... I guess because both core 1 and 2 are off, and double off took 2 more spaces than double on so...
2. could you hide unused frequencies? I am using Siyah, which is able to use 200 to 1800 but I set maximum to 1400, so you may consider don't show those unused frequency so occupy less place?
By the way, could you explain what "frequency transition " means?
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
1. yea, two off's seems to make that issues. I'll try to make a font little smaller, or maybe in two lines...
2. I was thinking about hiding unused freqs, but it didn't bother me enought! will do it.
Frequency transitions is number of frequency hops. so, it's number of times that cpu changed frequency.
amossam said:
1. yea, two off's seems to make that issues. I'll try to make a font little smaller, or maybe in two lines...
2. I was thinking about hiding unused freqs, but it didn't bother me enought! will do it.
Frequency transitions is number of frequency hops. so, it's number of times that cpu changed frequency.
Click to expand...
Click to collapse
A little thinking, I assume in frequency detail
It says "CPU (governor ) "
And beneath that there 2 sets of numbers, number in ( ) are means current setting min and max I think? But if so, consider you put word governor inside ( ), the number below shouldn't show up otherwise?
And I guess current frequency , something like 200 (200), is kinda useless (no offense, please don't get me wrong, maybe you put there for some purpose, but I just don't see it )
Sent from my GT-I9300 using xda premium
qtwrk said:
A little thinking, I assume in frequency detail
It says "CPU (governor ) "
And beneath that there 2 sets of numbers, number in ( ) are means current setting min and max I think? But if so, consider you put word governor inside ( ), the number below shouldn't show up otherwise?
And I guess current frequency , something like 200 (200), is kinda useless (no offense, please don't get me wrong, maybe you put there for some purpose, but I just don't see it )
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
no offense taken!
one number is what CPU reports it's frequency, and in () is number which governor says that CPU frequency is.
because those two number don't need to be same, altought most of time they are same. not shure did I explained well!