yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] samizad:
Best way to find naughty wakelocks is to use BatterBatteryStats. I recommend you buy it from Google Play to support the dev but it's free to XDA members http://xdaforums.com/showthread.php?t=1179809

---------- Post added at 01:39 AM ---------- Previous post was at 01:34 AM ----------

There are no magic settings that work for everyone. You have to play with different settings yourself and experiment. Eventually you will find the settings that give the best battery life and device performance that suit your daily needs.
[Samsung Galaxy Nexus] heo_con184:
I installed BetterBatteryStats since the day I realized my phone doesn't go to deep sleep correctly.

In BetterBatteryStats:

1. Partial Wakelocks : DHCP - Android System + Connectivity Service + etc

2. Kernel Wakelocks : PowerManagerService + wlan_rx_wake + mipi_link + etc

Do you guys have any idea ?

Thanks
[Samsung Galaxy Nexus] stupidslow02gt:
Yea airplane mode and 0% brightness. Please keep questions unrelated to this kernel in the Q/A section.
[Samsung Galaxy Nexus] stellaryt:
During whole night with deep sleep,I was only left 2g signal.But in Battery History details,it seems nearly 60% of the night is awake.Is that normal?Battery drain a little more than before.It's not problem but I just wanna know why did it "awake".I saw BetterBatteryStats,nothing special.

r130,Ondemand with Generic Hotplug,AOKP B31

I think there was not any special app ran in background.But it still awake.:confused:
[Samsung Galaxy Nexus] drawde40599:
Its a legit question!!! Wtf
[Samsung Galaxy Nexus] LKNim:
Using AOKP B31 + r-130

interactive sio

729/1344

Generic hotplug on

Wifi and 3G on

Drop 3% over night

Best battery life ever on my phone
[Samsung Galaxy Nexus] drawde40599:
This kernel is perfect right out the box u don't need do anything BUT!!!! If u buy his app ( link on first page ) there r tweaks for it make even better, if u never used this kernel I'd leave stock a few so u can get the "feel" be4 tweaking it . My opinion
[Samsung Galaxy Nexus] rookie8155:
Amazing..

---------- Post added at 10:08 PM ---------- Previous post was at 10:07 PM ----------

Thanks for your advice. I tried to download his app this evening but I am getting error to download it. May be I will try it tomorrow again.
[Samsung Galaxy Nexus] jericho7:
I've been getting very large amount of wakelocks with r121 and r130 for RILJ and SyncLoopWakeLock, both these go up in the 2000+ wakelock counts, anyone know what might explain this? thanks.
[Samsung Galaxy Nexus] ferris2375:
Huge thread, no instructions in the OP. Would someone mind telling me what I need to do in order to flash this ***** and what needs to be on my phone before I do?
[Samsung Galaxy Nexus] ricko2169:
Any 4.03 based ROM with Root access and a CWM Recovery installed.

Flash the same way you flashed the ROM, via CWM. First boot will take longer than normal.
[Samsung Galaxy Nexus] sluflyer06:
Need to be on a 4.0.3 based ROM. Flash after rom in recovery and enjoy. Remember to always backup before making changes
[Samsung Galaxy Nexus] ferris2375:
Cool, so ROM then Kernel. Now the million dollar question....which ROM should I flash with this bad boy?

:)

Thanks for the help.
[Samsung Galaxy Nexus] DDM123:
Working fine here, I'm just trying to get CIFS Manager working. I tested out my settings on an old N1 and it connected fine. I found this in dmesg:

<3>[ 818.171295] CIFS VFS: mdfour: Crypto md4 allocation error -2

<3>[ 818.171325]

<3>[ 818.171783] CIFS VFS: Error -2 during NTLM authentication

<3>[ 818.171966] CIFS VFS: Send error in SessSetup = -2
[Samsung Galaxy Nexus] Shetlander:
being testing the latest kernal and it is quick! However I noticed a funny glitch with this. When I click on an item in the app drawer it seems to flash briefly before opening. Then when you come out of the app it shows a blank desktop then jumps back to the app drawer. Anyone else noticed this?
[Samsung Galaxy Nexus] aimetti:
I'm using Peter alfonsos and It works great.
[Samsung Galaxy Nexus] coverton341:
Are you on a GSM or an LTE device? That would help a lot in pointing you in the right direction. I personally am running an LTE device and have flashed GummyNEX0.2.6 in conjunction with these kernels and I am more than happy with the performance.

