yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Khrushy:
**edit: ignore the main post - sr off doesn't seem to reliably apply voltages at all for me**

So, the plot thickens. I think the SR = Off guys might be onto something.

Because I had nothing better to do this morning than nurse a mild hangover and reboot my phone 1,430,914 times, I wiped everything and started over with SR off.

Tested primarily on the 192mhz frequency so far (all the others frequencies I'm just leaving at my previously known safe values while I sort out this SR business).

I'm now sure that even with SR Off my voltages are being applied correctly, because at 625mv and below on the 192 freq I get an instant lock or reboot every time. At 650mv it appears stable through stress testing, but I get the occasional reboot at infrequent intervals in general use. At 675mv it seems rock solid (thus far). That's a massive gain of 55mv from where I had my 192mhz voltage set previously with SR on. :good:

I'll keep you updated as I continue to play with it and see if I can nail down any more specifics.

~Cheers

Edit: Actually, **** only knows what's really happening with the SR = Off voltages, because when I went to testing the 384 freq I got the fun "set any value you want" thing happening again, and could also do that with the 192 freq again. I can't seem to find any rhyme or reason to it, but it seems that with SR off the voltages get applied sometimes (enough to fool you when testing) but never upon reboot, and often not even when you try to manually set them.

Giving up on SR off for now. If someone comes up with a way to actually check what voltage is being used, rather than just the reported setting (which I don't think is actually being used), then I might test further, but right now it just seems like the settings and reality don't match when you turn SR off.
[Samsung Galaxy Nexus] ijama:
Anyone can share their best color mod here...i try once but never get the right one..sorry
[Samsung Galaxy Nexus] WhatzinyourphonE:
Wow works great
[Samsung Galaxy Nexus] Khizar:
-15 contrast the rest are in the pic i attached..
[Samsung Galaxy Nexus] allgsmnetwork:
check GPU

I have seen several times in the frequencies of the GPU application franco.kernel updeter in device control and voltages are salts and down but the frequency remains at 153, but yesterday for a 30 minutes I saw that changed, the lower voltage average 153 384 and a maximum of 512 hours because I always see 153?there is something that is not normal?

Thanks!
[Samsung Galaxy Nexus] WhatzinyourphonE:
Wow love this. Works great
[Samsung Galaxy Nexus] osm0sis:
Wow. I have no idea what's going on. I checked and they were being set in the sysfs files for UV and they were being set correctly with SR off, but then it worked on my device anyway..
[Samsung Galaxy Nexus] Khrushy:
That's exactly it, the UV_MV_table seems to be updating correctly, even with SR off, but there's obviously no way it can actually be using some of the voltages set.

Basically I'm stumped.
[Samsung Galaxy Nexus] Khizar:
got a noobish question for you... when i try settings your voltage settings sometime the phone will freeze then reboot and when i set the settings after the reboot it sticks and no more reboots.. is this normal?
[Samsung Galaxy Nexus] Khrushy:
Hey Os, just checking, but your UV table is in this format right?
[Samsung Galaxy Nexus] lesp4ul:
Eh i see an audio setting, franco for 4.1.2 or 4.2.1?
[Samsung Galaxy Nexus] gianton:
Just to report, r348 with osm0sis UV settings is running rock stable the last 3 days with full usage of my phone. ROM is latest AOKP nightlies from Roman or Steve.
[Samsung Galaxy Nexus] tetrakinitis:
+1. Except rom, here in rasbeanjelly!

Sent from my SmoothCriminal™
[Samsung Galaxy Nexus] llevo3:
+1 on Slim Bean Beta 1
[Samsung Galaxy Nexus] Khizar:
trinity 4.1.2, its a old screenshot lol
[Samsung Galaxy Nexus] The Gingerbread Man:
Osmosis can you add your settings post to your signature? I can't bloody find it again now after hunting. Am gonna make a new init.d colour and forgot to back up my old one :rolleyes::p

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Khizar:
here, i have it bookmarked..lol

http://xdaforums.com/showpost.php?p=34951507&postcount=34567
[Samsung Galaxy Nexus] The Gingerbread Man:
Lol thanks bud!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] bunnahabhain:
Thanks...

But how can i see if the init.d script was loaded? I had to create such a folder cuz it wasn't present. I can't see any differences compared to setting colors in fkU...

Or did i something wrong and the init.d values are overwritten at startup
[Samsung Galaxy Nexus] Langduscher:
Since UV-ing seems hot again... how much am I going to profit as opposed to Smart Reflex doing its job?
[Samsung Galaxy Nexus] Khrushy:
If you do a really thorough job you might manage about an extra 30 mins of screen time, maybe a touch more, but that's with a few hours of setup and playing around with it for a few days afterwards. Unless you *really* want to play with it yourself, Smartreflex actually does a really good job.

I wish I could claim I'm entirely doing it for the battery life, but really, I just like tooling around with things.
[Samsung Galaxy Nexus] JBNex:
Now I'm on 192 min 1228 max 384 max screen off on interactive stock voltages and deadline. Lost only 3% overnight with everything off
[Samsung Galaxy Nexus] RevengeFNF:
Hey Franco, when i play a game like NFS Most Wanted, the game thinks that im playing with an S3 or something similar and puts the graphics to the maximum and the games runs very slow.

With Stock Kernel, the game play with medium graphics and it runs smooth.

Its not possible to change this?
[Samsung Galaxy Nexus] malaroth:
I play the game too... make sure to kill all apps and if you have a cache cleaner do that before playing. I play with 1305/384 interactive and osm0sis uv settings and get very lil lag unless a SMS comes through.

JBSourcery 4.1 + r348 Franco osm0sis UV settings FTW. Keep the Magic alive!

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

---------- Post added at 09:05 AM ---------- Previous post was at 09:05 AM ----------

Getting thanked by Franco and osm0sis makes me all warm and fuzzy.... or maybe that's just that I live in Texas where it's hot and I need to shave :P

JBSourcery 4.1 + r348 Franco osm0sis UV settings FTW. Keep the Magic alive!
[Samsung Galaxy Nexus] The Gingerbread Man:
You will be able to see when the colours get set on the Google screen when you boot. You need to create a folder called init.d in system/etc and I forgot the exact permissions needed to set so I chose all of them. You need to set the permissions on the script and the folder system/etc/init.d

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
Maybe mike already deleted it.
[Samsung Galaxy Nexus] stickjohnonaah:
Your nit making a fool of yourself. I'm very glad you worked on it and tried so we could test it. We will just have to wait
[Samsung Galaxy Nexus] joackie27:
Just a quick Q. The one with the OC at the end of the filename, is that the OC free or the one WITH the OC?
[Samsung Galaxy Nexus] franciscofranco:
With the OC.
[Samsung Galaxy Nexus] Danny80y:
Is this the OC that makes most phones jump/stutter? If so is there going to be a fix for it?
[Samsung Galaxy Nexus] franciscofranco:
Maybe, I don't have this phone... I put up two versions so people can test, test and see for yourself. My testers didn't complain.
[Samsung Galaxy Nexus] Danny80y:
Ok, I'm going to flash it will report back in a sec......:D
[Samsung Galaxy Nexus] mskip:
I have never experience any stutter with any of francisco's kernels and the latest version is absolutely amazing I will post some benchmarks in a few minutes but its the best by far.

Make a NAND backup and test it if anything goes wrong you can easily restore your stock boot image.

Mark.
[Samsung Galaxy Nexus] dwang:
Great job, the latest OC version doesn't stutter at 1.4 like the previous versions.

Super fast and smooth.
[Samsung Galaxy Nexus] Tung_meister:
Excellent, I'm consistently getting ~3500 in quadrant with the latest version, thanks for the update!
[Samsung Galaxy Nexus] Danny80y:
Well It's awesome but I can't run at 1.4 it boots and everything but once every 10 second it takes a second to pause. 1.2 it's tons better than some of the other ones.....
[Samsung Galaxy Nexus] bigxie:
I'm still getting graphics artifacts using the non OC, so it's not the GPU OC causing these issues.

I can confirm that too, using coolbho3k's UV only kernel that also has GPU OC to 384, never saw the artifacts.

I wonder which other patch can cause these artifacts?
[Samsung Galaxy Nexus] franciscofranco:
****, that ain't good. Thanks for the warning, I'll look at it.
[Samsung Galaxy Nexus] mrBira:
"Dude". Not everyone is close to a computer. Like me, one week without one. Thats why a cwm zip would kick ass.

// mrBira @ stock rooted rom.
[Samsung Galaxy Nexus] dwang:
spoke too soon. starting to get lag at 1.4 now..
[Samsung Galaxy Nexus] Tung_meister:
It's really strange how so many people seem to be having issues with stuttering and artefacts, even on the standard clock version, I've not had a single issue with any of the builds of the kernel.
[Samsung Galaxy Nexus] Shetlander:
Franco, any chance you can put the GPU overclock back in the 1.2ghz kernel. That would be perfect as it seems to be mainly the CPU overclock that causes issues.
[Samsung Galaxy Nexus] mskip:
Same here its always been consistently smooth and fast and I have tested all of Francisco's kernels.

I guess some people got the Galaxy Nexus Special Edition :)

