yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] d_phekt:
I'm another one using v3.4.39 with everything running perfectly. Not one single issue since it was released. No reboots, SOD's, etc. Also like the fact that it includes blinking BLN.
[Nexus S Android Development] leap_ahead:
+1

Perfect kernel for me !!!
[Nexus S Android Development] :
Ok, i will keep blinking in bln. I still need to figure out why it won't time out though.
[Nexus S Android Development] djees:
With 1.5b i Can't play vidéo On YouTube and in gallery With miui 2.8.10
[Nexus S Android Development] dkm911:
Love this kernel!! With the tuned interactive and BLN!! That's what I want!!
[Nexus S Android Development] italia0101:
Lost signal again on stock rom when listening to music with screen off

Only a reboot fixes it
[Nexus S Android Development] asphantix:
.39 is rock stable for me on my stock rom (i9023). Deep idle works but as always it sometines behaves strangly - sometimes it saves battery sometimes it drains battery. Hopefully we will soon be able to use this new IDLE2 thingy. Deep Idle was always a love and hate experience ;)

It's the snappiest kernel I ever flashed.
[Nexus S Android Development] :
The fix for that is in post 2 somewhere. Have a look :D
[Nexus S Android Development] :
Deep Idle breaks sometimes. If it breaks, it can't save power (it will use more! :eek:). The way to tell if it is broken is to keep checking the idle-stats, and if they ever stop increasing, deep idle is broken, and needs to be disabled until you can reboot.

I may be able to program this safeguard into the kernel.
[Nexus S Android Development] alen1901:
Hmm. That narrows my suspicion to the kernel. I had that signal drop too, on codename android.

And bedalus, for bln i dont use blink as this might use much battery and cause problems, so, im ok with this for now. :p

Sent from SpeedMachine i9023
[Nexus S Android Development] gregorypeg1000:
I thought that the idle stats should be increased only when the screen off and music playing,not every time you turn of the screen.
[Nexus S Android Development] :
They will increase if the system does anything in the background too, so long as it can be achieved in the deep idle state, e.g. sync data.
[Nexus S Android Development] :
Well BLN is fixed. You can have blink or not. It will time out and the lights go out.

However, there is a problem. If you are away from your desk and miss a BLN, when you return, you won't see any further BLNs unless you power on your screen.

I can't seem to find a way to make it activate for individual notifications.
[Nexus S Android Development] :
Here is...

v3.5 http://d-h.st/RDy (version for stock here: http://d-h.st/9ZQ)

-Update to linux mainline 3.0.40

-Fix BLN timeout

-Set DI at 800 MHz

-Fix init.d to work properly (e.g. set smartassV2 governor)

First link is for CM/AOSP based

Second link is for Stock OTA only

I haven't added init.d support to the stock OTA. But I think I could. Any stock users interested in testing that?

I'm setting DI at 800 MHz because I just want to rule out 400 MHz as the cause of some of the glitches being reported. If people continue to report problems anyway, I'll experiment with setting it back to 400 MHz.

I think I'll continue to roll with the mainline, rather than do what thalamus is doing. If you're not living on the edge, you're just not a crackflasher.

In the next update I'll try to write some code to disable Deep Idle if it breaks, because it goes from being more efficient to less efficient in this unfortunate situation. If AnTuTu can break it, so can other apps!
[Nexus S Android Development] Imppy:
Nice update going to test it now...what's the default settings for this? Like the schedule and governor ...and what would app you recommend to play with those settings? Setcpu good?
[Nexus S Android Development] :
Default governor is ondemand

Default scheduler is deadline

Since I fixed init.d in this release, NSTools works slightly better, but still seems keen on raising the min to 200 MHz, so I recommend using init.d scripts to set your own preferences.
[Nexus S Android Development] Imppy:
Could you guide me in how to make those scripts ? Is there a link?
[Nexus S Android Development] Blackcrx:
Only update for JB? No update for ICS? Haha
[Nexus S Android Development] JokerAce:
Save a script with NStools and go to a root explorer type of file manager and locate /data/data/mobi.cyann.nstools/settings/xxx

