yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] :
I don't game on my phone. I think there's one report of someone using this for games. I think it was a positive review. My kernel has OC up to 1.2GHz, and smartassV2 governor tuned properly. If you do decide to try it, please report back. :)
[Nexus S Android Development] Oodie:
3.4 with DI enabled runs fine . Played temple run for a while , few calls , some browsing . No issues yet .

°°° This comment is Sent from my Nexus S °°°
[Nexus S Android Development] :
Check the stats, does it continue to accumulate TOP=OFF time?
[Nexus S Android Development] gabling23:
Which app do you suggest me to use to set the bln, bld the schedulers and the governors?

Inviato dal mio Nexus S con Tapatalk 2
[Nexus S Android Development] sdhanjal15:
Excuse the graph. But I can't figure what's wrong. That almost flat line was me sleeping.

Sent from my Nexus S
[Nexus S Android Development] :
This is my method:

Create and save settings in NSTools, then go to /data/data/mobi.cyann.nstools/settings and copy the settings from there and paste into any existing script in /etc/init.d/

Delete the minimum frequency line or 100 MHz won't be used.
[Nexus S Android Development] :
Sorry, I don't understand what problem you are asking about.

Is the battery draining too fast? What version are you running? What governor settings, and what ROM? How many hours screen on time do you get on one charge?
[Nexus S Android Development] sdhanjal15:
Running codename android.

And the latest test with deep idle.

And my phone isn't sleeping like I sleep. Its not sleeping like baby:banghead:

Sent from my Nexus S
[Nexus S Android Development] :
It's probably PM_FAST. Did you turn off wifi?
[Nexus S Android Development] migz012788:
Okay. I will try this one. What is the best rom to combo with this kernel? And also i dont overclock as possible. Because im on jellybelly and games runs smooth even though it is not OC.

Anyway thanks mr. Bedalus :)
[Nexus S Android Development] caliban2:
Hey there, 3.4 with didle on is running fine here, great job! :)

But my script is overwritten on reboot, gov is always set to ondemand instead of smartassv2. I can change it manually, but then a side effect is that min_freq get's set to 200. Doesn't matter if i change that with nstools, terminal, adb, root explorer, cm10-settings, 200 is reset right away. Also cpuspy shows 100 is not used at all.

Anyhow, main issue is that the script (99kernel) is overruled. It's applied though, because my smartassv2-settings are always there (they differ a bit from yours).

(Batt-life with ondemand and didle on looks great, btw)
[Nexus S Android Development] :
Okay, my script is attached, but delete the .txt obviously and check the permissions.

The change you have to make is on the last line, change ondemand to smartassV2.
[Nexus S Android Development] sdhanjal15:
It was on all night. I feel like pm fast drains WiFi in standby

Sent from my Nexus S
[Nexus S Android Development] caliban2:
I thought I had already tried that, but setting gov manually via root explorer or terminal get's rid of the 200-side effect.

So it's just my script getting overwritten.
[Nexus S Android Development] :
http://xdaforums.com/showpost.php?p=29775571&postcount=996

I've edited the post above with my script.

I'll just double check now that what I've suggested actually works...
[Nexus S Android Development] :
1000 posts!
[Nexus S Android Development] caliban2:
hey, that should've been mine!!! :p

congrats, one could almost suspect you're making a good kernel. :D

regarding the script, i know mine works because my settings in /.../cpufreq/smartass are written during boot.

what happens if you change to smartassV2 in yours?
[Nexus S Android Development] :
GASP! You are quite right. I'll investigate...
[Nexus S Android Development] :
Yeah, see post above. (We have some timing issues with our posting... :p)

I'll look into it.
[Nexus S Android Development] eng.stk:
Man you're fast:good:

Will try, for me v3.3 was very good already, Deep Idle was the only missing goodie.
[Nexus S Android Development] Phoenix Wright:
Really good kernel, thank you for your work! ^_^

The only thing I'm missing is the fast charge :)

