yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] rabhw:
I'm getting so-so (I think?) battery life, 37% after ~12h with light-moderate use. Auto brightness. Attached screenshots if those help at all. I only installed BetterBatteryStatus halfway through the day, so these numbers might not be accurate, but wlan_rx_wake seems to be the primary wakelock, is that normal?
[Samsung Galaxy Nexus] sluflyer06:
I'm not sure what's affecting battery life for me, I can say for sure the phone is kicking out of deep sleep a lot, where it never did before and idle battery use is way up from 4.0.2. What radio are you using Francisco? I had do move away from xxkk1 with 4.0.3 because constant disconnects.
[Samsung Galaxy Nexus] wobbu:
The night before (stock 4.0.2) : 63% to 60%

Last night (AOKP + Nightly #2) : 90% to 80%

I too cannot tell if it's 4.0.3 or this kernel, more testing needed.
[Samsung Galaxy Nexus] craskman:
franco,

Please add cifs.ko module on #3 , you have forgotten on #2.

'brigado
[Samsung Galaxy Nexus] jimyen:
Please don't remove UV, its working just fine for me. Nightly #2.

I"m guessing it's not working only for LTE.

Ondemand.
[Samsung Galaxy Nexus] sluflyer06:
Try setting one so low it couldn't run and apply.it and see if works.But don't apply on boot obviously
[Samsung Galaxy Nexus] MKVFTW:
I am not 100% sure but isn't there some sort of chip level protection that doesn't allow undervolting below specified limits. It was that way with the SGS2.
[Samsung Galaxy Nexus] SS2006:
Is oc in works . I remember reading this cpus native speed is actually 1.4
[Samsung Galaxy Nexus] Mondfahrer:
going grey and therefore no internet connection. If I turned wifi off and on again everything is working, only standby-mode is doing some crap :mad:

Actually, if the bars turn grey there is no connection to google account, am I right? But why is there no internet connection at all on my GN? I can´t connect Whatsapp, Facebook etc.
[Samsung Galaxy Nexus] resynx:
I'm losing wifi, it's switching over to 3G.
[Samsung Galaxy Nexus] Mondfahrer:
That´s another issue on my GN. After my Wifi bars turn grey, there is no internet connections at all and it is not switching to 3g, it´s just staying on wifi with grey bars:rolleyes:
[Samsung Galaxy Nexus] zephiK:
What radio are you guys using? did this always happen? try isolating the problem. Go back to stock kernel. Problem occurs still? then it's not kernel related. I don't want to make this topic go out of topic because I don't think it's kernel related at all. I don't have this problem at all, franco r112 + aokp b29 + xxla2 + primela3 bootloader

Other than that, r112 has been extraordinary on battery. It's the best I've ever seen in idle. Not even losing %.
[Samsung Galaxy Nexus] mikeandjaimie:
correct, grey means you are only loosing sync to Google, not the actual wifi or net connection. I too have noticed that I have a hard time connecting for a minute, but it always reconnects writing a minute. This isn't kernel related though, as it happens on aokp stock and Franco. not a problem for me, add it only happens rarely, and connects again when I screen on
[Samsung Galaxy Nexus] Mondfahrer:
I am using XXKL1 for +1 month and never had this issue before, that´s why I thought it could be a Kernel issue. This happened since r110 to me.

I am trying to figure out, why I dont have a internet connection at all after turning grey and why it is not switching to 3g. Maybe I should go back to M2.
[Samsung Galaxy Nexus] zephiK:
Oh yeah... I forgot to include, what is your minimum frequency set at? I remembered that some phones have problems with screen off and screen on and losing connection. Set it to ~700 as the minimum and set it on boot. See what happens, that could be the problem.
[Samsung Galaxy Nexus] Mondfahrer:
I´ll try it with ~700, thanks and have a gn8
[Samsung Galaxy Nexus] zephiK:
Hope it fixes it for you. I remembered putting that as a solution to someone's problem with connectivity in the Q&A forum once. Report back if it helped or didn't help, I hope it does.
[Samsung Galaxy Nexus] resynx:
Wow that seems to have fixed the problem! Thank you so much for your help ^_^

Will setting the minimum at 700 have a negative effect on the battery life though?
[Samsung Galaxy Nexus] zephiK:
I remembered people debating about that earlier in this thread. Look a couple of pages back, I've had my minimum frequency at 700 and don't see any problems with battery life.. on GSM model, 2000 mah.

But I mean, I think at this point you would rather go with the 700 mhz than to have your connectivity issue :p you can leave it at 700 and see if you notice a difference in battery life or not. That's the best way to check.

I believe if I remembered correctly it went somewhere with the lines that it doesn't impact your battery life much because your CPU spends a lot of time in 700 frequency anyway. I THINK thats what I read a couple pages back, but I don't have the time to find it. You can do it if you want to see where that post went, it was in this thread.
[Samsung Galaxy Nexus] Felixpau86:
I think it depends on what you do. I spend the entire day at work streaming radio so my phone idles at 300ish... not that it really matters since I charge my phone at my desk anyways.

But without a charger im pretty sure 300 and 700 would make a difference on battery life.

With just occasional use id wager that there isnt a big difference since your phone should be idling/sleeping...
[Samsung Galaxy Nexus] mikeandjaimie:
Close.. it came down to the race to finish. At 7xx it finishes it's tasks quicker than at 3xx so going back to idle quicker, hence using less power.

I've tried both and you really don't see a difference in battery life, if it helps with stability, go with 700
[Samsung Galaxy Nexus] franciscofranco:
I tested 384 the last two weeks and I really hate it, not only gives me less performance, but in the end of the day hinders the race to idle and thats something I don't want at all on my device. 729mhz for the win =)
[Samsung Galaxy Nexus] nikulogical:
Franco why was oced gpu introduced again? I thought anything above a certain amount didn't bring any benefits and just hindered the battery?

Also does anyone know if the stock kernel has been changed with 4.0.4 and where I could find it
[Samsung Galaxy Nexus] franciscofranco:
Nightlies have gpu overclock because generally nightlies users are the type of persons that like to have their devices pumped up with some extra performance. At the same type who wants stability -> Milestones with stock gpu.

Yes stock 4.0.4 is changed from 4.0.3.
[Samsung Galaxy Nexus] nikulogical:
I understand that but didn't Colin Cross say something like it won't affect performance much? I just thought something changed and u added oced gpu as a result. Fwiw im running the latest nightly with the highest gpu option and even though my device can handle it I'm not sure where I'm supposed to see a performance difference. Nothing changed on terms of gaming over video for me.
[Samsung Galaxy Nexus] franciscofranco:
Colin was and is right. There is almost no noticeable performance increase and since it will possibly waste a little more energy they decided to reduce the frequency to a lowest OPP. Still that doesn't matter we shouldn't use it. I use 512mhz and I notice extra smoothness over stock frequency. Is it using more energy than before? Dunno, who cares?
[Samsung Galaxy Nexus] samuelfrm:
The camera work? greetings.
[Samsung Galaxy Nexus] inffy:
This is a kernel thread....
[Samsung Galaxy Nexus] BryanChung:
I am planning to switch from Trinity to this Kernal. But I am not sure to go for Milestone release or Nightly release now. Ha. :D
[Samsung Galaxy Nexus] :
just a note, on r112, my GNex has (occasionally) random reboots on "Interactive" Governor (384-13xxMhz)

However after I changed to "On Demand" Governor (384-13xxMhz), no random reboot.

Hope this piece of info helps ;)
[Samsung Galaxy Nexus] kashix:
once you go nightly, you'll never go back.
[Samsung Galaxy Nexus] BryanChung:
Haha so serious? :D
[Samsung Galaxy Nexus] AnthonyAldrete:
For someone that uses there phone most of the day to stream music, what would be a good min and max freq. setup?

