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

CM7 & MIUI only

NEO 16 codename: Beast

before you ask for any ETAs:

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

Characteristics:

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

- Juwe11's OOM killer settings use my kernel scripts & uncomment the section or use his script directly

changelog:

NEO 16 to NEO 16 codename Beast:

- led-notifications +/-

- gcc 4.6 toolchain

- back to optimization flags from NEO 15

- ext4 data safety & performance related changes (/data partition) - less data loss risk

- v(r) i/o scheduler

- simple i/o scheduler

- and others I forgot

NEO 15 to NEO 16:

- BLN [broken]

- wifi linux 3.0 / 2.6.38 port from nikademus (fugumod cm7 kernel)

- s5p (platform of our phone) - specific power-management improvements

- network security improvements

- more general fixes

- battery-runtime related timer improvements

- probably some speedups with sdcard access + better sdcard power management

- interactive, smartass, ondemand, conservative governor tweaks & improvements

- and others I forgot

NEO 09 redux v5 to NEO 15:

- lots of power management improvements

- sampling down factor support for ondemand governor

- "unbalanced irq" fix for sdhci regulator support (fixing up suspend-support for sdcard)

- reverted lcd,adc,ram undervolt (might not be good for the hardware -> warmer hardware)

- wm8994 sound improvements

- very low latency settings for scheduler (reverted in NEO 16 and set to optimized upstream settings, might break less stuff)

- out of memory handling (OOM) rewrite

- LMK (low memory killer) optimizations

==> improved memory & app handling, more smoothness and reliable operation

- general fixes

- and others I forgot

- galaxysmtd [repo synced against ~#81], captivatemtd [-> #81] , vibrantmtd [-> #78]

Kernel in the next post: (Link below)

(with WIFI fix)

http://xdaforums.com/showpost.php?p=16562023&postcount=390
[Vibrant Android Development] apollo15rover:
... everyone has one and they all stink..

hey.. I resemble that remark!!!
[Vibrant Android Development] hitman818:
Seriously. I dont think people with an i9000 will come to a vibrant forum to find i9000 modems.
[Vibrant Android Development] zacharias.maladroit:
"Quorra r10-rebirth" kernel (for MIUI and CM7 nightlies with

old RIL

)

kernel with old RIL applies to:

SGS: < #12

CAPTIVATE: < #14

VIBRANT: < #9

quorra_r10-rebirth/

<--

- SGS

- Captivate

- Vibrant

kernel available

based on Quorra r10

Changelog from Quorra r10:

- disabled PMEM

- s3cfb: fix for lock/unlock problem (radio + data already working without but this helps again lagginess before lock + unlock)

- bluetooth fixes (l2cap bt_power)

- [upstream] gpio fixes + cleanup

- working iptables & bluetooth stuff

- 332 MB RAM
[Vibrant Android Development] hitman818:
Are you going to make one for the update that was posted yesterday.
[Vibrant Android Development] jrafael:
Running great on Miui 1.5.13
[Vibrant Android Development] zacharias.maladroit:
Hi hitman818,

hi @all:

sorry guys I won't be involved with anything kernel, CM7 or MIUI-related at least until July

due to personal reasons + study

each time I shortly wanted to build a new release-kernel there were some trouble I ran into (the kernel wouldn't work as I had planned [e.g. missing features, not as smooth, stable etc.] - yeah I'm a perfectionist :rolleyes: )

and so of the planned MINUTES I wanted to spend became HOURS and this happened several times in the close past

I simply don't have the time for those HOURS spent & lost on this

since I need the time mainly for my studies and therefore I (temporarily ?) have migrated to hunky-dory stock ROM

I'd rather push performance & battery consumption of the kernel & ROM to newer heights (performance) and lows (battery consumption) & work closely with teamhacksung but I'm no hardcore hacker (and as experienced as coolya, codeworkx, atinm and the rest of the crew) so it simply would take significant amounts of time for me to do this

so I had to set priorities

Thanks for your understanding, support

and thanks for flying with Platypus Kernels :)
[Vibrant Android Development] notverycreative:
Thanks for all you've done and good luck!
[Vibrant Android Development] apollo15rover:
July's not too far away.. hurry back :)
[Vibrant Android Development] jrafael:
Good luck.

