yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] The Gingerbread Man:
Nope no other CPU altering apps here, no init.d scripts or anything else like that. Just got minco ROM, 248 kernel, v5 audio mod by Vomer, using latest supersu with updated binaries. For now my settings are sticking using 6.2 of francos app and I'll be sure to keep the back up and try either versions as they get released. Thanks for the suggestion / advice :thumbup::)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] sruel3216:
does anyone actually use the performance gov? it is so ****in smooth. but is it practical for everyday?
[Samsung Galaxy Nexus] yellowdie:
:eek: Well, I'll be! (I don't know what that statement actually means, but oh well). Oh my gosh. I spoke too soon, 'pparently. :( My wife's Gnex has now decided to cease cooperating with me--I'm now having her settings not stick on boot. LOL. I've been preaching for a few pages and now the plague has reached me as well! I'll quarantine her phone so mine doesn't catch it--I like having my settings stick. :p

So I just switched ROMS with hers. She was on AOKP (as I am right now), and I just switched her to Rasbean Jelly. After doing a fresh install, its not working anymore. :( I used MyBackupRoot to restore the apps and data, then I updated from 6.3.1 to 6.3.2. Now it's being a butt head. I've cleared the app data and rebooted--no dice. *sigh* lol. Oh the irony...

Franco, anything I can do to help? I have a phone that works and a phone that doesn't. Would aLogcat (etc.) help with anything? Feel free to PM me if you would like anything. I may hop back over to a nandroid of her AOKP. Maybe it's something ROM based. :/
[Samsung Galaxy Nexus] osm0sis:
You should see if you can restore franco.App 6.2 from an old nandroid to test TGM's theory.
[Samsung Galaxy Nexus] ceejay83:
did you install busybox? dont think rasbean comes with it. same goes to gingerbread man, might need busybox
[Samsung Galaxy Nexus] timbck2:
Same hardware, same OS, same kernel, but everyone has a different set of apps installed, etc. It could be almost anything.
[Samsung Galaxy Nexus] J-Hop2o6:
Still getting unsuccessful sticks Franco. What's different compared to 6.1 (the last one that worked).
[Samsung Galaxy Nexus] yellowdie:
Rasbean did come with Busybox, but I removed the version it had (deleted the apk from the zip before even flashing the rom) and installed it from the Play Store manually before the issue even came up. I always run a Busybox Smart Install when I do fresh install (or any install).

I totally agree. And in my case, I have two identical phones, with almost identical everything, and both sides of the coin apply. lol.

Negative. I flashed my wife's phone back to the nandroid I made today of AOKP--and I KNOW that it was working (on 6.3.1) when I made the backup. Well, now it's not working. W H A T . T H E . H E C K ? ! lol. :silly::confused::eek:
[Samsung Galaxy Nexus] cassius_20:
I restored to 6.2 and everything is sticking like butter so +1 on this. Currently on r246. When using 6.3.2., that's when it acted funny.

Nexus 7/R3 biaaatch
[Samsung Galaxy Nexus] frenchy714:
Dynamic Interactive was implemented as of 248 nightly, correct? It's not an actual gov name, but rather new features added to the Interactive governor?
[Samsung Galaxy Nexus] osm0sis:
Franco has had busybox built into the App for awhile now so that shouldn't make a difference. :(

Edit: Found it.
[Samsung Galaxy Nexus] Swint:
My options won't stick on boot any more since last update... :(
[Samsung Galaxy Nexus] osm0sis:
Read the last page or two before posting next time, please. That issue has been thoroughly reported, and we are now working out where things went wrong.
[Samsung Galaxy Nexus] vomer:
Hey franco - just reporting in that the new app update still does not seem to keep color settings on boot.

Also, people stop rating the app badly - patience guys... **** happens lol.
[Samsung Galaxy Nexus] yellowdie:
lol.
[Samsung Galaxy Nexus] vomer:
Not quite

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Pkt_Lnt:
Here are the Optimum colors and defaults for most kernels that support color choice.

https://docs.google.com/spreadsheet/ccc?key=0AmUsanWh1BpZdENqZ0FPQmRnUEs3SHBON1VsU3BmN0E#gid=0
[Samsung Galaxy Nexus] yellowdie:
Well Franco, I've been messing with this for about three hours now, but I'm going to bed now. Like others, I went back to a back up (v6.0) and it worked. Updated to 6.3.2 and it stopped working. :( I've tried every combo of trouble shooting I can think of--no joy. My phone still works fine, my wife's phone doesn't. Yippee... :rolleyes:

It's almost 1am for me, so g'night, y'all.
[Samsung Galaxy Nexus] gianton:
Color settings are not kept after a reboot, latest app 6.3.2 and #r248.

Thanks
[Samsung Galaxy Nexus] CADude:
I gotta say. Some of you guys have to be doing something painfully wrong because I'm running r248 on a clean install of Minco v4 and all my color settings stick on a reboot.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] yellowdie:
That's what we're trying to figure out. My wife and I both have Nexus' (I work on both myself); mine works with 6.3.2 on r248 and r249, but my wife's doesn't now (see previous posts).
[Samsung Galaxy Nexus] vasumit:
Finally purchased this great app to support the Dev.
[Samsung Galaxy Nexus] nzmn81:
r248 is the best .. thanks
[Samsung Galaxy Nexus] :
No problems so far, all values are sticking how they should!

6.3.2 and 248

Sent from my Galaxy Nexus running cm10
[Samsung Galaxy Nexus] gianton:
Even color settings? Mine are lost in every reboot, strange...
[Samsung Galaxy Nexus] :
yep, even color settings! funny
[Samsung Galaxy Nexus] gianton:
please share your step by step installation and setup of kernel updater app.
[Samsung Galaxy Nexus] asmodea:
I have R200 Franco kernel and an old Manhattam ROM, I tried to install millestone 5 but I bricked my phone so I was obligated to install again R200, so now all ok whit my phone, but I would like to ask what is the right way so I could intall millestone 5 so I can boot and use my phone. Thank you
[Samsung Galaxy Nexus] gm007:
5-6 pages about settings not saved,did one of you tried a fresh rom install with full wipe???
[Samsung Galaxy Nexus] gianton:
i did, but still no luck... only the color settings (1st two settings) are loosing their settings after a reboot.

cm10 latest rom, 6.3.2 kernel updater, r248 kernel.

tried on stock jb rom with same results.
[Samsung Galaxy Nexus] Bl4ck3urn:
I see your mistake. You're still on ICS. So r200 is an ICS kernel.

Please upgrade to a JB Custom Rom. Afterwards you are good to go to flash M5!
[Samsung Galaxy Nexus] asmodea:
Thank you for your advice, I have one more question: can u or anybody post a link with a JB custom kernel ? THX.
[Samsung Galaxy Nexus] Bl4ck3urn:
Well, M5 is a JB Custom kernel :silly:

Links are on OP.
[Samsung Galaxy Nexus] andQlimax:
Must be a ROM issue, on stock jb ROM with supersu and busybox everything stick here

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] Swint:
I'm on stock and nothing sticks.
[Samsung Galaxy Nexus] andQlimax:
So u set CPU to max 1305 for example (first set power modes to none to avoit other situations), flag the option "set cpu settings at boot", reboot the device, open the app and max CPU is not 1305?

Do u have other set CPU apps?

Edit: I'm on latest app and M5 and stick, maybe a problem with latest nighty kernel

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] RevengeFNF:
Franco Kernel Updater 6.3.2 + R248 + SuperSu

