yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] simms22:
just having setcpu installed(or similar apps) could interfere with the franco kernel updater app. uninstall setcpu and try without it. resetup the franco kernel app and reboot after, see if it sticks.
[Samsung Galaxy Nexus] marcuso:
I now purchased SuperSU Pro license (anyway good idea to support the dev ;-) and logged the commands the app is doing on boot.

I can see the commands to set the min/max-values for CPU there (as expected), but no commands about governor (after boot).

(also found other settings seem also to have issues - strangely not always..)

When i opened the app manually i see the governor-setting logged - but it just sets the default again (not what i set before) ...

Finally i will now give up and stop flooding this thread - maybe franco or anybody else will get the correct hint at some point - until then i will use SetCPU and just enjoy the kernel itself.
[Samsung Galaxy Nexus] mullemulle86:
Just tried my own power mode with aokp b40

Works nice and stays after reboot
[Samsung Galaxy Nexus] leets4uc3:
Gotta multiple freezes/reboots on 194. Its really weird, first I was using 3-12 and got a few then went to 16-7 thinking it might be the 500 step. First time this has ever happen on Franco kernel with this phone. I have undrrvolted or anything. Anyone have some enlightenment?
[Samsung Galaxy Nexus] rogersnm:
Post your last_kmsg.
[Samsung Galaxy Nexus] franciscofranco:
Thanks for the input. I will see what I can do.
[Samsung Galaxy Nexus] PhoenixAG:
So I tried the 181 series and then 185.

Both were ok for me but not as good as the milestone 4 so I went back to it.

I recently tried 191, 192 and 194, but this new interactive governor seems to be bad for my phone. My phone has been acting very slow, specially the recent list. i tried Wheatley governor and it was a little better but still not as good, even on 1536/729.

I'm now back on milestone 4 and 1344/328 interactive and it's smooth as butter again.

I had some reboots and crashes on 194 as well which I've never had on my phone before, with any version of this kernel.
[Samsung Galaxy Nexus] andrew53517:
I'm still getting the occasional random reboot. I'm not sure if it's because I'm on 1.6 ghz or a bug but I thought id mention it. I increased the voltage to 1400 for 1.6 ghz. Hopefully that helps. Are you going to do anymore changes to 1.6 ghz for stability?

Galaxy Nexus & ASUS Transformer Rooted!
[Samsung Galaxy Nexus] leets4uc3:
How do I grab the kmsg? I dont have access a Computer right now also. I lowered the CPU to 7-10 and I am still getting freezes. I have to pull the battery. Super weird. My phone has never done this.
[Samsung Galaxy Nexus] simms22:
use a terminal emulator app. after a reboot, after you boot back up, type this in your terminal..

su(press enter)

cp /proc/last_kmsg /sdcard/last_kmsg.text(press enter)

then check your sd card storage for that file.
[Samsung Galaxy Nexus] CaspaTheGhost:
Whatever file manager with root access you use, its in:

/proc

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] rogersnm:
I know I'm the last one to this party but hey:
[Samsung Galaxy Nexus] tsabasid:
Hey guys, sorry if this has been mentioned before, but are all the latest nightlies compiled with the linaro toolchain? I am currently on 194.
[Samsung Galaxy Nexus] rogersnm:
Nope
[Samsung Galaxy Nexus] marshy73:
Just updated Franco Kernal App in playstore.

Now i can't launch the app.

Getting Permission Denial to launch App error.

Edit: its somehow ok now.... No more errors
[Samsung Galaxy Nexus] bat0nas:
Hi,

When I try to set any of the Franco power modes, my phone hangs for a while and when restarts (usually after 30-40s).

I'm I the only one with this problem?

Is it the App, the Kernel or the Phone?

194+latest updater App + SlimICS 4.0 ROM.
[Samsung Galaxy Nexus] tsabasid:
Ok, thanks. Where can I get the linaro version of Francos kernel?

Also, is there a way to change the gpu clock through the Franco kernel updater app? I can't seem to find the relevant option.
[Samsung Galaxy Nexus] rogersnm:
For the first question, a picture speaks a thousand words:

