yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] akellar:
Much more likely it's something in your setup or there would be a lot more people complaining about battery drain. I myself am not having any abnormal drain.
[Samsung Galaxy Nexus] Stadsport:
Lucky I guess. I went ahead and bought Franco's app to play with it, and found that my SetCPU voltages weren't actually being applied. I set my voltages with Franco's app and it worked fine, but if I set 350mhz any lower than 775mV, I get a sleep of death nearly every time.
[Samsung Galaxy Nexus] Znomon:
Read my edit...
[Samsung Galaxy Nexus] Stockmoose16:
I literally haven't done anything but install the new kernel and restarted the phone. Then it sat in the same spot it's been all day for several hours. That's a very controlled environment. There's no reason it should suddenly have started draining, if not for the kernal.
[Samsung Galaxy Nexus] hyatari:
This kernel owns RL Benchmark. I haven't tried every kernel but none have come close to this with this bench.
[Samsung Galaxy Nexus] dincfool:
So build 13 is having problems? I have the app and want to flash but not if theirs issues.. im running kang M2
[Samsung Galaxy Nexus] Stadsport:
Okay, that's kind of what I expected from the beginning. What values are you running now?
[Samsung Galaxy Nexus] TMFGO45:
For anyone interested, my setup:

Mhz1200, 920, 700, 350 \ Mv 1125, 1000, 900, 800

Been running this for more than a few hours now. No lag, no freezes, no reboots, no issues I've discovered so far.

Everything I run is below. And everything runs great.

