yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Hanny:
i apologize in advance if im wrong, because i have already reverted back to ICS and stayed on r200-ICS after playing JB for a while

however here is a little idea as i posted some pages ago: try use SuperSU by chainfire, instead of the latest superuser app by chainsdd (with latest binary 3.1) as they are giving issues. dont forget to report back :)
[Samsung Galaxy Nexus] mingkee:
Search my post about init.d and busybox trick.

It finally worked even I see the color change on "Google" logo.
[Samsung Galaxy Nexus] YashBhatt:
I just updated to franco's latest app i.e 5.7 and evrything seems to be working fine now

Just love this kernel,Keep up the goodwork franco :)
[Samsung Galaxy Nexus] splus:
Yup. I already switched to SuperSU. It looks like it works better with Jelly Bean ROMs than Superuser.
[Samsung Galaxy Nexus] osm0sis:
Or try Superuser 3.2 RC2 http://androidsu.com/superuser/

It seems to work correctly for me now where 3.1.x did not. (I paid for Superuser Elite so I'm a bit hesitant to switch :p)
[Samsung Galaxy Nexus] atsavlis:
Franco, is fsync() still on by default?
[Samsung Galaxy Nexus] ntorresla:
I will call it blindness...

Lol

Thanks bro

Saludos desde Ecuador
[Samsung Galaxy Nexus] rogersnm:
Yes
[Samsung Galaxy Nexus] ntorresla:
I want yo download the r217, the latest one is the 512gpu?

Saludos desde Ecuador
[Samsung Galaxy Nexus] osm0sis:
Nah, I take it back... *sigh* The binary updater and ota rootkeeper work now but it's still borked wrt Franco app/settings. :(

Rolled back my binary to 3.0.3.2 again, but apk 3.2 doesn't seem to remember apps. Rolled apk back to 3.1.3. Ugh, buyer's remorse...

Nope. Both. http://minooch.com/franciscofranco/Galaxy Nexus/JB/Jelly Bean/
[Samsung Galaxy Nexus] Langduscher:
Dumb question: just flash in cwm?

Thanks
[Samsung Galaxy Nexus] osm0sis:
Yes, but, see post above yours. Don't bother.
[Samsung Galaxy Nexus] jaycarag:
First, thanks again to Franco for the update!

Just wanted to ask, I've been using Franco's kernel since ICS. Since I've switched to JB, I just stuck with the 384GPU. I'm really curious about the 512GPU and I really would like to try it. However, seeing as some of the users posting here are encountering some issues with the 512GPU is it really worth it? I've research that the overclocking the GPU can indeed be harmful to some phones. Other phones can work much smoother with it. So I would just like to confirm if the difference in performance between the 384GPU and 512GPU is really that great.

Thanks in advance and sorry if my question sounds stupid. :silly:
[Samsung Galaxy Nexus] ShankyJain:
JB 384 or 512

Can anyone tell me what is the difference between 384 and 512 version? At what cost do I get better GPU in 512?
[Samsung Galaxy Nexus] ntorresla:
R217 jb working flawlessly on JRN84D

Saludos desde Ecuador
[Samsung Galaxy Nexus] dandyqb:
the only difference is 3 frames in nenamark2. :)
[Samsung Galaxy Nexus] cchant:
Here is my experience with 384 vs 512:

My first Nexus ran 512 without issue so I did. I didn't notice much difference in UI smoothness or battery drain, so I kept installing 512.

My new Nexus has some occasional artifacting at 512, and will freeze up if I mess with it while it is charging.

I notice no difference in 512 and 384, battery or performance on my new nexus since I've installed jelly bean.

today I tried, just for fun, Quadrant on 512 vs 384. Everything is stock besides the GPU change, and I ran each test 3 times.

On 512 it performed an average 2957

On 384 it performed an average 3021

Not much of a difference, and I don't know why 384 has a higher score. If I hadn't run quadrant I would have never known the difference. The only reason I am on 384 now is because of the random artifacts, and the fact I can't use my phone while it's charging.

What's weird is my new Nexus doesn't seem to get as hot as my old one.

My advice, run whichever version your phone likes best
[Samsung Galaxy Nexus] emd2009:
So what ended up working for you? I'm having the same issue.
[Samsung Galaxy Nexus] osm0sis:
Well, I have Superuser 3.1.3 from the Play Store. Cleared data on it, uninstalled. Uninstalled Superuser Elite. Replaced su binary with 3.0.3.2 (remember chmod 06755). Reinstalled Superuser 3.1.3 from the Play Store and everything appears to work okay. No lag, gives perms correctly, Franco app runs well and seems to restore settings on boot. OTA Rootkeeper even works. Then I reinstalled Elite. If you do all that and it doesn't work, just keep clearing Superuser/Elite data, uninstall and reinstall Superuser until it reads the su binary correctly. It didn't work for me the first reinstall either (spinner keeps going). Once it reads correctly then you should be good to go from that point on.
[Samsung Galaxy Nexus] emd2009:
Where can I download that binary?

