yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] zacharias.maladroit:
yes it does,

strangely it had downloaded an outdated version from the market

so I also got the same error message

after downloading an updated one it worked

I downloaded several apps and had to attempt to download some of them several times due to failed downloads

could be some Market-related issues, not sure if it's the kernel or the scripts at all ...

some network security settings might be too aggressive or causing trouble

try replacing the scripts in the kernel-package with the attached ones (S98system_tweak got changed)
[Captivate Android Development] ls377:
Man...I completely missed Neo 9 :p
[Captivate Android Development] tarheelblueboy87:
Neo10 has perfect ondemand settings by default. The awesome work continues, this kernel is golden! My battery life doesn't suck so bad anymore!
[Captivate Android Development] oops_iv:
Haptic

I'm using MIUI 1.6.27 and was using NEO9 now NEO10 .. My haptic is busted and doesn't work for Swype or the Android keyboard .. I'm not sure if this is a MIUI prob or NEO .. any idears? Anyone else have success?
[Captivate Android Development] jesus_c:
it's not kernel

glitch - no haptic

stock - no haptic
[Captivate Android Development] jesus_c:
I realy love neo10!

miui+neo10+jvp = my choice for i9010 armani
[Captivate Android Development] amucinom:
will NEO 10 work with the CM7.1 RC1?
[Captivate Android Development] zacharias.maladroit:
of course

it's synced again 7.1.0-rc1 +#1 nightly

no one's reading the stuff I'm writing ?

fine :\
[Captivate Android Development] mcord11758:
Yes it should
[Captivate Android Development] donks232:
auto rotation is working fine for me i had to reboot after install and mess with rebooting to get me sd card working, but this has been the case with all the other kernels i have tried this week with 2.3.3 im using miui lags are very few and far between. benchmarks seem about the same 1300 vs 1300 only thing ive noticed i on quadrant standard the lil moon has a glitch line thru it(which i think happens on the other 2 kernels ive used) and before the jelly fish cubes in smartbench it slows down then for a half second. its not quite as fast as 1400oc but :rolleyes:
[Captivate Android Development] Dlev7:
What does it mean change the permissions to rw-r-r--??

Someone please help me, I love this kernel but miss BLN.

I downloaded this CM Parts .apk like it said in OP.

But when I move in System/App via. Root explorer I get force close like Phoenix said.

So when I long click on app in root explorer for permissions I get three by three column:

Read Write Execute

USER:

Group:

Others:

Which do I tick?

Again please help
[Captivate Android Development] zacharias.maladroit:
just follow bilboa1's instructions:

that worked for me :)

enjoy !

but read & write for all should be fine OK

I pushed it via adb and:
[Captivate Android Development] SweetwaterBurns:
Is anyone else having issues with the light sensor not adjusting the screen after flashing this?

Edit: nvm it appears that in my build from this morning, cm settings no longer has the option for setting custom levels. I think that is the problem. I'll try going back to an older build and clearing those first.
[Captivate Android Development] zacharias.maladroit:
Kernel release name: Rocketeer (same-day release like for the SGS - GT-i9000)

Changelog:
[Captivate Android Development] phoenix2217:
If you are using root explorer change the permissions so that the three in the left column are all checked and the one at the top in the middle is checked. Reboot and that should fix your issue.
[Captivate Android Development] phoenix2217:
Unfortunately, if you use the root explorer way, unless you set the permissions so they are the same as all the others in the folder, it will force close. =/ So it should be:

(Looking left to right)

Column 1 should have all three X's, column 2, only the top X, column 3, none.
[Captivate Android Development] h0ckey10:
anyone test out the 4/08 version yet? curious to see how this will go...
[Captivate Android Development] arcardinal:
I flashed the latest kernel as soon as I saw it. After the initial flash, auto rotate was not working. A reboot did not fix it. I had to boot into recovery and clear dalvik cache and fix permissions. This fixed it and its running perfect now. So far no other issues. Oh yeah, this is on the latest CM7 nightly.
[Captivate Android Development] donks232:
i spoke to soon on the 4/5 release saying it was running great for me. im going to give this one a shot. im downloading it now.
[Captivate Android Development] Grandelama:
Yes, this version is MUCH better, it's running fast and very smoothly, and it seems stable as well.

