yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] madd0g:
Stock deodexed DoubleX. Didn't have any with SimpleKernel though. I'll try to get a last_kmsg, maybe it's my device.
[Nexus S Android Development] caliban2:
Okay, sounds like kernel then.

Good luck with last-kmsg, it didn't create one for me.
[Nexus S Android Development] Phoenix Wright:
All kernels since 3.4.1 have not working GPS... just check with GPS Test (free from market)... no satellite is detected.

I have a i9023:rolleyes:
[Nexus S Android Development] Articudos:
@bedalus

IMO, jro03l is LTE stuff but, according to https://twitter.com/peteralfonso/status/233042830174597120

There was a lot changes in kernel, are u planning to merge changes?:)
[Nexus S Android Development] :
Steve! Great to hear from you!

Yes, I think I had a misconception about zImage.

My other approach is to use the ramdisk from stock to make a new boot.img.

I'll upload the result to the OP. Shouldn't take me very long.
[Nexus S Android Development] :
Yes, I'll do my best to stay completely up-to-date. :)
[Nexus S Android Development] Phoenix Wright:
Sorry, I saw that there was an edit to the post with a fixed version :) Great:)
[Nexus S Android Development] :
Download CPUSpy. It'll show that you are accumulating 100 MHz. If you are not, make sure you are using a script to set your preferences, rather than NSTools (uncheck the set-at-boot box).

When reporting a reboot can you say whether you have already tried wiping cache and fixing permissions?

This was reported as working. I haven't tested it myself. Again, try wiping cache and fixing permissions.

EDIT: Oh from your post above I see you were using one of my 'joke' versions.
[Nexus S Android Development] :
STOCK: http://d-h.st/MWT

STOCK with MTP: http://d-h.st/9HG

This a test version for stock OTA-based users.

It won't work cm-based ROMs but may work with AOSP based ROMs, however, if you use a custom ROM, you should use my regular version.

Please test if MTP works and report back!
[Nexus S Android Development] asphantix:
thanks, gonna try it now :)

edit:it booted!! it works :)
[Nexus S Android Development] :
Great! Ok, now I'll add MTP.
[Nexus S Android Development] :
OK MTP version is now added (in the post above). Hope someone can test and report back. Instructions on enabling MTP connection are in the OP.
[Nexus S Android Development] steve.garon:
Hey bedalus,

I'm not 100% sure on how you build your kernel to get a prebuilt boot.img but I can confirm that it boots. For those using a 100% stock rom its even better not to have the zip and just flash the boot.img with flashboot. The problem with the zip is that it alter the system folder therefore future updates will fail.

Can you show me how you create your boot.img? I'd rebuilt your kernel and set 1200Mhz by default. I don't have root on the phone I'm trying to run this on.
[Nexus S Android Development] :
Yeah, I'll post full instructions in post#3 tomorrow, it's 2am here now :)
[Nexus S Android Development] asphantix:
uhm in order to get deep idle to work in v3.4.39 I need to patch the framework_res.apk, right? Is there anybody who can do that for me for the stock OTA 4.1.1. I tried it with apktool 1.4.9 but it doesn't work - I don't know why.

edit: got it. I forgot to pullout the META-INF and manifest file first. But why is the original framework-res.apk much bigger?? :/
[Nexus S Android Development] polobunny:
It's not compressed, just stored.
[Nexus S Android Development] steve.garon:
No need to do that just for me. I figured it out myself. I used the unpackbootimg and mkbootimg tools and created some scripts around it so now I can try a zImage right after compile without even flashing it. I wonder why I was not doing that when I was building kernels :-\

Anyhow, now I just need to build myself a pre-overclocked kernel and I'm good to go. I had one build but it crashes, the voltages you use by defaults don't agree with my phone. I'll probably bring back a SlimSG kernel based of yours ;) well at least just a boot.img...

Thanks for your time.
[Nexus S Android Development] caliban2:
Yes, I always wipe caches when flashing a kernel or rom, despite some people saying it's not needed. Didn't fix permissions though, is something wrong with your script?
[Nexus S Android Development] :
Cool. I can add it to my OP if you like. If you start a new thread I'll just put a link to it instead.