where "xxx" is your script name that you saved using Nstools.

Basically the script generated by NStools have options for you to enable:

-BLN

-BLX

-etc

"1" means enable while "0" means disable.

Copy the file to /etc/init.d/. Open the file and edit the content -

1. Remove the "# v.16" and add "#!/system/bin/sh" (

without the quotes

)

2. Look for "echo 100 .... /scaling_min_freq" and remove this line. You do not need this line to set min_freq of the CPU.

3. For voodoo settings? Find your best combination and write down all the values! Now under the last part of the script, input:

4. Save

5. Change permission of the file to

- Tick "Read" for all (i.e. owner, group and others)

- Tick "Write" only for Owner

- Tick "Execute" for all

- Press OK

6. Ensure and double ensure that NStools' option to "run-on-boot" is uncheck.

7. Reboot.

Well, all these above works only if the kernel and ROM supports init.d execution. Just so you know.

Pro-tip:

To help Bedalus with kernel issues, he needs last_kmsg.txt

Under terminal type:

1. su

2. cat /proc/last_kmsg > /mnt/sdcard/last_kmsg.txt

Why you should pull last_kmsg and not kmsg? Explained here.

Next, upload last_kmsg.txt to the thread.
[Nexus S Android Development] technogravy:
Do you then need to uninstall nstools? Is there anyways to check the idle stats without opening nstools?
[Nexus S Android Development] :
I don't think there's much point doubling my workload to maintain the ICS version. Why are people still using ICS anyway?
[Nexus S Android Development] :
You could uninstall nstools. There is a way of checking using the terminal emulator.

You can execute cat /sys/class/misc/deepidle/idle_stats
[Nexus S Android Development] :
Actually, are there any app developers out there who could provide a widget to show the contents of this file with refreshes every fifteen seconds or something?
[Nexus S Android Development] Naa Laa:
MIUI is still on ICS.. Thanks for all the hard work :)
[Nexus S Android Development] alen1901:
3.5 working great so far. :)

Sent from SpeedMachine i9023
[Nexus S Android Development] pan1980:
with slimjb and xenonhd roms i dont get any deep idle top off stats, i know the issue for slimjb i thought it would work with xenonhd, which rom do you use for proper working of deep idle ?
[Nexus S Android Development] :
It'll work on stock since asphantix fixed the framework. I know it works on cyanogenmod based roms
[Nexus S Android Development] gregorypeg1000:
Since bedalus told that the idle stats should be increased with any backround process, i turned on sync but the stats werent increased after 5 minutes.Then i was listening music with screen off and also the stats werent increased.So the DI was broken.i dont have antutu in my phone.Something else brakes it.I disabled it for now.
[Nexus S Android Development] :
See if you can figure out what it is!
[Nexus S Android Development] italia0101:
So far running great on stock . Seems smoother
[Nexus S Android Development] tchaari:
You should check if the rom you use is compatible with DI
[Nexus S Android Development] :
Hi tchaari, trusted advisor. My kernel keeps rebooting. Should i go back to 3.0.31?
[Nexus S Android Development] KrisMurdrum:
3.0.39 on Green Bean works wonderfully. I had less than 5% drain while I slept. It is snappy and lagfree, so double kudos for you my man.

Carved into Runes with my Magic Rune Stone.
[Nexus S Android Development] :
Thanks for all the kind words.

I think what i need to do is really bite the bullet, and work out which commits are unstable.

I can do it by selectively reverting individual commits that make up the mainline patches. It'll be methodical, but it will take time. A long time.........
[Nexus S Android Development] alen1901:
I had SOD with 3.5. I pulled battery and turned on phone. Is kmsg saved? Worth sending it to you?

