yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Fenvarien:
R345 is running rockstable here using osm0sis UV settings. Stock ROM 4.2.1, no SODs or other hiccups. Great work Franco! :)
[Samsung Galaxy Nexus] alangrig:
R345 is great. All: GPS, WiFi, data, synch, NFC, Google now is being enabled.

View attachment 1570158

View attachment 1570167View attachment 1570169
[Samsung Galaxy Nexus] chickentuna:
I did. Set your Minimum CPU frequency to 192mhz first and set max screen off to 192. If you ask me, it didn't really make any difference battery wise. Maybe a little but far too little for it to be noticed. What's noticeable is that there was a delay which was pretty annoying when waking up the phone :p

I've ran it for a day and reverted back to default as I would rather have my device running smooth than having some hiccups here and there. What I did above was pointless as It didn't save battery that much, I did it for testing purposes, you are welcome to try though just giving my feedbacks
[Samsung Galaxy Nexus] Khrushy:
Setting screen off max to 192 is probably bad for your battery life actually - your phone will spend more time awake doing tasks at 192Mhz, rather than finishing tasks quickly at 729 (or 542, whatever you choose) and going back into the super-efficient deep-sleep.

And yeah, unforetunately, 192 min definitely shows noticeable lags, which IMO, no amount of battery life is worth :P
[Samsung Galaxy Nexus] The Gingerbread Man:
Charging your phone at night will prevent SOD

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] chickentuna:
yeah everything you said was correct and I still did it knowing those facts lol. I experimented and I wanted to prove to myself that lower clock speed doesn't always really mean saving more battery
[Samsung Galaxy Nexus] kCelsius:
Never knew this - good to find this out....so what would be a good min freq? Is 384 still too low? Do most use 537?

So would something with a 537 min freq and 537 max screen off be ideal so that it'll finish off tasks at that freq and go straight into deep sleep instead of lingering at 192?
[Samsung Galaxy Nexus] The Gingerbread Man:
It depends how you use your phone, I use xda and Google play music a lot so a high min speed would waste my battery. Tbh your best using 384 and let the phone choose what speed it needs as that will probably save more battery than sitting at 537 or higher for basic things like xda or music. I chose 192 and I find it fine without any lags.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
You misread. Screen off max = 537 since that's the sweet spot for battery life and race-to-idle. I said explicitly that when Franco adds Screen off min, that's what I'll be setting to 192. Min =/= max. ;)
[Samsung Galaxy Nexus] Khrushy:
I personally use 384 min, which is fine for music and most other tasks. In fact, 192 is fine for all those if they're just in the background, or being displayed with no input, but I noticed micro lag when I went to switch launcher screens or perform any new task - hence 384 min for me.

537 is probably overkill for min.
[Samsung Galaxy Nexus] teniente_dan:
R345 is absolutely brilliant, thanks franco ;)

Enviado desde mi Galaxy Nexus usando Tapatalk 2
[Samsung Galaxy Nexus] tobitronics:
That is exactly what I do, although I let my phone reboot every morning before i wake up, maybe thats the cause...
[Samsung Galaxy Nexus] SpecRek9:
The only thing I'd like to see enabled in r346 and that I already know Franco won't it's volume control, I jog with this device and the exterior noise is a killer.

---------- Post added at 09:04 AM ---------- Previous post was at 09:02 AM ----------

Off topic: has anyone managed to use Wi-Fi direct with this device? I've tried everything against a friend's GN and didn't succeed
[Samsung Galaxy Nexus] haxor:
Alright I setup 192 MHz min frequency and max CPU frequency for screen off is 537 MHz :D I think thats it what osmiss said !
[Samsung Galaxy Nexus] Khrushy:
I've noticed in the past that sometimes the alarms don't get turned on until you unlock the phone after a reboot.
[Samsung Galaxy Nexus] safendi:
if i set input_boost_freq to 1228 there is a problem? is better than 537?
[Samsung Galaxy Nexus] supernova_00:
Battery life is absolutly horrible for me while on WIFI ever since 342. I'm using MiNCO v6 beta 3 on toro in case that matters Franco.
[Samsung Galaxy Nexus] alex999999:
your android system is a long time awake. have you done a factory reset?

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] Khrushy:
Overkill really. Shouldn't cause a problem, but at the same time you don't really need to force your phone to clock at 1.2ghz just because you touched the screen. If you're not finding the response snappy enough when you're using your phone then you could try bumping it to 729 first, then 1ghz if it's still not enough.

