yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] TigaTiger:
Yeah um... ill look into that further. But thanks for helping.
[Nexus S Android Development] explorer-10:
So what's the verdict for everyone here using v19.5 vs v20.0?
[Nexus S Android Development] :
V20 has a power saving for amoled users, but slcd users are reporting problems.
[Nexus S Android Development] caliban2:
... not all slcd-users... ;)
[Nexus S Android Development] VaksenDK:
Yep. That pretty much sums it up. Maybe with the litle addition; most slcd users (including myself), but not all.
[Nexus S Android Development] dvdy:
Just bumping an existing bug, could you take a look at this mathkid?
[Nexus S Android Development] atl4ntis:
Same here aswell
[Nexus S Android Development] TigaTiger:
Just did some research on decompiling the framework. And it looks like its quite hard (well for me it is) to do. I guess im just going to deal with this than.
[Nexus S Android Development] Drizzy xS:
Is it just me or does deep idle not actually save battery using music? Cause I mean I'm using it with paranoid Android ROM and even though to = off stats show up it doesn't actually seek to be saving power like I'm still losing about 20 percent pet hour of music..?
[Nexus S Android Development] :
Hmm. Maybe try a different ROM. Deep Idle has been proven to save power. Check out nathanson666's incredible study using specialist equipment (designed to measure power output across synapses) http://xdaforums.com/showpost.php?p=23514288&postcount=490
[Nexus S Android Development] jimdem:
I've heard from other users here in Greece that they also have matrix and whatever rom they install, it keeps doing this. It happened to me again this morning as well. Please take a look at it. Thanks ;)
[Nexus S Android Development] mixtapes08:
@dvdy this happens because matrix have a UV voltages and nstools will not help your problem because nstools boot up values will just be implemented if you succesfully boot into Android. What you should do is activate or check use init.d script in settings bar of nstools then increase int voltages by +25 across the board. in this case nstools will create a init.d script that will immediately work when you power on your device.

Sent from my Nexus S®
[Nexus S Android Development] glennkaonang:
Follow these two user-friendly tutorials. I'm sure you can get through it with some more efforts.

Bluetooth Deep Idle Fix by wildestpixel

[MOD] Decompile and Rebuild ICS framework-res.apk without errors by stars2
[Nexus S Android Development] dvdy:
Wow that was simple, didn't know it had to be through init.d. Increasing +25 for int only didn't work though, it still froze but it was fine after I had +25 on arm too. Thanks! I'm back on Matrix
[Nexus S Android Development] mixtapes08:
Im glad to know that :) i suggest only int voltages because that was the only uv values in matrix while arm voltages is stock voltages.

Sent from my Nexus S®
[Nexus S Android Development] TigaTiger:
Thanks, ill just ask the guys in the thread for further information!
[Nexus S Android Development] Skyline969:
Oddly enough, after flashing this (20.0 CFS, yes I did wipe dalvik prior to flashing) my kernel still says the one I got when I flashed Kangy Ultra initially. I also do not have access to the additional CPU governors. What gives?

EDIT: I tried rebooting to recovery, wiping dalvik again and re-flashing the kernel, and it stuck this time. Just had to do it twice for some odd reason.
[Nexus S Android Development] Paragon_X:
Hey mate I play my music min 2 hours a day and I've tried every combo possible to find a battery saver. I can definitely say that CM latest nightly along with this kernel has done the job. My numbers are absolutely phenomenal and I can confirm deep idle works and saves battery
[Nexus S Android Development] dvdy:
Actually, raising just the int voltages seems to work. I think NSTools wasn't updating the init.d script properly at first so when I tried, it still crashed. I tried again by just increasing the int voltages and checking the script to make sure the right values were there, powered off and on and it was fine.
[Nexus S Android Development] mixtapes08:
Good job :)

Sent from my Nexus S®
[Nexus S Android Development] SA-07:
v20.5 coming soon!
[Nexus S Android Development] Dynamo Nath:
apologies for the noob question...