I forgot to mention the wifi driver can now be built into the kernel, so there's no module.
[Nexus S Android Development] :
No, the script is like that deliberately. I had a reboot after upgrading to 3.0.39, but wiped caches and fixed permissions, and had none since. People have been getting them in thalamus' thread too. It's either the caches or the kernel. That doesn't help narrow it down i guess! But as a general rule, i don't bother. I haven't had any issues recently. If you get a recurring problem even with cache wiped, try to catch the last_kmsg, otherwise there's not much for me to go on!
[Nexus S Android Development] technogravy:
Just switched from stock ROM to slim bean when you added support for stock. But thanks anyways.
[Nexus S Android Development] Articudos:
Super-battery stats:D
[Nexus S Android Development] anshumandash:
The stock version did not work for me. It booted well first time and worked well for some time. after few hours, I took few pics using the camera. It froze on 2nd click, rebooted in to "Safe Mode". This is what appeared on the bottom left corner. I had never seen this message before. The phone was really hot. Now every time I try to boot, it loads everything, I see the lock screen and then the screen goes black until I pull battery. I tried taking a last_kmsg, but when I get in to cmd in bootloader mode and type adb shell cat /proc/last_kmsg > kmsg.txt, I get a message Error: Device not found. I checked the ADB drivers, the are loading well.

Not sure if I did that correctly to take kmsg. I have now flashed back Matr1x and it is working.

Any idea what could have gone wrong. It worked for a few hours and was really fast & smooth with 200, 1200 CPU speed. It can't be OC as with ICS I had used upto 1420 OC without problems.
[Nexus S Android Development] italia0101:
I'm a little confused how do I get deep idle to work properly ? Only got top on atm
[Nexus S Android Development] alen1901:
With adb, first tipe adb root. Than your commands.

Sent from SpeedMachine i9023
[Nexus S Android Development] caliban2:
I know, which is why i wrote this in my report: :p

But so far it's been a one-time hiccup.
[Nexus S Android Development] italia0101:
I thought the deep idle was locked at 400mhz? Mine is using 100mhz
[Nexus S Android Development] alen1901:
You mean deep sleep uses 100mhz. Deep idle accumulates only when you listen music with screen off or similar and it uses 400mhz.

Sent from SpeedMachine i9023
[Nexus S Android Development] italia0101:
Good call, tested playing music at it was 400mhz all the way :)
[Nexus S Android Development] xjerlzx:
thanks to work of bedalus
[Nexus S Android Development] :
Just updated the OP:

I hope some visitors will be tempted to follow the guide and learn to build kernels. It's not always straight-forward, and troubleshooting can be frustrating, but when you get it right, it's rewarding!

Like it says in the guide, if you do attempt to build, and struggle with any of the steps, then let me know... I want to correct the bits that I explained badly! :)
[Nexus S Android Development] gregorypeg1000:
Which rom do you use?
[Nexus S Android Development] :
You are using a stock ROM? Was this with the MTP enabled version?
[Nexus S Android Development] italia0101:
anyone help me out with a framework apk fo the deepidle to work properly?
[Nexus S Android Development] anshumandash:
I am using this with Stock ROM 4.1.1. OTA upgraded from 4.0.4 factory image. It is the non-MTP version of Kernel. Somehow not able to get ADB to work to get kmsg. But fastboot commands are working in bootloader mode.
[Nexus S Android Development] :
Hmm. Can you go to CWM recovery, wipe cache and fix permissions?
[Nexus S Android Development] asphantix:
If you are on stock jelly bean I can help you out with a flashable of the framework-res.apk
[Nexus S Android Development] italia0101:
Yea would be great thanks
[Nexus S Android Development] anshumandash:
I had done a cache wipe before flashing the kernel. I flashed yours over Thalamus kernel. Now I have updated drivers on my Windows 7 x64 using android SDK. I could get kmsg. But I have already flashed Matr1x for the phone to work as I was expecting some calls today. Will this kmsg help get any details? I have attached it if you think it will still have some details from the previous kernel.
[Nexus S Android Development] :
Thanks for trying. You need the last_kmsg and you have to get it after the unexpected reboot.
[Nexus S Android Development] steve.garon:
That's a very complete Guide.

I created a couple scripts yesterday to wrap the mkbootimg and unpackbootimg tools and make this easier. Basically what you need is a source boot.img then I have a install_kernel and a try_kernel script that take a zImage as parameter and reboot your phone in bootloader mode, unpack to old boot.img, repack it with the new zImage and flash or boot the new kernel. Let me know if you want to look at them, it makes it easy to try zImages right after they where compiled.
[Nexus S Android Development] :
Thanks!

Sadly for me, i work on an old g4 PowerBook controlling the desktop upstairs through VNC. So no adb or fastboot for me.

I can't work on the desktop because I wake my daughter up!

If you want i can add it to the guide?
[Nexus S Android Development] asphantix:
Here you go...

bt_adapter_quick_switch_fix_ota_411.zip:

https://dl.dropbox.com/u/3985208/bt_adapter_quick_switch_fix_ota_411.zip