Btw I'm testing the Deep Idle version and it seems stable until now... I'll report back if it reboots or something.
[Nexus S Android Development] djjonastybe:
I suggest you discard MTP. A phone will benefit more from IDLE2 than the MTP we hardly use.

A phone will use IDLE2 24/7. but MTP maybe 1 hour a week?

Can you add BLN? If you do your kernel will be perfect.
[Nexus S Android Development] leap_ahead:
bln is there ...

i use mtp 20/24 hour trasfer new kernel :P
[Nexus S Android Development] caliban2:
Idle2 isn't working to it's full potential yet. Until that's the case, the point is mute. Does mtp even cause trouble with idle2? While connected to PC via USB, it doesn't kick in anyway.
[Nexus S Android Development] Phoenix Wright:
I had a reboot (the phone wasn't suspended, I don't think it's Deep Idle)

This is the kmsg: http://pastebin.com/3g01jjPe
[Nexus S Android Development] leap_ahead:
Rom ?
[Nexus S Android Development] jabbeboy:
I guess you cant help me beadalus, because it works for everybody else but not mine. And since i cant provide any logcat, or can i ?? How do i do that?:angel:
[Nexus S Android Development] Phoenix Wright:
Euroskank CM10 from 31/7:)
[Nexus S Android Development] :
If you had a reboot, why are you pulling the active kmsg log? You need the last_kmsg!

This is my personal kernel, I'm just sharing what I made for myself, so I don't really take suggestions as a general rule.

It won't work with JellyBelly. It should work with all other JB ROMs. I suggest you

1) format system

2) format cache

3) flash a JB ROM (but not JellyBelly if you want to use my kernel)

4) flash my kernel

5) reboot

If that doesn't work, then I am out of ideas.
[Nexus S Android Development] gabling23:
So after that I have created the file should I copy the whole file in the init.d folder or only what is written in that file?

The problem if I keep nstools is that the minimum freq can't go under 200mhz right?

Inviato dal mio Nexus S con Tapatalk 2
[Nexus S Android Development] :
Copy what is written in the file into an existing script and paste at the end.

Yes, keep the app, it's useful for checking things, but disable the Restore-at-reboot feature.
[Nexus S Android Development] :
OK, I give up. I have no clue why you can't set the governor to SmartassV2 with init.d script. I've tried everything I can think of. Anyone know anything about this?
[Nexus S Android Development] madd0g:
Stock deodexed JRO03E with 3.4 experimental + DI runs stable for me now since this morning (12 hours), I had a reboot and 2 freezes with 3.3.

I don't have DI enabled, but still had less battery usage with Airplane mode + SportsTracker + Poweramp (9% in 1 hour 12 minutes) then with IDLE2 . Settings are all stock, ondemand obviously. Seems like a great combo now, thanks for the good work.
[Nexus S Android Development] Phoenix Wright:
Sorry :) Here it is http://pastebin.com/5vJjGR9f
[Nexus S Android Development] :
There's no kernel panics in there, looks like a normal reboot.
[Nexus S Android Development] gabling23:
I put all what was written in the first file in the init.d folder.. I also modified the value of the min freq from 200 MHz to 100 MHz..

Can you check from the screens if I did it right? Will it work if I keep it like this?

Thanks for the patience and sorry for the questions but I'm not very good in this things..

Inviato dal mio Nexus S con Tapatalk 2
[Nexus S Android Development] caliban2:
Like I would know anything about this, but it couldn't be that one herring-file...? I remember thalamus saying something about how it has ondemand hardcoded on JB. IIRC it took him a while until he managed to get interactive as standard-gov.

Just a wild stab in the dark, probably stabbed myself. ^^
[Nexus S Android Development] :
Absolutely fine so far...

The line you just modified, it will probably cause the minimum to fix at 200 MHz anyway, due to some weird bug.

Instead, delete that entire line, i.e. if you don't try to set the minimum, it will automatically default to 100 MHz.
[Nexus S Android Development] :
lol :p be more careful.

