yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] zacharias.maladroit:
Kernel

CM7 & MIUI only

NEO 09

before you ask for any ETAs:

The first rule of CyanogenMod [and this project]: DO NOT ASK FOR AN ETA!

Changelog (from NEO_08):

core features:

- writeback improvements - less lags

- wifi fixes & improvements

- voodoo color

- voodoo sound (upstream)

- docksound support

- updated to 2.6.35.13

- lots of additional enhanced security features (in kernel + init scripts)

- FPS cap raised for smoother operation + 65 FPS

- printk + android-logger disable for less overhead & better battery runtime

- nofail variants for filesystem initialization - less overhead

- SFB scheduler

- memcopy&memmove - optimized variants for more performance

- selection of several cpufreq governors (interactive, smartass, tweaked ondemand, tweaked conservative, interactiveX, SavagedZen)

- bigmem: 339 MB RAM

- optimized memory handling (via init scripts)

- several battery-runtime related improvements

- VFS + VM fixes & improvements - less lags & more stability

- OC up to 1.6 GHz (thanks to bilboa1, morifc

- SLUB slab allocator (more stable & efficient, SLQB leads to instabilities & other issues)

- BFS scheduler (still too unstable)

- performance flags

- compiled with 2011.03 toolchain for more stability, reliability and performance (significant !)

- some other performance related stuff

- touchkey timeout (no led-notifcation) | led-notification (2nd kernel)

- Juwe11's OOM killer settings

changelog:

- ondemand + conservative governor (screen: on: ondemand & off: conservative)

- some more battery savings & speed-ups

- better memory management [thanks to nikademus !]

- lots of other performance and battery consumption related fixes & improvements

NEW:

- raised the max gpu clock [thanks to existz]

- some gpu changes [thanks to morfic]

- gannet kernel module on request

- synced with upstream: DIDLE disabled and sleep of death (hopefully) fixed

- several improvements in readability & some new settings in the init scripts

- galaxysmtd [repo synced against ~#34] tested on #32, captivatemtd [-> #35] , vibrantmtd [-> #31]

testing/need feedback:

- stability / reboots [it uses some new optimization-flags so I need to know if those affect stability]

- any regressions with games, apps, etc. ? [none known so far]

Troubleshooting and other stuff:

other governors:

hopefully the explanations in S98screenstate_scaling should be detailed enough to let you change to a different governor

if not let me know and I'll see if I can come up with a package with different script-variations to replace the scripts in the kernel-package

Mirrors:

Mirror #1:

NEO_09/VIBRANT/

(thanks to Roland !)

Thanks to teamhacksung|cmsgsteam !

edit:

Note:

MIUI builds (with MIUI splash) are available NOW !

I hope everything went OK (with 8 kernels - making that 16 kernels in total :rolleyes:)

hopefully I haven't mixed up led-notifications or MIUI bootsplash :p
[Vibrant Android Development] lightninbug:
Thank you so much man!!!:D
[Vibrant Android Development] hur8111:
Thanks! downloading now :)
[Vibrant Android Development] speed145a:
I just tried neo 09 with miui 1.6.24 and the bluetooth is somewhat amiss... i was doing fine with neo 07 on miui 1.6.17.

i flashed miui 1.6.24 and it replaced the kernel with the miui one

neo 07 seems to put me into a boot loop with miui 1.6.24

let me know if you need more info and i'll try to get back to you, thanks.

EDIT: to clarify "amiss" it is difficult sometimes to get the bluetooth to turn on at all. when it does turn on it seems to have a hard time connecting to my earpiece. if it does connect, the audio doesn't properly route and i can hear the caller on the phone (not the bluetooth) and they can't hear me at all.
[Vibrant Android Development] droidfan77:
I installed Neo 9 on CM7 #32 a few hours ago and while charging my phone just suffered the sleep of death. Is there something I can do to help prevent this from happening in the future?
[Vibrant Android Development] jimmyhawk:
I've read that if your using an app such as set cpu or antutu cpu it will do that. If your not using an app of that sort then I'm not sure of the problem. I can say that I'm using neo 9 no led on cm7 #34 and have been charging and no sleep of death...yet anyways
[Vibrant Android Development] jay661972:
download neo 9, got fc on gallery and need to pull battery to turn off the phone. luckily, did back up this morning. using cm7 #34.
[Vibrant Android Development] d_phekt:
Just installed Neo9 over nightly #34 earlier today. Took my phone out of my pocket a little while ago and was stuck on CM7 bootanimation. I have no idea how long it was doing it since I hadn't used my phone in awhile. Anyone else suffer this?
[Vibrant Android Development] jimmyhawk:
Never got stuck but I did have 2 reboots earlier and I was in the middle of a call both times. But lots of other calls where it was fine, not sure why though
[Vibrant Android Development] locoarmo:
neo 9 with cm#33. I'm getting the reboots and got stuck on the bootscreen twice. When its running, it's awesome but somethings not quite right.
[Vibrant Android Development] Locksmith81:
I use the kernel cleaning script everytime before flashing new kernel. I do it and flash kernel...boot loop? Really do the steps again. Works for me everytime
[Vibrant Android Development] d_phekt:
I was just wondering if the fix mentioned here has been included into the latest kernel? It seems that many of us are still suffering from SOD even with Neo9.
[Vibrant Android Development] carlosmann22:
Well I've been running this pretty much since it was posted on nightly 34 and I don't have any real issues. Its rebooted randomly twice but one of them while I was testing overclocking to 1.6ghz.
[Vibrant Android Development] jimmyhawk:
Was charging overnight and sleep of death occured, luckily I had my back up alarm clock set as well...lol

Was using cm7 #34 and neo9 @ 1200 oc and ondemand governor and no additional o/c apps.
[Vibrant Android Development] TNK2005:
Can I make headset button workson miui with CM7-MIUI_VIBRANTMTD_20110625-01_platypus-revolutions-kernel_NEO_09-led-notif?
[Vibrant Android Development] Berney:
bluetooth can't work with NEO-09...[my ROM is MIUI-1.6.24]
[Vibrant Android Development] jereader:
neo 09 on CM7 #35 is the first of the platypus kernels that I have had any success with. All previous combinations of nightly and platypus resulted in bootloops and reboots when I connected the headset. One strange thing that I am seeing with this one though is that under the kernel module options in voodoo control plus it says "device or kernel version not supported." Voodoo sound and color are definitely working though, so I have to say that I'm pretty pleased with this kernel.
[Vibrant Android Development] Cesarp 24:
Hows battery life on 35?

Sent from My CM7 Monster
[Vibrant Android Development] Locksmith81:
You wont get a reply since its been up not too long. Best advice is to try it yourself and find out. Didn't you ask this question on the CM7 thread?
[Vibrant Android Development] Locksmith81:
I get reboots during some phone calls on CM7 #35. Anyone else? Confirm?
[Vibrant Android Development] jereader:
For those experiencing the sleep of death issues with this kernel. I may have found a simple solution. I was having this issue myself, so I set the minimum cpu speed to 200mhz, and I have not had an SOD for over an hour now. I realize that this may use a bit more battery than the 100mhz min, but it will allow me to have convenient access to my phone when I need i. At any rate, if i experience any more SOD's I will post here again.
[Vibrant Android Development] cal4877:
Hey zach I love your work man but I have a quick question?. Can you make this work on any gb rom? Do you think is possible?
[Vibrant Android Development] notverycreative:
CM7/MIUI uses a heavily modified kernel that has little in common with the Samsung kernels, I think. Seeing as he is busy with studies, though, a new version of what we have is enough of a treat :)
[Vibrant Android Development] nickmcminn60:
NEO 9 CM7 version working perfect on my ENERGY 6.5 rom