Max Cpu - Not Sticking after reboot

Maximum Frequency for Screen off - Not Sticking after reboot

With R246 they were Sticking.
[Samsung Galaxy Nexus] franciscofranco:
Well this not sticking business is wizardry. My mac fried last night, by some ****ing "miracle" water dropped into it so there might be one or two days before I can try to fix again that app boot service problem.
[Samsung Galaxy Nexus] franciscofranco:
I remembered something, people with problems of app settings do you have fsync enabled or disabled?
[Samsung Galaxy Nexus] mrm43:
I'm on m5 and previously my color settings would stick , now they don't. I am not sure if it was 6.3.2, but it's just minor i am sure you'll fix it. Anyway your app still rocks. No worries.
[Samsung Galaxy Nexus] osm0sis:
A couple people have had success rolling back to 6.2 if that helps you narrow down the problematic code changes.

On the kernel front, I'm still loving r248 and feel it's smoother and faster than r249_test.
[Samsung Galaxy Nexus] hotnikkelz:
@franco Next time use windows :p I have nothing valuable to contribute. I'm still on 246 because it is just that damn good. I'll give 248 a look see today
[Samsung Galaxy Nexus] gianton:
How can I roll back to 6.2? I haven't got a back-up.
[Samsung Galaxy Nexus] RevengeFNF:
I have it enabled.
[Samsung Galaxy Nexus] hotnikkelz:
Ok tried to flash 248, phone froze on boot :) had to go back to 246
[Samsung Galaxy Nexus] The Gingerbread Man:
Not good sorry to hear about your mac! For info my fsync is enabled