Mark.
[Samsung Galaxy Nexus] rabhw:
Just wanted to chime in and let Franco know that even with the non-OC kernel, I'm still getting the major video artifacting, so something else is up besides the OC.
[Samsung Galaxy Nexus] hosmsdos:
Franco i want to buy your app, but i cant even if I'm using market enabler, I'm living in Saudi Arabia and the country is not even listed in the market !!. Can you provide other ways to buy your app.

Thanks
[Samsung Galaxy Nexus] ellesshoo:
Please tell me we'll get UV access via sysfs not just the app. If so, could you tell us the path?
[Samsung Galaxy Nexus] Thracks:
It will be available on http://www.androidpit.com/ when kernel #13 is released.
[Samsung Galaxy Nexus] franciscofranco:
I already said that that is ready for the next version. I'm working on it as we speak.

Of course...
[Samsung Galaxy Nexus] Pinkthesink:
Franco,

speaking of brightness, is there a way you can increase the brightness more? As I understand, you have already done so. But I'm wandering if there's a way to push it further.
[Samsung Galaxy Nexus] franciscofranco:
No, 300 is the maximum.
[Samsung Galaxy Nexus] aron7awol:
I've been running at full brightness all night and am seeing no difference at all in lag. That is, the minimal lag that I usually experience on auto brightness is still there on full brightness.
[Samsung Galaxy Nexus] minooch:
Lag while unlocking??
[Samsung Galaxy Nexus] cjones1348:
So since using this kernel I've experienced very poor battery performance, i rebooted and opened camera then backed out. I was getting about thirty percent better battery life before installing this kernel, any suggestions?
[Samsung Galaxy Nexus] mariusdroid:
Go back TO your privios one
[Samsung Galaxy Nexus] dpaine88:
In the OP it says the GPU is overclocked, is that still true? I thought I remembered somewhere that it was no longer overclocked.
[Samsung Galaxy Nexus] aron7awol:
The only lag I ever experience, and it's minor, is specifically when hitting the power button and waiting for the device to wake. I still have been experiencing it intermittently while on full brightness so auto brightness does not appear to be the cause. Like I said, it's minor, so it really doesn't bother me.
[Samsung Galaxy Nexus] dadsterflip:
this ^^

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] dpaine88:
I get this too....I was thinking maybe it is the Conservative gov that is causing it?
[Samsung Galaxy Nexus] JFMFT:
Maybe it's hotplug? Disabling CPU_1 when screen_off could be causing the screen to wake sluggishly.
[Samsung Galaxy Nexus] dpaine88:
Mine is still slower than stock kernel and I don't use the hotplug option.
[Samsung Galaxy Nexus] aron7awol:
Well, i use interactive and I don't use hotplug so I can eliminate those two as causes as well. It might just be one of those cases where "it just is". I can't even remember if it existed when I running stock, and it doesn't bother me enough that I'm going to flash back to stock to compare. I'll just live with it.
[Samsung Galaxy Nexus] minooch:
Yeah, That's not what we're on about - That has already been discussed!

