yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] mike216:
Thanks a lot for the help my friend! I disabled that setting then made my call and it was all good. Just bought my phone less than 48 hours ago so ill try to replicate the reboot. Very new to galaxy nexus and I must say that without a doubt this has been the best tech buy I've ever had. I love this phone. Coming from a nexus s. We all loved francos work over there also. I was thinking that I made a call rite after waking the device and maybe that was just a hiccup. I hope! Do you notice a dramatic difference in battery with hot plug enabled?

On another note I just got an oem extended battery 2100 and it comes with a cover exclusively for verizon models on eBay for 33 bucks free and super fast shipping. I think that'd well worth it and it doesn't add any uncomfortable bulk. Check it out
[Samsung Galaxy Nexus] mike216:
I love CM and will be a faithful user but not just yet as I'm shooting for stability for now
[Samsung Galaxy Nexus] Ma5heen:
This guy is an asshole for laughing cuz he knows something somebody else doesn't.
[Samsung Galaxy Nexus] greydarrah:
I don't use my phone all day, so when I use it, I want it as responsive as possible with no concern for battery life at all. Would I get this best from using the performance governor in SetCPU or would a different governor be better?
[Samsung Galaxy Nexus] SteroidalFish2:
I'm curious..how would hot plug, and dynamic hot plug work together? I'm assuming it wouldn't be a good idea. :P

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] sway40:
They don't have to bc dynamic will turn off one core when loads aren't high even with screen off.

~ Sent from my Galaxy Nexus running Cm9~
[Samsung Galaxy Nexus] Gahh Its Lee:
Well I just had my first lockscreen wake issue. Had to pull battery. And I can say that it did reset my settings to 700/1000.
[Samsung Galaxy Nexus] jjrudey:
My phone is running pretty hot while doing non demanding tasks on #16.
[Samsung Galaxy Nexus] TEK112:
Did you wipe cache and dalvik after flashing it?
[Samsung Galaxy Nexus] jjrudey:
I always wipe before flashing but I also tried it again after because of the heat.
[Samsung Galaxy Nexus] TemplesOfSyrinx:
Does Kernel Auto-Flash wipe cache and dalvik?
[Samsung Galaxy Nexus] bowsersoulstar:
I don't think it does. Ever since I read Franco (and few other devs) saying that they don't wipe anything on kernel flashes, I don't either. Never had a problem not wiping cache/dalvik on subsequent flashes.
[Samsung Galaxy Nexus] mbh87:
Got a reboot on 16 earlier and once I booted back up I had no status bar or nav bar and a lot of my apps werent accessible. I was out while it happened so I had to restore a nandroid and wasnt able to get a log.
[Samsung Galaxy Nexus] Gahh Its Lee:
Strange... My Facebook is being really odd. Constantly reloads feed and randomly signed me out once. No idea why. Xda app signed me out once too.
[Samsung Galaxy Nexus] dmmarck:
What are your settings? Facebook was giving me problems earlier (as in a day or so ago), but not since 16.0.
[Samsung Galaxy Nexus] Gahh Its Lee:
What settings exactly? Facebook and xda are set up normally. I under volt a bit but I don't think that could cause fb reloading could it?
[Samsung Galaxy Nexus] dmmarck:
Kernel settings. What's your minimum? Facebook takes a decent amount of energy from what I gather, mainly because of that stupid GPS thing it triggers. For me, I had to wipe the facebook cache/data, and so far it's been "OK" but it has its moments.
[Samsung Galaxy Nexus] franciscofranco:
Facebook app is the biggest amount of **** I've ever seen in a single app since I use Android devices.

#16.1 is out by the way ;)
[Samsung Galaxy Nexus] Gahh Its Lee:
I'm on 16.1 right now thanks man. And I use 700-1200 francoturtle with dynamic hot plug. Franco your a genius dude.
[Samsung Galaxy Nexus] dp92180:
Haha
[Samsung Galaxy Nexus] chardd23:
why does the kernel never goes to 350 Mhz? its always 700Mhz and deep sleep
[Samsung Galaxy Nexus] dmmarck:
Ain't that the truth. It was so bad that I traced, somewhat unscientifically, to a rash of FC's on my Inc many moons ago. Talk about clunky.