Thanks Zack
[Vibrant Android Development] speed145a:
Have you used bluetooth?
[Vibrant Android Development] bloodhawk:
Anybody else facing call issues? I know it is a common problem, but wanna know if it is really frequent with NEO 9?
[Vibrant Android Development] zacharias.maladroit:
Kernel

CM7 & MIUI only

NEO 10

before you ask for any ETAs:

The first rule of CyanogenMod [and this project]: DO NOT ASK FOR AN ETA!

Changelog (from NEO_09):

core features:

- writeback improvements - less lags

- wifi fixes & improvements

- voodoo color

- voodoo sound (upstream)

- docksound support

- updated to 2.6.35.13

- lots of additional enhanced security features (in kernel + init scripts)

- FPS cap raised for smoother operation + 65 FPS

- printk + android-logger disable for less overhead & better battery runtime

- nofail variants for filesystem initialization - less overhead

- SFB scheduler

- memcopy&memmove - optimized variants for more performance

- selection of several cpufreq governors (interactive, smartass, tweaked ondemand, tweaked conservative, interactiveX, SavagedZen)

- bigmem: 339 MB RAM

- optimized memory handling (via init scripts)

- several battery-runtime related improvements

- VFS + VM fixes & improvements - less lags & more stability

- OC up to 1.6 GHz (thanks to bilboa1, morifc

- SLUB slab allocator (more stable & efficient, SLQB leads to instabilities & other issues)

- BFS scheduler (still too unstable)

- performance flags

- compiled with 2011.03 toolchain for more stability, reliability and performance (significant !)

- some other performance related stuff

- touchkey timeout (no led-notifcation) | led-notification (2nd kernel)

- Juwe11's OOM killer settings

changelog:

- [probably] some more battery savings & speed-ups

- (complete ?) update/backport of the updated pl330 dma driver from samsung GB source [(probably) more performance, less power consumption]

- shorter kernel-package name on user demand (due to readability issues in CWM recovery)

NEW:

- bluetooth HID driver port from Samsung GB source (how to use this functionality ? probably less battery consumption - the more correct/complete drivers included - the more stuff can be sent to powersave)

- synced with upstream: 7.1.0-RC1 / nightly #40 (SGS numbering scheme)

- upstream additions: Hack a mute/unmute for Vibrant

- upstream: another variant of sleep/hang of death (probably also resolved)

- wifi + data networking issues resolved

- galaxysmtd [repo synced against ~#40 / 7.1.0 RC1] tested on 7.1.0-RC1, captivatemtd [-> #41] , vibrantmtd [-> #37]

testing/need feedback:

- stability / reboots [it uses some new optimization-flags so I need to know if those affect stability]

- any regressions with games, apps, etc. ? [none known so far]

- battery runtime

Troubleshooting and other stuff:

other governors:

hopefully the explanations in S98screenstate_scaling should be detailed enough to let you change to a different governor

if not let me know and I'll see if I can come up with a package with different script-variations to replace the scripts in the kernel-package

Mirrors:

Mirror #1:

NEO_10/VIBRANT/

(thanks to Roland !)

Thanks to teamhacksung|cmsgsteam !

edit:

Market issues ?

try replacing the included S98system_tweak script in the kernel-package with the one in the attached zip-file
[Vibrant Android Development] d_phekt:
You sir are the ****! Thanks for all the hard work. Love these kernels.
[Vibrant Android Development] TR88:
I'll wait and see if anyone has the same issues as they did in 9 before I jump the gun...
[Vibrant Android Development] zacharias.maladroit:
Hi d_phekt,

thanks !

glad you like it :)

what issues exactly ?

the mentioned call issues ?

it's already :)
[Vibrant Android Development] granduke:
Thanks for continuing to find time to support us.
[Vibrant Android Development] lightninbug:
Does the

"Hack a mute/unmute vibrant "

fix the mute/unmute issue where incoming calls would be hard for caller to hear you?
[Vibrant Android Development] cal4877:
Hey boss is it too much to ask if you can make a kernel that would work on any jvp rom?
[Vibrant Android Development] zacharias.maladroit:
sure :)

