yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] chuckenfoot:
I'm sorry for this question...I've searched and Googled though. How do I turn on deep sleep? Using CPU spy shows it as unused?

Thanks!
[Samsung Galaxy Nexus] TEK112:
You don't turn it on, it is a built in feature. Did you toggle the camera app as stated in the OP? Also, what ROM are you running?
[Samsung Galaxy Nexus] mikeacela:
+1 yay were all friends again lol. Being a college student myself I understand how finances can be a problem sometimes. No one should assume someone else is able to pay for anything especially since they don't know their personal finances no matter what price it is and it's none of their business anyway. That being said lets play nice and show franco our respect :)
[Samsung Galaxy Nexus] Gahh Its Lee:
I've had absolutely no issues with r111 I am running 700-1300 I know those aren't the exact values but you get it. Using the hot plug gov its running great
[Samsung Galaxy Nexus] mistawolfe:
Runs smooth as silk but I got a BSOD on almost every lock.

Liquid v1.2.
[Samsung Galaxy Nexus] franciscofranco:
r112:

* Sleep of death fix attempt
[Samsung Galaxy Nexus] mrwebb:
Which mhz(384/512) do we download for speed? I usually download your kernals with whatever stock settings you have set.
[Samsung Galaxy Nexus] Rem3Dy:
If you can't figure that out, you should probably stick with the milestone releases...
[Samsung Galaxy Nexus] fclifton:
I hope this isn't too off topic. I am using the Light Flow app. I am wondering if it uses more power to flash the LED, or to just leave the LED on continuously. I thought maybe some of you gurus might have some insights.

Galaxy Nexus LTE running IMM30B 4.0.4
[Samsung Galaxy Nexus] Tree of Knowledge:
Question about sound control: Do I need to have the high performance sound on to be able to adjust the maximum sound volume or are these two separate from each other?
[Samsung Galaxy Nexus] jbdan:
M2 is delicious on aokpb28 marvelous work, lovely kernel version! Thx!
[Samsung Galaxy Nexus] mike216:
I also use it and love it. What I do is use the timer in the settings so it doesn't turn the led notification on from 3am-11am

I also noticed the app does use a little juice but to me its worth the cost

This app is so buggy the answer to your question is linked in with the quote. Weird!
[Samsung Galaxy Nexus] mike216:
There totally separate. You'll have louder sound with the high performance disabled but it'll sound more clean if its enabled. I set the other at Max (3)
[Samsung Galaxy Nexus] Magnus_CA:
Franco is providing the nightlies in both stock and overclocked gpu versions but I've wondered the same thing myself.
[Samsung Galaxy Nexus] cdchris12:
Franco,

I've been using your kernel for a while now, and I love it. I got onboard around nightly 47 or 48, and I haven't even felt a slight inclination to flash anything else. Thanks for making such a kickass kernel.

One request I've got for you, though. I like to UV my CPU. The voltages never stick through a reboot when I use your app. Any chance you could add an option for the voltages to be set on boot, just like the frequencies and governor?
[Samsung Galaxy Nexus] raphenucleus:
Franco commented at some point that he doesn't make them stick on reboot so if you set unstable voltages it won't get stuck in a bootloop, so I doubt he'll add that feature. If you want them to stick on reboot, however, you can use setcpu.
[Samsung Galaxy Nexus] Zacisblack:
Hey Franco, one thing I want to report that I can only seem to reproduce on your kernel. While listening to music with headphones, I often get this extremely loud sound that sounds like radio interference/ a lawnmower and makes me almost **** myself. It seems to happen when I'm on wifi only and when I'm pulling data. I've uninstalled dsp manager, turned off high performance sound, tried different volume levels of ezeekels tweaks, and have tried 4 different music players. I've also tried 3 different pairs of headphones. Not sure what's going on but if you could look into it I'd be very grateful.

Edit:

