yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] abhidoT38:
Try this one http://bit.ly/MSJZCY
[Nexus S Android Development] Muvolt:
It works nice for me too, but I feel that the loss in performance is quite bigger...there is noticeable lag in comparison with v3.5.
[Nexus S Android Development] :
Yeah, i think there's some other things I need to check.
[Nexus S Android Development] marinierb:
Do you have PM_FAST in v4? Because WiFi seems to be using a lot of battery.
[Nexus S Android Development] :
Yes, I prefer PM_FAST.

It drains more battery, but it's not a big difference. In fact, it's very useful and considerably more power-saving if you are actually using wifi (with the screen off, e.g. background downloads, streaming music, etc.)
[Nexus S Android Development] seriosbrad:
I'll flash v4 test2 and use it at for the rest of the night and tomorrow at work then report back tomorrow :good:
[Nexus S Android Development] JokerAce:
Hehe hit thanks here
[Nexus S Android Development] asphantix:
So since v4 is based on Samsung's source code 3.0.31 it isn't based on thalamus kernel anymore?
[Nexus S Android Development] :
Thalamus' kernel is rebooting too. Once i get to the point where i integrate the mainline patches, I'll know if the stability issues were caused by something thalamus changed (that might have been incompatible with the mainline) or if it's the patches alone. If it's the patches, then I'll rebase on thalamus' kernel.
[Nexus S Android Development] caliban2:
I just hope it isn't bigmem-patch acting up. :D v4-test2 shows our device really has a ram-problem with stock-configuration... (yes I know I could patch it manually, but the idea is to run this test until bedalus is convinced it's stable)
[Nexus S Android Development] Articudos:
Well, bigmem patch doesn't increase ur total ram, bedalus must disable camcoder and video...

Those lib files prevent FC.
[Nexus S Android Development] :
Yes, flashing those lib files has no effect on the total RAM, but does prevent FCs, but afaik this is only a problem on MIUI (ICS).

Morfic's biggermem will take us up to 393MB in total anyway.
[Nexus S Android Development] caliban2:
Ha, learned something then. :)
[Nexus S Android Development] leap_ahead:
hello i get lost here :P

so v4 test2 is bug elimination ..

if i flash with bigmem patch file i get more ram ?
[Nexus S Android Development] KrisMurdrum:
Not sure what deserves thanks the most.

Your kernel (the .39 one).

Your guide to kernel cooking.

Or your git.

Carved into Runes with my Magic Rune Stone.
[Nexus S Android Development] :
Haha definitely not my github, it's a bit of a shambles!
[Nexus S Android Development] Articudos:
Not miui only, pre-included in cm9.

First, kalim made it, next, krarvind applied in slimics, and kong's miui, wildestpixel applied in pete's rom

.. Not sure about sequence..

(History class..?:p)
[Nexus S Android Development] :
edit: deleted due to ioplkj13 better explanation.
[Nexus S Android Development] :
I see over a hundred DLs of the bug elimination versions (w/BLN + w/oBLN) and no reboots reported yet.

Still to do:

-Add my timeout fix

-Add biggermem

-Add 3.0.40 mainline

Can people PM me for the next test version please? I'll be back in about 9 hours.
[Nexus S Android Development] caliban2:
Hey, it was you who said you want test2 stable for at least 48 hours - it's not even 24 yet. :p
[Nexus S Android Development] smoka206:
I've been running "v3.4.39" since it was released, i have changed roms but I'm on Paradroid now and am going to stick with for a while. I have never had a reboot yet, I have deep idle on and listen to music quite often. Its been stable and fast. I would upgrade to a new version but this one just works so well. Thanks for the awesome kernel, I've tried the others and this is so smooth! Although if I set the clock to 1200 it will just freeze and reboot, I doubt that has anything to do with the problems encountered by others.
[Nexus S Android Development] seriosbrad:
4.0test2 has been stable for me throughout the day. I've had poweramp running for basically 7 hours and Trillian idling in the background.
[Nexus S Android Development] linuxxp:
4.0_test2 is stable for me too. All day use GPS with Sigic and I have no problems, no random reboots, no anything annoying.
[Nexus S Android Development] tchaari:
+1

