yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] yellowdie:
High Performance Sound was written into the the kernel since r292. Franco rewrote it all just for us. :)

Well, sure enough. 7.1.1's not sticking Gov settings for me either.... :/ (And yeah, I've got the Box of Busyness) But so far, no FCs of any type. And the Scheduler sticks just fine for me.

Leave SR enabled and don't UV anything except for 192MHz. That is the only thing that's worth it. Try setting it to the mid 700s (eg 730). Then leave everything else stock and SR will take care of it all.

Very nice. :) I love that you put the gov settings in your signature, that's hilarious.

This is for everyone: If you want to share your Gov shorthand settings, it's not gonna make sense to anyone who's not up-to-date here (because osm0sis and I made it up, lol). So if you list it anywhere, you should hyperlink it to this link/post: http://xdaforums.com/showthread.php?p=33161912
[Samsung Galaxy Nexus] gaich:
It`s possible with Nova launcher-read this.:D
[Samsung Galaxy Nexus] Fenvarien:
+1

192MHz works perfectly, I use 730mv, but that's of course device specific.

GNex with franco.Kernel / MiNCO ROM
[Samsung Galaxy Nexus] Hans QC:
Why not have a textbox in Franco's app to enter the parameters in this same format? It would make tweaking these settings a bit faster.
[Samsung Galaxy Nexus] yellowdie:
That's Boss Man's call. Sounds like a lot of work on his part to save people like 1 second. The shorthand is easy to remember because it is just top to bottom in Franco's app. :) I would just bookmark that link for future reference if you ever need a refresher. :)
[Samsung Galaxy Nexus] franciscofranco:
You seem to forget I have tons of users that don't read this thread, they don't know whats X/Z/X/Y.
[Samsung Galaxy Nexus] reflexr:
Currently I am running 192 MHz at 730 Mz at CPU undervolt.

Do I have to disable the Core smartreflex?

Actually it shows 950 Mv

This are my current settings

Device: Galaxy Nexus

Kernel: 3.0.47-franco.Kernel-nightly-384GPU#295

Max Frequency: 1036 MHz

Min Frequency: 192 MHz

Governor: interactive

Io: deadline

Screen Off Max Frequency: 192 Mhz

Color Multipliers: 1350000000 1350000000 1900000000

RGB Gamma: -4 0 5

Thanks guys

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] yellowdie:
No, leave SR enabled. SR only goes to 830mV, so when you UV below 830 then it automatically disabled SR for that single speed (192). Also, I would turn your max screen off to 384. :)
[Samsung Galaxy Nexus] Leegalaxy:
I am running that exact setup and am having zero trouble with the latest r295 kernel or the Franco App. In fact, the setup is perfect. Great battery life so far and very smooth.
[Samsung Galaxy Nexus] yellowdie:
Off topic: Oh snap! MiNCO v5 just came out last night! I think I need to give it a try for the first time. :D

On topic: Franco, really random thought. This is a very minor request and I only bring it up because you asked for input on possible upgrades and stuff. I don't know if this is even possible, but is there a way for me/us to set a certain tab in your app as the default open tab? I would love if the app launched straight to the OC or Settings tab instead of having to scroll past four other pages to get to it every time. Thoughts? And just out of curiosity, what made you add a tab to install Imoseyon's Lean kernel? Did you partner with him in the past? Just curious. :D
[Samsung Galaxy Nexus] franciscofranco:
I don't know if that is possible, but I can take a looksie. I just asked him if he wanted me to host his kernels on my app because some users asked me to, and I did.
[Samsung Galaxy Nexus] chugger93:
So I'm still on m6, haven't followed this thread in a good week...really busy. Any good reason to toto 295 nightly? Thanks dudes
[Samsung Galaxy Nexus] yellowdie:
Cool. Thanks!

Sure is!! r295 destroys every other version of every other kernel that has ever been created before in any phone ever. Ever. :) Start here. :highfive:
[Samsung Galaxy Nexus] fredryk:
What is the reason for the default color values in this kernel? Is it supposed to prevent screen burn or something by having the colors be duller?
[Samsung Galaxy Nexus] Hans QC:
It was just an idea, no problem.

We could really go over the top and make QR-codes with all your app's settings :laugh: (just joking!)
[Samsung Galaxy Nexus] joeyfong:
7.1.2 is running
[Samsung Galaxy Nexus] a5pe4:
Was going to switch to trinity after only getting 2.5 hours screen on time yesterday. Words with friends wouldn't work on trinity so I came back to Franco and got my first 4 hour screen on time since before I was rooted. I'm still jealous of some of the battery life others have but this makes me feel better.
[Samsung Galaxy Nexus] franciscofranco:
4h screen on time is way above the average, so consider yourself lucky :)
[Samsung Galaxy Nexus] Timmyfoxeh:
Now for the inevitable question on the IO Schedulers, now that that app has the ability to choose which to use..

Deadline or BFQ?

What are the pros and cons of each and how do they work?

Could they be compared to CPU governors?
[Samsung Galaxy Nexus] reflexr:
I'm using this link there's a good explanation for every scheduler,

http://xdaforums.com/showthread.php?t=1631894

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] venividivici87:
IMHO

i've noticed with Deadline more smooth and less lag and Antutu score are bigger. So i finally switch to it.
[Samsung Galaxy Nexus] fredryk:
Anyone?
[Samsung Galaxy Nexus] b1337:
You need new eyeballs gramps! ;)
[Samsung Galaxy Nexus] yellowdie:
That's how Boss Man likes his to look. Therefore, it's default.
[Samsung Galaxy Nexus] zephiK:
Very impressive new build able to run at 192 including screen off and idle battery time is simply amazing, it doesn't drop.
[Samsung Galaxy Nexus] franciscofranco:
I slept for 9 hours tonight and I had 0% drain on idle, can't complain eheh

Btw 7.1.2 app is out, should fix some little bugs specially when restoring saved settings on boot.
[Samsung Galaxy Nexus] usmankh10:
Was ur battery fully charged??cuz it dont drop that quickly from 100% in idle
[Samsung Galaxy Nexus] strifej:
Can you explain your governor control? It's Interactive? I can guess the IB and HF, but what are the other numbers? Thanks

I'm using Wheatly since Franco was using that a few months back, and haven't switched since.

Anyone want to share their undervolt settings up to 1528?
[Samsung Galaxy Nexus] franciscofranco:
No, it was on 87% all night.
[Samsung Galaxy Nexus] Shadow-Nexus:
Really how did you do it?
[Samsung Galaxy Nexus] dandyqb:
tried the r295 for several days with 4.1.2 deodexed of bigxie before switching to minco v5 this morning... :) no problem encountered, but i dont see any change in smoothness compared with 4.1.1 :)
[Samsung Galaxy Nexus] BigBake88:
I'm going to guess Franco is going to say something to the extent of "I don't have any **** apps" LOL :p
[Samsung Galaxy Nexus] chugger93:
My max freq for screen off wont let me change to 192. Any reason for that?
[Samsung Galaxy Nexus] Shadow-Nexus:
I tried setting my phone on lazy governor with 192 for min and 384 for max with 192 max on screen off when I went to sleep but after like an hour it rebooted itself so then I set it to the same setting but now it was on interactive governor and it drained like 10 % overnight
[Samsung Galaxy Nexus] minooch:
UH, It looks like your email (exchange) is syncing & keeping it awake - try disabling that for a day (when not needed) & see if that helps
[Samsung Galaxy Nexus] ScottRTL:
Thanks again for the kernel.

Question:

I am using an app called Notify My Android, and basically it pushes growl notifications from a computer in your home network to your phone.

The app is working kinda. (When I open it, it synchronizes and I can see all my push notifications. But it will not sync unless I go into the app itself. Therefore, I won't get the notifications.

I am running nightly 11 on AOKP Milestone 1 (with no power save settings enabled)

Is there a possibility that there is something in the kernel preventing this? Or should I look at a different ROM?

I don't think anyone has asked this yet...

Thanks.
[Samsung Galaxy Nexus] ro_explorer:
Guys ... I need a little help confirming the GPU OC pushing the device to its limits.

Please, some gamers there, try and play a heavy 3D rendering game for a little longer than 30-45 minutes. Please see if the phone gets REALLY hot, please note the battery drain and also if the phone is rebooting/getting laggy .. anything that you may find of interest.

I've just did some extensive GPU test (read played like crazy GLWG :) ) ... and I already have my own conclusions (which I already shared with Franco). I only need a confirmation this is not just my phone (or maybe is).

The fact is that a GPU running that hot that is triggering the reboot of the phone is not an issue of stability but more like an issue of device life. So, using the aggressive OC on the GPU might result in bricked devices ... that why I think this is important.

As an example: OC GPU is drainign like 30% per hour while stock clock GPU is resulting in 20% per hour drain (this is while playing GLWG). This 0.6-0.7W difference (2W total power with OC GPU compared with 1.3W total power with the stock clock GPU) is a huge power drain caused by the GPU ...
[Samsung Galaxy Nexus] mfish123:
Thanks for the tip. I'm in the office most of the day so I don't really need to sync that frequently. I disabled exchange push to cut down on its wakelocks but do have it set to sync every 15 minutes. I'll see what happens if I disable it or stretch the sync out to an hour which is the most infrequent I can go in the settings. Also, I had it syncing 1 month worth of emails. I'm going to cut that down to 1 day too.
[Samsung Galaxy Nexus] minooch:
I'll give it run tonight (at work at the moment)

If you've got some time to test - try using the stock kernel (I know it sucks) & see if you get the reboot with that.
[Samsung Galaxy Nexus] ro_explorer:
I already tested exactly the same kernel (Franco's nightly #11) but with the GPU OC disabled and the reboots are gone, and also the hot device is gone ... now is just getting warm. So I already have very conclusive test results.

I just need to confirm this is not related strictly to my phone because, as we all know, some CPUs/GPUs can handle OC better than others. If the problem is localized on my phone (or a small number of devices) then a small warning on the OP should warn users that the specific OC GPU might not work all the times in their devices. If the problem is more general, then I guess the OC should be reduced or at least the code reviewed.

That's the purpose of a nightly after all - to test stuff :).
[Samsung Galaxy Nexus] samizad:
Francisco, just to let you know that CPU Spy shows my phone entering deep sleep fine, even if I do not open/close the camera on a fresh reboot.

I will stop doing the open/close camera action until this potential bug becomes confirmed.
[Samsung Galaxy Nexus] franciscofranco:
Yes. If it works fine for you then awesome. I just wrote it there as a potential warning ;)
[Samsung Galaxy Nexus] Thracks:
I too am trying to figure out why I can occasionally get long stretches of time where I drain at 2mA, and the rest of the time is spent at 13-40mA.
[Samsung Galaxy Nexus] franciscofranco:
Something wakes up and stays there woken? I had 0% drain last night for 9hours.
[Samsung Galaxy Nexus] chakra:
Franco, do you use the hotplug option yourself? Sorry if that has been asked.
[Samsung Galaxy Nexus] minooch:
It might also be a voltage regulator that Francisco back-ported from 3.2 (from imoseyon). It would make more sense that this is causing the reboots as it was only just implemented, and the reboots have only just started to popup - but we'll see when Francisco has some time :D
[Samsung Galaxy Nexus] ro_explorer:
Such high temperature is only possible with overclock or high voltage. I don't know what Franco did in the kernel but sometimes I can see the effects.(most of them being good ones, of course).

// sent from my green robot //
[Samsung Galaxy Nexus] chakra:
Last night I had some very high temps. I was doing some downloading and the thing was super hot. I pulled the battery and let it sit for a few. But who knows what it was. I am not blaiming Francos kernal, just giving my 2 cents.
[Samsung Galaxy Nexus] minooch:
With the temps it's fairly obvious the OC is the culprit (so long as it's within the GPU's thermal limits, it's no prob) - but the reboot not so clear - if the voltage being supplied is too low, you will get a possible reboot.
[Samsung Galaxy Nexus] Thracks:
No, that's not it. BetterBatteryStats is coming up clean, and CPU Spy is reporting deep sleep. This has been baffling me for days.

//edit:

CPU Spy: http://i.imgur.com/j59Nr.jpg

Better Battery Stats: http://i.imgur.com/rwVSK.jpg

Battery Log: http://dl.dropbox.com/u/10780260/battery_history.txt

Interestingly, Android OS is reporting very high utilization versus phone idle. It's the #1 consumer with 45 minutes of awake time.

The rabbit hole goes deeper, I guess. Looks like I have this problem: http://xdaforums.com/showthread.php?t=1387243
[Samsung Galaxy Nexus] triStateMindgate:
Not that much use, 2hrs screen, music during commute, sms, maps, little web browsing, some youtube, few emails through out the day....

For me, that's amazing so far.
[Samsung Galaxy Nexus] afzalarsalan:
Could you mind porting some of these features to the nexus s? :o
[Samsung Galaxy Nexus] franciscofranco:
Careful, deep sleep isn't idle. If Android OS is high then I'm 99,9% it's an app holding a wakelock somewhere.
[Samsung Galaxy Nexus] osm0sis:
I'm guessing it's lower than your global min? Either way, don't set it that low. 729 is where it should stay. Search the thread for race-to-idle. :)

I'm still running into some issues with settings staying with 7.1.2, now with my CPU settings. Never had any issues with this since switching to SuperSU ages ago until 7.1.1. Currently trying a full kernel clean flash and app reinstall and cache/dalvik wipe.
[Samsung Galaxy Nexus] BigBake88:
Hmm, maybe your phone doesn't like 192 min which is why you most likely got a reboot, and that probably cost you 3% battery drain on the reboot. Honestly, setting max screen off at 192 min may actually cost more battery as well, since the phone needs to stay awake longer to finish any tasks it may have running in the background. I think 729 is a nice happy medium since it gets back to deep sleep faster. And of course, drain is contributed to a lot of different factors as well (ROM, signal, apps running in background, sync, etc.)
[Samsung Galaxy Nexus] ÜBER™:
:confused: deep slept but shows it was awake? Makes no sense.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] yellowdie:
Well that's...odd... :confused: lol
[Samsung Galaxy Nexus] franciscofranco:
No bull**** apps running on my device.
[Samsung Galaxy Nexus] yellowdie:
I'm the same. I run only the bare minimum that I need. Even apps like Busybox, I reinstall when I need them, then uninstall again. Don't like junk running without me running it. :)
[Samsung Galaxy Nexus] osm0sis:
Okay now all appear to stay except above_hispeed_delay and go_hispeed_load. Some weird **** going on since 7.1.1 :(

They were even reverting back to 100000 and 50 at one point.

Tapping the RGB gamma sliders after a boot seems to reset them as well, even though their values don't visibly change in the app. Did franco make the app haunted for Halloween!? :p
[Samsung Galaxy Nexus] A.C.Sanchez:
Is that as simple as saying no Facebook notifications, Plume pushing of data (Twitter), etc... or is there more to it than that?

I literally can not comprehend how you guys get 3+ hours of screen time. I'm lucky to get 2.

Standard battery

295

192 min at 750

no other material changes, but I do have Friendcaster and Plume set to provide updates, and I leave bluetooth and GPS on. I realize those are clearly the reasons I'm seeing differences - but NONE of you guys with the insane screen on times use BT/GPS/Push Notifications?

Either way, this thread is amazing and I'm glad I took the time to read the past 25 pages. :D
[Samsung Galaxy Nexus] The Gingerbread Man:
I'm not entirely sure if its me or not but thought I'd leave it a little time before saying anything but since the fix for sound I'm not entirely sure if music sounds quite as good as before when high performance mode was able to be enabled. I mean only about music over my headphones here, its great now calls can be heard properly. What's peoples feelings on this?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] androidkid311:
Using the latest nightly but I can definitely say the WiFi signal is very weak. Any suggestions on how to improve it??
[Samsung Galaxy Nexus] whitedragonz83:
I recently wanted to try Franco after using Trinity Kernel for awhile. Is there any reason I would see my download speeds drop off signification going from Trinity to Franco? A co-worker using T-Mobile as well with the same plan I have did a check at the same time of his speeds and found no changes, but I went from ~8Mbps to ~1.5-2Mbps and occasionally really bad pings (1800+).
[Samsung Galaxy Nexus] reflexr:
My wifi is good. No problems here

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] yellowdie:
Did you install Busybox?!?!?!?!? :p:silly: jk jk.

Mine are sticking and my gamma's are there (but those apply from my init.d). But it would be really funny if he did a Halloween prank like that. lol

Yep, that's a big killer there. I very rarely use GPS and it's only on while I'm actively using Maps, then it goes right off. And BT is never on. The only push I have is my gmail. FB app has never been installed on my phone. GSM phone on stock battery. :) Also, what brightness are you using? Autobrightness will kill your battery faster because it's constantly active to check your surroundings. I usually run about 50%(sometimes 25%, sometimes 100%, just depends).

---------- Post added at 01:31 PM ---------- Previous post was at 01:28 PM ----------

I don't think Boss Man changed anything in the wifi. As far as I know, it's still stock. But mine is fine. (yes, I got much stronger signal with the wep-less drivers, but we've been there, so I'm not gonna beat a dead horse, lol)

I would try reflashing the kernel again, and then reflash your radio and ril. Also, did you change the TCP settings? Trinity uses Veno by default. Take a look at the second post in this thread of info on that. :)
[Samsung Galaxy Nexus] BigBake88:
Lol Franco do I win a prize for knowing what you were going to say??? Haha
[Samsung Galaxy Nexus] Blackcrx:
I had this problem initially also. Are you opening the app right after boot up?

I noticed that if I opened the app right after boot up it would show 10/5, but if I closed the app and checked back in 30 seconds or so it would show as 6/7 like it is suppose to

I also had enabled the boot CPU and governor settings
[Samsung Galaxy Nexus] whitedragonz83:
I rebooted the phone and my d/l speeds went up to ~6Mbps so better. Changed to Veno from Cubic, tried Westwood too, roughly the same d/l speeds. Changed from UGLH1->XXLF1, no noticeable difference and then back to UGLH1. Still around the same d/l speed. I will try a speed test early in the morning tomorrow at work, maybe the difference is just the time of day at this point. I don't know why else it would be lower on Franco's vs Trinity's Kernel.

Also I did reflash RasBean when I started testing Franco's.
[Samsung Galaxy Nexus] fleischbanane:
Normal day with normal use on r295 and CM10 Nightly 2012.10.24.
[Samsung Galaxy Nexus] Schneewitzchen:
As yellowdie i go with his meaning about

Bluetooth and GPS! This drains battery very quickly!

For me auto brightness is on all the time and look at my stats-->

View attachment 1430460

View attachment 1430461

So i don't agree with yellowdie that this has so much effect on battery drain.
[Samsung Galaxy Nexus] fleischbanane:
Normal day with normal use on r295 and CM10 Nightly 2012.10.24. Interactive 384 - 1228.
[Samsung Galaxy Nexus] nuwan32:
Well I get average 4+ hours now and I have Facebook, Gmail, whatsapp on sync and data on all day. The biggest contributor I found to battery was switching to inverted apps. Literally gave me twice the battery and running 192 - 729 was the cherry on top :D

I only ever turn on Bluetooth and GPS when I use it, same with Google location services, or else maps will run in the background and it drains the battery a LOT.
[Samsung Galaxy Nexus] amf100:
I suggest an app called Autostarts. It has worked perfectly for me for several years now across multiple phones. There may be other rom multi-feature apps that allow you to control when an app can be started, but this one has never failed me, so I've never tried any others. You just have to be careful about which system apps or services you disable of course.
[Samsung Galaxy Nexus] yellowdie:
I tried Autostarts and a few others but settled on Startup Manager awhile ago. It's works well for me to stop apps. But when it comes to system apps, I uninstall everything that I don't use. And by uninstall, I mean I delete the actual apks from the .zip of every single ROM that I install before I install the ROM. I usually trim at least 30-50MB out of a ROM before I even transfer it to my phone. :) I like having control of my technology. :laugh: lol

Edit: I'm out of Thanks for the day, but I'll try to remember to hit you up tomorrow. :)
[Samsung Galaxy Nexus] supernova_00:
I've seen that a few times in the past few days, drove me crazy trying to figure out what was causing wakelocks but nothing was reported in BBS and another battery monitoring program. I came to the conclusion that Android was just lying to me.

EDIT: I've also noticed (at different times) a program using some battery life when I didn't start them, autostarts blocks them from starting, and they don't use the internet. GSAM or whatever battery monitor said that "orientation" was using the battery for those programs. BBS had no mention of those programs running but Android's battery stats said they had as well.
[Samsung Galaxy Nexus] osm0sis:
Yeah I don't know, I took all my init.d stuff out to see what exactly wasn't sticking. Maybe you could do the same to see if you can reproduce any of it?

The issues I'm seeing:

- CPU max/min were not sticking on boot with a fresh install. Setting it again after the first boot seems to have stuck it.

- Governor tunables do not entirely stick. In 7.1.1 none of them stuck, in 7.1.2 above_hispeed_delay, go_hispeed_load, and timer_rate seem to be the only ones that don't.

- On a fresh install if checked directly after a boot you'll see 100k/50/60k/20k, but then seem to switch to the new defaults about 15 seconds in.

- Custom settings will also show correctly directly after the install, but then similarly revert to the new defaults of 6/7/6/3.

So far, I've:

- cleared data+cache on the app

- removed the /data/data/com.franco.Kernel folder

- reinstalled the app

- returned to stock kernel, ran the GLaDOS cleaner script and reflashed the franco.Kernel from both the app and using the recovery flashable zip

- formatted cache and wiped dalvik-cache

- gave franco.Kernel fresh permissions in SuperSU

- reinstalled BusyBox

Nothing fixed it, and obviously the only thing that changed between everything working fine for months and months and then suddenly not was updating the app, so that's the culprit here even if I am somehow an edge case. Would a logcat help, Franco?
[Samsung Galaxy Nexus] yellowdie:
That's just disgusting. :D lol

Maps. Do you actively use Maps a lot? If not turn off the everything under Location Services and that will shut Maps up. Then just turn on GPS if you need it.