Swyped from my Galaxy Nexus (Codename Android 1.1.4, franco.Kernel #13, Hotplug On, Inverted Gapps, Nova Launcher #12, 1200/350 UV'ed) in Tapatalk Pro!
[Samsung Galaxy Nexus] dotson817:
Im on code name also but haven't seen an inverted gapps, sounds sick
[Samsung Galaxy Nexus] Natolx:
Bought the app, thanks for the great kernel Franco!

One thing I can't seem to figure out from the changelogs, is the GPU currently overclocked in this kernel?
[Samsung Galaxy Nexus] TMFGO45:
Rootzwiki. Trev had been inverting them. Don't know if I can post links? If I can, someone tell me, and I will put the link here...otherwise PM me...

Swyped from my Galaxy Nexus (Codename Android 1.1.4, franco.Kernel #13, Hotplug On, Inverted Gapps, Fast Glow, Nova Launcher #12, 1200/350 UV'ed) in Tapatalk Pro!
[Samsung Galaxy Nexus] Rules.r:
I've tried to install the kernel on Revolution HD 2.1.3 several times (different downloads even) and it locks me at the Google unlock screen for hours.

Anyone else had that experience?
[Samsung Galaxy Nexus] redsox 98:
If I'm not mistaking isn't that from 4.0.2. This kernel is for 4.0.3.
[Samsung Galaxy Nexus] Elganja:
AR 2.1.3 is still a 4.0.2 ROM. This kernel is for 4.0.3 ROM's only

Please see the OP
[Samsung Galaxy Nexus] gambit07:
Well let us know
[Samsung Galaxy Nexus] Timdor:
werd, please do
[Samsung Galaxy Nexus] Znomon:
This is what I'm running now, set it last night. So far it has been on for 11 hours with no reboots or anything. 10 hours has been deep sleep so after I run the battery out a bit I'll let you know how performance runs.
[Samsung Galaxy Nexus] Rules.r:
You are correct that I am a jackass and should not have missed that... Thanks Elganja.
[Samsung Galaxy Nexus] androidmichael:
The media scanner is definitely messed up with this kernel. AOPK 19 it wouldn't stop scanning. My test is PlayerPro. If it has the little spinning circle while looking at an album that means its scanning and that doesn't stop on franco's. Flashed to stock aopk kernel and the media scanner stopped after it got done like it should!

Deal breaker for me for sure because I listen to a lot of music!
[Samsung Galaxy Nexus] psohn:
I loaded v13 and I set the UV for -50 across the board but my idle battery usage went from 2%/hr to 4%/hr. Did v12 have a more aggressive UV or is it the new kernel?
[Samsung Galaxy Nexus] mike216:
I don't think V12 had any UV? But version 13 has a pretty good UV out the box
[Samsung Galaxy Nexus] ndwatkins:
If anyone's interested, my phone seems very stable at 1200-1125, 950-1000, and 700-950. I keep it at 700/1200 (I've found better battery life at the 700 min than 350) and I don't overclock - I don't really think this phone needs it!

Been really happy with 13 so far. Battery life seems better for me at least!
[Samsung Galaxy Nexus] psohn:
What UV are you seeing out of the box? When I reboot Franco's app shows the current voltages at max value.
[Samsung Galaxy Nexus] EyeOfTruth:
Unless you check the option to set on boot you have to apply the TV settings each reboot.
[Samsung Galaxy Nexus] Gwanatu:
Thank you, none of the other configs posted worked for me. I did exactly what you said and so far so good for 30 minutes, time will tell how this affects me in both performance/battery/stability.
[Samsung Galaxy Nexus] rlrbjr:
I was running Franco-12 with AOKP-19. Kernel defaults plus hotplug (700-1350 conservative). Last night I flashed Franco-13. According to CPU Spy the 350 MHz and 1200 MHz slots are not being used. I expect no 350 MHz since my minimum is 700 MHz, but on Franco-12 I always saw some time for all of the slots and Deep Sleep. What would cause the 1200 slot to not be used?

I'm also seeing funny behavior with media. The media process seems to get killed after a reboot (a toast pops up). Probably why the earlier post reported that media scanning is not working.

UPDATE: I don't think the media problem is with the kernel. I see the same behavior with faux.
[Samsung Galaxy Nexus] psohn:
I'm aware of that, that's why if I reboot I should have the default values since I never selected the set on boot option. The numbers are going back to max voltage which should mean my out of box is set to max values.
[Samsung Galaxy Nexus] mzimand:
On my phone Franco's kernel runs the best of any kernel I have tried and I set the minimum to 350mhz as soon as I install it but am rethinking do so.

I was wondering what others are setting min/max and if you are leaving the minimum at 700mhz how are your results?
[Samsung Galaxy Nexus] kichard:
I feel like this build is sucking my batt like a night walker in a red light district. Anyone else?
[Samsung Galaxy Nexus] Geezer Squid:
No. This kernel is doing an excellent job on my Gnex. I'm running AOKP 19. Kernel is set at 700-1350 Performance and I'm still happy with battery life. Keep Awake time is absolutely no longer an issue for me. YMMV
[Samsung Galaxy Nexus] stevessvt:
Had my phones first spontaneous reboot soon after using this kernel. 12 was great.
[Samsung Galaxy Nexus] SomeGuyDude:
Same. I'm impressed with this one greatly. Bench scores are outrageous, battery lasts plenty long, and games run smooth as butter.
[Samsung Galaxy Nexus] nycdiplomat:
+1 i am running 12 now and its by far the best performance and battery life ever on my Gnex. afraid to flash 13 because i am so satisfied with how smooth my phone runs
[Samsung Galaxy Nexus] doublea500:
any mirrors for nightly #12?
[Samsung Galaxy Nexus] dcoy82:
Been running Franco for a week or so now been running great. 13 came out and I flashed it iall went well. Purchased the app yesterday and set hotplug and undervolted everything by 100 under stock. Ran everything for 24 hours perfect so I figured I'd set on boot since ran great for a full day.

Soon as I clicked set on boot it froze up and now I get constant boot loops. It'll get anywhere to halfway through boot then freeze and reboot or get all the way to the lock screen then freeze and reboot. Not sure what happened :confused:

Good thing I made a backup yesterday, time to restore :D
[Samsung Galaxy Nexus] pauliewalnutted:
What app do you guys use to UV? I have Franco's app but you can't actually set the UV settings within it can you? Sorry if I'm mission something...
[Samsung Galaxy Nexus] dcoy82:
I'm using the Franco app but if you read the thread above yours you will see the current issues I'm having with it!
[Samsung Galaxy Nexus] TMFGO45:
You can if you have version 2.0 of francos app. Make sure you are updated...

Swyped from my Galaxy Nexus (Codename Android 1.1.4, franco.Kernel #13, Hotplug On, Inverted Gapps, Natemz Mod w/ Fast Glow, Nova Launcher #12, 1200/350 UV'ed) in Tapatalk Pro!
[Samsung Galaxy Nexus] zeppelinmad4:
Music

So I noticed this on nightly 12 and it has carried on to nightly 13 it seems. I will play a song, any song, in Google Music and listen to it all the way through. When it is time for the next song to play, it never does. It seems like the song just gets stuck at the last second in it. Happens every time. I noticed a couple pages back people saying there was something wrong with the media scanner or something to that extent. I'm not exactly sure if this has anything to do with that but it's a possibility. I've attached a log just in case if it comes in handy for some reason.
[Samsung Galaxy Nexus] blaine07:
Mine does that too... sure its kernel related issue though or app?
[Samsung Galaxy Nexus] zeppelinmad4:
Almost positive it's kernel as it didn't happen when I was running Matr1x 2.0.
[Samsung Galaxy Nexus] pauliewalnutted:
Yes I'm updated...but how do you actually change the UV settings. I click on the UV tab but then can't change anything. Feel out of the loop lol
[Samsung Galaxy Nexus] nycdiplomat:
tap on each frequency and you should get a pop up box to type into.
[Samsung Galaxy Nexus] pauliewalnutted:
Figured as much, although the app didn't bring up a box. So I reinstalled and that did it. Thanks fellas!
[Samsung Galaxy Nexus] drmp3z:
I do not have that problem. I been playing Google music all day. Running a clean install of [ROM][CDMA][4.0.3] CM9 Kang *Updated 1/17 2:30pm. So how could it be a Kernel problem?
[Samsung Galaxy Nexus] Znomon:
I think that is how Google music is made. If you click on one sing it will just play that one song, and if you press shuffle or something it will continue. I think this is to prevent using too much data. Or maybe I mistook a bug as a feature... haha
[Samsung Galaxy Nexus] doublea500:
how to enable hotplug?

?
[Samsung Galaxy Nexus] Flip35:
i went throught the same thing but u have to go to the main screen and hit shuffle, i believe it has to do with the way google implemented, not anything to do with the kernel
[Samsung Galaxy Nexus] PaulG1488:
Read op

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] doublea500:
dont see where it says how. i see that i can buy the app but id like to try before i buy.
[Samsung Galaxy Nexus] franciscofranco:
New kernel and app updates.
[Samsung Galaxy Nexus] sinik420:
ill copy and paste it for you

Hotplug cpu1 is implemented somewhere else:

echo 1 > /sys/module/dsscomp/parameters/hotplug_enabled

cpu1 does not shut down on screen_off: echo 0 > /sys/module/dsscomp/parameters/hotplug_enabled
[Samsung Galaxy Nexus] wayneb02:
Anybody else having problems with the app not downloading the new kernel?

I get a force close window

Edit: never mind, I think it was my 4g connection
[Samsung Galaxy Nexus] 9wire:
DL'ed just fine.
[Samsung Galaxy Nexus] doublea500:
ooh i saw that too, wasnt sure if it was the instructions.

Does that basically mean that i change it from 0 to 1?
[Samsung Galaxy Nexus] sinik420:
use terminal emulator to enable, use 0 to disable
[Samsung Galaxy Nexus] doublea500:
so copy "echo 1 > /sys/module/dsscomp/parameters/hotplug_enabled" in terminal emulator? wouldnt that do the same thing as changing it manually in root explorer?
[Samsung Galaxy Nexus] sinik420:
i dont like when it adds back up files :p
[Samsung Galaxy Nexus] rlrbjr:
Worked fine for me. New app and kernel installed. This kernel fixes the problem I had with the 1200 MHz slot not working - all the slots (including Deep Sleep) are working as expected. But Antutu is slower -- with 13 I was seeing scores around 6900-7000 with 13.1 I'm seeing 6200-6500. Now let's see how the battery does.
[Samsung Galaxy Nexus] doublea500:
yea, i saw that popup saying it made a backup but i dont actually see a backup. very odd. i even refreshed. i can care less though. its easier to delete 1 character and click 0 then it is to restore the backup. ty
[Samsung Galaxy Nexus] sinik420:
can i ask why? if its related to UV then just raise the voltage. it gets cluttered when people report bootloops and things while they are undervolting. its why some devs dont allow it.
[Samsung Galaxy Nexus] Elganja:
potential settings for other users to use...

I suppose a separate undervolting thread is a better place for this...
[Samsung Galaxy Nexus] sinik420:
no, didnt consider that, awesome =] just remember everyone when reporting issues to include whether you are UVing and if you have gone to stock before reporting
[Samsung Galaxy Nexus] mike216:
Anyone know how to get some nice bright colors. 0 0 0?