Yeah, I have a vague recollection. I tried all sorts of crap. I even rebuilt the ramdisk. It must be in the kernel somewhere, but I haven't found it yet.
[Nexus S Android Development] leap_ahead:
Bedalus here is the fix for blx http://xdaforums.com/showpost.php?p=29305182&postcount=59

Thanks
[Nexus S Android Development] :
Hey, excellent work! Much obliged. :D
[Nexus S Android Development] polobunny:
Anyone had random freezes with non DI 3.4 but not with 3.3? I've had two or three of these weird freezes/lags where my phone becomes totally unresponsive, screen is on, BLD works because whenever I touch my keys I can see them lighting up then back to off state. Pressing power button does nothing but if I wait a minute or more then suddenly it un-freezes like nothing happened. Not too sure what's up with that. :S
[Nexus S Android Development] alen1901:
Post last_kmsg and bedalus will try to help.

Sent from SpeedMachine i9023
[Nexus S Android Development] :
Here's a little update, v3.4.1: http://d-h.st/B5r

-BLX fixed hopefully (thanks to leap_ahead :D)

-Fingers crossed smartassV2 can be called from init.d

Please test and report back for me and to inform other users... I can't test myself right now, I'm running an IDLE2 drain test for thalamus.
[Nexus S Android Development] caliban2:
Nope, not yet. :)
[Nexus S Android Development] explorer-10:
is there a way i can add fast charge myself for my own personal liking?
[Nexus S Android Development] polobunny:
I would have if I had one. But I rebooted since then. I was simply asking if anyone experienced this before jumping to conclusions. Nevertheless, I went back to 3.3 and so far so good... Strange issue!

Edit: Well nevermind, a few seconds after this post, launched Chrome, was gonna check for a new kang and bam, froze + reboot on me. Using bedalus v3.3 this time.

last_kmsg

http://pastebin.com/WtTBX576
[Nexus S Android Development] leap_ahead:
Thanks bedalus its ok now !!!
[Nexus S Android Development] sdhanjal15:
Why back to .38

Sent from my Nexus S
[Nexus S Android Development] leap_ahead:
its only the name ..he forgot to change it ..
[Nexus S Android Development] sdhanjal15:
Hahaha alright.

Sent from my Nexus S
[Nexus S Android Development] :
I'm halfway through writing a guide in the third post.
[Nexus S Android Development] :
D'oh!

You can see I've merged in 3.0.39 in my github. But I need to update the config.
[Nexus S Android Development] :
Again, unfortunately this looks like a perfectly ordinary reboot. No panics. I can't explain this. ROM issue perhaps?
[Nexus S Android Development] :
Okay, I've tried everything I can think of to get smartassV2 to set from an init.d script.

I've currently got a script that works if the user executes it manually, but if you try to trigger it from init.d, everything works except setting the scaling governor.

I've even built a version where smartassV2 is set as the default governor, and it still boots with ondemand as default.

The only thing I can suggest now is:

1) Copy the script to a new location and append with .sh

2) Make sure it's executable

3) Use root explorer and long-press > select make shortcut

Then you have a shortcut to your script as an icon on your homescreen. I know it's not ideal, but I'm totally out of ideas on how to make it fully automatic.
[Nexus S Android Development] Articudos:
I dunno about smartassv2 issue, but did u looked up latest r_data's changelog? He did some mistakes merging smartassv2 stuffs, so how about looking up his github?:D

Sorry If this not helped or mentioning other kernel made you feel bad..

:)
[Nexus S Android Development] jabbeboy:
Ehh i dont have jellybelly, i have the stock ota 4.1.1.... But maybe i need to change, i do experience somr bugs, and if i flash another rom, ir may be faster

?
[Nexus S Android Development] :
If you are on stock, you have to obtain root before flashing a custom kernel. Have a look through the stickies here and in general.
[Nexus S Android Development] :
Not at all, r_data is a nice guy. I've got no problem if you want to flash his kernel then report back here if init.d works for setting smartassV2. (Then I'll steal his ideas :p)
[Nexus S Android Development] :
Here is v3.4.39: http://d-h.st/WHn

