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.
THE LATEST NIGHTLIES HAVE BEEN REMOVING VOLTAGE CONTROL STATS, SO PLEASE REMOVE ALL OVERCLOCKING BEFORE FLASHING A NIGHTLY OR AN UPDATE FROM HERE.
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. To undervolt, use either Voltage Control, SetCPU, or Control Freak.
4. Want to go back to stock? First, if there's any particular reason, please let me know. I love to have feedback, good or bad. Then, just flash the latest official update.
5. Sources --> https://github.com/TheEscapistxda/android_kernel_samsung_aries
6. BLN is disabled by default. Please enable it by using the BLN control app from the market.
7. Its not an error. Don't freak out. Let it boot.
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]
-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[May6]
-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 (Something for you to shoot for, Shaolin. )
-set default governor to conservative
- New captivate/vibrant specific initramfs
v5.2[May 12]
-Upsteam changes to modem_ctl
-Upstream tvout drivers (Totally untested on my end, so i dunno if they work)
-fsa usb switch suspend
-Overvolting cap
-add the kernel version (v5.2) to the kernel name.
v5.3[May 16]
-Upstream changes to initial flash/initramfs
-Upstream changes to battery calculation percentage
-Some other stuff, nothing really important. Its all upstream changes anyway.
NIGHTLIES/WHENEVERS:
#1[May 25]
+Working ril (data + service)
+working gps
+switched to mfloat=softfp as it gives slightly higher linpack scores
+Voodoo sound v9
+LZO compression for a faster boot up time.
Known bugs:
Rild crashes in areas with no service, causing a hard reboot. (Can anyone tell me if this happens on the stock kernel?)
#2[May 27]
+Actually working ril (no more reboots)
+Optimized for size
+Updated to 2.6.35.13 kernel (No, I dont have a changelog. There is one on the internet somewhere. Needless to say, its huge.)
+Probably some other stuff.
Known bugs:
Bln is finicky on this build, try reflashing/rebooting if it doesn't work at first.
#3 [May 29]
+States table in voltage control kinda works, but is buggy.
+disabled ext2
+re-added 1.6Ghz with a higher voltage (be careful guys).
+upped 1.55ghz by a few Mhz so it should be one or two above rather than below.
#4 [June 4]
+Disabled the states_enabled_table again, cause voltage control was really sketchy about keeping the states properly enabled. Hopefully the new rewrite will help.
+Fascinate support
#5[June 28] UNTESTED
+All upstream merges
+GPU bus clock speed modifiable using Control Freak
+Other stuff that I can't remember or have time for
#6[July 12]
+Upstream changes
+Fixed BLN (For whatever reason, it won't work after booting into recovery. Do a normal reboot, and it'll work).
+Reenabled the debugging, cause it was causing issues
This is nice!! Waiting for Voodoo fixes!
So can we flash back to original cm7 kernel after this using odin?
Sent from my SGH-I897 using XDA App
chipsa964 said:
So can we flash back to original cm7 kernel after this using odin?
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
I believe you need to use the cm7-update.zip file to install the original cm7 kernel - unless there is a .tar cm7 kernel?
born_fisherman said:
I believe you need to use the cm7-update.zip file to install the original cm7 kernel - unless there is a .tar cm7 kernel?
Click to expand...
Click to collapse
There is, but it doesn't fix everything g that is necessary. You need the update zip.
Sent from my CM7 powered captivate
It'd be great if you can integrate BLN into the kernel as well!! Running kang's voodoo color/sound right now, but who ever comes out with a BLN kernel will have my full attention(and of many other people I imagine judging by the posts on the CM forum)!!
boardsportsrule said:
It'd be great if you can integrate BLN into the kernel as well!! Running kang's voodoo color/sound right now, but who ever comes out with a BLN kernel will have my full attention(and of many other people I imagine judging by the posts on the CM forum)!!
Click to expand...
Click to collapse
yes please 1+ for BLN.
That being said with Voodoo fixes soon to be intergrated, and hopefully UVing Im watching this thread closely.
And when we do flash this would we have to do anything differently? Or just flash it over the current set up via CWM like any other ROM.
Thanks and great work so far.
Would these recent captivate cm7 voodoo kernel be helpful to integrating voodoo into your oc kernel?
http://kang.project-voodoo.org/
Voodoo sound is almost done, either tonight or tomorrow. Then, ill look at making this compatible with xan's UV app. Bln is probably going to be last, as it looks like the most work. There is currently no bln for any nexus s kernel, so ill have to see if it'll work.
Sent from my SGH-I897 using XDA App
Dlev7 said:
yes please 1+ for BLN.
That being said with Voodoo fixes soon to be intergrated, and hopefully UVing Im watching this thread closely.
And when we do flash this would we have to do anything differently? Or just flash it over the current set up via CWM like any other ROM.
Thanks and great work so far.
Click to expand...
Click to collapse
Yeah, just flash it over top.
Sent from my SGH-I897 using XDA App
This might seem like a pretty hefty request, but what are the chances that you can implement MKV splitting into the kernel? I wouldn't expect the kernel to be the route to getting MKV support on a device, but apparently developers for the Advent Vega Android Tablet have done exactly that. H.264 acceleration on a device that supports the stream should work no matter the container as long as something else in the chain parses the container first.
I'm not sure about licensing issues though, but it seems that a device that came with support for the MKV container (pretty much all Samsung devices, even their TV's and Bluray players) shouldn't be in violation of anything if it's running a custom ROM that contains the same functionality. Or maybe we'll have to wait for a Samsung Gingerbread source and create a Samsung-CM7 Frankenstein project?
Not being able to play my library of 720p MKV's with embedded softsubs without remuxing (and remuxing to mp4 still doesn't support embedded softsubs) on my Captivate is a dealbreaker keeping me away from CM7, but the other features and the possibility of syncing a Wiimote to control the new N64oid emulator is still very appealing
GGXtreme said:
This might seem like a pretty hefty request, but what are the chances that you can implement MKV splitting into the kernel? I wouldn't expect the kernel to be the route to getting MKV support on a device, but apparently developers for the Advent Vega Android Tablet have done exactly that. H.264 acceleration on a device that supports the stream should work no matter the container as long as something else in the chain parses the container first.
I'm not sure about licensing issues though, but it seems that a device that came with support for the MKV container (pretty much all Samsung devices, even their TV's and Bluray players) shouldn't be in violation of anything if it's running a custom ROM that contains the same functionality. Or maybe we'll have to wait for a Samsung Gingerbread source and create a Samsung-CM7 Frankenstein project?
Not being able to play my library of 720p MKV's with embedded softsubs without remuxing (and remuxing to mp4 still doesn't support embedded softsubs) on my Captivate is a dealbreaker keeping me away from CM7, but the other features and the possibility of syncing a Wiimote to control the new N64oid emulator is still very appealing
Click to expand...
Click to collapse
Well, I'll keep an eye out for anything that might factor into that, but between having other, more crucial features that need to go in first, and knowing next to nothing about video codecs, I can't promise anything. Sorry.
Also, I'm pretty sure I've got voodoo sound in there, but the cm build system is messed, so I haven't been able to build a working kernel or rom all day. Once builds are working again, do people want me to start posting "nightly" builds in here too?
Sent from my SGH-I897 using XDA App
merging voodoo sound and color is fairly simple. you just have to "git pull git://github.com/project-voodoo/linux_samsung.git nexus-s-voodoo" and compile. the pull command automatically changes the content of each file that's different between your local files and supercurio's branch files. i hope this makes it easier for you.
Sent from a phone, playing a phone, disguised as another phone.
slifer315 said:
merging voodoo sound and color is fairly simple. you just have to "git pull git://github.com/project-voodoo/linux_samsung.git nexus-s-voodoo" and compile. the pull command automatically changes the content of each file that's different between your local files and supercurio's branch files. i hope this makes it easier for you.
Sent from a phone, playing a phone, disguised as another phone.
Click to expand...
Click to collapse
Sadly, no. the cm kernel isn't a stock nexus kernel, theres a lot changed. Even if I could some how merge in just sound and color, there would probably still be issues.
I was actually planning on implementing voodoo color last, because theres still so much work bring done on it. I figured once I got everything else in there, it would be further along.
Also, this is partly a fun learning project for me, manually patching files is my kind of fun.
Sent from my SGH-I897 using XDA App
TheEscapist said:
Sadly, no. the cm kernel isn't a stock nexus kernel, theres a lot changed. Even if I could some how merge in just sound and color, there would probably still be issues.
I was actually planning on implementing voodoo color last, because theres still so much work bring done on it. I figured once I got everything else in there, it would be further along.
Also, this is partly a fun learning project for me, manually patching files is my kind of fun.
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
actually there aren't any issues. I've been using a kernel I built after the pull for several days now.
Sent from a phone, playing a phone, disguised as another phone.
TheEscapist said:
Well, I'll keep an eye out for anything that might factor into that, but between having other, more crucial features that need to go in first, and knowing next to nothing about video codecs, I can't promise anything. Sorry.
Also, I'm pretty sure I've got voodoo sound in there, but the cm build system is messed, so I haven't been able to build a working kernel or rom all day. Once builds are working again, do people want me to start posting "nightly" builds in here too?
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
Of course. MKV support is definitely not a primary feature of a kernel, but it sure would be nice. Also, I'm not talking about a codec, I'm talking more of a demuxer that simply streams the H.264 and audio streams as if they weren't inside the MKV so the hardware could play them like any MP4 (kind of like an Android equivalent of Haali Media Splitter).
I'm giving this a try...i really like the fact that I can choose how my cpu scales....hoping it helps battery life a little...also looking forward to you adding uv...
Sent from my Captivate using XDA App
Testing now. While I'm not particularly interested in the OC, the fact that you're using SetCPU and it's working makes me want to see if I can UC this. The default kernel doesn't play too well with this.
Related
Give your phone about 5-10 minutes to fully boot the first time.
Flash stock JF6 before flashing this to avoid any issues.
Backup, backup, backup!
Upcoming Changes:
- Backup entire sdcard to timestamped folder before flashing
Build 99 Changelog:
Rebased on JL5
Lock Screen Chooser
Gingerbread Clone
NO GPS (network location still works, good for general location)
Build 9.5 Changelog:
- no more overclocking issues because its gone!
- no more sdcard corruption
- no more charging death
- no more random reboots
- everything else is the same
Build 9 Changelog:
- Rebuilt on JL3
- JL3 Modem
- Single kernel, upto 1.6Ghz, stock at 1Ghz (patches based on laststufo/hardcore/xcaliburinhand kernel source)
- Stock memory allocation(302MB), an extra 30-40MB for the user is pretty useless
- Set CFQ as default IO scheduler
- BFQ disabled
- Updated Voodoo (db694a992bf11420bffc)
- Fixed phone freezing when removing usb cable with oc enabled
- Fixed charging death while oc enabled (still happens randomly)
- Added Blinky (thanks to Guardian_Bob)
- Removed Samsung Bloat
- Removed Gingerbread Keyboard
- Added new Vending.apk (redesigned market)
- Added Blinky App (thanks to Guardian_Bob)
- Added JL3 Swype
- Added Samsung Keyboard
- Fixed home button haptic
Build 8 Changelog:
- xcaliburinhand's headset jack fix
- Voodoo LagFix updated (c1f5dd5d1a3c2216a381)
- Updated ClockWorkMod Voodoo Edition
- Gingerbread Keyboard (thanks to kennethpenn)
- Added Voltage Control 2.0-rc2
- Fixed APN settings crash
Build 7 Changelog:
CogKernel2:
- raspdeep's 1280Mhz OC/UV v217 kernel patches (I will have a non-oc version for those who don't need it)
- hardcore's kernel patches
- correct framework from jk3, accidentally put jj4 framework in build 6
- bluetooth all working correct again (messed up due to jj4 framework from build6)
- Removed ULF
- Added Voodoo5 Stable (e9dc810ed3e6695c767a)
- Added Supercurio's CWM Voodoo edition
- Reoriented
- Removed multitouch keyboard (missing or very well hidden keys)
- Added stock Froyo keyboard
- Added BLN control - Free
- Home button fix (no longer acts as back button)
- Custom boot image(by me), replaces the AT&T logo (thanks to morfic), You still get the at&t screen for about 1 second until we can edit the boot.bin, that won't change.
- Based on JPM Froyo kernel
- Voodoo5 Stable by Supercurio http://project-voodoo.org/lagfix
- Custom CWM Voodoo Edition by Supercurio
- 341MB RAM and all features should work
- Includes neldar's BackLightNotification 2.2 from https://github.com/project-voodoo/backlightnotification/tree/master/kernel_patches/
- Sharpness & color fix for UI, inspired by supercurio's work on Voodoo
- SpeedMod: Replaced kernel jhash2 with jhash3
- Includes hardcore's Startup Tweaks from http://forum.xda-developers.com/showthread.php?t=813309
- Adjusted kernel HZ value to (hopefully) balance battery life & smoothness
- Uses BFQ IO scheduler by default, from http://algo.ing.unimo.it/people/paolo/disk_sched/sources.php
- Updated ext4 code in kernel from http://www2.kernel.org/pub/linux/kernel/people/tytso/ext4-patches/
- Added Tiny RCU patch for better speed and efficiency from http://android.git.kernel.org/?p=ke...it;h=9b1d82fa1611706fa7ee1505f290160a18caf95d
- Optimized compiler flags: -mcpu=cortex-a8 -mfpu=neon -mfloat-abi=hard -fno-gcse -fprefetch-loop-arrays --param l2-cache-size=512 --param l1-cache-size=64 --param simultaneous-prefetches=6 --param prefetch-latency=400 --param l1-cache-line-size=64
In case you're wondering where I got those compiler params from, some of them are from here: http://ctuning.org/dissemination/grow10-03.pdf
Click to expand...
Click to collapse
Build 5 Changelog:
Added AppWidgetPicker
SetiroN i9000 SuperOptimized ReOriented v1.4.2
Replaced the creepy eye (I asked the creator for permission, since I take donations he didn't like that.)
Added even bigger APN list ~1900 (thanks to knightnz)
Changed file system settings to jfs+ext2 loops back, helps some apps work better, no negative side effects.
The ext2 loops are done like so, they are not done like OCLF where they sit on top of another file system
Build 4 Changelog:
Fixed Locale (US only apps may not work, thinks the phone is in Canada) (thanks to for.digit for a proper fix)
Fixed APN auto selection
Fixed Market not working for some (thanks to hansmrtn for the tip)
Added Titanium Backup to /data/app
Added Rom Manager to /data/app
Lagfix enabled by default
CLShortFuse's GPS Fix v006
Build 3 Changelog:
Fixed RIL that I broke in Build 2
Fixed video player crashing while playing recorded videos
Fixed Random no data on first boot (you might have to select the apn, read below on how to do that)
Fixed Voice Search (Just FC's right now)
Added redbend_ua (bmlwrite is having a hard time flashing modem)
Added Email w/less security (thanks to Fenny)
Fixed Sdcard (showing up as cd-rom drive)
Updated Maps
Updated Flash
Updated Market
Updated Youtube
Removed TouchWiz30Launcher and TwWallpaperChooser
Moved Launcher2 and VoltageControl_1.98b to /data for easy removal
Known Issues:
confirmed:
unconfirmed: (cannot reproduce)
none
Credits:
Supercurio (Voodoo)
laststufo/hardcore/xcaliburinhand (kernel source/patches)
hansmrtn (help with market issues)
Fenny (modified email.apk with less security)
[email protected] (animations)
MagnusRagnarok (animations)
loserskater (android_id script)
CLShortFuse (gps fix)
for.digit (locale fix)
moogoat (wired headset testing)
DJNgoma (stock lock screen)
kennethpenn (gingerbread keyboard port)
Pretty hyped for this. Does jk3 seem snappier then our captivate leaks?
Looks like I may be coming back to the Cognition side. I unfortunately left after Axura came around as it was undoubtedly faster, at least by my standards, but since you are incorporating some of the things that contribute to its' speed, I can come back to the good side. FYI-I was following Cog for forever and flashed every build you had up to b6. I can not wait for this release!!!
And here I was enjoying aospMod by Molecule for a whole 12 hours... Looking forward to this beast!
Is jk3 an official build
Sent from my SAMSUNG-SGH-I897 using XDA App
Thanks DG. I'll have to give it a whirl.
bts0uth said:
Pretty hyped for this. Does jk3 seem snappier then our captivate leaks?
Click to expand...
Click to collapse
JK3 was the reason I left Cog in the first place. It is fast as hell when paired with the correct modem. I am currently loving Axura, which is JK3 based, but will be coming back to Cog if this is up to par.
bts0uth said:
Pretty hyped for this. Does jk3 seem snappier then our captivate leaks?
Click to expand...
Click to collapse
Its blows the doors off of (unofficial)official captivate roms. Its faster then the i9000 stuff too. (jk3 is i9000m)
adamholden85 said:
JK3 was the reason I left Cog in the first place. It is fast as hell when paired with the correct modem. I am currently loving Axura, which is JK3 based, but will be coming back to Cog if this is up to par.
Click to expand...
Click to collapse
Actually, that is the same vibrant rom I used for 2.4, he just has the modem in there now from JK3, which is the best modem now.
Oooh can't wait to try this out when you post it DG! I love the i9000 roms for some reason...
I'm pretty sure axura is based off of a vibrant rom...the only thing that is jk3 is the modem. I think its so fast is becase all of the TW stuff is replaced....its also overclocked at 1.2 ghz. Plus it has ULF which in my opinion is alot faster than voodoo
Sent from my SAMSUNG-SGH-I897 using XDA App
deffinately need to give this a try
designgears said:
Its blows the doors off of (unofficial)official captivate roms. Its faster then the i9000 stuff too. (jk3 is i9000m)
Click to expand...
Click to collapse
Hell yeah. Can't wait for it to be posted!
Now this looks VERY promising!
Backing up and charging as I type....
designgears said:
Its blows the doors off of (unofficial)official captivate roms. Its faster then the i9000 stuff too. (jk3 is i9000m)
Actually, that is the same vibrant rom I used for 2.4, he just has the modem in there now from JK3, which is the best modem now.
Click to expand...
Click to collapse
I had no idea it was the same. That is interesting. Why did yours kill the battery so fast though? That is the only reason I had to stop using that one which is the reason you pulled it to begin with. I just can't freaken wait for this to be released so I can come back to the Cog world!
This has HSUPA right?
JK3 is designed for Bell (Canada)'s i9000m, they have a slight hardware difference than the i9000. So this should be great for all North American variant with the exception of the camera app. You may want to use the Captivate/Vibrant version.
Running JK3 for a night now, most reception issues related to 850Mhz is gone. HSDPA is working (from reports) and the buzzing noise during calls are gone too!
Language pack that come with this will be: English (Canadian), French (Canadian) and Korean (duh.... Samsung is Korean)
I smell bacon
shaolin95 said:
This has HSUPA right?
Click to expand...
Click to collapse
yessir
killer23d said:
JK3 is designed for Bell (Canada)'s i9000m, they have a slight hardware difference than the i9000. So this should be great for all North American variant with the exception of the camera app. You may want to use the Captivate/Vibrant version.
Running JK3 for a night now, most reception issues related to 850Mhz is gone. HSDPA is working (from reports) and the buzzing noise during calls are gone too!
Language pack that come with this will be: English (Canadian), French (Canadian) and Korean (duh.... Samsung is Korean)
Click to expand...
Click to collapse
It is english only, all the csc stuff was brought over from cognition. Dates, times, etc have all been americanized. Camera has been swapped, contacts, dialer, etc...
you see video call in two places, one in the settings for setting the video call ringtone and a video call button when a call ends(using jpo phone.apk and phone_util.apk for band selection)
Sound over bluetooth and headset are crystal clear, as they should be.
born_fisherman said:
I smell bacon
Click to expand...
Click to collapse
Do you smell what designgears is cookin!!?
haha, couldn't resist.
charging now.. haha!!
So.. can i flash this rom on bell i9000m also? i guess i can..
Sent from ATT Captivate operated by COGNITION 2.3b6 Froyo
This is a minimalistic Thunderbolt kernel based on the official gingerbread kernel source, patched to 2.6.35.14, and then a bunch of lean mods added (look at feature list below).
DOWNLOADS:
1) lean (normal lean version), 1) 184Mhz (184Mhz can be unlocked via st - note for many people 184Mhz is unstable and cause issues, also supports outgoing call recording)
speedtweak.sh
This script will allow you to "transform" your kernel into normal, extreme, 1.92, 1.92X and battsaver versions (ie. it allows you to control speed, voltage, and slots to a certain degree). Once you run the script, everything will be self-explanatory. To run the script:
1) Open Terminal Emulator (install it from market if you don't have it).
2) Type "su" (without quotes) and hit enter.
3) Type "speedtweak.sh" (without quotes) and hit enter.
leanKernel kernel speed tweaker
------------------------------_
1) normal: undervolted, overclocked to 1.41Ghz
2) extreme: extremely undervolted, overclocked to 1.41Ghz
3) 1.92: undervolted, overclocked to 1.92Ghz
4) 1.92X: extremely undervolted, overclocked to 1.92Ghz
5) battsaver: extremely undervolted, not overclocked
6) Unlock 184Mhz
7) Lock 184Mhz
8) View current settings
Please type 1, 2, 3, 4, 5, 6, 7, or 8:
Click to expand...
Click to collapse
speedtweak.sh and SetCPU
The risk of running setcpu is that it can inadvertently override the min and the max that were set by the speedtweak script. (oh it can also override the governor setting but that's not as bad). Other than that it's pretty harmless - it can't mess with the voltage settings. So if you're going to use SetCPU, keep this in mind. One way to make this work is to use SetCPU to configure governor and min/max, and use speedtweak.sh to configure voltage settings. Or just don't use SetCPU.
FEATURES
Includes lots of goodies from kernel source (2.6.36.x & 3.x from kernel.org) newer than stock.
speedtweak.sh script to adjust clock frequencies and voltages.
SVS - manual voltage tweaking via /etc/init.d/01vdd_levels
InteractiveX and ondemandX governors! Added my own suspend code to interactive and ondemand code to make the phone lock at low clock speed when screen is off. No need for sleep setcpu profile anymore.
For 1.92Ghz builds, interactiveX and smartass governors were modified to minimize unnecessary spikes above 1.8Ghz to keep phone stable.
vm, minfree, memory, buffers readahead buffer tweaks
All unnecessary kernel components removed to make kernel lean and fast!
low # (5-10) of cpufreq slots for simple management and less governer transitions.
Undervolted for longer battery life.
SWAP and EXT4 enabled.
Filesystems mounted via EXT4, and tweaked for performance.
init.d enabled in ramdisk
TUN, CIFS, NSIO (netspector) module support
zram (from linux 3.1) module support (to enable, go into Terminal, type su, and then type "zram enable" without quotes). What is zram?
TINY_PREEMPT_RCU.
CHANGELOGS
4.2.0 (10/28/11) - last "stable" kernel based on cm7 source.
5.0.0 (10/29/11) - based on official kernel source from HTC.
5.0.3 (11/1/11) - bluetooth, video playback, scaling frequencies sysfs all fixed. audio levels tweaked. netspector(nsio) module upgraded to 2.0.
5.0.4 (11/13/11) - 5.0.3 with audio levels reverted stock for better compatibility with MIUI (no need to upgrade from 5.0.3)
5.1.0 (11/16/11) - cpufreq and cpuidle updated to linux v3.2rc1, suspend support for LTE, 184mhz version supports in-call recording now (outgoing only).
DIRECTIONS
Uh.... flash the zip in clockworkmod. You may need to wipe Dalvik cache and/or delete /data/misc/dhcp, /data/misc/wifi.
Donate to your favorite charity, or donate to me.
GOVERNORS
First, my take on the governors that are out there: http://forum.xda-developers.com/showpost.php?p=13020648&postcount=617
I offer three governors: interactiveX, ondemandX, and smartass. What are they?
interactiveX - it's the interactive governor from CM, but I added suspend/wake logic so when the phone screen is off it runs at below 400Mhz. Also, I modified its code some more to minimize unnecessary cpu spikes above 1.8Ghz if you happen to be running one of my 1.92 kernels. Most tbolts are unstable above 1.8Ghz, and it's the quick jump above 1.8Ghz that usually locks up the phone. It will hit 1.92Ghz only when it makes sense (ie. sustained high load). This is my favorite governor - perfect combination of speed and power efficiency.
ondemandX - ondemand governor code from latest linux source *plus* the suspend/wake logic described above, except it has the ability to ramp to 369Mhz while screen is off. No additional code was added for stabilizing above 1.8Ghz.
smartass - smartass code from erasmux, but I wasn't happy with its performance so I tuned it for quicker ramp up in speed. It has the same suspend/wake logic as ondemandX, and the same >1.8Ghz stabilizing mod as interactiveX.
Source code
AOSP: https://github.com/imoseyon/leanKernel-tbolt-gingerbread/tree/aosp
AOSP FAQ
Wifi is not working - 1) first make sure you flash kernel via CWR, not kernel manager or rom manager, 3) clear dalvik cache, 2) delete all files in /data/misc/wifi and /data/misc/dhcp, and reboot.
Imoseyon said:
Thread split into GB and Froyo. "
Click to expand...
Click to collapse
finally took my advice huh???? lol
good work, flashing now!
Whats the change log on 2.5.3test2 ?
Will that work on cm7?
Great work as always! Very impressed!
Sent from my ADR6400L using Tapatalk
well we need to run scripts to over clock gbtest kernel like the previous ones for froyo and cm7
psicrest said:
Whats the change log on 2.5.3test2 ?
Will that work on cm7?
Click to expand...
Click to collapse
he's working on changelog and the 2.5.3 test 2 kernel is only for the "gingersense" leak...for cm7 flash the AOSP kernel
by default the 2.5.3 kernel will run at 1408mhz in "normal" mode
Awesomeness...finally able to boot all the way up...running battsaver...and confirmed camera is working...thank you imoseyon!!!
Saweeeet!!!!
I'll check back later with my experiences running
This may have fixed the slow charge issues inadvertantly. its not in your change log but either this (test2) or 1.3 on jcases build fixed it.
Sent from my ADR6400L using XDA Premium App
arcanexvi said:
This may have fixed the slow charge issues inadvertantly. its not in your change log but either this (test2) or 1.3 on jcases build fixed it.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
This new kernel fixed the slow charge for you or updated jcase gbread rom? I did both and my phone refuses to charge.
Sent from my ADR6400L using XDA Premium App
I don't know if this was posted before, so i apologize if it has;
Here are my questions;
How can having the 184 slot unlocked be worse? (I saw this posted with no explanation in the old thread)
I've used all governors on batt saver and all run smooth as butter, so which will give me best battery life? I understand interactiveX is for performance and efficiency, smartassx and ondemandx are both kinda similar.....
I adjusted the voltage to the lowest values that my phone could handle but my battery life was worse than before.....
Excuse my noobishness
Ok full change logs for v2.5.2test2 sense:
v2.5.3test2 (5/19/11) - fixed BT, backported usb stuff from ace kernel including otg, changed overclock/undervolt to safer values.
gonna work on wifi tethering today.
nerogold said:
This new kernel fixed the slow charge for you or updated jcase gbread rom? I did both and my phone refuses to charge.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
That is weird, mine charges fine. I'll try to look at this today.
Derrtydozen said:
I don't know if this was posted before, so i apologize if it has;
Here are my questions;
How can having the 184 slot unlocked be worse? (I saw this posted with no explanation in the old thread)
I've used all governors on batt saver and all run smooth as butter, so which will give me best battery life? I understand interactiveX is for performance and efficiency, smartassx and ondemandx are both kinda similar.....
I adjusted the voltage to the lowest values that my phone could handle but my battery life was worse than before.....
Excuse my noobishness
Click to expand...
Click to collapse
Sometimes extreme undervolting can do more harm than good. If your phone is not getting enough juice then it can have unpredictable results. Try bumping up voltage to see if it helps.
Imoseyon said:
Ok full change logs for v2.5.2test2 sense:
v2.5.3test2 (5/19/11) - fixed BT, backported usb stuff from ace kernel including otg, changed overclock/undervolt to safer values.
gonna work on wifi tethering today.
Click to expand...
Click to collapse
I've been waiting to flash this until the camera and USB issues were sorted out.
The GingerJane thread says "PSCII.apk (chingy) - fixes usb mounting with custom kernels"
...does this mean that I need to flash that file to fix USB mounting or is it already fixed on YOUR v2.5.2test2?
Natef53 said:
I've been waiting to flash this until the camera and USB issues were sorted out.
The GingerJane thread says "PSCII.apk (chingy) - fixes usb mounting with custom kernels"
...does this mean that I need to flash that file to fix USB mounting or is it already fixed on YOUR v2.5.2test2?
Click to expand...
Click to collapse
So turns out USB mounting wasn't really broken with the kernel. There's some compatibility issues with the leak connect to pc app. You'll need the new PSCII app for usb mounting to work. Both jane and gingeritis should have the new apk now.
How many are experiencing.lockups and random reboots with his kernel? I hope I'm not alone...
I thought it was just the radio but once I switched to the stock.kernel everything was fine and dandy
Sent from my ADR6400L using XDA Premium App
Imoseyon said:
So turns out USB mounting wasn't really broken with the kernel. There's some compatibility issues with the leak connect to pc app. You'll need the new PSCII app for usb mounting to work. Both jane and gingeritis should have the new apk now.
Click to expand...
Click to collapse
Nice. So install the APK and then reboot and flash the kernal and everything should be good?
How close is the kernal to the stock one in the GB leak? I have been getting decent performance and great battery life, hoping that doesn't change with the new one.
How about the wifi tethering issues?
Will the swap enabler work properly with the GB Sense Test Kernel??
Sent from my ADR6400L using XDA App
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
These kernels are provided as-is without warranty. I'm not responsible for any problem you can encounter with your phone or if your cat suddenly dies.
Although, don't expect support even if I will eventually help since I love cats.
Note : These kernels are only compatible with CyanogenMod and MIUI roms !
Do you want to discuss on this kernel, get the fresh news on development, or become a kernel tester ?
Join the IRC channel from your web browser herehttp://webchat.freenode.net/?channels=glitchkernel ! No registration needed
Make sure the channel is "#glitchkernel" and you're set.
For those who already have an IRC client,
here is the server : irc.freenode.net
port : 6667
Channel : #glitchkernel
Overview :
- Up to 1.7GHz CPU OC with added bus/GPU OC (Thanks to morfic for the great base of work)
- Undervolting (using third party apps)
- Voodoo Sound & Voodoo Color (Thanks Supercurio & renaudallard)
- FPS uncap (Screen running 68Hz instead of 60Hz, from 56 to 66 FPS max) from JPX source
- Various tweaks for more smoothness and reliability
- LED notifications using Neldar's BLN
CHANGELOGS IN #2 POSTThe frequency/voltage & informative UV settings table is as follow for V13 kernel :
Note that these UV settings will be unstable on many devices. It's only informative.
1700 MHz - [email protected] 243 MHz - 1.500v / -> Most phones will fail here. -25 to -50mV may help to stabilize. Much stabler as unique frequency for benchmarks.
1600 MHz - [email protected] 229 MHz - 1.500V / -> That's high and many devices will fail on this frequency. Find working UV for you if any.
1500 MHz - [email protected] 250 MHz - 1.500V / -25mV
1440 MHz - [email protected] 240 MHz - 1.475V / -50mV
1400 MHz - [email protected] 233 MHz - 1.450V / -50mV
1300 MHz - [email protected] 217 MHz - 1.400V / -50mV
1200 MHz - [email protected] 200 MHz - 1.350V / -50mV
1000 MHz - [email protected] 200 MHz - 1.250V / -50mV - If you have stability issues, try to let this one by default.
800 MHz - [email protected] 200 MHz - 1.200V / -75mV
400 MHz - [email protected] 200 MHz - 1.050V / -100mV
200 MHz - [email protected] 200 MHz - 0.950V / -150mV
100 MHz - [email protected] 100 MHz - 0.950V / -200mV - (can be very different between two devices)
GPU frequency is linked to bus speed
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.
-Pimp My CPU (recommended if you're using MIUI) : http://forum.xda-developers.com/showthread.php?t=1018411
-Voltage Control : http://forum.xda-developers.com/showthread.php?t=829731
-SetCPU : http://forum.xda-developers.com/showthread.php?t=505419
Downloads
Glitch kernel (CWM flashable only)
Glitch Kernel Updater app now available on the Android market to support us !i9000 :
- 03/01/2012 - V13.1
Captivate:
- 03/01/2012 - V13.1
Vibrant:
- 03/01/2012 - V13.1
Fascinate:
- 03/01/2012 - V13.1
Telus Fascinate:
- 03/01/2012 - V13.1
OLDER RELEASESLIVE OC GUIDEFAQ, Changelogshttp://forum.xda-developers.com/showpost.php?p=13021804&postcount=2http://forum.xda-developers.com/showpost.php?p=13021804&postcount=2
-------------------------
Source :
- Glitch repo : https://github.com/organizations/Glitchkernel
Who is the Glitch team ?
- Kernel developement : ssewk2x & Tk-Glitch.
- Public relations / web hosting : Sixstringsg.
- App developement : Smasher816.
- Beta testers team, with members coming and leaving
Credits :
Codeworkx, Pawitp, Atinm, GuiPerPT, Unhelpful, Coolya, Morfic, Ezekeel, Zacharias.maladroit, Bilboa1, TheEscapist, Netarchy, Supercurio, lippol94, MAMBO04, Galnet, nitr8, Rahulrulez, Chadouming, renaudallard, existz, times_infinity, bearsfan85
Thanks to the donators and everyone bying the Glitch Kernel Updater app from the market, it's much appreciated and encourages us to continue our work !
Thanks to the beta testers team and to everyone helping me to debug and find new useful things to integrate !
Without all of you, this kernel wouldn't be !
Changelogs :
V13 - LATEST
03/01/2012 - V13.1
- Cleanup.
- Fixed buttons freezing randomly.
- Fixed media buttons / headset buttons.
- Lots of GPIO fixes which eliminate phantom keypops.
- Added updated sysfs interface for smartass governor.
- Updated screenstate scaling script to use non-deprecated sysfs
interface for smartass2 and other govs.
- Back to CM7 LED Notifications.
- Lots of changes to cypress touchkey driver to guard against phantom
keypops and speed things up.
- Removed CarrierIQ-related virtual serial device. It probably wasn't
used, but now we know for sure.
- Changes to dpram (modem kernel interface) to make the radio a
little more stable.
- slightly more helpful gamma table error message.
- Moved call audio sysfs files from voodoo sound group to their own.
- Integrated 90call_vol into the kernel zip file so people don't
have to mess with it on their own.
- Now possible to choose any governor as sleep governor in the recovery.
- Vandalized bootlogo a bit.
20/11/2011 - V13
- Upstream synced to the latest at release time
- New CFLAGS again
- mfpu switched from neon to vfpv3
- BLN now working correctly, with LED timeout (thanks to Zacharias.maladroit)
- Back to hard float
- Updated toolchain to 4.5-2011.10
- Modified screen colors to look better (ugly gradient fixed, yellowish tint fixed). Don't use Voodoo Color punchy settings with this though (green screen likely to be back)
- Better reactivity under load
- 348MB RAM available
- Better 720p video recording (less buggy)
- Doubled SDCard read cache - Slight speed-up on SDcard read speed
- USB power drain fix
- Better memory management
- Back to 3.0V for the screen - 2.6V said not to give more battery life because of the added amperage
- Bugfixes
- Added Cgroup timer slack to group tasks by timer slack value
- Switched to Tree preempt RCU and added RCU boost
- New rethemed/recolored recovery menu and bootlogo, thanks to Fate-Silver for the blood
- Fixed "GLITCH" menu in recovery not showing for i9000 and Telus Fascinate
- Better handling of the CPU frequency table, + fixes
- Fascinate related fixes and updates from JT1134
- Added Lazy and SmartassV2 governors
- Fixes for SDCard handling
- All leakage settings are now available from a single kernel. Use the GLITCH menu in recovery (recommended way to switch the values)
- Added support of JT's 3-button recovery hack (credit to JT1134)
V12
13/07/2011 -> 29/09/2011 - V12 BETA #3
- BackLightNotifications (BLN) port, thanks to Zacharias.maladroit must use the BLN app. If it doesn't work, try Blinky. Still not fully working though.
- Some cleaning and added tiny fixes
- Fascinate : Now using Yamaha compass driver from ED01
- *Temporary* fix for green flashes/colors on low brightness (reborn/still not fixed in V11 - not yet proper though)
- Modified color multiplier to avoid yellowish tint by default
- Enhanced cleaning script when flashing
- Screen undervolt (from 3.0V to 2.6V) // it should help battery life
- Lowering kernel debugger buffer
- More work on leakage values
- Adding some old-school (V9D) CFLAGS resulting in substantial performance and stability gains
- 800MHz random lock fixed - not fully fixed it seems
- Popping keyboard bug fixed
- Make use of NEON accelerated mfpu
- Slightly more aggressive ondemand governor default settings // searching the best balance for efficiency
- Added a few speed enhancements
- In-call receive audio is much louder across the board. You can now hear your significant other yelling at you if you're in a noisy area. Sorry, guys
- In-call mic gain should see some improvement as well. Meaning your wife can now hear you apologizing better
-- caveat: I've heard conflicting reports about this while using bluetooth. I'm investigating that, so stay tuned.
- Overhauled the screen state scaling feature.
-- governor setting now stays put
-- users can now enable/disable the feature and configure it via the custom recovery listed below
- New recovery. Screenstate scaling is controllable via recovery, and it's themed now.
-Audio output and input controllable via script linked in OP
-Call volume tweaks re-written to be more clean/effecient.
-Screenstate bug fixed, doesn't cause lag anymore.
-Upstream synced (this means you must be on the latest nightly for your device for this to work)
-New drivers
V11
13/07/2011 - V11
- Upstream synced as always (updated recovery...)
- More debug stuff disabled & cleanups/fixes on various things
- Printk disabled to reduce overhead
- Updated to linux kernel 2.6.35.13
- OC implementation fixes and modifications (fixing overvolt in Voltage Control Xtreme as well as some other tiny things)
- Added experimental GPU OC implementation from TheExcapist (for future use / not yet functional)
- 1.7GHz step added - working on some pretty good phones
- Modified touchkey/Led notifications settings from Zacharias.maladroit
- Added SLQB
- Added SIO and BFQ schedulers
- Back to LZO compression for faster boot time
- New voltage settings for more stability
- Trying some new speed tweaks
- Better memory management
- 340MB of RAM available for user without breaking 720p recording
- Preemptible Tiny RCU
- Automated per tty task groups patch
- Added InteractiveX governor
- Two new branches for OC settings adapted to high and low leakage chips
- Toolchain sorcery, thanks to Zacharias.maladroit (RIL is compiled using 4.4.3 toolchain, and everything else is compiled using 4.5.2 toolchain -> more speed and stability)
- Enhanced Voodoo Color settings from renaudallard
- Voodoo Sound V10
- Allow CPU-supported unaligned accesses
- Logcat on/off scripts (built as module)
- Bluetooth HID support
- New, cleaner bootlogo
- Now cleaning old scripts, OC values, cache and dalvik cache on kernel installation - thanks to lippol94
- Green tint on low brightness fixed
- Switched to ondemand governorV10
27/05/2011 - V10A Do not use with CM7 builds older than 23/05 (as well as the 28/05 or newer build) or MIUI -> you'll get no service !
- Now fully compatible with latest CM7 Nightly builds
- Back to 2010.09 toolchain -> slower & less stable but needed to make a working kernel for latest builds
- Upstream sync (bigger radio partition, headset stuff..)
- Int voltage changes to get some stability back on all overclocked frequencies
- A bit faster 1.5 and 1.6GHz steps - Could make these steps unstable for some, please try and report
- Smartass governor tweaked for faster scaling up, and slower scaling down -> better stability and speed
- OC code bugs and inconsistencies introduced in V7B now fixed (it was here to prevent sleep of death issue, now fixed)
- Some fixes and enhancement for compatibility with Xan's Voltage Control app
- Various tweaks for MOAR SPEED
- Black magic
Known issues :
- The reboot recovery command seems broken for some reason on recent builds. Probably rom related.
- Some users still get freeze issue on boot. If you have this issue, please use the "no-optimization" kernel for you device from this post : http://forum.xda-developers.com/showpost.php?p=14180722&postcount=2077
03/06/2011 - V10B To use with newest builds only (equal or newer than 28/05) !
- Upstream sync (FM radio, new Voodoo Sound implementation, etc...)
- Back to 4.4.3 toolchain - needed for new RIL
- Big cleanup - rewrite from scratch
- Many fixes
- New tweaks for speed on 4.4.3 toolchain
- New tweaks for stability on 4.4.3 toolchain
- Black magic
17/06/2011 - V10C (Updated) To use with newest builds, #28+ for i9000 or equivalent
- Upstream sync (cpuidle, updated drivers (wifi etc.), Recovery 4.0.0.x, etc...) (updated as of today 17/06)
- More debug stuff disabled
- Dock audio support (experimental)
- Added DIDLE (Deep Idle) support (removed, buggy)
- New voltage tweaks for added stability on some devicesV9
16/05/2011 - V9A
- Merged with the now dead V8C update because of new added features
- Upstream sync : Calculate battery percentage as percent of max capacity reported when battery full, new wifi driver, etc.
- New PMEM settings for more available RAM (now 331MB)
- 1.54GHz step added with some gentle settings for now.
- New step by step frequency switch when scaling down (part of the Galaxy S II port from Bilboa1) - more stability on highest frequencies
- Corrections and further tweaking on smartass governor + some fixes from Netarchy (Nexus S). 400MHz lock when screen is on removed (not needed anymore -> more power saving)
- Higher cache for faster SDcard read speed
- New sleep settings : Effective lock to 400MHz max when screen is off -> fix long wake up/hiccups when playing music or similar use. Be careful with your UV settings on 200 and 400MHz steps to avoid sleep of death problems ! These were not used on previous versions of my kernel (locked to 100 MHz when screen off and locked to 400MHz when screen on with a buggy gap in smartass governor forcing generally 600+ MHz)
- 600 MHz step removed (it was generating instabilities on some phones when jumping to 800 or down to 400 when using UV)
- Some voltage tweaks for added stability on some devices (as always)
- Cleanups on unused/no more needed stuff
- Little surprise, thanks to Morfic
- Updated to V9A² to fix SOD and some performance issues
21/05/2011 - V9B
- Upstream sync (CWM recovery 3.1.0.1, better screen colors (kills voodoo color for now and looks awful on my 0516 build, but should be good on latest), GPIO fixes, samsung modemctl...) + small changes on my side for official CyanogenMod repository compatibility
- Voodoo Sound updated to V9 / cleaned voodoo color stuff until it works again
- New cleaner bootlogo based on the one in first post, preferred by most users
- Some additional compilation flags from Netarchy and Zacharias.maladroit (better overall performances + NEON)
- Screen refresh frequency bumped to 72Hz (68Hz effective). It'll uncap FPS to 66 again but seems stabler than before on framerate (the divide/2 behavior happens less)
- Added screenstate scaling script from well.heeled.man as a test (with my kernel's smartass default settings). It should give better sleep power consumption as well as better power efficiency on screen off tasks like music playing etc. by switching to conservative governor.
If you want more information, discuss on this or contribute to enhance it, please come here : http://forum.xda-developers.com/showthread.php?t=1087646
- Adding some stuff from Zacharias.madadroit :
- Higher battery charging temperature
- Scheduler tweaks
Alternative version now available (V9B-VC) using old AMOLED panel color/gamma settings and with Voodoo Color V2 added back.
24/05/2011 - V9C TO USE WITH CM7 Nightly build #12 OR HIGHER ONLY
(Updated to fix "no service" issue, but still sucks.. unstable on #12 build, very stable on others but no service)
- Upstream sync (PMEM disabled (gives 339MB RAM now), new RIL, headset fixes...)
- Divider changes for MUCH better stability on 1.2GHz at the cost of a slight decrease on performances
- New branch with Voodoo Color display driver and "old" color settings named "VC"
- Fix for Vibrant no service problem - hopefully
- Small changes on smartass governor for better scalability (reverts some old settings not needed anymore with the screenstate script)
- Glitch logo now in update script too for nanu_x2 to be amazed when installing my kernel
24/05/2011 - V9D TO USE WITH CM7 Nightly build #11 OR LOWER (for i9000, or cappy/vibrant equivalent) AND MIUI ONLY
First "D" revision.. Sound like duty. It's basically a fix of a fix done to make the V9C features available for "stable builds" (considering the i9000 #12 isn't)
- Obviously all the V9C changelog
- Using old RIL to be compatible with builds before #12 for I9000 (--> WON'T WORK with #12 for i9000 or equivalent !)
- Replaced 1.54GHz step by 1.6GHz (1.54GHz step was somewhat useless, too close to 1.5Ghz, and slower overall because of the lower bus speed)
- I can't build Vibrant ATM, the CM7 build system is broken on this device or I'm doing something wrong but I wasn't able to fix it. Any help is appreciated. I'm sorry for Vibrant users I'm screwed.V8
07/05/2011 - V8A - To use with 05062011 or newer CM7 build (useable on MIUI RC8 but you'll lose camera - MIUI needs an update)
- Upstream sync (camera fixes etc.)
- More stability fixes
- Cleanups on OC code (found that 1.2 and 1.3GHz were very unstable compared to earlier releases)
- More work on Vibrant/Captivate. The kernels are now available to download but are untested - for now. Feel free to try and report any problem or if all runs well. If I have enough positive reviews, these kernels will be released in their respective device sections.
11/05/2011 - V8B
Upstream sync only :
- USB switch suspend
- TV out stuff
- Fascinate specifics
- Revert "Got back to previous samsung_modemctl" for 05112011 CM7 build
V7
02/05/2011 - V7A - To use with 05012011 or newer CM7 build and MIUI RC8+ only
- Resurrect Voodoo Color killed by 2.3.4 merge.
- New step for 1.5GHz on top of 1.44GHz (now 9 steps total versus 8 before)
- Forcing 400MHz max when sleeping for added battery life (default = 800). Couldn't detect any side effect.
- New tweaked Smartass governor now default (800MHz min when screen on). Please report your experience
- It seems the smartass governor is not working by default, it will revert to performance >< Please force it to get it to work -> Ok found the problem, I'll update in a min
- Now updated to V7A-2 to fix the governor bug
03/05/2011 - V7B - To use with 05012011 or newer CM7 build and MIUI RC8+ only
- Resurrect Voodoo Color killed by 2.3.4 merge - Again - fully working now
- Fixed sleep of death issue when unplugged
- Switched to LZO compression for better overall speed and reduced boot time
- Tweaked smartass governor more for - hopefully - better battery life and a bit more responsivity
- New voltage and frequency table rewrite as a bonus with now 11 frequencies total
- Stability fixes on 1.5GHz step -> please test and report
- Reverted FPS uncap - at least for now - for two main reasons : more stability on high GPU freqs (1.4GHz and more), and to prevent FPS limit at max/2 (33 when unlocked to 66), limiting overall performances in heavy scenes. I think there's a lack of buffering somewhere.. It will give higher scores on some benchmarks, and lower on others. A better battery life can indeed be expected too.
- Upstream sync
05/05/2011 - V7C - To use with 05032011 or newer CM7 build and MIUI RC8+ only
- Upstream sync (better battery life, reboot recovery, etc.)
- A general stability fix missing from V7 branch added back
- Tiny tweaks on the voltage table
- Big bugfix on the V7 branch (redone from scratch, cleaner)
- Switched to 2011.03 toolchain
- Added some optimization flags, "-mfloat-abi=hard" being one of them (up to 40% performance gains in specific cases)
- Small improvements here and thereV6
WIP
22/04/2011 - V6pre - preview/work in progress of upcoming V6A update *test* :
- Reverted PMEM settings to new CM7 default (317MB - same as V5A)
- Reverted some stability fixes that weren't that stable on some devices, or even prevented some to boot
- New voltage table for a more linear increase, improving stability at default settings
- Switched to Deadline scheduler by default as it appears more stable
- Back to 2010.09 toolchain for speed and efficiency
- Synchronized with last update from SGS CM7 team
Better to use CM7 04212011 update with this kernel and newer.
22/04/2011 - V6pre - update 1 :
- Battery polling bumped to 15 sec (was 1 before), it should help battery to an extent (thanks to Zach for the idea)
- Some internal voltage tweaking to hopefully be more UV friendly
- Bumped USER_HZ for more smoothness
- Another -rare- bootloop fix
22/04/2011 - V6pre - update 2 :
- Added some tweaks from V5A for testing
- Resolved a bug generating fake voltage reading
- Resolved a bug on 400MHz step generating instabilities
- Slight changes to the voltage table
- Fixed a typo
- Trying some toolchain switch - again-
23/04/2011 - V6pre - update 3 :
- Corrected Led Notifications - Now it should work properly again !
- Various bugfixes and typo corrections
- Toolchain change once again
- Added new Interactive governor with aggressive settings for even more speed. You need to change it by app (pimp my cpu/cyanogen settings), it's still on conservative by default.
(thanks Zach for your suggestion)
25/04/2011 - V6pre - update 4
- Cleanups on Led notifications to resolve a bug (buttons stopped working randomly for some users)
- More typo corrections
- Voodoo Sound V8
- Various bugfixes on CPU load and schedulers
- CONFIG_CC_OPTIMIZE_FOR_SIZE disabled for speed
- Lower latency on GPU states switch for stabler performances
- Added a stability fix for voltage change latency when frequency is changing. It should give more stability with high undervolt or big voltage differences between two steps - Please test and report ! (Thanks Zach for pointing that to me)
- Two versions for testing purposes : V6pre-u4 is compiled using GCC 4.5.1 toolchain, and V6pre-u4(alt) is compiled using GCC 4.4.3 one. If you get instabilities on the first one, try the other and vice versa. Please report your findings on that because it was the first stability differences source between my kernel revisions. For information, V6pre-u2 was compiled with 4.4.3, and u3 with 4.5.1.
27/04/2011 - V6pre - update 5 >> 6
- Name changed from "TkGlitch" to "Glitch"
- Cleanups on buttons (Kangsterizer)
- Lower latency on GPU states switch for stabler performances in 3D and/or at high GPU frequency - corrected, thanks to Kangsterizer
- Added a stability fix when frequency changes for cpufreq governors
- Tweaked Interactive and Conservative governors for testing
- New Frequency table : 1.5GHz is now the max selectable frequency, and 800MHz and 400MHz steps are now replaced by a unique 600MHz one.
- Changed initramfs source to remove the annoying "E:no misc partition" error in the recovery
- Now bumped to update 6 to fix an issue with the conservative governor.
27/04/2011 - V6pre - update 7
- New Frequency table : 1.44GHz removed, 800 and 400MHz steps are back.
- Battery polling bumped from 15 to 30 seconds
- GPU power latency bumped from 10 to 60 ms
28/04/2011 - V6A - To use with 04282011 or newer CM7 build only
- New sensors drivers added
- Normalized 1.5GHz bus speed (GPU will now run @ 250MHz versus 247MHz before. It can affect your stability !)
- Int voltage lowered for 1.5GHz step because it did have a bad effect on lower frequencies stability
- GPU power latency back to default - but fixed (100ms)
29/04/2011 - V6B - To use with 04282011 or newer CM7 build only
- New initramfs source to fix compass and update CWM recovery
- 1.5GHz replaced by 1.48GHz for stability
- New voltage table as requested by many users (+25mv on 1200 to 1400MHz steps)
- New interactive governor for better scaling and battery life
- New tweaked smartass governor for testing (pretty bad on CPU benchmarks for some reason, please test how it feels in real world use)
- New ondemand governor from Zacharias.maladroit sources for testing
02/05/2011 - V6C - To use with 05012011 or newer CM7 build only
- Small update to merge with 2.3.4 source, no new feature.
02/05/2011 - V6C² - To use with 05012011 or newer CM7 build only
- Update to repair Voodoo Sound conflicts from 2.3.4 merge.
- Back to 1.44GHz max to prepare 1.5GHz return
V5
19/04/2011 - V5A - Initial release
21/04/2011 - V5B :
- GPU overclock on 1.3 GHz added (217MHz / +8.5% from default)
- New PMEM settings for more available RAM compared to V5A (now 328MB)
- Stability fixes for all frequencies, needing globally less volts. Results may vary depending on the device
- Switched to Conservative governor by default (still switchable by app). It can feel less responsive coming from idle but more battery saving, and plays better with high frequencies.
- New voltage table. Default settings should be stabler for most devices.
- Switched to 4.4.3 toolchain for added stability on some sensitive devices
Captivate and Vibrant support will come later. It will need more time than expected.
21/04/2011 - V5C : Small update to fix a bootloop issue on some devices.
F.A.Q.
Because I got tired of answering these same things 100's of times.
1) Where can I find the latest beta?
They are always in the OP. They are also in my signature, and the root of the FTP.
2) Where is the root of the FTP you ask?
Good question! It’s in the OP as well.
3) How do I install this? / I'm having problems installing
Reboot into recovery
Install zip from SDcard
Choose zip from SDcard
Navigate to the zip you downloaded.
4)What is Leakage (LL,ML,HL) and what one should i use?
Easy explanation: start with HL. If it allows you to OC how much you want, stay there. If not, move down until you get what you want.
For people who want more: Well, we made different leakages because koflem couldn’t OC, and he felt left out, so he started compiling on his own, which gave Tk-Glitch the idea to make three different versions. They have to do with the differences in different phones. Take for example different phones run better with different OC/UV. The leakages are the same way. They adjust the int voltages, which is something not configureable (yet) in userspace, so we have to configure them that way when we build. That way both the voltages that you are used to (the ones controllable via voltage control) are tailored to your device, as is the int voltages (the ones only we can do). Most people have no idea, but there are dozens of variables that we play with to make so that all of you can OC and UV as much as possible with as much stability as possible. Some aren't device specific, some are. We are trying to make the best experience possible for a wide range in chip quality, therefore we make different leakages, as well as making the kernel configurable via voltage control. From a stability/performance standpoint, and by extension standpoint, there is only one leakage right for your device. Different leakages aren't better in some ways for you and worse in others, there is only one good one for your device. Sorry if that didn't make sense, I tried to make it as informative as possible without it being overwhelming.
5) Does this work with Gingerbread bootloaders?
Yes
6) What ROM does this kernel work on?
For sure: CM7. Other CM7 based ROM’s may work, but I can’t offer you much support. If it works on CM7, that’s my goal. This WILL NOT work on Samsung based ROM’s, and I won’t port it. If you still don’t know what ROM this will work on, then you should read a lot more.
7) How do I enable BLN?
Download either BLN here: https://market.android.com/details?id=neldar.bln.control.free&feature=search_result Or Blinky here: https://market.android.com/details?id=com.kin.blinky&feature=search_result
8) How do I overclock?
Xan’s Voltage Control App here: https://market.android.com/details?id=com.darekxan.voltagecontrol&feature=search_result . READ THIS GUIDE FIRST: http://forum.xda-developers.com/showthread.php?t=1036020 If you break something while Overclocking, I won’t provide much support. Overclocking is awesome, but very variable across devices. We try and make a stable experience for everyone, but it is not guaranteed. If it breaks, I didn’t do it. If it makes your phone fly, I did it.
9) Can I be a beta tester?
Probably not. Unless you do something to make me like you a lot (cough strictlyrude27 cough), then you can’t have betas. The reason being they are unstable usually, and I already have a big enough team that I can get the information I need.
10) Why does my screen look ugly? / How do I change the screen color?
Go grab voodoo control from the market here: https://market.android.com/details?id=org.projectvoodoo.controlapp&feature=search_result , then play with the sliders until you like what you see. If you get really stumped, here are some values that people tend to like. They are from zacharais.maladroit.
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)
1)Color Profiles: Voodoo Profile V1
2) Screen v1 gamma hack :
- 50 red
- 53 green
- 44 blue
3) RGB multipliers:
Red ="2300875360"
Green ="2300875360"
Blue ="2709919680"
11) The backlights on my soft keys stay on all the time. Why is that?
Honestly, because I haven’t spent the time to “fix” it. They aren’t that bright, so people can stand it for a little while. I didn’t intentionally make it that way, it happened when we switched back to BLN instead of LED notifications. We made that switch because I like Blinky, and I get to pick until Tk-Glitch is back, or I am convinced otherwise.
12) I’m getting bootloops, why?
Well, the most common issue is that you have mismatched ROM’s and kernel’s. You need the latest ROM for your device, and the V12B3 kernel for your device. For where to find that, see above. The next is various scripts and “fixes” that you flash after/before the kernel. Reflash the nightly for your ROM, then the kernel. Let it boot. If it works and didn’t with the various other zips you may use, then don’t use those zips.
13) WHEN IS THE NEW VERSION OUT?
First Rule of Cyanogenmod... I'm allergic to ETAs so I try to stay away from them if at all possible. Causes all kinds of nasty problems they do....
14) How do I use the 90_callvolume script?
Download it here:
neh4pres wrote these instructions, if clarification is needed just ask.
There are many ways to apply this patch. But for these instructions i will be using root explorer because it has all the utilities needed.
After downloading, use root explorer to extract 90call_vol from the .zip. this will place 90call_vol in the extracted folder of your sd card. Long press and copy that file and paste it in the /etc/init.d folder. Once it pastes long press the file and open with text editor.
In call boost.. only change the final number in the line you want to adjust and keep that number between 0 and 3
INCALL_BOOST_EARPIECE=2
INCALL_BOOST_BLUETOOTH=2
INCALL_BOOST_SPEAKER=2
INCALL_BOOST_HEADPHONE=2
Mic gain only change the final number in the line you want to adjust and keep that number between 0-31
MIC_GAIN_EARPIECE=19
MIC_GAIN_SPEAKER=31
MIC_GAIN_HEADPHONE=29
MIC_GAIN_HEADPHONE_NO_MIC=18
Save changes when exiting and the editor will append the original file with a .BAK . You can use 90call_vol.bak to revert back one save. If you change multiple times and want to go to stock you can use the 90call_vol in /sdcard/extracted.
15) Is the GPU overclocked?
Yes. Can you control it? No. That code hasn't ever worked, and we don't really expect it to. The GPU is so overclocked at 1.5 Ghz that if it went any higher the memory would get corrupted and really bad things happen.
Nice work sixstringsg for maintaining a captivate thread for this kernel!
..also 10 pts for 1st reply!
Coreym said:
Nice work sixstringsg for maintaining a captivate thread for this kernel!
..also 10 pts for 1st reply!
Click to expand...
Click to collapse
Thanks! Now we just need to get more people on it
Sent from my CM7 powered captivate
20pts for third reply....I was fashionably late!
So maybe I just can't read , but does this have LED notifications, or did they get taken out when they were taken out of CM?
ls377 said:
So maybe I just can't read , but does this have LED notifications, or did they get taken out when they were taken out of CM?
Click to expand...
Click to collapse
This kernel has them.
Sent from my CM7 powered captivate
about time we got our own thread for this....i will still hang over on i9000 though....lol
o yeah 6th post......haha
I won't be here much, but it's good to have a thread in there. It'll clean the i9000 thread a bit and will help users to find the kernel for their own device.
Thanks for the help sixstringsg
Hi guys, just wondering if anyone is having issues losing signal after flashing a different kernel with the latest release of CM7?
is the latest miui release, 1.6.3, compatible with 10b?
cumanzor said:
Hi guys, just wondering if anyone is having issues losing signal after flashing a different kernel with the latest release of CM7?
Click to expand...
Click to collapse
I actually haven't tried. Try swapping out the modem.bin from whatever modem you want. Been using trusty ole JK4.
Sent from my SGH-I897 using XDA Premium App
where can i get the cpu scaling scripts agian?
SpaceKebab said:
is the latest miui release, 1.6.3, compatible with 10b?
Click to expand...
Click to collapse
No, you need to use v9.
A captivate version of 10 for miui would be special, but thank you for your great kernel
Sent from my GT-I9000 using XDA Premium App
Ignore post
sixstringsg said:
Actually, there isn't an miui kernel for captivate. Just i9000.
Sent from my CM7 powered captivate
Click to expand...
Click to collapse
V9 captivate works on miui.
Sent from my GT-I9000 using XDA Premium App
bam! what's on here? any points for super late reply?
sixstringsg said:
Actually, there isn't an miui kernel for captivate. Just i9000.
Sent from my CM7 powered captivate
Click to expand...
Click to collapse
ok. so i just noticed that Glitch isn't running this thread. weird. i also just noticed that you need to study a little bit of what Glitch is doing in order to run this thread properly so that you don't give out false information to others about his kernels. i'm running glitch V9 right now as i'm typing this to you. and i've run another version of his kernels also. SO yes there is a miui kernel for captivate. there are several. not trying to be rude at all but you may throw someone thats newer to flashing kernels off and not allow them to enjoy these kernels Glitch is putting out. the more people who use these kernels the more feedback= better kernels.
I'M A SUPPORTER OF BRINGING OFFICIAL ICS TO THE VIBRANT AND OTHER GALAXY S DEVICES!
> CLICK HERE FOR MORE INFORMATION <
Click to expand...
Click to collapse
CAPTIVATE 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)
officially declared new stable kernels will be up soon !
for now please go to the IRC channel (1st post to get the newest test-builds)
NEO 17 -r12 codename: Butterfly
http://forum.xda-developers.com/showpost.php?p=17339783&postcount=21
NEO 17 -r18 codename: Butterfly
http://forum.xda-developers.com/showpost.php?p=18268518&postcount=132
NEO 18-update1 codename: funky fish
NEO XX.1-update1 codename: mighty rhino
http://forum.xda-developers.com/showpost.php?p=19999998&postcount=192
ALL USERS MUST UPDATE (this fixes yet another potential data loss trigger)
2nd backup post (Changelogs)
Changelog list:
obsolete right now
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 Captivate 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)
@all:
Neo 17 r10 is available on IRC !
Changelog said:
NEO 17 (r10 - codename Butterfly) changelog [SGS/Telus, Captivate, Vibrant]
Changes (from r9 - 2nd testbuild):
• bumped RAM up to 348 MB (everything should still work, incl. Youtube HD recording)
• ported over smartass2 governor (super-smooth & battery-efficient, hopefully no issues anymore with getting stuck on high frequencies - unless due to system & broken apps)
• back to cm7 vanilla/stock yaffs2 driver - let's see if this fixes the discouraged random resets for few people (loss of contacts, apps gone, etc.)
Click to expand...
Click to collapse
Wow! New thread finally!
I'm testing with the Neo 17 R10 Kernel now.
Thanks!
Woohoo!
Sent from the frozen tundra known as Canada.
Spectacular. Gave it a shot from r7 and loving it since. Looking forward to future updates.
And about time for your own thread!
Sent from my I897 using Tapatalk
Thanks for the awesome kernels, they always work great, and I always look forward to the progression of this kernel. Thanks again for all your hard work, you are very talented.
Sent from my I897 using XDA App
I'm loving it as well, I don't oc much, maybe uv a little, and I do like the vc. Great work.
Sent from the frozen tundra known as Canada.
Thanks zach, r11 + smartassV2 is really super-smooth! You are doing an amazing job.
No problems so far, I got my last SOD on r9.
So on Neo 17 v11 what is set for governor(not showing in pimp)?? I got confused when reading the whole thing. Plus did you say it won't change from awake governor to sleep governor with the screen off? If so how do I make it so it does?? I don't see a screenstate scaling in root exploring under the right location. I have in the past but.can't now.
Sent from my I897 using XDA App
buresh.kevin said:
So on Neo 17 v11 what is set for governor(not showing in pimp)?? I got confused when reading the whole thing. Plus did you say it won't change from awake governor to sleep governor with the screen off? If so how do I make it so it does?? I don't see a screenstate scaling in root exploring under the right location. I have in the past but.can't now.
Sent from my I897 using XDA App
Click to expand...
Click to collapse
Uninstall Pimp My CPU.
Delete the Pimp My CPU folder in your SD Card.
Reflash the Neo 17 R11 Kernel and the V51 Script again.
Install back Pimp My CPU.
OK, you'll see the Governor and Scheduler which already been set by Neo 17 R11 Kernela and the V51 Script.
the new platypus 17r11 is superfast, my CAPPY felt great with it
thanks Zach
hope the color issue soon to be fix since i like to customize the color temp
Fate-Silver said:
Uninstall Pimp My CPU.
Delete the Pimp My CPU folder in your SD Card.
Reflash the Neo 17 R11 Kernel and the V51 Script again.
Install back Pimp My CPU.
OK, you'll see the Governor and Scheduler which already been set by Neo 17 R11 Kernela and the V51 Script.
Click to expand...
Click to collapse
Did you have this problem as well?? ha! I found the V51 Script, I think!
I tried to change awake governor but it's not showing in Pimp my Cpu. I rebooted, tried deleting & installing it again but no luck.
I edited the script with text editor from Root Explorer, put # infront of ondemandb, and took # from smartass2. Rebooted but pimp my cpu is showing ondemandb.
hi. can you flash this using the orange cwm that comes with cm7?
yuhenyo said:
hi. can you flash this using the orange cwm that comes with cm7?
Click to expand...
Click to collapse
Yes you can.
Sent from my I897 using Tapatalk
simple man said:
Yes you can.
Sent from my I897 using Tapatalk
Click to expand...
Click to collapse
awesome! can't wait to flash this. So is the download link in the other thread? I can't seem to find it on this one. or is it?
yuhenyo said:
awesome! can't wait to flash this. So is the download link in the other thread? I can't seem to find it on this one. or is it?
Click to expand...
Click to collapse
http://webchat.quakenet.org/
The instructions are in the O.P., but you'll need to login, download the file, extract the unpack_me.zip pick the kernel of your choice, download the kernel cleaning script 1st page this thread,flash it, then your kernel, then the screen state script.
Sent from my I897 using Tapatalk
DEVELOPMENT DISCONTINUED
Disclaimer:
You know the gig...I am not responsible for damaging your device or voiding your warranty. Play at your own risk!
_motley kernel:
Current version features:
OC support (overclock) - frequencies: 1.200, 1.400, 1.504, or 1.600Ghz (recommend 1.4 or 1.5GHz). Default clock speed is [email protected]
UV support (under-volting)
I/O schedulers: optimized deadline (default) and noop
Governors: optimized interactive, on demand, conservative, and performance
vfp, vfp3, vfpv3d16, thumb, thumbee, swp, fastmult, edsp, half
USB charging enabled
JRCU implemented - RCU for SMP with a single CPU garbage collector
Auto-group scheduling
Built in cifs, NTFS, Xbox controller, tun, PS3, joystick, mouse support
Encryption features CONFIG_DM_CRYPT, CONFIG_BLK_DEV_CRYPTOLOOP, and CONFIG_KEYS
Stock hardware/software is all working with no known issues (Camera, GPS, WiFi, sound, headphones, sensors, market, video/youtube etc.)
Prerequisites:
ROM must be based on the stock Galaxy Tab 8.9 with TouchWiz (stock and Overcome ROMs have been tested)
ROM must be rooted and have CWM installed.
Make sure you backup your boot.img so you can flash your stock kernel back. You should have a full CWM backup anyhow.
An app like SetCPU if you want to overclock(OC) or under volt (UV). I recommend only overclocking up to 1.4 or 1.5 GHz. Try 1.4 GHz first and see if it works for your tab.
Make sure you download the correct version for WiFi or 3G (3G only supported on Android 3.2).
Make sure you download the correct version for Android 3.1 or 3.2.
Android Honeycomb 3.2
Version v2d for Android HC 3.2
Add "autogroup" scheduling (for some background see: http://www.linuxfordevices.com)
Add support for LUKS and other file encryption utilities (CONFIG_BLK_DEV_CRYPTOLOOP=y and CONFIG_KEYS=y). Ext2 formatted loop devices should work now, but still no luck FAT12 8.3 volumes. Let me know how it works! (thanks ZeroPDA)
Misc merges\bug fixes from Nvidia repo (tegra\video\hdmi fixes, ext4 memory leak fix, interactive gov div\0 fix etc.)
v2d (7310 WiFi) View attachment motley_v2d.zip MD5 640af1d30eff11124f17b7fcb4c6201e
v2d (7300 3G) View attachment motley_v2d_3G.zip MD5 640af1d30eff11124f17b7fcb4c6201e
Version v2c for Android HC 3.2
WiFi only feature addition - added CONFIG_IP_ADVANCED_ROUTER=y to properly support Cisco VPN (VPNC Widget). This was not required for 3G as it already has this kernel feature. Thanks to questionmark for providing the info and testing the change for us.
UV bug fix - v2a introduced a UV issue where it was no longer subtracting the UV values even though they were set properly in sysfs by SetCPU etc. Thanks to Crashdown12 for reporting.
Important - I recommend removing the option to set UV on boot before installing this new version, just in case you were down to unstable voltages.
v2c (7310 WiFi) View attachment motley_v2c.zip MD5 cbfdee00b5ce514bef88e4230f7d0694
v2c (7300 3G) View attachment motley_v2c_3G.zip MD5 bce4881b2716f410b2903f96fe347271
Version v2b for Android HC 3.2
USB charging is now enabled like the GT10.1 (thanks pershoot, stefansaraev). See the following for usage: how-to (thanks dpakrr)
Performance: implemented JRCU, an RCU for SMP with a single CPU garbage collector so that each and every CPU doesn't periodically participate in RCU garbage collection. This is popular in the Android kernel space since dual CPUs have come about (thanks Joe Korty).
Performance: added optimized deadline i/o scheduler which is now the default since it is great for SSD (thanks morfic)
Added switch to turn off TouchWiz at the kernel level (not really relevant until someone tries to build a vanilla ROM)(thanks pershoot)
v2b (7310 WiFi) View attachment motley_v2b.zip MD5 3446574b2024897e41bad69f7c699aca
v2b (7300 3G) View attachment motley_v2b_3G.zip MD5 d299579a1de0d1469bfcb99ed6afc1d4
Version v2a for Android HC 3.2
Same features as v1i kernel, but now works for HC 3.2
Now a version for P7300 3G
v2a (7310 WiFi) View attachment motley_2a.zip MD5 59bfb8b8f213517676e06b6d69f35080
v2a (7300 3G) View attachment motley_2a_3G.zip- MD5 b5b6ab4f3dffe29dce5a83f32dd7eba6
Android Honeycomb 3.1
Version 1.0i changes (current for Android 3.1):
Governor default changed to OnDemand, but only so we can properly set back to the preferred interactive governor on boot using SetCPU and other tools (let me know!).
I/O schedulers: NOOP now the default (minor read/write improvements), CFQ still available, Deadline removed for now.
Starting voltages increased for 1.504 GHz and above due to some instability issues reported. I recommend you UV 25mV or so if you already achieved stability as it was increased by 50mV. Higher than 1.5GHz is still experimental and not recommended. I have been able to run at 1.6GHz for the first time in this build.
v1i - View attachment motley_v1i.zip - MD5 ea77e46967aa4c917e8dd8c429dca724 (current for Android 3.1)
Version 1.0h changes (beta 1):
Touchscreen lag fixed. Firmware downgrades prevented within Melfas touchscreen driver.
UV bug fix, no known issues.
Governor fixes, SetCPU seems to set properly on boot now (edit: still some issues setting on boot depending on SetCPU configuration)
Version 1.0g changes (alpha 2):
Overclock to 1.504GHz+ (only 1.5 is stable, over is experimental only)
UV (undervolt) support (experimental, still in testing)
NTFS and Xbox now built-in. No longer need to mess with loading modules.
Applied some upstream kernel patches.
Version 1.0c (alpha 1/first release):
Based on Samsung open source kernel from opensource.samsung.com
Overclock to 1.2GHz or 1.4GHz (a future version will likely be able to clock to 1.504Ghz)
Installation Instructions
Backup with CWM
Put the zip on your sdcard
Flash zip file from CWM
Install SetCPU and use to set governor to "interactive" and desired OC frequency (recommend 1.4 to start). The default governor has been set to On Demand on purpose even though it is not the recommended governor to use in SetCPU. Setting the recommended interactive governor will help SetCPU trigger the instructions to sysfs causing it to take hold. Sometimes it is finicky and a reboot can help once you have the interactive governor set with your desired frequency.
Optional: if you need or want to restore your original kernel, restore ONLY your boot.img from the CWM advanced recovery option.
Thanks go to:
pershoot for all his hard work on the 10.1 kernel. I used his kernel as a working guide and used his delivery method (Anykernel)
alterbridge86\Overcome for CWM.
Koush for the Anykernel delivery method.
Samsung for releasing the source like they should
Tiamat team, RichardTrip\roggin and NVidia for their open source git repositories.
All the testers!
Let me know if I forgot somebody!
Git repository:
https://github.com/motley-git
FAQ
Q: What is a kernel and why would I need it? How is it different from a ROM?
A: The kernel is the lower level of the operating system, or the engine so to speak. It is a bridge between applications and the actual data processing done at the hardware level. The Android OS utilizes a custom Linux kernel. The stock kernel provided by Samsung limits the CPU clock speed (i.e. CPU frequency) and other functionality that the upper level operating system can request (like mounting NTFS hard disks, undervolting, encrption, using certain joystick controllers, mounting network shares etc.).
A kernel is different from a custom ROM. A ROM is a customized version of the Android Honeycomb OS and will also come with a kernel. Most ROMs will come with the stock kernel, they should designate which kernel they use. In other words, most ROMs provide a customized version of the upper level of the operating system including base services and applications.
Q: What do I have to wipe before I flash?
A: For kernel only flashes, like this one, you don't have to wipe anything.
Q: What does the zip file do when I flash?
A: When the zip is applied in CWM, it does the following things using Koush's AnyKernel method:
Unpacks your boot.img from into a temp folder (into ramdisk and zImage components)
Replaces your zImage, i.e. the kernel binary
Updates the ramdisk default.prop (sets ro.secure=0 for adb root shell and removes init.p3.rc lines that set frequencies and governor during boot)
Repacks the new boot image and flashes back to /dev/block/mmcblk0p3
Updates two kernel modules in the stock location /lib/modules
Q: Will I lose any customizations to my ramdisk provided by a custom ROM?
A: No, your should not due to the use of the AnyKernel method described above.
Q: Will other overclocking apps besides SetCPU work OK?
A: Yes, they should work, but just keep in mind that not all apps are able to under-volt. I will typically be using SetCPU for all my testing, so keep this in mind if you have problems.
Q: Will overclocking use more battery?
A: Yes, higher voltages equals more current draw (I=VR). It will depend upon your setup and individual usage scenarios to how much runtime you will lose.
Using the interactive governor, your tablet will scale down to lower frequencies when the highest clock speed is not necessary. At the lower frequencies, the tablet will not use more power than it does stock.
Q: What OC frequencies are safe?
A: From research thus far, 1.5GHz is the top end for every day use stablity for most tablets. However, due factory tolerances 1.5GHz still may not be stable for everyone. You may need to use 1.4GHz or even 1.2GHz. Many choose to run 1.4GHz since it still gives a great performance bump over stock, but less heat is generated, and it will chew up a little less battery.
Q: I set my OC frequency to X, but I don't think it is working. How do I test to know that it is working?
A: For 1.4-1.5GHz using the interactive governor, you should be able to see a Linpack score between 70-87 depending on what else is running on the tablet.
The ad-free version of Linpack is better because the ads can lower your scores unless you hit test at the right time when the ad is already loaded. If you keep hitting test at 1.5Ghz, your consistent higher scores should be around 78-85.
Verify the clock speed by using Linpack scores
Verify in SetCPU that the different clock speeds are being used periodically, most particularly the highest clock speed.
It is kind of finicky sometimes until you get it set right and sometimes after a new version is installed it will get finicky. After you get it set right, then it stays put on reboot and you should have any issues from there. I am still wondering if there isn't something I can do about it to force it honor any changes SetCPU requests to sysfs no matter what. This is the reason why I eventually set the default governor to On Demand and then suggest that you configure it to be Interactive in SetCPU (the recommended governor). This seemed to help trigger the proper acceptance from SetCPU on boot. Pershoot (the 10.1 kernel guru) suggested that it might be falling to conservative at the default frequency like when it goes to sleep, but not coming back. However,when it goes to sleep and I turn it back on, it always goes back to my 1.5GHz just fine. And when it's set and happy, it never has this issue on boot either. Maybe a second boot is all that it takes, but I would sure like to pin it down and understand it better. Let me know if anyone has any ideas.
If your Linpack scores suggest OC is not working, I recommend that you do the following:
Uncheck the SetCPU setting to "set on boot" for OC and UV settings. Don't set this for boot until you are sure you are good to go with your clock speed and UV settings.
Upgrade to the latest kernel version for your tablet if you haven't already (Choose, HC 3.1 or HC 3.2, then 7300 3G or 7310 WiFi)
Boot up and use SetCPU to set your desired OC frequency AND then setp to use the "interactive" governor.
Verify your linpack scores to make sure they are higher than stock (~50-55). See above reference scores and notes about ads slowing down the scores.
Q: How do I setup under-volting (UV)? What values should I use for each frequency?
A: Not all tablets are created equal at the factory. What works on anothers tablet may not work on yours.
Uncheck the SetCPU setting to "set on boot" for UV settings. Don't set this for boot until you are sure you are good to go with your modified UV settings.
Once the clock speed is verified (see previous question), run some bench marks (Linpack, AnTuTu, and Quadrant are good) and do some multiple-tab browsing sessions to make sure your tablet is stable. Watch some vids or whatever you like to do, this is the key.
If you are stable, step down your voltage at the highest clock speed by -25mV. Repeat the benchmarks and usage scenarios. If it fails (locks the tab), hold down the power key until it reboots and step back up +10mV and repeat until it is stable.
Repeat the UV calibration for the next lower clock speed and so forth. I don't typically mess with anything below GHz since those are stock values.
Q: So, what OC and UV settings do you use?
A: I typically run @1.5GHz -50mV and leave the rest of the frequencies as-is. For my usage, I don't find the CPU spending a lot of time anywhere else besides 216, 312, 1000, and 1504. Every other frequency is typically less than 1% of time in state. If folks can UV further and keep it stable, that is great. I don't worry about battery too much since I am mostly around the house and don't mind charging every 2-3 days.
Q: I noticed that the stock tablet does charge using a normal PC USB port. The tab say discharging with a red x but it seems to be charging. So do I really need to use the usb charging script?
A: I grabbed this fix from the 10.1 kernel base. I was wondering the same thing when I went forward with the code change.
Here is what I know so far. The change in the kernel allows the tablet to properly report the charging state properly back to the OS. After the fix, the USB charging seems to be much faster, but it may just be the reporting mechanism. Before, it would take forever to trickle up 1%. Now it really seems be a viable charging source, but still slower than plugging in to the wall of course. I have not however done any tests to prove this, but I think the mod is definitely worthwhile. Samsung should have done it like this stock, but I think they did not want to deal with support calls to troubleshoot charging via USB as it is not as fast and reliable.
That said, the option is there and folks have a choice on whether to activate it or not. Others, please report back on your experience on this topic.
Any chance this would work on the 3g version?
Great! Can't wait to try it. Any reason it might not work with the overcome ROM?
EDIT: Just tried and it worked with Overcome 1.0.0. Noticeable improvement in landscape mode, buttery smooth in portrait.
Any chance we can undervolt the kernel?
Also, did you apply any optimizations (VFP3/FP/gcc-O etc.)
What is meant by "PS3" support?
KitF said:
What is meant by "PS3" support?
Click to expand...
Click to collapse
I assume it's support for the PS3 Dualshock 3 (which uses Bluetooth)
Hurrian said:
I assume it's support for the PS3 Dualshock 3 (which uses Bluetooth)
Click to expand...
Click to collapse
I highly doubt that. Maybe it supports it over USB.
+1 on this feature added to OC... I feel the stock ROM is too slow...
Hello mr. Motley!
awesome works, applied it to my 8.9" it works really neat both in 1.2 ghz and 1.4 ghz!
thumbs up from denmark!
---------- Post added at 12:52 PM ---------- Previous post was at 12:44 PM ----------
Hello!
haha my antutu benchmark (using overcome 1.2)
1ghz : 4900
1.2ghz: 5607
1.4ghz: 6590
woooom
---------- Post added at 01:24 PM ---------- Previous post was at 12:52 PM ----------
Hi,
at 1.4 ghz - the lockscreen seems to have some issues (it has a 10/15 sec freeze before unlocking)
+1 for the 3G version! Will this one work?
Also, +1 on the PS3 controller support. (Why wouldn't it be able to support Bluetooth? I figured it may be easier that way anyhow. Tell you what though, if it does work, I'm buying a PS3 controller! (I've never had the desire to own a PS3))
Jade Eyed Wolf said:
+1 for the 3G version! Will this one work?
Also, +1 on the PS3 controller support. (Why wouldn't it be able to support Bluetooth? I figured it may be easier that way anyhow. Tell you what though, if it does work, I'm buying a PS3 controller! (I've never had the desire to own a PS3))
Click to expand...
Click to collapse
Because ps3 uses a proprietary bluetooth protocol.
Android 3.1 has built in USB controller support, so ps3 controller should work over USB. If Samsung hasn't messed something up.
Def a long delay on wake up otherwise everything is running fine, thanks!
Def looking forward to a faster OC, would be nice to be able to test up to 1.7 like the Tiamat kernel. A GPU overclock option would be welcome too. Let me know if you need any testers.
Sixaxis app works fine on the 8.9, I use my controller via Bluetooth with my tab just fine. Guess it is good to know there is USB support, too.
alishankiti said:
Any chance this would work on the 3g version?
Click to expand...
Click to collapse
Sorry, but I don't think it has the right kernel options at the moment. Samsung has a separate source download for the GT-P7300 and I have not studied it to see if it is the same source. It may be possible to easily make it happen by using a different configdef to setup the kernel. We'll see about adding support in the future, however I don't have 3G (or even a 3G dongle) to give it a try so others would need to test it. Some of the 10.1 guys might be able to help determine whether this is a mountain or mole hill. If it is the latter, I am happy to give it a try at some point.
CanEpia said:
Great! Can't wait to try it. Any reason it might not work with the overcome ROM?
EDIT: Just tried and it worked with Overcome 1.0.0. Noticeable improvement in landscape mode, buttery smooth in portrait.
Click to expand...
Click to collapse
Thanks for the update, you may be the second person to run this kernel
Hurrian said:
Any chance we can undervolt the kernel?
Also, did you apply any optimizations (VFP3/FP/gcc-O etc.)
Click to expand...
Click to collapse
Yes, voltage control is definitely high on the list after all hardware and annoying glitches are addressed.
vfp and vfp3 are baked in already. I believe they were in the stock kernel already. As far as compiler optimization, I haven't done much playing with that. I tried to use the code sourcery toolchains, but I could never get the damn kernel to boot. I am currently using the Android NDK to compile. I even had to back off a version on these toolchains because it broke WiFi without any other coding changes. It's a very sensitive beast. If anyone has any known and proven compiler optimization for Tegra2 and ARM toolchains, I am happy to give it a try. I know that the toolchains are what do most of the magic for our CPU, so we would have to stick to whatever is supported in the toolchains.
KitF said:
What is meant by "PS3" support?
Click to expand...
Click to collapse
This is for supported the PlayStation 3 controller via USB (kernel option CONFIG_HID_SONY). Kernel option CONFIG_INPUT_JOYDEV is also built-in for supporting other generic joystick devices. I am not an avid gamer, so you guys will need to help out with the testing with this stuff.
All is well @1.4 on Overcome 1.2
Sent from my GT-P7310 using Tapatalk
randomb said:
Hello mr. Motley!
awesome works, applied it to my 8.9" it works really neat both in 1.2 ghz and 1.4 ghz!
thumbs up from denmark!
---------- Post added at 12:52 PM ---------- Previous post was at 12:44 PM ----------
Hello!
haha my antutu benchmark (using overcome 1.2)
1ghz : 4900
1.2ghz: 5607
1.4ghz: 6590
woooom
---------- Post added at 01:24 PM ---------- Previous post was at 12:52 PM ----------
Hi,
at 1.4 ghz - the lockscreen seems to have some issues (it has a 10/15 sec freeze before unlocking)
Click to expand...
Click to collapse
Thanks for testing from Denmark Good thing I posted it last night before bed!
Your lockscreen seems to be much worse than I am experiencing. I get the same 2-3 sec behavior no matter what my cpu speed is. Not sure this why this is different for you. Even if my lockscreen is turned "off", I still get the 3 sec delay on wake. I like a good sleep, but this is a bit more like a drunken coma.
poolguy said:
All is well @1.4 on Overcome 1.2
Sent from my GT-P7310 using Tapatalk
Click to expand...
Click to collapse
Good to hear poolguy, thanks.
Kernel is running nicely, as stated earlier it is about a 2-3 second wait time on the lock screen. The only issue I had is that the CPU was pinned at 1 ghz, this issue was solved by switching governors and then back to interactive. Now scaling nicely. Thanks for this.
Sent from my GT-P7310 using Tapatalk