I'm on Gummy 0.9.0 and nightly 112. The probably has happened since Milestone 2.
[Samsung Galaxy Nexus] arasky:
thanks, i'll try this. i have to wipe going to aokp b29 so no biggie if it im forced to wipe.
[Samsung Galaxy Nexus] Zacisblack:
Disregard.
[Samsung Galaxy Nexus] GinoSylum:
I'm using Roman AOKP 4.0.4. This is my fist rom with OC and UV settings controls built in. My question is how to I handle the settings? Do I make changes in Franco's app or in the rom control? Or do I set them both to match?
[Samsung Galaxy Nexus] mistermojorizin:
either one or the other. not both. if you want voltages to stick, then romcontrol.
[Samsung Galaxy Nexus] Dragnz:
Question

So I recently flashed Gummy 0.9.0. I let it cook in for a few days before flashing the newest stable version of Franco.

I'm also running Badass Battery Monitor to watch for any annoying battery sucking apps. I have noticed that since flashing the newest Franco stable (Milestone#2) when I look in Badass Battery Monitor under App Usage that "Kernel" always has the highest percentage of power used.

IT wasn't like this with the default Kernel that came with the rom. Is this normal or do I have something setup incorrectly ?

I do have the paid version of the Franco Kernel Updater app installed as well.

Thanks in advance.
[Samsung Galaxy Nexus] Gil Smash:
Well generally higher is faster...

Haha
[Samsung Galaxy Nexus] kimboinatl:
I installed 111, and was getting SODs and lockup, usually while shooting video - specifically, when I open my camera app and then select video recorder. My phone also SODed during the night. I installed 112, same thing. I had it set to use the Hotplug governor during screen off, 729 min. My main profile is conservative using 1344/729. Switched back to M2 for now.
[Samsung Galaxy Nexus] mike216:
I noticed that but you have to look at real time use. I can get over 4 hours of screen on time on M2, use a battery monitor app like better battery stats. Far more accurate when it comes to pinpointing problems
[Samsung Galaxy Nexus] Dragnz:
Thanks,

Ill give it a try.
[Samsung Galaxy Nexus] upther:
Maybe your phone is like mine and doesn't like Hotplug. That's the only time I've got SODs with these kernels.
[Samsung Galaxy Nexus] kimboinatl:
Hmm, possibly? I have always had Hotplug checked in my settings, before it was made its own governor. Maybe it just doesn't like it as a governor. Do you have problems with the Hotplug setting, or the Hotplug governor?
[Samsung Galaxy Nexus] upther:
Both. I haven't given it much time with the governor though. When I installed AOKP B29 and Francos 107, it defaulted to the Hotplug governor and before I realized it, got a SOD. Moved back to OnDemand and haven't had a problem since.
[Samsung Galaxy Nexus] kimboinatl:
I'll try re-installing 112 and set my screen off profile to Conservative and see how that works out. Thanks!
[Samsung Galaxy Nexus] spinkick:
Profiles cause issues, try eliminating their use and see if its more stable.
[Samsung Galaxy Nexus] axne1:
Are you serious man? :confused:
[Samsung Galaxy Nexus] hredder:
Hey guys quick question. Is there a way to prevent cm9 nightlies from overwriting the kernel so i dont have to reflash francos kernel. If not no biggy it only takes a few seconds to reflash
[Samsung Galaxy Nexus] winner00:
I guess you could modify the updater script to not flash the kernel but that would require you to modify it each time.
[Samsung Galaxy Nexus] hredder:
Yeah thanks winner. Again just easier to reflash I guess
[Samsung Galaxy Nexus] Xezuka:
Was going to say the same thing. Gotta give it to Franco for making it easier than ever to flash. I'd just re-flash each time to save yourself from any troubles. :)
[Samsung Galaxy Nexus] hajabooja:
#112 Has been running great for me.
[Samsung Galaxy Nexus] williamthegoat:
Does the leaked .4 count or does it need to be aosp .4?
[Samsung Galaxy Nexus] innov8ion:
I'm pretty sure that 4.0.4 is 4.0.4 regardless of the flavor...
[Samsung Galaxy Nexus] sway40:
Damn my phone is running insanely hot on 116 nightly, never had a heat problem. Soon as i felt it, it rebooted itself.
[Samsung Galaxy Nexus] laureanop:
Running the 384 version on liquid 1.25 and is rock solid. Awesome job