Sent from my Galaxy Nexus

---------- Post added at 01:09 PM ---------- Previous post was at 01:00 PM ----------

With difficulty. No one can share theirs as its a paid app (by sharing it means piracy and breaking xda rules) even though you bought it legitimately.... I'd ask Franco in PM for advice on that one.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] gianton:
I'll sent Francisco a PM thanks.
[Samsung Galaxy Nexus] gaich:
As for me, I`ve created my powermode and all the settings are the same after every reboot with all FKU versions ("Set power mode on boot" is ON). Running 248 and 6.3.2 now. Don`t know about colors, I do not touch this section (no need - the colors satisfy me...).
[Samsung Galaxy Nexus] nnnnr14:
Did you not read what I said?

I got 99 problems but bamf ROMs ain't one! -nnnnr12
[Samsung Galaxy Nexus] Flukester69:
Don't know about others but since after 241 I've been getting a lot of gray bars. I rolled back to 241 and its not happened since.

Brought to you by my Galaxy Nexus using Tapatalk.
[Samsung Galaxy Nexus] JRJ442:
Doubt that's kernel related, even though it seems like it. The kernel wouldn't effect Google sync stuff. I've never had that happen. On 248 now.
[Samsung Galaxy Nexus] hotnikkelz:
Nope I didn't. Just reported a problem I experienced. What did you say?
[Samsung Galaxy Nexus] osm0sis:
When you report a problem you should at least try to fix it first and report on that, or you might as well not waste our time and space in the thread.

Did you at least try clearing the cache and dalvik? That has fixed it for many.

For some others like nannnr12 simply waiting it out (up to 10min) allows it to fully boot the first time and then it works normally thereafter.
[Samsung Galaxy Nexus] nnnnr14:
After a kernel flash it will take a while to boot. Just let it do what it does trust me its worth the wait.

I got 99 problems but bamf ROMs ain't one! -nnnnr12
[Samsung Galaxy Nexus] tyraelasd:
I just want to report that I'm not able to reduce the frequency when the screen is off in your app, I just can increase it
[Samsung Galaxy Nexus] Flukester69:
So how do you explain that when I went from 248 that had same problem in 246 and then put 241 on and it went away instantly. I say its WiFi/mobile and WiFi is in the kernel and Franco has updated the driver several times.

Brought to you by my Galaxy Nexus using Tapatalk.
[Samsung Galaxy Nexus] mikeandjaimie:
If it was the wifi drivers you wouldn't be able to connect to your wifi at all, or have drops/low signal.. Grey bars means you are connected to wifi just fine but having issue with your connection to google services.
[Samsung Galaxy Nexus] franciscofranco:
Ok I got some more ideas to fix whatever is derpped for some but not borked for others. I'm setting up another computer to work later at night.
[Samsung Galaxy Nexus] Savant:
You're definitely a relentless guy when it comes to pleasing people. :beer::D
[Samsung Galaxy Nexus] tyea:
CNA 08/31 nightly + Franco 248, 384 gpu with cpu oc to 1420 , all other settings are untouched. My CPU temp is cooler at this setting than stock max CPU. Scrolling is smooth.

I'm using the latest Franco 6.3 kernel updater. I noticed if I check the improved sound performance feature, the voice recognition using Google Now degrades significantly. If I uncheck the sound performance, voice recognition returns to excellent performance.