i'm struggling to find out about the bigmem mod. I've read that it takes memory from the camera and other places. having installed this kernel, how do I know that the mod has taken effect?
[Nexus S Android Development] SA-07:
If you go into menu->manage apps->ALL

and look at the bottom at internal storage and you can see a lot of free memory (~700 mb for me)
[Nexus S Android Development] Pi3rluigi:
I can confirm,777mb
[Nexus S Android Development] Dynamo Nath:
Thanks for taking the reply to answer my noob question :)

I think perhaps I've misunderstood which memory this mod effects. I thought it expanded the RAM. Not that I seem to have gained more memory in the section you pointed me towards. I'll reflash and see what happens.
[Nexus S Android Development] caliban2:
Yeah, same here - always thought it increases available ram. And it went from 380 something up to 403 mb... :confused:

The section mathkid pointed to is internal memory (1gb), used and free.
[Nexus S Android Development] DaXmax:
Yo Mathkid, no updates for 3.0.34? :rolleyes:
[Nexus S Android Development] caliban2:
Yo daxmax, you ever care to read the last 10 posts before hitting reply? :rolleyes:
[Nexus S Android Development] DaXmax:
Is becuz im too busy to check back the posts....
[Nexus S Android Development] lupoalberto12:
Please, changelog, now :o !

Bye!

! :) !
[Nexus S Android Development] lupoalberto12:
v19.5 and rom stock.

In the last days I have a sort of "battery drain" and I didn't change anything :( .

I don't know because it happens...

Bye!

! :) !
[Nexus S Android Development] TigaTiger:
A clean install always works for me. Use titanium Backup to backup your system data and apps. (which is everyone besides your messages). Now for me i trust mobile backup II since i find it more reliable the others (others say they"fail" to backup some messages...). So there you go, just do a clean install of that. oh btw if your using v20. some say it drains battery on some phones and saves more/equal battery on others. But what i mentioned way earlier was, try doing a clean install and this will fix your problem (your already doing this anyway).

How to Update or Clean Install Roms and Kernels

Clean Installing Roms:

1) format /system /data /cache /boot

2) wipe dalvik cache

3) flash rom and gapps

4) Boot up for the first time and it should work

5) Optional: Only do this after you booted up once. Flash the kernel.

Updating Roms and Kernels

Wipe Dalvik Cache and Cache before updating
[Nexus S Android Development] caliban2:
... or after updating - just do it before rebooting. ^^

btw, matr1x wipes the two caches during install... guess all other kernels use the same script by now. but better safe than sorry. :)
[Nexus S Android Development] glennkaonang:
Do you use BLN with the blinking mode ON?

If so, it might be the thing that is keeping your phone awake and causing the heavy drain.
[Nexus S Android Development] Harbb:
You've set something to update every 15-20 minutes or so and is guzzling your battery as a result. BetterBatteryStats will tell you what it is instantly.

Edit: Also:

No need to go and click around 50 times to do wipes, this is all you need for CWM based recoveries. Pretty sure TWRP is the same, too. Also note that Matr1x has a cleaning script built in which clears some stuff in the /system directory and wipes the dalvik cache. Also, i'm pretty sure wiping the dalvik cache is meaningless for kernel changes but best to cite someone wiser than I.
[Nexus S Android Development] Billchen0014:
Linaro's tweak?

oops! accidentally beamed from my awesome NEXUS S!
[Nexus S Android Development] TigaTiger:
I wrote that as an "overall" for all roms and kernels. Well from my point of view, factory reset is slow, but if you go into recovery and do that, its much more efficient. And in some phones (eg htc legend) doing a factory reset, doesnt

actually wipe the sd card. Its actually not that hard to do both. Depends on what the user prefers :)
[Nexus S Android Development] lupoalberto12:
Thanks everyone.