btw, im on the 112 and its running so smooth thank you =)
[Samsung Galaxy Nexus] Colpophage:
flash-o-holics rarely joke :)

Swyped on my rooted 4.0.4 AOKP(29) Galaxy Nexus with XDA app
[Samsung Galaxy Nexus] BryanChung:
I'm just wondering do I need to be on nightly that's why. :P Convince me pls. =X
[Samsung Galaxy Nexus] kashix:
stick with default. 384/1228 ondemand.

---------- Post added at 12:51 PM ---------- Previous post was at 12:47 PM ----------

you already shelled out a premium for the device, why would you want to hold back in giving the best to your device? give me 1 reason not to go nightly?
[Samsung Galaxy Nexus] AnthonyAldrete:
okay will try it out thank you
[Samsung Galaxy Nexus] BryanChung:
Hehe. But what can I do in nightly that I cannot do in milestone release? :o
[Samsung Galaxy Nexus] sg1969:
Why don't you read the changelogs? Do the nighties after m2 add anything useful to you? If yes, get nightly, if not maybe stick with m2. We all want different things from our phones and use them differently, it's difficult to say "this is what you should use".

Technically you "should" use m2, since nighties are considered test builds.
[Samsung Galaxy Nexus] rafi300:
Basically , nightlies will add new features and unforeseen bugs as they are self implemented tweaks by the great Franco. The nightly adapters are the testers for the new tweaks that are added, updated and fixed to create a milestone stable, error free kernel.

