yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] gianton:
Updated to #r248 and franco kernel app 6.3.1 on fresh install with CM10 ROM but still my custom color settings don't stay after a reboot.

Any ideas?
[Samsung Galaxy Nexus] yellowdie:
Try clearing the app's data, reboot, set the colors, then reboot again and see. Always wait 2-5 mins after a reboot before touching settings to give them time to post.
[Samsung Galaxy Nexus] J-Hop2o6:
I believe Franco said to just leave the stock voltage alone and let smartflex do its work for you.

As for color settings (I switch up my values every now and then), here's what i'm currently using:

CM

R 173

G 153

B 200

Gamma

R -7

G 0

B 7

OMAP4 Gamma

1.0 (or 1.2)

Trinity Contrast

n/a (0?)

C.A.B. Disabled
[Samsung Galaxy Nexus] gianton:
Tried it but still looses settings: "Color Multipliers", "RGB Gamma". All other settings are kept after a reboot only those two keep defaulting. It started happening with app v6.3.0 and still there with v6.3.1.

Wifi signal strength is the best so far with kernel #r248. Hope Francisco will fix this pretty soon.
[Samsung Galaxy Nexus] Hungry Man:
Anyone else having the issues with 248 where settings don't stick - such as governor settings immediately changing after closing/reopening the interface.
[Samsung Galaxy Nexus] osm0sis:
Yes. The last 2-3 pages are all about that.
[Samsung Galaxy Nexus] Hungry Man:
Ah. My page was showing the last page that I'd posted on as being the last page in the topic - didn't see that.
[Samsung Galaxy Nexus] cassius_20:
Correct me if I'm wrong, Franco said 246/248 has a new feature within interactive in which then settings are dynamic (he posted this a few pages back) ?

I've experienced the random changing of values too in 246 and 248 using 6.3.1. Not sure if it was doing the same symptoms using 6.2 as I didn't notice this behavior till after flashing.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
Its only on r248.
[Samsung Galaxy Nexus] nemotheblue:
Does this mean you intend to remove governor control from the updater app?
[Samsung Galaxy Nexus] Marcb:
Francisco, about these changes to the interactive governor, adding more dynamism to it.... The goal is better performance or battery?
[Samsung Galaxy Nexus] JRJ442:
After reading earlier today the interactive governor settings are intended to fluctuate, I reflashed 248. Been running excellent. Scrolling seems smoother,seems better on battery too. Sorry for doubting you Franco. It won't happen again = )
[Samsung Galaxy Nexus] cassius_20:
Woops, 248 was having the behavior, sorry!

Back on 246 for now; however, CPU max/min (min 230) and gov control not sticking with 6.3.1. Easily recreatable after reboot. Done all the usuals again to make sure (reinstall SuperSU/clear app data and reinstall Franco app) all to no avail. Would dmesg or proc/last_kmesg help in this case?

Nexus 7 biaaatch
[Samsung Galaxy Nexus] clepsy:
R249 that franco posted gave me much faster boot time than r248, at least the start up apps, and think it has a faster ui response, that is all I can say for now
[Samsung Galaxy Nexus] osm0sis:
Franco, I went back to r248, and even at 384GPU it feels faster than r249_test. I feel the WiFi driver in r248 is also giving better/stronger signal over r249_test. I still have to disable 'Avoid poor connections' to keep it stable, but this is the best signal I've had since upgrading to JB.
[Samsung Galaxy Nexus] JRJ442:
What's the fastboot command for that? Fastboot flash kernel 249.img?
[Samsung Galaxy Nexus] cassius_20:
Fastboot flash boot [name of kernel]

Nexus 7 biaaatch
[Samsung Galaxy Nexus] osm0sis:
fastboot flash boot <filename>

or you can put it in the kernel_backups folder and do it from Franco's app.