I'm using Matr1x CFS v19.5 with ICS 4.0.4 stock after a full wipe and flash rom stock.

It's strange because this "battery drain" is started few days ago, without changing anything.

I'll try v20.5 and then, when will be released a AOKP Milestone with Linaro tweak, I'll make again a full wipe.

Thanks.

Is it possible only in the kernel?

Bye!

! :) !
[Nexus S Android Development] SA-07:
Yeah linaro once it gets on mac
[Nexus S Android Development] lupoalberto12:
What?

Bye!

! :) !
[Nexus S Android Development] SA-07:
I will use linaro once it gets ported to Mac.
[Nexus S Android Development] atl4ntis:
Awesome :D
[Nexus S Android Development] SA-07:
Ok, kernel update!

Just a quick note about FSync Control:

http://rootzwiki.com/topic/14685-28-may-glados-v134/page__st__700#entry607555

To keep fsync enabled, just leave the kernel as is because it is enabled by default.

To disable it, do either:

1. echo 0 > /sys/class/misc/fsynccontrol/fsync_enabled in terminal emulator

2. Go into /sys/class/misc/fsynccontrol/fsync_enabled in root explorer and save the file with the '0' value

Happy flashing!
[Nexus S Android Development] Raboragaroo:
Thanks! Working great.
[Nexus S Android Development] Paragon_X:
currently testing 20.5, thanks!
[Nexus S Android Development] original21:
Mathkid fps is still at 50. I cheched it twice with antutu. Scrolling around feels very smooth.
[Nexus S Android Development] :
Just installed it, set performance governor, antutu 3d (first test, ie lights) maxes out at 56 fps.
[Nexus S Android Development] original21:
I tried it twice i got both times just below 50. Now i am back on 19,5 and it scores just above 56

P.s i did the full test both times.
[Nexus S Android Development] chalan30:
not correct bro

see here

and
[Nexus S Android Development] b1337:
OOOOooo!
[Nexus S Android Development] original21:
Just tried again. Just wiped dalvik and flash kernel. Did i do something wrong?
[Nexus S Android Development] chalan30:
dont instigate
[Nexus S Android Development] mixtapes08:
Try this one.

1. Format /system

2. Wipe dalvic

3. Flash rom

4. Flash kernel

Sent from my Nexus S®
[Nexus S Android Development] original21:
When i get home i will wipe everything (and the sd card) and see how it goes
[Nexus S Android Development] chalan30:
dont wipe the sd card, that has nothing to do with it. wipe system and dalvik and reflash the rom, kernel,and gapps from recovery one after the other and then let the phone boot up. you wont lose data if you use this method. (credit bedalus :) )
[Nexus S Android Development] original21:
Final question. I use nightlies. I always make a clean install and flash

1. Nightlies

2. Gapps

3. Bm tweaks for cm9

4. Reboot and setup

5. Flash matrix

Is that correct? Can i flash the kernel after rom and gapps?
[Nexus S Android Development] chalan30:
Firstly, i only wipe system and dalvik, unless Im flashing an incompatible rom. I wipe system so the rom gets a "fresh start" so to speak, and it leaves my data in place. i cant speak for BM's tweaks as I dont use them but I always flash the kernel in recovery right after the rom before or after gapps no rebooting in between, so the rom goes through the boot process with matr1x and not kalimocho's kernel (or whatever the nightlies have now.)
[Nexus S Android Development] mixtapes08:
edit....nvm

---------- Post added at 02:41 PM ---------- Previous post was at 02:21 PM ----------

i think i have the same problem like original. i did this but still my fps is averaging at 48fps dont know why
[Nexus S Android Development] :
Fsync disable works perfectly!
[Nexus S Android Development] original21:
My phone is i9023. Could that be the problem?
[Nexus S Android Development] chalan30:
which rom are you running? I have noticed some pretty wild variations in benchmarks between roms... also are you overclocking the cpu or bus?
[Nexus S Android Development] mixtapes08:
Yeah were in the same boat