Thanks for the update, just flashed and will keep you updated.
[Samsung Galaxy Nexus] mbh87:
Because 350 isn't on by default. You need to lower the speed in Franco's app, set CPU or whatever you use.
[Samsung Galaxy Nexus] danman7:
So, on 16.1, I see where francoGazelle is now the default. I have some questions.

Should we use francoTurtle? Is it broken and will be fixed?

Does Hotplug work with francoGazelle?

Thanks for all your help.
[Samsung Galaxy Nexus] Jdella681:
I apologize ahead of time because the question probably has been answered already and too lazyto flip thru all the pages. But keeping the min and Max at 700-1000 promote better battery life when changed to turtle? And would changing them to 350-1250 min-Max more ideal for battery life too due to the fact that its a lower clock speed when in standby?
[Samsung Galaxy Nexus] Gahh Its Lee:
With Franco turtle set to 700-1200 with dynamic hot plug my phones spending like half its time in 1200 and a lot in 1000 as well any thoughts? Its not using 700 all that much.
[Samsung Galaxy Nexus] Pupalei:
350 kills kittens.
[Samsung Galaxy Nexus] dr_w:
Has anyone tried 16.1 on codenamedroids 1.3.3 ROM? Curious if they are playing well seeing how hes using 4.0.4 parts. Franco, your thoughts on this?
[Samsung Galaxy Nexus] dmmarck:
Best reply ever to this 350 v. 700 topic...

So far, running 700 - 1200, francoGazelle, hotplug mod enabled.
[Samsung Galaxy Nexus] Stadsport:
I keep flashing different kernels trying to find ones I like better but I always come crawling back to Franco's kernel..
[Samsung Galaxy Nexus] mike216:
I keep flashing great kernels but there all Franco's lately and its a big battle to top 15.2! I love 15.2 and will keep trying the new versions until he tops it. Going to be hard to do as 15.2s battery life is insane! 16.0 Was pretty good on battery but 15.2 is KING for now. On 16.1 and will give it my overnight sleepy test and let you guys know my experience. So far its blazing fast but what else is new! Thanks franco will donate on Thursday.
[Samsung Galaxy Nexus] Neo3D:
Where do you type in the echo commands for these to work?
[Samsung Galaxy Nexus] jbdan:
I use this, but there are others that will do the trick as well.
[Samsung Galaxy Nexus] Persianity:
13.1 = best.
[Samsung Galaxy Nexus] franciscofranco:
Who said it was broken? Normal hotplug yes, dynamic hotplug, no.
[Samsung Galaxy Nexus] Timdor:
I noticed in your app that the Dynamic Hotplug option specifically names the francoTurtle governor. Does that mean that francoGazelle has it built in automatically and I don't have to enable it here?
[Samsung Galaxy Nexus] danman7:
My mistake. The fact that you were no longer setting it as default led me to believe there was an issue with Turtle and hotplug, or at least dynamic hotplug.
[Samsung Galaxy Nexus] macellaio:
Dynamic Hotplug works ONLY with the Turtle governor and is not available at all for Gazelle.
[Samsung Galaxy Nexus] revolt1:
I see a drain in Android system with the new update on 4g with a full charge dropped from full to 82% over night but before 16 versions it would only drop to 90% same set up same everything same set CPU set up
[Samsung Galaxy Nexus] BFirebird101:
Awesome kernel as always! Quick question that's been on my mind for some time. On the francogazelle governor, if my min is at 700 and my max is 1350, does the governor go between any of those values, like to 1200 at all? Or does it only stay at either the min or max value?
[Samsung Galaxy Nexus] chirea.mircea:
Sorry - should've posted in the GSM one.
[Samsung Galaxy Nexus] psohn:
I'm running 15.2 and after the new batteries I went from 2% drain/hr to 5% drain/hr. My drop is due to TouchDown email which is now the highest battery hog, even over SCREEN. I have JuiceDefender running and even tried turning off LTE but still the same. Finally I turned off data and went 2hrs with no drop.