Just make sure after flashing this kernel you navigate to /system/lib/egl and delete libGLES_android.so
[Samsung Galaxy Nexus] franciscofranco:
Either delete the .so file or edit egl.cfg deleting the first line "0 0 Android". I'll include the edited egl.cfg in the next nightlies.
[Samsung Galaxy Nexus] Grims:
Hmm, I'm thinking I misunderstood this. Deleting egl.cfg was a bad thing..
[Samsung Galaxy Nexus] franciscofranco:
Sorry, I meant either delete that .so file or edit the egl.cfg =(
[Samsung Galaxy Nexus] Grims:
No problem. No recent nandroid... anything easy to flash to get it back?
[Samsung Galaxy Nexus] franciscofranco:
Just push egl.cfg with adb to /system/lib/egl
[Samsung Galaxy Nexus] Grims:
Sorry, not the advanced yet. Need to find a copy of egl.cfg and figure out the commands to push it via ADB.

I'll figure it out, thanks :)
[Samsung Galaxy Nexus] sluflyer06:
Been running nightly #4 for 2 hours now. Phone is not really using 700 or 920mhz.

20min 17% 1200

28sec 0% 920

1min8sec 0% 700

12min 10% 350

1h21m 70% deep sleep

All I've done is browse the web, no flash or anything, and a couple texts
[Samsung Galaxy Nexus] craskman:
I am getting this too.

When I used to play with kernels on my nexus one I remember that making cifs as module wasn't enough. There was something else like crypto module or this crypto would be built-in the kernel.

Francisco any though on this?
[Samsung Galaxy Nexus] franciscofranco:
Must be because of the ondemand tuneables, but I don't see a problem with that. Play around with SetCPU ondemand values and find which settings suits you best !

Yes, I will look into the next nightly.
[Samsung Galaxy Nexus] Unoid:
Pardon my ignorance, But with setcpu I'm showing 1200mhz as max with autodetect shouldn't it show 1400?

I am on a 4.0.3 rom.
[Samsung Galaxy Nexus] Grims:
Could anyone help me out with ADB real quick? Having trouble getting it to show the GN connected in the bootloader.
[Samsung Galaxy Nexus] jbdan:
What does this do and is it a must to delete this file?
[Samsung Galaxy Nexus] bigeyes0x0:
@franco: I got the log regarding the BT issue. See attachment
[Samsung Galaxy Nexus] franciscofranco:
Can you just pastie.org it and send me the link? It's easier for me.
[Samsung Galaxy Nexus] vomer:
Hey franco, I am planning on flashing a new rom today. Just wondering if you are working on a new nightly or milestone?

Thanks!

---------- Post added at 11:25 PM ---------- Previous post was at 11:23 PM ----------

file is too big for pastie franco, i put it elsewhere:

http://justpaste.it/vt5

http://justpaste.it/vt6
[Samsung Galaxy Nexus] splus:
Is that with GPU 384 or 512 MHz?
[Samsung Galaxy Nexus] KLUVJ:
franco, just flashed the cmplus kernel to compare to yours. is there any reason why all the benchmarks and overall fluidity of the phone is better with that kernel？ is it the VAUX3 and VUSIM difference？ sorry if this question has a too obvious answer, just curious
[Samsung Galaxy Nexus] LKNim:
It's 512;)
[Samsung Galaxy Nexus] drawde40599:
130, 512 retry

OK, I reinstalled the Rom I'm using and 130 at the same time, and the drain seems to be gone. Rom issue?? Kernel issue?? My issue?? : p, thanks Franco working flawless agn
[Samsung Galaxy Nexus] Drift spunk:
What UC settings are peolple using with 130?
[Samsung Galaxy Nexus] raubkatze:
End of testing r130 (384).

As I wrote above it's ordinary usage for me - some calls, social networks, mail, listen music and browsing.

Flashed r121 now. I'll test it again with same settings.

By the way after reboot (flash kernel) battery jumped from 19 to 54%
[Samsung Galaxy Nexus] Drift spunk:
I mean undervolt, I've taken around 80 off each frequency and so far all is good when benchmarking
[Samsung Galaxy Nexus] franciscofranco:
Hmm I dont see a reason why that kernel would be faster than mine. Sure he did a good job no question there, but after seeing that kernel commits I cant see how or why it could be faster than this.

Thos tweaks you mentioned are already on r130 and are aimed to increase screen on usage since its a simple undervolt.
[Samsung Galaxy Nexus] theMaDHakkeR:
I noticed that with r130 my core and Iva voltages are always at 1000 and 1076 using smarflex. CPU is fine and changes between 840+. This was on the latest cm9 nightly and aokp. Never had that before and also keep seeing wifi usage but not when on data.

Any ideas? I'm using prime03 bootloader with UGLC1 radio.

I also wanted to add that my bench scores went down to stock. That's with 1344 Oc and 512 gpu. I think it mostly started after the 4.0.4 roms popped up.

Thanks.
[Samsung Galaxy Nexus] franciscofranco:
Just wasted 10% - 40m of screen on, 3g/data and music while browsing xda and reading email. Seems legit.
[Samsung Galaxy Nexus] raubkatze:
Try to set default (384) min cpu with ondemand governor and look again.

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

Looks fine. What cpu frequency and governor do you use? It's r130 or new secret nightly? )
[Samsung Galaxy Nexus] franciscofranco:
Secret nightly.

1228/384 interactive with 50% brightness.
[Samsung Galaxy Nexus] raubkatze:
Thanks! Waiting for )
[Samsung Galaxy Nexus] rafael-as:
I'm still testing the r131 with aokp to see with i will have the drain that i had with liquid. But I guess something really changed because I never could use min cpu 384mhz with franco's ( drop signal ) but with r131 it's working. No drop signal at 384
[Samsung Galaxy Nexus] franciscofranco:
There is a r131?
[Samsung Galaxy Nexus] stereoprologic:
You must have missed it :)
[Samsung Galaxy Nexus] sago62:
I have a problem with wifi ... connects, but does not surf! the signal remains gray ….ideas?:confused:
[Samsung Galaxy Nexus] franciscofranco:
Cool because I think my internal build is r145 or something lol
[Samsung Galaxy Nexus] raubkatze:
I lost 10% for 1h 25m (35m screen on) - tapatalk, mail and some calls.