"the relentless pursuit of the perfect rom" now on the gnex
[Samsung Galaxy Nexus] axne1:
Well testing r116 right now with Aokp 4.0.4 biuld. 384 gpu wish me luck. Thanks Franco :)
[Samsung Galaxy Nexus] theboo7:
Anybody else having problems downloading past nightlys from link in OP?

http://minooch.com/franciscofranco/Galaxy Nexus/nightlies/

More specifically, if anyone has a backup, I'm trying to get a copy of nightly 112 384GPU
[Samsung Galaxy Nexus] Gahh Its Lee:
https://www.box.com/shared/b67a499903d9dd082193
[Samsung Galaxy Nexus] theboo7:
Thanks for this
[Samsung Galaxy Nexus] brycetrem:
R116 is running great so far with 512 oc :]
[Samsung Galaxy Nexus] zeke1988:
from HTC Dinc to GN, my phone always hot to touch..... it's hard for me to believe that statement haha
[Samsung Galaxy Nexus] sway40:
I didn't just mean a lil hot, I meant to where I couldn't even palm it without having to let it go. I went back to m2 kernel and M4 aokp... aokp 29 is way to unstable right now, I've never had rebooting issues until that build.

~Sent from my GNexus running Aokp~
[Samsung Galaxy Nexus] GinoSylum:
I'm running AOKP 29 with Franco's M2 with no heat problems at all and I'm over clocked. Maybe the problem is Franco 116 not AOKP 29? I haven't flashed 116 so I don't know...
[Samsung Galaxy Nexus] franciscofranco:
No no, not my kernel problem sorry, my device is insanely fresh and trust me when I say I ve been flashing a lot of experimental kernels myself.
[Samsung Galaxy Nexus] Ma5heen:
I haven't flashed either yet. I'm about to go with AOKP 29 and Franco 116. I'm doing full wipes. Only way to know is to try it yourself.
[Samsung Galaxy Nexus] sway40:
I said I was on nightly 116 if you would've read, that's where the issue began. If your on m2 then you prolly won't see an issue if it is the kernel. I didn't do anything else other than flash the kernel, so it couldn't have been anything else. No undervolting or overclocking at all.

~Sent from my GNexus running Aokp~
[Samsung Galaxy Nexus] axne1:
Did you update the rom 4.0.4 aokp?
[Samsung Galaxy Nexus] phydo:
Hey Francisco, I just wanted to let you know, the latest r116 has some sort of Bluetooth pairing issue I think. I never changed cm nightlies, and never had a problem. In my car music would play but voice came through handset. Tried switching settings and stuff. Next time in the car neither played. So I unpaired and repaired. It worked, but next time in the car it dropped. Now its hit or miss. Should be the kernel I'd believe. No log cats sorry :(
[Samsung Galaxy Nexus] sway40:
Of course I've been on it with random reboots after several fresh installs, so I fig id try the new kernel since it was for 4.0.4 and that's when it melted my hand. Like I said I've never had a heat issue until that kernel, even my new ringke slim case was on fire... it was mainly hot from the screen though on the top left

~Sent from my GNexus running Aokp~
[Samsung Galaxy Nexus] masri1987:
Is francoturtle back?
[Samsung Galaxy Nexus] Aerocaptain:
Nope. But still working beautifully.

Sent from GNexus w/CM-9 & franco.kernel
[Samsung Galaxy Nexus] mike216:
Thanks bud,is this 4.03 or 04? Thinking of trying but using codename and still on 4.03?
[Samsung Galaxy Nexus] zeke1988:
all android are like that, my friend's old droid, my htc and GN, after a little use, it became hot to touch.
[Samsung Galaxy Nexus] sway40:
Once again it wasn't just hot, it was ****ing cooking. I know what hot is this isn't my first android phone, im like a cheap hooker I've been around. This was unsafely hot, so since this topic is going nowhere people can stop posting on "the phone is suppose to be warm" bc it's not and never has been that hot. It was so hot my phone rebooted so obviously it's NOT suppose to be that hot.