edit: cassius you ninja! :D
[Samsung Galaxy Nexus] JRJ442:
I was close. Lol. Thanks!
[Samsung Galaxy Nexus] franciscofranco:
The idea of the dynamic interactive tunables is to cater to interactivity when it needs extra power and to slow down when it doesn't need much power at all.

I had this commit back in one of the latest nightlies of ICS.
[Samsung Galaxy Nexus] RoscoeDpG:
damn im still running nightly #240 lol it has been best in battery for me and performance, i think even better on my device then M5.....but....so.....tempted........ah **** it ill flash #248 for few days lol......
[Samsung Galaxy Nexus] Marcb:
nice man... leave it there... don't take it away! :D :good:
[Samsung Galaxy Nexus] yellowdie:
Awesome! I like it!

Also, Franco, does your app have any control over the IO Scheduler? Right now, I use the stock performance options in AOKP to change it to deadline. I'd love to be able to do it all in your app.
[Samsung Galaxy Nexus] kraleksandr:
Paranoidandroid, latest Franco, ntfs works.

Try another ntfs-mounter app, Paragon NTFS as example (just part of app name).
[Samsung Galaxy Nexus] franciscofranco:
Yes will be in the future, my priority now is, again, trying to fix the boot service.
[Samsung Galaxy Nexus] Langduscher:
Sorry for your hard work Francisco, on the interactive gov, but I'm using the performance governor now for laughs and giggles but damnnnn is my Gnex smooth :victory:
[Samsung Galaxy Nexus] willl03:
Got data drop, grey bars on 248, also it seemed less smooth than 246 with my tweaked governor

Back to 246, the best I've ever used!
[Samsung Galaxy Nexus] nnnnr14:
You must've flashed it wrong.. #248 has been the best signal and performance wise for me.
[Samsung Galaxy Nexus] Marcb:
what governor you guys think it's best for battery life? Lazy? Interactive?
[Samsung Galaxy Nexus] franciscofranco:
Get rid of that supercharge script, does more harm than it helps.
[Samsung Galaxy Nexus] Hungry Man:
Is there a way to override the interactive tunables? Now that I know it's not a bug I'll give it a fair shot.

How does it determine the settings?
[Samsung Galaxy Nexus] willl03:
I have a friend on stock Minco v4, we can se how my phone is snappier with the 2 phones next to each other, especially the launcher. Was also true when I was on milestone 5 due to the script. Supercharger memory management is underated

I dont have signal drops on m5 or 246 but my phone has always been sensitive to this if wifi voltage / drivers are modified
[Samsung Galaxy Nexus] osm0sis:
Can't yet to make sure it gets well tested, but I'm sure there will be an option if it gets finalized.
[Samsung Galaxy Nexus] bradm23:
Loving 246 right now. Been running on demand with great results. Been experimenting a lot of other devs kernels and decided I'm gonna stick with Franco like always... :)

I am looking to upgrade to 248 and try out the new dynamic interactive option because I like the theory behind it. If I don't like it and decide to use on demand, is this basically the same as on demanf with 246?

Thanks!
[Samsung Galaxy Nexus] Marcb:
I hate being the last one of the page! :D
[Samsung Galaxy Nexus] Langduscher:
Here you go :D
[Samsung Galaxy Nexus] nnnnr14:
Me I don't care about battery life I just want the performance!!

I got 99 problems but bamf ROMs ain't one! -nnnnr12
[Samsung Galaxy Nexus] franciscofranco:
By the way I pushed 6.3.2 app with more bug fixing. Hope it fixes the problems in the boot service.
[Samsung Galaxy Nexus] rickbosch:
Haven't used a Franco kernel in a while, so giving the latest nightly a go, so far, so good :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] shivasrage:
hello franco

i write you in the play store about some bugs in the updater app...

but i would never give one star rating ....always full rating because i know the lot of work...

is was only a report to you...what happend in my case i hope you dont missunderstood this ...

it is great work ...always been.... always wood...