flashable with clockwork recovery

and sorry for my late response.

let me know if something goes wrong. (always make a backup before you flash something)
[Nexus S Android Development] technogravy:
Using this kernel now on slim bean and this is the best battery life I've seen on JB ever.

Not to mention the smoothest too..
[Nexus S Android Development] Imppy:
What settings did you use? The default?
[Nexus S Android Development] italia0101:
Thanks a lot works perfectly
[Nexus S Android Development] Muvolt:
Yes, but a kernel has the least effect on battery life...
[Nexus S Android Development] asphantix:
Really? I beg to differ. I flashed the crap out of my Nexus S since gingerbread and I always noticed changes in battery life depending on which kernel I used. Deep idle works great for me. In 6 hours I lost 6% while the screen was off.

And this kernel really seems to be great. Great battery life and very smooth so far.

@bedalus:

one problem though: The BLN isn't working properly. Only the menu button is blinking/on and wifi seems to be a bit more unstable than with the stock kernel.
[Nexus S Android Development] italia0101:
anyone have the issue with deep idle that it kills the network coverage sometimes?
[Nexus S Android Development] alen1901:
Right now im without signal(gsm), and cant restore it. Only reboot would help. Dunno if thats because of kernel or rom. First time it happens. 1 time Before i lost signal for short amount of time, i just searched for networks and it connected. But not now.

Sent from SpeedMachine i9023
[Nexus S Android Development] italia0101:
Well I'm on stock . And it didn't happen before I used a custom kernel ...

I don't think its this kernel specific though . Iv had the issue with any kernel with deep idle
[Nexus S Android Development] schurl85:
also got a reboot during a phone call with deep idle on. it' feels like the same bug with ezekiels glados kernel on ics. i think the problem was never resolved.

it's the first time for me to get a last_kmsg. so i hope it's the correct one
[Nexus S Android Development] Fast-Droid:
Couple days on v1.5 - 3.0.39 with QISS ME 4.0.4 Rom....Rock solid awesome battery life...Only issue BLN not working...Same prob with BLN when i flash to JB inverted with v3.4.39..Other then BLN prob,both Kernels are really solid..Thank you,nice work
[Nexus S Android Development] Blackcrx:
care to post some stats? on time? screen time? etc..
[Nexus S Android Development] polobunny:
More or less related post, but do you think it's possible for you to put back the latest release version + date in the thread title? It makes it easier for crackflashers to see if there was an update without having to click the thread. I know, I'm lazy. :p
[Nexus S Android Development] Blackcrx:
anyone having problems with nstools settings going back to default after reboot? i have tried using "set on boot" and also "use unit.d script"

3.49.39
[Nexus S Android Development] vikingsail:
Same problem here but I did Dalvik wipe and cache wipe. And after I flashed this kernel it says lid has licked as well. But then the phone just stayed at the boot animation forever. So I restored my phone now it's back to original.
[Nexus S Android Development] gummie:
Thanks for this Kernel been using this for a day. Only problem I had is I dont know what causes some freezes on my device. It last for seconds but sometimes its severe it lasts for minutes.
[Nexus S Android Development] pan1980:
Running the latest stable since morning had just 2 reboots in a row, the second o e just after entering the similar card pin.I oveclock to 1.2ghz and suspect this is the problem.

I know from previous kernels that my phone needs at least 1.35v for 1.2ghz and I wonder which is this kernel voltage for this step and if is any way to change it.
[Nexus S Android Development] :
Do you mind if I mirror this in the OP? Will give credit of course.
[Nexus S Android Development] :
Holy crap. It's working for you? I'm trying to get it to work like that deliberately. It's not happening on my phone.

Can you tell me which version you are using? The entire kernel name including build time if you don't mind?
[Nexus S Android Development] :
Can you check your root folder to see if there is a radio dump?
[Nexus S Android Development] :
Thanks for trying. :)

This isn't that last_kmsg. You need to use root explorer (or similar) to copy /proc/last_kmsg to /sdcard/last_kmsg.txt and upload that, immediately after rebooting.
[Nexus S Android Development] :
Yeah, I'll go back to that format once people are aware of the guide for a few days. :D
[Nexus S Android Development] :
You need to use the right version for your ROM.

If you are on Stock OTA, use the OTA version, otherwise use v3.4.39, check the OP.
[Nexus S Android Development] :
That's the exact voltage I use for that step. Try wiping your cache and fix permissions.
[Nexus S Android Development] ilnanny:
Not work in slim j.b.

Wait new release. good job dev.

