yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] neosynthesis:
4.8.3 broke NSTools BLN, govornor

Hi there. just wanted to share my exp with 4.8.3 upgrading from 4.7.x

Good stuff:

after upgrading, NSTools now has the option to toggle Fast USB Charging. Great!

Others stuff:

NSTools governor now shows "unavailable", but MIUI Toolbox shows smartass V2.

BLN no longer lights up the capacitive buttons, even though BetterBatteryStats shows that it is still eating up battery.

Should I just use a different app to toggle CPU governors, BLN, and Fast USB charging? NSTools brought everything under one roof so i switched to it from SetCPU

what do you guys use? thanks for your advice.
[Nexus S Android Development] CrackerTeg:
I use nstools to write the script like stated in the OP. Then I use fast charge widget to toggle. Nice and simple.
[Nexus S Android Development] kiden:
Actually here is a script that will let you tweak all that, which I use myself: http://xdaforums.com/showpost.php?p=32421499&postcount=3436

---------- Post added at 11:34 PM ---------- Previous post was at 11:33 PM ----------

Disabling Google Now seemed to do the trick. Its weird though, cause I never had to disable it on other Kernels. But I dont use it so it doesn't matter to me.
[Nexus S Android Development] capoooro:
OK the flat part of the graph is with 4.8.3.... It seems definitely better

Tnx
[Nexus S Android Development] :
You know, i had the exact same thing, so i rebooted, fixed permissions, and wiped cache. Might actually have been that a reboot was sufficient. If anyone else gets rapid drain like this, please do a normal reboot (not to recovery) then grab me a last_kmsg please!
[Nexus S Android Development] JokerAce:
It's been about, 9 hours now, no reboots after the latest. However on a check with CPUspy, the 100mhz is not used at all. Well, I don't know if it is a trade-off.. 1200mhz never worked for me for any kernel, now yours is the only one that do. Does the 200mhz-sticky-peanut-butter really pose any problems?
[Nexus S Android Development] kiden:
I was having that same issue, I had to disable any app/script from setting the min freq, then it returned to normal.
[Nexus S Android Development] capoooro:
I've tried to send a PM with the last kmsg inside... after a while it begins again to drain... The server says too long to paste... sorry
[Nexus S Android Development] caliban2:
Zip it. Upload it to pastebin. Dropbox. Google drive. And above all: THINK!!! :banghead:
[Nexus S Android Development] capoooro:
I am with my little daughter.... In a park... not so easy;)

---------- Post added at 01:03 PM ---------- Previous post was at 12:48 PM ----------

here we are... finally at home.

now I can share the kmsg

I hope it works

https://docs.google.com/open?id=0B2tiVR5srvr4TFJveGRrV3BsMDA
[Nexus S Android Development] xis123:
Hi bedalus,

I love this kernel! Runs great with Slim Bean 2.6 & Pimp My Rom tweaks (all enabled except for kernel tweaks) - I just have a silly question, does having the backlight dimmer set to 0ms means its effectively off 99% of the time? If so, how much of an effect does this have on battery life?

Thanks!
[Nexus S Android Development] spider623:
is the 4.8.3 for the amoled models only?

Sent from my Nexus S
[Nexus S Android Development] deani77:
It for all model. I'm on i9023 and using it.
[Nexus S Android Development] jark99:
Can someone link me to the pimp my rom tweaks? I'm using slim as well

Edit**Found it!

Sent from my Nexus S
[Nexus S Android Development] spider623:
off topic what is the fastest jb rom for crespo?

Sent from my Nexus S
[Nexus S Android Development] leap_ahead:
rasbean for me
[Nexus S Android Development] gregorypeg1000:
I am having some freezes/reboots with the 4.8.2 and 4.8.3 versions. 4.8 rocks table. I think that these extra 5mbs of ram cause this problem :/
[Nexus S Android Development] jark99:
Slim for me. Ras lagged on my phone