SPH-L700
[Samsung Galaxy Nexus] yellowdie:
I tried both on and off. I also toggled Logger on and off and tried variants of those both. I tried 'Set CPU on Boot' and using a custom Power Mode.

I definitely agree. My phone that works, I was on r249 (had a happy moment and thought that might be the key, but it wasn't); I flashed back to r248 and it's definitely smoother now. And my settings are still sticking on my phone (I have fsync off).
[Samsung Galaxy Nexus] >stylz:
I dunno, why but the Kernel Version is always unknown....

Gesendet von meinem Galaxy Nexus
[Samsung Galaxy Nexus] bradm23:
Been getting really poor WiFi signal since 248 vs 246. Signal keeps bouncing in and out with 248, in areas where it was string with 246
[Samsung Galaxy Nexus] nnnnr14:
Are using the leaked jb radios?

I got 99 problems but bamf ROMs ain't one! -nnnnr12
[Samsung Galaxy Nexus] wendellc:
Reverted to r241, got best battery life.
[Samsung Galaxy Nexus] coolpages:
With Franco kernel updater 6.3.2, the settings are refusing to stick on boot even when I select it to Set power mode on boot.

Likewise, Battery extender setting refuses to stick as well.

Maybe be good to allow us to revert back to the previous updater unless this has something to do with latest B248

Update:

After updating to Franco Kernel Updater 6.3.3, and using B248, I was still having settings refusing to stick after a reboot.

So I decided to reinstall everything after a clean and wipe as I was dirty flashing the AOKP nightlies and wasn't sure if that was contributing to the problem.

Guess what, I'm happy to report that Settings are sticking after a reboot.

I'm on Franco kernel updater 6.3.3, Franco kernel, B248, AOKP nightlies, Aug 31.
[Samsung Galaxy Nexus] franciscofranco:
I already know what happened since app version 6.2 that causes the issue. Will try to fix it today if I have the time
[Samsung Galaxy Nexus] yellowdie:
Hey, I just flashed r249, r248, r246, and r241 on my wife's phone--still nada. Just fyi. :(
[Samsung Galaxy Nexus] nnnnr14:
Still nada what?

I got 99 problems but bamf ROMs ain't one! -nnnnr12
[Samsung Galaxy Nexus] pnut22r:
Very new here. Love the phone.

You guys like this kernel with jb aokp?
[Samsung Galaxy Nexus] nnnnr14:
We like this kernel with everything!!

I got 99 problems but bamf ROMs ain't one! -nnnnr12
[Samsung Galaxy Nexus] yellowdie:
Sweet!!

I was trying stuff to fix the non-stick stuff on my wife's phone. It was a follow up to my previous posts.
[Samsung Galaxy Nexus] nnnnr14:
Ahh... I see
[Samsung Galaxy Nexus] ssCISengineer:
Good to know...excellent post. That really added great Information to the thread!

please remember to thank me for e-peen points!

Sent from a Galaxy Nexus between here and there.
[Samsung Galaxy Nexus] Hungry Man:
248 gave very poor battery life. Standby/screen off time was draining at least twice as fast as it normally does, maybe more like 3x.

Went back to 246.
[Samsung Galaxy Nexus] nnnnr14:
Did you give it time to settle?

I got 99 problems but bamf ROMs ain't one! -nnnnr12
[Samsung Galaxy Nexus] gm007:
Maybe the battery need calibration.
[Samsung Galaxy Nexus] osm0sis:
From Franco. The device optimizes over a cycle or two with a new kernel flash. Do you plan to continue being so cocky as to contradict him, or do you have something useful to contribute to the thread?
[Samsung Galaxy Nexus] superbobup:
Even though kernels may not need time to settle, the algorithm that estimates the battery level may need time to adjust. The algorithm is probably based on previous data (discharge rates, voltages, etc) and a new kernel may lead to completely different data sets to base their algorithms on. Basically, the data sets may be different which could lead to errors and thus "poor" battery life.

Just a though/conjecture based on my university studies :D
[Samsung Galaxy Nexus] J-Hop2o6:
I was gonna say check out the old version (6.1/6.2?) before all this sticking issues started happening with the latest versions (6.2/6.3+).

You have to let it settle. Its goes back to normal after the 2nd or 3rd cycle. Using r248 now and getting the same screen on time (4 hrs) as previous releases.

---------- Post added at 03:09 PM ---------- Previous post was at 03:08 PM ----------

^^ This and the previous replies.
[Samsung Galaxy Nexus] rmk40:
Hi franco,

Which settings applied by your kernel updater/tuner application persist even once the app is uninstalled?

I was suspecting some of the implementation around color tweaking and/or volume enhancements were occurring outside of kernel tunables; please correct me if I am wrong. The reason I ask is that I suspect I applied changes which were causing complete device lockups. The lockups weren't eliminated after reverting to a completely stock kernel (i.e. fastboot flash boot boot.img directly from Google's image). I' went ahead and flashed a stock system.img as well to make sure I've cleared everything.