CM9

r121

max cpu 1228

min cpu 729

no uv

interactive gov

generic hotplug off

Try to set min cpu to 729.

But maybe issue with your wifi network?
[Samsung Galaxy Nexus] sago62:
also with 729 ..... I use the wifi shared with macbook ... worked fine yesterday … :mad:

restarted pc and phone ... now it works! mysteries of the occult ....
[Samsung Galaxy Nexus] raubkatze:
Grey signal means that device doesn't connect to google services or doesn't connect to internet at all (eg doesn't receive ip).

It periodically happens with shared wifi on Mac OS. It distributes a wrong ip so device can't connect to internet.
[Samsung Galaxy Nexus] rafael-as:
Sorry, r130
[Samsung Galaxy Nexus] lukasb9000:
So after testing r130 a couple of days now I must say that I too get better battery life with 121! Apart from that it works fine!
[Samsung Galaxy Nexus] rubino90:
Sorry franco before i flashed many kernel with 512 gpu oc but i have problem with glitch screen and some reboot now with trinity kernel with 499 gpu oc my phone fliyng without problem i suggest you talking with trinity for collaboration :) :)
[Samsung Galaxy Nexus] Antob125:
These are 512 correct?

The 384 are in the folder?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] raubkatze:
Yes.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] loudaccord:
Francisco... any chance of grabbing "Vibrator Control" from Ezek?

lol... as awesome as that sounds, I can't stop laughing.
[Samsung Galaxy Nexus] raubkatze:
Finally received my new 2000 mAh battery, flashed latest Skankwich CM9 build and now test r121 (384) anew ;)

max cpu 1228

min cpu 729

no uv

interactive governor