It's the while unlocking i.e. after you hit the power button, the screen comes on & then you slide to unlock
[Samsung Galaxy Nexus] sluflyer06:
Does the kernel do anything other than nenvle the use of init.d or does it actually do things with it? AOKPno has init.d tweaks you can enable...will that overwrite or interfer with anything your doing franco?
[Samsung Galaxy Nexus] aron7awol:
Ahh, well I just tested myself and I can definitely reproduce it consistently as well. Nice find, nikosrs4.

Edit: Did some more testing to see if I could get autobrightness to lag in other places while the phone is awake. I see no increase in CPU usage, no lagginess, even when going back and forth between pitch darkness and under a super bright light. This makes me wonder, why does the autobrightness have such a drastic effect when the device wakes?
[Samsung Galaxy Nexus] shawnaye:
Guys search the thread for nfs. You'll find a fix posted about a month ago.

It goes somewhere along the line of placing a file into the root folder of your sd card.
[Samsung Galaxy Nexus] Langduscher:
Permissions are chmod 755 (rwx-rx-rx)
[Samsung Galaxy Nexus] grotesque02:
With stock battery I set extender battery at 96.

Now I have a 2000mAh battery, I can leave at 96 or I have to change?

If yes, with what value?

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] Langduscher:
You can leave it the same (meaning your battery does not charge past 96% full). It just calculates 96% of capacity (mAh)
[Samsung Galaxy Nexus] osm0sis:
That means you've got a borderline voltage on one of your frequencies. It would generally be the one it froze immediately on when you entered it (if you were locking to each freq as you entered them). I'd suggest bumping that one up by 25mV. If it wasn't on a particular frequency when you entered the voltage, and just occurred randomly afterwards when you were done, then my first guess would be one of the ones you have set as either hispeed_freq or input_boost_freq, but you should try to isolate which one by narrowing your range with min/max and then stress testing them.