-Fixes up the 3.0.39 issue (I thought it was a config error, in fact I just got the merge completely wrong! :p)

-From v3.3 stable to here includes:

>BLX should allow to set 100% properly now

>Deep Idle is working, fixed at 400MHz for maximum efficiency. Using thalamus' code to fix the DI frequency seems to have solved the stability issue, compared to my own dodgy method in the ICS version.

Also, I've been wondering, does it work on NS4G? Can a 4G user report back?

If you have any unexpected behaviour after the 3.0.39 update, I suggest you first try wiping cache and fixing permissions. If the behaviour persists, please try to upload a last_kmsg for me :)

EDIT: All issues with GPS and Data Usage (menu item) should be fixed! :)
[Nexus S Android Development] jabbeboy:
Have you not read what i have been writing?? I am on the stock OTA rom, but i have flashed it manually, so of course i am rooted.. I have flashed other kernels and they work, i currently using your old version 2c and it works, so i have no idea why v3.3 doesnt work..., but i will try your tip, and change rom in the process, im getting little tired of the stock rom now:D
[Nexus S Android Development] :
Dude, I've got a wife, 2 year old kid, I work shifts at a new job, and I'm trying to learn how to develop better than an ape when I ought to be sleeping...

Just watch the tone, and I'll do my best to help, deal?
[Nexus S Android Development] italia0101:
Well said
[Nexus S Android Development] jabbeboy:
Okey, sound alright:D

Gonna try changing rom and try v3.3 and see if it works.
[Nexus S Android Development] alienmind:
on 3.4.2, cannot set min freq to 100mhz., on both ondemand and interactive. it gets reset back to 200. everything else working great so far. thx

Sent with my cold hands from the grave
[Nexus S Android Development] :
People have this problem often. Are you using nstools? If so, use a script instead. If you are already using a script, remove the line that sets the min, and it will default to 100 MHz. Use CPUSpy to check it worked.
[Nexus S Android Development] Articudos:
Damn, I think it's not working:p

Nevermind

:p
[Nexus S Android Development] gregorypeg1000:
Just installed 3.4.2v . Is deep idle enabled by default?Or i should enabled it from Nstools?
[Nexus S Android Development] nahsha:
Hey guys, how do you flash a kernel? I went through recovery and cleared cache and tried to flash it...gave me message 3 and saying (lid has licked) or something... then i go check about phone shows the old kernel.
[Nexus S Android Development] caliban2:
Please, at least read the last 5 pages before posting. :p (I'm not even mentioning that strange thing called "search".)
[Nexus S Android Development] :
I thought so! Nevermind. We'll just have to live with ondemand at bootup!

Read above post... and just FYI, NSTools is handy to see if DI has quit working. You should always see TOP=OFF stats accumulating when the screen is off, otherwise DI has broken down and you need a reboot to restore it. Why does DI crap out? AnTuTu definitely breaks it, and there may be other apps. It's on my list of things to try and fix, but ultimately make worse :p

You've been marmited :p
[Nexus S Android Development] leap_ahead:
3.4.3 release ??
[Nexus S Android Development] nahsha:
bedalus, can you explain? :)
[Nexus S Android Development] :
Well, I haven't tested it... but it's built. I'm actually just on ICS at the moment. I wondered if I could get DI down to 400 MHz using thalamus code (since my own code attempt fell flat on its face :o)

If it's stable I'll upload a v1.5 (ICS) and v3.4.3 within an hour or two.
[Nexus S Android Development] :
Sorry, marmite is just my little joke. All those messages you see when you flash the kernel are just jokes too. :o

What does your kernel version actually say?
[Nexus S Android Development] polobunny:
I moved to JB because support for ICS was getting dropped by every dev, and now this? >:|