Inviato dal mio Crespo
[Nexus S Android Development] :
It does, I'm running that setup myself. Did you try to use the stock kernel?
[Nexus S Android Development] pan1980:
Bln works for me, slimjb 2.0 and your latest stable kernel at first post in this thread.

I have i9023.
[Nexus S Android Development] asphantix:
I'm using the stock version with mtp on my stock 4.1.1. with the latest NSTools. When there is a new notification only the menu button blinks. Looks strange :D

And yes you can mirror the deep idle fix :)
[Nexus S Android Development] 4tticuz:
Using bedalusKERNELv3.4.39.zip with latest euroskank and bln doesnt work.

Anyone else with same issue?
[Nexus S Android Development] :
Are you on a 9023 or a 9020?
[Nexus S Android Development] 4tticuz:
i9023
[Nexus S Android Development] Imppy:
Ppl with 1920 seems to have problem with bln
[Nexus S Android Development] :
Would you mind testing this one: http://d-h.st/npq

I'm trying some new ideas for BLN

Question: Any NS4G users out there?
[Nexus S Android Development] 4tticuz:
Dalvik and cache wiped, flashed that file but bln option in euroskank is still grey and not chooseable.
[Nexus S Android Development] :
Oh. Ok, no problem, you can turn it on using a script. Search the thread, you should be able to find an example of an init.d script. Several have been posted.
[Nexus S Android Development] 4tticuz:
Using nstools and it works...
[Nexus S Android Development] alen1901:
Nope, no radio dump. I flashed new radio, now we will see if that happens again.

OT, do you know, if i fasboot or flash new bootloader(from google), will i loose root and would i need to unlock bootloader again? I mean, what if i flash new bootloader on my rom with cwm?

Sent from SpeedMachine i9023
[Nexus S Android Development] chappy824:
I can test something for ya. What's up? I'm loving this kernel on 800 max 200 min with great battery life.
[Nexus S Android Development] d_phekt:
I have an i9020T running kernel v3.4.39 with Kalim's latest CM10 and BLN is working fine here.
[Nexus S Android Development] asphantix:
This one isn't for stock, is it? I no longer have an overview :silly:

Why is it needed to have two different builds at all?

So at the end we will have a normal build, a stock version, and stock version for i9023?
[Nexus S Android Development] pan1980:
Using slimjb I have only deep idle top on stats, no top off. Is this normal ?
[Nexus S Android Development] leap_ahead:
i test it now and i will tell you

hahah lol only menu button blink :P
[Nexus S Android Development] italia0101:
Is it normal for 100mhz to be used while charging and not deep sleep ?
[Nexus S Android Development] Phoenix Wright:
I just had a reboot with 3.4.39...

here's the last_kmsg: http://pastebin.com/GDByTWXH
[Nexus S Android Development] vis80k:
everyone's bln working properly with also the led turning off after the time you set?
[Nexus S Android Development] leap_ahead:
sorry i dont know if working..

bedalus i see air kernel Based on Linux Kernel 3.0.40

are u going to update to 3.0.40 ?
[Nexus S Android Development] :
Will look at it now.
[Nexus S Android Development] :
I flashed a ROM that had the new bootloader included a while back, and didn't have to unlock again. I think you'll be okay, but it might be worth double checking in the Q&A section.

That one is not for stock. I need two different builds because I can't work out whether I need to add something from the stock ramdisk to my tweaked ramdisk, or whether I need to remove something from my tweaked ramdisk. It might be possible to have one build, but I need to look at it again.

This is normal. Krarvind doesn't incorporate the framework patch needed for TOP=OFF. Ask someone on that thread if they can do it.

Yes, for all kernels and ROMs, this is standard.

Actually, mine is not. The led timeout is broken. I tested the drain last night, I had wifi, 2G, and the LEDs on, and it still drains only at 1% per hour. It would be more like 0.5% per hour with PM_MAX but it's not worth it.

I'm currently messing with the BLN code to see if I can get just one LED to light up instead of all of them. It worked on the stock ROM for asphantix, I think he uses a i9023. For i9020 (amoled) users the same tweak doesn't appear to work.

I can probably get the timeout back by inserting some new code, but it will mean a script is needed to control it; NSTools will not work.
[Nexus S Android Development] :
There doesn't appear to be any panics, if it rebooted but saved the log, something must have triggered an ordinary reboot.
[Nexus S Android Development] caliban2:
No. The one and only way to lock bootloader again is "fastboot oem lock". Doesn't matter what you flash.

This has nothing to do with root, sigh. But no, you won't lose root when flashing a bootloader-zip or img via fastboot.
[Nexus S Android Development] alen1901:
I just read somewhere on internet that its possible for bootloader to lock itself, so if i unlock it, that would erase everything. Thats why im asking. Tnx for answer. :)

