yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] GaresTaylan:
Ok - used Odin and was able to get back to the stock rom on 4.0.2. The device remains unlocked and I rooted the phone again.

I copied the ROM file over to the internal storage location on the phone and booted into fastboot. Went into recovery and I am getting the little android guy on his back with a red excalamtion point on him. I cant see any of my files and dont have the option to install from SD like I did last time.

Ideas? Truly appreciate all the help I have received from you all. /system/recovery-from-boot.p is not in the /System folder when i look in root explorer.
[Samsung Galaxy Nexus] zeppelinmad4:
Good enough answer. Just wasn't sure if one wasn't keeping the settings or not.
[Samsung Galaxy Nexus] ejkeebler:
sounds like the default recovery overwrote your cwm recovery. Which means you need to reflash recovery, the reflash the rom.
[Samsung Galaxy Nexus] GaresTaylan:
I used the toolkit to reflash stock recovery. The file didnt reappear and the issue is still happening when I boot into recover. Any other ideas?
[Samsung Galaxy Nexus] ejkeebler:
I think you need to flash cwm not the stock recovery, I think, not sure you can flash a new rom with the stock recovery, but I could be totally misunderstanding the situation.
[Samsung Galaxy Nexus] rgoyena:
Hello. How do we revert back? This update is sucking up my battery like crazy!!!!
[Samsung Galaxy Nexus] RyderOCZ:
Did you flash 13 or 13.1? If you flashed 13 just flash 13.1.

If you still have issues with 13.1, you can get 12 here: http://dl.dropbox.com/u/1582804/franco.Kernel-nightly12.zip
[Samsung Galaxy Nexus] rgoyena:
I'm on 13.1. I bought the update kernel and I just check for updates there but this thing is horrible. I never had battery be killed this quick not even doing much.
[Samsung Galaxy Nexus] RyderOCZ:
Did you wipe caches and install the kernel? I am on AOKP 19 and 13.1 with no issues.

I don't think the kernel itself is causing issues, possibly a combination of your setup?
[Samsung Galaxy Nexus] rgoyena:
I did my usual and I do the long way. Clearing cache and dalvik before flashing. I'm also running on cnd 1.1.1
[Samsung Galaxy Nexus] drmp3z:
WOW! I am total opposite of you. I can't get my battery to die. I think this is fantastic. Did you go to camera after reboot and back out and go to apps and force close it?
[Samsung Galaxy Nexus] rgoyena:
No I never did. I've been using Franco's build and all of em are fantastic except from whats happening now. I will try and do that
[Samsung Galaxy Nexus] rgoyena:
Would it be a problem reverting back from 13.1 to 12? I was just thinking to flash 12 since very stable and takes less damage to battery.
[Samsung Galaxy Nexus] franciscofranco:
Yes that is normal. I use my own way to check for saved voltages, while setCPU uses it's own. Both apps work independently of each other.

I'm still unsure if setting it as performance is good or not, so I can't answer you clearly.

Seeing that 90% of the users are very happy with the battery in their phones, including myself, the issue it's surely at your end, possibly some app keeping your phone awake.
[Samsung Galaxy Nexus] rgoyena:
I reverted back to my backup and loaded Franco 12 but I can't redownload the updater. Said that its not compatible. Any clue why?
[Samsung Galaxy Nexus] franciscofranco:
Market being stupid and/or rom issue =(
[Samsung Galaxy Nexus] rgoyena:
Crap! I really love your kernel. My mission tonight is to make this **** work!
[Samsung Galaxy Nexus] franciscofranco:
Send me an email and we can sort something out ;)
[Samsung Galaxy Nexus] rgoyena:
I will. Thank you so much! First dev to actually offer some assistance. Love you brah! Hahahaha jk....

I loaded a different rom. About to flash your kernel again. :)
[Samsung Galaxy Nexus] TEK112:
What ROM are you on?
[Samsung Galaxy Nexus] Stockmoose16:
I've got to believe that power users will get better battery life by setting the cpu to 350mhz vs 700mhz. Logic says that a lower current will use less power.

