yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] franciscofranco:
When the app starts it sets permissions to max/min/governor files because if its not readable then the app force closes (blame google on that one for setting non-readable file permissions) - nothing more.

In the Boot service of my app I do one command at the time, first a try/catch for the colors, then another try/catch for the cpu stuff and so on. They just work independently of each other. Get me a cat of this file /data/data/com.franco.kernel/shared_prefs/com.franco.kernel_preferences.xml paste it on pastie.org and link it here please.
[Samsung Galaxy Nexus] kecinzer:
With M5 and R246 I have lot of data drops. It's happening when I changing network form 2G to 3G and otherwise. For bring data back I have to reboot phone. Airplain mode don't help. I think, that this problem starts before M5, but I don't know exactly when.

At first I think that this is AOKP ROM issue, but I flash it without franco kernel and now I don't have any data drops.
[Samsung Galaxy Nexus] joaquinf:
I experienced the same when i flashed m5 but i flashed the update.zip from ARHD, which contains a new radio (I9250XXLF1 is my baseband) and the issue is gone. Data connection is rock solid now
[Samsung Galaxy Nexus] GIKE:
Same issue here but with jellybro, now I'm on aokp and lean kernel, and looks better..
[Samsung Galaxy Nexus] kecinzer:
joaquinf: I have this radio since JB was released (july).

GIKE: Thank you for info, I was afraid, that I'm alone with this issue.
[Samsung Galaxy Nexus] joaquinf:
Well it was worth mentioning, i thought it could've helped :o i'm sorry for the outdated info, it's been 12 hours since i got my phone :p
[Samsung Galaxy Nexus] J-Hop2o6:
Looks like its not the SU apps since other SuperSU users are reporting issues also. Plus I never had an issue with SuperUser so I'll stick with it (plus it looks nicer :p).

Thx for the insight. But everything worked fine before the latest update. Can u post the last working version (6.2?) since 6.3 is having stick issues? And I would like to do a logcat for you, but how do I do it for that specific file? Or do I just open it up and look inside of it?
[Samsung Galaxy Nexus] Marreboy:
I also have some issues with data drops on 246.

I didn't have issues with previous nightlies or milestone 5. I have latest jelly bean radio.

The interesting thing is that data speeds on 246 seems a bit better than earlier kernels, but then suddenly it drops the connection and the app which is using it gives an error message about lost data connection. It looks like it has problems initiating data upload and that is where it drops.

I am on 3 network so I only have 3g connection (10 Mbit hspda+) , no 2g at all.

Tapatalked from my Nexus 7
[Samsung Galaxy Nexus] marcuso:
I don´t think its the file as several wipes, app-data-resets, etc .. have recreated the file anyway ... but here you go:

(looks fine to me)

<?xml version='1.0' encoding='utf-8' standalone='yes' ?>
<map>
<string name="screen_max_freq">729600</string>
<string name="blx">100</string>
<string name="min_cpu">384000</string>
<boolean name="fsync" value="true" />
<boolean name="cpu_boot" value="true" />
<string name="download_path">/storage/sdcard0</string>
<string name="gov">wheatley</string>
<string name="max_cpu">1305600</string>
</map>

EDIT: The above was taken before reboot - after reboot that file is back on default settings again ??!

(have done nothing but reboot and re-open the app after that)

<?xml version='1.0' encoding='utf-8' standalone='yes' ?>
<map>
<string name="screen_max_freq">729600</string>
<string name="blx">100</string>
<string name="min_cpu">384000</string>
<boolean name="fsync" value="true" />
<boolean name="cpu_boot" value="true" />
<string name="download_path">/storage/sdcard0</string>
<string name="gov">interactive</string>
<string name="max_cpu">1228000</string>
</map>

EDIT2: doing the same thing again and found that the file still has my own settings directly after reboot - before opening the app! (even if they are not applied!) ... as soon as I open the app again - the file gets resetted to default values ?!

Looks like some parsing issue or so ?! .. but strange that only few people have that.