Or you could just try enabling some of the higher clocks like 1400/1500mhz if you haven't already and performance is a priority for you. I'd probably suggest that rather than changing the input boost.
[Samsung Galaxy Nexus] whitedragonz83:
http://xdaforums.com/showpost.php?p=26255541&postcount=5161

Look at your data usage and see what apps are downloading massive data. You have a rogue app.
[Samsung Galaxy Nexus] safendi:
and if i setting hi_speed_freq to 1036? is not too low 729?
[Samsung Galaxy Nexus] Khrushy:
If you want to be aggressive about how quickly your governor ramps up clocks, then sure, set hi_speed to 1036 and input boost to 729.

But you'll probably not really notice much difference. The defaults do a good job, and if you're really looking for that bit of faster performance, then OC'ing the CPU a bit will bring you better results than messing with the governor (at the cost of slight battery life of course).

Edit: hold on - is input boost even supported in the current version? My f.Ku is telling me "no".
[Samsung Galaxy Nexus] safendi:
i use 342
[Samsung Galaxy Nexus] malaroth:
Not at the moment
[Samsung Galaxy Nexus] supernova_00:
yes, caused by the wifi kernel wakes

Nothing, auto starts or syncs and this was also after factory a reset with nothing installed other than franco updater and autostarts to kill crap from starting. The issue is the wifi kernel wakes for no reason at all. Weird thing about it is that same night I went to the bar and connected to their wifi and the battery life was great, at home it sucks ass.
[Samsung Galaxy Nexus] whitedragonz83:
Reset your home router and maybe unplug your modem for a minute. Then check wakelock.
[Samsung Galaxy Nexus] supernova_00:
I'll try that when I get home but what could of happened that would cause this that the modem/router (all one unit) would need rebooted?
[Samsung Galaxy Nexus] yellowdie:
Yes, Franco has Input_boost enabled at the kernel level. That's how he created Input_boost_freq as an option. :)

And yeah, the 729/537 defaults there are great, according to Franco and I; but osm0sis like to turn them up to 1036/729--just personal preference. :)
[Samsung Galaxy Nexus] duduzinho15:
1036/729 is very smooth I love this config and don't drain much battery :D
[Samsung Galaxy Nexus] whitedragonz83:
No clue, but if the bar WiFi worked and home didn't it makes sense to check. Really no idea though why.
[Samsung Galaxy Nexus] franciscofranco:
If it doesn't work correctly at your home but does on other places where do you think the problem lies?
[Samsung Galaxy Nexus] malaroth:
I think his problem might just be a very convincing liar, either that or he's not good at judging truth.:P

I also meant that the "boost" setting was greyed out in the current kernels not that you couldn't set the values.

And finally awesome job yet again Franco 345 is amazing!

JBSourcery 4.0 + r345 Franco FTW. Keep the Magic alive!
[Samsung Galaxy Nexus] Antob125:
Osm0sis do you have anytging else turned up past stock settings other than 1036/729?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] thegtfusion:
My 5 years old little sister said it lays with him :p

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] supernova_00:
Yes at first thought I would think the same thing but that is not neccesarily true. Of course I haven't proved it yet but whose to say it isn't the kernels fault with the wifi drivers that don't like 2.4 or 5 ghz frequency, the type of security, or some other setting? My point being, what exactly would rebooting my router have to do with it? What on my router could cause massive wakelocks on my phone? It doesn't make sense. My phone is the one that initiates and maintains the communication with the router not the other way around.

Also, my other point that may have been overlooked was that I'm running a test build of a ROM that Franco works on along with Franco's kernel so maybe has something to do with that. I'm not sure if there are even any other toro testers for those builds. I'm assuming it's a kernel issue though as those include the wifi drivers, hence posting here.
[Samsung Galaxy Nexus] vrehenriqu:
Olá Franco.

This kernel is great! I just want to report one thing on version 345 that is not happening on version 344: Bluetooth pairing with the car system takes a long time...

I use the lower frequency set to 192mhz. I will try 384mhz instead and report if it works better.

Note: using Xylon ROM at the moment.

Many thanks for your great work and dedication!

Bom Natal :)
[Samsung Galaxy Nexus] Empty Hand:
I'm not suggesting you're not having this issue, but just an FYI that I am not having any problem pairing bluetooth in my car with the same speeds as r344 (at least nothing I can notice).
[Samsung Galaxy Nexus] osm0sis:
I thought it was because Project Butter requires input_boost to be enabled so we don't really have the option anymore unless we want to break Project Butter. :confused:

Not in Governor Control. In general the only other thing I do is raise the max clock freq to 1536. I'll be keeping my settings post up to date, so you can always refer back to that if you want to know what I'm up to. ;)

In my experience those wifi_rx_wake locks are at some level ROM related. I had massive problems with it on yakju starting back in ICS. I could only work around it by changing the wifi sleep policy to off when in deep sleep. The thing that finally resolved it for me was when I switched to takju for JB. To do so I had backed up all my userapps+data with TiBU, then fastboot flashed system.img, and then used CWM Recovery to wipe data (but not sdcard), then I restored my userapps+data and set up the system settings from scratch. Never a problem since.

Do you dirty flash often? Try doing a clean wipe of data, since I think that was the key step in the process.
[Samsung Galaxy Nexus] sk8oldschool74:
+1
[Samsung Galaxy Nexus] osm0sis:
It's not hard to download the old versions from minooch.com/franciscofranco as linked in the OP. Put them in the kernel_backups folder on your sdcard and use f.Ku's Kernel Backup/Restore function to flash them. There doesn't need to be any more functionality for older versions added to the app since Franco has already made it simple.
[Samsung Galaxy Nexus] supernova_00:
I've had them happen a few times and if I remember correctly, the 3.4 wifi drivers were always the cause each time franco had tried using those in the kernel. He did revert to the stock ones recently correct? Yes, I did a complete wipe a day prior to those screenshots and had not "restored" all of my apps and user data at that point. I was trying out 4.2.1 without all my apps to take those out of consideration if I expierenced any problems...like I have.
[Samsung Galaxy Nexus] osm0sis:
Interesting. Then I'm definitely going to go with router/network issue. :(

No issues for me with the 3.4 drivers, and yes, we're back to stock.
[Samsung Galaxy Nexus] CaspaTheGhost:
Guys, its been epic, but a lovely little shipping email says I will be following Franco to the N4 forum in the next couple of days!

Love and respect to all that have made this the number one thread, feel free to join me in trying to make the N4 one just as epic!

R345 gets a farewell thumbs up!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] sk8oldschool74:
Calm down big guy... It wasn't an insult or lazy ness it was just an observation and on my +1 a suggestion to improve app... ;):)
[Samsung Galaxy Nexus] osm0sis:
That was calm. Just because my post doesn't have a smiley face doesn't mean I'm not calm. ;)

That feature has been requested many times before and the answer from franco was the same: No. It's easy enough as it is. :D:laugh::p:cowboy::):cool::good::highfive: :victory:
[Samsung Galaxy Nexus] irminsul:
I do not collect wake lock stats but WiFi performance can really be router related. I'm using WiFi at 3 places: at home, at my girlfriend's and at work. When I'm at home, my maguro and before crespo mostly drains 4/5% overnight. When I'm at my girlfriend's it easily drains 30% in 7, 8 hours sleep. At work my phone doesn't sleep long, not s good measure point.

I blame the router at my girlfriend's place for the drain. Cause of the drain? Never found, can't access router settings somehow. Rom related? No, 4.0, 4.1, 4.2, stock, BuglessBeast, always the same.

I just charge it, it doesn't matter to me :)
[Samsung Galaxy Nexus] supernova_00:
Exactly my point and thank you for the post. Now how do we get to the bottom of this? To begin with we need someone's input with how the type of router, security, frequency, whatever setting you can think of can cause this. I cannot believe the router needs reset every so often to fix this. There is an underlying cause somewhere and I only had it happen with the 3.4 wifi drivers and now that I'm on 4.2.1 with Franco's kernel it happens again, even though the 3.4 drivers are currently not in the kernel.
[Samsung Galaxy Nexus] nikulogical:
Anyone experience weird lag while typing on this nightly?

Sent from my Paranoid Francoid
[Samsung Galaxy Nexus] thegtfusion:
@ osm0sis

I undervolted the cpu coltages with -25mV. Its safe right? Using your settings you posted some pages ago.

Max :1536 min 384 , max screen off 537, my own voltages ( all -25mV)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
If you're only going to UV by -25mV across the board then you might as well just let SR do it's thing since you probably haven't moved m/any of them below their SR calibrated voltages. To answer your question though, it's always safe provided you've got fsync on, but it's all about what your device's silicon can handle. Every device is different. Yours might be able to handle lower voltages than mine, or it might not be able to handle them as low as my device can.

Go back to my post and follow the links for how to UV properly if you're really interested in trying, otherwise my recommendation is everyone stick with SR. :)
[Samsung Galaxy Nexus] shortbus1234:
Compatibility issue with smoothrom 4.2?