For the second question; no, the GPU frequency is hardcoded into the kernel.
[Samsung Galaxy Nexus] franciscofranco:
Sorry sometimes I miss some posts. I'm glad you get some nice results. About the 1,4ghz, that's not viable at the moment, and it won't happen as it lags in some phones, 1,35ghz is enough for now ;)
[Samsung Galaxy Nexus] sishgupta:
I've been noticing some lags using the pattern unlock. I am not sure what the cause is, perhaps when its coming out of deep sleep?
[Samsung Galaxy Nexus] franciscofranco:
That is not intended at all. Try with other governors e.g. interactive and conservative and report back please.
[Samsung Galaxy Nexus] Dr_Ownage:
Franco, you mentioned dont cap the CPU frequency? are you saying you SHOULD over clock for better battery?

I lost about 8% over 8 hours last night, running AOKP11 and nightly 8.
[Samsung Galaxy Nexus] franciscofranco:
Nah, don't need to cap screen off frequency at all, alas, I set the max frequency when the screen is off to 1,2ghz, that way it's not capped at all.

Not sure if overclocking will help for better battery, 1,2ghz is fast enough to race-to-idle.
[Samsung Galaxy Nexus] luffyp:
Franco, so I've read that there're quite a few reports of phones lagging especially when comming out of standby in lockscreen. This might be because you've undervolted and some phones may not be able to take it (not every Nexus is the same). Would it be possible to release a kernel with stock volting and your default undervoting as a script for people who want to undervolt? That should make every phone happy.
[Samsung Galaxy Nexus] franciscofranco:
I'll look at the undervolts again, but a script ain't possible as this must be set within the source. Thanks for the tip.
[Samsung Galaxy Nexus] mohitrocks:
I'm also experiencing some lag with unlocking the decide on nightly 8 on the conservative governor

EDIT: Nevermind, I guess I was just being paranoid.
[Samsung Galaxy Nexus] darrendm:
No lag with #8 here.
[Samsung Galaxy Nexus] energie:
No lag for me
[Samsung Galaxy Nexus] Antob125:
No lag Franco! Your kernals are amazing!
[Samsung Galaxy Nexus] aron7awol:
Did you perhaps forget to start the camera since the last time you restarted your phone? I haven't seen that kind of Android OS usage on the last few builds of this kernel. Also, download Better Battery Stats and check your kernel wakelocks. Something is wrong there.

---------- Post added at 08:26 PM ---------- Previous post was at 08:25 PM ----------

I don't think those are symptoms of the voltage being too low, but I could be wrong.

I do suggest that anyone who experiences that lag tries switching to interactive governor. I always run it and haven't had the lag at all, and a friend of mine had the lag and hasn't had it since he switched to interactive.
[Samsung Galaxy Nexus] :
No lag at all, tested ondemand, interactive, conservative.

Thanks!
[Samsung Galaxy Nexus] aron7awol:
Do you see >50 MB/sec in the SD Read test regularly? That is extremely high. What ROM are you running and have you done additional tweaking to achieve that?
[Samsung Galaxy Nexus] tyyau:
I think the lag is due to "Automatic screen brightness". I have that too, only when the phone is adjusting the brightness during wake. Switching it off proofs no lag at all. But I maybe wrong.

Amazing kernel....
[Samsung Galaxy Nexus] grinch247:
exactly! wow!!!!
[Samsung Galaxy Nexus] franciscofranco:
Ok, lag should be gone for good. Previously it worked like this:

Screen_on activity -> CPU ramped to max frequency

The problem with this is that it didn't stay in that frequency for long, maybe ramping down just exactly after it ramped up, so in the end it was pratically doing nothing.

Now after Greg suggested it to me that I could try to lock the max frequency ramp for 5secs before unlocking it I tried it and now it works like this:

Screen_on activity -> checks for max frequency ->

if 1,2ghz -> ramps to 1,2ghz -> stays there for 5 secs -> frequency is unlocked and it can ramp down again if it wants

else if 1,35ghz ramps to 1,35ghz -> stays there for 5 secs -> frequency is unlocked and it can ramp down again if it wants

Lag looks like its gone ;)
[Samsung Galaxy Nexus] sishgupta:
Hmm I just got a reboot while idling (screen off anyway) while using conservative. I dont know what the cause was but the only change between Mid day Friday and now was going from 7.1 to 8.

I know phone reboots can be flaky and it may have nothing to do with the kernel at all. Is there something I can check the next time it happens to help troubleshoot? Logcat?