EDIT3 (maybe it helps debugging): other settings (e.g. fast charge) survive properly, whereas color-gamma settings do get reset with boot (not sure if they are supposed to survive though - even if they seem to stay in the xml!? - color multipliers seem to be set correctly at boot (only command SuperSU logs) and stay both in the file and app.
[Samsung Galaxy Nexus] parkson:
Frequencies being reset by rom is a "powerHAL" issue, according to kernel developer Faux.

I'm no developer so I have no clue what that means. Anyone knowledgeable on the matter mind shedding some light for us?
[Samsung Galaxy Nexus] Astug:
Just got my GNex and I'm very happy with it. Great kernel and awesome app! However, the "set CPU settings on boot" does not work. Stock frequencies are set every time I reboot.

EDIT: Sorry, just noticed this has been posted before. Just figured I should report it but I guess I'm not the first. :)
[Samsung Galaxy Nexus] J-Hop2o6:
Yea, just try to avoid rebooting as best you can until this is worked out.
[Samsung Galaxy Nexus] leets4uc3:
My CPU sticks on boot and power mode didn't fc the app. Don't know what's going on with u guys.

I lost my interactive settings :( I had to guess what I had before :/
[Samsung Galaxy Nexus] creeve4:
I'm running CM10 with SuperSU, r246 and version 6.3 of the app. All kernel/color settings are correctly reapplied after every reboot.
[Samsung Galaxy Nexus] franciscofranco:
Ok I'll open my book a little bit, after all this is a development forum. Before I go try to fix whatever I broke, this is the code I use in the bootservice to power up the cpu frequencies:

final String max = preferences.getString("max_cpu", null);
final String min = preferences.getString("min_cpu", null);
final String gov = preferences.getString("gov", null);

This gets the previously saved freqs to the variables. If no freq was saved they are null.

if (preferences.getBoolean("cpu_boot", false)) {
if (max != null) {
root.run("echo " + max + " > " + MAX_FREQ);
} if (min != null) {
root.run("echo " + min + " > " + MIN_FREQ);
} if (gov != null) {
root.run("echo " + gov + " > " + CUR_GOV);
}
}

This checks to see if the variables are null or not. If they are not null I'll run the shell command. As simple as this, and it works fine on my GN.
[Samsung Galaxy Nexus] billykxda:
Back to Franco kernel after exploring Trinity.

Running 246 on VZW GNex and it's stable, fast, smooth and doing GREAT with battery.

Francisco: just don't "Fix" 246 tooo much. :)
[Samsung Galaxy Nexus] franciscofranco:
I pushed 6.3.1 some while ago hoping to fix some of those bugs. Minooch tried it and reported no issues.
[Samsung Galaxy Nexus] Savant:
Yup it works flawlessly and you do a great job Franco.
[Samsung Galaxy Nexus] franciscofranco:
Eheh. Still not good enough. r248 coming in 5...4...3...2...1...
[Samsung Galaxy Nexus] Savant:
You are the man and can't wait to see what this one holds. :D
[Samsung Galaxy Nexus] nnnnr14:
.......... Lol I was actually looking for it :mad:
[Samsung Galaxy Nexus] Savant:
Lmfao so was I ... he's a crafty one. :beer::what:
[Samsung Galaxy Nexus] osm0sis:
Soon enough though, I'm sure! The man is unstoppable. ;)
[Samsung Galaxy Nexus] Savant:
Lol right. He is definitely a kernel guru like faux123.
[Samsung Galaxy Nexus] hotnikkelz:
Ok nightly 246 is crazy good. Crazy good. Congratulations
[Samsung Galaxy Nexus] franciscofranco:
That I agree. Hope that r248 (uploading to the server...) is even better.
[Samsung Galaxy Nexus] franciscofranco:
r248:

* Fix bug on CM10 where the settings crashed when trying to access storage menu

* Merged another newer Wi-Fi driver

* Merged more patches from android-omap-3.0

* Corrected voltage derp on 230Mhz slot
[Samsung Galaxy Nexus] Savant:
Sweet, I thought you were just teasing.
[Samsung Galaxy Nexus] nnnnr14:
Flashing in 5...4...3...2...1
[Samsung Galaxy Nexus] kashix:
Dling IN 5...4...3...2...1...
[Samsung Galaxy Nexus] LNJ:
Settings in the Governor Control keeps changing every time I go into it even after changing it.
[Samsung Galaxy Nexus] parkson:
Sorry to hear but I'm glad I'm not the only one. Just rebooted a third time trying to figure out where it's going wrong.
[Samsung Galaxy Nexus] JRJ442:
Me too, seems like my color control settings don't wanna stick either
[Samsung Galaxy Nexus] LNJ:
I switched back to AIR kernel and the Governor Control settings stick just fine.
[Samsung Galaxy Nexus] ac3theone:
My undervolt isn't sticking on reboot. I'm milestone 5
[Samsung Galaxy Nexus] whittikins:
go_hispeed_load is changing

I'm noticing that in 248 with the latest franco app, the governor settings for interactive sometimes show go_hispeed_load at 70, and other times I check it's 95. I don't have any other apps or ROM controls that change governor settings, so I don't know why it's changing.

I'm running AOKP build 1, but I haven't noticed this fluctuation in previous kernels. Should it be 70 or 95 by default? It seems like I remember it being 50 in earlier builds.

Thanks

EDIT: I'm also noticing that hispeed_freq is usually max (12xx), but I just checked and now it's 384,000 (after changing from ondemand, then back to interactive).

Edit 2: this is in 248, not 246 like I had posted first. Sorry!
[Samsung Galaxy Nexus] JRJ442:
I believe Jelly Bean is 50 anyway by default. I went back to 246, all seems well again.
[Samsung Galaxy Nexus] Hungry Man:
I'm running AOKP 1 but it doesn't change the settings. Thta's weird.

50 is the default too... I think. Which makes it weirder.

---------- Post added at 06:10 AM ---------- Previous post was at 06:06 AM ----------

Wow, yep. Having that problem now too. Can't clock down to 230mhz either. This one seems very broken - I recommend anyone on 246 stays there.
[Samsung Galaxy Nexus] whittikins:
Yeah JB default is 50, but I'm curious what Franco is intending to use for all the Interactive governor settings.
[Samsung Galaxy Nexus] larkhillv:
Just flashed. Running on Lazy and deadline. Seems zippy and stable so far. I'll report back on battery life tomorrow. Thanks, Franco.
[Samsung Galaxy Nexus] schizophrenia:
i noticed after flashing this r248 the "hispeed_freq" of interactive went back to 1305600 instead of the previously 729600.

is this intentional?﻿
[Samsung Galaxy Nexus] luckylui:
For all the peeps here asking about the loads and what they are.. check this out.

http://rootzwiki.com/topic/13092-leankernel-minimalistic-kernel-jb-430-81912/page__st__11550

Galaxy Nexus HSPA+
[Samsung Galaxy Nexus] 15israellai:
Am I late to the party? Firing up 6.3.1 for 248 in 5...4...3...2...

Blazing on my Nexus Prime
[Samsung Galaxy Nexus] marcuso:
well ... I am not a developer and believe you that this should work, but for some reason it doesn´t for different people.

I don´t see any explanation as well - and am also confused how this can be ;)

maybe this helps: I just tried new app-version:

now max-CPU sticks, but governor not .. and now color-multipliers are not sticking any more (that use to stick before!).

Logging with SuperSU again shows that now the only command after boot is the MaxCPU one (not color multipliers as before)

This is getting weird!

As i don´t like the default color-multipliers - this is becoming a deal-breaker for me now ...
[Samsung Galaxy Nexus] J-Hop2o6:
So much win!

EDIT: Guess I gotta pump my brakes until the reports are sorted out.
[Samsung Galaxy Nexus] Hungry Man:
What's the exact frequency? 729X00 or something.

edit: Eh, it's just not working.
[Samsung Galaxy Nexus] cassius_20:
Been running v4 minco/m5/6.2.0 no issues whatsoever. Settings stick like no tomorrow. Excellent battery life overall.

However, been seeing some weird issues after updating to 6.3.1 with r246 or r248. Particularly, min 230 not sticling and governor controls changing randomly/not sticking after reboot (hispeed_freq and go_highspeed_load particularly). At first, thought it was Supersu so updated to latest version, rebooted, but still does not stick. Flashed either version but still would not stick. Yes, flashed properly each time (wipe cache/wipe dalvik/reboot back to recovery and repeat wipe again/flash kernel/wipe again for good measure/fix permissions/reboot). I've even gone so far as removed both SuperSU and Franco app and reinstalled but still would not stick. Uninstalled Franco, used SetCPU pro as a test, checked governor controls and was also acting weird/not sticking.

I can recreate this symptom. Only thing that I did not test was use 6.2.0 to download/change gov controls of 246/248 to see if it sticks. At this point, I'm not sure if its one of the 2 kernels or if it has to do with the latest app updates. Franco, which logs (if any) would be helpful on diagnosing this?

BTW, I've left 5 stars already for the app; not like those dicks that left stupid stars/comments recently because they're too lazy to follow this thread. Keep up the good work, cant wait for an n7 version of your app, r3 is awesome!
[Samsung Galaxy Nexus] ceejay83:
Same problem here, interactive governor settings keep fluctuating
[Samsung Galaxy Nexus] k_nivesout:
I can report that the fix for storage settings in CM10 worked great! However there were some issues that I was running into with settings changing and overall lag and choppiness (

possibly related).
[Samsung Galaxy Nexus] marcuso:
Just to add: using SetCPU works just fine (sets everything as configured at boot) ... so it unlikely it is something else messing with the settings.

(of course i have always been running one app at a time - either francos or setCPU)

But strangely I have similar problems with Glados Kernel and its app (settings also are not set and config-file gets resetted to default as soon as the app is opened again after boot)

weirdo ;)