Sent from my Nexus S®
[Nexus S Android Development] chalan30:
idk the different screens could very well be the cause :confused:
[Nexus S Android Development] original21:
Latest nightly. Smartassv2 min200 max1300
[Nexus S Android Development] mixtapes08:
Im on aokp. Yup ive overclock it to max value and set it to performance and yet still the same.

Antutu average:48fps

Quadrant standard:50fps..

Sent from my Nexus S®
[Nexus S Android Development] aLNG:
Mk, I saw from ur source about interactive that boost freq on touch. How is that gov?
[Nexus S Android Development] original21:
Maybe mathkid did the change for the superamoled (i9020) screen and the supetclear (i9023)
[Nexus S Android Development] chalan30:
for original: if you want high scores dont benchmark with governors like smartass. change to performance or ondemand for best results. but seeing how you and mixtapes08 are both having that issue im thinking it might have something to do with the difference between slcd (super clear) and samoled screens?. i really dont know for sure, sorry...
[Nexus S Android Development] mixtapes08:
Definitely.... flash 19.5 and it reach 56fps like what original said.

Sent from my Nexus S®
[Nexus S Android Development] lupoalberto12:
fsync is enable in stock kernel, right?

Thanks.

Bye!

! :) !
[Nexus S Android Development] lupoalberto12:
Ok, so I keep it enabled without changing anything :D .

I flash v20.5 after wipe cache and Dalvik cache and, like the last times, wifi didn't work.

Like the last times, I flash it again without wipe and wifi works :D .

Testing it.

Thanks.

Bye!

! :) !
[Nexus S Android Development] caliban2:
As long as I'm flashing a nightly almost every day, I'll keep fsync enabled as well. One never knows how stable the next one will be. ^^

Apart from that, smooth update to v20.5 cfs. To be honest, it doesn't feel any different to v20, neither good nor bad. :D

And no, I don't care about 50/56 Hz on my slcd. Despite 50 Hz need for speed showed no lags, and I deem that game quite demanding on graphics.
[Nexus S Android Development] TigaTiger:
How to Update or Clean Install Roms and Kernels

Clean Installing Roms:

1) format /system /data /cache /boot

2) wipe dalvik cache

3) flash rom and gapps

4) Boot up for the first time and it should work

5) Optional: Only do this after you booted up once. Flash the kernel.

Updating Roms and Kernels

Wipe Dalvik Cache and Cache before updaating
[Nexus S Android Development] caliban2:
And he posts it again... where did you get this from anyway? redundant wiping and why boot before flashing a custom kernel? :confused:
[Nexus S Android Development] micha3lvd:
This is common to install a new ROM. Always first boot the ROM with stock kernel so it can settle. After it's being settled (apps installed from market etc.) you can flash new kernel and only have to wipe dalvik-cache(not needed for this kernel because it already got cleaner in the file) and flash the kernel.

This is recommended to prevent any errors or problems to appear.
[Nexus S Android Development] :
If you want to stay on the same ROM the proper method is:

Flash cache/dalvic wiper

Format system

Flash ROM then kernel.

No problems with this method.
[Nexus S Android Development] sdhanjal15:
What kind of data could I be losing?
[Nexus S Android Development] caliban2:
full wipe / changing roms:

1. wipe data/factory reset (this formats /data, /cache and .android_secure on sd)

2. format /system, /boot

this leaves you with a "virgin" phone, only bootloader, recovery and radio are left. dalvik-cache resides on /data, so it's gone already.

3. flash rom

4. optional: gapps & custom-kernel. no need to let the phone boot & settle before flashing them.

5. reboot

just updating rom:

1. flash rom-zip

2. wipe /cache and dalvik-cache

3. reboot

optional: if using a custom-kernel, flash it again after rom-zip. most custom-kernels have a script that automatically wipes /cache & dalvik during kernel-install.