Do I have to have Elite?
[Samsung Galaxy Nexus] splus:
Switching to SuperSU worked best for me, no more lags or problems like Superuser. I got tired of messing with Superuser, trying to make it work properly...

Download latest SuperSU CWM flashable version at its thread:

http://xdaforums.com/showthread.php?t=1538053
[Samsung Galaxy Nexus] osm0sis:
You don't need elite. I just mentioned it since I do and I got rid of it as part of the process.

I posted the 3.0.3.2 su binary earlier in the thread. Hope it helps!

P.S. If you didn't pay for Superuser Elite then why don't you just switch to SuperSU? :p
[Samsung Galaxy Nexus] Hanny:
hi everybody i just occasionally used wifi tethering recently which i dont usually use it. as i know there been problems since r18X release and im here to report:

aokp b40

franco r200-ICS

wifi tether (from android settings) is WORKING with open security (no password)

and NOT working with both WPA/WPA2 secured networks

how not working:

on my side, it is shown correctly that the access point is activated. notification, the checkbox, everything normal.

however, on another android phone trying to connect to my phone, it stuck at CONNECTING and then becomes DISCONNECTED after 5-10 seconds.

if i use a PC/older cell phones, it simply says CONNECTION FAILED even the password is correct.

yes, and i have also tried the root wifi tether from the market - same results as above.

i am currently very fine with using an open network with my friends just rarely, but WPA/WPA2 secured tether may be important for some people :rolleyes:

ive seen not many mentioned about this in the last 40-50 pages so hope i wont annoy you by bringing this up again. is it fixed on jelly bean builds? if yes im glad to know that :D

thank you very much for ur attention!
[Samsung Galaxy Nexus] splus:
There's hardly any difference in battery life but the difference in smoothness is noticeable. This is easiest to notice in scrolling in various apps, for example Play Store.

Having GPU at 512 MHz makes using GNex much nicer and smoother experience because GPU is GNex's weaker side. Actually overclocking GPU has more impact on smoothness than overclocking CPU, at least on GNex.

There's no harm if you flash Franco's kernel with 512 GPU. If your device hardware can handle it it will run OK, enjoy it.

If it can't handle it you'll have artifacts appearing on your display in some apps, and in that case just flash the kernel with 384 GPU and all will be OK.

Some devices can't handle 512 MHz GPU and some can, it's the hardware thing. The only way to know is to try. Easy... :)
[Samsung Galaxy Nexus] The Gingerbread Man:
Many thanks this fixed it for me

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] sway40:
This is with stock battery, clocked at 1.6-350, ondemand. V3 jb with 216 franco.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] louyaorong:
I don't know why I still have problems with supersu. It works OK when I'm on 216, but after upgrade to 217 today, the options don't stick any longer after a reboot, even I revert to 216.
[Samsung Galaxy Nexus] timbck2:
I can't download v217 from Franco's app (the latest version 5.7). It flashes the download progress bar briefly on the screen then it disappears. Also my color settings aren't sticking, they are there when I go into each color but when I go back they're all 0,0,0. Any ideas?
[Samsung Galaxy Nexus] Treatcon:
Same for me except I am using 5.7 and 217/512, but if you touch the setting for each they are actually set, just the display what you read says 0. Change the numbers to something else, then change them back and they will stick until you reboot.

Also my Max and Min CPU settings are not sticking on reboot. They default to 1228 and 384 and I do have Set CPU settings on boot checked. Not using any power modes as well. Both power mode options are set to None. Nothing else has been changed in the app and I have never used any scripts to change settings. Using latest SuperSU app and binary.
[Samsung Galaxy Nexus] kid1da:
Can someone post the r200 ics /jellybean test kernel I get 404 error from the link in the op.
[Samsung Galaxy Nexus] The Gingerbread Man:
Flashing the cwm zip of supersu worked for me to make stuff stick on boot. I was using supersu before anyway but for some reason flashing it worked so give it ago.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
I dont know what else to do for all the options to stick. Some users are ok some arent... Im out of ideas it just works for me.
[Samsung Galaxy Nexus] mike216:
Works for me to. 217 is soooo good Franco,thanks champ

