yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] leap_ahead:
big problem on 3.4.3 i flash it and i lost data usage settings in menu !!

flash 3.3 all ok now
[Nexus S Android Development] caliban2:
+1

Just that I don't see it as a "big" problem. :p
[Nexus S Android Development] leap_ahead:
i want to se how many mb i download for that ,,,
[Nexus S Android Development] :
I've heard this issue from another user recently, and it appears to be some incompatibility with the stock OTA. I'll put it on my list of things to check out. It could be something to do with the ramdisk. I had to modify it to make it compatible with cm based ROMs. If I compare the ramdisk from the stock OTA to what I'm using now, if there's a difference, hopefully I can add it in.

It's exactly the same as thalamus' version.

I think having the backlight on could take the drain from 1% ph to 4% per hour, so it's not the whole story. Sounds like an app. But I will add BLN to the list.

I just ran a drain test overnight, and it registered 400MHz for the entire night. It'll only accumulate 400MHz time if you're playing music. If the screen was off, and there was no activity, then the most used state will be deep sleep. Perhaps I misunderstood you?

Oh yeah... that is kinda strange. I might have to revert 3.0.39. It's causing weirdness.
[Nexus S Android Development] leap_ahead:
i will wait for stable version like 3.3 ...
[Nexus S Android Development] caliban2:
3.4.3 also breaks GPS and has a rather long boottime. Flashed back to 3.4.2 and got a fix in 8 secs, boot is back to normal. :)

Lemme know if you can't reproduce, will get a log then.
[Nexus S Android Development] vis80k:
checked by charging phone to 90+% then disconnect with bln off. no notification sent. still the android OS was at the top of battery usage list at near 70+% again.

anyway, flashed 3.4.3. android OS is now at the bottom of the list.

this is rather strange because 3.3 with paranoid 1.9.2 did not have this problem. maybe just the wrong rom+kernel combo...

---------- Post added at 05:35 PM ---------- Previous post was at 05:34 PM ----------

+1

this was handy when I wanted to track down which app is pulling data when I don't expect any.

---------- Post added at 05:35 PM ---------- Previous post was at 05:35 PM ----------

3.4.2 giving you data usage in settings back?
[Nexus S Android Development] caliban2:
Jup. As a matter of fact I like 3.4.2 pretty much, seems stable to me.
[Nexus S Android Development] :
In v1.4d was it 404mb? I'll check that.

I think I know what's happened here. I had to restore my ICS branch from a commit reference, and it wasn't the final reference, so there's some crap that I sorted out that got un-sorted. It's like it went back in time to v1.4c instead of 1.4d. I can see what I need to fix looking at my github webpage actually. I'll fix the memory, and I should be able to sort out your NSTools stats crash too.
[Nexus S Android Development] :
That's because in 3.4.2 I failed to merge in 3.0.39! So even if it says it is, in fact it is actually still 3.0.38!
[Nexus S Android Development] madd0g:
Dude seriously, is that signature crap really necessary ?
[Nexus S Android Development] vis80k:
where's 3.4.2? I can't seem to find the link for it.

3.4.1, I found, then the next one I can find is 3.4.3. anyone care to repost the link?
[Nexus S Android Development] :
There's some stuff in your logcat about lulzactive/conservative governors coming from the dalvic VM. Did you try wiping cache?
[Nexus S Android Development] :
Yeah, I think I will revert the attempt at 3.0.39. It looks like more trouble than it's worth. I'm just going to fix v1.5 first...
[Nexus S Android Development] vis80k:
thx. makes no sense that they are there coz there is no jb kernel with lulzactive...and I clean installed current rom...

anyway thx for taking a look. will clean dalvik. btw going back to 3.3 kernel...android os is keeping its place at the bottom of the list. ;)
[Nexus S Android Development] :
I pulled it because I'd made a mistake. I hadn't merged in 3.0.39; I'd only merged in the label that said it was 3.0.39, so it was in fact still 3.0.38.