the timing when to wipe /cache and dalvik doesn't matter at all, it just needs to be done before rebooting the phone.

one could argue that formatting /system is a good thing on rom-update, as it makes sure for certain there's nothing left interfering with the new stuff. it's not needed, won't be a wondrous bug-solver at all but doesn't hurt. :)

none, as long as you don't wipe /data and /sdcard.
[Nexus S Android Development] micha3lvd:
Was familiar with that setup but the guy asking was wondering why you should do so :)
[Nexus S Android Development] caliban2:
it's because with all these instructions to double wipe stuff and when exactly to do it, people get insecure and start thinking they did it all wrong and that's why their system acts up. ^^

just had an argument with a friend last weekend, when i updated his phone and he went crazy on me because i didn't wipe caches before (!) doing anything else. :p
[Nexus S Android Development] TigaTiger:
Its the "General Way" of doing a clean install, update or roms and kernels. And its also be said numerous times in the CM9 forum. And as micha3lvd said, It's recommended so you dont get errors.

Most people (i think) wipe cache and dalvik cache, since its just temporary storage. And since your just deleteing everything and making a new...lets say directory, you dont need it at all, problems may occur if you wipe it AFTER. Thats what happened to me..
[Nexus S Android Development] Maxxd01:
I'm confused, this kernel is undervolted?
[Nexus S Android Development] mixtapes08:
Yes

Sent from my Nexus S®
[Nexus S Android Development] ziociccio:
is 20.5 better or not than 19.5?

20 version has very very more battery drain.
[Nexus S Android Development] Pi3rluigi:
I disagree,with 20 I had the attached result,tried 20.5 and gone back immediatly!
[Nexus S Android Development] b1337:
learn to laugh waffle
[Nexus S Android Development] chalan30:
ha......

wait wait let me try again

ha-he-heb

****

hang on ill get it

har-h-har

dang can you show me your michael jackson gif again? :)
[Nexus S Android Development] Maxxd01:
What are the stock values? I don't want to randomly mess with those values :P
[Nexus S Android Development] The1Shark:
I agree, I am having the same problem still at 50fps after flashing 20.5. I am using rooted stock.
[Nexus S Android Development] SA-07:
Sorry getting 56 here. I made sure it was 56 too...
[Nexus S Android Development] original21:
I tried it a few times and the max i got was 50. Could that be phone related (i9023)
[Nexus S Android Development] alexdemonumber3:
Any ideas why my processor only goes down to 400mhz when listening to music? I tried setting 200mhz as min with nstools, please help. Otherwise, 20.5 is sharp
[Nexus S Android Development] caliban2:
Because of you I installed antutu & quadrant - both max out at 50... ^^
[Nexus S Android Development] sdhanjal15:
So many battery pulls!!!!!! Keeps freezing
[Nexus S Android Development] The1Shark:
Hey MK it worth recheck. Seems like 9023 related.
[Nexus S Android Development] SA-07:
Ok let me look again

Edit: Yeah I found the problem... it will be fixed in 21.0 (that is IF there is a 21.0 ;) )
[Nexus S Android Development] irtehun:
I'm running 1300 with his set voltages all day and not a single problem.

Have to say best kernel I have tried to date with my current setup.
[Nexus S Android Development] nodstuff:
I'm oc'd to 1300 and min at 200 and live oc of 105% and raised voltages by 15 as MK said and its perfect!
[Nexus S Android Development] technogravy:
does this fix the dull automatic brightness on the i9023, or is that a ROM problem? thats the only problem on my ROM so far.
[Nexus S Android Development] cpaixao:
Yes, Sir. I would like this would solve end up video problem, but it doesnt. Video playback presents failure not only on youtube app, but on every player i could try out here: Galery video player (builted in android video player), ES Player, Mobo Player...

So, MK, i am liking your work very much, but we need to get a closer look into that issue, what you think?
[Nexus S Android Development] aic719:
Oh is it only the i9023 that has the problem? Hmm.. explains why I'm amongst very few complaining about it.