generic hotplug on
[Samsung Galaxy Nexus] ch33kybutt:
Might possibly be due to this early commit ...

Reduce transition latency to 10us on OMAP4 devices

Your kernel has it set to 40us. Makes a noticeable difference.
[Samsung Galaxy Nexus] franciscofranco:
Thank you, I will give it a try.
[Samsung Galaxy Nexus] leelaa:
Hmm this is interesting, allways room for improvement.
[Samsung Galaxy Nexus] drawde40599:
I don't have any issues with 512, but phone seem be faster and smoother with francos old 460 I think it was . Option for few different gpu clock speeds in his app would be cool, I'm guessing he don't do that because of milestone kernel, ( he don't want people messing with it ) but just a guess .
[Samsung Galaxy Nexus] franciscofranco:
I already explained...there is no GPU change-on-the-fly in the kernel so I can't do that in the app.
[Samsung Galaxy Nexus] sago62:
View attachment 994930

It does not seem right ... What is audio.out_1? He consumed a lot....
[Samsung Galaxy Nexus] nklenchik:
Do you have touch sounds enabled/notifications that make sounds?
[Samsung Galaxy Nexus] heo_con184:
Reupload if you can. We can't load your photo.
[Samsung Galaxy Nexus] sago62:
I have not activated any of this ...:mad:
[Samsung Galaxy Nexus] raubkatze:
Check settings. They could be active by default.
[Samsung Galaxy Nexus] sago62:
I do not know what setting ....
[Samsung Galaxy Nexus] raubkatze:
Settings > Sound > System

Settings > Sound > Ringtone & Notifications
[Samsung Galaxy Nexus] mikeandjaimie:
I think he was trying to mean that he was hoping for a 460 gpu version option in your app where we download latest version, like it does with 384/512 selection, not the on the fly option.

I too preferred the 460 version, but understand your reasons for not wanting alot of different kernel versions to make each time. My phone runs 512, so I don't mind, but preferred less gpu stress of 460 and almost no difference in performance that I noticed.
[Samsung Galaxy Nexus] jnr21:
Maybe...sound settings...
[Samsung Galaxy Nexus] relax24:
My main wake are audioout_1 and wlan_rx_wake.

I've not got any key sounds or haptic feedback on keypresses, obviously I have sounds for notifications but my phone's on silent

for wlan_rx_wake I've edited my router so it gives me phone the same IP, and I've given my phone the same static IP on the phone settings itself. My wifi is set to always on even when screen off, however I haven't had this issue before. Saying that I can't complain too much as my phone loses about 4% during nighttime when idle on wifi, and about 1-2% on 2g only and wifi off.

The main hog is my screen, I wish there was something I could do to help battery drain with that (besides never using my phone!) - I've edited auto brightness levels but that doesn't seem to help.

Using r121 - On demand, no uv, no generic hotplug 728/1228 mhz
[Samsung Galaxy Nexus] raubkatze:
AudioOut_1 wakelock as a rule is not kernel's but partial wakelock. It may be notification, keypresses, listen music, navigation voice etc etc.
[Samsung Galaxy Nexus] drawde40599:
Oh I no , just a feature that would make this kernel stand out even more ...... + this thing running so.flawless ur going get bored at some point .....: ) : ) thanks Franco
[Samsung Galaxy Nexus] Turbii:
Hi Franco,

a couple of posts back you said none of your testers experience a lot of battery drain. On most roms though, I do. Only CodeNameAndroid 1.6 (with your kernel) has great battery life.

Do you mind sharing the roms you use to test?

I love your kernel Franco, I would like to get the most out of it with a good rom too.

Thank you!
[Samsung Galaxy Nexus] nikulogical:
Are you doing the Codenameandroid challenge?
[Samsung Galaxy Nexus] Turbii:
Well, not really. Just trying out which rom is best for me.
[Samsung Galaxy Nexus] heo_con184:
There're something Roman should not say.
[Samsung Galaxy Nexus] leelaa:
Franco i have a problem with your app.

When trying to flash the kernel, i can only auto flash, but i would rather download the zip file and flash manual.