And to everyone just using my voltages wholesale, at least go through them correctly, isolating the frequency by setting it as your min and max and see if you can push the voltage any lower than mine. Your silicon may be stronger than mine is and you could be missing out on more UV savings. Please, all, take the time to make a correct voltage profile. :good:

Yup. It's interesting, the output is always like that (as in my settings post), but the way to write to it is in the echo "voltage voltage voltage" > format from the top down. Maybe check the other MPU voltage table file (/sys/class/misc/customvoltage/mpu_voltages) too to see if it's also showing correctly? They're supposed to both be tied together through the interface, but we're dealing with some funky **** here.

Already did a few days back. ;) You know you could just edit the init.d script on the phone using a file explorer app now that you've got it set up.

Pretty cool fix actually, some guys hacked the game to make it so that, instead of it deciding itself based on max CPU/GPU (a really dumbass idea), it's rewritten to check a file on the sdcard. You can put one of a number of values in that file to make it run as fast and as smooth (at the expense of graphics quality) as you want.
[Samsung Galaxy Nexus] Khrushy:
Yeah the fact it's written differently to the output is why I was asking.

And alas, other voltage file is the same and also updates its output correctly - back to being stumped!
[Samsung Galaxy Nexus] osm0sis:
Interesting that wiping settings worked for galakanokis for getting UV to work correctly with SR off, but it didn't for you. Try my franco.Kernel Emergency Reset zip. Perhaps clearing data+cache through App Info somehow didn't quite do the job.
[Samsung Galaxy Nexus] calibachrome:
r348 is working perfect for me thus far... Great performance, good battery life. Thanks!
[Samsung Galaxy Nexus] galakanokis:
Doubled checked this morning while trying to set all my voltages and things are still working as expected. I just cleared data through apps menu.
[Samsung Galaxy Nexus] nikulogical:
What's the default tcp algorithm supposed to be? Westwood or cubic?

Sent from my Paranoid Maguro
[Samsung Galaxy Nexus] chickentuna:
Cubic

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Khrushy:
Done and done. No change.

I reckon it's a ROM/dirty flash issue. Next time I switch Nightlies I'll do a 100% clean flash and see if anything changes.
[Samsung Galaxy Nexus] X1iser:
I've got some soft reboot since 345 which log can I submit? last_kmsg? logcat?
[Samsung Galaxy Nexus] kralde:
Does this kernel works with CyanogenMod 10,1? I get reboots :S

thanks
[Samsung Galaxy Nexus] shreddintyres:
if you can submit both thats great otherwise if im not mistaken last_kmsg will tell us if its kernel related or not.
[Samsung Galaxy Nexus] X1iser:
Thanks
[Samsung Galaxy Nexus] The Gingerbread Man:
Yeah forgot I had a downloaded copy on my SD card. Got it set up again and working great

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Wir3start3r:
I undervolt my phone with osm0sis settings should I disable MPU, IVA and CORE Smartreflex?
[Samsung Galaxy Nexus] jcmm11:
No
[Samsung Galaxy Nexus] RevengeFNF:
I found the fix, but its only for version 1.0.28.

I bought the game, so i prefer to play the version 1.0.46.

I guess im gonna use Lean Kernel until i get tired of the game, then i will return to Franco Kernel.

Thanks
[Samsung Galaxy Nexus] Khrushy:
So clean install of AOKP nightly, literally no other programs installed. Fresh install of f.Ku from play market and . . . . I can still lock my cpu freq to 192 and set voltages at 1mv with SR off and it accepts it happily. Both the voltage table files are updating correctly and showing 1mv.

I have no idea what's going on. I'm going to go back to my previous happy existence with SR on and pretend I never heard about the idea of turning it off.
[Samsung Galaxy Nexus] joao7458:
I changed my voltages and phone crashes and I always wanted the default voltages someone help?
[Samsung Galaxy Nexus] Khrushy:
http://xdaforums.com/showpost.php?p=35648172&postcount=35728

There's a reset zip file by osm0sis in the post I linked. Download the zip and flash it through recovery - it should reset all your kernel settings back to defaults.
[Samsung Galaxy Nexus] osm0sis:
PM I just got:

I can't help you learn to read today. Sorry.
[Samsung Galaxy Nexus] duduzinho15:
Work perfect with me :D
[Samsung Galaxy Nexus] osm0sis:
Logcat and copy kmsg. Email them to Franco with an explanation of the issue. :good:

Hopefully there'll be something he can glean from them. I wonder how widespread it is.
[Samsung Galaxy Nexus] Khrushy:
If I were you I'd edit my voltage post to have +25 or +50 on every voltage. The people who are just using them as a baseline will still test and find their own settings, and the copypasta idiots will have less chance to crash and bother you with it.

Edit: Will pull a logcat and kmsg when I get back to a pc with USB functionality (work is all locked down for security purposes).
[Samsung Galaxy Nexus] aimcr7:
I dont know whats wrong but on 348 i hardly can get 3.5hours screen on, battery life seems worse than 345 and 342.

On 345 i easily can get 4 hours or usually i can get more than 3.5hours with 17-20hours battery life.

Back to 345 now, let's see.
[Samsung Galaxy Nexus] osm0sis:
Wasn't r345 the one with the derped debug stuff that made battery life bad? I'd tend to agree battery hasn't quite been as good since that happened. r342 got me into the 4hr club.

Edit: Nevermind, it was r344 that was broken. I still don't think it's been as good since then though. Trade off, I’d guess; the new interactive patches made it the smoothest it's ever been on low frequencies but naturally use a bit more battery.
[Samsung Galaxy Nexus] MaLiXs:
I must admit that i use osm0sis voltage but i have carefully tested all Frequency with this app

https://play.google.com/store/apps/details?id=com.into.stability

I think it ok to use those setting but people need to test it before complaining

Envoyé depuis mon Galaxy nexus avec XDA premium
[Samsung Galaxy Nexus] jackpham:
Updated Vietnamese translations for FKU!

Pls add next build!

Tks!
[Samsung Galaxy Nexus] osm0sis:
Not sure about that stability test app. I adjusted my voltages down to values I knew to be borderline from when I was testing them (ie. working but unstable when switching or when stress from a 3D game was put on them), and that app didn't make it crash. So I don't think it's enough of a stress test for our purposes, unfortunately.
[Samsung Galaxy Nexus] haxor:
I am on Xylon 012 whenever i change kernel setting or voltage through Trickster MOD or From FK.U then after restart they become default :confused:
[Samsung Galaxy Nexus] ChazzMatt:
Hint. Don't put in those voltages.

Exactly. You've said many times:

1) make a backup

2) these are MY voltages that work with MY phone. Not guaranteed to work with yours.

Maybe you should add, "Will NOT work with yours". :silly:

if osm0sis put in fake numbers, then people would complain they aren't getting the battery "savings" or whatever.

Seriously, I think most people just need to leave the voltages ALONE. :rolleyes: Go find something else to screw up that didn't cost close to $400 with tax and shipping. :eek:

Guy I knew was messing with his car engine, trying to get it to go faster. Was his family car, a Honda. He was on this kick where he was using a drill to make a hole in the engine bigger where the fuel came through the fuel injector. (Pardon me if I mess up the facts a little, it was pretty technical.) For a week, every day he came to work all enthused because he got a little more juice going to the engine. He could rev it now! Then one day he came in and didn't say a word about his car. "Hey Tim, what's up?" CRACKED the engine. Finally drilled that hole just a little too wide. BAM. Engine going to need replacing. $2,000. Wife is mad at him.... Was it worth it? No. He had a perfectly good car. He screwed it up.
[Samsung Galaxy Nexus] osm0sis:
That and the big "no tech support PMs" in my sig. :p

I have adjusted the wording of the warning yet again anyway.. :rolleyes:

UVing, even incorrectly or too far isn't likely to in any way permanently mess up your phone though... Just saying. I do like the analogy though. :)
[Samsung Galaxy Nexus] haxor:
Anyone plz !
[Samsung Galaxy Nexus] arefx:
Anyone running this on PA, if so hows it running?
[Samsung Galaxy Nexus] osm0sis:
Pretty obvious.. You're trying to use two apps at once.
[Samsung Galaxy Nexus] haxor:
so which app you prefer its Trickster MOD or FK.U ?
[Samsung Galaxy Nexus] Khrushy:
He could add +25 to every level and it would still be a significant UV on almost every frequency, but it would give him a bit more breathing room from idiots.

And lets face it, idiots rarely know the difference anyway.

I mean, don't get me wrong, the ideal situation is "people stop being idiots", but this is my fourth phone, over a course of almost 6 years, that I've been using and messing with on XDA, and if one thing has been constant all that time it's that some people will always come in, ignore warnings, mess their stuff up, and expect others to help fix it.

Even if you're epically helpful like os is, giving yourself a little leeway from those people is a good idea in my book.