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

CM7 & MIUI only

NEO 02

(NEO_01 was internal build)

Kernel Scripts (Update):

- for switching to other governor (while screen is on - screen off = conservative) apply additional "screenstate_scaling switcher" script

description of governors:

- conservative [probably most battery efficient]

- interactive [pretty smooth operation - perhaps some hickups from time to time; phone gets quite warm with it; prefers higher over lower frequencies]

- interactiveX [same like interactive but with sleep & wake support - better suited for usage as only governor (testing)]

- ondemand [ondemand governor - compromise between speed & battery efficiency, very fast switching through all frequencies - in a perfect world the best]

- smartass [further evolution of interactive governor keeps the frequency at 600 MHz while idle (screen on) to ensure smoothest operation (need feedback, stability, etc.)]

- SavagedZen [further evolution of smartass governor (?) runs much better now (tweaked by arescode - thanks !) - I still prefer smartass the most in terms of performance ^^]

Link to governor changing scripts:

NEO_02/scripts/governors//

VPN users (disables rp_filter only - no change in governor):

systemtweak_VPN-enabled.zip

for those still getting bootloops (phones that need strict scheduler timings to work :eek: - no change in governor):

scheduler-issues_fix-enabled.zip
[Vibrant Android Development] apollo15rover:
CM7 Builds 9 & 10 - not too many are using now..

Can't wait to try this new Platypus out!

Too bad that call audio's broke on CM7 #9 and #10.. hopefully the next CM7 update will be workable. When it is, I'll definitely give this a spin.

Because of the issues, like many I've reverted back to build #6 and using with Kang.
[Vibrant Android Development] zacharias.maladroit:
I already wrote it in the captivate thread

but:

isn't this kernel-related ?

I included the "fixes" (to be precise it was a revert of the latest changes)

so that it should work with this kernel

and you can use #9 + #10 with this kernel and call audio should be fine

thanks !
[Vibrant Android Development] apollo15rover:
Hey Zack - do you have a link to this cleaning script? Might be useful..
[Vibrant Android Development] apollo15rover:
Ok.. downloading.. :rolleyes:
[Vibrant Android Development] zacharias.maladroit:
http://www.multiupload.com/922KMXMMVJ

:)

good luck !

hope it works *crosses fingers* :)
[Vibrant Android Development] gamikzone:
i hope audio in calls works on 11 i cant wait to try the newer version of this kernel im still running and older version of platypus with build 8 from cm
[Vibrant Android Development] apollo15rover:
Build #10 no joy.. downloading build #9