I'm going to fix v1.5 and then I'm going to revert back to 3.0.38 for v3.4.5, which will be in about an hours time.
[Nexus S Android Development] nexususer1:
No problems with 3.4.3 so far, seems really stable plus it's fast. Good job :)
[Nexus S Android Development] :
Hahaha, thanks :D

Unfortunately there are plenty of problems with the current build; read some of the posts above!

Everything seems stable, until it doesn't. :p

OK, v1.5b: http://d-h.st/BhK

-400MB RAM

-More sensible DI freq fixing code

-Wipe cache and do some interpretive dance.
[Nexus S Android Development] nunogilberto:
recently i'm running v 1.5 on latest CM9 nightly... it runs very well, and the battery life looks awesome... and yes, it's 397 MB in v 1.5
[Nexus S Android Development] meisze:
Use 3.4.3 playing Temple Run ,it lags after jumping . So restore to 3.4.2 .
[Nexus S Android Development] :
Move to v1.5b for more memory.
[Nexus S Android Development] :
Well, everything is fixed, but actually I think the problem was my config, which I should probably stop messing around with.

I'll just try the 3.0.39 merge one more time, and if it fails, I'll upload the working 3.0.38 version

EDIT: I might just upload both, then users have the option!
[Nexus S Android Development] gregorypeg1000:
For me the 3.4.3 version works good.stable,good performance.No reboots or locks with deep idle.The only problem is that the gps is broken.
[Nexus S Android Development] leap_ahead:
3.4.39 is ok to flash ?
[Nexus S Android Development] :
Two versions, the same except for the linux merge:

linux 3.0.38: http://d-h.st/JRL

linux 3.0.39: http://d-h.st/WHn

I think 3.0.39 is now fine, so try that first!

Is Data Usage menu item restored?

Is GPS working?

Is boot time normal?

Thanks for testing!
[Nexus S Android Development] JokerAce:
I see. Alright I get what you mean. Anyway how to check if my script is working. If I enable deep idle under advance settings in paranoid android rom, the 200mhz came back again.

---------- Post added at 07:45 PM ---------- Previous post was at 07:41 PM ----------

Yes dog. It is my personal preference. Your condescending sig is the one not required. Anyhow, you could just PM to tell me and not poop on this development thread.
[Nexus S Android Development] caliban2:
All positive. :)
[Nexus S Android Development] :
Yay. But also, that'll teach me for screwing with this config.
[Nexus S Android Development] DarkhShadow:
Bedalus, I got a kernel panic reboot on 3.3(yes not up to date but take a look anyway) do you have a email I can send to? I'm away from a PC and can only attach imgs via tapatalk :/

Sent from my ice cream powered Nexus S
[Nexus S Android Development] :
Thanks, just post it later, I'm off to work now anyway :)
[Nexus S Android Development] DarkhShadow:
Ah, k then :P

Sent from my ice cream powered Nexus S
[Nexus S Android Development] caliban2:
There's this thing called "Browser" on your phone. Or maybe it has another name.

Quiet now, don't tell anybody, but you can use it to access XDA as well! :p
[Nexus S Android Development] DarkhShadow:
Selecting files with the file chooser in browser does not work for me

Oh yes, and my browser dies due to a fatal error I have yet to find out if its kernel or ROM related

Sent from my ice cream powered Nexus S
[Nexus S Android Development] JokerAce:
installed the 1.5b, the mem is now 400 instead of 397. :good:

Btw, anyway to test if my script is working? Or it will definitely work without the need to test it.

EDIT: My script is called 97tools while your's is 90bedalus. Does it matter? I picked 97 because 90 is taken by 90userint. Somehow I feel that it's not working because the min value is still 200, the battery charge beyond 95% tho I set 95% for BLX..
[Nexus S Android Development] vis80k:
try with BLD on with 2000ms, so you know the script worked when your buttons turn off soon after boot.