Any help would be greatly appreciated!
[Samsung Galaxy Nexus] rgoyena:
Why is there an update on the 13? I like the high quadrant scores. Lol
[Samsung Galaxy Nexus] Berzerker7:
Not sure if anyone's pointed this out, but there's a typo in the franco app, when you set the 350MHz voltage, it says "Set the desired value for 3500MHz." I wish our phones were that fast.
[Samsung Galaxy Nexus] question.com:
What he said.
[Samsung Galaxy Nexus] rgoyena:
Can somebody post what's wrong with 13?
[Samsung Galaxy Nexus] question.com:
When I tried 13, phone made a strange popping sound then went into a permanent boot loop. Had to wipe and start fresh. Very scary. 13.1 is good.
[Samsung Galaxy Nexus] rgoyena:
Yeah 13 is good. I don't really see what the problem was with 13 vs 13.1
[Samsung Galaxy Nexus] Stadsport:
Just updated to 13.1 and got a sleep of death almost immediately after... will have to keep an eye on it.
[Samsung Galaxy Nexus] kichard:
13 gave me sub par battery life during the day I used it.
[Samsung Galaxy Nexus] mike216:
13.1 is sleeping very well and screen on time is extremely good with the provided UV settings!
[Samsung Galaxy Nexus] mike216:
I got one too directly after the flash. Rite after the android updating that happens when you wipe the dalvik cache but its very good. Screen on battery use is amazing compared to earlier versions
[Samsung Galaxy Nexus] Kidd_Funkadelic:
Wed night I lost 1%/hour during idle w/ drop 13, which to me was the best (a tie) I've found on a kernel yet (that was the first day I was using Franco's kernel).