Fresh install of smoothrom for Nexus 7

http://xdaforums.com/showthread.php?p=35571011&posted=1#post35571011

Installed bricked kernel and everything was working fine.

I really like the Franco kernel so much that I bought the Franco flash app from the play store. Only problem is that when I rebooted I get hundreds of pop up windows that say com.android.com has stopped. Also NFC has stopped and I an unable to unlock device. Hopefully someone knows how to fix this.

UPDATE: Seems to be working fine with build 345. Does not seems to like latest stable build 31.
[Samsung Galaxy Nexus] Antob125:
So I used your method and ended up with the same numbers as you also! So the only thing I'm disabling is Sr, not the other 2 correct? Also with your under volt setup are you able to play games with no problem or because of the low volts there will be issues?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Sik-1:
Its safe as long as your phone can handle it
[Samsung Galaxy Nexus] osm0sis:
Someone was saying not that long ago that the "brain-damaged" borderline voltage theory wasn't true. So either it works or it crashes. As I said in my second linked post about how to UV, I always stress test the frequency at what I found at idle to be a stable voltage, just to make sure. I usually do this with games. Since all my voltages are below the SR calibrated ones, that means SR doesn't calibrate them anymore, even if SR is left enabled. So personally I just choose to leave it enabled so that Device Monitor shows the correct voltages for the frequencies (it shows 0mV with SR disabled due to a bug or something.)
[Samsung Galaxy Nexus] thegtfusion:
If my phone cant handle it it means sods and reboots?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
Usually freezes and reboots for MPU UV. SODs are more of a CORE UV issue.
[Samsung Galaxy Nexus] thegtfusion:
Ok. Im curious if i will see any battery life improvements and especially since im running on 1536 mhz :p

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
Yeah that's how I got started. ;)
[Samsung Galaxy Nexus] nikulogical:
I tested out the stock PA kernel (cfq scheduler) for a while then came back to this. I'm noticing better idle battery life but its a bit laggier or jerkier at times. I just switched the scheduler from deadline to bfq and its seems better, still need some time to test. Benchmarks were higher with bfq as well. What scheduler is everyone else using, 2 cents?

Sent from my Paranoid Francoid
[Samsung Galaxy Nexus] Antob125:
So it's ok to have SR disabled with your volts if I'm running ok or should I keep it on?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] thegtfusion:
If i undervolt, do i need to undervolt all the voltages? From 192 up to 1536? All with the same amount right. (Eg -25 for all)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Redneck Trash:
Now that I'm on 4.2.1 I flashed r345 and the first thing I noticed is my phone runs much cooler than it ever has.

Set from my toroplus
[Samsung Galaxy Nexus] osm0sis:
Like I just said in the reply you quoted, it's the same difference on or off, so of course it's okay.

Like I wrote the first time you mentioned you were only UVing by -25mV across the board: don't bother UVing if you're not going to UV at least selective frequencies properly. Please go back and read the UVing posts like I also told you to.
[Samsung Galaxy Nexus] bradm23:
Deadline seems to settle in after a little while. Im running 192 (UV to 750)-13xx, interactive, deadline. I agree with the smoothness of cfq. I mentioned it to Franco and he said it will be active in the next nightlie (if he remembers again :D) along with some other "major" mainline patches from Google
[Samsung Galaxy Nexus] franciscofranco:
Yes I already enabled it on my build.
[Samsung Galaxy Nexus] galakanokis:
Holy sh cow , idle drain is phenomenal! Losing 2.2%/hr on wifi and syncing about 7 or 8 accounts. Just under 5 hours awake with an hour of screen time and down to 90%. And smooth as glass as per usual. Currently running all Franco defaults at the moment but might play with undervolting when I get home.

It will be interesting to test out the wifi battery drain theory posted a few posts up. I pretty much have the work wifi to myself (setup my own network that I rarely let people on) but the home wifi is used pretty heavily so it will be neat to see the comparison, never really thought about it before.
[Samsung Galaxy Nexus] supernova_00:
Unplugged router, no change. Had 47% drain in 11 hours on 3G with about an hour use and 15% in about two hours on wifi with no use.
[Samsung Galaxy Nexus] bradm23:
Im curious to hear the masters opinion on it! What you think?
[Samsung Galaxy Nexus] yellowdie:
Hey Os, you should start an Undervolting tutorial/QA thread and see where it leads. ;)
[Samsung Galaxy Nexus] Khrushy:
To massive amounts of frustration? :eek:
[Samsung Galaxy Nexus] hiarc:
I had a huge wlan wakelock problem ever since recent updates. I made a nandroid and reset everything, during this time I tested to see if an app was really the problem or something else. The two things that solved it: toggling on WIFI off during sleep like osmosis stated way back, and another thing I stumbled across was enabling Wi-Fi optimization under WIFI settings. The latter cut my wakelocks back to the usual sub .25% from the 50%+ I was getting prior over total time on. I am using latest RasBean.
[Samsung Galaxy Nexus] Shadow-Nexus:
I got great battery with 345
[Samsung Galaxy Nexus] allgsmnetwork:
voltages correct