or first set it to something real long, then on the next reboot to 2000ms
[Nexus S Android Development] DarkhShadow:
Here we go
[Nexus S Android Development] sidnoit22:
Now that's a good Kernel just got home and flashed 3.4.3, have to see Deep Idle is working! ( YAY) (:victory:)

And there is one request can you add VOODOO COLOR? :confused: just asking.. :p
[Nexus S Android Development] Icecoldmeat:
I am still very happy with your kernel bedalus. Using it on the latest CM10 kang (Euroskank hosting). Today I had 3hr screen on time, with heavy usage and 16hr total. Deep Idle is working fine too, keep up the good work! :)

Sent from my Nexus S©
[Nexus S Android Development] KrisMurdrum:
I flashed Marmite 3.4.3 on my Androxite 3.0 yesterday. I set gov to interactive from the first boot up and did not have any issues untill I set the Max clock to 1200. Then my phone froze for 20 seconds and rebooted as soon as i tried to home out of ROM Toolbox. Then I had another reboot when I opened the app drawer after boot-up finished. I put the last_ksmg in a zip, without compression, to comply to file size restriction
[Nexus S Android Development] madd0g:
Don't overclock? Lmao.
[Nexus S Android Development] nexususer1:
Can't boot your kernel using stock. Keeps getting stuck at android 4.1 boot animation.
[Nexus S Android Development] :
I had a look through your last_kmsg and it seems to be all PVR related. I did mess with some PVR config settings, but they are back to normal in the recent releases. Update, and hopefully the issue never returns!
[Nexus S Android Development] KrisMurdrum:
Haha, I know. But this is the first time I've not been able to over clock.
[Nexus S Android Development] :
vis80k suggests a good solution. You could also add echo marmite > /data/local/tmp/test.txt

...when you reboot, the script will write the word marmite into the test.txt file. You should check the time/date stamp of the file matches with when you boot up.

Your file name is fine. The permissions might need to be correct (not sure if this really matters actually) but you have to have

#!/system/bin/sh

as the top line.

If you try to set the minimum frequency, it will break the 100 minimum for some reason. Just delete the line that sets min. Let us know if you're still stuck.
[Nexus S Android Development] :
Voodoo color is in here. It's slapped on top of morfic's colours, so it's slightly customisable (although you can't set gamma).

I doubt it's overclock if you can do it with other kernels. I expect you need the latest version and cache wipe.

Yeah, it's not working with stock. It's on my to-do list.

I'll see if I can sort it out now actually.
[Nexus S Android Development] vis80k:
3.4.39 working great here! no reboots so far.

no android OS hogging, boot time actually feels shorter, data usage in settings showing normally.

however, the bln timeout doesn't seem to be working... I am setting it with nstools generated script. if nstools doesn't use proper script, could someone provide a script that works for the bln timeout?

edit. battery drain on idle was superb as well. 3.3 gave me a little over 1%(closer to 2%) per hour, but 3.4.39 gave me less than 1% per hour.
[Nexus S Android Development] Articudos:
Using 3.3 and v3.4.2, kakaotalk(it shows wakelock) keeps drainig my battery 10%per an hour(data off)..Is this JB prob?
[Nexus S Android Development] gregorypeg1000:
Application problem i think. since kakaotalk is an im app.Try to uninstall it and use an alternative.
[Nexus S Android Development] xjerlzx:
I think I feel an improvement in battery life in 1.5b
[Nexus S Android Development] caliban2:
Just passing through, 3.4.39 is still doing great! :good: :victory:
[Nexus S Android Development] nexususer1:
Thank you for your feedback Bedalus. (kernel not working on stock).

I had to switch to air kernel for a moment and I noticed that R_data's 65 fps kernel seems so much smooth. Is there any way you could implement 65fps mod into your kernel? Your kernel is extremly stable but air kernel seems to make the transitions faster and smoother. Would be great if you and r_data worked together to make one very stable kernel :)
[Nexus S Android Development] gregorypeg1000:
Is there any chance to make the kernel more overclockable?Something like 1.3ghz or 1.4?
[Nexus S Android Development] italia0101:
Did ya figure out why it didn't boot with stock ? Am patiently waiting to flash :)
[Nexus S Android Development] gmorel4:
Is anyone else having USB Mass Storage issues with 3.4.39?