Sent from my Nexus S
[Nexus S Android Development] leap_ahead:
No problem here !!! I try all version and no reboot
[Nexus S Android Development] polobunny:
So I got another reboot. Using 4.8.3 and kang in my signature.

Last_kmsg too big for pastebin so using Google drive instead

https://docs.google.com/open?id=0B3qECctHgezNbXhael9Ed0tYQ0E

Was browsing some comics using Rage reader and poof, suddenly it froze, then after a few seconds it rebooted to the Google logo. Not the first one though, the "second" one.
[Nexus S Android Development] :
It worked! Unfortunately i can't see anything in there that indicates a kernel malfunction
[Nexus S Android Development] :
Backlight dimmer saves about 1mA if I remember rightly. The info is in my spreadsheet somewhere.
[Nexus S Android Development] :
Unfortunately this is a memory page error, so it looks like I'll have to withdraw Ezekeel's bigmem patch. I'll put the other commit back in.
[Nexus S Android Development] FirePoncho86:
At first, I was like 1.5 hours, already 25%less battery?!?!?

Then I looked at my screen on time..

Dunno if its marmite 4.8, the cna 3.65, cause I flashed both yesterday, but I'm getting some badass battery life.
[Nexus S Android Development] polobunny:
Yeah I pretty much expected that from seeing the end of my log. :p
[Nexus S Android Development] leap_ahead:
fc camera now after take some photo ..here View attachment 1380762
[Nexus S Android Development] vinamilk:
CNA 3.6.6 and Marmite 4.8.3.
[Nexus S Android Development] :
v4.8.4: http://goo.gl/HvUrp

-Revert Ezekeel's bigmem patch

-Unrevert the other memory patch*

-Revert another memory tweak

*If there are still memory bugs I'll re-revert this patch. Basically, it'll be exactly the same as v4.8, but with just the more stable voltages for OC! (Talk about taking two steps forward, one step back :p)
[Nexus S Android Development] anshumandash:
As I did not have any problem with 4.8.3 on CNA & BB5, do you still suggest I update to 4.8.4?
[Nexus S Android Development] Daniel.Stevens:
@bedalus

Hey, I had random freezes and reboots with every kernel BEFORE 4.8.1 on CNA Jelly Bean-Version (at least one every day) but I still stuck with your kernel because it worked really well/fast for everyday use and I could take a reboot once in a while.

After you implemented Ezekeel's bigmem patch the kernel is (at least for me) rockstable and VERY fast/battery saving.

Nexus S GSM/CNA 3.6.5, 3.6.6/i9023xxkl1

So, today I tried 4.8.4 and had 2 random freezes/reboots so far. I went back to 4.8.3 and everything´s perfect again... That´s why I think it has something to do with Ezekeel's bigmem patch.

I think I´ll stay with 4.8.3 until you implement Ezekeel's bigmem patch again. I really don´t know anything about kernels and ROM´s except for what works for me. And your kernel WITH Ezekeel's bigmem patch and CNA works really good for me....

I´m sorry that I can´t give you any more useful information (kmsg etc.)

Just wanted to let you know that your kernel with Ezekeel's bigmem patch works nearly perfect under my conditions (GSM, CNA etc.)

THX !!!!
[Nexus S Android Development] :
I think everybody has useful input to give. It's not possible that bigmem is stable because I've seen a paging error. If your phone reboots again, please try and grab a last_kmsg. Remember to state which version you're using.
[Nexus S Android Development] capoooro:
4.8.3 reboot while messaging with whatsapp. I try 4.8.4
[Nexus S Android Development] kodora:
Random Reboot

