Related
Powersave CPU Manager
Automatically manages you cpu no matter what you use, ie. setcpu, cpumaster, virtuous_oc. This will automatically underclock your cpu and change the governor when your battery reaches a specified level. Kind of like powersave mode in settings.
You don't need to do anything to make it happen its all automated. By default it sets the governor to conservative and underclocks to 702000 then depending on whats installed it restarts virtuous_oc or changes back the governor to ondemand and the cpu back to stock (1188000).
These settings can be edited at:
/system/etc/init.d/74-virtuous for virtuous users
/system/etc/init.d/75-pcm for stock users
/system/etc/init.d/76-pcmapk for apk users (setcpu)
The lines are commented so editing should be easy enough in root explorer, if not lmk i will help out.
You will have to restart setcpu or whatever apk after your battery reaches the threshold. It works with setcpu, cpumaster, cputuner, and overclock widget.
Once you battery gets above the threshold it will restart virtuous oc or change the gov and cpu freq to whatever you specify in the script. It checks the battery level every minute.
The virtuous oc attachment includes virtuous oc this can be flashed right over my flashable oc daemon. It can be used with roms that include virtuous oc as well.
Download the zip you need:
Virtuous_OC-PCM = Virtuous_OC and PCM
PCM = PCM Stand alone Auto sets default cpu frequency use without setcpu or virtuous
PCMAPK = PCM for use with some apk's that control cpu (setcpu)
Please report any bugs here.
How to edit settings:
This is virtuous_oc version but they are all about the same.
Edit the lines in red to adjust settings, this is labeled actual script will look a little different.
Code:
#!/system/bin/sh
#PowerSave CPU Manager Virtuous
#smokin1337
SLEEP=60
(
while : ; do
#Powersave Threshold Default-25
CAP=[color=red]25[/color] [color=blue]<<-- This is the battery percent where the powersave settings will be applied, change the number in red.[/color]
LEVEL=`cat /sys/class/power_supply/battery/capacity`
if [ "$LEVEL" -lt "$CAP" ]; then
pkill virtuous_oc
#Powersave Governor
echo [color=red]conservative[/color] > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor [color=blue]<<-- Edit this to the governor you want it to be set to in powersave mode. ie. powersave, conservative, ondemand, userspace, etc.[/color]
#Powersave CPU Frequency
echo [color=red]702000[/color] > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq [color=blue]<<-- Edit this to set the cpu frequency for powersave mode ie. underclock. [/color]
else
/system/xbin/virtuous_oc
fi
sleep $SLEEP
done
) &
In the stand alone version (75-pcm) there is also a setting for your default governor when not in powersave. This will be your default setting.
Your rom MUST support init.d, this is a script.
Thank you!
I will try it now.
Does this work with the kernel in the 2.08.651.2 release?
Is this a Terminal-based app or an actual app? If Terminal, what command invokes it?
Also, you say whatever CPU management tool we use doesn't matter, does that also mean I can just toss SetCPU altogether?
Yes it works with the new kernel. It gets installed to init.d so it runs by itself when you boot the phone. You dont need to run it in a terminal.
It works with setcpu, you need the pcmapk version. What it does is shutdown setcpu when your battery gets low and underclocks your cpu to save battery. You just have to run setcpu again when your battery gets charged.
I'm interested in this mod but I don't understand what i have to do. Do I download all 3? I don't want to use any apk. to help. Do any of those downloads manage everything alone. PLEASE HELP...thank you and sorry for the noob ???s.
abreuw83 said:
I'm interested in this mod but I don't understand what i have to do. Do I download all 3? I don't want to use any apk. to help. Do any of those downloads manage everything alone. PLEASE HELP...thank you and sorry for the noob ???s.
Click to expand...
Click to collapse
Yes the PCM-signed.zip will manage it without any apk or virtuous oc. Just flash it as is. Sorry about the explanation of it i didnt know how far to go.
Wow...thanks for the quick response. Thank you for your work.
not trying to be a **** here but whats the point of this being used with setcpu since setcpu seems to already do what you are describing here. profiles set up right will underclock and change govenor when battery gets to level X.
Now for the others it seems to be helpful for those that like profiles being used.
Honestly i havent used setcpu. But your right it works well by itself, and really good with virtuous oc. I use it personally with virtuous oc and it helps alot saving juice.
Gonna try this out. I don't want to overclock, I just want to underclock in order to save juice.
Please help me understand it a little more, I already use virtuous oc, I've been running the pcm version with virtuous oc the last dew days and notice a huge lag when phone reaches 20%, how can i give it a bit more juice? I think whatever you set it to when battery is low is too slow..
How does virtuous oc work together with pcm?
Also is the version for the virtuous OC-PCM in this thread the same as in the other thread (virtuous OC thread)?
3vo fre3vo'd
Anyone can help with this please ^^^^
3vo fre3vo'd
my phone after installing virtuos OC-PCM kept rebooting spiral how can I remove it from recovery.. thank you...please fast ...
drZuheir said:
my phone after installing virtuos OC-PCM kept rebooting spiral how can I remove it from recovery.. thank you...please fast ...
Click to expand...
Click to collapse
Download the uninstaller file in the thread related to it. But by now im pretty sure you fixed it. Is it stable yet?
Edit: This is stable but it doesn't save juice and my OC isn't completely stable.
TKSGB KERNEL HAS BEEN RENAMED TO KGB KERNEL!
NEW THREAD HERE
PLEASE DISREGARD THE REST OF THIS POST
----------------------------------------------------------------------------------------------------------------------------
There aren't very many tweaks in yet but it should be stable again and a lot of ext4 and lowmemkiller lag issues should be gone! Here's an incomplete list of features.
Voodoo: Lagfix and sound. No color for now
CPU governors: The same ondemand, ondemandX, interactive, interactiveX, smartassv2 and ondemandX as default
I/O schedulers: The same cfq, bfqv2r1, sio, deadline, vr and deadline as default with the last three being optimized for flash
jhash3, OC/UV, BLNv9, 3rd-party batteries, boot animations
LED flashlight, CIFS and TUN
zram
User-adjustable in-call audio boost, no boost by default!
Preliminary dock audio support, need more feedback
Autogroups and Tiny RCU removed pending performance evaluation
How to adjust in-call audio and zram
Run callboost or zram from a root prompt (AS ROOT). To manually tweak zram size or call boost volumes, look in /etc/init.d/ for the startup scripts they drop after enabling. The filenames are 05zram and 91callboost.
Recommended settings for callboost are 1 or 2, 0, 0, and 0 or 1. zram is 12.5% of available RAM by default.
The zram script crashes when enabling if there isn't enough RAM free. Don't run zram enable unless you're sure you have enough RAM on hand, such as right after a fresh reboot.
How to use dock audio
Preliminary testing (thanks ACLakey even if you do have a Mesmerize ) indicates it does something right. I have no way to know if it's doing something wrong or even if it doesn't work at all so give me feedback.
How to use your phone as an access point
Get the latest Wireless Tether for Android (3.0b6 last I checked), and set mode to Samsung softap in the settings. It won't be peer-to-peer and WPA2 encryption will work.
"STABLE" DEVBUILD 1027
CWM zip: http://www.mediafire.com/?tjsadn6v0cocqy6
Odin: http://www.mediafire.com/?redm61dt4uwjpt2
Oh, and just because...
"BLEEDINGEDGE" DEVBUILD 1116
CWM zip: http://www.mediafire.com/?mg78n9a77sje6e4
Changelog: Drivers/kernel settings from EI20, except for the dpram driver which is still from EH09. Removed carrier hotspot tracking code in init.rc (doesn't make hotspot tracker directories in /system), ARM and memory and RCU updates/tweaks, changes to scripts in ramdisk.
Still pretty untested
P.S. Don't confuse one for the other, thanks
Please excuse the mess below.
----------------------------------------------------------------------------------------------------------------------------
Kernel is alpha and untested for the most part, and I cannot guarantee stability or robustness of features. Still, I've been using it every day for a few weeks now, and it's pretty stable for me. It should work on most EH09-based ROMs out there, including PowerWashed, GeeWiz and TSM Resurrection, just to name the ones I know as I am a Fascinate user. It works with Mesmerize and Showcase too, I'm given to understand, with the proper ROM tweaks (which I don't claim to know anything about).
FEATURES
Voodoo: Lagfix, Sound v10, and Color v2. Use with Voodoo Control.
CPU governors: conservative, performance, ondemand, ondemandX, interactive, interactiveX (ondemandX as default)
I/O schedulers: Noop, CFQ, BFQv2-r1, SIO, V(R), Deadline (deadline as default). The last 3 are optimized for use with flash memory.
Autogroups, jhash3, Tiny RCU for responsiveness.
OC/UV up to 1.7GHz, with Voltage Control/Pimp My CPU.
Third-party battery support allows use and charging of aftermarket batteries and batteries for other Galaxy S phones.
No hotspot monitoring with the WiFi driver from the i9000.
In-call audio boost: Higher volumes and mic gain settings. Works OK as of 10/18.
CIFS and TUN included in base kernel. UTF-8 native language support was already there.
BackLightNotifications v9 with a ported touchkey driver from the i9000. Automatic installation of the proper liblights. Use BLN Control and/or Blinky to get down to business.
Bootanimations: Works with /data/local/bootanimation.zip, /system/media/bootanimation.zip, or /system/media/sanim.zip. Automatic installation of the proper bootanimation binary.
LED flashlight: The camera LED makes a surprisingly good flashlight. Activate with any of a number of flashlight apps from the Android Market.
zram from Linux 3 (credit imoseyon). Open up a terminal and run "zram" to get started. By default "zram enable" will use 12.5% of total RAM as an LZO-compressed ramdisk and set up swap space on that. Don't run the script unless you have at least 50MB or so of RAM free. To change the size of the zram, edit the relevant line in /etc/init.d/05zram (it's in bytes, do your own math) and reboot.
Other standard features: init.d support, adb shell gives you a root prompt
Various behind-the-scenes tweaks: A growing list of ARM and Samsung kernel/driver patches for hardware errata and Linux kernel patches to enhance interactivity
CHANGELOG
For complete changes refer to github.
Code:
[size=4][B]1018[/B][/size] Most changes on this one are behind the scenes.
[b]In-Call volume boost changes[/b] +12dB at earpiece only & mic gain boosts
[b]Update interactiveX and ondemandX CPU governors[/b]
[b]ondemandX as default[/b] i'm pretty sure this is a backport from linux 3 too
[b]Use CodeSourcery 2010q1 toolchain[/b] bad Linaro, bad!
[b]zram backport[/b] and add zram script to initramfs
[b]Memory tweaks[/b] optimize memcpy functions, tweak lowmemorykiller
[b]Bugfixes[/b] to autogroups and a couple other things
[b]initramfs changes[/b] probably falls under bugfixes actually
[size=4][B]1012[/B][/size]
[b]In-Call volume boost changes[/b]
[b]dvfs lock fixed[/b], no more pegging CPU at 1440MHz with bluetooth
[b]lowmemkiller settings[/b] changed in init.rc
[size=4][B]1010[/B][/size]
[b]In-Call Volume boost[/b] numbers were chosen arbitrarily, need detailed feedback
[b]Autogroups, [strike]Tiny Preempt RCU[/strike][/b] woopz
[b]Bootanimation support[/b] install required binary on boot
[b]Add ondemandX CPU governor[/b]
[b]ondemand as default[/b] interactiveX pegs the CPU high on hw video playback
[b]optimize sio and vr[/b] for flash devices
[b]Voodoo Color fix[/b] no more green tint at low brightness
[b]More tweaks[/b] ARM, Samsung, buildflags; see github
[size=4][b]1006[/b][/size]
[b]Third-party battery support[/b] apparently works fine as of 10/10
[size=4][b]1005[/b][/size]
[b]BackLight Notifications[/b], neldar-flavored, finally!
[b]Installs liblights on boot[/b]
[b]deadline scheduler[/b] tweaked for flash memory
[b]interactiveX governor is default[/b]
[size=4][b]0927[/b][/size]
[b]Initial release[/b]
KNOWN ISSUES/TO-DO LIST
Dock audio: I've almost got this merged but have no dock and no way to test.
Lots more tweaks and testing. I know it isn't fully polished and some things could use cleanup and updating. There is also a veritable sea of tweaks out there that I haven't even started parsing through.
Autorooting, autoinstall of busybox, bash, nano, and a bunch of obnoxious init.d scripts
Recovery with crazy rainbow colors and logos, etc.
TKS does not yet come with CWM. The version most of you are using is probably the blue ClockworkMod Recovery 3.0.2.8x by I believe times_infinity. It's pretty compatible with my kernel with a couple of minor bugs. Mirrors: http://www.mediafire.com/?91cq99066cwph4d http://www.multiupload.com/QEP9U2MC2G
CWM-FLASHABLE ZIPS
NEW 1018 http://www.mediafire.com/?07nero2764ktcn4 http://www.multiupload.com/V81P3FNJOD
1012: http://www.multiupload.com/JFLEF7U7EH
1010: http://www.mediafire.com/?9f58oks4a988a7o http://www.multiupload.com/PDXE2U08IG
1006: http://www.mediafire.com/?ev1g554de7ab9g0 http://www.multiupload.com/KB7833E0E4
1005: http://www.mediafire.com/?em8md8yxq7o61ny http://www.multiupload.com/EHJFAPYW51
0927: http://www.mediafire.com/?76ea7izaqc3e7a2 http://www.multiupload.com/O1HRXNCQQW
ODIN TARS
NEW 1018: http://www.mediafire.com/?didta4h7vk0uh8p http://www.multiupload.com/EXS2REYBAI
1012: http://www.multiupload.com/W8VZQGA3AG
1010: http://www.mediafire.com/?2tiiwoeav61ha0f http://www.multiupload.com/4XORWQIQIZ
1006: http://www.mediafire.com/?p9u3ow2mw70n26c http://www.multiupload.com/58XYU7OF86
1005: http://www.mediafire.com/?5ojvasq4lurvxnp http://www.multiupload.com/4W2GPSZHU7
0927: http://www.mediafire.com/?rqwe26c1pi4766r http://www.multiupload.com/JST3N8AAIP
GITHUB
All I do is kang other people's work, get it?
https://github.com/kangtastic
Also where you can see the full changelogs.
THANKS
imoseyon: Merged Voodoo Lagfix by hand. Also, he and the next two guys and I are like the only ones doing anything with the TW GB kernel on this phone.
ccampos784: Merged Voodoo Sound, and some other dev work before I forked his branch.
djp952: Ported the i9000's Wi-Fi driver and killed VZ's hotspot monitoring dead. It wasn't the only thing he ported from the i9000 to get EH09 building. And on that note...
The Samsung Galaxy S i9000: It is truly the gift that keeps on giving. Comparing good work i9000 people have done on the i9000 and CM7 repos with the EH09 code makes broken things work again, period.
TeamSbrissenMod & Supporters: The TSM-Resurrection ROM got me to try EH09, but they've done lots of great work over the last year.
jt1134: Got me started with cross-compiling my first kernel, and he is responsible for most of the innovation on this phone.
Other "historically important" people: adrynalyne, imnuts, SirGatez, nemesis2all, navenedrob etc.
IRC people too numerous to list and random people too numerous to list from whom I have taken all sorts of ideas and code that ended up in this kernel
DISCLAIMER
I am not a developer and the sole reason I started was so that I could be happier with the kernel I use on my own phone. If something does not get added or fixed, you are welcome to do it yourself.
I take no responsibility for exploding phones, voided warranties, missed appointments, dead babies and the like which are claimed to be related to your decision to use my kernel in any way. You're in the "development forum."
That said, feel free to leave useful feedback and suggestions. For bug reports, link logcats and dmesg output. And enjoy!
INFORMATION REGARDING OC/UV VALUES
The default values in the Samsung source are as follows:
1000MHz arm_volt=1275mV int_volt=1100mV
800MHz arm_volt=1200mV int_volt=1100mV
400MHz arm_volt=1050mV int_volt=1100mV
200MHz arm_volt=950mV int_volt=1100mV
100MHz arm_volt=950mV int_volt=1000mV
arm_volt_max=1350mV int_volt_max=1250mV
Of these the values that everyone talks about are the arm_volt values. arm_volt is what is modified by Voltage Control, Pimp My CPU, etc. int_volt is a secondary line that is not reported or directly adjustable by the user. The Glitch kernel plays around with int_volt for their different "leakage" versions, demonstrating that int_volt, too, plays a significant role in max overclock, but this isn't a concern of mine at the moment.
arm_volt_max is set to 1350mV which would then be the theoretical "overvolting limit". In this example you could overvolt 1000MHz by up to +75mV before running into driver limits.
Here are the default values in TKS.
1700MHz arm_volt=1500mV int_volt=1250mV
1600MHz arm_volt=1500mV int_volt=1250mV
1500MHz arm_volt=1500mV int_volt=1225mV
1440MHz arm_volt=1500mV int_volt=1200mV
1400MHz arm_volt=1450mV int_volt=1175mV
1300MHz arm_volt=1400mV int_volt=1150mV
1200MHz arm_volt=1350mV int_volt=1125mV
1000MHz arm_volt=1250mV int_volt=1100mV
800MHz arm_volt=1200mV int_volt=1050mV
400MHz arm_volt=1050mV int_volt=1050mV
200MHz arm_volt=950mV int_volt=1050mV
100MHz arm_volt=950mV int_volt=1050mV
arm_volt_max=1500mV int_volt_max=1250mV
Let's look at 100-1000MHz first. At 1000MHz there is a slight -25mV arm_volt undervolt (or just plain old undervolt) as well as a -50mV drop in int_volt for all frequencies <1000MHz. In other words, for stock frequencies there is already an undervolt built right in that you should take into account.
At higher clock settings the values are essentially best guesses at the proper settings for that speed, refined by community experience, so talking about a "proper" undervolt level is a little bit inaccurate. Note that voltage is maxed out at 1440MHz and above, but the secondary int_volt values keep increasing. The effect is a ramping up of total power supplied with increasing clockspeed, as it should be.
So I wouldn't be at all surprised to see 100-1000MHz benefitting from a couple +25mV boosts compared to "the settings I used to use on my old kernel" here and there and I'd pay attention to differences between the default voltages, especially 1200MHz+, of the old and new kernels. With different defaults, seemingly different undervolt settings could translate into the exact same amount of mV supplied.
awesome man...great to see eh09 finally getting some kernel love
hopefully once imoseyen gets his i500 from someone sending it, u can get some more help as well
(if u bet bln working ill reactive my fascinate for awhile lol)
I can give feedback about what DOES work despite being in alpha stage:
Voodoo color is working (personally, I like to go "punchy" on gamma hack)
OC is stable at least to 1400 for me with default noop/interactive, and with 100mhz state disabled (I could only go up to 1200 on MIUI without immediate instability on Glitch)
My phone is quite stable (so far) on this kernel, more so than what you'd expect on an alpha release
I'm glad you posted your own thread for this kernel comeradesven
Another Fascinating post by my XDA app...
This kernel is what I've been looking for
With a battery fix and in-call volume fix, I think I'll have a permanent GB solution! I'm hard of hearing and most of these GB kernels just don't cut it for me. CM7 (MTD) works, but Slacker caching doesn't work because of the file system. Slacker says tough s**t, we're not supporting it. So here we are. I'll put this on my spare Fassy and test it out today.
I'm also hard of hearing, but in-call isn't too, too bad for me on speakerphone... Media volume, on the other hand... IDK if media volume has anything to do with this kernel or if it's an EH09 issue...
Another Fascinating post by my XDA app...
Does this kernel use the Nexus S color source like on Glitch's kernel?
FDro said:
Does this kernel use the Nexus S color source like on Glitch's kernel?
Click to expand...
Click to collapse
If you're talking about mDNIe values, then no. I tried adding some new values earlier and it didn't work. It does have a ported Nexus S framebuffer driver like all Voodoo Color kernels AFAIK.
Awsome work sir!!
which one is better... voltage control or pimpmycpu?
now i use voltage control oc up to 1400 with uv 50 all way down. so far run smooth.
i use noop and ondemand, if i use conservative then phone get lag
I purchased SetCPU originally, can I use it instead?
Sent from my SCH-I500 using xda premium
djblu said:
I purchased SetCPU originally, can I use it instead?
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
IIRC the answer to that for this variety of overclock code is as follows.
Short answer: No
Long answer: Maybe but you might/probably will have problems
will this eventually have a -100uv kernel. i've the best battery life using pbj kernels with that setup. hope this gets it too. will switch kernels once all the kinks get worked out.
thx for your efforts.
mgrimmenator said:
will this eventually have a -100uv kernel.
Click to expand...
Click to collapse
Voltage Control = roll your own undervolt
The only real missing feature is BLN.
Can't seem to get it to download on my fiancee's phone.
Just flashed 9-27 through cwm and flashlight confirmed working. Awesome job
sent from my SCH-I500 PWGB 2. 0b3 voodoo , shot v7
Does this kernel support non OEM batteries?
Idea: RAM optimization, if feasible
Another Fascinating post by my XDA app...
So far this kernel is working out great for me. Loving voodoo color. Makes me wish I waited on buying that Thunderbolt off eBay. The cwm file didnt work for me (probably a bad download, stayed on bootanimation for WAY too long, lagging the animation) so I used the Odin version instead. Booted instantly. Many thanks for putting this together.
Sent from my SCH-I500 using Tapatalk
Originally Posted by djblu
I purchased SetCPU originally, can I use it instead?
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
IIRC the answer to that for this variety of overclock code is as follows.
Short answer: No
Long answer: Maybe but you might/probably will have problems
Click to expand...
Click to collapse
Thanks for the clarification. next question:
how do keep from getting stuck in boot loop? Do I need to reflash my recovery immediately after flashinging the kernal?
Sent from my SCH-I500 using xda premium
Hi, I am running leedroid's v5 and it works perfect but the governor smartassv2 is a little strange
Because after some time it locks to highest clock set and never go down again until I change governor and back again.
Is it supposed to work like this? How is it really supposed to work?
What governors do you guys recommend?
what oc program are you using?
System tuner pro
But leedroid just announced that there is a problem and he's trying to fix it so right now this thread is solved
hi all
now we have the doomkernel we can finaly play with the setttins
started this thread so we all can share the setting and foor noobies like myself share them so other can do their bennefit with them
I tried all the three apps..
setcpu; works damn fast but cant realy set the govenor ( not that i can figure out lol) maby some1 can help, great ics-theme
nofrill; makes my phone go cracy with reboots...but has the new cool thing that you can watch the batt-use like cpuspy.
incredicontrole; nice app you can set cpu,govenor and the voltages. but seems to give a little lagg
all of these set min/max to 192 - 1728 (seems like the standaard doom made it run with his kernel.)
smartassv2
cfq if possible
dont know how it works with the voltages..do i set them all lower ore just a few?
maby some1 already figured it out and can share..
hopefully this way the thread of the kernel keeps at developing an here the how to aply
I was using SetCpu which I had purchased and was causing a restarts on smartassv2
Bummer.
yesterday i tried al 3 of them and decidet to stick with setcpu...but after deleting the other my setcpu forced on demand evry time and couldnt get it back to smartass ore smartassv2..
i think maby all these apps are storing some kinda settings in the rom itself wich keep interfeering with the settings,
will try a fresh flash an keep just 1 without triying the other....
tried all, use incredicontrol - for a balance of power and battery, the best combo is ondemand with noop
[ Info ]
RC-1 Released
[ WARNING ]
Use this at your own risk!!
I am not responsible for any damange to your phone, pc, that you will get fired because alarm doesn't work
[ Features ]
- Overclock up to 1,15GHZ DON'T OVERCLOCK, JUST SELECT THE 1GHZ OPTION IN OVERCLOCK APP
- Cpu governess
- I/O Schedulers
- Recovery
- lots of new drivers
- Smooth
[ How to install ]
1. Download the boot.img
2. Flash it with fastboot (Fastboot flash boot boot.img)
3. Go to recovery, advanced and wipe dalvik cache!
4. reboot
5. ENJOY!!
READ THE FULL THREAD BEFORE ASKING ANY QUERIES OR REPORTING ANY BUGS/ISSUES
Credits:
Krabappel2548
Doomlord
KeiranFTW
Kamarush
ThJap!
Deepunknown
Shaan (S Advance)
Munjeni
my sources: https://github.com/nickholtus
Nick
If you want to user abt of thuis files, pm me first
Downloads:
Kernel: RC-1 Boot.img
just realised: this is my 1000ste post here on xda
RC-1
-Totally rebased the kernel
-Mainstream update 3.0.69
-Updated st-ericsson drivers
-Added lots of fixes (more then 80!)
-Added governers
-Added I/O schedulers
-A lot of other things!!!
-DONT USE OC, JUST USE THE 1 GHZ OPTION, otherwise system will lag. Will be removed in next version, this oc option was for test purposes)
last one
reserved..
just in case
Are the sources for Xperia P and U out?
yes they are
Thanks!
Flashed kernel a few minutes ago, looking good so far. I'm using smartassv2 governor and deadline scheduler, no overclock.
Hopefully there won't be any bugs to report
Just one thing: it would probably be a good idea to post stock WiFi modules, for those folks that may want to go back from your kernel to the stock one.
---------- Post added at 10:41 AM ---------- Previous post was at 09:56 AM ----------
Aaargh... scratch that, there are some issues with the new governors:
Scrolling in LauncherPro (between screens, in the app drawer) is jerky. Also in Pulse News and Pocket (ReadItLater), although not as bad as with the launcher.
It's the same for smartassv2, minmax, interactive.
Ondemand and performance are fine, smartass (not v2) is a bit better but still laggy.
Also, the device is slow to wake up, with any governor: takes about 2-3sec for the screen to turn on, after pressing the power button.
EDIT- forgot to mention, I'm running KA02 ROM... there may be conflicts with one of the init.d scripts that come with the ROM.
Would appreciate it if anyone running stock firmware would test the kernel and report back.
cezarL said:
Thanks!
Flashed kernel a few minutes ago, looking good so far. I'm using smartassv2 governor and deadline scheduler, no overclock.
Hopefully there won't be any bugs to report
Just one thing: it would probably be a good idea to post stock WiFi modules, for those folks that may want to go back from your kernel to the stock one.
---------- Post added at 10:41 AM ---------- Previous post was at 09:56 AM ----------
Aaargh... scratch that, there are some issues with the new governors:
Scrolling in LauncherPro (between screens, in the app drawer) is jerky. Also in Pulse News and Pocket (ReadItLater), although not as bad as with the launcher.
It's the same for smartassv2, minmax, interactive.
Ondemand and performance are fine, smartass (not v2) is a bit better but still laggy.
Also, the device is slow to wake up, with any governor: takes about 2-3sec for the screen to turn on, after pressing the power button.
EDIT- forgot to mention, I'm running KA02 ROM... there may be conflicts with one of the init.d scripts that come with the ROM.
Would appreciate it if anyone running stock firmware would test the kernel and report back.
Click to expand...
Click to collapse
The new governors just aren't optimized yet for new Xperia devices
It has nothing to do with the tweaks, but I can try to add some specific tweaks for the new governors, it might help
Sent from my MT15i using XDA
krabappel2548 said:
The new governors just aren't optimized yet for new Xperia devices
It has nothing to do with the tweaks, but I can try to add some specific tweaks for the new governors, it might help
Sent from my MT15i using XDA
Click to expand...
Click to collapse
Choice is good, but so many governors? I am no expert on this matter, which is exactly my point. Someone with a good understanding on how governors work should add options for, say, three scenario's:
- Performance. When needed, throttle to max. overclocked speed and switch to faster speeds sooner
- Medium, scenario between energy saving and performance.
- Energysaving. Do not overclock, set the clock the lowest setting possible when screen off, sleep mode and use moderate throttling just enough to ensure the device doesn't feel laggy but isn't as snappy as Performance.
Or.. post the settings for these scenario's here
hi,
i just added 4 governes
most of them are stock
ok good news
After a lot of testing, editing etc with Krabappel2548 we have got more frequences
normally we have 4 freq, now we have got 7 working
Release: Soon
also added 1.2ghz (if everything goes well)
Awesome work guys!
Just a couple of days of struggling with study, and then I''ll finally have some time to experiment with the phone. Hopefully this new kernel will allow a nice improvement in battery life
have a little improvement in battery life.
working on that...
nickholtus said:
have a little improvement in battery life.
working on that...
Click to expand...
Click to collapse
Yes, we are working on the kernel, we just added extra governors, I/O schedulars and extra CPU freq
ICS kerrnel v2 is released and on the Fileserver now Nick, maybe a little changlog?
quick panel
--
krabappel2548 said:
ICS kerrnel v2 is released and on the Fileserver now
Click to expand...
Click to collapse
Flashed v2, very slowly, even in his native launcher in ondemand mode.
On V1 was ok, only 2 times rebooted itself in sleep mode.
select another governer
conservative is fast
v2b or v3 will be released today or tomorrow without any lag
nickholtus said:
ok good news
...
also added 1.2ghz (if everything goes well)
Click to expand...
Click to collapse
Is there any problems with 1.2 GHz freq that you didn't include it to the ROM For now the highest freq is 1.15GHz...
no didn't add it
maybe in the next update (if we get some things figured out)