S.R. :)
[Samsung Galaxy Nexus] Langduscher:
For me 6.3.2 seems to fix the boot service (r248) :good: Thanks for your dedication :cowboy:
[Samsung Galaxy Nexus] olivercervera:
LOVE YOU

Finally I can flash CM10 :D
[Samsung Galaxy Nexus] dracon6ai:
Any issues I have had with settings not sticking I fixed by wiping app data and cache (via settings) then uninstall the app. Reboot my phone and reinstall the app. Set everything back like I had it and everything will stick though reboots no problem after that. And as for changing the cpu scheduler you can use JRummys Rom Toolbox to change it till Franco builds it in.

Laziness is nothing more than the habit of resting before one gets tired!
[Samsung Galaxy Nexus] The Gingerbread Man:
Sorry but I'm still not getting my settings for colour to stick on reboot using #248 kernel and 6.3.2 app. So far I wiped all data from Franco app, uninstalled it then wiped data for supersu and then reinstalled that from the market. Reinstalled Franco app and set values and rebooted.

Then wiped data and uninstalled Franco app and supersu again, reboot to recovery wipe cache & dalvik, flash minco v4, #248, fix permissions and wiped caches again. Set up colour values again and rebooted and again they set back Franco recommended settings mostly and I say mostly as its 180, 192, 205, (forgot exact Franco default gamma values)

What I'm trying to set is 135, 135, 200, (0,0,5 gamma)

Interestingly somehow my blue colour multiple gets set correctly at 200 so I end up with 180, 192, 200 with Franco default gamma

Perhaps this helps somehow?

update 1

just seen 200 is default for blue multiplier

Only other thing I can think of that much help is if I try flashing the latest supersu file as I think it somehow works better than installing from the market. I'll edit this post shortly with my results.

Update 2

Flashing supersu 0.96 didn't make a difference, colours not sticking still

Update 3

I just want to make sure what I'm saying isn't meant to be a negative post or complaint but hoping to leave a constructive feed back providing details of what if tried. I love Francos work :D

Update 4

custom power mode didn't stick on reboot either

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] ffgf:
Thanks but paragon gives me a fuse error, anyone?
[Samsung Galaxy Nexus] The Gingerbread Man:
Updated previous post 4 times.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] arhung:
I don't think so, it seems the problem still here with r248 and 6.3.2
[Samsung Galaxy Nexus] The Gingerbread Man:
What did you try?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] ceejay83:
guess i'm one of the lucky ones, my settings always stuck even before the app updates :)
[Samsung Galaxy Nexus] The Gingerbread Man:
Indeed. Its weird how it works for some and not others. You'd think the same code would work on all phones of the same make & model running same operating system. I really don't know what else I can try, I wiped apps, caches, reinstalled apps, ROM and kernel. Truly puzzling. I'm pretty sure the app worked fine before something was done to app for the s3 and that's when problems started occurring

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] ceejay83:
did you open supersu and update the binaries?
[Samsung Galaxy Nexus] nnnnr14:
After flashing a kernel I reboot my phone (the Google thing stays up a long time), after it gets done doing whatever it does my phone just glides on cloud 9!

I got 99 problems but bamf ROMs ain't one! -nnnnr12
[Samsung Galaxy Nexus] The Gingerbread Man:
Oh yes I forgot to mention that, I did it before that before I even opened the Franco app.

Sent from my Galaxy Nexus

---------- Post added at 02:25 AM ---------- Previous post was at 02:03 AM ----------

OK so back on Franco app 6.2 my settings are now sticking. Perhaps this helps in bug tracking. I dont know if this settings not sticking is persistent across all devices supported within the app but I'm wondering would it be easier to sort out problems if each device had their own app? I'd be happy to buy it again myself. Enough from me anyway, I'm sure you all had enough of me posting tonight :o:p:D

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] arhung:
I just go into the governor control once and I click back, when I go into the governor control again, the setting is not the same.

But after I flashed the r249_test, the problem seems really gone.
[Samsung Galaxy Nexus] The Gingerbread Man:
That would be explained by