I guess I will write my own init-script now ... don´t change settings often - so that would work as a workaround I guess.
[Samsung Galaxy Nexus] gianton:
With latest updater app v6.3 after a reboot my custom color settings go back to default.

I'm on milestone 5.

Anyone else noticed this?
[Samsung Galaxy Nexus] franciscofranco:
Interactive settings changing by itself is normal, I merged a patch to test overal reaction, but I guess everyone is more interested in checking if the values are changing/not changing instead of actually testing out how it feels...
[Samsung Galaxy Nexus] nnnnr14:
My phone is running like a champ on #248. If I could I would go to the Verizon store and flash this on all the gnexs in the store!

I got 99 problems but bamf ROMs ain't one! -nnnnr12
[Samsung Galaxy Nexus] nemotheblue:
Franco, could you explain what this means, please? If that behaviour is intentional, a little explanation might prevent more people from complaining about a "governor settings not sticking" bug. I haven't updated/rebooted yet, but that would have set off alarms with me too :eek:
[Samsung Galaxy Nexus] gianton:
I have trinity kernel flashed with CM10, can I just flash #248 kernel or do I need to reflash the ROM and then the kernel?
[Samsung Galaxy Nexus] six_dfx:
Latest app and r248 flashed few minutes ago, after reboot only the min/max CPU freqs are set, color control and governor are set to default although the settings appear OK in the app.
[Samsung Galaxy Nexus] osm0sis:
Feels a bit zippier with the new defaults! Settings were sticking fine for me but I disabled set cpu/governor to give it a whirl.