So if you want to live on the bleeding edge of gNexus technology , than Franco nightlies are the way to go . Otherwise, Milestone is the most stable and battery friendly ROM and error free.

Sent from my gNexus using a Swyping thumb!
[Samsung Galaxy Nexus] BryanChung:
Yeah okay! :D
[Samsung Galaxy Nexus] asim0:
Om nom nom

I love milestones!

AOKP M4 + francoKernel M2
[Samsung Galaxy Nexus] cyanoviper:
by the way i have the same issue: grey bars on wifi or 3g means no internet. i noticed that before on other kernels and roms, so i guess its not kernel related. i have no idea what it is though, doesnt make sense to me
[Samsung Galaxy Nexus] odin13:
i thought the grey bars only meant there is no connection with the google servers...internet should be working though
[Samsung Galaxy Nexus] cyanoviper:
i know its supposed to mean there is no connection to google, still i cannot access the internet when the bars are grey.

oh and i just had a random reboot... i attached my last kmsg and apparently it was a "warm software reboot"
[Samsung Galaxy Nexus] franciscofranco:
Increase min freq to 729mhz, done.
[Samsung Galaxy Nexus] franciscofranco:
What triggered the reboot? Did you turn off wifi and it rebooted?
[Samsung Galaxy Nexus] cyanoviper:
no i didnt, i pushed the power button to lock it, put it on the table and after some time i wanted to check something and it asked for a pin and the battery menu said it had been ruuning for 10 minutes. wifi was on when i locked it.
[Samsung Galaxy Nexus] lcheng1:
Just curious, is the GPU clock 307Mhz or 512Mhz on the nightly builds? I know that in the OP it states 307Mhz, but there's some mention of 512 in the thread so I'm just double checking.
[Samsung Galaxy Nexus] Remoteconcern:
Milestones are 307 (stock).

Nightlies have the option of either 384 or 512, selectable in app when you press download nightly.

Hope that helps.
[Samsung Galaxy Nexus] :
I too had random reboots with r112:eek:
[Samsung Galaxy Nexus] lcheng1:
Thanks! Is there any way to get 512 without the app though? Or is there a way I can get the app through donating with Paypal? I don't have access to a credit card unfortunately so I'm unable to purchase market apps.
[Samsung Galaxy Nexus] franciscofranco:
Yep I know what it is, it happened with me as well.

512mhz and 384mhz.
[Samsung Galaxy Nexus] cyanoviper:
Yes! search for the downloadlink in the first post and get one of the regular nightlies (they have 512) or get a 384 one from the 384 nightly folder if you ever wish to.
[Samsung Galaxy Nexus] sago62:
no build of 4.0.4 official?:D
[Samsung Galaxy Nexus] franciscofranco:
Sorry?