Battery wise I preferred ICS (and even GB) to JB but it's definitely the smoothest experience out of them all.
[Nexus S Android Development] nahsha:
I got xenon hd (the latest)...

when I look in the kernel it says: 3.0.31-android-build@vpbs1 #1 PREEMPT etc...

I tried to flash with bedalusKERNELv3.4
[Nexus S Android Development] :
Uh... maybe download again, then try to flash again.
[Nexus S Android Development] superhil:
Hi bedalus

I still have the issue, min cpu freq can't set to 100

I already deleted the line which set the min cpu freq

but still cpu min freq go back to 200

I also have tried to set 100000 as min cpu freq, but strangely cpu min freq back to 200MHz

Currently I'm using PA (CM10 based), doesn't have this problem with stock kernel
[Nexus S Android Development] :
In CPUSpy does it register 100MHz?
[Nexus S Android Development] :
Blast from the past! New ICS 4.0.4 version:

Here is v1.5: http://d-h.st/xZ0

-Morfic's colours fixed!

-Merged to 3.0.39

-DI fixed at 400 MHz, the most power saving state, using thalamus' code, which is stable!

-cyanogenmod based (kalim's source)

-ICS ONLY!!

I was unsatisfied with where I left v1.4d for ICS, so today I went back and sorted it all out. If you are still rocking ICS old-skool-style, v1.5 has the goodies. DI is now properly fixed and stable at 400MHz, thanks to thalamus' code. Morfic's colours are also sorted, and the base is merged up to 3.0.39 for good measure. Enjoy! :D
[Nexus S Android Development] jabbeboy:
Hi beadalus, just want to tell that 3.3 works now, i flashed androxide rom, but probably the solution was format systrm and cache. Thanks for the help.
[Nexus S Android Development] sidnoit22:
Where is the download link of 3.4.3?

Sent a Jellybean from my Jar
[Nexus S Android Development] :
I built it, but it rebooted. I think i need to double check a few things. I've really struggled to get this 3.0.39 update to work on jb. Seems fine on ICS though.
[Nexus S Android Development] polobunny:
Not wanting to blame the kernel too quickly, but moved to knzo cm+ kernel and so far no freeze. I'm really wondering what the heck is going on. :S

I wish I knew better how to debug for Android because I'm grasping at straws with my problem. Kinda keeping me from running your kernel even if it seems like a rom problem.
[Nexus S Android Development] :
Nobody should run an unstable kernel! I appreciate all the feedback. Keep posting your last_kmsgs and maybe I can get to the bottom of it.

I'm re-building v3.4.3 now, and if it behaves itself for a few hours, I'll post it. Sometimes, my fresh builds seem to work fine until about 5 minutes after I've published the link! We'll see. I just switched ROMs aswell, which doesn't make for a consistent testing environment. Ezekeel would turn in his <whatever-living-people-turn-in>.
[Nexus S Android Development] polobunny:
Currently not running marmite so no useful last_kmsg to get. :P

If it freezes in a similar manner it will only confirm my suspicions. Otherwise, I'll shed some tears.
[Nexus S Android Development] :
Sorry that comment wasn't directed specifically at you... I meant anyone who downloads a test version is doing me a favour!

Let me know what you discover in any case :)
[Nexus S Android Development] :
Slightly later than scheduled...

Here is v3.4.3: http://d-h.st/2Mj (TESTING)

EDIT:

I'm not 100% confident in this version. Things have just been a little weird since updating to 3.0.39, but I also switched ROMs, so I'm not sure if it was just that. I didn't format my data, so there could be some conflict there I suppose.