sent from my precious nexus
[Samsung Galaxy Nexus] The Gingerbread Man:
Maybe add supersu into your kernels so as you flash the kernel you get supersu at the same time as its superuser variations and versions seems to be causing the problems. That's of course if chainfire is cool with it.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] RayGarden:
JB V3 (Bigxie) ???? where did you get that from?
[Samsung Galaxy Nexus] sway40:
Huh??

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
Yeah good idea. He'll obviously be cool with it :)
[Samsung Galaxy Nexus] laureanop:
I'm one that cannot get settings to stick.

Who cares ? A couple of clicks is a small hassle for such awesomeness !

"the relentless pursuit of the perfect rom "
[Samsung Galaxy Nexus] :
+1 My settings don't stick but this is exactly the way I feel. So many ppl ***** about stuff and Franco is great! Love this kernel and app!

Edited due to mistype...
[Samsung Galaxy Nexus] g33k3r:
He was asking if when you said V3 JB you were referring to the Bixie ROM since he only has a V2 ROM out.
[Samsung Galaxy Nexus] foxehkins:
My CPU 2 says it's offline. I didn't see anyone mention this.
[Samsung Galaxy Nexus] sway40:
Oh ok, no vicious rom v3

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] derPianist:
Turn it on? :rolleyes::D:p
[Samsung Galaxy Nexus] foxehkins:
Lol I wish I could. I click it and nothing happens!!!!! XD
[Samsung Galaxy Nexus] jenicekk:
Me too:-(
[Samsung Galaxy Nexus] 105437:
Running nightly 217 with Vicious v3 and color settings revert to default after a reboot. In addition CPU settings revert as well.

Certainly not a huge issue at all... loving this kernel! Thanks! :good:
[Samsung Galaxy Nexus] foxehkins:
I cleared app data too but nothing. I click the CPU and it nothing happens, no menu or anything. Haven't noticed a performance issue so maybe it isn't having an effect.
[Samsung Galaxy Nexus] derPianist:
Go to Franco Power Modes and then select Full Power and both Cores should be back online. Than you can again change Settings as you want!

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] Langduscher:
OK so I flashed latest SuperSU+busybox from bigxie's thread...

Now NONE of the settings stick :eek: getting fed up with it....... and yes I use my phone A LOT so I reboot 2x a day... REALLY fed up with having to seup the kernel settings over and over again... :cyclops:

Did this n00b forget something or... (how da fuq do I delete superuser??)
[Samsung Galaxy Nexus] jopherr:
Hey guys, I used to keep up with this thread a lot more, but lately I have just been lurking every now and then. Could someone explain to me how come when people post their color control numbers, the values are always in the low 200s-150s? I noticed that by ramping up the rgb values to 360,318&370, I can get the screen up real bright and the colors look really nice. Do people keep the numbers down to keep the screen brightness down to save battery life?
[Samsung Galaxy Nexus] muhsli:
How weird is'nt that, I just came in here to let people know that flashing exactly that package fixed my issues with non-sticking settings :eek:

idk why it does'nt work for you, but suddenly in my case all settings get restored upon boot!

This here is what we're talking about now..
[Samsung Galaxy Nexus] johno168:
How do you get the old binary back? I. E 3.0.3.2?
[Samsung Galaxy Nexus] The Gingerbread Man:
This is basicly what I said a page or two back and yet still people have commented since about it not sticking.

This isn't directed towards you muhsli but toward perhaps some lesser experienced xda guys.

Why you no read recent pages?

If you want to solve problems then at least try to put a little effort in. I had supersu app, even donated to pro one and stuff wouldn't stick on boot but somehow flashing the supersu 0.93 (exactly the same as installed from play store) worked.

That's why j suggested to Franco to include it in the flashing process. I try to help people I really do but even my patience is running a little thin with the same bloody issues and no one searches for the answer...

So thanks who ever suggested to flash that supersu app I'm grateful to you but again I say again (to general noobies here)

Y U NO SEARCH :banghead:

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] rogersnm:
The default values are 200/200/200. Values above this level are supposed to increase the risk of burn in and are therefore not recommended however values significantly below this lead to a dark screen, this means that most suggested colour profiles lie near the 200/200/200 mark.
[Samsung Galaxy Nexus] eddie_gordo:
Hi Francisco.. :)

Will you continue to develop Kernels for ICS or will r200 be your "final" ICS kernel? :) I am still using ICS Rom's and I miss flashing your Kernels almost everyday.. :D

Notice I am not demanding anything, I'm just curious on your plans regarding ICS and JB.