These are my uv settings
[Vibrant Android Development] nateskates:
Im reporting that Neo-04 is still getting reboots during calls.
[Vibrant Android Development] nickmcminn60:
Did you not see this, I think hes done for a while.?

hi @all:

sorry guys I won't be involved with anything kernel, CM7 or MIUI-related at least until July

due to personal reasons + study

each time I shortly wanted to build a new release-kernel there were some trouble I ran into (the kernel wouldn't work as I had planned [e.g. missing features, not as smooth, stable etc.] - yeah I'm a perfectionist )

and so of the planned MINUTES I wanted to spend became HOURS and this happened several times in the close past

I simply don't have the time for those HOURS spent & lost on this

since I need the time mainly for my studies and therefore I (temporarily ?) have migrated to hunky-dory stock ROM

I'd rather push performance & battery consumption of the kernel & ROM to newer heights (performance) and lows (battery consumption) & work closely with teamhacksung but I'm no hardcore hacker (and as experienced as coolya, codeworkx, atinm and the rest of the crew) so it simply would take significant amounts of time for me to do this

so I had to set priorities

Thanks for your understanding, support
[Vibrant Android Development] cashyftw:
He made a kernel on the i9000 thread about an hour ago.

Sent from my SGH-T959
[Vibrant Android Development] nickmcminn60:
Good glad to see he couldnt stay away lol!
[Vibrant Android Development] zacharias.maladroit:
:)

yeah - but I'm back to Samsung Gingerbread since I finally found what I wanted:

a kernel which is fast, has support for zram and can be modified (sources available in a git repo: short: Talon :) )
[Vibrant Android Development] zacharias.maladroit:
NEO 06

characteristics:

- conservative governor (screen: on & off) [you want a different governor ? - edit the 90screenstate_scaling script] see: Howto

- touchkey timeout (no led-notifcation) / led-notification [different kernels]

- some more battery savings & speed-ups

- OC up to 1.6 GHz (but it seems the power-saving measures don't let it scale up performance correctly - so max frequency recommended is 1.4 GHz)

- 339 MB (that's nearly 340 MB of RAM !)

testing/need feedback:

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

- smoothness of HD recording & playback [this kernel might have some surprises ^^]

- mic recording / video-recording + sound

- battery runtime [for me it was there for 7-8 hours in Airplane Mode (while I slept) and no battery drain - looks pretty similar to stock Gingerbread =) ]

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

so it is only compatible with BN #15 + #16 [SGS numbering scheme] (inofficial official nightlys)

but should also work with official #13 + #15 nightlies

I'm back on Stock Gingerbread (from Samsung) with a heavily forked & modified Talon-Kernel - everything what I need right now (FM Radio, and other stuff) works - perhaps after / in July I'll migrated back to CM7

I hope that codeworkx, atinm and the other dev soon-ish are able to re-route the FM Radio output so that we can adjust the volume

currently it only has one level: LOUD

and it only works with the Samsung (or other) headphones with 3 connections

and the reception isn't really optimal

the repo was synced yesterday (Thursday 2nd of June) so the kernel includes the init & other files state of that date

kernel with led-notifications is up

now I hope you got what you wanted :p
[Vibrant Android Development] lightninbug:
Will this work on latest MIUI?
[Vibrant Android Development] zacharias.maladroit:
new nightlies == new RIL

MIUI doesn't contain new RIL changes

so: NO - unfortunately not
[Vibrant Android Development] apollo15rover:
Running well.. your best yet!!
[Vibrant Android Development] notverycreative:
Oh wow, this thing downright flies! You're the best :D
[Vibrant Android Development] jonathanhuerta4:
I think I found true love... not really but DAMN my phone is flying. Best work by far, wish you the best in the work that is in your way. :)
[Vibrant Android Development] KWKSLVR:
Maybe I missed the answer? I assume Neo 16 requires Gingerbread Bootloaders? I flashed Neo 15 and lost my radio and a few other things (still on Froyo BL's). Neo 16 sounds promising!
[Vibrant Android Development] zacharias.maladroit:
it's backwards compatible

so you can stay on Froyo bootloaders

but Gingerbread bootloaders are recommended

if you lost radio - try reflashing it

hope you had a backup
[Vibrant Android Development] KWKSLVR:
I just restored by Nandroid. I dove head first into CM7 and all of these test kernels just this week for the first time so it's my own demise to not have fully read everything (and there's a LOT out there). I'll search modems next, I've just always rocked the KA7 that is in the nightlies. Shoot, I'm still on nightly #74.