Any info would be appreciated. Cheers and great work.
[Samsung Galaxy Nexus] Hungry Man:
I was getting higher clocks. I used it a few hours after it was released. I don't know how much time it oculd take to settle, I used it to browse and do my typical routine. I've also flash previous kernels (like 246) and there was no 'settling' period that I could see.
[Samsung Galaxy Nexus] gm007:
If there is any it should be a script in system/etc/init.d
[Samsung Galaxy Nexus] rmk40:
Not necessarily. If it were that simple I would not have asked. Furthermore the stock ramdisk does not execute the contents of init.d.
[Samsung Galaxy Nexus] gm007:
Did you wiped the cache and dalvik cache after flashing the stock kernel?
[Samsung Galaxy Nexus] Arrio:
248 has some audio issues where music distort and stutters very often.
[Samsung Galaxy Nexus] nnnnr14:
What app do you use for playing music?

I got 99 problems but bamf ROMs ain't one! -nnnnr12
[Samsung Galaxy Nexus] wend0:
There is milestone 5 with 512 MHz GPU overclock?

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] renna1992:
no. use the 3xx mhz version, fast enough :)
[Samsung Galaxy Nexus] Savant:
No there isn't. He only wanted to make one with the lower GPU voltage.
[Samsung Galaxy Nexus] nnnnr14:
If your looking for something with speed download #248 512mhz

I got 99 problems but bamf ROMs ain't one! -nnnnr12
[Samsung Galaxy Nexus] franciscofranco:
Yeah r248 is pretty fast. I believe I'll go with r248 interactive changes rather than r249.
[Samsung Galaxy Nexus] yellowdie:
I agree. And from my novice experience, wouldn't 'input_boost' be better defaulting to 1? Also, why do you like bfq over deadline or sio? Is it actually faster?
[Samsung Galaxy Nexus] franciscofranco:
Ok I just did some reverting and the settings MUST apply on boot now, theres no chance in hell that its broken. I just booted my app into several devices, Nexus 7, SGS3, Hauwei X5, Galaxy Nexus, Note, all stick.
[Samsung Galaxy Nexus] franciscofranco:
input_boost is handled by Tuna PowerHAL, its beyond userspace control. I feel BFQ v4 faster than any other scheduler.
[Samsung Galaxy Nexus] grafyman:
For me the kernel r241 is more stable and have great battery life.... Thanks franco...
[Samsung Galaxy Nexus] rmk40:
Per my question earlier, are any settings persistent outside of the app? As in, one removes the kernel and app, what sticks around?
[Samsung Galaxy Nexus] franciscofranco:
App goes boom all the settings come as default as they come from the kernel. Kernel goes boom... well it will default to whatever app/kernel defaults you set.
[Samsung Galaxy Nexus] rnjsgurwn96:
Is it a good idea to set profiles on set cpu with this kernel? Or will it take care of itself?
[Samsung Galaxy Nexus] nnnnr14:
Profiles suck. This takes care of itself.