~Sent from my GNexus running Aokp~
[Samsung Galaxy Nexus] axne1:
Look I know what you mean man we both been on the same forums for a while now. I don't know what's happening because r116 is working for my wife and me. Gpu 384/ odd. I don't know all I can say is try to talk to franco, and see if you get help. Sorry about your troubles man.
[Samsung Galaxy Nexus] formula84:
Ditto, I am running 116, with aokp 29, 384 gpu and it is flawless and running cool. Maybe it's your phone man.
[Samsung Galaxy Nexus] sway40:
Idk but it started giving me random reboots again so hot or not I had to go back to m2 and aokp b28 so it's all good. The rom was the reason for the reboots maybe it heated the phone too hell idk. I'll wait for more stable aokp 4.0.4 rom. I appreciate the thoughts, just got annoyed at some comments saying it's supposed to be hot.

~Sent from my GNexus running Aokp~
[Samsung Galaxy Nexus] ArtnerC:
feedback on r116 + AOKPb29:

This is running amazingly. Further, all I changed was kernels going from stock to faux-m14 to franco-r116. On the previous kernels I had kernel using significant battery and kworkers everywhere though nothing indicating why. Now, kworkers seem to be gone and kernel battery use is significantly down.

I am at 16hours on battery with exactly 1 hour screen on and have 70% battery remaining. This is running at 512-700/1300-hotplug no power saver or weird settings changers, mostly wifi but some 3g, stock battery. With long periods of use over several minutes the top/back gets a little warm but otherwise is cool, though this is nothing new to this kernel version for me.

Very very pleased. I haven't felt this way for any kernel since the early days of this kernel on GNex.
[Samsung Galaxy Nexus] mike216:
I don't want to get roasted for asking this but I'm running the current 116 and was wondering if the gpu is 384 or 512? Any help would be appreciated

Nevermind I see now how to find the 384 version
[Samsung Galaxy Nexus] mike216:
Running on codename which is still 4.0.3 and 116 is running great. I like the 384 version because a big wuss and don't want to fry my phone, not to say that 512 will but I just don't know any negative or beneficially reasons so I just stick with 384.

Anyways thanks Franco once again for pure speed and will report on battery after a few charge cycles!
[Samsung Galaxy Nexus] mike216:
Haven't done a whole lot of battery testing but so far batterys idle time is extremely good and I'm loosing with screen on like I was on M2. 116 feels perfect like M2 but just a little quicker. Running 384 version

Also Android OS is lower then M2
[Samsung Galaxy Nexus] AcE XBOX:
r116 ran line absolute shiiiiit. It rebooted like 20 times. Lost the bottom buttons this morning. Whenever I would switch pages this weird pixelation kept popping up all over the screen like when you overclock a gpu and it is just too much for it to handle. I hit reboot and it was stuck on the google screen for a while. Had to pull the battery let it go through it's reboot process again before the phone came back on and I could reinstall milestone. Way too unstable for me.
[Samsung Galaxy Nexus] laureanop:
What a different range of experiences with 116! My wife's , my brother's and mine run flawlessly with 116 and liquid 1.25

"the relentless pursuit of the perfect rom" now on the gnex
[Samsung Galaxy Nexus] mike216:
maybe try the 384 version if you haven't already and I hope your not on that one aokp build that many,many have complained about.

Please list the rom when reporting problems!

Day 2 and battery life along with speed and stability are insane! May overtake M2 Franco!
[Samsung Galaxy Nexus] Flip35:
Thanx for the info cuz I'm getting ready to flash liquid.25 and I downloaded 116 hoping it works smooth with it, I'm just waiting for jays theme to finish to get going
[Samsung Galaxy Nexus] mike216:
I'm on a 4.0.3 codename build that was suggested not to run on for optimal performance and its running flawlessly
[Samsung Galaxy Nexus] laureanop:
I've tried both m2 and 116 and they both run great. But 116 with the 4.0.4 merge is a match made in heaven for liquid 1.25

"the relentless pursuit of the perfect rom" now on the gnex
[Samsung Galaxy Nexus] axne1:
I'm on aokp b29, Franco 116/384 gpu. :)

My wife and I both have the same setup. Reporting no problem at all Bravo Franco! My device made in Korea, My wife's China Made.