Neo 15 also axed my camera and a few other things. However, I downloaded it in the middle of nowhere on GPRS while updating some market apps so it might have been a bad download. ;)

Thank you for the information, and your hard work on this project. I hope I haven't spammed your thread.
[Vibrant Android Development] Jasonhunterx:
I'm having really bad reboot problem I leave my phone sitting there an it rebooted by it self an watching video then locking screen makes it reboot also
[Vibrant Android Development] Bluejay913:
I flashed Neo 15 over trigger redux 0806a and I've never put on gb bootloaders. Sounds like a bad flash or download. Its been working for me since yesterday with no problems
[Vibrant Android Development] KWKSLVR:
It must have been. I just flashed Neo 16 with no problems so I guess we'll see how it looks over the next several days. No UV for now. It's very snappy and looking at System Panel, I can already tell that it has better CPU management then anything else I've tried.
[Vibrant Android Development] ChoctawT:
My ffc is messed up after flashing neo 16 anybody else experience that?
[Vibrant Android Development] lookitzjohnny:
i am also, had same issue in neo 15, but if you want to use ffc neo 9 redux doesnt have this problem
[Vibrant Android Development] Bluejay913:
Been running neo 16 w/ led for a few hours and bln has been working flawlessly. Also, this seems to be very responsive and quick.. thanks for this
[Vibrant Android Development] zacharias.maladroit:
Kernel

CM7 & MIUI only

NEO 16 codename: Beast - r2 (maintenance release)

before you ask for any ETAs:

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

changelog:

NEO 16 codename Beast - to - NEO 16 codename Beast -r2:

- WIFI Problem with Channels 12, 13, 14 fixed - now it should work

- galaxysmtd [repo synced against ~#81], captivatemtd [-> #81] , vibrantmtd [-> #78]

attached below
[Vibrant Android Development] Jasonhunterx:
I hope 16R2 doesn't give me reboots
[Vibrant Android Development] gamikzone:
im trying it havent got any so far i was on 9 v5 before
[Vibrant Android Development] ChoctawT:
Can me not having a gingerbread bootloader ,be the reason why the ffc is messed up?
[Vibrant Android Development] roffee:
how to set touchkey backlighting timeout? i like neo09. neo16 is longer
[Vibrant Android Development] Jasonhunterx:
Had ui reboots it go to boot up screen then starts backup
[Vibrant Android Development] hurtz777:
No issues so far with Neo16R2. Screen scrolling is smooth and crisp and it makes CM7 fly at 1.2ghz with very little battery drain using Nightly #79. Great job Zach!
[Vibrant Android Development] d_phekt:
Does the keyboard still pop up during calls when OC'ing on Neo16?
[Vibrant Android Development] KWKSLVR:
Not sure if there's any point to posting this, but I'm a data collecting dork. These are the results my first battery cycle on Neo 16.

*No OC

*UV:

100Mhz -100mV

200Mhz -75mV

400Mhz -50mV

800Mhz -25mV

1000Mhz -25mV

Governors: Stock Kernel Settings

Scheduler: Stock Kernel Settings (noop)

Non-GB Bootloaders

This was about 50/50 3G/Edge. I also have what has to be a tired battery (it's the 14 month old original). The only thing I noticed is that it takes it a while to sleep once the screen goes off. Clearly, AngryGPS was going batty for some reason. I ended up freezing it fairly early on in the battery cycle (at about 80% left or so). You can tell from my Screen On time that I didn't use it all THAT much today. No WiFi/GPS/BT at all other than about 2 minutes with the GPS on...come to think of it, I wonder if turning on the GPS for that short amount of time attributed to the phone not wanting to sleep.
[Vibrant Android Development] roffee:
flash neo16 on NEO 09-redux_V5， and then everything are crash...... like lost contact, desktop setting, and many FC

Reflashed. ok
[Vibrant Android Development] hurtz777:
dphect,

I haven't had the keyboard pop up when overclocked to 1.2ghz like I did in earlier Neos.
[Vibrant Android Development] nedlog:
Flashed V16R2 over Glitch after doing the kernel script cleaner. First time rebooting phone got stuck on splash screen; held down power button and rebooted. Everything worked great until I rebooted again, then my radio wouldn't load; re-flashed KB5 and everything has been smooth ever since. I'll report back with any issues; I did notice two of my apps had to reinstall for some odd reason but they work fine now. Thanks for the hard work!! :D
[Vibrant Android Development] Abu-7abash:
New record? Great work platypus, awesome kernel!
[Vibrant Android Development] zacharias.maladroit:
sorry - I don't get it :p

the massive drain ?

or

you overclocked it massively and it is running longer than ever ?

Thanks anyway ! :)

edit:

what do you do with your phone ? most of the time reading stuff ?

59% is a lot ! O.o
[Vibrant Android Development] T.C.P:
This kernel is the ****z 26 hours :)