Sent from SpeedMachine i9023
[Nexus S Android Development] italia0101:
Just lost all gsm signal again on 3.5 on stock
[Nexus S Android Development] tchaari:
Seems a wise approach. Take your time buddy. Only the result count ;)

You can start by taking out deep idle and bln. All the trouble seem to be from there :)
[Nexus S Android Development] alen1901:
Bln is only problem when set to blink as i know. I never had problem with what. Its DI that is causing problems. I would say.

Sent from SpeedMachine i9023
[Nexus S Android Development] 309041291a:
What kind of battery are you guys getting? Only thing keeping me from switching is that + my beloved Voodoo haha.

Nexus S. (GSM i9020a)

Paranoid (1.97a - 4.1.1)

Air Kernel (Week 171 - Voodoo)

Ondemmand (1000/200)

Deep Idle (On - Deadline)

Black Exodus (Inverted apps)
[Nexus S Android Development] d_phekt:
Just flashed 3.5 and seems to be great so far. It does seem a little smoother.
[Nexus S Android Development] Articudos:
Oh, I was too late maybe..

I was using previous version, and init.d installer..

http://xdaforums.com/showpost.php?p=26249862&postcount=1252

Anyway, u released v3.5, I'll flash it right away:)
[Nexus S Android Development] :
Remember, the current version is only stable until it reboots. Wipe caches and fix permissions recommended.
[Nexus S Android Development] gregorypeg1000:
I use the last version of euroskank.I did a fresh install and tried with apolo.Di was working for maybe 30 minutes.Then it broke without opening any other app than apolo and nstools.Unistalled apolo and tried with poweramp.After the reboot was working again for some time but then it broke again.No other apps installed.It may be a conflict with the rom.
[Nexus S Android Development] :
Okay, I'm removing deep idle. We wait for thalamus' IDLE2.
[Nexus S Android Development] gregorypeg1000:
Wait a little more.Doing some more tests.I think that nstools ****s up the measurements.
[Nexus S Android Development] :
Edit: New test version here: http://xdaforums.com/showpost.php?p=30122351&postcount=1375

This is out of date (PLEASE READ ANYWAY!):
[Nexus S Android Development] gregorypeg1000:
Finished testing.DI broke again.Nstools doesn't broke the measurements so...
[Nexus S Android Development] :
Can you test the version above please? I'm going to need as many people as possible to report back on whether it is stable or not. :p
[Nexus S Android Development] Articudos:
So... to fix deepidle breaking, ezekeel needs to look at the code?:)
[Nexus S Android Development] xjerlzx:
because kangy ultra rremix for jb isn't out =).
[Nexus S Android Development] marinierb:
I just installed V4. Are the defaults (ondemand and deadline) your preferred settings? I notice BLD is working. I can set it through the CM10 advanced settings. Nice. That's really the only option I want in a kernel. For the rest I usually run default values.
[Nexus S Android Development] tchaari:
Does it have high big mem please? I can't live without it :)
[Nexus S Android Development] Articudos:
Yes :)
[Nexus S Android Development] polobunny:
Two number 2 in your list bedalus. Might wanna rewrite that as 1 2 3 4 :p
[Nexus S Android Development] tchaari:
No I am only seeing 344 Megs of total RAM :)

bedalus, can you please add this to your to do list?

I am also seeing 3.0.31 in your build number. Is it correct?
[Nexus S Android Development] Articudos:
It can't be, what version are u using?
[Nexus S Android Development] djees:
Link for highbigmem patch in 2post is dead for ics

File not found
[Nexus S Android Development] :
Has anyone got a copy of that? I'll upload it to dev-host.

Thanks, I've added it to the list.
[Nexus S Android Development] Articudos:
ICS high bigmem patch

https://www.dropbox.com/s/j4ceft1k54us16q/BigMem_NS_ICS.zip

JB high bigmem patch

https://www.dropbox.com/s/ftenzcqu9fkxtdb/BigMem_NS_JB.zip

