Related
DISCLAIMER: I AM NOT RESPONSIBLE FOR ANY HARD OR SOFTWARE BASED DAMAGE. IF YOUR PHONE BRICKS, YOU LOSE IMPORTANT DATA, OR OTHERWISE INCUR LOSSES AS A RESULT OF RUNNING THIS KERNEL, ITS NOT MY FAULT.
DELETE ALL VOLTAGE CONTROL SETTINGS, AND REMOVE BOOT SETTINGS FROM CM SETTINGS AND VOLTAGE CONTROL AND DISABLE SETCPU PROFILES BEFORE FLASHING THE LATEST UPDATE. THIS GOES FOR ALL UPDATES, INCLUDING UPDATING CM.
This is a CM7 based kernel with a 1.6 Ghz overclock, Voodoo sound and color fixes, uv support, and BLN. See the changelog for all the updates and features.
Informations (THESE CHANGE ON A REGULAR BASIS):
1. Max clock is set to 1GHz on the first boot, set the max clock in CM settings or voltage control or setCPU.
2. I cannot possibly stress this enough. IF YOU EXPERIENCE BUGS WHILE ON THIS KERNEL, POST HERE. Do NOT submit bug reports to the CM team, until you have flashed back to stock CM, and can verify the bug exists there too.
3. Use Xan's UV app to undervolt.It's in that market, search "Voltage Control".
4. Want to go back to stock? First, if there's any particular reason, please let me know. I love to feedback, good or bad. Then, just flash the latest official update.
5. Sources --> https://github.com/TheEscapistxda/andoroid_kernel_samsung_aries
6. BLN is disabled by default. Please enable it by using the BLN control app from the market.
7. Its not a bug. You're not bricked. Let it boot up.
Thanks to Netarchy for his Nexus S oc code, coolhbo for setCPU, the CMSGS team for their work, Supercurio for Voodoo, raspdeep for his oc/uv patches(showed me how to create a sysfs interface for uv), Xan for the uv app, neldar for BLN, and cyanogen for his amazing rom.
CHANGELOG:
V1:
Initial release
V2:
Voodoo Sound v4 added!
v2.2
Fixed the OC bug from v2
Fixed the OC bug from (the unreleased) v2.1
Added some initial testing code for UV!
Removed v2 from the downloads
Added a stock kernel to downloads
v2.3
Added wifi sleep workaround from coolya
v2.4
Updated to be in sync with the official releases
Removed some debug code (coolya)
Added compatibility with the cpusettings in CMparts(coolya & atinm) (Only works under updates after march 04 update, as it requires code in the actual rom.)
v3.0
Added compatibility with Xan's uv app!
v3.1
Added the new wifi sleep fix
Fixed the uv bug (hopefully)
Removed v3
v3.2
updated to stay in sync with the 03122011 nightly
yas259 fixes(don't ask me about these, this driver is way over my head)
radio fixes(not ril polling)
config edits
v3.3
updated to keep in sync with the 20111303 nightly
Lots of little tweaks
-kernel hz = user hz =100
-update timings (Thanks Kang)
-enabled Tiny RCU
Removed the returntostock kernel
v3.4
Updated Voodoo sound to v5
Implemented voodoo color v2
v3.5
Updated Voodoo sound driver number to v5 (now the control app says 5)
Added 600mhz and 1.3Ghz steps
Added interactive and smartass cpu frequency governors
Some initial work on BLN (disabled)
Added frequency_voltage_table for compatibility with custom frequencies in the uv app (disabled due to bugs)
v4.0 - (BUGGY, BETA RELEASE)
Increased voltage on 600mhz and 1.3ghz steps (let me know how this affects stabilty, guys)
Implemented BLN (VERY EXPERIMENTAL AND BUGGY)
Added states table to Voltage Control app that doesn't actually do anything.
Added Atimn/eifert's fix for the bad block issue.
v4.1
Fixed the stability issue on 1300mhz (Big thanks to kang for his help)
Added in the cardock fixes from xcaliburinhand (grab the "DockSound Redirector" app from the market)
fixed the ?mv bug in voltage control
Fixed bln (thanks to neldar)
Added 1000hz version of the kernel
Did a few tweaks to smartass, it's still kinda sketchy though
Updated voodoo sound to v6
There's probably more, I just can't remember them.
v4.2
More stability tweaks on 1300mhz
-The voltage for 1300mhz is now the same as 1200mhz, so you won't be able to undervolt it as much in the app, but it seems to help with stability.
Latest bln from neldar (fixes the touchkey disabled bug, and the touchkey on during sleep bug)
Enabled the microphone presets for voodoo sound
v4.3
Added 1400, 1500, and 1600mhz steps
Updated voodoo sound v7 (very little feature changes though)
Unlocked FPS cap
Built on latest upstream code (pulls in all fixes in recovery, etc. If people are still having bad block issues, let me know)
v4.4
Disabled some debug code
Fixed the ?mv bug on 400, 200, and 100mhz steps in voltage control
Fixed up smartass
Integrated the sdcard r/w cache fix (Thanks to Existz for pointing it out)
v4.5
Upstream fixes:
-New wifi driver
-New kernel flashing method, which should help bad block people
-Dual sd card sharing
Added a time that a frequency must stay at before scaling up in smartass
- You can tweak it same way as you can tweak all the other settings, its ramp_up_rate_ns
v4.6
Upstream fixes:
- Lots of random JVB merges, code clean up, etc.
Fixed the notification bug crash on the first v4.6
v5.0[May 3]
- Extend battery polling to 15s
- Sched_autogroup patch (increases smoothness under heavy load)
- New bootlogo
- Fix setCPU crashing on screen off
-Unified HZ (256) (should increase battery life, and has no adverse effect on performance)
- Reunlock fps cap
-Switch to the Codesourcery toolchain (should result in faster/smoother code)
-Full compatibility with 2.3.4
v5.0b[May 4][First Vibrant supported/tested version]
-Fixed touchkeys for real this time
-Temporarily enabled debugging (will be disabled in the next update)
-Fixed the crazy battery stats
-Reenable smartass governor
v5.1[May 6]
-Lots of upstream gpio changes
-Camera drivers kanged from JVB (REQUIRE THE LATEST NIGHTLY TO WORK)
- -03 optimizations
- Switched to hardware based floating point calculations (seems to increase performace under certain loads)
- Dropped 1.6ghz to 1.55ghz
-set default governor to conservative
- New captivate/vibrant specific initramfs
v5.2[May 12]
-new(old) modem_ctl
-tvout stuff
-fsa switch sleep
-overvolting cap
v5.3[May 16]
-upstream initramfs/initial flash changes
-Upstream change to the way battery percentage is calculated
-Lots of little( irrelevant) upstream changes
-Actually fixed the kernel version.
NIGHTLIES/WHENEVERS
#0[May 27]
+Way too many to list. Big changes include an update to 2.6.35.13, voodoo sound v9, and a properly working ril.
#1[May 29]
+States table in voltage control kinda works now, but is herp derp.
+Disabled ext2
+Re added the 1.6Ghz step
+Upped 1.55ghz freq by a few mhz
#2[July 12]
+Up to date with everything
+GPU bus controllable via Control Freak
+Other stuff
TheEscapist said:
NOTE: I need testers, as I dont have a vibrant. There *shouldn't* be anything that breaks specifically on the vibrant, but still.
Click to expand...
Click to collapse
Miui?? Trying it neways thanks
nickmcminn60 said:
Miui?? Trying it neways thanks
Click to expand...
Click to collapse
Epic Fail! So this should work with miui tomorrow after the 2.3.4 update? Can you post a 2.3.3 version?
nickmcminn60 said:
Epic Fail! So this should work with miui tomorrow after the 2.3.4 update? Can you post a 2.3.3 version?
Click to expand...
Click to collapse
I dont have a 2.3.3 source tree right now, so no. As for miui, probably, but I'm not officially supporting miui.
Sent from my SGH-I897 using XDA Premium App
TheEscapist said:
I dont have a 2.3.3 source tree right now, so no. As for miui, probably, but I'm not officially supporting miui.
Sent from my SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
No worries, ill just flash with miui tomorrow.
This kernel didnt boot it just went to the screen with the little computer
Went into recovery and flashed another kernel and it booted smoothly.
Sent from my SGH-T959 using XDA App
es7241 said:
This kernel didnt boot it just went to the screen with the little computer
Went into recovery and flashed another kernel and it booted smoothly.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
That's the custom boot screen. if the kernel didn't boot, you wouldn't have been able to get into recovery.
Sent from my SGH-I897 using XDA Premium App
i been running it for a day now
1.2 ghz smooth
1.3 ghz smooth
1.4 ghz starts to get choppy
1.5 ghz locks up reboots
1.6 un useable .
but its giving me good color, and operates pretty smooth at 1-1.3 ghz
brian(: said:
i been running it for a day now
1.2 ghz smooth
1.3 ghz smooth
1.4 ghz starts to get choppy
1.5 ghz locks up reboots
1.6 un useable .
but its giving me good color, and operates pretty smooth at 1-1.3 ghz
Click to expand...
Click to collapse
It sounds like you're unstable at the higher frequencies. Try playing with the voltages settings (I can't run 1.5 without undervolting), that might help.
Sent from my SGH-I897 using XDA Premium App
TheEscapist said:
It sounds like you're unstable at the higher frequencies. Try playing with the voltages settings (I can't run 1.5 without undervolting), that might help.
Sent from my SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
what settings do you reccomend ?
brian(: said:
what settings do you reccomend ?
Click to expand...
Click to collapse
Its different for every phone. If you want something to start off with, there is lots of people who have posted theirs in my captivate thread, and there is also an overclocking/undervolting guide by shaolin in the captivate forums.
Sent from my SGH-I897 using XDA Premium App
TheEscapist said:
Its different for every phone. If you want something to start off with, there is lots of people who have posted theirs in my captivate thread, and there is also an overclocking/undervolting guide by shaolin in the captivate forums.
Sent from my SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
ah, nonee seem to be working, i got 1.4 ghz to run tho, but im only getting 1744 in quadrant?
brian(: said:
ah, nonee seem to be working, i got 1.4 ghz to run tho, but im only getting 1744 in quadrant?
Click to expand...
Click to collapse
Because Quad scores are the be all and end all of a phone. (fyi: I pull anywhere from 1900 to 2600 at 1.55ghz).
If you're concerned, run linpack or some other cpu intensive task. If you keep getting an "Inaccurate" error in Linpack, you're probably unstable at that frequency, which could cause crashing, lag, slowness, etc.
Been running this for about 15 minutes and its running good so far, but one question how dangerous is this to the phone running at 1.5ghz as compared to 1.3ghz?
Sent from my SGH-T959 using XDA App
es7241 said:
Been running this for about 15 minutes and its running good so far, but one question how dangerous is this to the phone running at 1.5ghz as compared to 1.3ghz?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Any overclocking reduces the lifespan of a device, though typically from decades down to several years to a decade. Voltage wise, its a 100mv increase (though you can decrease it). It shouldn't be that much of a difference, and ive been at 1.5 for a while now, but obviously, there's always a chance.
Sent from my SGH-I897 using XDA Premium App
TheEscapist said:
Any overclocking reduces the lifespan of a device, though typically from decades down to several years to a decade. Voltage wise, its a 100mv increase (though you can decrease it). It shouldn't be that much of a difference, and ive been at 1.5 for a while now, but obviously, there's always a chance.
Sent from my SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
Thanks for the quick reply, I have voltage for 1.5, 1.4, & 1.3ghz to -25 , and the rest stock , ill see how that goes because either way ill probably end up buying a new phone soon 8)
Sent from my SGH-T959 using XDA App
es7241 said:
Thanks for the quick reply, I have voltage for 1.5, 1.4, & 1.3ghz to -25 , and the rest stock , ill see how that goes because either way ill probably end up buying a new phone soon 8)
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Just watch you temp. Run it at 130f all the time it wont last a month.....just keep it cool.....
nickmcminn60 said:
Just watch you temp. Run it at 130f all the time it wont last a month.....just keep it cool.....
Click to expand...
Click to collapse
Not sure what that is in celcius (Canadian here), but under 45c is a good limit to aim for. Charging cuts off around there, not sure the exact value off the top of my head.
Sent from my SGH-I897 using XDA Premium App
VIBRANT edition of the Platypus Revolutions kernel
This Project is inactive/low activity for a longer period of time
Kernel
CM7 & MIUI only
NEO series
(since May 24th '11)
Do you want to discuss on this kernel, get the news on the current state of development, or test kernels even fresher than fresh ?
connect via webchat from your browser:
http://webchat.quakenet.org/
and join #platypus-kernel
(recommended)
Fire up your IRC client, and join via client
the server (for now is) : irc.quakenet.org
port : 6667
Channel : #platypus-kernel
(thanks to Tk for the layout idea )
before you ask for any ETAs:
The first rule of CyanogenMod [and this project]: DO NOT ASK FOR AN ETA!
---------------------------------------------------------------------------------------
First step before install & kernel switch:
Always have this cleaning script on your internal SD card ready
If you're
- switching kernels,
- have issues with auto-rotation,
- the cam,
- bootloops
- want to remove init script
- recover from a failed overclock attempt
please give either:
- lippol94's updated cleaning script (apply via CWM recovery): http://www.multiupload.com/XFH1GCK4MB
or
- WiwiPouPou's SYSTEM CLEANER SCRIPT (also apply via CWM recovery): (http://forum.xda-developers.com/showpost.php?p=14805606&postcount=21739)
a try
the kernel already applies some cleaning steps during install but sometimes that's not enough ...
---------------------------------------------------------------------------------------
Introduction:
Hi guys,
this is my first modded kernel for the SGS (CM7/MIUI only)
I first needed to test it to make sure that it'll be stable & boot at the first place
so far it's very fast & responsive & smooth
This thread shall serve as the center for my testing kernels (stability & functionality-wise)
DISCLAIMER: the kernel (binary) and driver modules are provided as is. If problems occcur they most probably are from upstream and can be fixed with the newest version. Since I'm doing this in my free spare time as a hobby (quenching my thirst for tweaks & performance) updates will occur irregularly as time permits and I see fit (most probably when new features & bugfixes arrive). YOU are responsible for the actions that you take (such as over- or underclocking), etc. You agree that I can not be held liable for any potential damage that arises from your actions in combination with or the usage of this kernel and other related parts.
Kudos:
* Google, Andy Rubin & the whole Android crew
* Linus Torvalds & the kernel hackers for upstream Linux
* cyanogen & all the devs out there hacking on this
* Supercurio for enriching our media experience of this smartphone
* codeworkx, coolya, guiper, atinm - the whole teamhacksung|cmsgsteam crew and all other hackers working on CM7
* laststufo, hardcore, nikademus, existz and all the other kernel hackers on the SGS forum
* zen-kernel team for inspiration to create a kernel, too
* all other contributors (devs, users, etc.) who make this possible
The purpose of these kernels is extensive stability testing addressing the following sticking points:
- overall stability & functioning of the kernel and phone
- call drops, missed calls, etc.
- lags (suggestions for improvements are welcome)
- auto-rotation, sensors, etc.
- Voodoo Control Plus [any crashes ? compatibility problems ?]
- working on CM7 or MIUI ?
- scheduler, sound, video synchronisation & lags: Tap Tap Revenge 4 (especially at the beginning of songs)
- scheduler, sound, video synchronisation and any other issues: doodle dash (while shooting & sound activated)
- proper pmem memory layout & settings: proper functioning of Google Googles
for those who love SAUCE (Source):
old source:
ALL MY SAUCE for QUORRA KernalZ ^^
new source:
android_kernel_samsung_aries
(fork and 1:1 update to upstream kernel source - changes in different branches)
(latest changes sometimes might not be in [yet] but in the whole repo everything should be available)
current UV & OC stable values:
Recommended apps for OC/UV:
- Pimp my CPU (also available here on XDA for those who don't have a credit card, etc.)
- Xan's VoltageControl
on stability testing:
http://forum.xda-developers.com/showpost.php?p=13255871&postcount=5
(start with "Q: I'm new in OC/OV operations so please could you explain to me how to set it in the best way?")
the following OC/UV values are only applicable for kernels with the old OC/UV implementation (max. 1.3 GHz)
my current UV (undervolt) stable Values :
old OC/UV implementation (morfic, bilboa1/kang, TheEscapist):
1300000 0 (haven't tested 1.3 GHz much yet)
1200000 -25
1000000 -50
800000 -75
600000 -100
400000 -100
200000 -125
100000 -150
edit:
1200000 -50
1000000 -75
800000 -75
600000 -225
400000 -125
200000 -150
100000 -175
thanks jetcz !
new OC/UV implementation (morfic, bilboa1/kang, TheEscapist - Tk-Glitch):
Tk-Glitch said:
Note that these UV settings will be unstable on many devices. It's only informative.
1600 MHz - 1.500v / -> That's high and many devices will fail on this frequency. Find working UV for you if any.
1500 MHz - 1.500v / -> That's high and many devices will fail on this frequency. Find working UV for you if any.
1440 MHz - 1.475v / -75mv
1400 MHz - 1.450v / -75mv
1300 MHz - 1.400v / -75mv
1200 MHz - 1.350v / -75mv
1000 MHz - 1.250v / -50mv - If you have stability issues, try to let this one by default.
800 MHz - 1.200v / -75mv
400 MHz - 1.050v / -100mv
200 MHz - 0.950v / -150mv
100 MHz - 0.950v / -200mv - (can be very different between two devices)
More volts is not always equal to more stability. Try to add more UV (less volts) if the frequency you're trying to achieve is unstable.
Considering all phones will respond differently to OC/UV, to tweak the values to suit your device will be required.
By default, no overclock/undervolt is applied. You'll need to use one of the tools below to adjust the frequencies and voltages.
Note : Never ever use SetCPU with this kernel. You could encounter many stability problems like random reboots or bootloops.
Click to expand...
Click to collapse
3D performance and games:
recommended apps:
[root] Chainfire3D
1st backup post (kernels)
Kernels:
kernels are listed in descending order
older -> newer (newest at the bottom - for now)
NEO 07
Link: http://forum.xda-developers.com/showpost.php?p=14731525&postcount=137
NEO 09
Link: http://forum.xda-developers.com/showpost.php?p=15044144&postcount=206
NEO 10
Link: http://forum.xda-developers.com/showpost.php?p=15141552&postcount=232
NEO 09-redux_V5
[Gingerbread bootloader support + access to external (micro)SD - no hourly battery drain anymore !]
http://forum.xda-developers.com/showpost.php?p=16298709&postcount=310
NEO 16 codename: Beast
http://forum.xda-developers.com/showpost.php?p=16552743&postcount=380
NEO 17 -r12 codename: Butterfly
http://forum.xda-developers.com/showpost.php?p=17339844&postcount=500
NEO 17 -r18 codename: Butterfly
http://forum.xda-developers.com/showpost.php?p=18268541&postcount=566
NEO 18-update1 codename: funky fish
NEO XX.1-update1 codename: mighty rhino
http://forum.xda-developers.com/showpost.php?p=20000100&postcount=630
ALL USERS MUST UPDATE (this fixes yet another potential data loss trigger)
2nd backup post (Changelogs)
Changelog list:
currently obsolete
3rd backup post (modems list)
modems:
Description:
Modems play a crucial role in how much battery drains in standy.
e.g. if you have a good signal area and the modem still has high
"Time without a signal" indicator under Cell standby you still will get bad standby time
make sure you have little to no "Time without a signal" in Cell standby
there also somewhat seems to be a connection between "Time without a signal" and high "Android OS" number in battery use (!)
Following modems are only compatible with new radio (modem) partition layout:
radio-cm-7-GalaxyS-JVP-signed.zip (4.29 MB)
md5sum: fb38dbf82daf0720fd2328f5f649013e radio-cm-7-GalaxyS-JVP-signed.zip
For more modems & bootloaders please go to siky_dude's Modem Thread:
[CM7/MIUI][28.08.11] Modems + Bootloaders(MD5)
[SGS / i9000 Thread so some frequencies might be missing, e.g. 850 MHz]
for more modems please refer to a modem thread in the Vibrant Forums section
4th backup post (results)
Results & FAQ/Documentation
Results:
(04/27/2011) Results for platypus-kernel_20110427_18_quorra_r1:
- broken auto-rotation & sensors for some [insert ROM (CM7 ? MIUI ?)]
- stable
(05/03/2011) Results for CM7_SGS_platypus-kernel_20110503_17_quorra-r4_exp
- high battery drain, either due to kernel config or optimization flags, fixed with >= quorra r5 (2nd update)
FAQ / Documentation
@bootloop / boot post victims ^^
Hi guys,
could you please try to replace the existing kernel on your MIUI or CM7 nightly CWM-Package with my kernel, modules and its scripts ?
then install that updated package (with the new kernel, modules and scripts)
after that all should work
the bootloops seem to be an issue with bml_over_mtd (broken sectors on the SSD on your phone)
I'll investigate this and see if anything needs to be rewritten and/or updated in that regard
Thanks !
Overclocking / Undervolting:
Q: I'm new in OC/OV operations so please could you explain to me how to set it in the best way?
A: start with -50 mV (delta from default value) other values probably are too low
my testing includes:
- Angry Birds Rio (several missions)
- Gun Bros (for some time)
- mp3 playback, (flac playback - optional)
- surfing the web via browser, opening up bit.ly links from cmsgsteam twitter feed
- watching youtube video
- watching video via rockplayer lite or mobo video player
- running benchmarks (Smartbench 2011, quadrant standard, an3dbenchXL, anTutuBench)
- Labyrinth Lite (for gravity sensor), auto-rotation (also for sensor)
when 1 GHz (1,2 or 1,3) is OK - go lower with undervolt value (e.g. -75 mV)
after it gets un-stable - go back to last known stable value
then you can limit max frequency to lower one, e.g. 800 MHz
and repeat testing for that frequency
for more info: checkout shaolin95's Mini Overclocking Guide:
Link: http://forum.xda-developers.com/showthread.php?p=12910471#post12910471
LED Support FAQ
Q: Do LED notification require an app, such as BLN, etc ?
A: No. It uses Android's and Cyanogen settings, other apps are not required, although some that are designed for regular LEDs may work.
Q: How to I turn off LED notifications, scheduled or/and complete turn off?
A: Use Cyanogen's Quiet Hours feature (settings>cyanogen>sound>quiet hours) and check "Dim the LEDs during quiet hours" (in reality it will turn them off on the SGS). If you schedule a complete day, then LED notifications will be off all the time.
Q: How do I setup per app, find other LED settings etc?
A: Settings>cyanogen>interface>LED notifications
Q: What to do with LED color settings?
A: We have only one color, so that doesn't work. Use Green as default setting. Some non-bright colors turn off notification, as it's the equivalent as diming LEDs (note that on real LEDs if you dim them too much they look like off too anyway, the difference is that it's gradual. On the SGS the LEDs can be only on or off, not gradual)
Q: How can I troubleshot my system, I can use ADB but...
A: adb logcat | grep lights (on linux) will show you Android requests to turn LED on or off. "status" tells you what we decide will be interpreted as "turn LED on" (1= on, 0 = off)
adb shell cat /proc/kmsg for live view (or adb shell dmesg if you're using adb after the issues occurs - careful the backlog is limited in size so don't be too slow)
notify_led_on and notify_led_off are requests to the kernel to turn LED on or off.
touch key write/read errors (cypress) are non-fatal failures to ask the touch key to do something (eg lit up the LED), when the hardware goes crazy or there's a logical error in the code (can be both)
touch key recovery routine or "stopped responding" are either hardware errors, either a logical error where the driver would try to write something the touchkey doesnt understand. in some occasion lock&unlock fix those as a work around, of course a permanent fix is required
Voodoo Color settings:
Q: I don't have that nice ice-ish white color on my screen anymore - you suck !
Q: my screen looks like someone pissed on the screen - you suck !
(sorry for the language ^^)
A: I love you too ^^
download Voodoo Control or Voodoo Control Plus
Screen RGB multipliers:
- Red: 321*
- Green: 321*
- Blue: 429*
Screen v1 gamma hack:
- use Alt. settings
- or if you prefer others - use: "Reset to 2.3.3 defaults", "Punchy settings" (punchy could lead to a great screen while locking the screen and having "screen off" animation disabled)
other recommended settings:
Also a lil tip for people who use voodoo color!
1 )Color Profiles: Voodoo Profile V1
2 ) Screen v1 gamma hack :
- 50 red
- 53 green
- 44 blue
3 ) SRB multipliers:
Red ="2300875360"
Green ="2300875360"
Blue ="2709919680"
With those adjustment, black colors are BLACK and white colors are WHITE. Everyone should try this.
Click to expand...
Click to collapse
SGS CM7 nightlies wiki
http://sgscm7nightlies.pbworks.com/w/page/41483487/FrontPage
Android OS bug, :
(thanks to ceriko ! and his awesome guide for DarkyROM 10.1)
If your battery drains very fast and your battery stats mentions Android OS above 10%, often between 40 and 60%, sometimes more, this is the best to do as far as I know:
- Remove the 2/3 system files as per the beginning part of this guideguide about batterie issues.
- Install WatchDog and open (I set it to "moderate", then I close it, that's all), this app will warn you whenever an app or a process miss-behaves by draining the battery excessively. It will not fix it but just flag it and you will see a notification.
- Reboot usually stops the drain for a while until it naturally comes back, so reboot whenever you see Android OS above 10% and rising or after you see WatchDog mentioning "Suspend" process using too much battery (the suspend process hanging is the Android OS bug).
- Some apps trigger it, most common are Gameloft games (blame Samsung, not the games/apps). No need to use apps or games for this drain to happen, it also happens straight after boot once phone has been fully charged.
This bug can not be fixed by anyone but Samsung. Some never see it, some will experience it everyday no matters what they do... It's just annoying and unfair but that's the same on all Gingerbread releases by Samsung (JVK, JVB, JVO, JVH). Apparently even the SGS2 has this...
screenstate scaling aka my governor won't change after screen locked:
So what is this all about ?
it's an init script that is put in to /system/etc/init.d
and switches between the configured governors in the script
depending on whether the screen is on (AWAKE_GOVERNOR) or off (SLEEP_GOVERNOR)
in most cases your phone is off - in that case it would be good to use a governor which doesn't fire up the cpu frequency too fast since you don't need it (no GUI, smooth scrolling, etc. needed while the screen is off - lol),
so conservative governor is set
when using the phone (screen on) it really depends on what you want to do: e.g. latency & smoothness is crucial: try smartass2, smartass, ondemand;
you're mainly browsing & reading stuff: try ondemandb, conservative (the screen is already burning enough battery so you don't need another component burning yet more)
only use one governor at a time
e.g.
AWAKE_GOVERNOR
# AWAKE_GOVERNOR
# AWAKE_GOVERNOR
SLEEP_GOVERNOR
# SLEEP_GOVERNOR
# SLEEP_GOVERNOR
that means lines with "#" are commented out and not used by the script
e.g.
# AWAKE_GOVERNOR
AWAKE_GOVERNOR
# AWAKE_GOVERNOR
SLEEP_GOVERNOR
# SLEEP_GOVERNOR
# SLEEP_GOVERNOR
also would work (intentionally not filled in any governors)
5th backup post (you never know )
yet to be declared
MIUI kernels == MIUI + CM7 prior to RIL switch to Samsung's (closed source) RIL
CM7 kernels == CM7 with newer RIL only
Kernel
CM7 & MIUI only
NEO 04-energy
(energy efficient build for max battery runtime, efficiency & smoothness)
(NEO_01 was internal build)
before you ask for any ETAs:
The first rule of CyanogenMod [and this project]: DO NOT ASK FOR AN ETA!
Changelog (from NEO_03):
- fugumod security hardening re-added
- optimized memcopy & memmove for maximal efficiency & speed
- optimized for size (less cache-misses & leaner and [perhaps] faster system)
- optimized for NEON-usage
- conservative-governor ONLY (one governor to rule them all) - battery consumption + performance == win + win
- FIQ-console disabled (probably less overhead + battery savings)
- LED notifications disabled - only LED light timeout enabled (battery savings)
- printk time-stamps disabled (probably less overhead + battery savings)
- fixed HD Video recording + mic recordings (sound works again)
- "old" OC-UV-implementation OC until 1.3 GHz
- re-added Nick Piggin's inode integrity patches (2 of them) - (more stability & perhaps some saved cpu cycles -> battery)
- re-added several of the previously not included patches from quorra kernel-base
not yet included:
- fugumod security improvements (thanks to nikademus for sharing the source !)
- bluetooth l2cap powersave mode
- and many more
current stable UV values (for me)
1000 -50 mV
800 -75 mV
600 -225 mV
400 -125 mV
200 -150 mV
100 -250 mv
Download Link:
Mirror #1:
CM7 / new RIL:
CM7_VIBRANTMTD_20110529-10_r_platypus-revolutions-kernel_0_NEO_04-energy.zip
MIUI / CM7 / old RIL:
CM7_VIBRANTMTD_20110529-09_MIUI_platypus-revolutions-kernel_0_NEO_04-energy.zip
(thanks to Roland for hosting !)
Mirror #2:
this post
Troubleshooting & short-FAQ:
- WIFI & stuff not working ?
lippui94 cleaning script, then wipe dalvik, then fix permissions, then kernel - eventuall governor switch - , then wipe dalvik, then wipe cache, then fix permission
- reboots during calling ?
please report ASAP !
this is supposed to be fixed & a non-issue [if it's still happening try with different nightly]
- Radio (phone function) not working ?
new RIL kernels only work with nightlys > #12 on the SGS (including #12)
- phone is not as smooth as with previous kernel releases
yeah - sorry, might be due to the fact that I'm forced to use stock toolchain (less optimized toolchain)
sticking points to test & feedback:
- call drops, reboots during calling & potential instabilities
- general stability (if this also happens on stock: post but add a note that it's from stock - thanks !)
- BT & WIFI switching
- HD video recording & playback (is smooth for me during playback, recording with HD & Youtube HD works)
- mic recording, HD video + sound (tested & should work)
- iptables
- battery runtime
- smoothness
Link to old thread + 2nd mirror (thread):
http://forum.xda-developers.com/showpost.php?p=14260897&postcount=392
hitman818 said:
It says nightly #12, do you mean the one that came out today, cm7.1.0?
Sent from my SGH-T959 using XDA Premium App
Click to expand...
Click to collapse
please read all of it
#12 on the SGS (including #12)
Click to expand...
Click to collapse
it's a different numbering scheme
kernel with new RIL applies to:
SGS: >= #12
CAPTIVATE: >= #14
VIBRANT: >= #9
I think ill stick with neo 3 it is the only kernel with working bln on miui. And is very fast and stable no complaints.
i just flashed neo 4 on lasted cm7 build. getting no service..
I just tried the old ril one and I had no service either on the new cm7 update.
Yeah, no service for me either
Sent from my SGH-T959 using XDA App
So far so good for me, flashed the old RIL on CM7 V8 and everything is working.
good on latest miui im running with UV its a little slow, does undervolting too much reduce speed or just stability?
gamikzone said:
good on latest miui im running with UV its a little slow, does undervolting too much reduce speed or just stability?
Click to expand...
Click to collapse
Reduced stability=reduced speed
If u want BLN to work try NEO3
nickmcminn60 said:
Reduced stability=reduced speed
If u want BLN to work try NEO3
Click to expand...
Click to collapse
what exactly does bln do? and i was able to improve the speed these are my rates that i find as a good UV
1300 0
1200 0
1000 -25
800 -25
600 -50
400 -50
200-75
100-75
gamikzone said:
what exactly does bln do? and i was able to improve the speed these are my rates that i find as a good UV
1300 0
1200 0
1000 -25
800 -25
600 -50
400 -50
200-75
100-75
Click to expand...
Click to collapse
BLN uses the capacitive buttons as a notification LED for when you get a text, an email, or something. In the newest builds of CM7, however, it has been disabled.
Sent from my SGH-T959 using XDA App
BLN - Overrated IMO
BLN = Big Lame Nothin'
or
BLN = Battery Leeching Nuisance
END OF LINE
w8 wtf?
galaxy S modems on the Vibrant?...
please tell me that's not what your doing...
apollo15rover said:
BLN = Big Lame Nothin'
or
BLN = Battery Leeching Nuisance
END OF LINE
Click to expand...
Click to collapse
opinions are li......
Introducing the new variant of Bali kernel, Bali for CM7. The main goal of this kernel is the same as other Bali kernel, balanced performance and battery life. I can't guaranteed you will get the same battery life as Bali for Froyo but you will definitely get an improve battery life over stock kernel.
Features:
- OC/UV up to 1.4GHz (Safe boot to 1GHz) [require setCPU from market]
- Voodoo Sound v10
- Voodoo Color
- Multiple CPU governor, smartass included (default: ondemand)
- Multiple IO scheduler (default: BFQ)
- LED notification support (no external app required)
- CIFS support
- Support SetCPU screen off 100/400 profile
- Dock sound redirector support [need Galaxy Dock Sound Redirector app from market]
Disclaimer:
As always, I'm not responsible with any damage cause to your phone.
Special Thanks:
- Team Whiskey - you guys are awesome.
- Alexia - for great work on the new splash image.
- Supercurio - for awesome work on Voodoo
- xcaliburinhand - for wonderful work on dock sound redirector.
- Everybody at CM dev community for their hard work on this awesome ROM.
- Everybody at #teamwhiskey for beta testing this kernel and their support.
I apologize if I miss anyone ..
Flashing Instruction:
- If you're coming from another kernel, flash "Ultimate Kernel Cleaning Script" by lippol94 first (http://www.multiupload.com/XFH1GCK4MB)
- Once that's done .. then flash Bali-CM
If you don't know how to flash then this is not for you.
Download:
Bali-CM_v2.2.2
Change Log:
Code:
- 2.2.2 [10/18/2011]
CM update
Re-enabled LED by default
- 2.2.1 [9/12/2011]
Fixed screen jitter issue
- 2.2 [9/10/2011]
Upgraded BFQ to v2
Added Smartass v2 with extra tweak
Fixed ondemand and tweaked for smoother experience
Set ondemand as default governor
Other fixes and tweaks
- 2.1 [9/1/2011]
Disabled SLQB and revert back to SLUB
Disabled LED notification for the time being
Added more UV settings
GPU tweaks
Added v(r) scheduler
Added Tiny Preempt RCU
And other tweaks and fixes
- 2.0 [8/25/2011]
Disabled ramzswap and switched to zram
Enabled zcache for better IO performance
Memory tweak, now gives you 340MB
More tweaks
- 1.2.1 [8/19/2011]
Fixed video playback issue
Fixed battery report when charging, it goes to 100% now
- 1.2 [8/18/2011]
Updated source with the latest CM patches
Added SLQB slab allocator for better memory management
Added more tweaks
- 1.1.1 [7/26/2011]
Fixed kernel instability that cause random reboot
- 1.1 [7/26/2011]
Added Voodoo color V2
Fixed UV portion to make it easier to manage
Added Voltage Control support
Added compiler tweak
- 1.0 [7/22/2011]
Initial release
A little explanation on different governors (taken from Lord ClockAn thread):
- interactive - Instead of sampling the cpu at a specified rate, the governor will scale the cpu frequency up when coming out of idle. When the cpu comes out of idle, a timer is configured to fire within 1-2 ticks. If the cpu is 100% busy from exiting idle to when the timer fires then we assume the cpu is underpowered and ramp to MAX speed.
- smartass - Is an improved version of interactive governor
- ondemand – Available in most kernels, and the default governor in most kernels. When the CPU load reaches a certain point (see “up threshold” in Advanced Settings), ondemand will rapidly scale the CPU up to meet demand, then gradually scale the CPU down when it isn't needed.
- conservative – Available in some kernels. It is similar to the ondemand governor, but will scale the CPU up more gradually to better fit demand. Conservative provides a less responsive experience than ondemand, but can save battery.
- performance – Available in most kernels. It will keep the CPU running at the “max” set value at all times. This is a bit more efficient than simply setting “max” and “min” to the same value and using ondemand because the system will not waste resources scanning for CPU load.
- powersave – Available in some kernels. It will keep the CPU running at the “min” set value at all times.
- userspace – A method for controlling the CPU speed that isn't currently used by SetCPU. For best results, do not use the userspace governor.
Q and A:
My screen has green, yellow, or orange tint.
Use Voodoo Control to set color profiles (courtesy of d_phekt)
Screen RGB Multipliers:
Red = 230996000
Green = 230996000
Blue = 2704668800
Screen v1 Gamma Hack:
Red = -50
Green = -53
Blue = -44
is GPS still functional with this kernel?
gamikzone said:
is GPS still functional with this kernel?
Click to expand...
Click to collapse
Yes .. GPS still functional.
drhonk said:
Yes .. GPS still functional.
Click to expand...
Click to collapse
im about to flash this hows ur battery life compared to stock? im getting pretty good battery on stock who knows how great it will be with this
gamikzone said:
im about to flash this hows ur battery life compared to stock? im getting pretty good battery on stock who knows how great it will be with this
Click to expand...
Click to collapse
Just like other Bali kernel .. it takes 2 - 3 days to settle in, but my beta testers reported anywhere from 15 - 20 hrs average. I myself got 18hrs with 2 push email accounts, twitter, sms, and few calls.
drhonk said:
Just like other Bali kernel .. it takes 2 - 3 days to settle in, but my beta testers reported anywhere from 15 - 20 hrs average. I myself got 18hrs with 2 push email accounts, twitter, sms, and few calls.
Click to expand...
Click to collapse
thats good im getting around 14 hours with stock, have u tried the ondemand setting for your cpu? i seem to get better battery life with that compared to conservative
gamikzone said:
thats good im getting around 14 hours with stock, have u tried the ondemand setting for your cpu? i seem to get better battery life with that compared to conservative
Click to expand...
Click to collapse
Try smartass with this kernel ..
drhonk said:
Try smartass with this kernel ..
Click to expand...
Click to collapse
i think i will try this out tonight
I believe this will be ok to use with miui.
Nice animation.
Looks like not meant for Miui. after seeing the animation (Approved Cyanogen Bali), it turns black and wont turn on. Need to pull the battery.
jay661972 said:
I believe this will be ok to use with miui.
Nice animation.
Click to expand...
Click to collapse
Trying it out , any recommeneded UV settings?
Sent from my T959 using XDA App
jay661972 said:
Looks like not meant for Miui. after seeing the animation (Approved Cyanogen Bali), it turns black and wont turn on. Need to pull the battery.
Click to expand...
Click to collapse
It does work on miui,
Sent from my T959 using XDA App
drhonk said:
Try smartass with this kernel ..
Click to expand...
Click to collapse
would downloading SetCPU and just setting the governor to smartass improve battery life? or do you have to actually UV and all that
Really, how did you do that? I did the clean script first and flash Bali.
es7241 said:
It does work on miui,
Sent from my T959 using XDA App
Click to expand...
Click to collapse
Okay I will try this one more time.
jay661972 said:
Okay I will try this one more time.
Click to expand...
Click to collapse
confirmed .. it works on MIUI since I just flashed MIUI with it.
jay661972 said:
after seeing the animation (Approved Cyanogen Bali), it turns black and wont turn on. Need to pull the battery.
Click to expand...
Click to collapse
Same here except im flashing from trigger redux #12 and ive tried flashing from trig w/glitch and w/du jour
Sent from a cell tower to the XDA server to you.
now that's the trick. if you have glitch kernel, you need to re-flash stock miui rom then flash Bali. It works now for me
drhonk said:
confirmed .. it works on MIUI since I just flashed MIUI with it.
Click to expand...
Click to collapse
jay661972 said:
now that's the trick. if you have glitch kernel, you need to re-flash stock miui rom then flash Bali. It works now for me
Click to expand...
Click to collapse
So you can't flash bali on miui energy? You have to revert to stock miui?
Sent from my T959 using XDA Premium App
Aperture Laboratories presents
GLaDOS V2.11
The latest innovation in human-smartphone interaction. Our scientist have shown in extensive tests that humans operating our kernel on their devices experience 67% more joy in life while simultaneously the likelihood of being maimed or killed by falling space debris is significantly reduced. Also preliminary human trials indicate that it might offer some protection against lethal dosages of gamma radiation and blows to the head with a rod-like object.
Features:
Based on stock Android kernel 3.0.8 IMM76D
CPUfreq governor 'lazy'
Live OC version 1
Custom Voltage version 1
Battery Life eXtender (BLX) version 1
Power saving state DEEP IDLE version 2
Touch Wake version 1
Backlight Dimmer (BLD) version 3
Backlight Notification (BLN) version 9
Brain **** Scheduler (BFS) version 0.357
SLQB memory allocator
Voodoo Color version 2
Voodoo Sound version 10
CIFS
TUN
Bigmem (+20 MB more available RAM)
USB OTG build 5
Download:
http://goo-inside.me/devs/aperture/GLaDOS-NexusS (thanks to goo-inside.me for hosting)
Always make a backup of your /efs/ directory (http://forum.xda-developers.com/showthread.php?t=1138873) before installing custom kernels or ROMs.
During installation the cache partition, Dalvik-cache and modules, init.d scripts and bootsounds from previously installed kernels are cleaned.
Source code:
https://github.com/Ezekeel/GLaDOS-nexus-s/tree/glados
Do not use profiles, they are unnecessary and only lead to instabilities.
If you experience any problems and are on a nightly or kanged ROM, try the latest stable version of that ROM first. I will not give support or answer any questions if you do not try this before reporting a problem with the kernel.
If you experience stability problems like reboots, freezes, FCs and SoDs and you did OC or UV, first try changing back to the stock settings. If this solves the problems, your OC/UV configuration is not stable. There are some indications that OC/UV settings which run fine at high battery charges might still cause problems at lower battery charges. So to be safe always check that your OC/UV configuration runs fine at low battery like 5%.
I do not offer support/help/recommendations on OC/UV. If you decide to do so and your device is unstable you are on your own. Check http://forum.xda-developers.com/showthread.php?t=1335429 for help.
If you experience the problem that the DEEP IDLE state is not properly used (according to the idle_stats), read the last section of http://forum.xda-developers.com/showpost.php?p=18299324&postcount=1.
When reporting a bug always include information about your ROM and hardware model. Also be as precise as possible when describing the problem. Just because a single person is experiencing a problem, it does not mean there actually is a problem with the kernel. I always wait until at least one other person can confirm the issue before I look into it. So if you see someone posting a bug report, do not be shy and feel free to confirm the issue or if you do not have the problem let me know that too.
When asking for a feature you would like to see implemented in GLaDOS always provide a link with information about this tweak and preferably also a link to the source code.
Aperture bootanimation courtesy of rascarlo (www.twitter.com/rascarlo)
For users unfamiliar with init.d scripts I recommend NSTools by arifhn (http://forum.xda-developers.com/showthread.php?t=1333696) for managing the various tweaks.
Changelog
GLaDOS-V2.11
Added kernel patches for Android 4.0.4 update.
Fixed bug with Touch Wake.
The kernel installer no longer modifies the ramdisk for adding init.d support.
GLaDOS-V2.10
Added USB OTG build 5 by sztupy.
Fixed small bug in Custom Voltage.
Fixed bug in Live OC.
Changed to new bootanimation by Rascarlo (many thanks!).
Changed default V1 gamma values for Voodoo Color to stock settings.
GLaDOS-V2.9
Fixed two small bugs in LiveOC.
Fixed small bug in Lazy.
Reduced display frequency back to stock settings.
GLaDOS-V2.8
Fixed a bug in LiveOC.
Fixed optimized compiler flags.
GLaDOS-V2.7
Fixed TouchWake issue of long powerkey presses causing the touch controls to be disabled without delay on next screen off.
For BLN the blink interval and blink time can now be adjusted in the sysfs interface. Also BLN is disabled by default.
For lazy the sampling rate is initialized to a default of 15000.
GLaDOS-V2.6
Fixed the problem of the CAM module being active all the time preventing DEEP IDLE from being used.
GLaDOS-V2.5
Fixed bug.
Removed several unnecessary kernel drivers and features.
Removed kernel debug and logging features.
Included logger as a module.
GLaDOS-V2.4
Fixed bugs in Live OC.
GLaDOS-V2.3
Fixed the freeze/reboot problems when changing the frequency limits.
GLaDOS-V2.2
Removed the limit of the minimum frequency to 200 when the GPU is active.
Preliminary bandaid to DEEP IDLE compensating for various bugs in ROMs.
GLaDOS-V2.1
Added Voodoo Color version 2 and Voodoo Sound version 10.
GLaDOS-V2.0
Update to Android kernel 3.0.8 for ICS 4.0.3 IML74K.
GLaDOS-V1.12
Fixed the camera problems caused by Bigmem (increases available RAM by 21MB now).
GLaDOS-V1.11
Added Bigmem option (increases RAM available for the system by 26MB).
GLaDOS-V1.10
Added DRAM scaling to Live OC.
Flash memory I/O tweaks.
Added Tiny Preemptive RCU.
Updated the optimized CRC32 algorithm.
Removed CFQ I/O scheduler.
GLaDOS-V1.9
Added OC frequency states 1.4GHz and 1.2GHz.
GLaDOS-V1.8
Fixed the problem of the touchkey backlight lighting up when touched while the screen is off.
Increased display frequency to 72Hz necessary to achieve 65fps.
GLaDOS-V1.7
Fixed the increased battery drain while in SLEEP when DEEP IDLE is enabled.
Fixed the problem on the NS4G of DEEP IDLE not being used while 4G is enabled.
GLaDOS-V1.6
Disabled most logging and debugging kernel config options.
Included logger and TUN as modules.
During installation the cache partition, Dalvik-cache and modules, init.d scripts and bootsounds from previously installed kernels are cleaned.
Removed '98touchscreen' init.d script.
Aperture bootanimation and -sound courtesy of Euphorie (http://forum.xda-developers.com/showthread.php?t=1061627).
GLaDOS-V1.5
Fixed problems with setting voltages and min/max frequency with SetCPU.
Fixed problems with the vibrator and DEEP IDLE.
Improved stability of wireless connection.
GLaDOS-V1.4
Updated to latest toolchain arm-2011.03-41
Optimized compiler flags
Added optimized RWSEM
Fixed BLD bug for i9023 of the touchkey backlights not getting re-activated on touch
Changed to advanced TCP congestion scheduler VENO
GLaDOS-V1.3
Improvements to JHash.
Improvements to CRC32.
Fix memory leak in CPUfreq stats module.
Removed PMEM. I do see any improvement regarding the available RAM, but removing unused code is never a bad idea.
GLaDOS-V1.2
Fixed 'Screen v1 gamma hack' not working for Voodoo Color.
GLaDOS-V1.1
Fixed BLN problems for i9023.
GLaDOS-V1.0
Initial release.
Oh this is going to be good.
...Thanks E
Sent from my Nexus S 4G using xda premium
oh man... downloading now
thank you so much for providing this!
Stock android uses deadline scheduler or VR?
A bit off topic, but did anyone ever toy with SIO, NOOP and CFQ on Nexus S?
Wow
Testing right know
can i flash this on my rooted stock 2.3.6? that is the latest for my country.
Ezekeel's own kernel?
Ezekeel's own kernel?!
I knew you have only provided kernel devs with MODs.
Very tempting... Will leave it a few releases before I jump from Matr1x but expecting this to be very good!
I'd be interested in seeing what people's battery life is like on this kernel compared to others, as that's the main selling point for me!
just ran a quadrant benchmark, ~1000 point increase from franco's 06 kernel on carbon c02 rom with 110 liveoc
i'm try ...
v3rk said:
just ran a quadrant benchmark, ~1000 point increase from franco's 06 kernel on carbon c02 rom with 110 liveoc
Click to expand...
Click to collapse
so its better than franco's? and does it include the latest deep idle fiX?
Finally a kernel of a master hehe
Sent from my Nexus S using xda premium
Oh em gee. Here we go!
Sent from my -=Nexus MV=- powered Nexus S c",)
--
MarkVis
After flashing no more lights in soft keys
Edit:
Solved
thegtfusion said:
so its better than franco's? and does it include the latest deep idle fiX?
Click to expand...
Click to collapse
lol
read up who made deepidle-fix. and all those other kernel-tweaks. this kernel comes from the horse's mouth so to speak, or how this is said in English.
now let's see if it's stable.
Yusei said:
After flashing no more lights in soft keys
Click to expand...
Click to collapse
Use bln app to see if it's enable.
MarkVis said:
Oh em gee. Here we go!
Sent from my -=Nexus MV=- powered Nexus S c",)
--
MarkVis
Click to expand...
Click to collapse
If i am in you, I'd have chose which kernel to include in next nexus mv release
Inviato dal mio Nexus S
report: Oh yeah this is awesome syrup, my phone loves it.
Edit : everything good on this side.
Sent from my Kush'd Google Nexus S 4G using xda premium
Ezekeel, can you put this kernel taking around 65fps in 3D graphics globe?
Btw, this rocks.
This kernel is based on teamhacksung's kernel, with updated Linux base to 3.0.38
This kernel is working with every ICS based Rom
Features:
- 378, 391 and 403 Mb Ram available (selectable in kernel, no need for a patch (403 mb breaks 720p) only reboot required)
- 2 different recoveries included (cmw touch recovery + twrp recovery (to use TWRP, just create a file named "twrp" at /cache))
- SIO scheduler (default)
- V(R) scheduler (maybe even faster than SIO, can be set as default by using NSTools for example)
- init.d
- Voodoo Sound and CM9 Color Adjusment / Voodoo Color (VC version)
- Devil Idle
- BLN V9 (thx to mialwe)
- USB Host mode driver (for more information about this, and for saying thanks to the guy, who ported this for our phone, please visit this thread: http://forum.xda-developers.com/showthread.php?t=1450298 )
-Ezekeel's Live_Oc
- Ezekeel's Deep Idle V2
- Touchwake
- vibrator intensity control (by mialwe)
- BLX (Batterie Life Extender, I don't think we need it, but maybe one feels better by using it )
- backports from Linux 3.2 and 3.3
- Swap/Zram support
- Zcache, Cleancache and Frontswap
- Uksm
- Fiops io scheduler
- Smooth_ui included to ondemand, conservative, smartass, lulzactive, lagfree and lazy governor (only one setting for activating/deactivating it in general)
- 3 cpu governor presets (smooth, normal, powersave) for ondemand, conservative, smartass, lulzactive, lagfree (only one setting for switching the mode in general)
- many other small features and improvements
Donwload and Changelog post 2
FAQ and known issues in post 3
Click to expand...
Click to collapse
Many of the features (like Live_OC) require NSTools, which can be found at market for free.
NEW:
Devil kernel Config: http://forum.xda-developers.com/showthread.php?t=1715383
Devil Kernel Manager: http://forum.xda-developers.com/showthread.php?t=1723222
Both Apps are really great. Please try on your own, which one you like more.
you still can use the previous methods of setting up the kernel:
Please also try this app http://forum.xda-developers.com/showthread.php?p=22430406, for setting many of the options which are only available with my kernel.
a pre configured file for use with command center can be found here: http://forum.xda-developers.com/showpost.php?p=27353078&postcount=240 (you have to remove .zip extension)
a good explination/example of how to use it, can be found here: http://forum.xda-developers.com/showpost.php?p=26301176&postcount=4842
if you don't like additional apps (or are having problems with command center), i recommend using this init.d script: http://forum.xda-developers.com/showpost.php?p=26683004&postcount=5346
Click to expand...
Click to collapse
Kernels with VC in the name are coming with Voodoo Color
oliva94 said:
IF the kernel zip name contains _JB_, THEN and only then you can use it IF you do NOT have datadata partition
ELSE if you HAVE datadata, then use one WITHOUT _JB_ in the name
if you use it otherwise, it will boot but system is eventually going to crash/not load due to partition table (thus blockdevice naming) mismach
Click to expand...
Click to collapse
Many Thanks to:
Teamhacksung
Zacharias.maladroit
Onecosmic
ytt3r
TK Glitch
Ezekeel
Eugene373
franciscofranco
Sunra
scheichuwe
perka
sztupy, for his great work, to get usb host mode driver
mialwe
stratosk
F4k for the idea to flash bigmem libs
...
sources:
https://github.com/DerTeufel
Click to expand...
Click to collapse
This kernel is also available for:
Captivate, Fascinate and Vibrant
Click to expand...
Click to collapse
Working on this kernel is taking many hours almost every day. With a small donation, you show me, that my work is appreciated by you.
If you like this kernel, please donate to me
Changelog:
changelog 02.08.2012:
- bug fix to bln, to prevent kernel panic in some situations (thx to thalamus)
- switched from deep_idle 2 to idle2 (also thx to thalamus)
- updated kernel to linux 3.0.38
- dockaudio sysfs for captivate and fascinate
- automated symlinking from data to system: if one wants to free up some space at /system, without removing an app completely, just copy it from /system/app to /data/sys-parts/app (create the folder if not there), and reboot. during reboot, the app from system gets deleted, and the app from /data/sys-parts/app gets symlinked to system. this is working for almost every app, but i don't recommend doing this with apps, needed for android to work (framework, media provider, settings,...)
IDLE2 can be enabled with the following command:
echo 0 > /sys/module/cpuidle/parameters/idle2_disabled
IDLE2 can be disabled with the following command:
echo 1 > /sys/module/cpuidle/parameters/idle2_disabled
Stats can be obtained from the standard cpuidle interface, which, for
IDLE2 is located at:
/sys/devices/system/cpu/cpu0/cpuidle/state*/time
where * = 1, 2, 3
changelog 25.07.2012:
- updated recovery (no "sdcard format"-bug anymore, external sd card is named correctly)
- vibrant: hopefully fixed froyo ril
- jellybean: galaxy s settings working now
changelog 22.07.2012:
This kernel is for use with ICS only, if you are looking for a kernel, running on teamhacksung cm10 build, visit my jellybean kernel thread[/url]
- updated kernal base to linux 3.0.36
- updated "block" to linux 3.3
- readded fiops io scheduler (kept cfq this time)
- updated cwm recovery to 6.0.1.0 (please create a new nandroid, because of possible incompatibilities between old/new recovery)
- compiled with linaro toolchain (gcc 4.7.1) and O3 compiler flags
- made uksm scan less often (save cpu time and power)
- at first boot: only delte init.d scripts created by other kernels
- increased usb write performance
- lowered ram and display voltages a little bit
- fixed some bugs related to devil settings (they should stick now after reboot, if set by one of the devil apps)
- support for scripts in /system/etc/shutdown.d (thx to Efpophis)
all scripts placed at /data/local/shutdown.d or /system/etc/shutdown.d get executed at shutdown/reboot
you can use this, to play a shutdown sound for example.
by default 00shutdown gets created, which plays a music file, when it is placed at one of these folders/places
/system/media/audio/ui/shutdown.ogg
/data/media/audio/ui/shutdown.ogg
Click to expand...
Click to collapse
- disabled some debugging options
- audio (and for fascinate: camera fixes) by Efpophis+
- patch for improving batterie life by CML
- nfts read/write driver built in (for use with usb host mode)
- reverted refreshrate_mod and gpu_oc mod, as both weren't working
changelog 18.06.2012:
- some changes to load balancing
- added ultra ksm (metioned by zach thx for this my friend)
- readded fiops io scheduler (still experimental and could cause instablilities)
- using snappy compression for zram now (2 times faster, but only 2% less compression)
- added the possibility to change zram size (at /data/local/devil/zram_size, with valid values: 50, 75, 100 and 150 (all in mb))
- fixed the applying of user_min/max freq after reboot
- vibrant: fixed gps
- fascinate: fixed nandroid in cwm recovery
what is ksm? http://en.wikipedia.org/wiki/Kernel_SamePage_Merging_(KSM)
uksm is more optimized and also working for single core systems. using this should give much better ram usage, but at the cost of more cpu usage
############# most probably not working (yet)##############
i have added seperate gpu oc from jt1134's galaxy_tab (to switch between 200 and 250 mhz), but i did not get any improvements in antutu...further tests needed
echo 1 > /sys/kernel/pvr_oc/pvr_oc (for 250 mhz)
echo 0 > /sys/kernel/pvr_oc/pvr_oc (for 200 mhz), no reboot needed
and also have changend default screen refreshrate from 60 to 56, with the possibility to change it:
echo 1 > /sys/kernel/refreshrate/enable (60 hz)
echo 0 > /sys/kernel/refreshrate/enable (56 hz)
######################################################
changelog 10.06.2012:
cwm recovery:
- fixed mounting of external sd card to pc
kernel:
- picked two commits from linux 3.0.32 (avoid a possible memory leak, small fix to ext4 driver)
fascinate:
- fixed wrong mount points
changelog 09.06.2012:
- updated Zram and Zcache from linux 3.3
- updated android binder driver from linux 3.3
- fixed restoring of backups within TWRP recovery
- added virtual buttons to cwm recovery (Attention: they still don't work!)
- call vol hack from tk glitch (take a look at init.d folder and edit the script to make changes to call vol hack)
- bigmem values get applied at first boot after power on (if there is a value at /data/local/devil/bigmem, 1 for 391 mb and 2 for 403 mb (the last one breaks 720p)
- prevent phantom key presses (from tk glitch)
changelog 24.05.2012:
- Smooth_ui included to ondemand, conservative, smartass, lulzactive, lagfree and lazy governor (only one setting for activating/deactivating it in general)
- 3 cpu governor presets (smooth, normal, powersave) for ondemand, conservative, smartass, lulzactive, lagfree (only one setting for switching the mode in general)
- no need for activating/deactivating of selective live_oc anymore --> just change target low and target high
- BLX back in
- fixes to devil idle to be more stable while in call
- 1,5 mb more ram (thanks to mialwe)
- added aroma filemanager to cwm recovery
- added fully working TWRP recovery optional to cwm recovery (to use TWRP, just create a file named "twrp" at /cache)
- added option to select ram config in kernel --> no need for flashing an other kernel to get more ram (thanks to stratosk)
- switched to new initramfs from stratosk and mialwe ( now there will be cmw zip and odin tar file of every kernel version)
- added possibility to use Zram instead of Swap
- no need for flashing/using special scripts to make swap/zram working anymore
- added zcache
- added frontpage
- added cleancache
- added fudgeswap (thanks to ezterry and faux123)
changelog 01.05.2012:
- all changes from cm9 stock kernel (including mount points option)
- some fine tuning to deadline and sio
- Devil Idle: limiting bus/ram/gpu speed to 100 mhz for 100-800 mhz cpu freq, while screen off (automatic mode) or always (permanet), both modes automatically reduce the int voltages of the affected freq by 50 mV
- compiled with swap support
- added stratosk's smooth_ui to lulzactive governor (activated by default)
- rest oc_value to 100 while screen off, and back when screen turns on (combined with devil idle automatic, can't be turn on/off without devil idle)
- added posibility for different voltages while screen off (also bundled with devil_idle, with default settings, stock arm voltages are applied, because of live_oc set to 100)
- added the possibility to set freq limits while screen off (min and max freq)
19.04.2012
- even better fix to selective live_oc (last one (in test kernel) generated some overhead)
- fixed sampling rate of ondemand and conservative (have ported mialwe's/stratosk's sleep multipliers)
- new tunables for ondemand and conservativ
sleep multiplier and tunables:
mialwe and stratosk had the great idea, to change the sampling rate of conservative and ondemand governor while display of. for this, he introduced the sleepmultiplier (in his case factor 3). this means, if you set sampling rate to 20000, it changes to 60000 while screen off, and back, when screen on.
for ondemand and conservative:
i have made this multipliers tunable. proper values are between 1 and 5, because one could want a higher multiplier while screen off, if sampling rate is very low while screen on (higher sampling rate means, less checking for work load --> better batterie, worse performance). with this tunables you get better batterie, without making the performance worse while screen on.
two other tunables: up_threshold_min_freq and responsiveness_freq
the first one is a very low threshold while on low freq (by default 40), to make the governor scale up faster, until the responsiveness_freq is reached.
the responsiveness_freq is set to 400000 (400 mhz) by default. while the freq is below this value, up_threshold is the same as up_threshold_min_freq, and freq jumps to responsiveness_freq, with skipping the freq between the actual one and the responsiveness_freq. (conservative governor does not jump up to this step)
responsiveness_freq can be set to values between 100000 and 1400000
up_threshold_min_freq can be set to the same values as the normal up_threshold.
not tunable: while screen off, up_threshold is set to 95, no matter your other settings, to save more batterie.
up_threshold_min_freq is disbaled by default for conservative governor
for lulzactive:
for this governor, i did similar things, but they are not tunable till now.
when screen off:
- inc_cpu_load is set to 90, and back to the original value, when screen turns on
- up_sample_time is set to 50000, and back to the original value, when screen turns on
- down_sample_time is set to 40000, and back to the original value, when screen turns on
other changes:
- fix to touchwake from ezekeel, and another fix from stratosk
- upstream fix to compass
- building for i9000B now, too (big thanks to F4k for the hints by pn )
- removed some typos from recovery
- removed some annoying "no's" and "yes" from recovery in misc menu
- fixed wifi mode switch (pm_fast is the one with better signal)
14.04.2012:
- new b versions (only stock ram) changend to 377 mb, VC version needs the 720p fix from my ftp server. cmc version already patched
13.04.2012:
- updated wifi driver
- added the possibility to switch between wifi PM_Fast and PM_Max mode (Pm_Fast = better signal, PM_Max = better batterie, default is PM_Max)
- user interface to disable fsync (this gives more performace, at the risk of data loss on a crash, taken from ezekeel, so it should be ok ), default is off, to be safe
- fixed voodoo color kernels (these have the VC in their names)
10.04.2012:
- added vibrator intensity control (by mialwe), presets can be changend in recovery
- stock ram version now available (348 mb ram), XL (390 mb), XL_bm (402 mb)
- removed 1080 mhz freq for now
- small correction to touchwake
- small correction to selective live_oc (now the low freq really are not live_oc'ed)
05.04.2012:
- fixed bug in selective live_oc, which caused the target high not taking affect to the highest freq, if highest freq equals target high
- fixed another bug in selective live_oc, which could lead to gpu crashes due to overclocking the ram, but not the cpu freq (for low steps)
- added a switch to change between "normal" and selective live_oc
by changing the live_oc mode while using it, live_oc value is set back to 100, to prevent strange things
- added possibility to set max. freq for boot (in recovery). This freq is set until init.d is executeted (it is automatically set to 1000 at this point, to make sure there are no conflicts with other cpu settings from users)
#Already in the last version, but i forgot about it:
- deep idle fixes from stratosk (many thanks)
- added possibility to underclock by using live_oc (limit is 90 now, which means lowering all freq and bus speed by 10%, to save more batterie when really needed)
03.04.2012:
For now there are three different RAM versions:
- stock mem kernel has 379 mb ram, everything working
- "slim ics" (XL) kernel comes with 390 mb, this is breaking playback of some high resolution videos
- XL_BM is coming with 402 mb ram, but breaking 720p
(while flashing the kernel, the modded rom files are also flashed, so you don't need to flash a new rom to get 379 or 390 mb)
-added new frequency: 1080 mhz (1100 does not like live_oc)
- fixed SmartassV2 for live_oc (after changing live_oc value, you have to change the smartass values, too, but then they automatically apply to the live_oc value (although you can only select 800 mhz in nstools (for example))
- touch recovery with custom devil menu (for some reason it takes a few seconds to load the first time, missing virtual keys is a warning, because there are no virtual keys yet)
-fast charge (thx to chad0989 for this), disabled by default.
you also can use the widget from chad (to place on homescreen) to toggle the fast_charge mode
https://play.google.com/store/apps/d...stchargewidget
Click to expand...
Click to collapse
while fast charge is activated you cannot connect as usb device
- added datafix script to init.d (this script is deactivated by deafult. to make it work, you have to creat a file named datafix and placed in /data/local/)
- reworking and cleaning many parts to get more ram, speed, and stability
05.03.2012:
- updated sio i/o scheduler to latest version
- small updates to ondemand and conservative governor from linux 3.2
- bettter performance for CFS kernel due to tuning and patches
- tuning to deadline scheduler
- better i/o performance
- changed bootlogo (probably not the last time )
28.02.2012
- finally working bln V9 (no need for LED2 anymore)
- fixed lockscreen freezes
- reverted memory tweaks, which could be the reason for lagging after using a day
- again wlan fixes from tk-glitch
- tweaked conservative and ondemand governor (conservative still is not too aggressive)
- added dm-cache again (who has removed this from my github? )
- improve usb signal quality
- xcaliburinhand's dock audio support (untested, do not have a dock)
- less debugging
- fixed kernel version not displayed under "about phone"
12.02.2012
- Added newest Fiops scheduler (tuned for more performance)
- When Gpu is active, min CPU freq is set to second lowest step
- fixes to live_oc and custom voltage
- default mount parameter NOATIME and NODIRATIME (faster)
- updated Wifi drivers (thanks to tk-glitch)
- tuned intellidemand for better performance
- removed some stuff (zram, swap, tweaks to cpufreq untill I know what was causing the instabilities of last build)
05.02.2012
- added Touchwake
- added BLX
- upgraded BLN from V8 to V9 (working for missed calls, blinking or static light, configurabel by using NSTools or BLN Pro App)
- added Intellidemand governor
- added mdnie settings to voodoo color version
- readded deep idle v2 again (I think it is the best/only working one, although
- version with CFS (instead of BFS) now also available (maybe better multitasking and batterie life, but slower)
- removed BFQ I/O Scheduler
- tons of smaller fixes and improvements
30.01.2012
-revert: Voodoo Sound now to be set with DSP Manager
29.01.2012
- Linux kernel 3.1.10
- Deep Idle from Eugene373 (always enabled, no stats)
- added BFQ v 3.1 I/O Scheduler
- Voodoo Sound now to be set with DSP Manager
- Zram (can be disabled by removing Zram file from init.d)
- Zcache and Cleancache (not working yet?)
- optimized rwsem algorithm
- USB Host V5
24.01.2012
- init.d support (the folder is not created by the kernel. You have to do it for yourself)
- Deep Idle V2 back in
- new Cpu governors: MinMax, Lagfree, Lulzactiv
- LED V2 (you can set blinking by using nstools, also working for missed calls in most cases (sometimes it is not working for missed calls, don't know why at the moment))
- Backlight Dimmer (only LED version): used to turn led backlight of, while screen is on, after defined period of time. Deactivating it, makes your backlight stay on all the time
- I/O-less dirty throttling completely backported from kernel 3.2
- Ext4 with 3.2 patches
- Proportional Rate Reduction for TCP - by Google
- USB Host V 4
19.01.2012
- Usb Host drivers integrated
- Cm9 Color adjustment
- Removed Deep Idle because of Bluetooth problems (hopefully it will come back, still testing)
16.01.2012:
- Updated Kernel basis to Linux 3.1.9
15.01.2012:
- fixed bug in cpu spy, caused by live_oc
- still using voodoo color for now, maybe two additional kernel versions tomorrow
Click to expand...
Click to collapse
files with .zip have to be flashed within recovery (twrp or cwm)
files with .tar can be flashed by using odin or heimdall (they are placed at the end of post 3)
ICS:
http://rootaxbox.no-ip.org/divers/ICS/ many thanks to Rootax
JellyBean (with default cm10 partition layout for use with teamhacksung's rom):
http://rootaxbox.no-ip.org/divers/jellybean/
http://devil.haxer.org/ many thanks to SysTem-X (not updatet yet)
Known issues:
- virtual buttons in cwm recovery not working
vibrant specific:
nothing
Click to expand...
Click to collapse
How to:
you can change ram setting by doing the following ( to make these settings even stick after power off, you also have to echo the same value to to /data/local/devil/bigmem):
echo 1 > /sys/kernel/bigmem/enable (this gives you xl mem of 391 mb)
echo 2 > /sys/kernel/bigmem/enable (this gives you bm mem of 403 mb (this is breaking 720p))
echo 0 > /sys/kernel/bigmem/enable (this gives you cm9 default mem of 378 mb)
you have to reboot to make changes work
Click to expand...
Click to collapse
With setting this, your desired swap mode gets automatically applied at boot time. For swap, you have to create a swap partition at your external sd card before
echo 1 > /data/local/swap_use (for using swap partition on external sd card, you have to create this partition before)
echo 2 > /data/local/swap_use (for using Zram, no other modifications required)
you have to reboot to make changes active. You can't use swap and Zram at the same time
Click to expand...
Click to collapse
These are the settings for devil idle:
activate automatic:
echo 1 > /sys/devices/virtual/misc/devil_idle/bus_limit
permanent on:
echo 2 > /sys/devices/virtual/misc/devil_idle/bus_limit
deactivate
echo 0 > /sys/devices/virtual/misc/devil_idle/bus_limit_automatic
Click to expand...
Click to collapse
to set different voltages while screen off (this only is working, if devil idle automatic mode is activated)
this is an example, how to apply screen_off arm voltages:
echo 1450 1400 1350 1275 1075 975 875 800 > /sys/class/misc/customvoltage/arm_volt_screenoff
this way, it is possible to undervolt while screen off, but overvolt and overclock while screen on
for now, the int voltages can not be changend
Click to expand...
Click to collapse
set freq limits while screen off (min and max freq)
enable the limits:
echo 1 > /sys/devices/virtual/misc/devil_idle/user_min_max_enable
disable:
echo 0 > /sys/devices/virtual/misc/devil_idle/user_min_max_enable
set values to be applied if activated:
echo 100000 > /sys/devices/virtual/misc/devil_idle/user_min
echo 800000 > /sys/devices/virtual/misc/devil_idle/user_max
both are independent from devil_idle, and get applied when screen turns off
by default 100 and 1000 mhz are set.
values which can be put here are all "stock" freq (without live_oc level) multiplied with 1000. live_oc values get applied automatically.
Click to expand...
Click to collapse
to set responsiveness_freq, up_threshold_min_freq or sleep_multiplier for ondemand and/or conservative governor, you have to do it like this:
echo VALUE > /sys/devices/system/cpu/cpufreq/ondemand/VARIABLE_NAME
and
echo VALUE > /sys/devices/system/cpu/cpufreq/conservative/VARIABLE_NAME
example:
echo 400000 > /sys/devices/system/cpu/cpufreq/ondemand/responsiveness_freq
echo 50 > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold_min_freq
echo 5 > /sys/devices/system/cpu/cpufreq/ondemand/sleep_multiplier
up_threshold_min_freq is disbaled by default for conservative governor
(to disable it for ondemand you have to set up_threshold_min_freq to 100.
Click to expand...
Click to collapse
switch between wifi PM_Fast and PM_Max mode (Pm_Fast = better signal, PM_Max = better batterie, default is PM_Max)
echo 1 > sys/module/bcmdhd/parameters/uiFastWifi (pm_fast)
echo 0 > sys/module/bcmdhd/parameters/uiFastWifi (pm_max)
Click to expand...
Click to collapse
user interface to disable fsync (this gives more performace, at the risk of data loss on a crash, taken from ezekeel), default is on, to be safe
echo 1 > /sys/devices/virtual/misc/fsynccontrol/fsync_enabled (fsync enabled)
echo 0 > /sys/devices/virtual/misc/fsynccontrol/fsync_enabled (fsync disabled)
Click to expand...
Click to collapse
to set the values for vibrator intensity:
echo value > /sys/class/timed_output/vibrator/duty (where value is between 20000 and 43640)
if you want the changes to be applied at boot, you have to use one of the presets from recovery, use an init.d script, or:
echo value > /etc/devil/vibrator (where value is between 20000 and 43640)
Click to expand...
Click to collapse
activate fast charge: echo 1 > /sys/kernel/fast_charge/force_fast_charge
Click to expand...
Click to collapse
deactivate fast charge
echo 0 > /sys/kernel/fast_charge/force_fast_charge
you also can use the widget from chad (to place on homescreen) to toggle the fast_charge mode
https://play.google.com/store/apps/d...stchargewidget
Click to expand...
Click to collapse
while fast charge is activated you cannot connect as usb device
Click to expand...
Click to collapse
Questions and Answers:
Q: What the hell are all these governors?
A: here you should find the answer: http://forum.xda-developers.com/showthread.php?p=19846297
Q: What's a good setup for live_oc??
A: No one knows. Every phone is different. It seems like the folling setup is running well for some (many?) users. If you get reboots with it, you have to find the setup for yourself.
if you are satisfied with this configuration, please hit the thanks button of Crack: http://forum.xda-developers.com/showpost.php?p=22194160&postcount=1246
.:Crack:. said:
OK, these are mine. Rock stable
LiveOC 117% -> 1200 MHz -> 1404 MHz
Freq/ARM/Init
1200/1400/1150
1000/1325/1125
800/1250/1125
400/1025/1100
200/900/1100
100/875/1000
low freqs could possibly be tweaked harder but stability was my fist goal
Click to expand...
Click to collapse
Q: How can I set up swap?
A: Take a look at this thread: http://forum.xda-developers.com/showthread.php?t=1610835, and especially at this post:
http://forum.xda-developers.com/showpost.php?p=25578231&postcount=83
Q: What is Touchwake? Can you explain it?
A: With Touchwake, the touchscreen still recognices your fingers, after turning off (for a predefined time (NSTools)). For a detailed explenation, take a look at Ezekeel's thread: http://forum.xda-developers.com/showthread.php?t=1239240
Q: How can I make Voodo Color settings been saved after reboot?
A: You have to use Voodoo Pro App, because of changes between Gingerbread and ICS, and only the Pro app is updated till now.
Q: Which is the best IO Scheduler?
A: I think SIO and V(R) are the fastest.
Q: How can I enable DeepIdle/Live_Oc?
A: You have to use NSTools. You find it on market. It's free.
Deep Idle Questions:
Q: How can I activate the deep idle stats?
echo 1 > /sys/class/misc/deepidle/stats_enabled
Q: What's the meaning of TOP=Off and TOP=On when I look at the Deep Idle status?
A: When TOP=Off is used, the best powersaving state is used. TOP=ON will be shown, when bluetooth or gps are running.
Q: In Idle status I only see TOP=On. What's wrong here? I don't use Bluetooth or Gps.
A: You have to flash the modded framework-res.apk, because ICS does not fully deactivate bluetooth by default. Even if you never use it.
Q: Idle Stats only are showing Idle, but no Deep Idle. Why?
A: An App is preventing the use of Deep Idle. At first, you should try closing the cam, running in the background. Also rebooting should solve this problem.
Q: What is fudgeswap?
A:
Setting this to a very large positive number will indicate swap ought
to be fully used as free (and will slow the system down)
smaller numbers will allow you to put some pressure on SWAP without
slowing the system down as much.
small negitive numbers will allow the system to be faster at the same
minfree level.
default is 512 to give a very little bit of pressure to use some swap
but this can be modified at runtime via:
/sys/module/lowmemorykiller/parameters/fudgeswap
I'm going to be the next American Ninja Warrior!
Sent from my SGH-T959 using xda premium
Thanks...
Sent from my SGH-T959 using Tapatalk 2
Awesome!
Hellz yeah! Finally we get the official Devil kernel for Vibrant! Subzero has been nearly flawless for me except for some wifi drops here and there on certain router. I will test this out and see if it is any better and if the GPS will initialize after deep sleep as consistent as Subzero. DerTeufel1980 will you please post the Voodoo Color version for Vibrant? I noticed that there was no call volume init.d script like Glitch. Will this feature work without a script?
I just tested the 0.66 CM color kernel in the GPS doesn't initialize properly with no satellites in view. The GPS icon comes on though. MP's subzero kernel which is based off of Devil has the proper working GPS ramdisk for Vibrant if that will help you.
No issues, loving this. I haven't had a GPS issue probably because I flashed the GPS fix.
Sent from my SGH-T959
Flashed this with aokp build 38 and running great. Don't use gps so not sure if it works, but everything else is going perfect. Thanks for the kernel.
hurtz777 said:
Hellz yeah! Finally we get the official Devil kernel for Vibrant! Subzero has been nearly flawless for me except for some wifi drops here and there on certain router. I will test this out and see if it is any better and if the GPS will initialize after deep sleep as consistent as Subzero. DerTeufel1980 will you please post the Voodoo Color version for Vibrant? I noticed that there was no call volume init.d script like Glitch. Will this feature work without a script?
I just tested the 0.66 CM color kernel in the GPS doesn't initialize properly with no satellites in view. The GPS icon comes on though. MP's subzero kernel which is based off of Devil has the proper working GPS ramdisk for Vibrant if that will help you.
Click to expand...
Click to collapse
I'll check the ramdisk.
Voodoo color is going to come soon.
Gesendet von meinem GT-I9000 mit Tapatalk 2
DerTeufel1980 said:
I'll check the ramdisk.
Voodoo color is going to come soon.
Gesendet von meinem GT-I9000 mit Tapatalk 2
Click to expand...
Click to collapse
SubZero ramdisk with working GPS after deepsleep.
https://github.com/mr-psycho/initramfs/commit/90e603f541b7306b3afdff283d9b7d7e22bdb7ca
Looking forward for next update.
mohamobo said:
SubZero ramdisk with working GPS after deepsleep.
https://github.com/mr-psycho/initramfs/commit/90e603f541b7306b3afdff283d9b7d7e22bdb7ca
Looking forward for next update.
Click to expand...
Click to collapse
Is gps working with cm9 stock kernel? This would make it easier to identify gps tweaks from others.
Gesendet von meinem GT-I9000 mit Tapatalk 2
You have been thanked DerTeufel1980
You have been thanked DerTeufel1980 & this puppy has made it to the Kernel Bible.
Congratulations and great work, looking forward to more of your valued work.
Nice Documentation with this release!!!
serendipityguy said:
You have been thanked DerTeufel1980 & this puppy has made it to the Kernel Bible.
Congratulations and great work, looking forward to more of your valued work.
Nice Documentation with this release!!!
Click to expand...
Click to collapse
Yeah, finally I got it. And sorry mate, for the trouble last time.
Gesendet von meinem GT-I9000 mit Tapatalk 2
DerTeufel1980 said:
Yeah, finally I got it. And sorry mate, for the trouble last time.
Gesendet von meinem GT-I9000 mit Tapatalk 2
Click to expand...
Click to collapse
Will this puppy work with CM9, you have stated that it is a ICS kernel
DerTeufel1980 said:
Is gps working with cm9 stock kernel? This would make it easier to identify gps tweaks from others.
Gesendet von meinem GT-I9000 mit Tapatalk 2
Click to expand...
Click to collapse
Before someone else jumps in let me say this myself that it doesn't work.
GPS is dying after DS on stock CM9, and I need to figure out why it works on SZ.
I informed people to try your kernel because I wanted to find out if it was a Devil or SZ commit that made it work.
serendipityguy said:
Will this puppy work with CM9, you have stated that it is a ICS kernel
Click to expand...
Click to collapse
Yep. It is based on their kernel.
FaultException said:
Before someone else jumps in let me say this myself that it doesn't work.
GPS is dying after DS on stock CM9, and I need to figure out why it works on SZ.
I informed people to try your kernel because I wanted to find out if it was a Devil or SZ commit that made it work.
Click to expand...
Click to collapse
Thanks. Then it has to be subzero who fixed it. I just took the I9000 initramfs.
Gesendet von meinem GT-I9000 mit Tapatalk 2
DerTeufel1980 said:
Is gps working with cm9 stock kernel? This would make it easier to identify gps tweaks from others.
Gesendet von meinem GT-I9000 mit Tapatalk 2
Click to expand...
Click to collapse
FaultException said:
Before someone else jumps in let me say this myself that it doesn't work.
GPS is dying after DS on stock CM9, and I need to figure out why it works on SZ.
I informed people to try your kernel because I wanted to find out if it was a Devil or SZ commit that made it work.
Click to expand...
Click to collapse
Same answer with FP but devil kernel are completely dead!
mohamobo said:
Same answer with FP but devil kernel are completely dead!
Click to expand...
Click to collapse
First, great work as usual on the Devil kernel DerTeufel!
As for GPS, I can confirm GPS breakage, too. Currently, I'm on AOKP Build 38, and with Devil 3_0.66, I get no birds at all, even after several minutes of letting it sit. Seems like GPS doesn't see the sats or just isn't communicating with them. Tried clearing/updating AGPS data, and still nothing.
As a test, I re-flashed my subZero kernel, and saw 12 birds in under 10 seconds with GPS lock in under 30 seconds. And that's in the middle of the Pacific Ocean with clouds and drizzling rain.
So, DerTeufel pointed out he's using his i9000 initramfs, which probably doesn't have the Vibrant GPS tweaks. I started with DerTeufel's Vibrant branch of the i9000 initramfs, making tweaks from Glitch and THS. So, it's no special secret.
With my latest, forth-coming kernel, I've gone with the CM9 (and AOKP) design of GPS modularity (init.aries.gps.rc). Testing confirms GPS still works even after deep sleep.
One difference between subZero and nearly all the other ICS kernels out there, is that I don't use DeepIdle. I don't compile it in. I'm not sure if DeepIdle is what could be breaking GPS after deep sleep on the Vibrant.
I'll probably have the latest initframfs changes up on Github soon. In case anyone is interested in looking at it more closely.
MP
mr_psycho said:
First, great work as usual on the Devil kernel DerTeufel!
As for GPS, I can confirm GPS breakage, too. Currently, I'm on AOKP Build 38, and with Devil 3_0.66, I get no birds at all, even after several minutes of letting it sit. Seems like GPS doesn't see the sats or just isn't communicating with them. Tried clearing/updating AGPS data, and still nothing.
As a test, I re-flashed my subZero kernel, and saw 12 birds in under 10 seconds with GPS lock in under 30 seconds. And that's in the middle of the Pacific Ocean with clouds and drizzling rain.
So, DerTeufel pointed out he's using his i9000 initramfs, which probably doesn't have the Vibrant GPS tweaks. I started with DerTeufel's Vibrant branch of the i9000 initramfs, making tweaks from Glitch and THS. So, it's no special secret.
With my latest, forth-coming kernel, I've gone with the CM9 (and AOKP) design of GPS modularity (init.aries.gps.rc). Testing confirms GPS still works even after deep sleep.
One difference between subZero and nearly all the other ICS kernels out there, is that I don't use DeepIdle. I don't compile it in. I'm not sure if DeepIdle is what could be breaking GPS after deep sleep on the Vibrant.
I'll probably have the latest initframfs changes up on Github soon. In case anyone is interested in looking at it more closely.
MP
Click to expand...
Click to collapse
Hi, long time no see.
Thank you very much. I'll try your initramfs when I come home in 7 hours.
Do you still use the cwm touch from "me"? If so, I have solved the issue with the devil menu. It was the mounting of /datadata
Gesendet von meinem GT-I9000 mit Tapatalk 2