Edit: Whoa, now I see the settings issue, governor stuff went all over the place. 70 to 95 for load and hispeed went from matching maxcpu to 729 and back.. Sounds intended; are these like SR for governor settings?
[Samsung Galaxy Nexus] nnnnr14:
Wipe cache and dalvik then flash kernel.

I got 99 problems but bamf ROMs ain't one! -nnnnr12
[Samsung Galaxy Nexus] joeyfong:
so no need to check set governor control?
[Samsung Galaxy Nexus] franciscofranco:
Its not an issue thats due to a new patch I introduced but I didnt say anything about it to see people reaction.

Anyway please people compare r248 with this test r249:

http://db.tt/EBOShxOq

The file is big because thats a direct backup from my device since Im out from home for a few hours.
[Samsung Galaxy Nexus] gianton:
Thanks!
[Samsung Galaxy Nexus] nnnnr14:
Will flash after school.

I got 99 problems but bamf ROMs ain't one! -nnnnr12
[Samsung Galaxy Nexus] Marcb:
Francisco, I'm curious on where you get those new wifi drivers! :)

thanks man!! nice job!
[Samsung Galaxy Nexus] osm0sis:
I'm guessing scaling based on load? Like once 50 is reached it hits 1037, then 70 -1228, 95 - max? That would explain what I'm seeing. min_sample changes too, probably in an attempt to keep it from maxing out too easily. So my guess would be right then, sort-of a SR for governor settings. Very cool, I take it 249 has an override for those who want to tweak every little detail. Great idea. Checking it out now.
[Samsung Galaxy Nexus] billykxda:
Is moving to SuperSU just a matter of buying the app off the market? Installing it will replace SuperUser? How does one delete what's left of SuperUser from system directories?