Unless its your colour settings and / or power modes not setting upon boot in which case Franco app 6.2 seems to fix.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] yellowdie:
Dude, I'm so sorry. You should not be getting retarded low stars for an issue like this. :( Not cool.

---------- Post added at 09:44 PM ---------- Previous post was at 09:37 PM ----------

Do you have the Trinity Kernel Toolbox or any other Kernel control app installed? Do you have any init.d files that could be setting colors? If you don't have either, then try installing something like the TKT app and see if that app will allow you to set the color correctly.

We're all on the same team here and trying to get everyone happy. :) I know my phone and my wife's phone don't have any issues with stuff not sticking (on versions 6.3.0, 6.3.1, or 6.3.2).
[Samsung Galaxy Nexus] bdangol:
the command

mount -t vfat /dev/block/sda1 /sdcard/usbStorage

comes back with invalid arguement
[Samsung Galaxy Nexus] Chainfire:
Works for me ...
[Samsung Galaxy Nexus] minooch:
Cheers Chainfire,

I was thinking that too - but when you say it, it's gospel :P

Great to have you here, love your work
[Samsung Galaxy Nexus] Dmw017:
Hey mike so this kernel says it has usb host but I just tried connecting my Razr mouse and the wireless adapter for Xbox 360 controllers and neither actually did anything. I'm using the oem Samsung USB OTG cable.

..Also running AR HD 1.3.1 if that makes any difference

Am i missing something or is usb host not actually fully functioning yet?
[Samsung Galaxy Nexus] beekay201:
1) you need to create /sdcard/usbStorage before you issue mount command

2) if that doesnt work, format your pen drive as fat32 and retry. It's possible ntfs module is not available.

adb shell

su

lsmod | grep -e ntfs

Do you see ntfs module in the output? Or there's no output at all?

sent from a ics
[Samsung Galaxy Nexus] Proyoyo:
Mine says No device found.

The cable works with mouse though
[Samsung Galaxy Nexus] nick w:
So i thought i might venture out and try this kernel again.

Delete /system/lib/egl/libGlES_android.so and reboot. It's very important!

How are people deleting this file. File manager doesn't have rights to delete, are people doing through ADB?

Thanks

N
[Samsung Galaxy Nexus] drdino:
Root explorer!

Sent from my GNex using smoke signals.
[Samsung Galaxy Nexus] Shetlander:
Every time I try Root Explorer I get "cannot be deleted because the file system is read only"
[Samsung Galaxy Nexus] flakz0r:
Did you mount /system as read/write inside root explorer? Check the buttons at the top.
[Samsung Galaxy Nexus] Shetlander:
That did it. Thanks.

You learn something new everyday.
[Samsung Galaxy Nexus] nism0o:
What did i do wrong here? Dont remeber the fastboot commands..

Eiriks-MacBook-Air:root EirikHildre$ ./fastboot-mac flash boot.img

unknown partition 'boot.img'

error: cannot determine image filename for 'boot.img'
[Samsung Galaxy Nexus] MontAlbert:
i am having issue with adb with this kernel- using the modaco stock kernel in r4 I have no issues but when i flash this kernel i get:

E:\Android\Galaxy Nexus>adb remount

remount failed: Operation not permitted

But when i flash back to modaco i get adb access back.... does this kernel not have adb?
[Samsung Galaxy Nexus] flakz0r:
what you wrote:

./fastboot-mac flash boot.img

what you need to write:

./fastboot-mac flash boot boot.img

:)
[Samsung Galaxy Nexus] cmonthegas:
It looks like you missed defining what partition you wanted flashed.

Might be different on a mac to windows, but try

./fastboot-mac flash boot boot.img
[Samsung Galaxy Nexus] franciscofranco:
Can anyone test me this: http://www.multiupload.com/5HM903T9FO