Update I reverted back to M2. Because of some freezing issues. On both mine and my wife's Galaxy Nexus. :o
[Samsung Galaxy Nexus] mike216:
I couldn't agree with you more!
[Samsung Galaxy Nexus] ibe2fly:
flashed r116/384 and gummy 0.9.5.testbuild2 about an hour ago ... running sweet no issues
[Samsung Galaxy Nexus] mike216:
I wonder what rom Franco runs?
[Samsung Galaxy Nexus] mild7intl:
Gotta second that ..

Liquid 1.25 and 116 go well together

Faux has a beta up and its running smooth too. If anything its probably from related issues when it comes to overheating. Did u turn off sr in Francisco app?
[Samsung Galaxy Nexus] mike216:
Interactive is also extremely responsive on this great test build! Don't know which one I like most between conservative ondemand or interactive
[Samsung Galaxy Nexus] laureanop:
What's sr ?

"the relentless pursuit of the perfect rom" now on the gnex
[Samsung Galaxy Nexus] mike216:
smartreflex in fracnos app
[Samsung Galaxy Nexus] laureanop:
Oh ! No I use it. And then I set the voltages within 25 of the calibrated ones

"the relentless pursuit of the perfect rom" now on the gnex
[Samsung Galaxy Nexus] mike216:
Me to ;) just letting you know what he or she meant by SR

I'm not sure on the whole UV thing I feel I get about the same battery no matter if I UV or not. Maybe its minimal and I just don't notice it?
[Samsung Galaxy Nexus] laureanop:
I'm not sure either. While we're on the subject one of the changes that 4.0.4 was supposed to bring was a lowered android os battery consumption and boy they delivered ! Mine went down from 20-40 to 2-10 percent with the same usage as before. I wonder if the changes are in the kernel or the rom code.

"the relentless pursuit of the perfect rom" now on the gnex
[Samsung Galaxy Nexus] Gahh Its Lee:
The effect is extremely minimal even if you under volt over 300 for every speed you'll only save about 2% battery.
[Samsung Galaxy Nexus] JOrtenzi:
Hi everyone. I'm on b29 running lean kernel. Have heard great things about M2 so I decided to flash. However, after flashing, I was stuck on the Google boot screen. After 10 minutes, had to battery pull and reflash lean kernel to get my phone to boot up again. Any thoughts to why? Any info/help would be greatly appreciated!
[Samsung Galaxy Nexus] axne1:
That was a bug fix that was applied to 4.0.4 :)
[Samsung Galaxy Nexus] JOrtenzi:
Was that a reply to me? If so... I'm not sure I understand what you're telling me. Thanks!
[Samsung Galaxy Nexus] axne1:
No not you man.
[Samsung Galaxy Nexus] Aerocaptain:
Did you wipe cache & dalvik? B29 is AOKP if I'm not mistaken right? Which GPU did you use?

Sent from GNexus w/CM-9 & franco.kernel
[Samsung Galaxy Nexus] JOrtenzi:
B29 is 4.0.4... I know others are using this ROM/kernel combo. Not sure what the issue is
[Samsung Galaxy Nexus] Aerocaptain:
The only 2 areas I've seen that tends to give a boot loop is if cache and dalvik are not wiped before flashing a new kernel or you installed the higher clocked gpu and your device for whatever reason can't handle it. The other ways that don't seem to apply to you is applying the kernel to 4.02 or lower rom, and under volting......I'd make sure your AOKP Rom doesn't have any kernel mods set at boot before attempting to flash.

Sent from GNexus w/CM-9 & franco.kernel
[Samsung Galaxy Nexus] JOrtenzi:
Aha... I think that was it. I erased my boot settings from my previous kernel and M2 flashed just fine... thanks!

Another question though. Still new with my GN. Does Andriod "update" after flashing a kernel or rom? It always says "optimizing applications". This never happened with my Fascinate or Charge... so I am guessing this is Nexus specific?
[Samsung Galaxy Nexus] laureanop:
Yeah download the 384 version