All the slow downs and lags I was experiencing with the last version seems to have disappeared. Led notification is working too (through root explorer).

Only issue: auto rotation is not working. Tried to clean dalvik cache and fix permission but no luck
[Captivate Android Development] ls377:
New release is running great except for one thing: When I'm in a call, the screen won't turn on at all. Had to battery pull to hang up. Is this isolated to me?
[Captivate Android Development] zacharias.maladroit:
wow - I thought this was fixed :confused:

(it works for me btw, no black screen or screen not turning on)
[Captivate Android Development] ls377:
Weird...I'll give it another try later.
[Captivate Android Development] arcardinal:
Auto rotate stopped working for me. Nothing I did would fix it. Clear dalvik cache and fix permissions did not work. Had to reflash another kernel for it to work again.
[Captivate Android Development] Grandelama:
clear Dalvik Cache

boot

press power button for more than 10 seconds

reboot

fixed it for me
[Captivate Android Development] zacharias.maladroit:
Introducing "Flubber"

04/09/2011 (release name: flubber; WIP - work in progress release)

kernel:

Changelog:

Please take not that this is a WIP (work in progress) release and therefore does NOT include all fixes & improvements like the Rocketeer release

it should however work fine (similar to bilboa1's kernel)

Please test specifically for the following sticking points:

enjoy ! :)

edit:

FYI:

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

please also test the kernel for following things:

thanks !
[Captivate Android Development] ls377:
@zacharais-If you don't mind, I just added a link to your post in the OP since its just a testing build. I can add it fully if you want, or wait for it to be tested.
[Captivate Android Development] zacharias.maladroit:
@ls377:

that's fine :)

like you stated - it's just an interim build (approx. 50% fixing/feature-adding complete)

but should work fine overall

I threw it out to get some more feedback on stability, etc.

thanks !
[Captivate Android Development] Grandelama:
I'm testing the new release. Everything seems to be working all right.

Wifi is working, auto-rotation is working, auto-brightness is working (it was broken in last release, at least for me), sd card is accessible :)
[Captivate Android Development] peachpuff:
For some reason led notifications only work with gmail, with text's or other notifications the touch keys don't light up, is this normal?
[Captivate Android Development] tarheelblueboy87:
Its in the individual keyboard settings, "vibrate on keypress" or something. I'm using Swype beta 3.0, but it should be in the regular too.

Sent from my SGH-I897 running CM7 clocked to 1.44Ghz, dang that's fast! Platypus NEO10 kernel, battery life on CM7 doesn't completely suck anymore!
[Captivate Android Development] pamaguin:
If you don't mind, can you share your settings? I have never been able to OC from previous nightlies either. Thanks in advance! And what voltage app are you usingł the OP or off the market
[Captivate Android Development] tarheelblueboy87:
It always varies from phone to phone. My old Captivate(build 1010- not sure if it matters, but its not as new as my current 1012 build) wouldn't UV very far, I could get -50mV at 1000mhz, -75 at 800mhz. I didn't run CM7 though, which has been rumored to be more stable when undervolting, and now, I have my Captivate running super-stable at -125mV from 800mhz through 1440mhz, except for the 1000mhz state, which I have at -100mhz (always seems to need -25mV compared to the 800mhz and 1200mhz steps). So I am doubling the undervolting on my current Captivate as compared to my last one. My settings are shockingly stable, although they probably wouldn't be stable on many Captivates. You figure it all out through trial and error, start with less UV and increase until its stable at each level. I use Stability Test 1.5 and run it for at least 20 minutes to see if my phone is stable. If you are undervolting too much at any step, it crashes by then.

This should get you running, just remember every phone is different when you are tweaking the voltages: Check out the mini-overclocking/undervolting guide by shaolin95 - http://xdaforums.com/showthread.php?p=12910471#post12910471

Keep this voltage settings removal script handy too - http://xdaforums.com/attachment.php?attachmentid=589472&d=1304784398

I set my voltages with Control Freak Beta 0.4.2, which is based off voltage control, and I have use the deadline scheduler, just fyi, use whatever works best.