Last night I lost a hair under .5%/hour overnight on 13.1, which blew me away. I'm not used to that kind of battery life!

For reference, on 4.0.2 stock I was dropping ~2.5%/hour, and on 4.0.2 stock w/ faux kernel went up to 3.5%/hour. Then moved to CNA ROM (Lean kernel?) and went to 1%/hour.

Note aside from stock all setups were UV to ~90% and OC to 1.3, using interactive gov...

So Franco wins a gold star in my book! (Still using CNA- highly recommended).
[Samsung Galaxy Nexus] 5280WRX:
Franco - I've been reading about using c4 in ezekeel's thread. With this addition to your kernel, should we use performance governor now or at least move away from conservative and a lower minimum frequency for best battery life and performance. It seems like it is now better to keep the frequency up and let it enter the c4 state more quickly to save battery. Am I reading this correctly?
[Samsung Galaxy Nexus] TMFGO45:
The answer to the question regarding keeping the minimum frequency at 700 is a matter of how you use your phone.

If you are a power user, and the screen is on quite a bit, and you just always seem to be using it for something...then make it 350 minimum.

If you don't use it a ton, go with 700.

Swyped from my Galaxy Nexus (Codename Android 1.1.4, franco.Kernel #13.1, Hotplug On, Leaked 4.0.3 radios, Inverted Gapps, Natemz Mod w/ Fast Glow, Nova Launcher #12, 1200/350 UV'ed) in Tapatalk Pro!
[Samsung Galaxy Nexus] Elganja:
can you go into a little more detail? to me it doesn't make sense why you want 350 as a power user but not as a regular user.

what usage states puts you in 350?
[Samsung Galaxy Nexus] question.com:
I would also like to know this.
[Samsung Galaxy Nexus] Gwanatu:
I'm wondering the same. I would assume keeping it at the lowest possible is best.
[Samsung Galaxy Nexus] GaresTaylan:
/sigh

So I had my phone rooted a running fine for the longest time. I installed CWM and it worked fine. I booted into CWM recovery and installed the kernal and now Im stuck at a Google logo. So what is the recomendation to fix?
[Samsung Galaxy Nexus] Elganja:
what ROM are you using?
[Samsung Galaxy Nexus] ejkeebler:
advanced restore the boot.img from a nand backup I think. Are you running a 4.0.3 rom? If not that's probably why it's not booting.
[Samsung Galaxy Nexus] Geezer Squid:
If you get bootlooped or other non-recoverable issue:

1.	Pull battery and replace it.

2.	Hold down the up and the down volume key and press the power button.

3.	You have a screen that shows the android with an open hatch and the word Start above it.

4.	Use the up and down keys to navigate to the “Recovery Mode” menu

5.	Press the Power Button to reboot into Recovery (CWR)

6.	Reinstall your rom or restore a backup.
[Samsung Galaxy Nexus] zeppelinmad4:
Undervolt

Is there a reason why SetCPU and Franco's app show different voltages and saved settings for undervolting? Is there a terminal command to find out the actual voltages that are set?
[Samsung Galaxy Nexus] GaresTaylan:
My own stupid fault. I was using Android Revolution HD, which is 4.0.2.

Now my backup I created isnt working. Its still hanging at the Google logo after running.

Is it worth trying to just reflash the rom?
[Samsung Galaxy Nexus] Elganja:
hmm... the only issues I had was with the old app...

for the old app:

"If set on boot is ticked and we change the values after we tick it, the new values won't be updated in the init.d script. Going to fix it today." even though this was the case, his app would show the new values while setcpu would show the correct values

this should be fixed now... tbh i get in the habit of ticking off and on every time I make a voltage change (and I reboot)
[Samsung Galaxy Nexus] dgwood12:
Sounds like it's your only option at this point...

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] 5280WRX:
My question is actually different from 700vs350. Should we now keep it at say 1200 so that it can enter the c4 state more quickly. That is what seems to be suggested on ezekeel's thread.
[Samsung Galaxy Nexus] Elganja:
wouldn't keeping it at 1200 causing a ton of drain during usage? I understand that is probably the best thing to do for idle time (i.e. wake up and finish tasks quicker)... but i think usage battery life would blow if it always ran at 1200