My battery life is insanely good though! so crazy.
[Samsung Galaxy Nexus] franciscofranco:
That might be my fault uv wise. A logcat and dmesg please yes.
[Samsung Galaxy Nexus] drtrmiller:
I have v8 nightly and I'm using No Frills to control, and when I set to Performance governor, noop, 1.35 GHz works fine until I turn the screen off, at which point the only freq CPU Spy records is 1.2 GHz and deep sleep. AOKP ROM.
[Samsung Galaxy Nexus] tsabasid:
Is there any way I can get 512Mhz gpu with Franco.?
[Samsung Galaxy Nexus] franciscofranco:
Yes, if you take 1s to search the thread you'll know your answer ;)
[Samsung Galaxy Nexus] tsabasid:
Thanks all. You are right, I got a bit lazy with search as I am currently accessing the forum through Tapatalk. Anyway just flashed the linaro optimized 190 512Mhz on Xenon v5 which is also linaro optimized. First impression is quite good regarding speed. Especially on Google play, whn scrolling through apps. Thanks for the work Franco. :-)
[Samsung Galaxy Nexus] franciscofranco:
https://plus.google.com/106873500108976028532/posts/Jc9xNzSRp51
[Samsung Galaxy Nexus] SpOuK-3-:
Lol :)
[Samsung Galaxy Nexus] jairmoreno:
Hi Franco, there are increasing reports of incompatibility between AOKP and your kernel, did you notice that? Is there something that I can help you?
[Samsung Galaxy Nexus] pluto22:
I posted this in the CDMA forum but this forum gets a lot more traffic so I figured I'd post here to see what the interest level is like. Please "THANK" this post if you like the below idea or it's something you'd use.

I'd love a Tasker plugin for the Franco App that could change the power modes. It would be great to automatically change the power mode when loading certain apps or for certain events.

Just being able to "set" a mode would work but being able to "toggle" a mode would make it even easier.
[Samsung Galaxy Nexus] franciscofranco:
Don't know anything about it. What kind of incompatibilities are we talking here?

Not sure I want that. A widget in the future, sure, but something like a Tasker hmm I doubt it.
[Samsung Galaxy Nexus] SeanHacker:
most likely user error. ive been running this kernel and aokp since day one. no issues what-so-ever. the only thing i can think of in reference to incompatibilities is that the user cant seem to find what or where their device likes to run at.
[Samsung Galaxy Nexus] Antob125:
Running franco on aokp now and always have. Runs perfect. No issues.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
Just pushed 5.4 of the updater to Google Play. Lets hope Google minions work fast to make the update available in the store fast!!

5.4

Common:

* Settings persisting on reboot interface completely written from scratch - I hope it fixes any problems with settings not persisting through reboots. Make sure you have busybox working. This is mainly targeted to the Galaxy Nexus users

Sorry AndroidPit buyers, you'll have to wait until tomorrow, I encountered some major problems with the licensing of the app for their market and I gotta fix them, but now its already 5AM.
[Samsung Galaxy Nexus] pluto22:
Widgets are ok but some of the jobs I'd create with Tasker would be to automatically switch power modes when :

- Music power mode when a player is running and the screen is off.

- Low mode (ex: cons 192/576) when launching card games, Tapatalk, reading news, etc

- High Game mode (ex: oc wheatly/interactive) when launching graphic intense games

- Battery Low modes (ex: cons 192/729 when below 15%)

- Work Mode - lower power mode by location

- Full Power mode when charging and battery > 75% (and screen on)

Of course I may be the only one that would use it in which case it would be a colossal waste of time. :)
[Samsung Galaxy Nexus] franciscofranco:
I understand what you mean, but I HATE automatic services, and if its something that I hate its most likely not going to be added. Custom power modes is already offering a lot of customization, I'm happy with the way things are at the moment.
[Samsung Galaxy Nexus] dandyqb:
im in androidpit, hope you figure out the problem soon, thanks... :good:
[Samsung Galaxy Nexus] derPianist:
...but could you add a widget to your app where we can quickly switch between those powermodes? And with the AOKP navbar function it would be really awesome.

Thanks!

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] T-Loop:
Same here. Running AOKP + Franco from day one and never encountered a problem. Both Kernel + App works like a charm. Settings always sticks on boot and work like expected.

Thank you Franco for keeping this device running high.
[Samsung Galaxy Nexus] marcuso:
.. you really have spent the night on this ?! ;-) ...

Your commitment is so great, but unfortunately this did not change a bit for the issue i see:

Still the governor-setting is not applied. SuperSU logs show CPU-Freq beeing apllied correctly, but no command is setting the governor that has been set in the app.