Hey bedalus, just had a random reboot while trying to read an sms. Phone was plugged to wall charger and I had just flashed v4.8.4. On 4.8.1 and 4.8.3 stability was great and had no reboots at all. Attached is the last_kmsg! Hope it helps on development! ;)
[Nexus S Android Development] :
Hmmmmmm...... what's going on with this then? I think i need to pull the UN-reverted tweak too. I feel like I'm going backwards! Thanks for all the testing!
[Nexus S Android Development] asphantix:
4.8.3 works perfectly fine for me on my stock rom.
[Nexus S Android Development] :
It's a ticking time bomb...
[Nexus S Android Development] Daniel.Stevens:
I will do that next time it reboots, but to tell you the truth: I had not one single reboot from 4.8.1 to 4.8.3 with that versions my phone is/was rockstable and blazing fast. That´s why I decided to leave you a message in the first place, just to tell you that those 2 versions are awesome ;0)

Every version before that rebootet once a day and with 4.8.4 I had a reboot 1 hour after I flashed it (using WhatsApp).

Since 4.8.3 is so freaking awesome I decided to do a really clean install of cna 3.6.6 with it so I don´t really want to install 4.8.4 to force a reboot ;0(

But as far as I can see some other people are having some issues with the new 4.8.4 and had no issue with 4.8.3 and 4.8.1

You wrote today

What do you mean by that? Is using 4.8.3 in any way bad for my phone ?!?

Thank you ;0)
[Nexus S Android Development] :
No! Nothing bad will happen! :p My phone has very rarely rebooted. The great thing about this thread is the shear number of man&woman-hours that have gone into testing it. If a hundred people download a testing version, then within an hour, the equivalent of 4 days of testing has accumulated. While meddling with stuff since v4.8 i've introduced a memory bug. You can see the things I've done I've done in the changelog. Since it's likely to be one or both of the memory tweaks I can eliminate it by trying the various combinations, rather than resorting to debug versions.
[Nexus S Android Development] CrackerTeg:
Well, I'm going to stick with 4.8.3 unless you recommend to flash the new one. Each and every version I've used has been stable for me. With these incremental updates, its not giving me enough time to fully test. lol
[Nexus S Android Development] :
Stick with it yes. For the cutting edge, 4.8.3 is what i recommend. I'm not 100% certain that that it has a memory problem either. More reboot reports needed!
[Nexus S Android Development] :
v4.8.5 is here: http://goo.gl/HvUrp

-Reverted all memory tweaks since v4.8

-This version is like v4.8 stable but with fastcharge added, and some OC stability fixes for voltage.

If you want to add an extra 4MB try v4.8.3 because they are identical apart from that extra memory! So, in fact, v4.8.3 in some ways is more advanced. However, it may be causing a problem. I'm not 100% certain yet. Either way, both versions need more testing!

If v4.8.5 comes back with a paging fault, then the only other possible culprit is fastcharge. That would be really strange. I'm holding my breath for more last_kmsges!
[Nexus S Android Development] CrackerTeg:
This one I'm definitely going to download. I don't think fast charge would be the culprit tbh. I'm thinking its the memory hacks. Since 4.8 was the last stable before the memory mods, this new version that is essentially that but with fast charge is the one that has my attention.
[Nexus S Android Development] :
I think it will be the one that appeals to most testers. I hope at least a few people still go for the extra memory in v4.8.3 because I've forgotten what kmsg I was looking at when I decided that was the potential cause. I need a new one from that version.

On a complete tangent, for voodoo app users, I now recommend

1951208320 Red

1694245920 Green

1974299520 Blue

...for the initial values, then adjust according to taste.
[Nexus S Android Development] CrackerTeg:
Honestly, I don't think you'll get a kmsg from me as I haven't had an issue. From the few posts I've glanced at in between versions, the majority came from the cm users. I could be wrong though.
[Nexus S Android Development] :
It's possible that the last_kmsg I saw when v4.8.3 was released contained no page fault. I can't remember. I'll have to scour backward through the thread. Tomorrow, because I'm overdue to go to bed!
[Nexus S Android Development] Articudos:
Why the # exists in max/min freq- related line..?
[Nexus S Android Development] JokerAce:
Because when you put a # in front, it becomes a comment instead of a executable command. The user didn't want to execute that command, thus he did that. When he want to, he simply just remove the # sign.