---------- Post added at 02:28 PM ---------- Previous post was at 02:09 PM ----------

Nvm, tried flashing a different kernel, and am still having the USB problems, must be the hardware of my phone :(
[Nexus S Android Development] xjerlzx:
1.5b

1.5b all great, tried MTP for the first time. notice a big speed improvement!
[Nexus S Android Development] leap_ahead:
put it on other port on your pc
[Nexus S Android Development] gmorel4:
I did, I'm on my work PC using my usb cable from my Kobo, the usb cable works fine with the Kobo and computer, I will try the cable that came with my Nexus S and on my home desktop when I am home.
[Nexus S Android Development] jabbeboy:
Does the newest version have voodoo colors? If not, is the colors modded anyway? How is this kernel?
[Nexus S Android Development] :
Thanks! I'm really happy with it. It took a long time to work out the kinks. I definitely took two steps backwards for every step forwards.

r_data does a lot of modifications. My ethos is to try and keep that to a minimum. I just want a particular feature set and for it to work well. 65 FPS drains battery faster, and for me that's a good enough reason not to include it. I may consider a lower frame rate for battery saving as an alternate version in the future.

No. I only included 1.2GHz as a special favour for daXmax. I don't use it. This is my personal kernel, I'm just sharing. Please feel free to make suggestions, but be prepared to hear a no.

Yes, I thought it might be differences in the ramdisk, but when I compared mine to stock, there didn't seem to be anything obviously superfluous or deficient... I could try building with a stock ramdisk, just as a test version? If it still won't boot it proves the problem is not with the ramdisk.

MTP is the bomb!
[Nexus S Android Development] :
We sort of have voodoo colours here. We have morfic's colours, and voodoo on the top. So, gamma cannot be set, but RGB can.
[Nexus S Android Development] DaXmax:
So dude, is MTP working properly on v3.4 JB?
[Nexus S Android Development] :
Yeah, I tested it. You need an app at the moment, because no ROMs have a quickswitch yet. There's instructions in the OP
[Nexus S Android Development] DaXmax:
Okie cool, gonna flash it tomorrow or when im sober nuff. :P
[Nexus S Android Development] :
Don't drink and flash :p
[Nexus S Android Development] leap_ahead:
zimage v3.5? what is this ?
[Nexus S Android Development] technogravy:
I cant get this kernel to boot on the stock OTA ROM.. is it not compatible? or am i missing something?
[Nexus S Android Development] MrBigWaffles:
Doesn't work on stock ROM. This is actually explained a few replies back on this very page by Beladus himself.
[Nexus S Android Development] caliban2:
Should be a new (test-)version. If you don't know how to use it, it's not meant for you. ^^

EDIT:

Forget it, i think it's the same as 3.4.39. Just has "dirty" in the string, #392 instead of #391 and appears to have been built an hour later. But bedalus will explain I guess. :) (nobody ask how to use it, do your homework!)
[Nexus S Android Development] technogravy:
Apologies, I may have missed that comment.. Back to Simple Kernel for me.. :(
[Nexus S Android Development] JokerAce:
I removed the set min freq line, it still stuck at 200 min when I turn on my phone after deep sleep. My script is working because it generated the test.txt file.

EDIT: Should I uninstall the NSTOOLS? I don't use it tho. Never activate anything.
[Nexus S Android Development] nexususer1:
Could you please tell me if 65 fps mod actually makes the screen more responsive?
[Nexus S Android Development] Articudos:
Yeah, but drains little more juice;)
[Nexus S Android Development] :
Just a note about the zImage in the OP...

Some people have been asking to use on a stock ROM. Can someone who knows how to use fastboot please try and flash the zImage on a stock ROM for me? If it works I will upload a version with a stock ramdisk, and I will try to include MTP if it works on stock. I will then post a flashable zip. Thanks!
[Nexus S Android Development] Articudos:
Even though my phone keeps awakening(i think it's jb bug), battery is super, :eek::eek:

Long-lasting, Very smooth...:D
[Nexus S Android Development] sdhanjal15:
How so I get it to stay at 100mhz
[Nexus S Android Development] Articudos:
In nstools, it's kind of fake.

If ur device doesn't use gpu, min freq shows 200mhz but uses 100mhz.

@bedalus, How about add this in op?:D
[Nexus S Android Development] steve.garon:
I'm not sure that zImage are meant to be flashed using fastboot. As far as I remember, they don't contain the Ramdisk... If you use Koush's Anykernel it should work fine with a flashable zip in CWM. Beside you can't just flash a zImage without also pushing the wifi module because the wifi won't work. (unless you compiled the wifi in the kernel and not as a module)

I'm interested in your kernel to work on stock ROM because my girlfirend is running my old NS and she finds it slow so I was looking at custom kernel for her stock JB 4.1.1 install.
[Nexus S Android Development] caliban2:
Not true (anymore).

Once you had nstools open, min-freq is 200. Cpuspy shows 100-step not being used anymore afterwards.

To answer the OP's question:

SEARCH AND READ, DAMN IT!!! This has been answered a 100 times. Only use nstools to make yourself a script. When that's done and you have your script in place, don't launch it or you have to reboot. Same goes for various built-in settings in ROMs (like in CM).

---------- Post added at 03:40 PM ---------- Previous post was at 03:35 PM ----------

Just had a freeze/reboot.

Was browsing a page with opera when everything froze, after ~30 secs it rebooted to bootanim (!), no sim-unlock needed. Last-kmsg is the short one from recovery, useless.

I know this could be caused by ROM as well and that it's a bit early to call CM(-kangs) stable, but I thought I'll post for reference. :)
[Nexus S Android Development] Articudos:
Ok, I never used cpuspy so....

But In my cm10>performance shows 100mhz:confused:
[Nexus S Android Development] caliban2:
Hey, you're right. I just opened nstools and as long as I close it with 100 set, step is used. Same with performance-settings. This was different a few kernel-versions ago. So at least we can check settings again without a reboot. :)
[Nexus S Android Development] nexususer1:
I think it's worth it! It's so cool to have that responsiveness:) i think it's more responsive than an iphone (don't kill me, but i think responsiveness on iphone is amazing):)
[Nexus S Android Development] madd0g:
Well I had reboots with 3.4.39 also, sorry no last_kmsg.
[Nexus S Android Development] italia0101:
Yea seeing as this kernel doesn't work with stock yet . I tried the 65fps air kernel and yea ... its so nice !