I have updated to latest version.
[Samsung Galaxy Nexus] nklenchik:
Can't reproduce that problem here. I get both options.
[Samsung Galaxy Nexus] franciscofranco:
Yes always worked fine with both options.
[Samsung Galaxy Nexus] raubkatze:
You can't manually flash kernel in app. You must:

- download it using app (Download latest nightly kernel > Download .zip > choose build)

- reboot to recovery

- flash downloaded zip
[Samsung Galaxy Nexus] johno168:
Does this mean you've abandoned on demand and min 700?
[Samsung Galaxy Nexus] mikeandjaimie:
I do believe that's what he just said.. Why do people ask a question, get an answer, then ask the same question again, just a different way.. It can't get any more clearer..
[Samsung Galaxy Nexus] leelaa:
Yes thats what iam on about, i have bin able to do it and then it stopped working
[Samsung Galaxy Nexus] franciscofranco:
I'm testing, I have to test everything as much as I can.
[Samsung Galaxy Nexus] CaspaTheGhost:
Made me laugh, one for the ladies...

Phone has got all stroppy on me this evening, to the point of loading circle on app drawer press and an eventual crescendo in the form of an Android reboot.

@Franco

Kernel working great, definitely interested in seeing whether there is any benefit from that commit.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
I can't feel any difference so far, but I'll just release the nightly and let users test for themselves along with all the recent changes. After all this is the nightly branch, gotta test a lot.
[Samsung Galaxy Nexus] jhericurls:
Well i just spent my first working day with 130 and still have 31% left before bed.

15 hrs 44 mins

3 hrs screen time

3g always on and only wifi in the evening.

ondemand with hotplug.
[Samsung Galaxy Nexus] leelaa:
Great, cant wait.

Also i solved the problem i was having with your app. Just cleared data and rebbot :)
[Samsung Galaxy Nexus] pastasauce:
*Drool*

Looking forward to it!

I'm not sure why but I seem to get very little screen time even with my constant shutting off of 3g when not in use and minimal brightness... (either the lowest brightness or a notch up).

I have about 3.5 hrs of screen on time at 15% left, split up as follows:

-1 hour watching a show that's been loaded on SD card (3g, wifi off, lowest brightness)

-1 hour reading an ebook using night theme, lowest brightness

-30 minutes watching a TV show, streamed over 3g

-1 hour of random browsing on reddit/XDA/facebook/Text

Seems low to me... I'm on GPU 384 r130, interactive gov 384/1228. AOKP B29
[Samsung Galaxy Nexus] franciscofranco:
r133:

* More OMAP4 patches for battery and stability

* Since last nightly IVA and CORE voltages were higher on 384mhz cpu frequency than they should've been - this is now fixed

* Interactive governor patches from mainline kernel and android-omap-3.0 for stability and interactivity

* Picked 4 ext4 patches from 3.0.27 patch as they reduce some cpu load and fix some small bugs

* Added BLX mod from Ezekeel - I set it as 96 by default, but the next app update will have support for changing BLX values on the fly

* Updated Simple IO scheduler to its latest code from 2012

* Decreased transition latency from 40us to 10us by ch33kybutt suggestion

* Made the kernel way leaner - removed tons of unused drivers
[Samsung Galaxy Nexus] ChongoDroid:
Nice! Love the direction you're taking with this kernel Franco! Godspeed and party on!

Sent from my francoPhone
[Samsung Galaxy Nexus] Ownatik:
130 has just been amazing. Trying out 133. Good work man!
[Samsung Galaxy Nexus] franciscofranco:
Yep, I decided to go a little wild. In any case if big **** comes at me I can always go back to r121 and build on top of it, thats no problem at all. But I'm sure this r133 will be awesome, I'm loving it.
[Samsung Galaxy Nexus] teiglin:
I'm sure you'll have a big fan to handle that big ****. :D Loving r130 so far, gonna give r133 a spin now. Thanks!
[Samsung Galaxy Nexus] johno168:
Sounds good! Flashing now. What set up should we use with this?
[Samsung Galaxy Nexus] franciscofranco:
Whatever you want to test. I've been testing Interactive as there were some interesting changes to the governor as seen on my repo.
[Samsung Galaxy Nexus] johno168:
I'll stay on ondemand for now, seems to be the best for me.
[Samsung Galaxy Nexus] ChongoDroid:
Well it's perfect time because I recently went on a bug killing spree, I had so many non kernel related bugs that it was impossible to test anything. I had a problem with voicemail settings (fixed with a dialer code, ugh), I also wiped everything by relocking my bootloader and fresh installed aokp and Franco and so far, zero wakelocks. Let's get trippy now haha