---------- Post added at 09:43 AM ---------- Previous post was at 09:41 AM ----------

Hey Bed, if I experience lag and freezes but no reboots, can I do a reboot and pull the kmsg? Will that help?
[Nexus S Android Development] CrackerTeg:
I'd say that would help. It might have info on the lag.
[Nexus S Android Development] Articudos:
I know, but why did he exclude min/max freq. command?
[Nexus S Android Development] JokerAce:
Because he want's to use stock min/max freq values. Unless you want to make changes to that, you can exclude those commands. The kernel will use dev default values. For instance, if he wants to use 1200 mhz, he will then remove the # sign from the max freq and change the value to 12000000.
[Nexus S Android Development] JokerAce:
Hohoho, not sure if it's good or bad news, but I had my first reboot on 4.8.3 after 28 hrs. Look at attached

EDIT: More to come. Oh no... whats happening :crying:
[Nexus S Android Development] srthimsen:
First reboot with 4.8.3, rasbeanjelly ns4g.

Last_kmsg:

http://db.tt/0CIA0pTU

I was using Google maps at the time, which was having trouble acquiring GPS signal.
[Nexus S Android Development] migz012788:
can't understand the difference between 4.8.3 to 4.8.5? i am using 4.8.5 now.
[Nexus S Android Development] JokerAce:
from here you can see that the main difference is the 4MB extra RAM 4.8.3 has over 4.8.5
[Nexus S Android Development] :
No kernel errors in there. What ROM are you running?
[Nexus S Android Development] :
This one is interesting because it's got a null pointer dereference, which is bad!
[Nexus S Android Development] neosynthesis:
4.8.5 broke camera?

First off, thx, kiden, CrackerTeg, got my scripts running and no longer needing NSTools.

Observations so far 4.8.3

I noticed that 4.8.3 was more battery draining than 4.7.x. With only GMail, contact sync turned on in the background, HD Widgets set to pull weather info only once every 2 hours), after an hour of text and one 10min call, i lost 30% battery life from 100%. Phone battery was already calibrated the night before using MIUI.US Tools. I know I probably should let the kernel 'settle'.

4.8.5 camera issue.

Don't know if you guys encountered this: installed 4.8.5, the camera app could launch as usual but when i pressed the shutter to take a photo, nothing happens. After a few tries, it FCed. Restarted the camera app, same thing. Restarted the phone, same issue was reproduced on first try.

Flashed back to 4.8.3, camera was working again on first boot. Anyone else had this?
[Nexus S Android Development] :
That's really odd. I think I need to check over the code. I've gone forwards and backwards and I may have lost track of something.

Camera is working fine for me on v4.8.5. I need more feedback!
[Nexus S Android Development] JokerAce:
See my sig.

Btw, are there any difference in these commands?

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

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

What's the diff in kmsg and last_kmsg? Does that mean that there are many kmsg files?