Sent from SpeedMachine i9023
[Nexus S Android Development] :
thanks my friend, I'm using your kernel with AOKP_CRESPO euroskank, coupled fantastic :)

thanks
[Nexus S Android Development] andremarinho:
Plus one ;)
[Nexus S Android Development] smoka206:
Went to back to ICS and I am using this kernel. Using Kangy RR Remix, battery life is amazing so far on the first day, at 14 hours total with 55min of screen time and 45 Minutes of music playback. Phone was idle overnight but radio was on. Awesome kernel is super stable and smooth on this setup.
[Nexus S Android Development] benoit2600:
I have a reboot with the 3.4.39 kernel when I listen music (screen off) with deep idle activated. Here is the last_kgms http://db.tt/tx4qIxht

My ROM: jellybro

Device : nexus S amoled version
[Nexus S Android Development] :
This is really interesting.

Here's a normal sleep and wakeup:

[51107.244642] early_suspend: CPUfreq locked to 400MHz
[51108.196129] pn544_dev_write : i2c_master_send returned -6
[51108.266598] dhd_set_suspend: force extra Suspend setting
[51108.278493] dhd_get_dtim_skip bcn_li_dtim=3 DTIM=3 Listen=10
[51199.476647] request_suspend_state: wakeup (3->0) at 51199665698945 (2012-08-10 09:54:36.201381849 UTC)

and here's where it had an unhandled fault:

[51204.267653] early_suspend: CPUfreq locked to 400MHz
[51204.621313] dhd_set_suspend: force extra Suspend setting
[51204.628996] dhd_get_dtim_skip bcn_li_dtim=3 DTIM=3 Listen=10
[51212.869659] Unhandled fault: imprecise external abort (0xc06) at 0xd5ca0cc0
[51212.869839] Internal error: : c06 [#1] PREEMPT

If you look at the seconds in the first example:51108 to 51199 that's 91s where everything is fine. Then it wakes up. No drama.

In the second example:51204 to 51212 is only 8 seconds. There's no indication that anything was different, just for some reason, a fault wasn't handled.

ARM says:

(source)

...which I barely understand, but I think it could just be a one off crash of the audio handling processes.
[Nexus S Android Development] :
Sweet! I finally worked out how to get init.d scripts to work properly. In the next release you will be able to set smartassV2 automatically at boot.

Also, in the next release I'm raising the DI sleep freq back to 800 MHz, because I'm still not convinced 400 is stable. :(

I'm going to remove blinking from BLN. I actually seem to have broken it completely at the moment though.

Also, thalamus thinks that 3.0.31 was the last stable stable, so I may revert all the mainline patches back to this point also, or just rebuild from scratch.
[Nexus S Android Development] madd0g:
+1,

.39 is just so goddamn unstable, I went back to SimpleKernel.
[Nexus S Android Development] gregorypeg1000:
For me the kernel is rockstable.Using with jellybro.I always have di enabled,1200-200 smartassv2,bln blinking works.I set it with the blncontrol pro.No problem at all.
[Nexus S Android Development] :
Well, i may just keep rolling with the updates. I'm not sure which way i want to go with it yet
[Nexus S Android Development] madd0g:
You know how it is usually - do as _thalamus suggests, saves wasted time ;]

I'd use thalamus kernel at the moment if it had bln, SimpleKernel runs great, but I miss highbigmem. Ah, nothing's ever perfect enough... :]
[Nexus S Android Development] MrBigWaffles:
I've been using the latest update and its really stable with the jellybro mod. Deep idle is working fine.

No complaints here.
[Nexus S Android Development] shivasrage:
hi bedalus

I use .39 kernel since release and had no reboot sod's or other issues at all.

Kernel seems to be stable every time.

Also your kernel is the only one where BLN-blinking works without problems and no reboots.

The battery drain is also O.K.

For me kernel works....always....

Thanks, S.R. :)
[Nexus S Android Development] alen1901:
Your latest kernel is too good to be true. Everything works. I will update only if you update to 3.0.40. And thats maybe. Im happy now, awesome battery and smoothnes on 800mhz. ;)

Sent from SpeedMachine i9023
[Nexus S Android Development] caliban2:
Same here, 3.4.39 is stable, good balance between battery & performance on smartassV2. I still think that one reboot was rom-related, not kernel. At least it didn't crash on last two versions of jellybro. Didle@400 working fine. :)
[Nexus S Android Development] pitmaster:
Nice work....been 2 full days on my ns4g and not an issue....everything I use works. Thankee sai

10....0011....10101