So, Zach, how do you open the locked voltage states on your kernel? I have always wanted to know. I think you should at least unlock the 400mhz state, or at least tell me how to, because I want to UV that step and its stable at -150mV on my phone. Great call on keeping the 100mhz and 200mhz states locked though, stability is an issue when undervolting those levels, as I learned with other kernels - it always messed up rebooting.
[Captivate Android Development] tarheelblueboy87:
I don't use gmail, but my texts definitely light up my keys. That's pretty much all I can confirm, except that under my Call Settings I have the box checked that says "Missed Call LED Notify". That probably means nothing, but something is definitely wrong if it doesn't light up on texts and missed calls. I'd make sure you don't have something else running that might interfere with this kernel. You can start by running the kernel cleaning script twice (you can find it in the OP), then reinstalling the kernel (make sure you have the latest one, zach did put one up on 6/28 with LED notification).
[Captivate Android Development] gabby131:
@zach

Thanks for the Neo 10. Works like a charm....everything is smooth....I can't really tell the stability for 1.6ghz for my device does not want freqs higher than 1.5ghz.

If I may ask....is ondemand governor be the neo series' default screen awake-governor? Ondemand likes my cappy and my cappy likes it as well.

Thanks and regards

EDIT: works with cappymtd 6-29-2011.

EDIT: streamsync ~#41 oops....I missed that....>_<

Sent from my Cappy
[Captivate 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

(I'll answer your question posted later when I find time)
[Captivate Android Development] tarheelblueboy87:
Hope all goes well for you zach. This is a good kernel version to go out on. I appreciate the time and effort you have put into what is now a pretty awesome and stable kernel. Thank you.
[Captivate Android Development] PhoneTay11:
Will NEO 10 work with CM 7 #43 (I believe CM 7 #43 is latest one so far?)
[Captivate Android Development] rwells813:
Yes it will work, 44 is the latest as of yet and Neo 10 will work with that as well
[Captivate Android Development] capita:
Appreciate all your work on this kernel Zach. Rock solid stable, fast, and good on battery.
[Captivate Android Development] pamaguin:
Battery life is good with this kernal. 1 day unplugged and still have 17%..
[Captivate Android Development] Tarima:
I'm confused, how am I supposed to get the LEDs to stay on when the screen is on. Keep the Lights On doesn't seem to work on this Kernel, and I see no option for it in Settings either.
[Captivate Android Development] readitodie:
I'm running MIUI beta7 and can't get BLN working.

i flashed miui led notification version.

Pls help me.
[Captivate Android Development] peachpuff:
For me led notification only works on missed calls and gmail, on every other notification it doesn't work, not sure what the issue is.

Great kernel btw, extremely smooth.
[Captivate Android Development] readitodie:
I can't turn on BLN.

everything else works fine but bln.
[Captivate Android Development] peachpuff:
Oh you mean the app? Well this kernel doesn't support bln so it wont work with the app.
[Captivate Android Development] ls377:
Get a cmparts.apk from one of the older nightlies that had bln (or just get a nightly for a phone with an LED and steal the app) and install it. You'll be able to access it from the settings then.
[Captivate Android Development] zeronothing:
By default is this kerenl set to be overclocked and underclocked? Or is that something I can setup if I want too? I just want to leave the CPU at its intend speed.

thanks
[Captivate Android Development] sixstringsg:
Its default clock to start out with, and is configurable.

Sent from my SGH-I897
[Captivate Android Development] five5outh:
I'm on MIUI 1.7.1. and the LED notifications isn't working for me.

It just flashes once then turns off. I have the MIUI_CAPPYMTD_NEO10 LED NOTIF kernel installed on my phone.

Ran the cleaning script thrice... any ideas?
[Captivate Android Development] insane08:
im running NEO-10 for captivate miui and my phone sseems to heat up very quickly even if it is on charge for 2 minutes...i have heard good reviews about NEO so im not giving up on it just thinking of going down to NEo - 9 or 7 ...

1) which would you recommend..?

2) if i want to go from 10 to either 9 or 7 i should run the cmw clean script and then flash the zip for the kernel right ? please correct me if i am wrong..thank you for any help
[Captivate 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
[Captivate Android Development] Cozmo1:
Looking good, Zacharias. Anxiously awaiting to use the cwm improved and enhanced Neo 11 on my Captivate :)
[Captivate Android Development] XsceneXhippieX:
With the stated changes will there be any noticable performance differences? i assume the scheduler that got the "fix" will perform better but i dont know which scheduler it is :p im sorry if im way off in my guess
[Captivate Android Development] zacharias.maladroit:
better wait for NEO_12 :p

