yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Hanny:
hi, as with some of the other users, i am here to sadly tell that r194 is working unstable for me which the behaviour of the phone has never been this before :(

i was on 384/1536 since the introduction of 1536mhz slot. it was unstable for me on 1400mV until i increased it to 1450mV and it was stable for a record of 5h30m 1536slot usage and an uptime of over 36 hours.

however since r194, i have played with 1.6ghz and discovered that my phone cant handle it. no problem, so i am back to my stable 384/1536. unfortunately, usually when constantly playing games (GTA, mega jump, etc) my phone will freeze and reboot. whats sadder - is that it will continue to reboot after 30-60seconds after boot, as my set cpu on boot option is checked.

to stop the continuous auto reboot, i have found two ways - both are starting with quickly opening franco's updater as long as the lockscreen is shown (usually opened within 10 seconds) so it hasnt start making boot settings.

1) immediately uncheck the set on boot option so the cpu stays on 384/1228

2) quickly go to cpu undervolt settings and manually apply values (1450mV at 1536mhz for me) before the app does it. and it magically stayed stable at 384/1536.

today, i was playing mega jump, using 384/1536 interactive and it frozen then rebooted. [kmsg ONE] is attached.

then, i suspect it maybe the 500ish mhz slot problem, so i changed it to 729/1536 interactive, increased my past-stable 1450mV voltage to 1475mV for 1536mhz, check cpu set on boot, completely turn off the phone and turn it on. without doing anything (i did not do the quick fix stated above as i went to bath), it continuously auto rebooted for 6 times until i stop it with method one above. after these 6 reboots, [kmsg TWO] is attached.

so its not the 500ish mhz slot problem and i dunno why 1536 is not working stable for me even after increasing its voltage to 1475 when 1450 was stable for me (recorded in r181)

i once suspected PGM2, but with it disabled and set on boot unchecked, the same unstable behaviour occured.

when i recorded my 1536 long stable uptime before, i was using wheatley governor. so i suspect whether its the problem of interactive governor? so i used 729/1536(1475mV) wheatley and played gta. 10 minutes -> freeze and reboot. so again not the fault of interactive :rolleyes:

if you can find any hint in my /proc/kmsg, or if you have any advice, please let me know! thanks so much for the time.

please give me two mins after posting this with the xda app as im going to desktop browser mode and upload the two kmsgs.
[Samsung Galaxy Nexus] franciscofranco:
Thank you. I shall look into it :)

First kmsg looks like it rebooted due to high temperatures since it was throttling for a long time.

Second kmsg its the same MPU Watchdog timer reset, it doesn't seem a kernel crash. However, I suspect the 576Mhz is giving some issues even if its not used its still in the CPU table. Anyway which rom are you using?
[Samsung Galaxy Nexus] rogersnm:
The first one looks like it died because your battery was out of juice, the second one was due to too low voltages. You stated that you set the voltage for 1536 MHz to 1475 mV and then turned off the phone and rebooted, without reapplying the voltage after the boot cycle. The set on boot options in the app do not apply the voltage, you would have had to manually reapply it to set it back to 1475 mV. Seeing as apparently you have a rare phone that doesn't like the 1536 MHz slot @ stock voltage you should use an init.d script to set the voltage on boot, before Franco's app changes the maximum frequency.
[Samsung Galaxy Nexus] ficklecycler:
Just piping up as another user who would love for USB audio-out to happen. Thanks for all of your work on the GNEXUS dude!
[Samsung Galaxy Nexus] kekko986:
Tf201.. i got you! Silver medal! :D

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] bioan:
Franco I just had a signal drop. Flashed your kernel this morning. Didn't have any signal drop on trinity and rascream.

Do you need any logs? Thank you.
[Samsung Galaxy Nexus] rogersnm:
I really don't understand whats going on with the voltages..

These were my settings on AOKP M5:

1536 MHz: 1250 mV
1420 MHz: 1225 mV
1344 MHz: 1175 mV
1228 MHz: 775 mV
1036 MHz: 750 mV
729 MHz: 750 mV
576 MHz: 825 mV
384 MHz: 725 mV
192 MHz: 800 mV

Today I flashed Liquid 1.5 and had instabilities so I spent a couple of hours redoing the voltages from scratch and ended up with:

1536 MHz: 1200 mV
1420 MHz: 1175 mV
1344 MHz: 1150 mV
1228 MHz: 1050 mV
1036 MHz: 1025 mV
729 MHz: 875 mV
576 MHz: 825 mV
384 MHz: 725 mV
192 MHz: 700 mV

Generally higher voltages in the mid frequency range and lower voltages in the high frequency range :\ I don't understand why the ROM choice should impact on voltages... I restored to my nandroid of AOKP M5 and the previous voltages work fine :\
[Samsung Galaxy Nexus] Hanny:
thank you for the quick reply from the both of you! :) :) yea i suspect that too. im using aokp b38 with nothing touched in rom control -> performance, except scrolling cache = default enable and zipalign apk on boot.

well i remember for the first kmsg, i was charging the phone while playing mega jump

and you mean "power off" -> "long press power on" will cause my uppervolts (1450/1475mV) not stick? i thought they always stick based on my experiences.

and even assume they stick, i had also once been aware of the instability between the time of [boot complete] and [franco app apply voltage] when the phone is using the stock voltages (1400mV) - and thats why 1.6ghz is unstable for me because it needs about 1525mV to be hold stable on my phone and it will crash itself if it runs for 1400mV during that short period before voltages are applied.

however, the strange thing is that before r194, 1536mhz@1400mV on my phone was able to survive that short period until 1450mV holds it stable, and strangely not be able to survive this short period on r194.

anyways, say in the worst case, im not familiar in making init.d scripts for myself :p do you have a quick guide?

thank you franco and roger very much again! :)
[Samsung Galaxy Nexus] monkey hung:
Hey Francisco I have suggestion, if it's possible, make a widget that acts as a power mode switcher so I can switch profiles on the fly! Usually when I have my phone plugged in I OC like crazy. As soon as I unplug and want to go somewhere where I need to conserve battery, switch right to a minimum power or balanced. What do you think? A widget like this would actually be worth it compared to all the useless widgets android has these days.
[Samsung Galaxy Nexus] derPianist:
Lol. Just today morning posted the Same.

A widget would be great stuff! :thumbup:

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

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] franciscofranco:
Argghh I promise its the next **** I add to the app...and a toggle to enable fsync, got a few requests for that as well. Im off today, need to clear my head of Android for some hours :)
[Samsung Galaxy Nexus] Moz007:
What maximum frequency for screen off is the best you think ?
[Samsung Galaxy Nexus] franciscofranco:
Stock 729mhz works for everyone.
[Samsung Galaxy Nexus] derPianist:
Wow! Cool. Awesome. Great work and support Franco!

Will donate for you.

Thanks a Lot!

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] arzbhatia:
Thanks franco.

Quick question: Are you going to be adding clockspeed frequencies about 1.6Ghz?
[Samsung Galaxy Nexus] franciscofranco:
I already did.
[Samsung Galaxy Nexus] rogersnm:
I've posted previously in this thread about an init.d script for UV settings (or in this case OV settings) however the search is disabled at the moment so I can't find it :\

Edit: Google helped - http://xdaforums.com/showpost.php?p=27271505&postcount=19442

Essentially navigate to /system/etc/init.d and see what scripts you have. [Assuming you have at least one script] Open the script with the highest numerical prefix and append to the end:

echo "level1 level2 level3 level4 level5 level6 level7 level8 level9 level10" > /sys/devices/virtual/misc/customvoltage/mpu_voltages

Where levelx is just the voltage value in integer millivolt form for a particular frequency (eg. use 1475 for level1). level1 represents the highest frequency, 1651 MHz, and level10 represents the lowest frequency, 192 MHz. You should be able to just set level1 and level2 and leave out the rest, alternatively just reset the stock values for the other levels and SR will do it's thing anyway.