Long ago, I suggested you to include this lib files in kernel zip file by default:p
[Nexus S Android Development] pan1980:
I use version 3.5 do I need to flash high bug men patch? Right now I have 412mb usable ram.
[Nexus S Android Development] Articudos:
If video and camcoder works longer than 10 seconds, u don't have to
[Nexus S Android Development] vikingsail:
Now I see the problem. I'm on the ota version and the kernel seems working quiet well. I didn't overclock my device and it's working stable. Thx for your help bedalus.
[Nexus S Android Development] tchaari:
V4. The latest test version :)
[Nexus S Android Development] :
I've mirrored these and linked in the OP. Thanks ioplkj13!

I'll see about including these in the kernel .zip - just need to test first.

UPDATE: v4 for Stock OTA now linked in the OP also.
[Nexus S Android Development] xjerlzx:
just realised CPU min stuck at 200 icsv1.5b on nstools, rom toolbox, after setting it at 100mhz, is there anyone that can guide me to use the init.d script. sorry noob here =X
[Nexus S Android Development] towelboy:
Why is available memory just 343mb
[Nexus S Android Development] italia0101:
You cant get big mem on stock can you ?

Also I'm on 3.5 and turned off deep idle . So far so good
[Nexus S Android Development] alen1901:
I wont test v4 yet, i am preparing myself for going to seeside. But, on 3.5 my phone was awake a lot of time during the night., check screen. Maybe it needs to settle down. Interesting thing is, i didnt loose any battery, 1 or 2 percent.

Sent from SpeedMachine i9023
[Nexus S Android Development] Muvolt:
Is v.4 a joke? I mean, no bigmem, no BLN, no Deep Idle and an older source code? So what this Kernel is good for?
[Nexus S Android Development] alen1901:
Older source code doesnt mean that kernel is not good. He is trying to find a bug, to make the most stable kernel working with (allmost) everything needed - if possible. So there will be some test versions so people can report and help. You can stay on version before if you want, or if dont feel the need to participate. :)

Sent from SpeedMachine i9023
[Nexus S Android Development] Muvolt:
Was that bug in v3.5 so "severe" to make him get rid of all the extras? I think it works good in my phone...
[Nexus S Android Development] sykomaniac:
Don't use it then goddamit

Sent from my Nexus S
[Nexus S Android Development] alen1901:
Well, theres nothing wrong in being carefull. He wants to make stable kernel for EVERYONE. I will repeat, feel free to stay on 3.5 or 3.0.39. Nothing or nobody is forcing you to update. Please, dont be "rude" to developer. :thumbup:

Sent from SpeedMachine i9023
[Nexus S Android Development] Muvolt:
I'm not rude to the developer and I'm sorry if my post looked rude to him. I'm just bored with all those flashings, bugs etc...I thought that I had found the best Kernel and now we are back again. Anyway, thank you Bedalus...I understand the purpose of these recent changes.
[Nexus S Android Development] shivasrage:
When you come on this tread you must first click at Nexus S development.....and this is

what happens here...development...development has sometimes to go back and forth.

Thats it.

S.R.
[Nexus S Android Development] madd0g:
Kernel has nothing to do with wakelocks. JB does weird stuff with waking up, it's same on stock.
[Nexus S Android Development] alen1901:
I didnt have that on prevous build of codename and kernel. It might be related. But, on wednesday, good by tehnology world. So i will experiment only after 2 weeks from now with different combos. :)

Sent from SpeedMachine i9023
[Nexus S Android Development] caliban2:
Just got a reboot on 3.5, bootloop and no last_kmsg at all after pulling battery. Sorry. ^^

Guess going back and adding stuff one by one really is needed.
[Nexus S Android Development] :
It's a joke on the illiterate.
[Nexus S Android Development] :
JokerAce's concise guide is now linked in the OP. Thanks JokerAce!
[Nexus S Android Development] Imppy:
So nstools could actually create a script?
[Nexus S Android Development] :
Read the notes about v4 in the post above.