very stable here too. Waiting for higher big mem version ;)
[Nexus S Android Development] alen1901:
I would recommend making kernel with all features (only without thalamus codes and without DI or idle2) based on googles sources. That way you can immediately see if some of this 3 "new" things are buggy.

Sent from SpeedMachine i9023
[Nexus S Android Development] tchaari:
Nice suggestion in my opinion ;)
[Nexus S Android Development] :
What? This is why i need more sleep. Next test version in 24h
[Nexus S Android Development] :
Who says i haven't already tried that? :p
[Nexus S Android Development] KrisMurdrum:
Hey bedalus.

you might want to redo this part of your guide

When I tried it it gave me an error message stating that it was outdated and directed me to

sudo apt-get install oracle-java7-installer

although I will admit I did get an error message with that one too :confused: and I ended up just going straight to Oracle's download page and dl'ed the jdk-7u4-linux-x64.tar.gz directly. After which I entered

tar -xvf ~/Downloads/jdk-7u4-linux-x64.tar.gz

in order to install java jdk on my ubuntu

-------------------------------edit

yes. you were right about the

is obsolete. Needs to be replaced with
[Nexus S Android Development] alen1901:
Bedalus i cant quote you, XDA app is having fun with me. -.- anyway, when did you do that, you didnt say anything nor you released it to public? :p

Sent from SpeedMachine i9023
[Nexus S Android Development] :
I was just amused because just minutes before i'd read that i'd just built one. Unfortunately the final addition of the last three elements seems to have led to a reboot. I don't know if it's the bln tweak, the biggermem, or the mainline patch, so I'll just stick to my original plan of upgrading one thing at a time.
[Nexus S Android Development] :
Thanks! I'll update the guide. Let me know how you get on!
[Nexus S Android Development] tchaari:
As bln is running fine without the tweak (blinking disabled) let's have biggermem addition only ;)
[Nexus S Android Development] towelboy:
v3.5 running super stable :D
[Nexus S Android Development] towelboy:
41 hours on v3.5 no reboots no nothin! i think v3.5 is better then v4 :D

EDIT: deep idle is enabled throughout the whole time
[Nexus S Android Development] shivasrage:
hey

same for me ...tested 3.5 since release ...nothing...

no reboots no sod´s.....running stable and smooth..:good:

what is normally responsible for reboots....??

why is there is so much different between phones..?

or is a certain situation on the phone causing that...?

S.R.
[Nexus S Android Development] alen1901:
Bln is working fine. Also bigmem(v3.5 kernel). No issues until now. So it could be some patches. But im thinking that DI is making problems to some people. I have DI enabled but i dont have problems when DI is not in use. I just had 1 freeze with mercury messenger in background and screen off(DI). Im trying to help. :)

Can you look at this, it looks interesting. Maybe it can be implemented in some future days if you like it and when stability issues are fixed. I copied links from air kernel thread.

[YOUTUBE]jri2BMQHHrs[/YOUTUBE]

source is here : http://xdaforums.com/showthread.php?t=1603808

Sent from SpeedMachine i9023
[Nexus S Android Development] caliban2:
Please, stop blaming didle for everything just because you've heard someone say it's garbage-code. Didle has been working fine for a long time... The problems with 3.5 certainly aren't caused by didle because when it crashed on my phone, didle was disabled and i've been using the phone. I literally watched it first freeze and then reboot.

Bedalus,

v4-test2 did fine for about 36 hours, but i'm back on 3.4.39. Turns out phone becomes very laggy without bigmem. ^^ Patiently waiting for your next clou.
[Nexus S Android Development] alen1901:
I didnt say its garbage, im just assuming because before week or two ezeekiels DI didnt work on jb, so there still might be some problems. Or im wrong? Bedalus will figure it out sooner or later.