"the relentless pursuit of the perfect rom"
[Samsung Galaxy Nexus] mike216:
Also on this I couldn't agree more. But it has to be in the kernel code because I'm on codename which is 4.0.3
[Samsung Galaxy Nexus] Aerocaptain:
I believe it to be an ICS thing. It will happen when you flash anything that effects the apps directly. Usually a Rom, kernel, or if cache is wiped.....glad your able to enjoy all that is Franco.kernel. If you like it, which I'm sure you will, definitely purchase Franco's app on the market. He implemented some awesome features on it! Definitely recommend.

Sent from GNexus w/CM-9 & franco.kernel
[Samsung Galaxy Nexus] kingoanklebreakn:
It's ICS specific. My tablet does it also.
[Samsung Galaxy Nexus] bengals1975:
I think prior android versions did this as well, it just happened in the background while the boot animation was on screen. This is why it would take longer to boot after you wiped Dalvik and Cache. Now the boot animiation runs mostly the normal time and this new screen pops up and shows you the progress of the system rebuilding it's Dalvik cache. i like this design better.
[Samsung Galaxy Nexus] TEK112:
^ This....
[Samsung Galaxy Nexus] mike216:
Anytime the dalvik cache is wiped it will zip align on reboot
[Samsung Galaxy Nexus] andrew53517:
You know, I go to bed with this crazy amount of battery left... what about adding higher clock speeds (1.5? 1.6?) to waste a little of it ;-)

Galaxy Nexus & ASUS Transformer Rooted!
[Samsung Galaxy Nexus] sway40:
Ok for anyone who cares im back on aokp 29 and 116 nightly...but 384 gpu which I was in the higher one before. I think that could've been the prob with heat issue, as soon as I flashed everything fresh it got warm but not crazy hot. While setting up I got a random reboot, but after about 6hrs haven't got another since so let's see.

Every since I've tried aokp 29 I've gotten random reboots even going back to stable version and fresh install of stable version which is weird. I can't stand being behind on updated roms and kernels so im trying the rom and kernel again.
[Samsung Galaxy Nexus] franciscofranco:
r121:

* Updated the ramdisk to 4.0.4 to prevent bugs (I forgot to do this on r116)

* Kanged Simple IO scheduler from Imoseyon's repo - this should perform faster than Noop or Deadline

* Added back Hotplug mod, but now it's renamed to Generic Hotplug - this IS NOT TO BE USED WITH HOTPLUG GOVERNOR. It's now more robust too. This is the new path: /sys/module/omap2plus_cpufreq/parameters/generic_hotplug

* Weird media scanner wakelock is now 100% fixed

* Two patches from Ezekeel for his mods

* Some one or two extra fixes

App 3.9:

* Reworked settings panel for a better organization

* Changed "Turn CPU1 on", "Turn CPU1 off" from CheckBox to a PreferenceScreen and labeled them differently for a better understanding

* "Hotplug mod" option is renamed to "Generic Hotplug" to match the latest hotplug implementation in the nightly branch

* Changed Sound Volume boost from EditText to a ListPreference for better usability

* Some bug fixing
[Samsung Galaxy Nexus] Zacisblack:
Thanks man. Any idea if the patches for his sound mod included loud noise emitting from headphones related to data usage?
[Samsung Galaxy Nexus] EniGmA1987:
Did the dev do significant modifications to SIO scheduler? Becuase if not, then Simple IO is most definitely NOT faster than noop or deadline. Testing has shown it to be the least performing of the 3.
[Samsung Galaxy Nexus] JayDaKissEP:
What's the best governor for battery on this? Would it be conservative and even better with the hotplug mod enabled?
[Samsung Galaxy Nexus] zeke1988:
i run miui with this kernel, interactive doesnt want to play nice on it. so, i have to use conservative 700min with hotplug and SQlite and logger off. i can survive my daily use with just 2 or 3 charges.
[Samsung Galaxy Nexus] andrew53517:
Is there really any benefit to sqlite on?

Galaxy Nexus & ASUS Transformer Rooted!
[Samsung Galaxy Nexus] pluto22:
I asked the same awhile back. I tried both that and the logger and didn't notice any difference so I turned them off. I'd love to know other peoples experience/test results.
[Samsung Galaxy Nexus] Kancerstick:
i would love to know as well!