I'm going all aggressive on next build and merge android-omap-3.0 branch changes to my exp branch, there are some interesting things in there. I'm still syncing the branches to pick the changes, let's see what happens by the night.
[Samsung Galaxy Nexus] wisey18:
Loving your work Francisco!
[Samsung Galaxy Nexus] lcheng1:
Oh so these are all 512?
[Samsung Galaxy Nexus] sago62:
:D ... mine was a little provocation ... I know you're at work ..... you're a magician!:D
[Samsung Galaxy Nexus] inffy:
Hmm seems i just got a SOD with nightly 112
[Samsung Galaxy Nexus] franciscofranco:
Odd, I haven't got SoD reports on r112.
[Samsung Galaxy Nexus] jkoljo:
The parallel IO performance is worse in #112 than M2. If I am (for example) downloading a torrent, browsing XDA and listening to music, the music stutters every once in a while. I have tried ondemand and interactive governors, but I think that the problem is in IO governor, caused by buffer underrun.. Not enough I/O speed for music app? I did not have this issue with M2. Liquid 1.1 ROM, stock clocks.
[Samsung Galaxy Nexus] franciscofranco:
Install No Frills app change to deadline and try to reproduce that issue please.
[Samsung Galaxy Nexus] jhericurls:
Same here, didn't see it happen but noticed my on-time was only a few minutes when it should of been hours.

Also had a reboot when on a call yesterday.

Using #112 with aopk b29
[Samsung Galaxy Nexus] nklenchik:
Hey Franco,

Any way we get a CPU state page on the app like with "CPU Spy"? I feel like that's the only thing your app is missing.
[Samsung Galaxy Nexus] rafi300:
I got an SoD on 112 , aokp b29 just now while restoring my apps from play store. Majority are getting SoD's. There's gotta be something wrong.

Sent from my gNexus using a Swyping thumb!
[Samsung Galaxy Nexus] raubkatze:
Completely agree! It's cool idea.
[Samsung Galaxy Nexus] nodstuff:
I think what you meant to say was minority, not majority.

There are very few SoD reports.

Try raising minimum clock speed to 729 and see if you get SoD again.

I'm running the exact same set up as you and I have never had one.
[Samsung Galaxy Nexus] Puzzlegirl:
I haven't had one on 112 though I did on 111. Everything is smooth and fast with stunning battery life.
[Samsung Galaxy Nexus] franciscofranco:
Yeah, thats doable :)
[Samsung Galaxy Nexus] rafi300:
I found out the reason for SoD. It was hotplug governor . I was on 729 . Changed to on demand so lets see now ...
[Samsung Galaxy Nexus] raubkatze:
I'm using hotplug governor since kernel flashed. On 729-1228. No SoDs till now.
[Samsung Galaxy Nexus] bradm23:
How come a lot of people are using hot plug gov lately?
[Samsung Galaxy Nexus] kashix:
Squeeze the most out of battery
[Samsung Galaxy Nexus] Treatcon:
Just an idea for an addon to your app Franco... some sort of CPU temp widget or status bar notifications. I haven't found an app on the play store yet that does CPU on our phones. Most only do battery temp.
[Samsung Galaxy Nexus] darrendm:
Just posting to say r112 is amazing. Worthy to be a milestone for sure. Cheers for all the hard work once again.
[Samsung Galaxy Nexus] bradm23:
How? We have hot plug on all of our governors using the app? Is there another advantage I'm missing?
[Samsung Galaxy Nexus] Puzzlegirl:
+1 for this. I would love a frequency widget too if it were possible.
[Samsung Galaxy Nexus] baggy247:
The hotplug gov is dynamic hotplug, so whereas hotplug mod only turns off one core when the screen is off, the gov can turn it off when CPU usage is below a certain point and its not needed.
[Samsung Galaxy Nexus] momomok:
If you're on M2, the hotplug mod in updater app is effective

but NOT for the nightlies, as hotplug mod has been removed in r111 and r112

instead a specific governor called "hotplug" is created, and it is the only governor that has hotplug mod baked in