The init.d scripts are run at around the point of the vibration during the boot animation, a similar time to when the screen brightness is applied. It should be set long before Franco's app applies it's settings - which is a few seconds after the lock screen appears.
[Samsung Galaxy Nexus] The Gingerbread Man:
Was already added in latest version 194

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Gahh Its Lee:
Well still getting reboots on 194 only really happens when its doing low demand tasks. Played temple run fine as soon as I clicked out reboot and data corrupted. Wish I had thought to grab a log but I just went ahead with reflashing and what not
[Samsung Galaxy Nexus] Hanny:
thanks a super lot ! :) i will do this, but after seeing if franco has any idea in his next public nightly.

by the way, do you think reflashing the kernel would possibly help in my case?
[Samsung Galaxy Nexus] franciscofranco:
Wait for r195/r196, I removed 576Mhz slot as it was causing some instability. I believe that will fix your problem along with some other random reboots that we've been seeing.
[Samsung Galaxy Nexus] simms22:
no need for a log, we know what most likely happened.
[Samsung Galaxy Nexus] franciscofranco:
Yep, that will change soon Mr. Simms ;)
[Samsung Galaxy Nexus] simms22:
thank you :D
[Samsung Galaxy Nexus] franciscofranco:
****...now I understand why people want morfics contrast option so badly, this looks ****ing gorgeous. Time to ship r196.
[Samsung Galaxy Nexus] simms22:
ahh.. you finally got to it :p
[Samsung Galaxy Nexus] metalspring:
Lol, I like my colors, nearly prefect white whites

red 200

Green 200

Blue 265

red gamma -6

Green gamma 0

Blue gamma 8

omap4 gamma 1.2 (6 actual value)
[Samsung Galaxy Nexus] dandyqb:
dont know what happened but suddenly my franco updater has just stopped working :(

its running again, just reinstalled it again from androidpit
[Samsung Galaxy Nexus] IINexusII:
194 working sweet :)

Conservative still feels like the best one for me in terms of scaling. wheatley and ondemand seems to ramp up to 1228 too quickly with light applications whereas conservative would usually be around 729-1036 for the same usage
[Samsung Galaxy Nexus] simms22:
clear its app data in manage apps and try again(or uninstall and reinstall).
[Samsung Galaxy Nexus] dandyqb:
reinstalled it, working but i found some bug, my cpu freq is not save after boot even its set on boot... waiting for ver 5.4 to hit androidpit :)
[Samsung Galaxy Nexus] franciscofranco:
r196

* Remove 576Mhz entirely - it was causing some undesired instability