Sent from my ice creamed Nexus S sandwich
[Nexus S Android Development] KBanause:
You mean the problem that it gets brighter but only darker after you turn the screen off and on again? That's a ROM problem and I always have it with stock ROMs.
[Nexus S Android Development] athanaso77:
He is working on it... we are all waiting for next release!
[Nexus S Android Development] ragnarokx:
Just got BSOD when trying to reboot using the app Quick Boot. First time that's ever happened to me on any kernel, strange.

Sent from my Nexus S
[Nexus S Android Development] athanaso77:
I don't think that it's a kernel issue, i use quick boot with no problem.
[Nexus S Android Development] onasri15:
I tested with drew garen and one more from xda. Same thing. Is it my phone ?
[Nexus S Android Development] DaX05:
CFS link is broken in the first post. :(
[Nexus S Android Development] SA-07:
Nope, works for me

What browser?
[Nexus S Android Development] X1111:
mathkid95 i'm waiting for 13.0 beta testing :D
[Nexus S Android Development] DaX05:
Stock lol. I clicked on bfs & it goes thru. But I always use the cfs version.

Beamed from my Nexus S
[Nexus S Android Development] aic719:
+1

Always here :)

Sent from my ice creamed Nexus S sandwich
[Nexus S Android Development] X1111:
do u have any news about ETA , lol ? ;)
[Nexus S Android Development] SA-07:
Sorry, no eta anymore... :(
[Nexus S Android Development] DaX05:
I got the link to work. It had "http" twice & I was getting an error.

Beamed from my Nexus S
[Nexus S Android Development] X1111:
i know , that was a joke ;)

btw, all your firend in my country can't use wifi on ics at all :(
[Nexus S Android Development] athanaso77:
Can't you just fix the video problem? This kernel is pretty good but video problem is a serious one.
[Nexus S Android Development] apatal:
Such a tease. lol :D

Sent from my Nexus S
[Nexus S Android Development] caliban2:
Sweet.

This means amoled-devices, which actually profit from 50, are now running on 56 again and slcd-devices, where some (not me) claim higher batt-drain with 50, still are on 50.

You got it all wrong, dude! :p
[Nexus S Android Development] :
If you want to make an omelette you gotta break some eggs...
[Nexus S Android Development] caliban2:
Yeah, but the idea is great. Just the other way round. ^^ I'm happy with 50 anyway.
[Nexus S Android Development] Imppy:
Is it hard to make two versions?
[Nexus S Android Development] Paragon_X:
Edit: So now 20.5 runs at 56hz. I have a amoled version so suffice to say 50hz in theory would be better in terms of battery drain? Mind you I don't game, music and social stuff.

Edit: GPS issued resolved, maps might have just been taking a while to get going, who knows...
[Nexus S Android Development] Blackcrx:
Same. Lots of freezes also. Back to 19.5 for me
[Nexus S Android Development] SA-07:
Wow is my phone the only one that is stable? I'm a loner :)
[Nexus S Android Development] d_phekt:
Running nice and stable here too. Had some issues with the latest CM9 nightly, but I got it straightened out... definitely wasn't kernel related. Thanks again MK
[Nexus S Android Development] mixtapes08:
Im running the latest version pretty stable. I just got one reboot from yesterday that i dont usually experience in matrix

Sent from my Nexus S®
[Nexus S Android Development] Paragon_X:
Kernel is stable for myself also however CM is an issue. I recall 06/08 being good for me, might have to revert waaay back. So many weird annoyances it's hard to overlook, notification errors, lag drawing up keyboard, etc...
[Nexus S Android Development] d_phekt:
+1.

My phone seemed to find a sweet spot with 06/19. The past few nightlys have been crap for me... but thats why they're called nightlys. This kernel rocks tho.
[Nexus S Android Development] FlatEric0074:
No, had also never any problems with matrix kernel ;)!