Edit: as far as governors I've been pinging back and forth between conservative and interactive. Both seem good

Sent from my francoPhone
[Samsung Galaxy Nexus] drawde40599:
133 '512gpu

I'm already noticing 133 smoother u can really tell going in and out of SMS screen, i was getting a " hickup" coming in and out SMS screen its gone now: )
[Samsung Galaxy Nexus] lukasb9000:
Just flashed r133 and I must say I think my phone never run this good... animations completly fluid and everything really snappy =D

Will see about battery life...

Running 512 gpu with 700/1300 mhz interactive

Oh and a question since I oced the cpu I would expect a performance boost, but at least in quadrant the score for the cpu seems to be a nano meter shorter then for the stock gnex in the graph?

Why is that so? Since my phone feels super fast I dont really care about that...I'm just curious :)
[Samsung Galaxy Nexus] nklenchik:
Perfect timing. I have to be up at 6 am tomorrow and won't stop until 10 pm. Awesome for kernel testing :P
[Samsung Galaxy Nexus] ChongoDroid:
Btw, not trying to thread jack but I just flashed this theme, and it is thoroughly good.

http://xdaforums.com/showthread.php?t=1590491

Edit: with horizontal multitasking it's really functional.

Sent from my francoPhone
[Samsung Galaxy Nexus] carlosaeg28:
I get stuck in bootanimation (and distortion seen my screen, it requires a complete wipe?

Nightly133
[Samsung Galaxy Nexus] Timmyfoxeh:
Um, just a question..

As far as governors go, how does hotplug, ondemand and interactive differ practically? I've understood how they work, what what differences should I expect in terms of battery life and performance?

And before you tell me to compare myself, I'm not asking what is the better one for battery life or performance, just what I should expect. Like hotplug, because of the way it disables the second core on low load I believe should save the most battery in theory, but is the performance hit very noticeable comparing to ondemand or interactive? And about what are your experiences with ondemand vs interactive?

And another much simpler question, I asked it before but didn't get any reply... 1228 vs 1344 clock, is there any major impact on battery to expect, considering they both use the same stock voltages or should 1344 give you a little more performance and very little impact on battery life comparing to 1228?
[Samsung Galaxy Nexus] nklenchik:
Nope, I flashed over 130 with 0 problems.
[Samsung Galaxy Nexus] drawde40599:
Its a kernel not a Rom, try agn, if still an issue just restore ur backup

---------- Post added at 04:26 PM ---------- Previous post was at 04:25 PM ----------

Yep went on flawless,feels smoother, didn't no that was possible but it dose
[Samsung Galaxy Nexus] soapinmouth:
I'm still getting high core n iva voltages
[Samsung Galaxy Nexus] Timmyfoxeh:
Oh and, one last thing.. I know the zips in the gpu_384mhz folder all have the GPU at 384MHz, but the main directory, are they 512MHz or 307MHz? because OP says it's stock clock but reading through this thread, it seems to be 512..
[Samsung Galaxy Nexus] borneanheadhunter:
130 was good. Somehow during 133, the system stutters...
[Samsung Galaxy Nexus] RobbyRob:
133 is so much better speed wise on interactive.
[Samsung Galaxy Nexus] drawde40599:
No stutter here, smooth as butter!!! 133 Actually got rid my stutter
[Samsung Galaxy Nexus] stellaryt:
Yes,tring interactive in r133,feel perfect.:D
[Samsung Galaxy Nexus] jeetS:
interactive 133 feels pretty good so far
[Samsung Galaxy Nexus] carlosaeg28:
I come from GLaDOS 1.27, franco app try autoflash, and did wipe cw Dalvik, insurance something I'm doing wrong: (I'm on stock 4.0.4

edit:

sorry for double post

starts and gets stuck in bootanimation with distortion on the screen