Anyway, I think it's safe to release. I rebuilt it slightly different, and it has behaved itself so far... Again, if you experience any weirdness, please try to retrieve a last_kmsg! :D
[Nexus S Android Development] Imppy:
How this compare to the interactive setup of thalamus kernel?
[Nexus S Android Development] polobunny:
I would say it is very similar. Interactive seems to be snappier, ready to go as soon as you turn your screen on. However, jelly bean in itself is very snappy so it's hard to quantify. It's also hard to tell placebo from noticeable difference, sometimes I wish I didn't read changelogs or peruse commits...
[Nexus S Android Development] Imppy:
Yes i like the snappy part of interactive and battery seems good. Not sure how smartass compared
[Nexus S Android Development] asphantix:
couldn't get past the boot animation. is it compatible with i9023?
[Nexus S Android Development] vis80k:
sorry if already asked and answered. can't find a way tp search in a thread with taptalk...

when bln enabled, does it get counted in to android os in battery usage? just observed 40+ drain overnight and I think bln is the issue as bln never went off after the time I set it to.
[Nexus S Android Development] xjerlzx:
ICS? hell yay! downloading now!
[Nexus S Android Development] madd0g:
No. JB is drainy itself.
[Nexus S Android Development] vis80k:
73% by android os? had paranoid 1.9.2 before as well as a few other jb rom. nothing like this even on early ics...

currently on paranoid 1.9.5 with bedalus kernel 3.3.
[Nexus S Android Development] sidnoit22:
What i say that

....

DOWNLOAD ALL KERNEL FROM NEXUS S FOURMS AND STEAL THEIR IDEAS! :D

Sent a Jellybean from my Jar
[Nexus S Android Development] sidnoit22:
Which ROM are you using?

Sent a Jellybean from my Jar
[Nexus S Android Development] vis80k:
Hello Bedalus and others capable of deciphering the log files. ;)

never had this kind of drain ever, not on GB, ICS or any of the other JB roms and kernels I've tried.

40+ battery drain overnight. Android OS being 70+% of that drain.

Paranoid 1.9.5 and Bedalus kernel 3.3 with everything at default setting except for BLN and BLD enabled via NSTOOLS.

With BLN, observed that the BLN doesn't go off after the time I set via NSTOOLS. there was a pending notification when I turned the screen on this morning, so I am suspecting BLN may be bechind this drain...

attached is kmsg, wakelocks, and logcat. I don't know which is for kernel troubleshooting. from kernel side, I can only suspect the BLN not going off after a set time, but if looking in to the attached files gives any obvious reason for the drain beside from kernel issue, it would be appreciated if some insight can be given. :D

edit. files attached. ;)
[Nexus S Android Development] JokerAce:
As of 1.5v for ICS, the mem should be 404? I have 397 tho?

EDIT: Had a crash when I tried to see the idle stats..

EDIT2: I think you should add the code to extract last_kmsg from terminal into the OP to encourage users to do it. I had to search google for it. For convenience sake I would say. :)
[Nexus S Android Development] _android_:
Same here. Kernel v3.3 Could not get past boot animation. i9020T on rooted-ota-stock JB4.1.1 .

Tried clearing cache and dalvik. No difference.
[Nexus S Android Development] d_phekt:
3.4.3 running great here on Kalim's CM10. Nice and smooth. Great work as usual.
[Nexus S Android Development] asphantix:
JB ota 4.1.1

Tried wiping cache and dalvik before.
[Nexus S Android Development] caliban2:
I had the same problem with 3.4.1, but by the time I noticed 3.4.2 had been released. It's fine, as was 3.4. Haven't tried 3.4.3 yet. I'm only using BLN, no BLD.

How about you updating to a more recent version?
[Nexus S Android Development] JokerAce:
Caliban, if nstools is buggy and I don't want to use it. What other tools are there available for me to use? Scripts?

If scripts, how do I go about doing that?
[Nexus S Android Development] caliban2:
Last time I quoted this on page 106...
[Nexus S Android Development] vis80k:
now that it's out as stable, I will. :)

it's just that the last I checked, 3.3 was stable but 3.4.x were getting there... ;)
[Nexus S Android Development] JokerAce:
Looking at CPU Spy, it's back to 100mhz again :victory:

However, it is not registering the 400mhz even though my script has deep idle enabled.