Sent from a phone with android 2.3.5
[Vibrant Android Development] KWKSLVR:
So what the heck is going on with my drain? This is mostly over night. Angry GPS was draining the crap out of my system. So I froze it and rebooted. Now, last night, Google Maps started it too. It refuses to sleep.

Edit: this is V16r2, no UV.
[Vibrant Android Development] KWKSLVR:
A couple more.
[Vibrant Android Development] KWKSLVR:
Hrm, I was kind of thinking his was outstanding, especially looking at that screen on time. Compare where I'm at so far in the cycle with screen on time. Don't get me wrong, it's a HUGE improvement, but I'm still not getting what most people seem to get. I definitely have some weird things going on. I may flash the new nightly and redo everything.

Edit: So System Panel shows Google Maps acting normal. What the heck! LOL

Also, I tried out the KA5 modem on this round. It sucked up a lot of battery as well over KA7.
[Vibrant Android Development] asatnik11:
V16 r2 with moderate UV and 1.3ghz overclock with 17% battery remaining after 17hr 43min.....best ever on CM7 on the vibrant for me!
[Vibrant Android Development] karimsaud21:
After flashing the kernel i am having problems booting into recovery.

When i tell my phone to reboot it turns off and goes to a black screen and staying that way (even though my phone is charging which should trigger it turn on) unless i pull the battery.

When i put the battery back in it will proceed as if nothing happend and enter recovery mode.
[Vibrant Android Development] t1h5ta3:
so, im guessing you use lattitude, and leave background sync on overnight?

what your seeing realy isnt that bad... not great, but not bad since every thing is syncing all night, lattitude's trying to get a fix, and you have a non functional gps.

the other thing to do is look at actual voltages not just %, esp if you havent cycled your bat several times.

100% is around 4.2v, 0% is kernel dependent and varries from 3v-3.5v depending on who's your on. ( yet another reason to calibrate your battery stats..)
[Vibrant Android Development] KWKSLVR:
I calibrated the battery right out of the gate, which is something I normally don't do (I flash at 100%) but since it's CM7, I decided it would be best to do so. My battery never quite gets to 4.2v, but really, I think that's expected. In all reality, 4195mV probably is completely full. I ran another test last night. Now, I did swap to KB1 because KA5 is just abysmal on this setup for me. It drained my battery from 96% to 60% after 1 hour in the gym streaming Tune In on 3G (and this was at full signal strength) :eek:.

I also solved a good portion of my sleep issues by going into settings > applications > development > stop app via long-press (checked it). I also managed to forget to turn stupid 3G off last night (I normally sleep on edge) but you can see how the phone actually slept most of the time for once. I went ahead and ordered a couple of OEM batteries so I'll see how it does with a battery that hasn't had ooooooh, probably 750 cycles over the past 14 months, along with being stuck plugged into a car charger a TON. I also didn't have any rogue apps or processes go wild.

It's getting better, but it's FAR from 20+ hours. The only way I think I could squeeze 20 hours out of this thing would be screen off the entire time in airplane mode. Also, no UV/OC.
[Vibrant Android Development] vibey101:
Is there a no voodoo version of this kernel?
[Vibrant Android Development] gamikzone:
i dont think so
[Vibrant Android Development] Locksmith81:
Is v2 BLN supported? I have the app installed and no prompt for kernel not supported but no light for keys for notification.

from the amazing Jets Bread
[Vibrant Android Development] hurtz777:
It will be interesting to see if battery life gets better with NEO16 R2 and Nightly #83 since low power mode has been enabled. Low power mode might actually work with this kernel since it is kernel 2.6.35.13 rather then the older kernel 2.6.35.7 that doesn't support low power mode. I am trying it out now.
[Vibrant Android Development] Locksmith81:
Keep us posted.

