yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] MONKY_1:
Here you guys go read up!

http://forums.androidcentral.com/ve...g-roms-hacks/156679-sqlite-franco-kernel.html

Galaxy (:
[Samsung Galaxy Nexus] andrew53517:
I just enabled it.. I don't know, what the heck haha
[Samsung Galaxy Nexus] axne1:
Well Franco I'm off m2 &running the New! :)
[Samsung Galaxy Nexus] mike216:
121 is great! Its noticeable faster and I thought 116 was fast and battery life is also superb. I wasn't sure if I could run it on my favorite codename rom that's still 4.0.3 because of the stock 4.0.4 ram disc.
[Samsung Galaxy Nexus] gnexdude:
Is the down load link down? I keep getting download unsuccessful! Thanks :)
[Samsung Galaxy Nexus] laureanop:
I got tired of download unsuccessful messages with the stock browser so I switched to dolphin for downloads

"the relentless pursuit of the perfect rom"
[Samsung Galaxy Nexus] gnexdude:
PPreciate that bro!
[Samsung Galaxy Nexus] laureanop:
121 384mhz on liquid running solid 384-1366, no hot plug on demand , calibrated voltages

"the relentless pursuit of the perfect rom"
[Samsung Galaxy Nexus] Clarkkent434:
Any shell commands to use in tasker for the kernel to change color on the screen for different time of the day like F.lux? I have tried echo "-10 0 -2" /sys/class/misc/colorcontrol/v1_offsets but its not working.

Sent from my Droid Nexus.
[Samsung Galaxy Nexus] robstunner:
Still have wake lock on 121 and aokp b29
[Samsung Galaxy Nexus] HIcycles:
The wakelock time is 4 minutes. Is this a problem if your phone was unplugged for over an hour?

I'm sorry if it's a dumb question...
[Samsung Galaxy Nexus] robstunner:
Beats me. Its #3 from the top
[Samsung Galaxy Nexus] djd338:
I'm also on B29 and #121. And, I also have the wakelock issue. Looking at your screen shot, it looks just like mine. Except I have about double the run time but the numbers are proportional. I have:

"Keep Awake: 8m 42s

# of wake locks: 137
[Samsung Galaxy Nexus] franciscofranco:
That seems more of a rom problem than kernel, I already fixed what it needed to be fixed for that wakelock.
[Samsung Galaxy Nexus] ozymandiaz:
Franco, I'm ONLY getting about 3.5 hours of screen on time, 700 min/1344 max, 100 percent brightness, on the stock battery with live wallpaper (spring zen HD) running.

You rock, man!:D
[Samsung Galaxy Nexus] seegs11:
I'm still on b28 with v112. Went up to 3.5 hrs of screen time on 24 hrs. With 1.5 hrs i was at 44 hrs of battery life!

Franco totally rocks.

Sent from my Gnex
[Samsung Galaxy Nexus] alphanu22:
dontknowifsrs
[Samsung Galaxy Nexus] mike216:
Franco has been rocking his ass off for awhile now! I pleasantly bumped in to his work on my nexus S and its been a wonderful ride ever since! I'm sure glad he's an Android enthusiast and not an IPhone guy :D almost at 200 thanks so watch out Franco I'm catching up to you :rolleyes:

Donated also thanks for everything!
[Samsung Galaxy Nexus] azsl1326:
Just switched to r121 from r89. Believe it or not r89 gave me the best battery life, performance, etc - even better than M2. Anyway, has anyone tried running Quadrant? I get severe stuttering when doing the graphics test.
[Samsung Galaxy Nexus] laureanop:
Not really. I got 3400 on the first run. Liquid 1.25