That's setting the voltages correct any kernel version you have the right compromise between battery and performance with antutu to 1536 MHz 9400 to 1420 MHz points instead around 9200 points, tested with stock rom, rom purity and raseben :good:

Voltage settings

https://docs.google.com/document/d/1yjK1fkCGP1E8Ph4YU4A6okRt_1NlJv5vjUsdqDeszV8/edit

Test Antutu
[Samsung Galaxy Nexus] osm0sis:
This line, "This allows those voltages we setup earlier to take true effect otherwise smartreflex will up the voltage or lower depending on how it sees fit," (referring to Disable SR) isn't entirely correct. That's not how SR works.

SR calibrates during boot (so not on-the-fly) and is consistent in that it always seems to calculate the same values for your specific device. Leaving it enabled will lower the voltage only if what you set is still above what SR has calibrated it to. Once you go below the SR calibrated voltage then it is out of SR's control. It will not raise it.

Anyway those look like decent settings. Thanks for sharing. :)
[Samsung Galaxy Nexus] allgsmnetwork:
SR do you mean? Imposed where the franco updater application? Then advise me how to set it better?

Tkanks for you ;)
[Samsung Galaxy Nexus] sk8oldschool74:
If you look closely you did a small charge during that time...;):)
[Samsung Galaxy Nexus] Shadow-Nexus:
Honestly I didn't, something is up with my battery that when it was idle it when up 1%
[Samsung Galaxy Nexus] osm0sis:
I explained it 3 times in the last 2 pages. Have a read please. ;)
[Samsung Galaxy Nexus] franciscofranco:
I find it funny how 12 months later people are still asking the same questions over and over :'(
[Samsung Galaxy Nexus] franciscofranco:
r348:

* Add 2 more patches for Interactive from Google's repo

* Merge 3.0.57

* Enable CFQ by users request

* Enable config.gz export to userspace (forgot this before and its useful if one wants to build my kernel from source)

Documentation for the interactive patches is on my git.
[Samsung Galaxy Nexus] nikulogical:
Thoughts or testing regarding cfq?

Sent from my Paranoid Maguro
[Samsung Galaxy Nexus] franciscofranco:
Dunno. I think its better for non-flash based storage, but you can never know. I did some timed tests with this command:

time dd if=/dev/urandom of=/dev/zero bs=1M count=50M for example to see how long would it take that IO scheduler to perform a random write of 50Mb and they all did mostly the same thing. Try and see for yourself.
[Samsung Galaxy Nexus] nikulogical:
Fair enough.

Sent from my Paranoid Maguro
[Samsung Galaxy Nexus] franciscofranco:
See my edited post.
[Samsung Galaxy Nexus] allgsmnetwork:
voltages are left normal or can be lowered?

Thanks :)

---------- Post added at 09:52 AM ---------- Previous post was at 09:49 AM ----------

not all are experts and then I have a galaxy nexus for 2 weeks I have to test well...
[Samsung Galaxy Nexus] knightmedz:
Excited to try out 348. Was getting good battery life with 345. Got 4+ hours screen time. 100% to 2% -> 1 day 6 hours+. Stock franco kernel settings / Osmosis color settings. Stock takju 4.2.1.
[Samsung Galaxy Nexus] momomok:
all IO scheduler finishes this in 0.001s except noop

maybe I should test with count=500M? :p
[Samsung Galaxy Nexus] Khizar:
using r348 with osm0sis settings and it works great.. getting good battery life and almost no lag
[Samsung Galaxy Nexus] spupuz:
does franco kernel is by default undervolted?
[Samsung Galaxy Nexus] djdeeles:
Perfect kernel but i miss sound control :(
[Samsung Galaxy Nexus] viscocesco:
Me too...
[Samsung Galaxy Nexus] HyvelTjuven:
Question: Does Color Control use up a lot of juice?