so most of the nightlies users have to rely on this governor...
[Samsung Galaxy Nexus] franciscofranco:
Widgets are planned, just haven't had much time for that, but its planned for sure.
[Samsung Galaxy Nexus] franciscofranco:
Thats true. Hotplug mod will be revisited later, I have to work it out differently because I can't have it conflicting with hotplug governor. All in its due time.
[Samsung Galaxy Nexus] :
as reported before, i had random reboots with "interactive" governor, everything is fine on "On demand" governor. probably same cause as SoD? ;)
[Samsung Galaxy Nexus] rabhw:
Is there anywhere to re-download r111? r112 is giving me the mediascanner wakelock like crazy. I haven't changed ROM builds in over 2 weeks, so I don't think it's the AOKP bug that was mentioned earlier...unless that bug was present in AOKP M4 and was triggered by something that changed in the kernel...but I had no wakelocks from r96 - r97 - r98, r107, r110, r111, and I see others are having the same wakelock on 112 no?

Edit: I'm an idiot, thanks Diger :) Been a while since I looked at the first post since I've been using the app for everything. Oops.
[Samsung Galaxy Nexus] Diger36:
See the first post mate!
[Samsung Galaxy Nexus] AdrienC:
Franco, any way we can help out on widget development?

I'd interest in helping out to do something to quickly turn on different color modes as we have on CM Render FX.
[Samsung Galaxy Nexus] robto:
Mmm.... OsMonitor? CPU activity om status bar.
[Samsung Galaxy Nexus] franciscofranco:
Well thats a bit of a grey area. Sure anyone can send me code but it would be extremely unethical to add third party code in a paid app.
[Samsung Galaxy Nexus] teiglin:
Wouldn't it be easier (or at least better) to factor the dynamic hotplug code out of the governor so it is always available? I haven't looked at your hotplug governor code at all, but I know this was possible on Exynos platforms. Then people can use whatever governor they want and select whether they want dynamic hotplugging or not.

I also wanted to ask about the gpu clock--I certainly appreciate you giving the two builds, but wouldn't this also be something more easily solved by dynamic configuration? Then you wouldn't have to compile two kernels per release, nor change it for milestones, and people who want to overclock their gpu could do so without having to come here whining about how they can't figure out what their gpu clock is.
[Samsung Galaxy Nexus] cyanoviper:
so i switched from 384 min to 7.. min and apparently that solved the issues i had with the wifi bars turning grey. i also flashed the new radio and bootloader from the factory image and they seem to work fine.

Awesome work franco! thank you!
[Samsung Galaxy Nexus] rubino90:
Franco r112 have gpu ov?
[Samsung Galaxy Nexus] Serious_Beans:
All the nightlies will have gpu oc
[Samsung Galaxy Nexus] rafael-as:
384 or 512. Choose on ftp
[Samsung Galaxy Nexus] rubino90:
Precedent version have the problem TO glitch display please franco used app for OC gpu because with this most users choose the setup ;-) for example with r89 i stay very good because the kernel based d 307 gpu but with the app id possible oc thanks in advance
[Samsung Galaxy Nexus] Diger36:
Erm... this can't be possible?

Today I flashed AOKP b29, Franco r112, Radio XXKL2 and the new 4.0.4. Bootloader. Did a clean install and even locked and unlocked the bootloader to get it as clean as possible.