NEO_11 still included autogroup (which has some issues with sound playback - at least for me and some testers),

next one will have (hopefully working) BFS, BLN, etc. :)
[Captivate Android Development] zacharias.maladroit:
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​

I'm still new to this IRC thingy (not using it much even though I know it)

so bear with me, ...
[Captivate Android Development] XsceneXhippieX:
i know the differences in the schedulers from googling the names (ie noop vs cfq vs bfq vs deadline) but i am still at a loss as to which is better for android, i can say the concept of bfq seems to be the most logical and efficient according to what i read, but the default is normally set to deadline, is there a reason for this? does it hold advantages over the others available thus far? and what would i have to do to submit a request for the interactiveX or savagedZen governors, or GPU oc'ing lol sorry i have so many questions but ill never learn if i dont ask them :) i love the way this kernel performs, its easily the fastest and smoothest performing kernel ive tried on my personal cappy, im on escapists latest because of its upstream changes and a slight gpu oc and it still doesnt keep up with NEO_10 on my device, gotta give props where they are due, this kernel rocks!
[Captivate Android Development] zacharias.maladroit:
fresh from IRC:

these are not final yet (using stock toolchain)

but should be ready for general testing / consumption

let me know what you think of them :)
[Captivate Android Development] mcord11758:
Working well on miui, have not encountered any issues yet
[Captivate Android Development] b0uncyfr0:
Yes its working wonderfully. I havent noticed any problems. Voodoo Control Plus is working and BLN is also fully working. Its looking very good so far.
[Captivate Android Development] Fate-Silver:
Haven't encounter problem yet for the Neo-12 Test Kernel.
[Captivate Android Development] Cozmo1:
Neo 12 test working very well on the latest MIUI release.
[Captivate Android Development] mcord11758:
I appear to have relatively frequent issues with soft keys using neo 12

Miui Captivate
[Captivate Android Development] readitodie:
+1 seems like the same problem occurs when using other kernels too
[Captivate Android Development] MadeInMex4usa:
Working good so far (2nd day)
[Captivate Android Development] Cozmo1:
Hmm.... you guys use the Android keyboard or Swype? I use Swype almost exclusively and haven't had any issues. If referring to the home/menu/back/search buttons, I don't have any real issues with them either.
[Captivate Android Development] b0uncyfr0:
Im using swiftkey and dont have any problems. What is this soft-key problem?
[Captivate Android Development] skrallbro:
I've had these problems as well and I've used gingerbread keyboard, Swype, and Smart Keyboard.
[Captivate Android Development] zacharias.maladroit:
fresh from IRC:

please test if BLN works now (it seems there were some issues before)

timeout isn't added/implemented yet
[Captivate Android Development] peachpuff:
No issues with bln with neo12 on my phone.
[Captivate Android Development] Fate-Silver:
I guess the "soft-key" issue means the 4 soft touch buttons(menu, home, back, find). Yes, it does have problem sometime. But, I am not sure if it's due to this kernel... because I encountered it on other kernels as well.
[Captivate Android Development] Thnikk:
I didn't realize how much I missed BLN until I installed blinky. Touchkeys are fine so far.
[Captivate Android Development] zacharias.maladroit:
awesome !

could you guys please feedback what ROM you're using and what you did to get it working ?

testers / users on the sgs / i9000 forums are having trouble to get it working

many thanks in advance ! :)
[Captivate Android Development] Thnikk:
I'm running the latest MIUI and I just had to install BLN control and select activate :)
[Captivate Android Development] zacharias.maladroit:
and the lights turn on as soon as you receive a message (SMS), email or other stuff ?

the problem for me right now is that I can't send messages or test things easily cause I'm on holidays outside of Austria so things get expensive fast - as soon as I send several SMS to test stuff ^^