Does it boot and hows I/O benchmark? Just asking to make sure that what I changed was a success.
[Samsung Galaxy Nexus] nism0o:
Testing this kernel with android revolution and my phone feels much faster and smoother :) Great job mr. franco :)

---------- Post added at 04:22 PM ---------- Previous post was at 04:20 PM ----------

Going to test this one now :)
[Samsung Galaxy Nexus] GchildT:
ok

10char
[Samsung Galaxy Nexus] bigxie:
This does boot.

I ran Antutu prior and after, and the I/O score was practically the same 540 vs. 545 on your previous kernel.

Any other I/O benchmark you suggest?
[Samsung Galaxy Nexus] nism0o:
Your test kernel boots fine :) Score 7016 in antutu no oc. Database IO: 545
[Samsung Galaxy Nexus] dwang:
I don't see how the boot loader has anything to do w the battery life. I think what happened is when you rebooted that caused one of apps that was draining your battery to reset.
[Samsung Galaxy Nexus] franciscofranco:
I'm sorry, I don't wanna sound rude, but why are you discussing battery drain and another kernel in this thread? It kinda sucks having to deal with off-topic everyday, for me and for users that want to read feedback and/or anything related to this kernel. You'll help roman better than help me if you discuss this kind of stuff in his own thread. Thank you.
[Samsung Galaxy Nexus] just4747:
But I've been talking about the kernel in all my posts before this. I then said I was flashing back to the stock kernel just to see if it makes a difference in battery life.

Why wouldn't I discuss batter life I am getting with this kernel in this thread? Read my post a few back, it explains how I went from full to 90% overnight last night on battery, with no use at all and deep sleep working fine, and I totally relate that to the kernel (unless I am wrong), not the ROM. Still boggled as to why I had that kind of drain in 7 hours with no use.

Isn't it ok to try to get help figuring that out in here??
[Samsung Galaxy Nexus] franciscofranco:
I misread, I apologize.

I'm 99% sure you have a rogue app wasting your battery. My phone just lost 1% during 9h idle.

From AOKP thread:

Since you have a CDMA device that might help you rule out some probs.
[Samsung Galaxy Nexus] just4747:
No problem. I really want to use your kernel but I want to find out the drain first and what is causing it.

What do you consider the best way to figure out which app may be draining? I have checked the battery stats in stock settings, no apps are showing much use, except the usual Android OS which seems to keep awake like 10-20% of the time of a full battery life span usually. I've also used Better Battery Stats and it never shows anything since charged that is keeping the kernel awake or anything like that.

And do you mean the PowerSaver instability may be affecting my battery life? I don't ever use the PowerSaver settings or turn it on, so I dont think it does anything negative. And there are others with CDMA on that ROM and your kernel without my battery issues (some).
[Samsung Galaxy Nexus] franciscofranco:
That's a bit hard without looking at the device in my hands. For example Facebook, Maps, Latitute, these apps tend to wake the device a lot.
[Samsung Galaxy Nexus] twilightrevenant:
There is a thread I like:

http://xdaforums.com/showthread.php?t=1423054

you should read it and try to graph your results. test extensively. I can't say much about rogue apps because I use few 3rd party apps. Just curious though, have you tried your normal battery again? Perhaps you got a bad battery?

-franco: love your work! inspired by the others, I'm going to graph my battery drain from kernel #8 and compare it to #9.2 later today. I was using stock 4.0.3 and I have not experienced a significant difference in battery drain against your build.
[Samsung Galaxy Nexus] just4747:
But if I am not seeing these apps show up in the Battery numbers in settings or in Better Battery Stats, and seeing deep sleep in CPU Spy...then wouldn't that mean they simply aren't an issue?

---------- Post added at 11:32 AM ---------- Previous post was at 11:31 AM ----------

I would try to see if my battery is bad, but I have randomly gotten 24 hours of extended battery life on a certain AOKP ROM/kernal combo before updating a day or two later (thus losing that life)...and I've never seen it since. SO I know the battery is capable, it's just not happening no matter what I try now...
[Samsung Galaxy Nexus] incomer:
Hi Fransico,