(and this time it seems that only cpu-max is set, but not cpu-min ?)

And as with the tests before I resetted the app-data, rebooted, checked busybox, tried with fresh (other) ROM, ...

And again: when opening the app later SuperSU logs shows that it sets the governor-default (not what has been set before) then.

--> @franco: somehow i have the idea that it is not the function of applying the setting during boot, but maybe the settings storage that somehow gets corrupted during reboot - could that be possible ? Anyway to check this ?

I almost feel bad about all the efforts you are putting in this - as obviously not all are affected, but as i described i made sure it is not the ROM, any setting etc..

Let me know if i can help with anything (logs, tests, ...) in case you want to debug further.

Thx

Marcus
[Samsung Galaxy Nexus] DonXoB:
I have the same problem at the moment. I have done a dirty reinstall of slim ics. I thought I was the only one with this problem. It seems that you are the second. I am not able to download or autoflash any version, too.
[Samsung Galaxy Nexus] Moz007:
Since a few builds or app update, 192Mhz step become very unstable even without undervolt...

Still testing !
[Samsung Galaxy Nexus] The Gingerbread Man:
Is it that you just need a different busy box app perhaps? Try busybox free 8.4 by stericson and install 1.20.1 in system/bin

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] PhoenixAG:
OK further to my post, I just upgraded to aokp 40 and the latest version of Franco app and it gave me a lot of problems.

Firstly, with milestone 4 and latest aokp (40), I can't go into Settings>Storage. It closed on me every time.

So I tried updating to latest nightly again to see whether that fixed the problem. Franco app has always been very stable and bug free for me. The latest version kept hanging / crashing on me every time I clicked the button to install the nightly.

I've managed to get 194 installed now and it's fixed the settings>storage problem as it no longer crashes, but the app is still as buggy.

Even now if I click the button to install latest nightly it hangs.

Thanks a lot for all your work Franco and I hope this feedback is helpful.

Btw, nightly 194 is now smooth for me with latest aokp and interactive governor.
[Samsung Galaxy Nexus] rogersnm:
The nightly version/download doesn't work atm because minooch.com is down.

Edit: Back up now, it should work
[Samsung Galaxy Nexus] minooch:
You beat me too it, was coming here to say that there was going to be a outage at some random point in the next 48 hours - got an email saying my server is being "upgraded"

Sorry for the late news
[Samsung Galaxy Nexus] Moz007:
This is funny, now my phone need more mv for 192mhz step than 384mhz...

Any ideas ?
[Samsung Galaxy Nexus] DonXoB:
Now the app is working again as well as always.
[Samsung Galaxy Nexus] franciscofranco:
Why dont you let Smartreflex do its job? It does it fine, no need to worry about voltages anymore.
[Samsung Galaxy Nexus] rogersnm:
@Franco I ran into a bug in the app:

Bug: App crashes when you open "Colors Multipliers" under "COLORCONTROL"

Steps to reproduce:

Open app and go to the colour multipliers panel

Set Red to something low using the slider, such as 80

Set Green and Blue to 0 using the slider

Close app

Reopen app and go back to the colour multipliers panel and it'll crash

Logcat:

E/AndroidRuntime( 3190): FATAL EXCEPTION: main
E/AndroidRuntime( 3190): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.franco.kernel/com.marclandis.francokernel.ColorControl}: java.lang.StringIndexOutOfBoundsException: length=1; regionStart=0; regionLength=3
E/AndroidRuntime( 3190):	at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2079)
E/AndroidRuntime( 3190):	at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2104)
E/AndroidRuntime( 3190):	at android.app.ActivityThread.access$600(ActivityThread.java:132)
E/AndroidRuntime( 3190):	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1157)
E/AndroidRuntime( 3190):	at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 3190):	at android.os.Looper.loop(Looper.java:137)
E/AndroidRuntime( 3190):	at android.app.ActivityThread.main(ActivityThread.java:4575)
E/AndroidRuntime( 3190):	at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 3190):	at java.lang.reflect.Method.invoke(Method.java:511)
E/AndroidRuntime( 3190):	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:789)
E/AndroidRuntime( 3190):	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:556)
E/AndroidRuntime( 3190):	at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime( 3190): Caused by: java.lang.StringIndexOutOfBoundsException: length=1; regionStart=0; regionLength=3
E/AndroidRuntime( 3190):	at java.lang.String.startEndAndLength(String.java:593)
E/AndroidRuntime( 3190):	at java.lang.String.substring(String.java:1474)
E/AndroidRuntime( 3190):	at com.marclandis.francokernel.ColorControl.onCreate(ColorControl.java:58)
E/AndroidRuntime( 3190):	at android.app.Activity.performCreate(Activity.java:4465)
E/AndroidRuntime( 3190):	at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1049)
E/AndroidRuntime( 3190):	at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2033)
E/AndroidRuntime( 3190):	... 11 more
W/ActivityManager( 200): Force finishing activity com.franco.kernel/com.marclandis.francokernel.ColorControl
W/ActivityManager( 200): Force finishing activity com.franco.kernel/com.marclandis.francokernel.Main
W/ActivityManager( 200): Activity pause timeout for ActivityRecord{41821390 com.franco.kernel/com.marclandis.francokernel.ColorControl}
I/Process ( 3190): Sending signal. PID: 3190 SIG: 9
I/WindowManager( 200): WIN DEATH: Window{417e3468 com.franco.kernel/com.marclandis.francokernel.Main paused=true}
I/ActivityManager( 200): Process com.franco.kernel (pid 3190) has died.