glad you like it

that one can be viewed as feature complete

since there are currently no other things to add from the samsung source or features (except maybe zram but that was unstable last time I tested)

since compiling, checking and uploading that whole stuff takes significant amounts of time I'll reduce the rate of kernels releases from now on (I simply need the time in other parts of my life :rolleyes:)

it's rather related to audio-recording if I read it correctly:

yeah - unfortunately :(

there's no official GB source for the vibrant available from samsung

(probably the reason: samsung charging money from the network operators for updates and so they'll end up in refusing to pay and samsung doesn't update the phones + source)

edit:

The Samsung Secret - Why U.S. Galaxy S Phones run Android 2.1 Still (in this case rather 2.2 than 2.1)

edit:

this means that the source would need to be ported to the vibrant,

besides that the kernels from samsung only work with their proprietary GB bootloaders

which might be a must to let it function correctly (e.g. for deep idle standby/powersaving mode a gingerbread bootloader is needed) - but unfortunately that is not the case

and I'm sure the SGS bootloaders won't work on vibrant phones, flashing those on the vibrant might render them useless up to the case of bricking them

I don't have any vibrant and I'm also not that experienced (yet) to do this big task (a group of experienced devs would be better suited), besides that I don't have that time and/or am not wiling to sacrifice that much

sorry ! :(
[Vibrant Android Development] jrod33084:
Did I miss something or is BLN not supported in Neo 10? I flashed and now its not working
[Vibrant Android Development] geoffcorey:
click the mirror link, and look under the led-notif directory, that is where the led-notif kernel resides. ;)
[Vibrant Android Development] jrod33084:
Ah ok thanks man didn't even notice that
[Vibrant Android Development] darkness122:
jw, once ive flashed the kernel, how do i enable the led notifications?

i tried installing bln but it keeps saying im on an un supported bln kernel.
[Vibrant Android Development] speed145a:
Thank You so much for the NEO 10 kernel release!

It's silky smooth and the bluetooth issues are resolved.

I've got this thing OC'd and UV'd heavily and it's stable so far. I love it
[Vibrant Android Development] speed145a:
it should "just work" no BLN app needed
[Vibrant Android Development] geoffcorey:
This isn't bln, it's led notification, a different type of bln implementation. And if you've flashed the led-notif kernel, then you're set (unless you've changed any of the led settings in the cm settings menu).
[Vibrant Android Development] d_phekt:
Any reports of SOD or random reboots yet? Kind of hanging in there before I try it this time.
[Vibrant Android Development] bloodhawk:
Just flashed NEO10. Working great!
[Vibrant Android Development] djjeesh:
+1 to this. Got this issue all the time on MIUI. Went to another ROM because of this.
[Vibrant Android Development] geoffcorey:
It's not kernel related, it's framework and ril related (which btw, Samsung wont ever release source for and never have to, and are partially legally obligated not to). So it's going to take a lot of trial and error to fix, and will take even longer until a dedicated vibrant dev steps up to take the cm reins.
[Vibrant Android Development] Cesarp 24:
I thought I read in the changelogs that we could now choose different governors I'm stuck on ondemand. Neo 10 is good so far ill check back in tomorrow.

Sent from My CM7 Monster
[Vibrant Android Development] Cesarp 24:
Sod!

Sent from My CM7 Monster
[Vibrant Android Development] bloodhawk:
I last night went to Stock JFD, then flashed Initial CM7, and then flashed to the latest MIUI. The issue vanished for me. Im on NEO10 btw.
[Vibrant Android Development] geoffcorey:
you need to edit the S98_screen_scaling script in /system/etc/init.d/ and change the screen-on and screen0off governors. (and possibly the op where it explains how to change the governor)
[Vibrant Android Development] RaptorFB:
I've getting an odd bug with this kernel for the past three versions. After flashing with the cleaning script first, I will randomly get something similar to the sleep of death. The screen will suddenly turn on while my phone is just sitting on my desk and "reboot", showing the circular CM7 boot animation, except extremely dim and with the colors almost entirely drained. From here the device never exits the animation unless I pull the battery. Upon reboot this way, it is as if nothing ever happened. No changes to OC/UV. I use this kernel purely for the voodoo addons. Currently running 7.1.0-RC1 with NEO10 no led notifications.

This does not happen on stock kernel.
[Vibrant Android Development] zacharias.maladroit:
oh - you mean

you haven't "experienced" this with the stock kernel yet

I've seen this in the past but very rarely ;)

it seems to be a sort of soft-reboot where only the system and not the kernel reboot

from what I saw ...
[Vibrant Android Development] RaptorFB:
Well, if you say so. I had the best combination with nightly #23 and neo7 actually. Any idea on the criteria for reproducing this problem? I use my phone as the morning alarm, but there's always a good old fashioned mechanical alarm clock...
[Vibrant Android Development] fatboy547:
I have rc 1 and neo 10. I had 2 random reboots can someone help or if someone knows how to prevent this from happening it would help alot thx ahead of time
[Vibrant Android Development] Locksmith81:
I had the same issue. Flash the kernel cleaning script then flash Neo10 again. See if that helps. Any time I get boot loops or soft bricks I always due the steps I stated
[Vibrant Android Development] geoffcorey:
Hmmm... on Neo 7, I'm running into an issue I saw reported in the glitch thread as well, a little bit after Neo 7 was posted. After running a game, the phone wont scale back down past 800 MHz, so it eats battery.

Also, I'm kinda afraid to upgrade to Neo 10 with the latest nightly as I've heard about the sod issues.
[Vibrant Android Development] Locksmith81:
Running RC1 on Neo10....u will like the speed and stability
[Vibrant Android Development] granduke:
The kernel cleaning script...Do I need to back up or does this not touch my settings and data?
[Vibrant Android Development] jrod33084:
It does nothing like that. Does what it says. Just may take a lil longer to reboot cuz it wipes dalvik cache
[Vibrant Android Development] uurrnn:
Installed 10led on miui, but I'm not getting any led action. I used the script, but it's old (not sure if there's a new version)
[Vibrant Android Development] speed145a:
I'm having the same problem. I tried the led version of the cm and miui kernels and neither of them work.

I can see an occasional hint that it was trying to light the led but it doesn't work as it did on previous versions...
[Vibrant Android Development] bdubs4200:
All my apps are stuck in landscape ...?? Flashed script cleaner then Neo 10 . Still landscape?? Am I missing a new setting? I just updated to n39 ...
[Vibrant Android Development] bdubs4200:
EDIT: I feel a fool, 0 degree rotation :-P begin with the insults I deserve ... hahaha
[Vibrant Android Development] fatboy547:
Why is it when I oc every 2 hrs or so my fone soft bricks? And I wud need to battery pull? When I don't oc fone runs fine. I use setcpu and set it at 1300 max and 200 min. Plz help
[Vibrant Android Development] Locksmith81:
Don't use SETCPU I use the CPU settings under CM settings - performance

Setcpu may be the culprit. See if that helps.
[Vibrant Android Development] bdubs4200:
Idk if this is Neo 10 or nightly 39, both are fresh out of the oven on my vibe, but I keep getting "unexpected error" notifs and when I clear, it pops right back up...?

Sent from a sgs-V, running gingerbread
[Vibrant Android Development] fatboy547:
Thx! Switched to pimp my cpu. Seems to be better. Well update on testings. Thx so much
[Vibrant Android Development] zacharias.maladroit:
This will be the last kernel for some time since I need to take care of personal things

I will still continue development on the Talon/Platypus Kernels in the background but will

keep a "small footprint" on XDA and phone-related stuff

All what you post will be read but I most likely will only answer what not already has been asked and e.g. some troubleshooting, etc.

Thanks for your understanding
[Vibrant Android Development] apollo15rover:
We'll wait!
[Vibrant Android Development] geoffcorey:
zacharias.maladroit: when you say "this will be my last kernel for a while", do you mean neo 10, or one that you are currently cooking up?
[Vibrant Android Development] zacharias.maladroit:
neo 10

I'm looking for some improvement for the kernel once in a while

so I'm sort of always cooking ;)
[Vibrant Android Development] }{Alienz}{:
Can you produce a version of this kernel which does NOT have Voodoo Color and uses the I9000 drivers instead of the Nexus S.

I know Glitch has a voodoo color and non-voodoo color and for the Vibrant, the non-voodoo color is MUCH MUCH prettier. Something noticable I can't do with this is set Voodoo color such that color maps aren't compressed if you will. For some reason, no matter what the settings, grays on moving live wallpapers are ALWAYS pixelated (look around the edges of live wallpapers which end in a black background-> Ice Galaxy, Flurry and you will see it). It looks rather terrible.
[Vibrant Android Development] nickmcminn60:
Thank's for neo 10....best so far...many thanks
[Vibrant Android Development] }{Alienz}{:
nightly 40, neo 10. Woke up and phone had the bug which nightly 40 says it fixed: namely, I could not wake the phone up with a power button. Pressing the capacitive buttons made them lit up for a second and then turn back off. I could not even restart the phone from the power button. Had to do a battery pull. :(

Can you sync the kernel with the latest nightly fix for that because battery life was almost fixed with it and I like neo 10.
[Vibrant Android Development] konigswagger:
having a nightmare with neo10 >_< when it works, it's great, but when it doesn't (a lot of the times), my phone is simply unusable (random reboots, boot loops, etc) and I have to do a battery pull.

anyone know if one of the neo kernels are compatible with the cm7 nightlies without issues?
[Vibrant Android Development] speed145a:
I found the problem on my phone at least and now have functioning LED notification.

I had to go into the settings for MMS and toggle "Screen-wake" off. Apparently the screen wake was conflicting with the LED notification.

Hope that helps someone :)
[Vibrant Android Development] jereader:
Neo 10 and nightly 40 are slick as dog snot for me so far. No SOD's, no random reboots, no problems to speak of at all so far.
[Vibrant Android Development] }{Alienz}{:
The Glitch kernel works good with nightly 40. No issue where screen won't turn on requiring battery pull.
[Vibrant Android Development] bdubs4200:
Sorry Zach, this is your thread, but guys I'm not finding the "Glitch kernel"... is it private

Sent from a sgs-V, running gingerbread
[Vibrant Android Development] zacharias.maladroit:
you need to search further in the forum ;)

[Kernel][CM7][Link] Glitch [6/17]
[Vibrant Android Development] zacharias.maladroit:
this kernel is for you and all the others that need logcat + printk:

it's a slightly improved NEO_10 kernel

with

- logcat+ printk enabled

- a scheduler fix

- swaptoken patch from CK (we don't have swap right now - so probably no effect)

- updated background aging patch for no-swap systems

- enabled network congestion (QoS) stuff

- correctly set vfp

- default scheduler is conservative + conservative