probably similar ideas of 700vs350 can be applied to 700vs1200
[Samsung Galaxy Nexus] rgoyena:
I'm actually now losing more battery on this new update. I don't know why.
[Samsung Galaxy Nexus] TMFGO45:
Okay. So I was saying 700 for non power users so when the phones sleeping, it will wake up, finish quicker, get back to sleep.

350 because usually the screen will be on because you are constantly using it, maybe hardly ever going into deep sleep, so the 350 will conserve while in use.

Swyped from my Galaxy Nexus (Codename Android 1.1.4, franco.Kernel #13.1, Hotplug On, Leaked 4.0.3 radios, Inverted Gapps, Natemz Mod w/ Fast Glow, Nova Launcher #12, 1200/350 UV'ed) in Tapatalk Pro!
[Samsung Galaxy Nexus] TMFGO45:
I tested my numbers last night. Went to sleep at 59% battery. 7 3/4 hours later, I'm at 51%. I do believe that's 1% drain an hour in sleep mode. Pretty damn good.

Now when the phone is being used....that's just going to vary in my opinion based on exactly how the user is using their device....but as for me, I'm VERY happy with the numbers I'm getting across the board.

Swyped from my Galaxy Nexus (Codename Android 1.1.4, franco.Kernel #13.1, Hotplug On, Leaked 4.0.3 radios, Inverted Gapps, Natemz Mod w/ Fast Glow, Nova Launcher #12, 1200/350 UV'ed) in Tapatalk Pro!
[Samsung Galaxy Nexus] Elganja:
have you done any extensive testing?

i'm curious what idle life is for 350 vs 700 (like actual #'s or % differences between the 2 for both idle and some usage use case)
[Samsung Galaxy Nexus] TMFGO45:
All I can say is that I'm a power user. Always on my phone. When I check cpuspy, most of my activity gets listed in the 350 slot. Now if I had it at 700 minimum, seems like I would have been wasting that extra 350.....so I say, 350 minimum for power users, 700 for non....that's the best I can do for numbers. Unless you ask for something specific I can show you?

Swyped from my Galaxy Nexus (Codename Android 1.1.4, franco.Kernel #13.1, Hotplug On, Leaked 4.0.3 radios, Inverted Gapps, Natemz Mod w/ Fast Glow, Nova Launcher #12, 1200/350 UV'ed) in Tapatalk Pro!
[Samsung Galaxy Nexus] GaresTaylan:
Since my backup/restore wont work I was going to reflash my device since its hanging at the Google logo. The rom won't launch while in recovery.

Is there any way to get the phone connected to the computer and overwrite the rom installer i have on it to make sure that isnt it?

Sounding more and more like I may be dead in the water?
[Samsung Galaxy Nexus] Natolx:
Can always go to the boot loader and reflash recovery image using fastboot
[Samsung Galaxy Nexus] TEK112:
Just do a factory reset and let the rom start stock. Then copy you're files again and boot into recovery.
[Samsung Galaxy Nexus] GaresTaylan:
Doesnt work. Still hangs on Google logo.

Same as above. I am beginning to wonder if I should just use Odin?
[Samsung Galaxy Nexus] dwallersv:
FWIW... used to swear by Juicedefender, and was still using it through nightly #12. I verified that I was truly getting some benefit from JD (not much, but still some).

With nightly #13, I'm getting such incredible battery life that it's actually worse with JD. I've disabled it.

I keep 4G disabled. Get good 3G (1-1.5Mbps down) in the Santa Cruz / Scotts Valley CA area, so for 99.9% of my data usage (primarily streaming Pandora, syncing email, and other small stuff) I don't need 4G. Leaving it off unless needed saves a TON of charge.

Whatever Franco's done in this latest build has 3G, even when on all the time, sipping H2O molecules at network idle, rather than taking gulps. So leaving data on all the time is using less battery than having JD toggle it on and off every 15 minutes for apps to "check in".

I'm getting as good battery life as the best who have posted here. I'm running #13 with GummyNex 0.5.4. The only serious drain I get is when I'm using the phone, which doesn't surprise me at all.

Worst is playing Deadspace and Shadowgun :-)
[Samsung Galaxy Nexus] Berzerker7:
Just uninstall SetCPU and trust the Franco app's voltages, they work.

Yes, that will reflash the boot.img included in the ROM. I also suggestion switching to a 4.0.3 ROM.
[Samsung Galaxy Nexus] Zorachus:
You on 13 or 13.1 ? What settings ? Hotplugged enabled ? Which governor ?
[Samsung Galaxy Nexus] chubbrock:
Anyone having issues with Bluetooth? I had no issues connecting to my car to stream Bluetooth audio with nightly 13, but now can't connect with nightly 13.1. I'm on Codename Android 1.1.4.
[Samsung Galaxy Nexus] Codiusprime:
Seems with the latest update my camera has stopped working. It will work fine right after I reboot but after that it just goes to a black screen and force closes. I vaguely remember having this issue the last time I tried out one of Franco's kernels. Any ideas?
[Samsung Galaxy Nexus] Gwanatu:
Alright so I've changed my CPU profile to 350-700, and honestly I've not noticed any difference in any application so far. The OS is just as smooth as before, and I've played a few games and used it for the last 3 hours and it's been great. I've also adjusted the voltages to the following:

700mhz - 900mV

350mhz - 750mV

Time will tell what this does with the battery, but I'm hoping for a massive improvement.
[Samsung Galaxy Nexus] Zorachus:
Is there still an issue with the camera or was it bluetooth ? We had to turn one of those on, and then off, due to some deep sleep bug ?