from the amazing Jets Bread
[Vibrant Android Development] Abu-7abash:
This is hands-down the best kernel I've ever had on my Vibrant and I've had them all. Great battery life, no bugs, lags, great graphics and sound quality and most importantly no reboots. Again, a job well done Platypus, can't thank you enough bud :)
[Vibrant Android Development] asatnik11:
I second that....!
[Vibrant Android Development] iwapu:
Same issue here
[Vibrant Android Development] Locksmith81:
The new link fixed it. It was stated previously that BLN was broken. Updated now and works. But I'm back on CM7#85 stock kernel.

from the amazing Jets Bread
[Vibrant Android Development] Locksmith81:
Using v2 with latest nightly erases the low power mode. Flashed #85 with r2 and it doesn't stay off while charging.

from the amazing Jets Bread
[Vibrant Android Development] hellboyborn:
NEO 16 codename: Beast best kernel so far :)

Thanks
[Vibrant Android Development] mohamobo:
wait for neo 17. it will include offline charging.
[Vibrant Android Development] hotadef:
hmmmm neo 9 gave me better battery life with trigger than anyother neo. now my battery may have gotten worst since i tried neo 9 as it says it is at 100% at a lower voltage. but i had 8hrs 51 with 58% batter left. havent came close with any other neo. i guess im waiting for 17
[Vibrant Android Development] Locksmith81:
Patiently

from the amazing Jets Bread
[Vibrant Android Development] strictlyrude27:
On one hand, I was "wtf?"ing when I realized logcat was disabled.

On the other hand, WOW MY PHONE BOOTS FAST
[Vibrant Android Development] epakrat75:
I flashed #16 r2 while running Trigger 2.3.5 and upon reboot, my contact / SMS db was empty. :eek: I flashed back to #9 (what I was on previously) and all is well. :cool: No idea why that happened but my phone is not necessarily broke this way so I'm probably not going to try to fix it again (until the next release at least). :p
[Vibrant Android Development] zacharias.maladroit:
Neo 17 test-kernel

is available on IRC:

(requoting the IRC-server address)

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 :p)
[Vibrant Android Development] nbhnohome:
hi, what is the difference bt stock color vs vc one?

Thank you
[Vibrant Android Development] zacharias.maladroit:
stock color (like in cm7 stock kernel)

vc == voodoo color, change color settings via "Voodoo Control" app from Market
[Vibrant Android Development] hotadef:
i got to get on irc so i can see what sweetness is 17 to compared to 16 whats new and is anyone having any problmes with 17
[Vibrant Android Development] nbhnohome:
Can u tell me the difference bt OnDemand vs OnDemandX cpu governor? Thanks
[Vibrant Android Development] zacharias.maladroit:
Neo 17 r7 is available on the IRC !

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 :p)
[Vibrant Android Development] mohamobo:
Neo 17 r7 all working perfectly. Previous r5 can't charge offline..

Thanks Zach
[Vibrant Android Development] jalenthejiv:
how do i flash neo 16 do i use the scripts for anything never flashed neo before
[Vibrant Android Development] mohamobo:
what rom and kernel do u use?
[Vibrant Android Development] Djapatos:
This is the best... PERIOD
[Vibrant Android Development] buhlerbuhler:
Care to mirror?
[Vibrant Android Development] gamefreakgcb:
Can anyone mirror this please?
[Vibrant Android Development] d_phekt:
Tried Neo17 r7 w/led notifications running MIUI Revamped SS and randomly lose my Live Wallpaper when unlocking and after receiving texts. Also my missed call led notifications don't work, but that has been an issue on all kernels I've tried on this rom so far. All other notifications work fine. Excellent otherwise.
[Vibrant Android Development] gamikzone:
i would love a mirror and a changelog :p im on 16 r2 its great but i bet 17 is greater lol
[Vibrant Android Development] ferhanmm:
Those are both on irc...you can even do it from your phone. stop being extra lazy lol
[Vibrant Android Development] mohamobo:
respect OP

[NEO_17 r7 [open test]

Stock : http://bit.ly/nlEvl8

VC : http://bit.ly/rat56i

Changelog : http://bit.ly/qUvv5u
[Vibrant Android Development] bigtom624:
Thanks man