* Add toggle to turn on/off fsync: echo Y > /sys/module/sync/parameters/fsync_enabled (it's disabled by default which means that enabled = less IO speed while having data integrity; disabled = more IO throughput but less data integrity)

* Add morfics contrast interface. To change the value: echo X > /sys/module/panel_s6e8aa0/parameters/contrast (change X to the desired value; the default is -24 so don't cry if you think your device is too contrasted)

* Change some ramdisk tweaks for better end-user experience

* Change BLX default value from 96 to 100 - this allows the users to use all range of 0-100 values for the BLX interface
[Samsung Galaxy Nexus] metalspring:
Awesome changes Franco...I still think the latest interactive patch is counterproductive (sacrifice performance for battery life on a governor designed for more performance when there are already governors for battery life?)

But these changes are great (the blx and fsync in particular has been bugging me)

Btw a suggestion to everyone for the fysnc- enable it until you're sure your setup (rom kernel, undervolting, overclocking, etc) prove to be stable then disable it for the extra performance
[Samsung Galaxy Nexus] pluto22:
I respect that, I'm in charge of development & business applications for my company and I pretty much do the same. If I don't like a request / spec I won't approve it for development. :)

I haven't looked at SetCPU in over a year but someone told me the profiles can now contain multiple criteria and has more options like "applications". Next time I forget to take it out of Game mode maybe I'll grab it and take a look.

Thanks again!
[Samsung Galaxy Nexus] IINexusII:
The contrast value makes the screen way too dark and ruins some of the colors on my nexus :(

Changed back to 0 lol
[Samsung Galaxy Nexus] bongostl:
Franco-will you eventually add these toggles to the app?

Thanks for the update!
[Samsung Galaxy Nexus] franciscofranco:
Obviously :)
[Samsung Galaxy Nexus] joeyfong:
The color is changed with the same setting in r196.....is this normal???
[Samsung Galaxy Nexus] franciscofranco:
No **** sherlock. Read the changelog please.
[Samsung Galaxy Nexus] nikulogical:
What do I change the contrast value to get it back to stock? 0?
[Samsung Galaxy Nexus] dpaine88:
I cant seem to get the contrast thing to work...my screen is wicked dark so trying to change it to 0 but changing it to zero does nothing..

Also tried -1 and it looks the same...
[Samsung Galaxy Nexus] nikulogical:
Same thing here.
[Samsung Galaxy Nexus] tcchuin:
The range is from - 24 to 16
[Samsung Galaxy Nexus] nikulogical:
What's stock?
[Samsung Galaxy Nexus] franciscofranco:
It seems that the new value isn't being updated in the hour. A current workaround is this:

1 - set a new value to the contrast interface

2 - if you have my app go to the color multiplier and change one of the colors and the screen will update with the new contrast.
[Samsung Galaxy Nexus] joeyfong:
Strange, I really feel different, anyway:p
[Samsung Galaxy Nexus] nikulogical:
Changing value to 0 then using method 2 worked. Cheers.
[Samsung Galaxy Nexus] IINexusII:
I just edited the file to 0 and locked/unlocked the screen to get it back to normal. It would be great if you can make this a toggle for the people who need this feature.

Other than that, 196 is running sweet :)
[Samsung Galaxy Nexus] nikulogical:
I really hope the 576 step will be added back in the future. Seemed like the perfect min freq. 386 still gives me the occasional lag.
[Samsung Galaxy Nexus] metalspring:
what governor???

i use 192 as a min with interactive and absolutely 0 lag whatsoever...its not meant to run at those frequencies all the time, only on very low demand tasks that dont need any more...and more frequencies= more lag and less battery in general
[Samsung Galaxy Nexus] fatappel:
This method works until reboot and then it goes back to -24. Just fyi. Sure you're working on a permanent fix. Thanks
[Samsung Galaxy Nexus] nikulogical:
Wheatley. I'm using 384 now. The lags aren't often but they're there esp when multitasking or pattern lock.
[Samsung Galaxy Nexus] a5pe4:
Is anyone else unable to download the latest nightly from the updater app?
[Samsung Galaxy Nexus] andrew53517:
Take the gamma color down to 1.0 or 1.2 from whatever your settings were and the screen looks really good with the new contrast. Try it out. I actually really like it!

My screen settings are

180

192

210

-4

0

5

Yes, basically the recommended with a little more cooler colors. They look really good!
[Samsung Galaxy Nexus] metalspring:
in terminal emulator

su
sysrw
echo "#!/system/bin/sh
echo 0 > /sys/module/panel_s6e8aa0/parameters/contrast
echo 2000000000, 2000000000, 2000000000 > /sys/class/misc/colorcontrol/multiplier" > /etc/init.d/99colorcontrol

where 2000000000, 2000000000, 2000000000 are your full color multipliers (change the first 3 digits of each to what you set in franco app

that should work on custom roms with init.d support
[Samsung Galaxy Nexus] fatappel:
Didn't try terminal emulator. Adjusted contrast value with text editor in root explorer and temporarily changed a color multiplier value back and forth in franco's app. This works but only until reboot. Good enough until r197.
[Samsung Galaxy Nexus] leets4uc3:
Loving 196!

For a while now. When I wake my phone while the screen is off, there is a mild skip in the music. Is there anyway to avoid this? Maybe a certain governor or min and max? I have tried a few and can't seem to fix it.

I am on aokp 40, 196 and have HQ sound check and latency fix to 20ms

Edit: changed power mode to music and I think it all good now.... good work with 196. It is really superb!
[Samsung Galaxy Nexus] lemmy_0:
no problems on mine.
[Samsung Galaxy Nexus] kylebarendrick:
I also can't install from the app anymore. It shows the download progress bar (which stays at 0%) and then reboots the phone. I'm not having any other problems though.
[Samsung Galaxy Nexus] a5pe4:
That's what happened to me. But then I tried after rebooting and it instantly rebooted and it says I have 196 now :confused:
[Samsung Galaxy Nexus] denglili:
I feel like losing details on dark spots with the above settings.

Revert back to r194 for now...
[Samsung Galaxy Nexus] kylebarendrick:
Thanks for that. I went back and looked and mine says I have 196 also. Maybe it is just the progress bar that isn't working.
[Samsung Galaxy Nexus] Hanny:
hi franco, on my phone and on my previous stable voltage 1450mV for 1536mhz is working good for me on complete power off and on - before and after your app set the boot options, they are both stable. therefore its mostly the 500ish mhz slot causing problems :) thanks your a magician.

1651mhz is also working nice for me on boot even with the set on boot option. with 1400mV it survived that short period before your app sets the voltage, and without an init.d script. currently im testing on my stable voltage for 1.6ghz starting from 1500mV.

however the default contrast seems abit too dark for me and as i have read the manual value is temporarily not persisting on boot. but its all good until you next release / app update and i am very good and satisfied with r196 because stability for the win!! :D thank you very much!
[Samsung Galaxy Nexus] theking_13:
Is this confirmed to work? I'd rather not have to change the setting after every reboot. :)
[Samsung Galaxy Nexus] mullemulle86:
+1
[Samsung Galaxy Nexus] mtmjr90:
May have missed this but what's the reason for the split nightlies links in the OP? Is r196 the same for each link?
[Samsung Galaxy Nexus] mullemulle86:
Can someone tell me why my benchmark results are worse with 1.6 + 1.5 ghz than with 1.3ghz?

For example Quadrant :

1.3ghz -> 3800

1.6ghz -> 3500
[Samsung Galaxy Nexus] pluto22:
I use Franco's app so I'm guessing one for 384 GPU and one for 512 GPU.?
[Samsung Galaxy Nexus] The Gingerbread Man:
Thermal throttling.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] danielvc:
Franco: you're a jerk :-) Got my SGS3 a few months already, but I'm still updating my Gnex like crazy with CM9 and your kernel. It just keeps getting better and better, never had any problems with it (only around #14, when you got me in a bootloop :-)).

And now, I really dig the new colors and slide2wake-thingy. Argh. I want my Gnex as my primary phone again :-(
[Samsung Galaxy Nexus] derPianist:
Which is the default GPU Clock on Milestone releases.

I am wondering because in nightly releases i can choose between 300 MHz and 500mhz

Which is better?

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] pluto22:
384 is the milestone value and more stable. Some people have issues running 512.
[Samsung Galaxy Nexus] marcuso:
I can not resist on posting this quote (also in francos sig. ;-) ...

"However, if you put any trust in Quadrant scores you could use them to prove that dancing naked for 5 minutes in your garden affects device performance." By Chainfire
[Samsung Galaxy Nexus] rogersnm:
You don't appear to have used the updated ramdisk:

rogersnm@buildbox:~/dev/temp$ wget http://minooch.com/franciscofranco/Galaxy%20Nexus/nightlies/gpu_384mhz/franco.Kernel-r196.zip
2012-06-26 08:07:05 (1.32 MB/s) - `franco.Kernel-r196.zip' saved [3347159/3347159]
rogersnm@buildbox:~/dev/temp$ unzip franco.Kernel-r196.zip
rogersnm@buildbox:~/dev/temp$ cd ..
rogersnm@buildbox:~/dev$ cp temp/boot.img .
rogersnm@buildbox:~/dev$ ./unpack-bootimg.pl boot.img
rogersnm@buildbox:~/dev$ mv boot.img-ramdisk 196ramdisk
rogersnm@buildbox:~/dev$ diff --recursive 196ramdisk 191ramdisk
No Difference
[Samsung Galaxy Nexus] tirolerhut:
Wired headphone volume too low

Hello Franco!

I love your kernel. Pefect battery life and perfect performance.

But it has one BIG BUG: When i plug in my wired headset for a phone call, the volume is very, very low. Any possibility to fix????

(on Stock Kernel AOKP B40 there is no volume problem)

Galaxy Nexus GSM

AOKP B40
[Samsung Galaxy Nexus] matt22:
And did you have a look on this Kernel for example ? http://rootzwiki.com/topic/14685-28-may-glados-v134/
[Samsung Galaxy Nexus] odin13:
Francisco,

Could you take a look @pegasusq governor? It's really performing well on sonicxml's kernel...

Would love to try it out on yours :D

Verstuurd van mijn Galaxy Nexus met Tapatalk
[Samsung Galaxy Nexus] rogersnm:
See this post: http://xdaforums.com/showpost.php?p=27486615&postcount=19933
[Samsung Galaxy Nexus] schizophrenia:
where is the "contrast interface"?

in your app or?

it's definitely too dark now
[Samsung Galaxy Nexus] impulse101:
This only changes the color modifiers you can do that in the app. I the OP wanted to know how to edit the new contrast ratio setting
[Samsung Galaxy Nexus] Stretlow:
Agree with the others that say the new gamma setting is too dark... lost the vibrant colours
[Samsung Galaxy Nexus] jnr21:
Put this in /system/etc/init.d and change permissions (to same as other files in that folder or just rwxrwxrwx), edit values if you want, then reboot.

http://db.tt/zvjqefFX
[Samsung Galaxy Nexus] Stretlow:
Thanks for you're help, genuinely appeciate it, unfortunately my laptop is out of action at the moment so im not flashing or messing with anything except kernels incase I screws it.
[Samsung Galaxy Nexus] jnr21:
You don't need to flash it, just copy that file to /system/etc/init.d with root explorer (or any other file explorer with root capabilities).
[Samsung Galaxy Nexus] coogh:
I already did it, Chainfire app mounts ntfs usb stick but it appears empty.

Any other suggests?

Tnx for your help, Franco!
[Samsung Galaxy Nexus] arzbhatia:
Sorry for last post, wasn't clear much.

Franco, would you add frequencies ABOVE 1.6ghz in the next update or in future?
[Samsung Galaxy Nexus] tuemdeluxe:
I'm loving the new trinity - like colors and the low call volume issue with r194 also doesn't occur anymore!

Great work, thanks for that!
[Samsung Galaxy Nexus] arzbhatia:
I told you :laugh:
[Samsung Galaxy Nexus] jnr21:
This isn't trinity thread :)
[Samsung Galaxy Nexus] emerica243:
Franco, using Kernel Updater App the set power mode on boot isnt working.

If i have that checked, my custom power mode isnt set on boot, cpu freq/gov get reset to default.

If i have set cpu settings on boot along with set power mode on boot, then everything is right EXCEPT it has both cpu cores online when my powermode is set to only have one, the cpu freq and gov are correct though(because set cpu on boot is checked id assume)
[Samsung Galaxy Nexus] tuemdeluxe:
Thats why I was talking about franco's kernel ;)
[Samsung Galaxy Nexus] bigeyes0x0:
The contrast option is nice until you brought your phone out of your batcave and into the sun illuminated world. I'm in the minority that don't like it.
[Samsung Galaxy Nexus] Rovian:
The colors are not the same on r196, anyone else having weird colors on it? it's not like what I used to see on Franco Kernels.
[Samsung Galaxy Nexus] chrisgtl:
Is this why my new Kenwood car stereo won't play music from the Nexus via USB?