Would love that here
[Nexus S Android Development] Naa Laa:
These settings does not bring similar results (bright white), like the one you see on the Trinity kernel. I am using the latest bedalus ICS kernel from post#2.

Am I missing something that needs to be tweaked/changed? I changed to the above gamma and RGB settings using the VooDoo Pro app.

Thanks for listening!
[Nexus S Android Development] alen1901:
Yeah, you are missing second post by bedalus. :D

Sent from SpeedMachine i9023
[Nexus S Android Development] mattrc77:
can't get pass boot anyone else have this problem?
[Nexus S Android Development] :
Good job you decided to spare my life! :p

Glad it's working nicely on MIUI. Version 0.8 coming...
[Nexus S Android Development] :
Version 0.8 (EXPERIMENTAL): http://d-h.st/Q6Y

I had a look at franco's tweaks and added the ones that I thought looked like performance improvers:

-ARM rwsem header tweak for atomic functions

-Franco's timer tweak 200 > 1000 Hz

I can't vouch for the stability of these tweaks, but I'll run them for a few days and see if there are any hiccups. Feel free to download and help test. If you experience any issues see if you can get adb access, and run:

adb shell cat /proc/last_kmsg > bedalus_crash.txt

...and upload it to the thread. Happy testing.

Feel free to stay with v0.7 if testing is not for you.
[Nexus S Android Development] :
EDIT: removed the google TCP tweak, and seems to be stable http://d-h.st/Q6Y (for the brave)
[Nexus S Android Development] Jamalsid:
Interesting to see you know developing bedalus. Downloading now and gonna give it a try (.7 that is).
[Nexus S Android Development] caliban2:
Running for two hours and nothing bad to report.
[Nexus S Android Development] :
Anyone can develop when they eat Marmite :silly:
[Nexus S Android Development] technogravy:
For someone not interested in MTP does this kernel have better battery life or performance?
[Nexus S Android Development] Icecoldmeat:
Nice to see a kernel from the ''Guru'' itself. Testing now.