Regards from Portugal and keep up the awesome work!!
[Samsung Galaxy Nexus] osm0sis:
I've linked to it like 3 times in the last 5 pages. Shouldn't be too hard to find. Cheers! :)

:laugh:
[Samsung Galaxy Nexus] franciscofranco:
r200 is just experimental, but yes that is the last ICS build. r196 is stable as a rock too in case r200 doesnt work as it should. From now on its Jelly Bean only builds.
[Samsung Galaxy Nexus] Yenupuri:
Was looking for an answer like this .. was trying to see which one to pick (after the last milestone release...) r196 shall be the one.

Thanks !!!
[Samsung Galaxy Nexus] jaycarag:
Thanks! I tried using the 512GPU but, my phone display turned into an 80's TV. :eek:

I reverted to back to 384GPU which I think is the maximum GPU my phone's hardware can handle.
[Samsung Galaxy Nexus] dandyqb:
its confirmed, SuperSU .93 release resolve the non-sticking configuration issue in franco app. :cowboy: :good:
[Samsung Galaxy Nexus] acPIZZA:
So 384 is what we should be installing? I do not know the difference or what that really means. I just want the most powerful effective, stable version of the already great kernel.
[Samsung Galaxy Nexus] neederishelp:
If your phone can run 512, do that, if not,run 384
[Samsung Galaxy Nexus] franciscofranco:
Try it for yourself. It's kinda obvious that more Mhz means more performance, but not all devices handle that bit GPU frequency.
[Samsung Galaxy Nexus] jeetS:
wahoo.

r217 512 and no artifacts finally!!!!!

me likey
[Samsung Galaxy Nexus] franciscofranco:
Yeah been saying that for ages, the problem is the su binary, not the app :)
[Samsung Galaxy Nexus] jaycarag:
I think it really depends on you device's hardware. Like I said, some users here are using the 512GPU without any problems whatsoever. I was previously using the 384GPU but, I decided to try and install the 512GPU because of my curiosity. Sadly, my GNex can't handle the 512GPU.

I would suggest that you try the 512GPU first and hope that your device can handle the "hyper" overclocked GPU. If it can't, then you don't have any alternative but to use the "milder" (hehe) overclocked 384GPU. :good:
[Samsung Galaxy Nexus] emd2009:
So I tried the binary posted earlier and I tried downloading the Su .93 and neither options allow the app to save color settings after a reboot.
[Samsung Galaxy Nexus] BigBake88:
After bumping up the voltages a little bit, I am running 1.8Mhz stable now! Thank you, FF!!!
[Samsung Galaxy Nexus] eris72:
franco, the OMAP gamma changes built into every kernel i've used causes music to skip when turning the screen off and on. EXCEPT Faux's kernel. He uses a different method, from his thread:

forward ported OMAP4 DSS Gamma control settings from Panda Board Linux 2.6.32 kernel

http://en.wikipedia....amma_correction (this gamma correction is done in the framebuffer, so it is a SOFTWARE correction, different from the Gamma Hacks by supercurio which is more of a Hardware gamma correction and are totally independent from each other.

Would you consider looking into this? I love your kernels, but the omap gamma settings have a huge impact on my screen. i can't be the only one experiencing this??
[Samsung Galaxy Nexus] kolyan:
Doesn't 196 still have the low volume bug?
[Samsung Galaxy Nexus] dandyqb:
one thing i found after flashing the superSU .93, my charging indicator wont reach 100%, it follows whats in the BLX, unlike before, my blx is 98% but my indicator is in 100%, i dont know if this one is kernel related or another SuperSU bug. :confused:
[Samsung Galaxy Nexus] TEK112:
Usually it is the other way around. BLX at 100, but indicator at 98%. There is a long and drawn out story behind this, but it is normal and I am surprised you haven't come across it before.
[Samsung Galaxy Nexus] dandyqb:
so now im bumping up my BLX to 100% just to get the indicator right, and i dont know the effect of this on my battery in the long run. :(
[Samsung Galaxy Nexus] ChanceOfChange:
but the app needs more improvment thoo...;)
[Samsung Galaxy Nexus] TEK112:
Don't let the battery weirdos scare you. I would rather have the extra 10% for a year or two and risk having to buy a new battery after a year (not because it fails, but because it only charges to 90%), than live with only 90% to play it safe.