Sent from SpeedMachine i9023
[Nexus S Android Development] asphantix:
Had no reboot with any version of this kernel. I'm on stock OTA maybe the roms you are using are unstable or their tweaks are conflicting with the kernel?
[Nexus S Android Development] alen1901:
Nope, there was 1 post, ota stock, and he had a reboot. Hm.

Sent from SpeedMachine i9023
[Nexus S Android Development] gmorel4:
May your days be long upon the earth.
[Nexus S Android Development] :
I can't add bigger mem until after bln tweak.
[Nexus S Android Development] :
Ha, that looks like fun. I'll take a look at it. I hope keeping the buttons awake is not a source of excessive battery drain.
[Nexus S Android Development] :
Actually I can. I suspect neither tweak will cause problems. If there is a problem, I will remove one of the tweaks to confirm.

Here is v4.1_test: http://d-h.st/Wzp

-Biggermem

-My BLN tweak

There is a new setting:

echo 1 > /sys/class/misc/backlightnotification/blink_finalstate

if you want the BLN to stay on after it times out.

echo 0 > /sys/class/misc/backlightnotification/blink_finalstate

if you want the BLN to turn off after it times out.

The time it takes before it times out = 450 * (1.02)^<0.5*max_blink_count> ms

... this is regardless of whether you have blinking enabled or not. So if you want the notification light to stay on, you must echo 1 to blink_finalstate.

My BLN tweak affects blinking time: each delay between blinks increases by 2%
[Nexus S Android Development] technogravy:
This has the two features I need (apart from bld).. Downloading now..

Is bln and the time out enabled by default?
[Nexus S Android Development] caliban2:
Sweet, plus 3mb of ram (396). :p

Let's see how it does. One thing I noticed right away: again just that wee bit less snappy than 3.4.39. But it shouldn't deteriorate as much as v4-test2 did with time, thanks to biggermem. *fingers crossed*
[Nexus S Android Development] alen1901:
If this is tweackable, like bln/bld, we could put timeout for keys stop being awake. But if it drains battery much, no thanks. :p

Sent from SpeedMachine i9023
[Nexus S Android Development] polobunny:
The biggest drain you would get from that is having your phone in your jeans pocket, face towards your leg. All the presses will get registered and bam, there goes your battery.

Edit: No point in timeout on the slide. That makes the whole thing pointless if you have to press the power key to make them useable again. :p
[Nexus S Android Development] technogravy:
Noticed a bug on 4.1, happened twice when I unlocked my phone, it took 10 seconds for the display to come on.. Seemed like an sod at first but then it wakes up
[Nexus S Android Development] seriosbrad:
Strange, I just had a reboot on 4.0 Test2. I wasn't doing anything, the phone was screen off sitting on my desk.
[Nexus S Android Development] irishrally:
Oh yeah, one post? Case closed.
[Nexus S Android Development] skinner12:
On jellybro i have a lot of lag.. For example, it takes up to 20 seconds to open messaging app..

Nocerino's Rulez with RAScarlo's ROM features TriNitY ;)
[Nexus S Android Development] :
Uh, BLN I think is disabled by default and if you want the LED to ultimately stay on, you need to echo 1 to blink_finalstate

This is a new problem since v4_test2? What ROM?

What ROM was this?

Is this only with my kernel? Is it when you first open the app, or every time? Which ROM?
[Nexus S Android Development] :
v4.2 will be merged up to 3.0.34. Why only 3.0.34? I helped stress-test matr1x kernel for mk a while back back (on his ICS v22.0) when for some reason updating to 3.0.35 caused unpredictable reboots.

If it does turn out to be a problem with 3.0.35, I can easily eliminate the problematic patch(es) by a systematic set of reverts, with decent periods of testing in between.

I'll post the link for v4.2 tomorrow assuming there isn't a sudden flood of last_kmsgs for v4.1
[Nexus S Android Development] Phoenix Wright:
I had 2 reboots on 4.0 test 2, one after the other, here's the last kmsg (I think it might be useful this time)
[Nexus S Android Development] :
Sorry about the reboot. That one was definitely my fault!! It's my BLN tweak. I forgot to reinitialize the blink-length timers after it times out.