That being said, I'm curious what kind of screen on time others are getting with 13.1 unmodified? With 4g on, never using wifi, I max out at 2:15-2:30 min. I think this is the best way to make a comparison, since everyone uses their phone differently.
[Samsung Galaxy Nexus] Tree of Knowledge:
I run 4g all day as it's faster than my apartments terrible wifi and I max out at right around 2-2.5 hours of screen on time as well. However when using the screen off data function on AOKP and switching it to 3g while my screen's off as well as hotplug enabled I did reach upwards of 3 hours screen time the other day with fairly heavy usage.
[Samsung Galaxy Nexus] TEK112:
For everyone out there... this is a real world usage situation. I get the same thing. Short of using a flashlight coupled with a screen brightness of 1%, you won't see more than 3 hours of the screen.
[Samsung Galaxy Nexus] Stockmoose16:
Glad to hear all these stories about 6 hr screen on time are bogus. If I'm on wifi instead of 4G, I can probably get 3 hrs+, but solely on 4g, it's nearly impossible to get more than 2:30 min. The kernels only seem to help with idle time. That's why overclocking this kernel gives you a low battery drop with the screen off. Don't think anything can help screen on time.
[Samsung Galaxy Nexus] TMFGO45:
I also think 3 hours screen time max in a real world situation...that's been my experience.

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] Stockmoose16:
I'm having one major issue with this kernel. When I select "reboot" from the power menu, my phone starts to go through the process, but then the screen freezes with the reboot logo on the screen. The only way to restart the phone is by pulling the battery. I've tried clearing cache, dalvik, and fixing permissions, but still can't get the phone to restart.

Any suggestions?
[Samsung Galaxy Nexus] mike216:
My phone runs around 105-108 while in use. Is that ok or considered to be high. I think its battery temp as I have no idea how to get a read of cpu temp. Any help would be greatly appreciated

Normal cpu temp?
[Samsung Galaxy Nexus] EyeOfTruth:
Franco,

13.1 is awesome. I have 700/920 and in 12 hours I have have used a little under 40%. And most of that was all earlier when I had heavy phone use. My settings say my battery has been mainly used by my voice calls at 41%. So I am defiantly pleasantly surprised.
[Samsung Galaxy Nexus] TMFGO45:
I think around 35 to 37 Celsius is where it hangs when not being used....not sure what temperature that is for, I think maybe it is just one overall phone temperature or something?

When tethering and charging at the same time, mine has hit the 50's.....won't hurt anything but overall battery longevity to my knowledge...just don't put it in the freezer to cool it down :)

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] EyeOfTruth:
The first one I am hoping is posting in in Fahrenheit and the second one is posting in Celsius

Just for a quick reference the 105 is about 40 Celsius and 35 is about 95 Fahrenheit

But I would agree it probably wouldn't hurt anything if you are worried about it if you are OC slow the processor down. The UV shouldn't really cause it maybe if you OV(Over Voltage) the processor it might cause it as well.
[Samsung Galaxy Nexus] rgoyena:
I tried everything and also different rom but I can't seem to make 13.1 hold battery life. I switched back to version 13 and works like a charm.

Franco, do you know why my battery holds better on 13 and not on 13.1?
[Samsung Galaxy Nexus] mike216:
What works for you may not work for me! I also got better sleep on 13 so I would go back to that if I were you. Its strange and I don't understand why some have totally different experiences. I like to name a folder on my SD called A-kernels and throw all the kernels I really like in there.
[Samsung Galaxy Nexus] TMFGO45:
When flashing kernels, can they just be flashed over previous? After wiping the proper areas...no need to reflash ROM or anything right?

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] SDC_Bolts:
Correct, wipe cache and dalvik....flash zip
[Samsung Galaxy Nexus] PapaWangsta:
I'm having issues with the 13.1 kernel!

Problems:

1. Random reboots.

2. Phone over heats to 110 degrees.

3. Alarm for some reason doesn't turned on.

4. Battery life is getting way way worst, when I woke up this morning my battery was 11%, normally the battery was over 80% left in the morning.

I had none of the above issues using 13.

Luckily, I still have the version 13 on backed up! :)
[Samsung Galaxy Nexus] rgoyena:
I have to agree. The 13.1 was really actually weird on mine. Draining lots of battery but was lucky enough that I still had a copy of version 12 and 13. I'll just wait for Franco's update rather than using 13.1.
[Samsung Galaxy Nexus] zeppelinmad4:
Couple things. I went ahead and removed SetCPU just so there weren't any conflicts between the two apps. I then undervolted to 1200@1150 920@1025 700@925:

I had rebooted the phone and since "set at boot" wasn't ticked I figured the current numbers would have changed. They were still the same. I wasn't sure if it was a problem with the app or if it really was still the same so I went to terminal emulator and typed "cat /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table" and found out that it was back to stock:

At this time, I just decide to change it back to 1200@1150 920@1025 700@925 and click "set at boot." I played with it for a little while just to make sure everything was fine and then rebooted. Phone turned back on and the battery started plummeting like no one's business. Soooooo....I went to CPU spy and noticed that the only unused state is Deep Sleep (should be 1350 and 300):

The only way to get Deep Sleep to turn back on (that I figured out) is to restore boot.img from a backup.

Maybe this is a bug or maybe I am just stupid. If I am just stupid, I hope somebody can help me in figuring out how to get the undervolting values to stick at reboot or to have Franco's app show the correct values.
[Samsung Galaxy Nexus] calebv2:
my deep sleep works just fine I think its something that you did
[Samsung Galaxy Nexus] zeppelinmad4:
Obviously. I just stated everything I did. I'm just trying to figure out how to get the undervolting to stick after reboot.
[Samsung Galaxy Nexus] Zorachus:
Anyone have a link to the older 13 kernel ?
[Samsung Galaxy Nexus] fred fredburger:
What recovery are you using? I had a similar problem using the Touch version of CWM here, flashing both kernel and ROMs. Once I went back to 5.5.0.4 I was able to flash just fine.
[Samsung Galaxy Nexus] 2015Ducatimulti:
yeah I have the standard 5.5.0.4 CWM, I gave up for now I had to restore from a back-up