Bottom line, work email sucks. The way I figure it, the only way to get good battery life with descent reception is to win the lotto and quit my job! :)
[Samsung Galaxy Nexus] TEK112:
Change your email frequency from push to 15min. See if that helps. Also, are you bypassing corporate security? I have seen the security bypass "fix" cause higher usage because initial server checks fail. I have had better success spoofing my phone as an iPhone (I don't know if touchdown has this capability).
[Samsung Galaxy Nexus] Tree of Knowledge:
What's the concensus on this being better than the stock kernel on 4.0.4? I used Franco's kernel prior to that coming out and I'm considering going back since I bought the app and I love Franco's work. Suggestions?
[Samsung Galaxy Nexus] Esteway.619:
I use #16 on stock rooted 4.0.4. Rom no issues and battery life is really good. Everything runs super smooth.
[Samsung Galaxy Nexus] Tree of Knowledge:
What kind of screen time are you getting?
[Samsung Galaxy Nexus] Esteway.619:
Haven't paid attention but I'll test that tomorrow and will. Let u know.
[Samsung Galaxy Nexus] dincfool:
What's better for battery dynamic hotplug or hotplug mod? Since your not suppose to use them both at the same time which was is better to use on aokp m3?
[Samsung Galaxy Nexus] Tree of Knowledge:
Dynamic hotplug since it turns off one of the CPUs when you aren't performing demanding tasks rather than only when the screen is off. Just keep in mind it only works on francoturtle so if you're more performance oriented, you'll want to stick with francogazelle and regular hotplug.
[Samsung Galaxy Nexus] KassaNovaKaine:
What exactly are the performance differences between turtle and gazelle? I'm on 700/1350 and haven't really noticed anything when switching between the two. Admittedly I haven't done extensive testing.

Is multitasking slower/faster? Transitions are smoother? Less slowdowns when multiple apps are open?
[Samsung Galaxy Nexus] Echo5Kilo:
So I noticed in the Franco Kernel Updater app it says that if I'm using the FrancoTurtle governor, and I want to enable Dynamic Hotplug, the min mhz is 700. If I'm using SetCPU, I'm assuming I have to set the min to 700mhz and do a reboot for that to take effect?
[Samsung Galaxy Nexus] Gwanatu:
I'm going to see if there's a way to set it to 15 min, that would be better than push for sure.

Also seems that since updating to Franco 16 and 16.1 I've had two instances, one yesterday and one today, where the screen won't turn on. The notification light pulses like normal, so it doesn't seem like the device is "frozen" per say, but it's completely unresponsive to anything I try to do. I'm going to try to keep the voltages normal and see if that helps in the next day or two, but these are the same voltages I've been running since switching to Franco some time ago.
[Samsung Galaxy Nexus] TEK112:
I have had that happen too. Dynamic hotplug, francoturtle, 700/1000. I just wait 5 seconds and press power again and then the screen comes on. Like you, it has only happened a couple of times. However, I have experienced it prior to 16.
[Samsung Galaxy Nexus] sway40:
It's happened to me a few times on same settings, I had to pull battery mine wouldn't come on and I waited a while.

~ Sent from my Galaxy Nexus running Cm9~
[Samsung Galaxy Nexus] TEK112:
Franco,

Hey man, can you change the download path of the kernel through the app? It is set to go to sdcard/Downloads. However, our phone does not have a Downloads folder it has a Download folder, singular.

Thanks.

edit: the app indicates that it is downloading to sdcard/Download, but the dialogue box says it is going to sdcard/Downloads.
[Samsung Galaxy Nexus] Gahh Its Lee:
The screen not turning on is likely an issue with dynamic hot plug. If you check other kernels they say don't use the hot plug gov which has dynamic hotplug basically built in.
[Samsung Galaxy Nexus] toby1064:
Second this

Second this, also had one instance of trying to wake the phone, pressed the power button and the speaker popped and it rebooted. disabled dynamic hotplug and switched back to regular to see if I get this again. it seems like it started with the intro of the dynamic version.
[Samsung Galaxy Nexus] Syn Ack:
Kernel Auto-flash = BEST INVENTION EVER

/we're.not.worthy/we're.not.worthy
[Samsung Galaxy Nexus] Howie Dub:
anyone else not getting deep sleep with 16.1? 700/1200 francoturtle with hotplug. thanks.
[Samsung Galaxy Nexus] mbh87:
app shows its going to /mnt/sdcard/Download for me and thats where it downloads to.
[Samsung Galaxy Nexus] TEK112:
Prior to the update released today or after the update?
[Samsung Galaxy Nexus] mbh87:
Im not sure, never paid attention. It still downloaded to the Download folder though.
[Samsung Galaxy Nexus] Zacisblack:
Does anyone know what "vbus-tuna_otg" is? Its listed as a kernel wake lock in better battery stats and has been running for 2 hours. FrancoTurtle, no hot plug mod.
[Samsung Galaxy Nexus] jkc120:
lock up and 10+% battery drained

Just noticed my phone was dead (power button didn't work). I did a battery pull and rebooted and it had lost nearly 15% battery.

I have hotplug enabled as well as dynamic hotplug with the francoTurtle governor and CPU set to 700/1200 on #16.1

There is no /proc/last_kmsg to post. logcat is only showing stuff since I rebooted. So not sure what other debug info I can provide...
[Samsung Galaxy Nexus] psohn:
You are NOT supposed to enable them both, only one or the other.
[Samsung Galaxy Nexus] EvilDobe:
IMO the best part about the kernel is the FAQ. Everything has been running smoothly & I have zero complaints. Just wanted to say keep up the great work. :)
[Samsung Galaxy Nexus] Gahh Its Lee:
Grr new app keeps resetting me to default settings in reboot. Set on boot in enabled.
[Samsung Galaxy Nexus] Kidd_Funkadelic:
Is there any reason that the app still says no update available when I'm still on 15.2?
[Samsung Galaxy Nexus] dincfool:
So are the majority of you getting better battery with dynamic or hotplug enabled?
[Samsung Galaxy Nexus] dcoy82:
Thanks for your great Kernel Franco. Been using it for quite some time now. For some reason 16.1 has been the only version so far that I've got bad battery life on. Every other release I've gotten roughly 12-14 hours battery time with 2.5 - 3.5 hours of screen on time. This release I'm only getting about 8 hours of battery and 1 - 1.5 hours of screen on time :-(

Keep up the hard work Franco! Purchased your app a while back.
[Samsung Galaxy Nexus] ocbooger:
I'd have to agree with this, I'm seeing almost exactly the same here. 14.2 was great for me on CNA 1.3.3
[Samsung Galaxy Nexus] Stadsport:
SoDs/kernel panics/lockups/whatever WRECK your battery. Not sure why. They seem to use more power than what would be physically possible.
[Samsung Galaxy Nexus] dincfool:
I guess I answered my own question. Ran dynamic enabled and disabled the other and within 10 mins my phone froze up had to pull battery...

16 seems to be draining faster than others but will keep testing....
[Samsung Galaxy Nexus] b33zy682:
Very true sixteen drains battery more than others. Those kworker processes are all over the place. Anyone else have the issue where the Franco app doesn't save UV settings after reboot? I have to apply the values after every reboot.
[Samsung Galaxy Nexus] neederishelp:
The UV is made to be that way, and I got fantastic battery on 16,thinking of going back to it, I'm on 16.1 right now
[Samsung Galaxy Nexus] neverhappy:
I'm on 16.1. had a few SOD's while roaming thru various apps while set for francoturtle and dynamic hotplug min freq 700 max 1200. The screen would go black, but apps were still running. Yes, had to do a battery pull.

kept francoturtle, disabled dynamic hotplug, enabled just hotplug. been running for 11.5hrs light use and still at 80%.I'll call this my safe spot to go to.

Still want to try new enhancements as Franco deploys them though. Knowing I have a reliable setup to revert back to, when I need it, is a bit more reassuring.

Also Running AOSP 4.0.3 ver 1.3.3

Update: well, since I posted, 16.2 is out. Looks like dynamic hotplug is removed (for now). That's ok, it was a great idea.
[Samsung Galaxy Nexus] dmmarck:
Just flashed to 16.2. 400mhz, eh? Innaresting...
[Samsung Galaxy Nexus] dincfool:
I was thinking the same thing, what are your feelings on this franco? Also how much extra should we be expecting to get out if turning cpu 1 off?

Btw nice with the updates, testing 16.2
[Samsung Galaxy Nexus] avid.aria:
Where can I find a link to 13.1,

I got the best battery life out of that!
[Samsung Galaxy Nexus] gnocchi_ny:
happened to me this morning... battery pull required
[Samsung Galaxy Nexus] gnocchi_ny:
+ 1
[Samsung Galaxy Nexus] dcoy82:
Flashed 16.2 hopefully my battery will be at least as good as it was before 16.1. Thanks again Franco
[Samsung Galaxy Nexus] Gahh Its Lee:
Running it at 400 min is creating lag pretty randomly I wish there was a way to have it run at 400 and more easily ramp up to 700 but conservatively ramp above that. I can dream lol
[Samsung Galaxy Nexus] jbdan:
I think here
[Samsung Galaxy Nexus] itch808:
Which version of 13.1 are you referring to? There are two listed with different dates on that page.
[Samsung Galaxy Nexus] jbdan:
There is only one 13.1 listed on that link dated the 20th of Jan. I think it's listed 13-1-20xxxxx

It's the best :D
[Samsung Galaxy Nexus] pauliewalnutted:
^^ok curiosity got me...want to see what this fuss is about. 700/1200 conservative/hot plug?
[Samsung Galaxy Nexus] jbdan:
I use 350-1200 conservative no hotplug. I also flash faux's reset kernel prior.
[Samsung Galaxy Nexus] Seano.:
after seeing so many people talk about 13.1 i went and reflashed it. it does seem like one of the best to date with battery and performance.
[Samsung Galaxy Nexus] danman7:
Loaded 16.2 last night. Seems to be running pretty well. However, I'm surprised with some results with AnTuTu. Running it with francoTurtle 400/1000, I get ~5400. Running with performance 700/1350, I get ~4500? That seems counterintuitive.
[Samsung Galaxy Nexus] yondercomesthetrain:
Is this even right? These voltages seem..... a bit too high for the CPU speeds. I just flashed 16.2 and I had the stock CNA kernel on it before. I've been having ducky battery life for a couple of days. Perhaps this is my reason?

Running CNA 1.3.3 with Franco Kernel 16.2.
[Samsung Galaxy Nexus] jd1001:
By far the best one yet. I found 16.1 very laggy on visual transitions. This one so far is a 100% improvement. Thank you very much.
[Samsung Galaxy Nexus] crimson12:
hey franco, Ive read a lot of your posts regarding the reason for the 700min and honestly i agree with it. However, I was wondering if in certain situations the 350 (now 400) is better? For example, I use my phone for music for at least 3 hours a day. Now when it's awake to play music it cannot enter deep sleep correct? So it stays awake at the 700 min. Would it not be better to set the min to 350 (or 400 depending on your kernel version) in a case such as this? I havent tried changing anything yet but I was wondering your thoughts on this. Thanks for a stellar kernel and app.
[Samsung Galaxy Nexus] mbh87:
Read up on ezekeels voltage control. Essentially those numbers are the highest points, since the voltage fluctuates and adjusts itself it doesnt mean you will ever see those numbers.
[Samsung Galaxy Nexus] yondercomesthetrain:
So these are normal numbers, you think? I mean, I've seen the lower frequencies with 3 digit voltages. Now they're all four digits.
[Samsung Galaxy Nexus] mbh87:
They are stock voltages. If you want to change them, go for it. Although ezekeel doesn't recommend it.
[Samsung Galaxy Nexus] mbh87:
This is what ezekeel had to say in his thread, and I'm assuming Franco implemented it the same way. I could be wrong though.

Custom Voltage:

Set the nominal MPU (= CPU), core (includes bus, RAM and GPU) and IVA voltages.

/sys/class/misc/customvoltage/mpu_voltages

MPU nominal voltages for the different MPU frequency states in mV (default = stock voltages; set with 'echo "voltage1 voltage2 voltage3 voltage4" > mpu_voltages'; this entry is mirrored to /sys/devices/system/cpu/cpuX/cpufreq/UV_mV_table for compatibility with SetCPU and similar apps)

/sys/class/misc/customvoltage/core_voltages

core nominal voltages for the different GPU frequency states in mV (default = stock voltages; set with 'echo "voltage1 voltage2" > core_voltages')

/sys/class/misc/customvoltage/iva_voltages

IVA nominal voltages for the different IVA frequency states in mV (default = stock voltages; set with 'echo "voltage1 voltage2" > iva_voltages')

Using Custom Voltage for UV can cause problems! The optimal voltages for each frequency state are determined automatically by Smartreflex Adaptive Voltage Scaling (AVS). The nominal voltages set with Custom Voltage are only the upper limit and used as a starting point for the calibration. Reducing the nominal voltages can cause the automatic calibration to fail and result in voltages which are too low for stable operation. Use at your own risk!
[Samsung Galaxy Nexus] itch808:
Good catch, the other is 13/18.

Does 13/1 need the echo command to enable hotplug as well for optimum use? Or is it good to go once flashing?
[Samsung Galaxy Nexus] MasterRy88:
SOOOO as long as you dont go too low then you should be all good right? My general thought process is that I drop my voltages a little at a time, then when it becomes unstable I bump up to what I was 2 steps ago, so that it should be WELL above what it crashed at. This has generally worked for me and ive never had any issues.......yet
[Samsung Galaxy Nexus] Tree of Knowledge:
Back on 13.1 again. I still think it's the best one.
[Samsung Galaxy Nexus] jbdan:
Yup still need to echo command in terminal for each reboot for hotplug to stick. Or you can use franco app and set on boot.

---------- Post added at 01:48 PM ---------- Previous post was at 01:45 PM ----------

+1

I don't do all these testing things, battery monitor, better batt stats, wake log thingys, etc... I just use my phone and check battery at the end of the day. I know what works on my phone for my usage. 13.1 is special!
[Samsung Galaxy Nexus] franciscofranco:
I seriously have no idea but I wouldn't count on bench values too much.

Those are stock values from TI.
[Samsung Galaxy Nexus] far_star:
No deep sleep on 16.2 running turtle with all default values on AOKP. Reverting back to 16.1
[Samsung Galaxy Nexus] mbh87:
If you are on AOKP 22, it's likely the SDM.apk causing your sleep issues. Lots of people are having the same problem.
[Samsung Galaxy Nexus] MasterRy88:
"Dynamic hotplug removed - this is a good idea on paper but CPU spikes up every other time while trying to check if cpu1 was online or not, and that is not expected at all. I may return to this implementation in the future if I think of a better way to do it"

But I still have the option to use it in 16.2 so it wasnt really removed?

EDIT: Or maybe you can still select it but it does nothing?
[Samsung Galaxy Nexus] Elganja:
update your app
[Samsung Galaxy Nexus] yondercomesthetrain:
I agree. I just went back to 13.1 and my phone is running supa fiiine.
[Samsung Galaxy Nexus] ccogan:
Do you happen to have a link to download 13 .1?
[Samsung Galaxy Nexus] jbdan:
There are a lot of people including me who have run all your kernels. I know you don't support older versions that is fine. But do you have any insider info as to why you think so many of us are finding 13.1 to be so exceptional? Do you take comments and reports from older kernels and try to implement similar parameters in newer revisions? What I have learned with kernels and the GN is that newer is rarely better. I'm just curious, I understand if you have not enough time to reply.

---------- Post added at 03:33 PM ---------- Previous post was at 03:32 PM ----------

Yes here dated Jan 20th. Just remember older versions are not supported
[Samsung Galaxy Nexus] far_star:
yep. That was it. I froze the app with Titanium Backup and I phone sleeps and sleeps and sleeps.

Thanks.