I got 99 problems but bamf ROMs ain't one! -nnnnr12
[Samsung Galaxy Nexus] Savant:
They don't suck it all depends on what you are using them for.
[Samsung Galaxy Nexus] yellowdie:
I think what he meant was r248 is dynamic and changes to meet your needs. It's pretty stinkin' brilliant on Franco's part. And it makes profiles not as relevant. :D
[Samsung Galaxy Nexus] creeve4:
What is the governor setting for input_boost in your app for then?
[Samsung Galaxy Nexus] rnjsgurwn96:
awesome thanks
[Samsung Galaxy Nexus] yellowdie:
6.3.3 works! Franco rocks! =D
[Samsung Galaxy Nexus] vomer:
+1 thnx Franco

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] prembox:
6.3.3 #home run!
[Samsung Galaxy Nexus] joeyfong:
AndroidPIT pls.
[Samsung Galaxy Nexus] The Gingerbread Man:
Settings sticking upon reboot here too. Many thanks!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] JRJ442:
I gotta say...This kernel is amazing. So glad I switched = ) App is working perfectly now.
[Samsung Galaxy Nexus] GIKE:
just updated the franco app, and color configuration remains after a reboot :good:
[Samsung Galaxy Nexus] haxor:
Just flash kernel i am in stock jelly bean how can i get utilization of kernel like overclock and all in stock rom ?
[Samsung Galaxy Nexus] gianton:
+1 thanks Francisco!
[Samsung Galaxy Nexus] gm007:
Download franco.kernel updater from playstore.
[Samsung Galaxy Nexus] :
+1

Sent from my Galaxy Nexus running cm10
[Samsung Galaxy Nexus] pen²:
Hi,

In your franco kernel app, I noticed that the latest lean kernel reported as stable is 4.2.0. However, the latest stable is 4.3.0 - I don't know if you determine the latest stable version yourself or if you parse a file from imoseyon.

In addition, it would be nice to be able to download lean kernel releases from the app (at the moment you can only flash them directly)
[Samsung Galaxy Nexus] marcuso:
Wohoooo .. it works again ! :good:

@franco: while investigatin SuperSU logs I found something that might be of interest for you.

While the app is obviously chown-ing/chmod-ing some files before it sets values i found that for some you are chmod-ding to "Root" instead of "root" which fails .. and some of those files don´t seem to be there (maybe depening on kernel version)

Some: examples (logged with SuperSU)

chown Root system /sys/devices/system/cpu/cpufreq/interactive/timer_rate

No such user 'Root'

chown Root system /sys/devices/system/cpu/cpufreq/interactive/min_sample_time

No such user 'Root'

chmod 0664 /sys/devices/system/cpu/cpufreq/interactive/min_sample_time

Unable to chmod /sys/devices/system/cpu/cpufreq/interactive/min_sample_time: No such file or directory

... there are a couple more of those.

However it does not have any effect for me - those files are all root:root for me and the essential settings i want to change are ok.

So for me it is only cosmetic - but maybe not for others ?!

Otherwise: again :good: for keep working on the settings fix. :)

Marcus

P.S. could provide full logs if needed.
[Samsung Galaxy Nexus] haxor:
Thanks but is there any other app for this because its paid app :(
[Samsung Galaxy Nexus] thumm138:
Getting amazing battery life on 248. 2 hours of screen on time and at 64% still!! Keep up the good work Franco you're the man.
[Samsung Galaxy Nexus] eddie_gordo:
You won't regret the money, plus you will be supporting the developer, Francisco Franco. :)
[Samsung Galaxy Nexus] !crazy:
You can edit files and write scripts by yourself. If you insist on app and don't want or can't buy Franco's one try TeicksterMod (IIRC) or RomToolbox.
[Samsung Galaxy Nexus] dannyfly:
i need some help to find out why does my gnex has so many random reboot lately, i dont think ive my uv setting is extreme low but...

happens when i play game, watch youtube, browse with chrome

i've attached last_kmsg

kernel b248 512gpu

my cpu runs at 384-1536mhz, interactive governor, franco's recommended color setting

mpu smartreflex disabled

uv setting

384 850mv

729 1000mv

1036 1100mv

1228 1150mv

1305 1200mv

1420 1250mv

1536 1300mv

*also had this reboot issue back with b246 384 and 512 gpu, both with default volt setting at the time

iva and core volt untouched