What you are doing is fine.
[Samsung Galaxy Nexus] WillJitsu:
I'm not sure if this helps, but when I use the option in your app to set the CPU frequency on boot, it does not stick. However, if I use SetCPU to set the CPU frequency on boot, it does stick.
[Samsung Galaxy Nexus] Antob125:
I'm on ics 200 and this is what my su looks like. From what I've read, I have the correct binary for colors and cpu set on boot to work, but it doesn't. What am I doing wrong?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Myster:
Should we expect a last Milestone5 or thats just it ??
[Samsung Galaxy Nexus] mike216:
The bittersweet fact ice cream sandwich will be a long forgotten OS here soon so don't give to much thought to it. Franco has said 196 is rock solid stable and will be the last ICS kernel. Time to turn the page and look forward my friend better things to come for you very fortunate galaxy nexus owners

Edit. Sorry 200 is it

sent from my precious nexus
[Samsung Galaxy Nexus] ranasrule:
i havent been able to get the app to stick settings since version 5.61....not sticking with version 5.7 and SuperSU either :(
[Samsung Galaxy Nexus] mike216:
I would try a different rom if it's a big deal. I have no issues.

sent from my precious nexus
[Samsung Galaxy Nexus] ranasrule:
I have tried on both LiquidSmooth and SlimICS :confused:

the thing I have notced is that with 5.7 at startup I dont seem to get the message indicating that the app has been granted SU permissions whereas with 5.6.1 I always get that message...but then again i dont know if that would make any difference sine when i open up 5.7 after restart the settings are back to default anyway
[Samsung Galaxy Nexus] mike216:
I've had much success on jellybelly

sent from my precious nexus
[Samsung Galaxy Nexus] ranasrule:
Im waiting until the custom ROMs start coming out after release of source code before switching to JB
[Samsung Galaxy Nexus] mike216:
I'm fairly confident when source hits soon all these minor issues will be a thing of the past. Hang in there a week or so bud!
[Samsung Galaxy Nexus] ranasrule:
source for JB ? How will that affect the issues the app is having with ICS ?
[Samsung Galaxy Nexus] T-Loop:
I once had an issue with settings not stick, I cleared data on Franco's app and it started to rock'n roll again. I guess uninstall and reinstall does the same trick.
[Samsung Galaxy Nexus] Myster:
Don't know if this helps but i managed to get settings stick by

1. Clearing all Cache & Data from Franco.Kernel Updater Application

2. Boot into Recovery and Clearing all /Cache and Dalvink Cache

3. Reboot

** EDIT **

Well on a second thought i do not know if this is what helped ...

I noticed that settings stick when

1. i first set a Franco Power Mode ( any )

2. uncheck Set power mode on boot

3. Manually set my CPU settings & Governor

4. Check Set CPU Settings on Boot
[Samsung Galaxy Nexus] mike216:
Developers will have everything working in short

sent from my precious nexus
[Samsung Galaxy Nexus] mike216:
sent from my precious nexus
[Samsung Galaxy Nexus] splus:
Franco, it looks like there's no end to problems with settings not sticking on boot for many users.

Older versions of your app had no problems at all with settings sticking on boot, this happens only in newer versions of your kernel app. I suppose you implemented some changes there, which unfortunately are not working good for many users. But the thing is that some apps like SetCPU work OK with SAME ROM setup, so it's not just user's thing.

So here's a suggestion (I don't know if it is practical or doable for you though) - how about changing the code that sets the settings on boot in your app back to way it was before, when everything worked OK?

It just seems to me that the way the current kernel app sets the settings on boot isn't compatible with many ROM setups...
[Samsung Galaxy Nexus] ranasrule:
yeah I second that...if its possible
[Samsung Galaxy Nexus] The Gingerbread Man:
And you tried flashing supersu 0.93 as suggested a few pages back?

http://db.tt/bMvKpAM3

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] ranasrule:
Yup...that didn't help either
[Samsung Galaxy Nexus] arhung:
My phone keep losing 5% battery for one hour, not bad. But still wondering can it be batter?
[Samsung Galaxy Nexus] The Gingerbread Man:
If I were you try to wipe Franco app data, uninstall it. Reboot, download the Franco app again, download the kernel you want again, boot to recovery, flash kernel, flash the supersu 0.9, boot up, go to supersu app and allow it to download new binaries, go to Franco app set your stuff up then reboot. I'll be damned if it still doesn't.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] garu12:
SuperSu .93 did the trick over here. Settings stick no problem (Bixies Jb)

More importantly 217 seems smooth and solid. No crazy 2ghz oc or anything. Slight oc and color tweaks only. Can't judge battery yet but hopefully that has the Franco touch ;) Thanks and keep it up.
[Samsung Galaxy Nexus] derPianist:
Solved Problem for me! Oh my goodness. DAAAYAAAM!

via Google Galaxy Nexus