The attached, 4 is from proc/kmsg and 5 is from proc/last_kmsg
[Nexus S Android Development] migz012788:
Got plenty of reboots on 4.8.5 and sorry i didint manage to get the last kmsg :( now i am trying 4.8.3 now. I can feel that version is much smoother and better

Sent from my Nexus S
[Nexus S Android Development] :
PA is based on CM nightly I think. Could be that the new features in there are causing reboots.

The last_kmsg is just a backup of your ksmg made just before your phone restarts (if possible). So if you cat the current kmsg, it tells me nothing really, because no error has happened yet!
[Nexus S Android Development] :
I don't think that 4MB extra RAM is going to make it smoother. It might mean under some circumstances you can keep an extra app open.
[Nexus S Android Development] vinamilk:
I'm on 4.8.3 now for 2 days without any reboot. Battery is very good.

Confirm that colors are better than before. Good contrast, more saturated colors, white is white.
[Nexus S Android Development] :
I'm compiling a debug version, should be up within about half an hour. I've rolled back to v4.8, ad re-added fast-charge. This is better than trying to revert the individual bits of code I've changed since then, because I now know exactly where I am. Unless I'm mistaken, this is going to be identical to v4.8.5 (which I've pulled) but with all the debug options included, which makes the last_kmsges easier to interpret.

If you're happy with v4.8 stick with that. If you need fastcharge, use v4.8.3, and if you've had a reboot, please consider using the debug version to help me locate where they are coming from.
[Nexus S Android Development] migz012788:
did you overclock your phone using that version of kernel?
[Nexus S Android Development] :
debug versions are up: http://goo.gl/HvUrp
[Nexus S Android Development] vinamilk:
Nope, default speed at 1GHz. That's enough for me.
[Nexus S Android Development] gregorypeg1000:
4.8.4 is perfectly stable for me at stock speed. (1ghz) battery drain is just a flat line at idle. Awesome work bedalus!

Rom jellyb - tsm (aosp)
[Nexus S Android Development] Articudos:
Hmm...why did u pulled v4.8.5?

It's stable here....:)
[Nexus S Android Development] :
I'm considering readding bigmem, but I'm not sure the kernel is stable. With enough bug reports from v4.8.3 and the debug versions, I should be able to figure out if the problem is bigmem or a pre-existing issue that just popped up by coincidence.
[Nexus S Android Development] caliban2:
Can't give you any logs, so far the so-called timebomb "4.8.3 CM" is still ticking... :p
[Nexus S Android Development] beppegg:
Bedalus I'm that guy experiencing seldom reboots even on kernel that other used find stable.. If you think it would be useful, I'll flash the debug kernel; otherwise I'd stay with 4.8.0

I'm on rasbean with i9023 nexus!

Inviato dal mio Nexus S con Tapatalk 2
[Nexus S Android Development] FirePoncho86:
Reached 50 hours uptime on 4.8.

I'm gonna go as far as I can!
[Nexus S Android Development] :
Yes, maybe use it for a day, and try all your apps.
[Nexus S Android Development] :
http://xdaforums.com/showthread.php?p=32497021

I'd appreciate it if someone could help this with ROM, they decided to integrate my kernel and need a tester
[Nexus S Android Development] FirePoncho86:
It occurred! Lol at your pic though
[Nexus S Android Development] CrackerTeg:
There's something really wrong with this debug kernel. My phone is fast, responsive and I don't know what to do with myself. Damn you bedalus for putting out good product! Damn you!
[Nexus S Android Development] :
@Erythnul That is a really detailed description. I can link to it from the OP, or you could start your own thread in general, or both. Let me know.
[Nexus S Android Development] anshumandash:
Wanted to give some feedback. I am running 4.8.3 on BB5 for last 30 hours. No reboots. SmartassV2, 200-1200. Have tested some games like temple run & others. Running quite stable.
[Nexus S Android Development] :
I'm struggling to interpret this last_kmsg, not least because it's from a non-debug build. I would have been able to use grep to scan the system.map using the instructions from the stacktrace, except the system.map needs to be from the same build, and there's been a few builds since then. I need to introduce a policy of archiving the system.map to avoid this problem in the future. I'll add that function into my build script!
[Nexus S Android Development] neosynthesis:
overwhelmed! thank you!

wow, Erythnul! i'm totally overwhelmed by your detailed, thorough tutorial with great screenshots to boot. thank you for sharing your expertise and giving us a huge boost in learning to troubleshoot our own battery drain issues.

last but not least, congratulations is in order: uncle Erythnul! :good::good::good:
[Nexus S Android Development] Articudos:
Guys, If you are using BBS and want to analyze dump file by yourself, this thread might help.:)

http://xdaforums.com/showthread.php?t=1827676
[Nexus S Android Development] ebs512:
still nobody has gotten back to me on beta testing this for us, if someone with a crespo device is online right now please get ahold of me if you want to beta test bb6
[Nexus S Android Development] DarkhShadow:
I would be willing but it would need to wait until I'm home :/ (7 or so hours)

Sent from my Jelly Nexus S
[Nexus S Android Development] ebs512:
when you get home later, add me on google talk ebs512@gmail.com
[Nexus S Android Development] DarkhShadow:
Gonna add now or I will forget xD
[Nexus S Android Development] beppegg:
+1, I'm having the exact same experience!!! =)
[Nexus S Android Development] alen1901:
I would like to test too, but only tomorrow or the day after tomorrow. My phone is still on repair.

---------- Post added at 01:14 PM ---------- Previous post was at 01:10 PM ----------

Bedalus you got a lot of kernel versions there. Thats better, i will test them, also i will use debug version to help development, in few days. :thumbup:
[Nexus S Android Development] N_E_X_U_S:
I'm on CNA rom 3.6.6 with the latest bedalus kernel. When uploading picture to Facebook it always stack in the middle.

Any suggestions?
[Nexus S Android Development] alen1901:
Why you posted here? I can suggest fixing permissions and wipe cache. Than try. If not working wipe app data which you use for upload. The last thing is to reflash rom.
[Nexus S Android Development] mishamosher:
Got reboots with marmite 4.8.3 and CM10 official nightly of October/07. Everything freshly wiped.

Rebooted two times without charger plugged in, at around 2 hours of playing Asphalt 7, in 1.2 GHz step with SmartAssV2. Then played with charger plugged in and it didn't happen again, with 5 hours of playing.

Only managed to get one last_kmsg, which is attached.

The reboot was 'total' (Google and lock boot loader screen showed, wasn't reboot from boot animation).

Hope it helps :cyclops:
[Nexus S Android Development] mishamosher:
And my device is a i9020A!
[Nexus S Android Development] caliban2:
Getting to 24 hours with cm nightly 1007 and marmite 4.8.3. No problems at all, smooth and stable so far. Browsing, calls, YouTube, watching movies - you name it.

Will do a full wipe tonight as I'm having trouble with album art and gallery cache, but that's not kernel-related.

Anyhoo, so far absolutely no sign of trouble with stability, loving it! :thumbup: :)
[Nexus S Android Development] capoooro:
4.8.3.... strawberry 35 hours no troubles at all

CFS

On demand

No oc
[Nexus S Android Development] Erythnul:
Linking to it in the OP would be great. If I make a new thread in General, it'll get buried over time anyway, this way it's always linked as long as it's relevant, and I'll also link it in my signature. I've edited it to include the link Articudos mentioned (Thanks! I totally forgot about that post! :)), I remember reading that back when it was originally posted, quite a bit of my knowledge is from that thread. Also, it's quite a bit more detailed and thorough than I've been in my tutorial, I heartily recommend it to everyone.
[Nexus S Android Development] towelboy:
A problem with 4.8.3(CM) that I found was that when opening gallery, quickly switching between photos in any folder will force it to close, although no force close screens comes up.
[Nexus S Android Development] caliban2:
Just flicked very quickly through an album with 64 pictures - can't reproduce...
[Nexus S Android Development] towelboy:
Hmm weird, I can easily reproduce it. Maybe I'll wipe some stuff and reflash haha

---------- Post added at 01:31 PM ---------- Previous post was at 01:28 PM ----------

EDIT: reflashed, now everything is fine except the screenshot folder. Can you try to see if yours is affected any chance?
[Nexus S Android Development] Ser Gilgoroth:
I'll be helping where I can in regards to the below post.

____________________________________

http://xdaforums.com/showthread.php?p=32497021

I'd appreciate it if someone could help this with ROM, they decided to integrate my kernel and need a tester