I like you're kernel allot, but I have one thing that I'm missing...

Thats NTFS support for the HOST controller..

Hope you can add this soon, because all my usb sticks are normal NTFS..

Incomer
[Samsung Galaxy Nexus] DJTaurus:
Guys any link of #7.1? I had the best battery life with tha build :o
[Samsung Galaxy Nexus] loudaccord:
* Added toggle option of the cpu1 suspend during screen_off:

cpu1 shuts down on screen_off: echo 1 > /sys/module/omap2plus_cpufreq/parameters/hotplug_enabled

cpu1 does not shut down on screen_off: echo 0 > /sys/module/omap2plus_cpufreq/parameters/hotplug_enabled

^ do I just punch that into terminal emulator?
[Samsung Galaxy Nexus] sishgupta:
I get the best battery idle with hotplug enabled. My idle consumption seems to halve from ~32mA to ~16mA.

Looking forward to #10 :)
[Samsung Galaxy Nexus] Masix:
Here you go :)

http://www.mediafire.com/?vnrsd6czvoibfu0

How long does your screen last?

I think I may have the same problem. I see the percentage drop when screen is on, resulting in around 2h max screen on time... Idle performance is around 1% / hour I think.

Just recalibrated the battery, going to see if that helps a bit.

Curious about your battery life with stock kernel :).
[Samsung Galaxy Nexus] bebolf:
Yup, with root permission.
[Samsung Galaxy Nexus] just4747:
I'll give you my screen-on time when my battery dies later (if that's what you mean).

I recalibrated the battery with the app (same as wiping stats in recovery) 2 days ago, and it didn't help or change anything at all....

Plus I just read this in the calibration thread, so I don't think "calibrating" this way does anything:

"So, for the Nexus One at least, there is ABSOLUTELY NO correlation between battery calibration and the battery stats file. NONE. The values on the battery chip determine everything."
[Samsung Galaxy Nexus] Nebucatnetzer:
I can give you my stats of today after my battery died. I'm on 30% now. With 2.5h screen on time. So it shouldn't take to long.

Tomorrow morning I will start the real test. I thought I could do it like this.

Unplug the phone at 0600 o'clock and then use with my settings it until it dies.

Then I'll do the same thing again on Sunday but with the kernel's stock settings.

If I'll be listening to music I'll make sure that I have the same duration on both settings. And the same duration of Wifi connection to keep it as accurate as possible.
[Samsung Galaxy Nexus] Thracks:
Over the next few days I will be charting what happens to this kernel with the ro.ril.power.collapse and ro.ril.sleepmode build.prop settings. Stand by.
[Samsung Galaxy Nexus] sirj00:
For sure one app that will kill your battery over night is the stock clock.

If you set an alarm and leave it dim automatically, it will drain the battery

Leaps and bound.
[Samsung Galaxy Nexus] loudaccord:
I did:

SU
echo 1 > /sys/module/omap2plus_cpufreq/parameters/hotplug_enabled

I didn't get any confirmation or anything, just went to # the next line... is there a way to tell if it worked?
[Samsung Galaxy Nexus] DJTaurus:
+1 thanks meter :cool:
[Samsung Galaxy Nexus] The Gingerbread Man:
Its rare I rate threads, just gave 5 stars. I always use xda app so never really think about it. I do hope I didn't sound negative in my other posts though, it wasn't my intention.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] yellowdie:
Hey, just so we don't get misunderstood, I wasn't pointing that at you. :) I was pointing that at people who gave his app 1 star ratings. I just got Franco's 6.3.2 and his change log said:

---"Instead of rating the app 1 star because "OMG X SETTING DUN STICKZ ON REBUUTS" send me an email or post in the respective XDA thread. It's discouraging reading such posts that would be simply avoided by a single email or XDA post."---

That made me really sad for him. :( :(