Sent from my Nexus S©
[Nexus S Android Development] :
No, marmite is not a performance enhancing substance. You may crave it if you have worms. #truefact
[Nexus S Android Development] madd0g:
Any link about those tweaks and what are they for ? I'm actually on 0.6, because I don't OC and everything is tip top :]
[Nexus S Android Development] :
Well, I'm not exactly sure, but the timer was on 256hz, and Franco adjusted it to 1000hz, which i feel makes sense, because it divides into the system clock speed with no remainder.

The rwsem algorithm is by arm, so it makes sense to use it since they designed the architecture.
[Nexus S Android Development] madd0g:
Ah thanks, I guess I'll leave it like it is - "don't fix if it ain't broken" :P
[Nexus S Android Development] :
Well, it turns out the previous version may not have had the SLUB allocator as I intended. I think my .config file got reverted somehow (I'm still getting used to git)... also, I think Deep Idle vanished...

...not to worry. Version 0.9 is here: http://d-h.st/klo

-Fixed SLUB enabling in .config

-Fixed Deep Idle enabling in .config

-Added tweaks for ondemand algorithm from franco that allow disk IO operations undue influence over the frequency stepping

-Added my own preferred values for ondemand to get frequency more balanced across the available steps for a good power-saving.
[Nexus S Android Development] alen1901:
Did anyone yet compared battery life with default cm9 kernel? Im eager to flash this. :rolleyes:

Sent from SpeedMachine i9023
[Nexus S Android Development] DaXmax:
Again. I was bored. http://xperiencewithgoogle.blogspot.sg/2012/07/nexus-s-bedaluskernel-w-marmite-09.html
[Nexus S Android Development] madd0g:
Hope we can get this kernel on JB soon, I'd miss BLN & Voodoo :]
[Nexus S Android Development] tycruickshank:
Is there any way to make a deep idle fix for the stock 4.0.4 odexed rom? I know how ot make one for a deodexed rom but not stock odexed. I'm on stock 4.0.4 right now running Thalumus' kernel but I would like to give this one a try with deep idle.
[Nexus S Android Development] y3mita:
Had a reboot with .9 and rr daxmax ROM
[Nexus S Android Development] Oodie:
0.9 running well , deep idle works now .
[Nexus S Android Development] spupuz:
Random reboot this night

Inviato dal mio Nexus S con Tapatalk 2
[Nexus S Android Development] original21:
Just a quick respond on battery life. I am using latest JellyBro CM10 07/08. No games played, just ordinary business use.

Overall i am happy with battery life. Very close to ICS.

SmartassV2, min200, max1200, deadline

Excellent job bedalus.:good:

p.s. I do not use D.I.
[Nexus S Android Development] Naa Laa:
I am not sure which post you referring to... Can you please point me to the post?
[Nexus S Android Development] alen1901:
http://xdaforums.com/showthread.php?p=27608488

Read carefully.

Sent from SpeedMachine i9023
[Nexus S Android Development] caliban2:
RebootS, plural? Which ROM?

So far I just had the one and I'm not so sure yet it's caused by kernel...