(EDIT: No go on #9 either..)
[Vibrant Android Development] VeryCoolAlan:
Nor #11

Back to #8
[Vibrant Android Development] zacharias.maladroit:
The following kernels only work with the new RIL

(Nightly #12 and newer on the SGS - Vibrant & Cappy == different nightly numbering)

Kernel

CM7 & MIUI only

NEO 03

(NEO_01 was internal build)

before you ask for any ETAs:

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

Changelog (from NEO_02):

- removed memcopy&memmove (let's see whether this improves stability & any in-call reboots)

- tweaked smartass & SavagedZen governor

- added downscale fixes from SGSII (thanks to kang/bilboa1 & Tk-Glitch !)

- some small fixes to pl330 (updated to Samsung's SGS driver) & cpuidle stuff

- some minor fixes & improvements

- memory mapping fix for HD video recording (no more FC when camera app is switched to camera / HD recording) [some commit in my repo seems to set wrong memory mapping which breaks HD recording :confused:]

- [upstream] larger radio partition ---> with newer Nightlys - need system change (thanks coolya !)

- [upstream] some mic & headphone fixes (thanks atinm !)

- Memory available: 339 / 340 MB

- switched to Tk-Glitch's OC/UV implementation [up to 1.6 GHz] (seems to be more stable, lower UV & higher OC) (thanks Tk-Glitch ! :))

- re-add: bluetooth l2cap powersave mode

- conservative smartass tweaks (if you want old behavior back please flash the smartass script for NEO_02)

not yet included:

- fugumod security improvements (thanks to nikademus for sharing the source !)

- bluetooth l2cap powersave mode

- and many more

Download Link:

Mirror #1

:

CM7_VIBRANTMTD_platypus-revolutions-kernel_20110527_r0_update.zip

CM7_VIBRANTMTD_platypus-revolutions-kernel_MIUI-20110527_r0_update.zip

(thanks to Roland for hosting !)

Mirror #2

:

this post

Troubleshooting & short-FAQ:

- WIFI & stuff not working ?

lippui94 cleaning script, then wipe dalvik, then fix permissions, then kernel - eventuall governor switch - , then wipe dalvik, then wipe cache, then fix permission

- reboots during calling ?

please report ASAP !

this is supposed to be fixed & a non-issue

- Radio (phone function) not working ?

this only works with nightlys > #12 on the SGS (including #12)

- phone is not as smooth as with previous kernel releases

yeah - sorry, might be due to the fact that I'm forced to use stock toolchain (less optimizations)

sticking points to test & feedback:

- call drops, reboots during calling & potential instabilities

- general

stability

(if this also happens on stock: post but add a note that it's from stock - thanks !)

- BT & WIFI switching

- HD video recording & playback (is smooth for me during playback, recording with HD & Youtube HD works)

- iptables

- battery runtime

- smoothness
[Vibrant Android Development] zacharias.maladroit:
there were some issues with 600 MHz so it got removed - don't know exactly what happened but it might have been stability issues (Tk-Glitch removed it :) )

1st post:

I let Tk-Glitch talk - he's the expert of his OC/UV :)

new OC/UV implementation (morfic, bilboa1/kang, TheEscapist - Tk-Glitch):

current values so far I have further tested are

100 MHz - 0.950v / -250mv [with Pimp my CPU] -> results in 700 mV

1400 MHz -75 mV (not much tested for stability yet)

1440 MHz -75 mV (not much tested for stability yet)

1500 MHz stock

1600 MHz stock
[Vibrant Android Development] hitman818:
Is the call audio fixed?
[Vibrant Android Development] nickmcminn60:
@ Zack,

You hit the nail on the head with this one. MIUI 1.5.27 and your latest = home run

been waiting on a kernel relese as stable as Kang. dont know what you did but my auto rotation is super fast! (even with dark themes). Keep up the good work!
[Vibrant Android Development] geoffcorey:
did you have to quote the entire long post just to ask this question?

And this is a test kernel to try and figure out if the call issue is kernel related at all.
[Vibrant Android Development] nickmcminn60:
And your justified to waste space also with your rude comments?

@ZACK

Is there a reason your 90screenslate scripts dont work with this? Im trying to use smartass.
[Vibrant Android Development] jonathanhuerta4:
Finished flashing CM Nightly 11 for Vibrant, than proceeded to install the latest Platypus release (NEO 3). Called a friend, and the call audio bug is still there. I'm just reporting not complaining. :)

UPDATE: I found something interesting. My service provider is not T-Mobile, it is Simple Mobile. When I flash the nightly, as well as the Nightly+Platypus Combo, the Simple Mobile banner in the lockscreen and in the notification drop down both show T-Mobile and not Simple Mobile as my carrier. It used to show Simple Mobile in the banner normally on build 8 and 6. My APN's are as I left them there, so APN is not the problem. This may be related to the in-call audio bug, or not, just reporting.
[Vibrant Android Development] nateskates:
What's the difference between the interactive kernel and the regular kernel?
[Vibrant Android Development] apollo15rover:
Thanks for the sacrifice.. I was curious about this myself but wanted to see if someone else would bite the bullet.. :D

I have the newest Platypus sitting in my phone.. waiting to see what happens with Build 12 whenever it comes out. If others say the call bug's gone, I'll try it out and install Platypus and see how it goes..
[Vibrant Android Development] apollo15rover:
A Worse than ETA Question..

Since Bilboa's out of the picture, how easy would it be for you to make Two Kernels - one the Platypus we all love, but also another "safe" vanilla type workhorse such as Kang?

Thanks in advance and yeah, I know I have no business telling you what to build - worse than asking for an ETA on what you already are building.. (can I find any thinner ice to skate on?)
[Vibrant Android Development] lralexl:
which vibrant nightly does this work with? it breaks my signal with nightly 11
[Vibrant Android Development] hitman818:
Is there a way to change the scaling to conservative without having it switch to smartass everytime I lock and unlock the phone?
[Vibrant Android Development] zacharias.maladroit:
Hi nick

it *should* work

could you please post some more info what trouble you're running into ?

thanks !

Hi jonathan,

the call bug hopefully *should* be fixed with next kernel (and changes from upstream)

thanks for your report !

interactive governor: http://android.doshaska.net/interactive

regular ?

it uses the "ondemand" governor

I'll take a look at it:

what features would you want in it ?

the same like in bilboa1's kernel ?

nightly #9 and after

make sure you don't flash the MIUI-kernel but the other one ;)

yes, flash a different 90screenstate_scaling script (or edit it in system/etc/init.d/ AWAKE_GOVERNOR="smartass" to the governor you like)

http://xdaforums.com/showpost.php?p=14112233&postcount=837
[Vibrant Android Development] DAKIDD236:
my camera doesn't work after flashing this. is there anyway to fix it?
[Vibrant Android Development] apollo15rover:
Baseband broken on latest (5/29) CM7
[Vibrant Android Development] nickmcminn60:
try going to titanium and wipe user data for the camera app, if still no go then try blinking the screen while the camera is open.
[Vibrant Android Development] DAKIDD236:
Okay, thanks

After wiping user data I get a force close popup "Activity Camera (in application Camera) is not responding"
[Vibrant Android Development] nickmcminn60:
reboot into recovery and fix permissions
[Vibrant Android Development] DAKIDD236:
Still a no go :(, Ill just nandroid to back and try a different kernel. Thanks for the help!
[Vibrant Android Development] nickmcminn60:
try taking the camera apk out of the rom and push it to the system/app folder and change permissions to rw-r-r. Its getting super confusing to new people with all the kernels and nightlies that have become incompatible.
[Vibrant Android Development] DAKIDD236:
Okay, I'll keep you posted

I still get the black screen then force close message

I'm on cm7 build 8.. is that the problem?
[Vibrant Android Development] nickmcminn60:
probably.....restore ur backup or update
[Vibrant Android Development] ceoesquad:
My phone wont find my Bluetooth with this kernel,is it the rom or the kernel I'm runing mui?
[Vibrant Android Development] iwapu:
Do I have to convert ext4 to something else if flashing other kernels over this? Didn't see an option in Recovery though.
[Vibrant Android Development] nickmcminn60:
No ext4

This kernel DOES NOT convert your files sytem to EXT4! Everything is Yaffs2 with the exception of data.

Any kernel made for MIUI or CM7 at the moment does not change the file system
[Vibrant Android Development] nickmcminn60:
Any one use "AD FREE"? When I try to Download the host list it says it cant find a partition to mount to write the files.....any ideas? Ive been using it with MIUI and CM7......could it be the kernel?
[Vibrant Android Development] idtheftvictim:
I too would love to know the answer...lol
[Vibrant Android Development] iwapu:
Thx for making it clearer!

What about data? What does the kernel do to data? Just wondering if the data will be compatible with other kernels.
[Vibrant Android Development] nickmcminn60:
Any kernal that is compatable with cm7 or miui all use the same pertitions and file systems. MAKE sure your trying to flash a cm7\MIUI kernal

here: http://kang.project-voodoo.org/f/CM7/Vibrant/

here: http://xdaforums.com/newreply.php?do=newreply&p=12948971

PS> all of these kernels use ext4 on data and yaffs2 on system\cache-\data\data.

If you want to see what file system each partition is just download this app... https://market.android.com/details?id=com.android.term&feature=search_result and type ''mount'' and hit enter.

If you want to go to another rom other than miui or cm7 you will need to Odin to stock with repartition and efs clear checked.
[Vibrant Android Development] iwapu:
Thanks bro.

I know I'll need to Odin to stock with repartition. Did it several time :-)

But I'd recommend not having efs clear checked. Doing that you'll lost your efs and have to restore from your efs back up.
[Vibrant Android Development] nickmcminn60:
efs wont need to be restored if your going to use any other rom besides cm or miui
[Vibrant Android Development] cervantesjc:
I tried the step, and it seem that the battery is getting worse, around 10%/hr with little to no use.
[Vibrant Android Development] xriderx66:
thats good i lose like 10% in 10 minutes lol with idle.
[Vibrant Android Development] cervantesjc:
how can i fully disable bln on the phone, it seems is draining my battery.
[Vibrant Android Development] dxtrlabs:
Activate quiet hours for all day in cm prefs under sound i think.
[Vibrant Android Development] djordan79:
After booting up from CWM, Rom manager force closes as soon as the phone starts back up.... even without opening Rom manager.......what gives??
[Vibrant Android Development] djordan79:
thanks for the reply.... i just deleted rom manager for now as it cant be used on this rom anyway....
[Vibrant Android Development] djordan79:
so I admit I'm a noob when it comes to this kernel thing ;}

is there a way to access the kernel settings and tweak it myself?

or is it pretty much use "as is"?

I've seen comments about undervolting, etc....

just seems like I'm missing something here as far as being able to control the kernel after flashing it.... any help would be appreciated....

thanks
[Vibrant Android Development] apollo15rover:
Running CM7 + MIUI + KB5

(EDIT: Further information: also running Platypus Conservative; SetCPU at 1.3 and Conservative)

After some time, autorotation doesn't work and WiFi won't activate.

Battery pull resolves but this is happening regularly -

Do I need to reflash? Any other recommendations?

Thx
[Vibrant Android Development] iynfynity:
so which one would you recommended? the ondemand or conservative?
[Vibrant Android Development] zacharias.maladroit:
ok, time for a test:

kernel test-release (for stability, latency & overall feedback)

Introducing "Core low-latency" release

04/17/2011 (release name: "Core" low-latency edition; should be Stable )

kernel:

1st Mirror / Host

: [recommended]

test - "core low-latency" (thanks a lot to Roland !)

2nd Mirror

:

this thread (XDA)

3rd Mirror

:

CM7_VIBRANT_platypus-kernel_20110417_20_core_low-latency.zip (3.91 MB)

md5sum:

f60a64dbbb7f879bb7302cf20d937d77 CM7_VIBRANT_platypus-kernel_20110417_20_core_low-latency.zip

(only conservative right now, if you want others: change in /system/etc/init.d/90screenstate_scaling)

Changelog:

Installation steps:

Troubleshooting:

Please test specifically for the following sticking points:

enjoy ! :)

FYI:

for your convenience the kernel zip-files are also attached to this post

thanks !
[Vibrant Android Development] notverycreative:
Baseband is broken on newest nightly for me too.
[Vibrant Android Development] apollo15rover:
My vote would be just a solid basic workhorse for Voodoo Sound and Color..
[Vibrant Android Development] kimbo1986:
Cm7 and the file format is fast as all hell. I obviously see improvement when overclocking could but its far from something I need nor really want considering extra battery drain and having to clock back for certain things (my phone freezes when over 1ghz while watching movies). As some others have said a work horse kernel that includes the stock cm7 kernel that has been worked on by the cm7 team and just throw in voodoo sound/color and maybe other minor tweaks for ram and such. Kind of like overstock (2.2 kernel). That would do me just fine! Its obviously something people want. If you where around when overstock hit the seen it blew up dramaticly because everyone wanted that but just didn't realize it until it was made!
[Vibrant Android Development] nickmcminn60:
then why not just run this kernel with the default 1ghz clock?

If I need a good stable kernel I still come back to R12
[Vibrant Android Development] kimbo1986:
Which one is r12 can't find it.
[Vibrant Android Development] Abu-7abash:
R12 is the product of kang, not Platypus and it's no longer supported. You can find it here
[Vibrant Android Development] nickmcminn60:
R-12: http://kang.project-voodoo.org/f/CM7/Vibrant/CM7_Vibrant_kernel_kang_20110507_r12_update.zip

R-25: http://kang.project-voodoo.org/f/CM7/Vibrant/CM7_Vibrant_kernel_kang_20110511_r25_update.zip
[Vibrant Android Development] notverycreative:
r12 and r25 should not be used as they are approaching a month old and will lack many features and FC and bug like hell. Don't do it.
[Vibrant Android Development] nickmcminn60:
Hes on MIUI (I think) and they are still rock solid.(on MIUI)...... believe me I know. If your on cm7 then no go
[Vibrant Android Development] Abu-7abash:
Even on CM7, if he's on Nightly 8 and downwards then it will work like charm. Best kernel for those two IMO.
[Vibrant Android Development] cashyftw:
Is there any version for the newest nightly.

Sent from my SGH-T959
[Vibrant Android Development] zacharias.maladroit:
MIUI kernels == MIUI + CM7 prior to RIL switch to Samsung's (closed source) RIL

CM7 kernels == CM7 with newer RIL only

Kernel

CM7 & MIUI only

NEO 04-energy

(energy efficient build for max battery runtime, efficiency & smoothness)

(NEO_01 was internal build)

before you ask for any ETAs:

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

Changelog (from NEO_03):

- fugumod security hardening re-added

- optimized memcopy & memmove for maximal efficiency & speed

- optimized for size (less cache-misses & leaner and [perhaps] faster system)

- optimized for NEON-usage

- conservative-governor ONLY (one governor to rule them all) - battery consumption + performance == win + win

- FIQ-console disabled (probably less overhead + battery savings)

- LED notifications disabled - only LED light timeout enabled (battery savings)

- printk time-stamps disabled (probably less overhead + battery savings)

- fixed HD Video recording + mic recordings (sound works again)

- "old" OC-UV-implementation OC until 1.3 GHz

- re-added Nick Piggin's inode integrity patches (2 of them) - (more stability & perhaps some saved cpu cycles -> battery)

- re-added several of the previously not included patches from quorra kernel-base

not yet included:

- fugumod security improvements (thanks to nikademus for sharing the source !)

- bluetooth l2cap powersave mode

- and many more

current stable UV values (for me)

1000 -50 mV

800 -75 mV

600 -225 mV

400 -125 mV

200 -150 mV

100 -250 mv

Download Link:

Mirror #1

:

CM7 / new RIL:

CM7_VIBRANTMTD_20110529-10_r_platypus-revolutions-kernel_0_NEO_04-energy.zip

MIUI / CM7 / old RIL:

CM7_VIBRANTMTD_20110529-09_MIUI_platypus-revolutions-kernel_0_NEO_04-energy.zip

(thanks to Roland for hosting !)

Mirror #2

:

this post

Troubleshooting & short-FAQ:

- WIFI & stuff not working ?

lippui94 cleaning script, then wipe dalvik, then fix permissions, then kernel - eventuall governor switch - , then wipe dalvik, then wipe cache, then fix permission

- reboots during calling ?

please report ASAP !

this is supposed to be fixed & a non-issue [if it's still happening try with different nightly]

- Radio (phone function) not working ?

new RIL kernels only work with nightlys > #12 on the SGS (including #12)

- phone is not as smooth as with previous kernel releases

yeah - sorry, might be due to the fact that I'm forced to use stock toolchain (less optimized toolchain)

sticking points to test & feedback:

- call drops, reboots during calling & potential instabilities

- general

stability

(if this also happens on stock: post but add a note that it's from stock - thanks !)

- BT & WIFI switching

- HD video recording & playback (is smooth for me during playback, recording with HD & Youtube HD works)

- mic recording, HD video + sound (tested & should work)

- iptables

- battery runtime

- smoothness
[Vibrant Android Development] zacharias.maladroit:
you can try with the latest kernel

but no guarantees:

I don't know what exactly is needed for the latest nightly & whether my kernel has all needed changes

besides that if something breaks you need to start over from the beginning (-> flash Froyo and then back to CM7 from Froyo) - since it's using a different partitioning on the radio-partition
[Vibrant Android Development] hitman818:
It says nightly #12, do you mean the one that came out today, cm7.1.0?
[Vibrant Android Development] zacharias.maladroit:
please read all of it :p

it's a different numbering scheme

kernel with new RIL applies to:

SGS: >= #12

CAPTIVATE: >= #14

VIBRANT: >= #9
[Vibrant Android Development] cashyftw:
Could you start your own thread, I forget about this one since the op has gotten a new phone, and the title is never updated lol.

Sent from my SGH-T959
[Vibrant Android Development] hur8111:
Anybody tried neo 4 with newest build?
[Vibrant Android Development] nickmcminn60:
Whats different than the 5-27-11 miui kernel?
[Vibrant Android Development] zacharias.maladroit:
that's NEO03 ?

read the changelog :)

@Everyone:

please post in its new thread:

http://xdaforums.com/showthread.php?t=1102280
[Vibrant Android Development] T.C.P:
gracias amigo off to test i go :p
[Vibrant Android Development] Hung0702:
Tested Antlion and Core-Latency. No auto-rotation with either. Followed directions to a T.

I really like the kernel though. I've been able to get really low undervolted settings. Too bad I need auto-rotation more.

CM7
[Vibrant Android Development] zacharias.maladroit:
wow - is it broken for EVERYONE on the Vibrant ? :confused:

that's really weird - I feel bad for you

don't know what might be it

Hung0702 you by chance use MIUI ?
[Vibrant Android Development] g1flasher:
No rotate for me on nre Core release either, rotate worked on antilonipizzasause :):)
[Vibrant Android Development] apollo15rover:
Rotation spotty on Antlion (conservative) and Core Latency. WiFi broke entirely on Core Latency. Tried going back to Kernel Lang but neither worked! I am running latest miui + KB5.

So went to Antlion again (this time on-demand) and WiFi's back thank God. Reboot brought back rotation.

So far Antlion on-demand is working out best for me..
[Vibrant Android Development] hitman818:
The power save mode scaling on setcpu is really unresponsive and laggy.
[Vibrant Android Development] vinnydakid:
Rotation 100% broken in Latency but wifi worked fine.
[Vibrant Android Development] hitman818:
Rotation works fine for me. Maybe some of you have auto-rotation off.
[Vibrant Android Development] hitman818:
My phone just randomly rebooted while I was on the web.
[Vibrant Android Development] nickmcminn60:
Keep losing widgets.....Im on Platypus\MIUI not sure if its the rom or kernel? Corruption?
[Vibrant Android Development] hitman818:
I think the browser is messed up. It causes the phone to reboot right when it opens. Happened three straight times to me.
[Vibrant Android Development] hitman818:
After three random reboots the browser is fine.
[Vibrant Android Development] iynfynity:
where is this kernel based on?
[Vibrant Android Development] cervantesjc:
confirmed, auto-rotation broken with the test build, wifi and browsing are fine, one thing that i did notice and makes me happy with this, is that my camera started working again.