so I'm somewhat dependent on user & testers input

thanks !
[Captivate Android Development] Thnikk:
Yup. I've tested it with phone, sms, and email, and all are working fine.
[Captivate Android Development] peachpuff:
Using cm7 #59, enabled bln with the app and that was it.
[Captivate Android Development] b0uncyfr0:
Finally ran into that soft-key problem everyone was talking about. The keys just dont light up and stop working. Easily fixed by putting the phone into sleep then bringing it back.

Ive flashed that new kernel (dated 17-7) that was posted, im testing it now to see if its been fixed or not.
[Captivate Android Development] drancid:
cpu governor keeps restoring to ondemand by itself. any suggestion plz?
[Captivate Android Development] tarheelblueboy87:
Use Zachs instructions in the screenstate scaling script, located in system/etc/init.d, or follow the more complicated way below

You have to go to the screenstate scaling script and underneath the section for the current settings (no #in front of the governor) change the name of the top governor from "ondemand" to whatever you want. (make sure there is a # sign before all other options you arent using, that's important), then restart your phone to reflect the change. The script is located in system/etc/init.d, open it as a text to edit it, and make sure u mount the system as R/W if its set to R/O.

Sent from my SGH-I897 on CM7 clocked to 1.44GHz

Glitch v11 ML
[Captivate Android Development] tarheelblueboy87:
I run into that occasionally on all kernels, it's beyond kernel development I think, we'll have to patiently wait for a CM fix, but they are good so it should come soon.

Sent from my SGH-I897 on CM7 clocked to 1.44GHz

Glitch v11 ML
[Captivate Android Development] b0uncyfr0:
It hasnt happened again so it just must be a matter of time.
[Captivate Android Development] mcord11758:
Bln working on miui using last release with blinky app

Miui Captivate
[Captivate Android Development] tarheelblueboy87:
Its really random and shows up so little that it doesn't take away from the awesomeness if CM7, a fix will be nice tho :-)

Sent from my SGH-I897 on CM7 clocked to 1.44GHz

Glitch v11 ML
[Captivate Android Development] wetwhere:
Thanks for the kernel to test. NEO-12-test02 running fine so far. I don't use BLN so I can't help with that.

Captivate 1007, CM7 nightly-62, 1300MHz max, default script settings

One question. What is the purpose of having a 2 second pause before the governor is changed in the screen-scaling loop? I understand the benefit of having the script sleep but why at that location specifically? Why not, for instance, sleep after the governor is changed and the cache settings are updated?

Thanks,

WW
[Captivate Android Development] zacharias.maladroit:
this is due to the use with Samsung kernels:

I also used it with samsung kernels (non CM7/MIUI) and without that pause it seemingly didn't work correctly with switching the governor ^^
[Captivate Android Development] wetwhere:
I can report after half a day mote using 12-test02 that I'm also experiencing soft key problems. Also, the framework has rebooted twice for no reason (not full reboot, maybe just zygote)

As for the loop script. ever thought of employing a cpufreq daemon (using userspace gov) like the desktops do? It seems to me it could be potentially much more versatile. For instance, the daemon could change settings based on a variety of variables such as plugged in or charging, sleeping/awake, low battery, etc. Don't know if anyone has discussed it before -- just a thought.
[Captivate Android Development] skrallbro:
Usually soft boots are caused by undervolting too much. I'd say reduce your undervolting and see if you still get the reboot issue.
[Captivate Android Development] wetwhere:
Well, I'm using the same settings that I've used reliably for weeks with NEO 10 without a single reboot.
[Captivate Android Development] zacharias.maladroit:
the problem is that for these IRC / bleeding edge testing only kernels

I use the stock toolchain from Cyanogenmod (gcc 4.4.3) which isn't as stable as the 2011.03 toolchain (gcc 4.5.2)

so it indeed might be possible that it reboots with UV values that previously were stable with 2011.03
[Captivate Android Development] Thnikk:
Weird, when I reflashed the latest miui, I had to flash 7/15 before 7/17 to get bln to work.
[Captivate Android Development] mcord11758:
I had to take the light sensor from escapist kernel and placed it in system/lib/hw. Then reboot

Miui Captivate