Steps to fix:

In ADB run: echo "2004318071 2004318071 2004318071" > /sys/class/misc/colorcontrol/multiplier

Open app again and it works.
[Samsung Galaxy Nexus] franciscofranco:
Thank you. I shall look into it.
[Samsung Galaxy Nexus] Moz007:
Because the values are way too high with SR on than my personal and stable values...

But it's not important, i can run perfectly stable 384-1536mhz and i think it's enough.

Now hop to see new features like... uv on boot ! No don't whip me ! Lol
[Samsung Galaxy Nexus] sluflyer06:
Franco. Has there been any progress with USB Audio Out? I know a couple months ago you had received a DAC to try to get that working with the Nexus.

Thanks!
[Samsung Galaxy Nexus] franciscofranco:
This is what happened:

1 - Received the DAC and compiled the kernel with the needed modules

2 - DAC is recognized but nothing happens

3 - Did research and found out it needs a layer in userland to switch the audio output to/out of the DAC

4 - Talk with Ezekeel and he told me that needs a major re-write of the libaudio which is C++ and I have 0 knowledge of it, plus I don't have programming logic to work on libs from scratch

5 - Sent the DAC to Ezekeel

6 - Something happened and the DAC came back to my doorstep

I haven't sent the DAC back to Ezekeel yet, been lacking free time to go to the Post Office. I'll try to do that tomorrow.
[Samsung Galaxy Nexus] KingDavid63:
Not getting any incompatibilities here with AOKP, smooth as butter.
[Samsung Galaxy Nexus] coogh:
NTFS Usb Stick

Hi all,

I have a GSM GNex with AOKP Rom (build 39) and Franco Kernel (nightly r194) 384 Mhz Gpu.

I'm trying to access a USB Stick, NTFS formatted, but it tells me that the support is empty or it is formatted with an unsupported file system.

I know that since January Franco Kernel support this FS, so why I can't access my NTFS Usb Stick? Do I have to enable something?

Thanks for your help.
[Samsung Galaxy Nexus] KingDavid63:
Thanks Franco for the app update, haven't tried the reboot yet, but no biggie to me, I can justopen the app and select the power mode again. ;-)
[Samsung Galaxy Nexus] Flukester69:
I wish you would put the wifi from nightly 189 back in or give an alt version. I have problems with your kernel after 189 because the handoff or something from wifi to mobile data sucks. I get gray bars with 190+ kernel and I put 189, bang it all works perfectly. I mean what is the chances that all my 3 nexus phones work with 189 yet as soon as I move away from it I get grey bars on all of them. I go in and I always make the same changes.. 1344/729 and screen off is 729 too. Scaling governor is interactive. My GetRIL is right @ UGLC1, use FasterFix and agps patch to make sure my GPS is fast.

To resolve the issue (kinda) on nightly 190+ I disable wifi and then mobiledata turns on.. Then turn on wifi and they are both back but it's f'ing annoying and so that's why I stay with 189...
[Samsung Galaxy Nexus] franciscofranco:
Try Sticky Mount app from Chainfire.
[Samsung Galaxy Nexus] leelaa:
Thanks for the app update franco, the colour settings never used to stick on boot for me unless i opened the app straight away. Everything is perfect now. Thanks mate. :)