It's fixed in tomorrows version. :)
[Nexus S Android Development] Phoenix Wright:
Oh thanks :) I thought you added the tweak in 4.1 though?
[Nexus S Android Development] :
Good point. That means it's definitely not my tweak, and might just be bln! Needs further investigation.
[Nexus S Android Development] tchaari:
Nice bedalus, I am really loving the fact that you returned to the source base (directly from samsung).

For me 4.0 is stable and BLN work good (without blinking) and the capacitive light stays on (without blinking) until I unlock the phone.

Good work man ;)
[Nexus S Android Development] technogravy:
I had some Android os drain on idle after 4.1. Could this be a kernel bug? using slim bean
[Nexus S Android Development] :
I probably shouldn't say that's definitely my bln code, so I'll just say it's probably definitely my bln code, but it should be sorted in the next version. Probably. :p
[Nexus S Android Development] towelboy:
v3.5 ftw!

1.2Ghz oc

bln on

bld on

deep idle on

61 hours of fine smoothness no laggyness no nothin! also great battery life

kalim's official cm10 rom

smartassv2 & cfq

Edit: i love your kernel
[Nexus S Android Development] technogravy:
Thanks, for now I'm heading back to 3.5 that was by far your best so far, will test 4.2 when available
[Nexus S Android Development] :
EDIT: This version has been reported to be working very well!

New versions for AOSP/AOKP/CM/Custom ROMs

...and also an update for the Stock OTA version:

Stock OTA only: http://d-h.st/f5z

marmite_v4.2: http://d-h.st/ncp (for all other ROMs)

Just a reminder of the feature set:

- CFQ scheduler. It's a tiny notch down from deadline in performance, but very consistent.

- Deadline I/O scheduler adjusted for flash for lowest I/O latencies (thanks thalamus)

- SmartassV2 governor, with correct values for the Nexus S

- Ondemand, with values balanced for good performance and battery saving

- Removed pointless governors

- Removed noop scheduler

- BLD

- BLN blinking is tweaked, and timeout behaviour is customisable

- OC to 1.2GHz (thanks daXmax)

- No UV (pointless source of instability)

- PM_FAST (fast wifi with screen off: power saving for downloading files, but slightly higher power use when idle compared to PM_MAX)

- Morfic's colours