Thanks in advance!

-bk
[Samsung Galaxy Nexus] osm0sis:
SuperSU is free, but has a Pro license just like SuperUser which enabled settings like PIN activation. SuperSU actually has a setting to allow you to choose your superuser app (ie. switch between SuperSU and SuperUser if both are installed) but I'm not sure how well that works in reality so it's probably better to have only one at a time.

Might as well start by installing SuperSU from the Play Store, it will take effect once we've done everything else. To remove SuperUser, it depends how you installed SuperUser. If you installed it from the market only then you should be able to simply Uninstall. If you flashed it/use a ROM with it in system/app/ then you'll have to adb shell in and rm the SuperUser.apk from there. While adb shelled in you'll also need to rm the corresponding su binary belonging to SuperUser. It is either in /system/bin/ or /system/xbin/, again, depending on how it was installed. Once you've removed that, adb push the SuperSU su bin (from the CWM zip) to /system/xbin/ and then adb shell to chmod 06755.

You could also just flash the CWM zip once you've got SuperUser removed, but I prefer to not have things under my system/app/ if they don't need to be, that way you can uninstall/reinstall via the Play Store if you need to at some point.

Hopefully that's some help? :eek:
[Samsung Galaxy Nexus] billykxda:
Thanks osmOsis. Will take a re-read. Plus, I think you responded to another thread I started on this subject. Gotta go re-read that one as well. I'll report back.

---------- Post added at 08:30 AM ---------- Previous post was at 08:21 AM ----------

OsmOsis:

I have a thread on this topic here

Someone else responded with slightly different suggestions. If possible, can we take this discussion there so as not to take Francisico's thread OT?

Francisco:

Running r248 on VZW GNex. Perfect. All previous settings persisted between flashes, even though I wiped cache/Dalvik. Don't know how that happens, but I don't mind!

-bk
[Samsung Galaxy Nexus] gm007:
Download supersu from playstore,open it and update the binaries then go to system/app and delete superuser.apk

Reboot and now all the apps that need root access will use supersu.

easy?
[Samsung Galaxy Nexus] osm0sis:
Joesyr is correct, and we both said pretty much the same thing, he just didn't get into the details of adb and was talking more about the way to have both installed works. I think you're all set though by the looks of your last post there, so I won't bother to make a Rootzwiki account today. Probably one of these days.. Maybe tomorrow. ;)

Edit: I wasn't sure that SuperSU could use the SuperUser su binary to install itself, so I gave you the fully manual method, but I'm sure gm007 is right and that way will simplify things a fair bit, just leaving you with adb/root explorer for removing the old SuperUser apk from system/app/.
[Samsung Galaxy Nexus] billykxda:
Very easy.

Thank you!

Edit:

And thanks to OsmOsis too.
[Samsung Galaxy Nexus] timbck2:
It is for me...I just switched ROMs from Liquid to Minco and was a little disappointed at the performance at first with the stock M5 kernel. Then I flashed r248 and I'm very pleased!
[Samsung Galaxy Nexus] Savant:
I don't have problems with 248 since it works well and I don't have any lag when multitasking is a must.
[Samsung Galaxy Nexus] franciscofranco:
So anyone done some testing r248 vs r249_test? They both have different interactive patches and behaviors.
[Samsung Galaxy Nexus] vomer:
Hi franco, New Franco app update is not keeping color settings on boot. I tried re applying them but they always reset on boot.

Edit - looks like others have the same prob.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] spaceman860:
Also battery life extender resets to 100 and fsync keeps turning on

Sent from my BAKED Nexus
[Samsung Galaxy Nexus] yellowdie:
I updated to 6.3.1 (then wiped the app data for good measure), and I just flashed r248. It looks good and my color settings and regular settings stick just fine. The only thing that doesn't stick is the go_hispeed_load, which, according to Franco, is by design, I think.

Franco, I'm gonna try r249 to test it now. With the .img file, do I just throw it in the kernel_backups folder then use your app to do a restore? I'm making a nandroid and trying it now. :) And to stick with the recent theme, I'll throw in a friendly 5...4...3...2...1...
[Samsung Galaxy Nexus] Savant:
Haven't used the test version yet but 248 works great.
[Samsung Galaxy Nexus] osm0sis:
Still feels snappy, but perhaps slightly more microlagging on the Apps/Widgets drawer.. very hard to tell as my usage varies though.. I'll give it some more time and switch back to 248 to see if I notice anything more.
[Samsung Galaxy Nexus] sachilleas:
I see a tremendous change in wifi behaviour with r248! It connects and stays connected in places where didn't before. Thank you so much!
[Samsung Galaxy Nexus] yellowdie:
Okie dokie, Franco. Here's my report. =)

I flashed r249 and my settings stick perfectly fine (even go_highspeed_load, hispeed_freq, and my color settings). The input_boost is grayed out, as I'm sure you're aware (it says 'Not supported in this kernel version'). So for me, I have no issues whatsoever with the app and settings sticking properly.

As far as the kernel itself, r249 feels snappier than r248, but still not nearly as smooth as r246 for me. I haven't UVed it yet, which I normally do. I'm still trying it all on stock to compare. My biggest priority (other than smoothness) is the wifi. And you've got the best work being done on that front--so thank you!

Also, if I install the 512Mhz GPU version, should I disable the Core Smartflex? I don't change the GPU voltages.

Also, Franco, thank you so much for all of your hard work. I love your kernel and your app (it's one of three apps that I've actually found valuable enough to pay for. :laugh: ) I feel like you've been getting bashed for the past dozen pages, and it makes me sad. :( Keep up the great work!

Since I'm writing a short novel, I figured I'd throw out my color settings to people. :) I've played with the color a lot and I LOVE this:

Multi: R200, G150, B250. Gamma: R-8, G0, B8. Disable Content Adaptive Brightness. Trinity: -5. OMAP4 Gamma: 1.2 (or 6) [Alternatively, Trinity: -15 and Gamma: 1.0 (or 5)]
[Samsung Galaxy Nexus] gianton:
Is multi B250 safe? Nice color settings thanks.
[Samsung Galaxy Nexus] ffgf:
One quick question using USB OTG With a NTFS disk is not working, does it depends o kernel or ROM using

Thanks
[Samsung Galaxy Nexus] yellowdie:
I've been running this for a week or two and haven't had any issues. And thanks.
[Samsung Galaxy Nexus] L-ViZ:
could someone post the colour-config, which was suggested in the app? can´t remember, used them + trinity -16. was a bit darker, better white than in the previous post.

@franco: or include them again in the app. :) or as an info with menubutton :)

thx in advance :)
[Samsung Galaxy Nexus] nikulogical:
180 192 200

-4 0 5