This is the result so far: See screenshots. I think it's absolutely incredible. Mind you: no black theme here... Auto brighntness, governor Ondemand with 729-1228 No undervolt and any of this stuff... This might be a winning combo.
[Samsung Galaxy Nexus] jeetS:
I'm using the foxhound rom with the kernel it comes with. Should I try Franco? and which one lol theres so many its confusing
[Samsung Galaxy Nexus] kashix:
Extended battery pack? Is it relevant to lock and unlock bootloader to be as clean as possible? Does it contributes to the performance of the new rom + kernel combo? A working theory but will need more people to support that I guess :(
[Samsung Galaxy Nexus] kashix:
Just try them and see which one do you like?
[Samsung Galaxy Nexus] winner00:
Looks like the 4.0.4 kernel sources were pushed! Time to see what new awesome stuff you will do to it.
[Samsung Galaxy Nexus] marvi0:
Hello new user here, were can we get the voltage custom control app, by Ezekeel, searched on market, couldn't find it please.?
[Samsung Galaxy Nexus] nklenchik:
4.0.4 Liquid v1.25

I was experiencing a wakelock when I turned off my screen off with Switchpro widget. Went to M2 and it's gone :D
[Samsung Galaxy Nexus] franciscofranco:
Strange...can you post dmesg log of that wakelock?

By the way I'm talking now live about Android:

https://plus.google.com/u/0/107538503004482952974/posts/1dERNGTQHhn
[Samsung Galaxy Nexus] nikulogical:
Nice. Do you know if theres any way I can flash stock 4.0.4 kernel?
[Samsung Galaxy Nexus] franciscofranco:
Oh really new sources? Let's see whats up.
[Samsung Galaxy Nexus] nklenchik:
To be honest I have no idea how to retrieve logs, but if it helps I THINK it said wakelock 243 in betterbatterystats
[Samsung Galaxy Nexus] ArmanUV:
that's what I call multitasking.
[Samsung Galaxy Nexus] franciscofranco:
Yeah, my brain kernel is running on steriods xD

New Tuna kernel source is really online. I'll be wired in the next hour to get all the changes up for a new nightly.
[Samsung Galaxy Nexus] KLUVJ:
franco. from the looks of stock kernel on 4.0.4 ota, once u inbed the new kernel with 4.0.4, our screen on time should catch up to the 5.5 hours of the note！

here are pics of my one day test on stock unrooted 4.0.4
[Samsung Galaxy Nexus] nklenchik:
Sugar and coffee my dude
[Samsung Galaxy Nexus] vomer:
Question: When a new "official kernel" is released, do you look for what they changed to improve it and then add it to your own kernel?

Just trying to get how the process works :D

Also, you still on BAMF? I am still on 4.0.3 and thinking of BAMF vs AOKP
[Samsung Galaxy Nexus] franciscofranco:
I just merged all their patches since 4.0.3 kernel changes, it's now compiling. I'm on some 4.0.4 aosp build.
[Samsung Galaxy Nexus] bendirkss:
When listening to music in my car off my phone and I get a notification, my music lags and sounds like ****. Anyone know a quick fix? And a way to actually turn the notification sounds off, cause turning to silent doesn't stop the sounds.
[Samsung Galaxy Nexus] franciscofranco:
r116:

* Merged 4.0.4 kernel sources - for the best usage I recommend in using 4.0.4.
[Samsung Galaxy Nexus] vomer:
Thanks!

Gonna find a 4.0.4 rom first :p
[Samsung Galaxy Nexus] BryanChung:
Thank you! Updating the kernal now :P
[Samsung Galaxy Nexus] nklenchik:
Did we jump ship "4" from 112 to 116? hahah
[Samsung Galaxy Nexus] vomer:
I think he goes by days? 112 was released a few days ago...

116 might just me M3 :D
[Samsung Galaxy Nexus] nklenchik:
No one else is getting a wakelock on 116?

build.board: tuna

build.bootloader: PRIMELA03

build.brand: google

build.cpu_abi: armeabi-v7a

build.cpu_abi2: armeabi

build.device: toro

build.display: Liquid ICS v1.25

build.fingerprint: google/mysid/toro:4.0.4/IMM30B/257829:user/release-keys

build.hardware: tuna

build.host: ubuntu

build.id: IMM76D

build.manufacturer: Samsung

build.model: Galaxy Nexus

build.product: mysid

build.radio: unknown

build.serial: 0146B5BA1401A010

build.tags: release-keys

build.time: 1333128287000

build.type: user

build.user: liquid

version.codename: AOSP

version.incremental: 257829

version.release: 4.0.4

version.sdk_int: 15
[Samsung Galaxy Nexus] nodstuff:
What's the problem?

There are supposed to be some wakelocks, otherwise the phone would be as good as off when the screen was off.

It holds a wakelock to search for signal, to ping a tower, syncing, gtalk etc.

Its only a problem when it is abnormally long, for example when you have screen off for an hour and no deep sleep. That is a problem wakelock.

Also don't worry about kernel wakelocks, you should be looking under partial wakelocks.

betterbatterystats in the wrong hands is as useful as a fridge in an igloo.

Also give a new kernel more than a few minutes before you complain about wakelocks.