"the relentless pursuit of the perfect rom"
[Samsung Galaxy Nexus] mike216:
I have the feeling that M3 is near ;)
[Samsung Galaxy Nexus] m3ta:
Yeah. I'm always near.
[Samsung Galaxy Nexus] franciscofranco:
Now that seriously made me laugh ;)
[Samsung Galaxy Nexus] axne1:
R121 quadrant 3789!!!! :D standard Franco settings ondemand .
[Samsung Galaxy Nexus] tcchuin:
"However, if you put any trust in Quadrant scores you could use them to prove that dancing naked for 5 minutes in your garden affects device performance. By Chainfire"
[Samsung Galaxy Nexus] azsl1326:
Had to bail on r121. Random artifacts showing up on reboot and during use. Back to M2 or r89
[Samsung Galaxy Nexus] Gahh Its Lee:
You installed the 512 gpu. Try the 384 version nothing wrong with the kernel just people not reading.
[Samsung Galaxy Nexus] zeke1988:
does the new nightly only for 4.0.4?
[Samsung Galaxy Nexus] mike216:
I'm running it now on codename which is 4.0.3 and have for a couple days without 1 single problem ;)

Good morning then to you M3 and hope we will see you coming out very soon
[Samsung Galaxy Nexus] azsl1326:
Downloaded from my phone and didn't see the 384 option. Thanks!
[Samsung Galaxy Nexus] ArmanUV:
No it should work on 4.0.3 too.
[Samsung Galaxy Nexus] franciscofranco:
Its writen 4.0.3 too in the title, how is that not enough straight foward?
[Samsung Galaxy Nexus] mike216:
and this is why I said what I said. Only had to read one page back,come on guys do just a little research before asking that question
[Samsung Galaxy Nexus] JayDaKissEP:
http://minooch.com/franciscofranco/Galaxy Nexus/nightlies/gpu_384mhz/franco.Kernel-r121.zip
[Samsung Galaxy Nexus] axne1:
Wow Franco this is awesome +100 :D
[Samsung Galaxy Nexus] mikespe:
What do you guys consider good battery life with this kernel (v121 384 ondemand) in regards to ON BATTERY (not screen time but that was approx 1hr20min) with the VZN extended battery. I know screen time is a big factor though. I just looking for when you take the phone off charge & have to charge it again. With moderate use (20min streaming music, 30min mp3 music, normal browsing/email/Facebook use....

I took mine off charge at 6am & by 3pm it was at 20%...so that's 9 hours. I gave it a quick charge while I drove to a meeting I had to go to (about 15min drive).....is this considered good for this kernel?
[Samsung Galaxy Nexus] Gahh Its Lee:
Personally I'd say that's not terrible. But some others get ridiculous battery life that I've never been able to achieve
[Samsung Galaxy Nexus] mike216:
Your only going to get 4-5 hours of screen on time if your on 3g or wifi. Mostly wifi. If I'm on 4g all day I'll be lucky to get 2 hours of screen on time. If your gaming and on 4g you'll get even less
[Samsung Galaxy Nexus] spinkick:
Franco, you had a wiki talking about how overclocking the video card on these phones has marginal at best improvement and its basically a waste in power. Why do you run an overclock on your kernal? If we dont play games etc, will we see any kind of smoothness difference anyway? How much power difference do you think we are talking between the video overclock and not at all?

Thanks!!
[Samsung Galaxy Nexus] mikespe:
There's a guy on the Liquid v1.25 thread that is saying he's going on TWO DAYS and still has 32% to go!! I asked him if he ever turned his screen on because NO smartphone gets that kind of battery life!
[Samsung Galaxy Nexus] ozymandiaz:
On wifi yesterday, I got approximately 3.5 hours of screen on time with heavy use running 729 min 1344 max, hotplug off, performance governor, live wallpaper on, 100 percent brightness, etc etc.

Today, using only 4g, I got approximately 3.5 hours of screen on time with heavy use running 729 min, 1036 max, hotplug on, plain black wallpaper, letting the rom control my brightness. Also, this was also on the performance governor, I forgot to change it back to conservative. =(

These were both on the stock battery. So, I can look forward to 7 hours of screen on under heavy use when I get my 3800 mah battery from seido. Score! I score this daily (121) and rom (liquid smooth v1.25) a success at battery life! Now I can go back to my more normal light usage patterns, and worry about the 25-30 hours of standby time with only about an hour or so of screen on time that is more common to my pattern of usage. (or 50-60 hours with 2 hours of screen on time when I get the bigger battery!)
[Samsung Galaxy Nexus] spinkick:
Do you run the overclocked video card? Also, why do you run min 729 mhz? Doesnt that waste energy? I would think the screen and LTE use the most energy. Does underclocking the device really save all that much?
[Samsung Galaxy Nexus] ozymandiaz:
As to the 729 min, Franco and others have theorized that if your phone can more quickly finish the tasks that wake it from deep sleep, it can go back to sleep faster, saving battery. This is actually more important in my normal usage, and probably mattered not at all in these tests, as I didn't let the phone enter deep sleep even for a second.

And I forgot to mention that I am using the stock video card, because I wasn't seeing any real performance gains from the 512. I imagine that I would notice a slight but definite drop in battery life if the tests had been done using the overclocked video.

As far as how much underclocking saved, well, 4g is a huge battery drain, and I enabled the 4g instead of wifi on my underclocked test, and the results were the same, so I would estimate that the 4g battery drain was approximately the same as the battery savings I got from underclocking and turning off the live wallpaper. ymmv, of course.
[Samsung Galaxy Nexus] spinkick:
Thanks! Have you seen a difference from 729 vs 384 deep sleep wise and also performance wise?

Thanks for the input, I appreciate the scientific results.
[Samsung Galaxy Nexus] ozymandiaz:
I will test that in a couple days. TBH, I have been amazed at what I've gotten so far out of this build. 4g and the huge screen combine to be the death of a battery under normal circumstances, so even 3.5 hours of active use with the screen on is amazing to me. I will see how much total time I can get with lighter usage and letting the phone hit deep sleep for both 729 min and 384 min over the next week and let you know. Of course, since I'm a flash a holic, if Franco drops a new nightly, I will have to start over. lol
[Samsung Galaxy Nexus] al2x:
Anyone have any tips to undervolting, what settings to set it to, and how it'll help? I've been flashing different kernels since my Incredible days, but I've never tampered with undervolting. Thanks
[Samsung Galaxy Nexus] spinkick:
Honestly you don't really getting huge savings undervolting. I think the savings is in the radio and the screen coupled with low instances of wakelock.

Unless you are limiting the CPU to 1ghz or something like that. Even then... I doubt its worth the stability trade offs
[Samsung Galaxy Nexus] ozymandiaz:
Yeah, haven't messed with undervolting at all. I'm sure some people swear by it, but I'm having enough success without it that I'm not tempted to try it yet.
[Samsung Galaxy Nexus] zeke1988:
i always UV, but tomorrow, i will test a full day of no UV and see how it perform.
[Samsung Galaxy Nexus] mike216:
let us know how it goes :)
[Samsung Galaxy Nexus] mike216:
Tried another great kernel for comparison and yours is faster and is much better with screen on actually use battery drain. I find that conservative makes the UI so fast. Don't know why I figured ondemand or interactive would be quicker
[Samsung Galaxy Nexus] JayDaKissEP:
If someone manually turns off CPU1 using Franco's app, does it remain off after a reboot or do both come back online?
[Samsung Galaxy Nexus] axne1:
Trying performance gov today. I've been hearing great things!
[Samsung Galaxy Nexus] spinkick:
Let us know how it goes
[Samsung Galaxy Nexus] axne1:
Oh I will. A real power user right here! :cool:
[Samsung Galaxy Nexus] jamor414:
I was using r98 and really loving it.

I just wiped cache, dalvik and flashed Milestone2 and now I can't get past the Google splash screen.

I have to battery pull and then force Boot Recovery.

Tried reflashing r98 over Milestone2 and rebooting and I still can't get past the Google splash screen. Used francos links. How do I fix my phone without wiping data?
[Samsung Galaxy Nexus] TEK112:
Wipe cache and Dalvik, flash M2 and wipe cache and dalvik again, reboot and make a sandwich.
[Samsung Galaxy Nexus] jamor414:
OK!

edit:

It's been quite a while now sitting at Google splash screen still... 15 minutes easily and getting pretty hot.

I'm on [ROM]IMM30B 4.0.4 Stock,rooted,deodexed,zipaligned,busybox,insecure boot + mods zips
[Samsung Galaxy Nexus] TEK112:
Hopefully it wasn't a bad download. Repeat the same steps, but flash r98. Do you have other kernels on the device you can flash?
[Samsung Galaxy Nexus] jamor414:
No just r98. But r98 won't get past the Google splash screen either even though it worked perfectly when I first got it in March and it's the same file on my root sd.
[Samsung Galaxy Nexus] TEK112:
This time wipe cache and dalvik before and after flashing r98. See how that goes.
[Samsung Galaxy Nexus] jamor414:
Tried.. It's just sitting on Google splash screen and getting hot again.
[Samsung Galaxy Nexus] TEK112:
OK. Plan B.

Make a backup.

Wipe Data/cache and reboot

Download a few kernels

Reboot and restore backup

Flash different kernels
[Samsung Galaxy Nexus] jamor414:
Working on it now..

---------- Post added at 11:52 AM ---------- Previous post was at 11:36 AM ----------

Wiped data/cache, rebooted and still can't get passed google splash screen. I really must have screwed something up bad.

---------- Post added at 12:01 PM ---------- Previous post was at 11:52 AM ----------

I ended up just flashing a 3/16 Nandroid and everything is working again.
[Samsung Galaxy Nexus] TEK112:
Sorry about that. It looks like definitely a kernel issue. The data wipe rules out a ROM issue.

Just use the original package that you used to root your phone and copy a few kernels in there. Then reboot into the bootloader and use ADB to push the files from the folder with ADB in it to your phone with:

adb push kernelname /sdcard/

The file should appear on your phone and you can then restore your backup and flash the kernel you just pushed.

---------- Post added at 01:04 PM ---------- Previous post was at 01:03 PM ----------

Sweet. Now go download a few kernels and reboot into recovery, flash the backup you just made that won't boot then flash one of the kernels you downloaded.
[Samsung Galaxy Nexus] franciscofranco:
Something got corrupted =(
[Samsung Galaxy Nexus] TEK112:
Agreed. That's why i always keep a slew of ROMs and kernels on my phone in case this crap happens. It sucks when it does.
[Samsung Galaxy Nexus] laureanop:
After a couple of days of using 121 I feel that 116 is better. Yesterday I had two inexplicable sod s within two hours of each other so I went back to 116.

"the relentless pursuit of the perfect rom"
[Samsung Galaxy Nexus] sway40:
I thought I was the only one, I have had nothing but sods back to back. I had to restore to older rom and kernel. Tried on aokp and cm9 with same result, both fresh installs.

~Sent from my GNexus running Aokp~
[Samsung Galaxy Nexus] brycetrem:
I haven't had any sod, but I also turned off ho plug mod since there have been issues.
[Samsung Galaxy Nexus] laureanop:
I never use hot plug and I'm not undervolt ed

"the relentless pursuit of the perfect rom"
[Samsung Galaxy Nexus] brycetrem:
I'm also using 512 vr of b121. So far not a single sod since 116. Odd.
[Samsung Galaxy Nexus] spinkick:
On latest. No sod. I'm using the regular video speed
[Samsung Galaxy Nexus] Theteflondon:
Will this kernel work regarless of lte or gsm version?
[Samsung Galaxy Nexus] TEK112:
Yes.
[Samsung Galaxy Nexus] foxdog66:
Seeing how the sod bug is directly related to the hot plug governor, why are people still using it?
[Samsung Galaxy Nexus] sway40:
I still got sods and haven't used the hotplug governor ever.

~Sent from my GNexus running Aokp~
[Samsung Galaxy Nexus] axne1:
I didn't get the battery life I expected with r121. so I went back to milestone 2.

:confused:
[Samsung Galaxy Nexus] mikespe:
What kind of battery life are you getting now? I'm also not happy with the battery life on 121
[Samsung Galaxy Nexus] sway40:
Battery life has been meh on anything past m2 for me.

~Sent from my GNexus running Aokp~
[Samsung Galaxy Nexus] :
+1 I would love to get call recording for my Nexus! I miss it from the SGS.
[Samsung Galaxy Nexus] kingoanklebreakn:
I thought there was a different one for GSM. There's a different thread for it at least.
[Samsung Galaxy Nexus] mike216:
Same kernel. Maybe its better for Franco since he's got s GSM version
[Samsung Galaxy Nexus] mike216:
I've been running 121 it seems for awhile now and haven't had any reboots. What rom are you guys getting reboots on? I'm on the current codename
[Samsung Galaxy Nexus] sway40:
Aokp 29 which has been a nightmare for me, but had same results on cm9 with 121. I tried m2 on aokp 29 which still sucked but that was the rom not kernel. I've tried 121 on aokp m4 and got random reboots and sods so I know it's the kernel there. Basically 121 and aokp 29 have not been nice to me since there release.
[Samsung Galaxy Nexus] mike216:
its probably AOKP then because like I said I haven't been able to produce reboots. I've been running the min and Max I think 344-1344 or something like that. Or your phone doesn't like that particular combo?
[Samsung Galaxy Nexus] sway40:
Eh they both give me probs separately... together it's armageddon, idk what it could be but im on stable rom and kernel now.
[Samsung Galaxy Nexus] segfaultex:
I seem to have all sorts of bluetooth issues with every beta past milestone 2. Half the time mid way through a call the other person just stops being able to hear anything I say. Other times bluetooth in general just gets stuck in limbo where I cant turn it on or off just sits at "Turning on". Its to the point where the annoyance outweighs the positives. Outside of that it runs fine but still..
[Samsung Galaxy Nexus] axne1:
Back to around 14 hours with a 4 and a half hours on screen time with m2
[Samsung Galaxy Nexus] itch808:
121 is treating me well. ZERO SODs. Best battery life of the many kernals (Better than M2). Smooth.

Running stock kernal out of the box, no UV/hotplug/etc.
[Samsung Galaxy Nexus] mike216:
M2 is good on battery but if I use light flow it will chew the battery up. Oddly 121 doesn't go through battery using light flow. Went back to 121
[Samsung Galaxy Nexus] mark manning:
Just out of curiosity how do you know? Also are you sure its light flow?

The reason I ask I am trying out M2 this week and it seems pretty good on battery but I do have light flow installed. I love that app so I just want to make sure you are sure before I uninstall it.

Sent Telepathically
[Samsung Galaxy Nexus] superkeest:
You dont "turn it on" when your screen is off it should go into deep sleep unless:

there is something keeping it awake.

you can use betterbatterystats to see what is holding wakelocks

but it should go to deepsleep seconds after the screen is off. It will not deep sleep if the usb is plugged in however. Also builds of bugless between 1/5 and 1/12 had a bug in which deep sleep was never entered.
[Samsung Galaxy Nexus] chuckenfoot:
I'm running aokp...yes I did open and close the camera. I get good battery life, just CPU spy shows deep sleep unavailable...not sure what gives
[Samsung Galaxy Nexus] Takeoisblack:
NFC tags not working

Anyone running Bugless and this kernel having trouble reading RFID tags?
[Samsung Galaxy Nexus] TEK112:
What is your android OS % at?

It may be a newly found facebook bug.

---------- Post added at 11:41 AM ---------- Previous post was at 11:39 AM ----------

I haven't tried that ROM. Are you sure it is supposed to be working? A lot of ROMs have issues with NFC tags. Did it work before franco's kernel?
[Samsung Galaxy Nexus] chuckenfoot:
Android is is currently at 26%, second to screen on
[Samsung Galaxy Nexus] TEK112:
If you see it get unwieldy 50% or so, try uninstalling facebook and see if your battery life improves.
[Samsung Galaxy Nexus] Mikes30000:
If you're running anything beyond aokp m2 then there is a deep sleep bug that is currently being worked on. Toggling bluetooth on and off is a known temp fix to get deep sleep worKing
[Samsung Galaxy Nexus] chuckenfoot:
My issue isn't battery life, its that CPU spy says deep sleep is unavailable.
[Samsung Galaxy Nexus] Takeoisblack:
I don't think I tried it before flashing the kernel.
[Samsung Galaxy Nexus] nerdslogic:
Hey Franco....I have a question....I seem to get similar battery life with your kernel as I do with Faux....but I get much higher scores when doing any benchmarks? What is this FIOPS stuff and is it all smoke and mirrors?

I know you and Faux are completely different but you are in the same field....just thought you could shed some light on that topic for me.
[Samsung Galaxy Nexus] TEK112:
They are both related. Facebook sync may be causing excessive wake states not allowing the phone to sleep. Poor battery performance is a bi-product of this.
[Samsung Galaxy Nexus] SomeGuyDude:
Try toggling BlueTooth on and off. Worked for me on Codename 1.1.0
[Samsung Galaxy Nexus] chuckenfoot:
I deleted Facebook, rebooted, started and stopped the camera app, toggled blue tooth on then off, let sit for 30 minutes then checked CPU spy....still no deep sleep....hmmm
[Samsung Galaxy Nexus] TEK112:
Did you pat your head and rub your tummy...lol :D

There are a lot of steps involved. How long did you let your phone chill with the screen off before you looked in cpuspy?
[Samsung Galaxy Nexus] chuckenfoot:
30 minutes
[Samsung Galaxy Nexus] TEK112:
I guess the real answer is stroll the AOKP boards and see if their users are having issues or try another kernel and see if you can get it to sleep.
[Samsung Galaxy Nexus] chuckenfoot:
Which kernel are you using? I'll start there lol
[Samsung Galaxy Nexus] TEK112:
I am using codenameandroid stock and he uses a kernel compiled from imoseyon's leanKernel source 3.0.16.

Honestly, I would just flash codenameandroid and see if you like it. If not, nandroid back to aokp.
[Samsung Galaxy Nexus] mykenyc:
I would like this also please, currently interactive x gives me the best battery life on imo kernel.
[Samsung Galaxy Nexus] nerdslogic:
So is it bluetooth to be toggled or camera?
[Samsung Galaxy Nexus] alphanu22:
Light Flow hasnt been or ever been a problem for me.

Been running M2 for the longest time-
[Samsung Galaxy Nexus] mike216:
I said light flow was an issue because I was on 121 for a week or so then last night I threw M2 on and battery life was insane. When I woke up I had massive drain and light flow was one of the main drains looking through my battery monitor app. Under these same conditions on 121 I don't notice any drain on idle with light flow in use. But I will say that I got unbelievable screen on drain on M2 and never seen anything like it
[Samsung Galaxy Nexus] mike216:
Don't uninstall it mark! It could be my setup and may not affect you so give it another shot. Hell I'm going to reflash M2 now after reading your guys comments. There are two things I'm not giving up on and that's LF and Franco's kernels. He's such a wiz with these kernels! I love the conservative governor on both M2 and 121 its so damn fast I can see skid marks across my screen :D

I would love to post a screen shot of M2 screen on drain showing 1 hour 5 minutes at 80% battery but XDA'S app won't let me upload pics anymore?
[Samsung Galaxy Nexus] alphanu22:
lol, Light Flow only drains battery if the LED is blinking, means its doing its Job. Untill you clear/look at the notification that Light Flow Stops working-

:rolleyes:
[Samsung Galaxy Nexus] mike216:
I know bud but at the rate of drain was very high opposed to 121 along with Android OS but I know that's probably normal. One of the fixes in 4.0.4 was lower Android OS
[Samsung Galaxy Nexus] TEK112:
I thought it was a reporting bug with the Android OS being fixed in 4.0.4. I didn't think it actually used less battery.
[Samsung Galaxy Nexus] mike216:
That's what I said Android OS reporting is definitely lower on 4.0.4 kernel's
[Samsung Galaxy Nexus] axne1:
Aokp b30 & Franco M2 has been awesome!!!!! Cdma