Yes, I can build them in.

v3.6 was a shocker for rebooting. It might not just be Deep Idle, there may be other unstable code too.

I need to be more gradual and cautious about adding stuff. Anyway, everyone happy with v4_test? I'm going to do a v4_test2 now. Will upload if my daughter naps long enough! :p
[Nexus S Android Development] :
Here is v4_test2: http://d-h.st/qbx (BUG ELIMINATION)

BLN is added.

I remember this was a source of almost continual myths about stability back when it was first introduced, but it's been considerably refined since then. Either way, I'll want at least 48 hours with no reported problems.

If problems are reported, I'll do my best to debug it.

Also, I've heard from thalamus, and he's going to continue working on IDLE2 but needs to test it himself to be sure of consistent test conditions. It could be some time until we see the results of this, but even with my limited understanding of his code, it's far more logical and efficient than the old version, and will hopefully have better power savings, and be reliable.

Anyway, please test!
[Nexus S Android Development] italia0101:
Oh right ... I thought the ROM needed to be big mem compatible to work
[Nexus S Android Development] Muvolt:
Yes, you are right, I didn't read that and I will try to follow your tests and be helpful.
[Nexus S Android Development] :
Thanks. Just be aware that regular visitors to a thread will not look kindly on those who haven't read it fully.

It's partly my fault for not making that information more visible. I'll put a notice in the OP.
[Nexus S Android Development] acrossy:
Either way... this looks promising! Good luck Bedalus ^0^)b
[Nexus S Android Development] 309041291a:
Can someone give me a screen shot or tell me what the default settings are for bedalus's smartassv2 governor?

Nexus S. (GSM i9020a)

Paranoid (1.97a - 4.1.1)

Air Kernel (Week 171 - Voodoo)

SmartassV2 (800/200)

Deep Idle (On - Deadline)

Black Exodus (Inverted apps)
[Nexus S Android Development] :
I had it on over night, no reboot, but had wifi off, and no data allowed on 2g.

The reboots may be due to some of the recent tweaks from Franco.

Can you copy your proc/last_kmsg?

For now we'll label .9 experimental

EDIT: Okay, the main download link now points to 0.8

If anyone gets a reboot please post your proc/last_kmsg here. Unfortunately I've got 2MB of data left before I get charged extra, but the new month begins tomorrow, so I won't be posting a fix today.
[Nexus S Android Development] :
That's a nice article! Thanks!

My wife doesn't even let the knife I use to spread marmite go anywhere near her toast, in case it 'taints' it. #truefact
[Nexus S Android Development] pan1980:
i am using 0.9 since released (coming from airkernel)

very happy with it, no issues yet.

i am using cybergr v14 rom, but i can not find any mpt settings.

which roms support mpt ?
[Nexus S Android Development] :
It's been reported that this works with Cyanogenmod, and I suspect any ROMs based on that. I personally prefer Slim ICS. Please, everyone, consider a donation to krarvind for making MTP available for our Nexus S :)

In other news, I found my phone frozen just now, running 0.9, so I'm going to look at the last_kmsg and see if I can decipher the cause.
[Nexus S Android Development] caliban2:
How long did it take with 0.9 to freeze? I'm reaching 5 hours and so far, so good. (btw, I really need to adjust to testing such a new kernel - never came to my mind to check if didle is there on 0.8 ^^)
[Nexus S Android Development] technogravy:
Using v9 for a few hours and no issues, its very smooth except for one thing - the min frequency keeps going back to 200 even after setting the freq to 100. Anyone facing the same issue?

Tested on slim 4.2.
[Nexus S Android Development] :
There is nothing remotely interesting in that log. Everything there is normal.

A hard lockup and no panic is never good though, it means that the whole lot has gone out to lunch including the watchdog which would normally reboot the system, which likely means that the apps processor has got wedged.

Could be many different things, Undervolting / Deep Idle / perhaps a deadlock somewhere, who knows...