edit : rom I`m using is ICL53F Deodexed Rooted Busyboxed + Softkeys + APM/AB MOD: http://xdaforums.com/show....php?t=1394639

by: bigxie
[Samsung Galaxy Nexus] fred fredburger:
This kernel is only for 4.0.3 (IML74K), it won't work on 4.0.2 (ICL53F). You could install Bigxie's IML74K build here and then use this kernel.
[Samsung Galaxy Nexus] brocktice:
Trying stock CM9 kernel

Just for control purposes, I'm going to go back to the stock cm9 kang kernel and see if my battery woes change at all. If someone could tell me on which date franco #8 was available, I think I already have the .zip and can try going back to that as well.
[Samsung Galaxy Nexus] 2015Ducatimulti:
well I feel like a frickin idiot thanks I will try that :D
[Samsung Galaxy Nexus] fred fredburger:
We all start somewhere, and yesterday was my day for being an idiot, so you're only a day behind! :cool:

Page 1 says January 1, but I don't know if that's early morning (12/31) or late night (1/2). #9.2 was early morning of its stated date, January 5.
[Samsung Galaxy Nexus] brocktice:
Wow, it's only been a few hours, but I'm already seeing a MAJOR difference between the stock cm9 kang kernel and Franco 9.2. Battery use is almost nothing so far on the stock kernel, vs. dropping like a rock on 9.2. Will report back after more time and usage scenario variation.

EDIT: It's now been almost 6 hours on battery (with the stock cm9 kang kernel) and I've seen a drop of 28% over 6 hours or just under 5% an hour. At that rate I should get around 20 hours which, if true, would be phenomenal.
[Samsung Galaxy Nexus] stevessvt:
Hey man, trying to buy your app in the app store, but on Wookie ROM and its not coming up for me.
[Samsung Galaxy Nexus] fiveoh:
I went 18 hours on the 9.2 kernal and only had a drop of 11%. I'd say we have a winner. Granted 8 hours of that was in the middle of the night with no usage, but the other 10 were pretty typical usage for me.
[Samsung Galaxy Nexus] ejkeebler:
how on earth??? i have a mere 30 minutes of use and i'm down 20%
[Samsung Galaxy Nexus] JATPol:
Same here. : -(

What you guys doing getting so good times on battery????
[Samsung Galaxy Nexus] pospower:
How to undervolt.

I am not seeing options anymore for undervolting anyone?
[Samsung Galaxy Nexus] sinik420:
Read the op
[Samsung Galaxy Nexus] pipnmike:
I'm using #9.2 with Gummy the latest version. Almost 6 hours usage with a few calls, texts, and checking email several times. I'm at 81%. It may be the camera sensor bug issue possibly? After booting, I started the camera app and just went back into the homescreen.
[Samsung Galaxy Nexus] :
I just got SoD after I enabled hotplug. Running #9.2 on GummyNex 0.3.8

Edit: Is anyone here, that is getting the amazing battery life, using the hotplug option?
[Samsung Galaxy Nexus] franciscofranco:
Hotplug is still very experimental, so it's normal :)

Nightly 10 is out btw.
[Samsung Galaxy Nexus] tps784@yahoo.com:
for the people using GummyNex I am going on 9 hours with 40% left. Although this morning I was on WIFI and my phone lost its Cell connection and it was trying to connect for about an hour. My battery was dropping quick I was down to 60% after the hour. Once I figured it out I restarted my phone connected and was good to go hence the 9 hours 40% left. Not sure if you guys are having the same problem. Thought I'd share.

I am running Gummynex 0.4.2 and Franco's 9.2
[Samsung Galaxy Nexus] :
Thanks!!!!!

Edit: I had to of checked for update (and missed it) RIGHT before you posted through your app :)
[Samsung Galaxy Nexus] marc91988:
its seems my Netflix is not working is this due to the kernel or is it winners cm9 kang?
[Samsung Galaxy Nexus] franciscofranco:
Not kernel, that's for sure.
[Samsung Galaxy Nexus] TMFGO45:
My dropbox....I keep them until I know I will never revert back :)

http://db.tt/V2XeIqOn

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] b33zu:
OK guys I have some questions since you all probably have tested this kernel way more then me. I'm currently on 13.1. What settings do you guys use that helps like undervolting, hot plug, under or over clicking, or using setcpu or frillscpu. I'm interested to see what you guys say. Thanks
[Samsung Galaxy Nexus] TMFGO45:
I'm running hotplug on using francos app. Then I use setcpu to drop minimum to 350. And to undervolt as follows: 1200\1175, 920\1075, 700\925, 350\800

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] dwallersv:
13, hotplug enabled, 1350/700 max/min, stock UV.
[Samsung Galaxy Nexus] EyeOfTruth:
I have hotplug enabled, UV 700 @ 900MV and 920@1000mV. I also have my phone UnderClocked why because its a dual core phone it has more power than it needs. I am running GUmmy Rom.

My phone acording to CPUSpy hardly goes to 920mhz it tends to either be in deep sleep or 700 mhz.

I used to use setcpu for the profiles, but then decided it was pointless because it adds more overhead as it is constantly monitoring my CPU so I just use the built in CPU management inside the Gummy Rom. Yeserday I made an update so far my phone has been off the charger for about 5 hours and I have used 8%. I have it constantly connected to 3g/4g depending on signal, made a few phone calls, and txts. I also lowered my brightness to almost the lowest it will go since I tend to be inside most of the time.
[Samsung Galaxy Nexus] kichard:
Hot plug, conservative, under clocked to 9mhz and I shut off 3g when I'm jot using the web ....I'm very impressed.
[Samsung Galaxy Nexus] TMFGO45:
9mhz?

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] kichard:
My bad!
[Samsung Galaxy Nexus] Gahh Its Lee:
So is hot plug the governor to use with this? On faux kernel he said use interactive. I'm curious how this will run compared.
[Samsung Galaxy Nexus] TMFGO45:
No, hotplug can be used with all governors. Just needs to be enabled.

On faux, I think interactivex is the hotplug enabler on the kernel....

But with franco, you can use it on all....

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] Gahh Its Lee:
And in order to use hot plug I need to buy the app?
[Samsung Galaxy Nexus] denpad2010:
when I find these settings I'm running AOKP and I don't find the setting to change voltage or CPU speed
[Samsung Galaxy Nexus] MalaysianMafia:
In Franco updater app on marketplace
[Samsung Galaxy Nexus] EyeOfTruth:
Nope go back to the first post if you know how to run shell commands

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

This command has to be ran after each reboot
[Samsung Galaxy Nexus] denpad2010:
Thanks I just downloaded the app now I don't know exactly how use it I mean what is the best setting to get the best battery life....I guess I have to try different settings and see which works betters am I right ??? Thanks again

I'm using these settings u hope is not dangerous I have no experience with this
[Samsung Galaxy Nexus] jbdan:
Just tried 13.1 yesterday it works really well!

Standard 1850 battery 3.7 hrs of 4G rest on wifi. Cell signal for me sticks around -105dbm
[Samsung Galaxy Nexus] Tsoflyyup:
Wow thats impressive....any other settings ur using clocking? Voltage? Govenor?
[Samsung Galaxy Nexus] kinggroin:
I'm not sure if this is the place for requests, but I'd like like to make one:

The ability to have a per app profile. Maybe like 5 slots.

I like to keep my phone at 700mhz, but the kairosoft games run sluggishly at that speed since they don't have any gpu acceleration. For those exceptions, I'd put the CPU back to Max.

Thanks for the hard work.
[Samsung Galaxy Nexus] jbdan:
Just using setcpu to set to 350mhz -1200mhz. Default mVs and conservative gov which is default also I think.
[Samsung Galaxy Nexus] PapaWangsta:
Mind take a screen cap of your SetCPU settings? That's really impressive.
[Samsung Galaxy Nexus] jbdan:
Not at all will post some pics up later this afternoon
[Samsung Galaxy Nexus] dcoy82:
What's your brightness set to? Was it the same the whole time?

Are you using hotplug and/or undervolt?

4 hours of screen on time is pretty good.
[Samsung Galaxy Nexus] jbdan:
I actually think 4hrs screen on is outstanding. :) remember though 18 hours was on Wi-Fi.

Auto brightness whole time. Using kernel like it came from Franco conservative gov. Only thing I changed was minimum frequency to 350. I haven't tried his app yet or done terminal to enable hot plug.
[Samsung Galaxy Nexus] doublea500:
which rom are you running?
[Samsung Galaxy Nexus] jbdan:
Aokp 19
[Samsung Galaxy Nexus] jbdan:
Here ya go :) stock throughout except min frequency
[Samsung Galaxy Nexus] b33zy682:
Using this kernel for awhile but all of a sudden "surface flinger" is a process that's taking up alot of battery. Anyone know what that is
[Samsung Galaxy Nexus] b33zu:
Which one is better. Francos kernel or Imoseyons new 1.7.1 kernel
[Samsung Galaxy Nexus] jbdan:
I think they are both very comparable. Can't go wrong wither way imo
[Samsung Galaxy Nexus] PapaWangsta:
Thanks for sharing! I had mine at interactive, now trying conservative settings, and see what's the result! :)
[Samsung Galaxy Nexus] denpad2010:
Hello I just bought the extended battery any suggestion to have the best performance I mean do u suggest make a calibration or something thanks
[Samsung Galaxy Nexus] TEK112:
No offense, but that isn't a question for this thread. Search around and you will find the battery calibration threads.
[Samsung Galaxy Nexus] denpad2010:
My question os not how to calibrate is for any suggestion using this kernel and the extended battery thanks anyway
[Samsung Galaxy Nexus] TEK112:
Please go back and re-read your first post. It is very hard to understand.

As far as performance gains from an extended battery, there are no changes necessary regardless of which battery you have installed. This kernel will perform the same.
[Samsung Galaxy Nexus] denpad2010:
OK thanks maybe a language issue I'm not a native English speaker sorry for the misunderstanding
[Samsung Galaxy Nexus] TEK112:
No apology necessary. You at least speak two languages. Hell, I only know english and bad english...lol

Regardless of how you run this ROM you probably want to check out the battery calibration threads around here. It could improve the use of your battery. As for kernel operation, no special changes need to be made.
[Samsung Galaxy Nexus] denpad2010:
Lol thanks
[Samsung Galaxy Nexus] rgoyena:
Franco ftw! Not using 13.1 though since its kills my battery
[Samsung Galaxy Nexus] Gahh Its Lee:
Which are you using if not 13.1? Also if I change voltages I can only get a positive battery effect off lower voltages right? I found slightly lower voltages my phone works with and wanna make sure I'm not hurting myself.
[Samsung Galaxy Nexus] neederishelp:
I'm using 13, got 10 hrs of battery with 3 hrs of screen on
[Samsung Galaxy Nexus] mfish123:
Couldn't we set the regular min mhz to 350 and the screen off profile min mhz to 700 and get the best of both worlds?
[Samsung Galaxy Nexus] mcampbell:
You can do that with setCPU if you don't get it stock I think; no?

---------- Post added at 09:43 AM ---------- Previous post was at 09:41 AM ----------

That's fantastic. I've never been able to get less than between 2% and 3% sleeping, with lots of tweaks (sound off, location services off, removing a bunch of stuff from auto-starting, etc. I tried juice defender, but it takes way too long to turn data back on when it's off so I ditched that.
[Samsung Galaxy Nexus] franciscofranco:
I haven't got any of those issues. I'll double check few things. Thanks.

I didn't know the app was still having that bug. I'll correct it (the first shots).

The second problem...well something happened there with the voltages. I think the phone entered in some kind of stall and was stuck at max freq for a while. I thought that was fixed in Imoseyon's UV interface...guess it's not.
[Samsung Galaxy Nexus] TMFGO45:
I read somewhere that profiles, especially screen off profiles, are bull****. But just doing one profile, exactly like you described seems like it could be beneficial...since it was your idea, you get to be the guinea pig and report back :)

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!