- Voodoo colours (but no gamma control, due to morfic's tweak)

- Stock kernel base patched to 3.0.34 linux mainline

- Made the codename 'marmite' official :p

Thanks for the continued support from everyone who has been putting up with the bug elimination process! I think the reboot bug must be in the mainline in 3.0.35 somewhere...

...so these versions are patched up to 3.0.34 only. I'm going to build a 3.0.35 version and see if I start getting reboots.

@testers, please remember to try to collect the last_kmsg

i.e. copy /proc/last_kmsg to /sdcard then rename it to last_kmsg.txt and attach it when you post a reply in the thread (use the go advanced button to do attachments).
[Nexus S Android Development] xjerlzx:
Deep idle/ idle 2? Or none
[Nexus S Android Development] granets:
lol, I was about to flash 4.2. So, I'll be waiting for 4.3 then. Currently running 4.0 and it's been a good experience for me, no problems, except for a couple of little buggs, but those are from the AOKP rom I'm using. Keep it up mate :)
[Nexus S Android Development] leap_ahead:
bedalus i use rom that called stock ota ... which version i must choose ??

because i use the Marmite v4.2... not the stock version ...
[Nexus S Android Development] 4tticuz:
Do you suggest to use NSTools with your 4.2 kernel for JellyBro?
[Nexus S Android Development] :
None. I'm waiting for idle 2
[Nexus S Android Development] :
You can use it, but it may break the system's ability to rest at 100mhz. Or you can use an init.d script. You can find help on how to do that in the op
[Nexus S Android Development] 4tticuz:
Kernelversion displayed: 3.0.34-bedalus-03189-gd123b77

Is that correct?!
[Nexus S Android Development] xjerlzx:
Yes pls read his posts
[Nexus S Android Development] 4tticuz:
Sorry, have seen it too late :/

Other question: I deleted NSTools and flashed the kernel. BLN is not working and I dont get it how to enable it.

Could you help me please?
[Nexus S Android Development] sidnoit22:
Woah i was about to flash 3.5. Thanks mate..will tell you if got any issues. :good:
[Nexus S Android Development] Drizzy xS:
Bedalus just wondering. Why did you get rid of interactive scheduler isn't that how JB is meant to run ?
[Nexus S Android Development] xjerlzx:
U use a custom kernel to get more performance/battery. I suppose he based on his research and only add 2 governors that he proved with most battery savings with performance. U could follow his guide on how to build a kernel if u need interactive badly
[Nexus S Android Development] towelboy:
I originally thought that too... until I tried smartassv2
[Nexus S Android Development] Drizzy xS:
Faster?
[Nexus S Android Development] 4tticuz:
Sorry, but how do you enable BLN without using NSTools? :(
[Nexus S Android Development] technogravy:
How are you changing governors? I see it greyed out on nstools

---------- Post added at 09:13 PM ---------- Previous post was at 09:12 PM ----------

4.2 seems really good so far.. Very smooth.. Will report back with more details. But BLN working fine for now
[Nexus S Android Development] leap_ahead:
go to cwm and fix permission !
[Nexus S Android Development] Phoenix Wright:
First bug report... on 4.2 minimum clock with smartassv2 is 200 MHz... even with an init.d script.
[Nexus S Android Development] yihtang:
Just upgrade from 3.4.39, v4.2's speed improvements are very noticeable. Thumbs up
[Nexus S Android Development] caliban2:
No. Either remove that minfreq-line from your script or stop using nstools, rom-cpu-settings or whatever.

I reflashed 3.4.39 just for comparison and they're on par, definitely no speedup. Not complaining though, fast is fast is fast. :)
[Nexus S Android Development] gabling23:
if i create an init.d script like in the guide of the op, can i keep only the firsts lines because the only things that i want are bln and bld, to set the governor and the scheduler i use setcpu..
[Nexus S Android Development] Phoenix Wright:
Contents of my script:

#!/system/bin/sh

echo 1 > /sys/class/misc/backlightdimmer/enabled
echo 30000 > /sys/class/misc/backlightdimmer/delay
echo 1 > /sys/class/misc/backlightnotification/enabled
echo 1 > /sys/class/misc/backlightnotification/in_kernel_blink
echo 600 > /sys/class/misc/backlightnotification/max_blink_count
echo 100 > /sys/class/misc/batterylifeextender/charging_limit
echo smartassV2 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo 800000 > /sys/devices/system/cpu/cpufreq/smartass/awake_ideal_freq
echo 800000 > /sys/devices/system/cpu/cpufreq/smartass/sleep_ideal_freq
echo 800000 > /sys/devices/system/cpu/cpufreq/smartass/sleep_wakeup_freq
echo 40 > /sys/devices/system/cpu/cpufreq/smartass/min_cpu_load
echo 80 > /sys/devices/system/cpu/cpufreq/smartass/max_cpu_load
echo 400000 > /sys/devices/system/cpu/cpufreq/smartass/ramp_down_step
echo 200000 > /sys/devices/system/cpu/cpufreq/smartass/ramp_up_step
echo 40000 > /sys/devices/system/cpu/cpufreq/smartass/down_rate_us
echo 20000 > /sys/devices/system/cpu/cpufreq/smartass/up_rate_us
echo deadline > /sys/block/mtdblock4/queue/scheduler
echo deadline > /sys/block/mmcblk0/queue/scheduler
echo 1200000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

On 4.1, minimum clock is 100 MHz, on 4.2 it's 200 MHz... I check with the "performance" tab in the cyanogenmod settings
[Nexus S Android Development] caliban2:
Script is fine. Performance-tab is one of the rom-cpu-settings I wrote - forget it, it reports the wrong value (and even may really set minfreq to 200 on closing). Use cpuspy to check what's going on.
[Nexus S Android Development] 4tticuz:
Do you use nstools to configure kernel options?
[Nexus S Android Development] Muvolt:
I second that...but it needs to be faster/smoother (if it is possible with its structure).
[Nexus S Android Development] :
Um, idk really, i just don't like it. I think my on-demand is smoother.
[Nexus S Android Development] :
Caliban is right. Use cpuSPY to check. Make sure if nstools is installed that restore-settings-at-boot is unchecked.
[Nexus S Android Development] :
Follow the link in the op for jokerace's guide, and check out an example of a script a few posts up.
[Nexus S Android Development] :
I definitely feel like this kernel has some magic happening. I may have a little breather before tackling the planned mainline update.
[Nexus S Android Development] kmjo29:
Hi guys quick question. I want to disable bln on this script. Anyone with quick help on disabling bln or correct properties to disable it? I appreciate it!
[Nexus S Android Development] :
Same advice!
[Nexus S Android Development] pan1980:
Any chance for implementing v6 superchanging script?
[Nexus S Android Development] :
It's not effective for the nexus s. I've got a research thread on it, see my signature for the link
[Nexus S Android Development] technogravy:
I agree, 4.2 seems to have bettered your earlier best in 3.5...

Very stable, battery friendly and no bugs noticed so far.
[Nexus S Android Development] gummie:
In marmite 4.2 do I have to Flash the Bigmem Hack (patch) or its already a Feature of the Kernel?
[Nexus S Android Development] Articudos:
It depends on ur ROM, flash it, no harm maybe:)
[Nexus S Android Development] towelboy:
I use both the settings -> performance and the app no-frills cpu control

---------- Post added at 12:26 AM ---------- Previous post was at 12:25 AM ----------

v4.2 is the new v3.5 :D
[Nexus S Android Development] caliban2:
Why, is it crashing without producing a last_kmsg?! :laugh: :silly:
[Nexus S Android Development] gummie:
I'm currently using euroskank latest CM10 I cant seem to discern if Bigmem is with the ROM already. Anyway I thought Bigmem was a Kernel Feature, so if you flash over marmite to cm10 it basically get rids all cm10 kernel features. Correct me if I'm wrong.
[Nexus S Android Development] :
! :D

Here's a real contender for the next v3.5...

(If you don't understand that joke then stick with v4.2 - linked in the OP)

marmite_v4.3: http://d-h.st/kms (BUG ELIMINATION VERSION)

Everyone should stick with 4.2, unless they are interesting in helping finding out if if mainline 3.0.35 has some sort of issue that causes reboots. :p
[Nexus S Android Development] :
I'm not sure what features the CM10 kernel has. My free memory goes up to 396 MB. There's another 8MB lying around somewhere, but I haven't researched it yet.
[Nexus S Android Development] :
Lol, i just answered your q in the PA thread.
[Nexus S Android Development] xjerlzx:
Just add in? Or need to delete any part?

Edit

Oh I figured how alr hahaha I'm dumb lol
[Nexus S Android Development] :
Good times!
[Nexus S Android Development] xjerlzx:
Hmmm not sure why but SDboost value still doesn't change in sd-booster app.
[Nexus S Android Development] towelboy:
No, v3.5 was the best imo but now 4.2 is even more smooth and fast.

---------- Post added at 02:20 AM ---------- Previous post was at 02:19 AM ----------

@bedalus What's the difference between mainlines?
[Nexus S Android Development] Muvolt:
I got v4.3...I'm going to report here if I see anything strange. Thanks!
[Nexus S Android Development] :
http://www.kernel.org/pub/linux/kernel/v3.0/ChangeLog-3.0.35

You can replace the .35 with any number up to .40 to see the changes introduced in each patch. Each mainline patch is a collection of fixes for specific issues in the Linux kernel, but some fixes have no impact for our device.
[Nexus S Android Development] dkm911:
Is the tuned Interactive governor included in 4.2??? Thanks!!