This is why you should be conservative about what code you merge and not slap together random patches from all over the internet...
[Nexus S Android Development] Oodie:
**** . Reboots doesn't happen for me with 0.9 . I feel bad :P

°°° This comment is Sent from my Nexus S °°°
[Nexus S Android Development] caliban2:
Yeah, with every reboot it gets set to 200, despite nstools having 100 (everything else is applied though - I use different settings for smartassv2). However, once I've set it manually, it stays on 100 until the next reboot.
[Nexus S Android Development] spupuz:
same for me at reboot i get 200 instead of 100
[Nexus S Android Development] tchaari:
A bedalus product, so I have to try it :)

I think that it will be easier to consume than benchmarks :D
[Nexus S Android Development] Oodie:
have you gone somewhere or something . long time no see .

& word of advise , don't use this product . i tried it . it's really bitter :eek: ( I meant about marmite )
[Nexus S Android Development] :
That's normal, it's the minimum frequency being raised to 200 while the gpu is in use. Don't worry, the minimum is still 100.
[Nexus S Android Development] :
Deep idle is working fine in v0.7 so i think the likely culprit is the Franco tweaks. I'll remove one by one until it is stable again.

Oh, if it's the Ondemand tweak, running smartass instead will solve it. I'll run that for a bit, see what happens.
[Nexus S Android Development] Oodie:
oops . i'm running smartassv2 from the beginning . still no reboots .

on 3g , wifi tethering , tried with rune raiders ( game ) , deep idle on . tried everything .

I just can't get this to reboot :|
[Nexus S Android Development] technogravy:
Not really.. CPU spy shows it idling at 200.
[Nexus S Android Development] technogravy:
Long press the power button and hit reboot. :D.
[Nexus S Android Development] :
Hmm. That's not normal after all. I'm gonna reflash and see.

Ok, idk, 100mhz is working for me.
[Nexus S Android Development] Oodie:
Yay ! It worked :laugh: :cyclops:

:silly:

:silly:
[Nexus S Android Development] linuxxp:
Here:
[Nexus S Android Development] 309041291a:
Thanks. I always find bedalus's settings have the best battery life so I'm going to try these out.

Nexus S. (GSM i9020a)

Paranoid (1.97a - 4.1.1)

Air Kernel (Week 171 - Voodoo)

SmartassV2 (800/200)

Deep Idle (On - Deadline)

Black Exodus (Inverted apps)
[Nexus S Android Development] caliban2:
I'm quite certain deep idle wasn't the bad guy here. First, I had it disabled for the past 24 hours because I wanted to test something (didn't seem to be broken, but rarely kicked in). Second, I've been reading xda via tapatalk when it rebooted - even if enabled, didle would've been inactive.

But how good are current jb-roms as test-foundations? I've seen tremendous performance-gains with last 4 euroskank-roms, all with bedalus 3.4.39. So I don't think one can blame only kernel yet, too much going on with CM... (and aokp, miui)

Now running v4-test2. Good so far, though I seem to imagine a minimalistic loss of performance.
[Nexus S Android Development] niteh@wk:
Is this test2 version? I flashed test2 but NSTools says Governor not available. I also turn on BLN using NSTools but it doesn't look like BLN lights up when I receive an sms. I tried to wipe dalvik cache and cache, reflashed test2, same results. Could very well be my phone's settings.
[Nexus S Android Development] abhidoT38:
Do use nstools for Governor, use this app http://bit.ly/NwptJ3 :good:
[Nexus S Android Development] niteh@wk:
I'm using ROM Toolbox Pro and I can see the SmartassV2 governor. It's just that it doesn't have all the params like ramp up, ramp down, etc... I think same for No-frills. Thanks for the suggestions though.

---------- Post added at 02:36 PM ---------- Previous post was at 02:24 PM ----------

Third time is a charm. Wiped, reflashed, now BLN is working.
[Nexus S Android Development] :
I think this is definitely a factor.