yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] yellowdie:
Originally, I was thinking that lower would be better (because it's better for the battery), but we're talking 50ms to 60ms--very, very little difference in terms of battery. What we're thinking now is that by setting the min_sample_time to be a multiple of the timer_rate it helps things smooth out a bit. This post explains more:

So if the timer_rate is 30ms (30000) that means there is a 30ms gap between when the cpu can change frequencies. But by choosing 40-50ms for the min_sample_time, you're basically giving the phone one 30ms cycle to make a decision but then telling it to wait an additional 10-20ms before changing. But by lining up the timer_rate and the min_sample_time, it helps keep things changing (up and down) faster and smoother.

That's the current theory anyways. :cowboy: :) Please continue to share your real world experiences! :D
[Samsung Galaxy Nexus] aeroseek:
Francisco, your **** just works.

683088554P850482F

Thanks!
[Samsung Galaxy Nexus] yellowdie:
Very nice. What clockspeeds? Did you UV 192 at all?
[Samsung Galaxy Nexus] Stigy:
Thanks for the quote explaining the difference.

I am going to run 6/7/6/3 for today and then 6/7/5/3 tomorrow and see which one gets me better performance & battery life.
[Samsung Galaxy Nexus] cap'nC:
Wow, I switched from r290 to r295 and.. just wow! I've never seen performances like these on my phone. Good job Franco!

Little question: is it normal that I can't set bfq as i/o scheduler? The phone reverts to deadline every time I try to change it.
[Samsung Galaxy Nexus] tgyberg:
Man r295 smokes! :good:
[Samsung Galaxy Nexus] crimmylol:
I have little shutters when listening music. Using Neutron Music Player, YouTube app, Tunein and all of this apps have shutters when screen on or off doesn't matter. I'm using interactive governor 384-1500, screen off - 784. Can anyone help with this problem? Thanks in advance.
[Samsung Galaxy Nexus] AndAllThingsWillEnd:
Same here... I don't know if its CM10 or the kernel.
[Samsung Galaxy Nexus] franciscofranco:
Install busybox and smart install the binaries via the app.
[Samsung Galaxy Nexus] sajty:
Hi.I bought franco kernel updater.Where is option to change i/o scheduler?Cannot find it.
[Samsung Galaxy Nexus] franciscofranco:
Nowhere for now.
[Samsung Galaxy Nexus] sajty:
Oh,OK.Thanks.
[Samsung Galaxy Nexus] usmankh10:
R295 is flying on pa 2.50 ,will report battery after some cycles
[Samsung Galaxy Nexus] BigBake88:
Lol idk why someone would be offended by this. Good for you, brother! Franco kernel=winning! Give us a final screenshot when you're done with the cycle!:good:

---------- Post added at 01:30 PM ---------- Previous post was at 01:23 PM ----------

I had this same issue. Are you running rasbean by chance? I know I was and no matter how many times I wiped or flashed max CPU kept falling to 1200. I flashed another ROM and all is well now. Maybe something gets borked when the ramdisk is replaced with francos on some roms...

Edit: just saw Franco told you to install busy box! I didn't have it installed when I was on rasbean! That was probably the issue!!! Son of a gun!!
[Samsung Galaxy Nexus] nuwan32:
192-729, and yea everything uv'd. 192 @ 675mV.

And here's my governor settings

It's amazing how these settings feel the same as max 1.2GHz. Little micro lag at app drawer but that was there before as well and I don't mind
[Samsung Galaxy Nexus] duduzinho15:
All the time that I flash any file I wipe both cache :-$
[Samsung Galaxy Nexus] yellowdie:
Interesting. What made you choose those min_sample_time (10000) and timer_rates (50000)?

Cache and dalvik-cache has absolutely nothing to do with the kernel. In no way, shape or form does it help. It's 100% placebo, if anything. :)

See here and here.
[Samsung Galaxy Nexus] TEK112:
Seems like you only have one option... wipe it all and reinstall or try a new ROM. Just make backups first.

---------- Post added at 01:57 PM ---------- Previous post was at 01:47 PM ----------

That is true, but you are missing one important aspect. While wiping the caches does not directly affect the kernel. It does directly affect apps that use the kernel.

I have experienced more than a few failures as the direct result of flashing a kernel. I don't blame the kernel, but rather the process. Most of the time it is resolved by wiping the caches.
[Samsung Galaxy Nexus] yellowdie:
I would try reflashing your ROM without wiping anything at all--you won't lose anything (but still make a backup first, of course). That will restore the original kernel and ramdisk. Then boot into it and autoflash r295 again. See if that helps.

---------- Post added at 02:01 PM ---------- Previous post was at 01:57 PM ----------

I admit, I don't remember what the original problem was. If it was an issue with a specific app, then I could see that being valid as well. If I get apps that give me problems, I'll clear that app's data or uninstall it completely, then fix permissions and it usually solves everything. If that fails, then I'll try clearing caches and fix permissions again, but I don't really think it's needed--I just fall back to my placebos. :) Usually uninstalling the app then fixing permissions solves my issues.
[Samsung Galaxy Nexus] Tommy_FIN:
I'm getting this weird popping sounds in spotify with r295. I used Franco's music power mode. With 729 max the popping sound is still there but less frequent. With 1036 max the sound is gone. I didn't notice this with m6.

I'm using xenonhd rom if that matters.
[Samsung Galaxy Nexus] TEK112:
Very true.

My bigger concern is the instability in the filesystem and the fsync options out there. I believe one user can't select the reboot option from the menu otherwise it trashes the ROM, he has to manually shutdown and power on the phone each time. Sometimes a boot will take 30 seconds or 10 minutes. It is very random and very strange. I wonder if they worked that out with 4.1.2.
[Samsung Galaxy Nexus] duduzinho15:
http://www.4shared.com/file/ZyO3gMG6/last_kmsg.html?
[Samsung Galaxy Nexus] Hans QC:
512GPU worked fine before, but I'll try 348.

Edit: still lagging with 348GPU.
[Samsung Galaxy Nexus] nuwan32:
I just choose it by trial and error I'd say... I don't really have a mathematical explanation lol, it's just the settings that worked best for my preferences on my phone
[Samsung Galaxy Nexus] Antob125:
Trying out 5/5/9/3 for performance and im loving it! I currently have min=384 and max=1228. Would you recommend pumping up min to 729 for more performance. And screen off frequency is set to 729, is that default?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] FrankNS:
WOW! r295 is lightning fast on my phone!

Love it! :thumbup:
[Samsung Galaxy Nexus] P30SiNa:
Can 512Mhz GPU cause problems for the device if I use it for a long time? I mean, after one or two years?!

I always use 384Mhz kernel. I'm afraid of overclocking! Because I wanna keep my nexus as long as it gets updates from google or even more.

btw, I was getting a bad walelock with r295 (AudioOut_2)

Back to r290 and it's gone!
[Samsung Galaxy Nexus] nuwan32:
who knows? this device hasn't even been out for 2 years. Higher clock probably does decrease life of gpu, but your phone will definitely die of something else before the gpu does
[Samsung Galaxy Nexus] 11768:
I am undervolted and have SR disabled, but why isn't the saved value of the mV be applied after reboot? It still shows the stock one running (e.g. 192 Mhz, 1000 mV current, 730 mV saved).
[Samsung Galaxy Nexus] yellowdie:
Nah, don't bump up the min. I was using 729 as my min, but after these tweaks, I have gone down to 192MHz (UVed to 730mV) as my min (I have never gone below 384 before) and it's fantastic for performance. :)

It can cause problems in the very long run, like four+ years. So for the most part, probably not. :)

Franco's app will never set voltages on boot--by his design. You can just go back in and reapply them if you reboot. :good:
[Samsung Galaxy Nexus] Stigy:
So it seems that 192 is what everyone is testing - if I do 192/1305 without modifying anything else will I see any improvement or I might end up with SoD's etc?

Thanks for all the help guys - this is probably the best kernel thread I've been in yet.
[Samsung Galaxy Nexus] yellowdie:
Fantastic performance, zero SODs. But try 192-1036. :D Trust me.
[Samsung Galaxy Nexus] TEK112:
The it sounds like a settings issue. You can try clearing the app data for francos app and run it stock. If it is better, then you know it is a value you set. Make a backup through titanium first so you can revert if this is not the issue.

---------- Post added at 03:52 PM ---------- Previous post was at 03:47 PM ----------

The biggest audio out offender for wakelocks are the touch screen sounds and lock screen sounds.
[Samsung Galaxy Nexus] Hans QC:
I cleared settings and rebooted, still same problem.

Envoyé depuis mon Galaxy Nexus avec Tapatalk
[Samsung Galaxy Nexus] TEK112:
Uninstall francos app, download and flash the kernel using this and see if it gets better:

http://minooch.com/franciscofranco/Galaxy Nexus/JB/Jelly Bean/franco.Kernel-r295-512GPU.zip
[Samsung Galaxy Nexus] Marvelix:
sorry, wrong thread
[Samsung Galaxy Nexus] Blackcrx:
currently running 192-1228 (192 @800mV), I thought about running 192-1036 but the voltage difference between 1036 and 1228 is only 25mV. Is it even worth it?

wouldn't it be worth it to stay 1228 for the "race to idle" theory?
[Samsung Galaxy Nexus] Hans QC:
Still the same. Scrolling lags when an image appears.

Envoyé depuis mon Galaxy Nexus avec Tapatalk
[Samsung Galaxy Nexus] Schneewitzchen:
Hey Franco, just want to say thanks for the best kernel and rom! :D

It's fast, smooth and the battery life is just awesome!!!

I'm on minco v5, nightly v295, first battery cycle, 192 - 1036 MHz, 192 slot uv to 750 mV.
[Samsung Galaxy Nexus] yellowdie:
How cow, you guys. This is insane. 100 Thanks in one post. lol. Y'all are awesome, and I feel blessed. I'm really glad that people found our research helpful and easy to understand. r295 is a beast!

:):D:laugh::good:
[Samsung Galaxy Nexus] black_sith:
Franco thank you for this awesome kernel.

Run r295 with cna 3.6.5, 192-1305 mhz,192 uv, 2000mah extended battery, and performance and battery life is unbelievable.

Think this kernel is perfect!!!

Gesendet von meinem Galaxy Nexus
[Samsung Galaxy Nexus] creeve4:
franco, will you be releasing a change log for 295? I'm curious what changed between 290 and 295.

BTW 295 is killer! Thank you!
[Samsung Galaxy Nexus] Stigy:
I'll give that a shot and see how my phone responds to it. Thanks again everyone! :)
[Samsung Galaxy Nexus] CaspaTheGhost:
Didn't thank the post as I feel betrayed dude, you're supposed to be part of the keeping it real crew. :p

729 till I die!

Been some great work going on whilst I've been busy at work, threads buzzing along at quite a pace. :thumbup:

Giving 295 a whirl fully stock, let's see if I can forget about 729 and not die.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] kmjo29:
Hey Franco..nice kernel! One question. Can you check to see if the newest app update somehow took out TCP please..I need to change to westwood because I think that's where my lag is coming from. I've downloaded the app and auto flashed the kernel but nothing is showing TCP. Thanks for the help
[Samsung Galaxy Nexus] chrisgtl:
Been using your kernel and app for a while and find both faultless.

Donated, enjoy a couple cold ones on me.

16R00105GE2303054
[Samsung Galaxy Nexus] yellowdie:
haha, bro, I totally understand. I was preaching for awhile about 729 mins. Then when this whole thing started a few days ago, Osm0sis was having a problem that I couldn't replicate. Turned out it was a problem with the 230 min--which I have never used. After doing some testing, Franco putout a test version with the 192 and this whole process began. So I was r e a l l y skeptical of giving up my 729 min, but honestly, I think it's fantastic at 192! :D

I have the latest app and still have the TCP setting. Sounds like the kernel didn't install properly. Try doing another autoflash from the app and see if it fixes it. :)
[Samsung Galaxy Nexus] Controvrsy046:
What do you mean by 5/5/9/3 ?
[Samsung Galaxy Nexus] yellowdie:
Read this. :)
[Samsung Galaxy Nexus] kmjo29:
I been auto flashing trying to get TCP to show all day. I've tried on mobile network and WiFi.
[Samsung Galaxy Nexus] Controvrsy046:
Awesome thank you!
[Samsung Galaxy Nexus] yellowdie:
Very strange. Did you try clearing the app's data? Uninstall it? Fix permissions? Try flashing Trinity kernel, then flash r295 again. :/

My pleasure. :)
[Samsung Galaxy Nexus] franciscofranco:
Install busybox.
[Samsung Galaxy Nexus] kmjo29:
I'll try that. Thanks for helping me out YD!
[Samsung Galaxy Nexus] osm0sis:
I only ever see the AudioOut_2 wakelock when I've been snoozing my alarm for awhile in the morning.

The one for touch sounds is AudioOut_1. Screen lock sound doesn't produce a wakelock that I've seen.

Also, I still think we can do a little better on the tunables, performance-wise. I'm seeing jitteriness while scrolling slow in the browser on xda thread pages here, and I had to both set to 5/5/9/3 and raise the min to 384 to resolve it. Working now to see if I can figure anything out while sticking with 192, but it's not looking good so far..
[Samsung Galaxy Nexus] yellowdie:
I'd go with Franco's response. Install Busybox.
[Samsung Galaxy Nexus] CaspaTheGhost:
I concur on the audio wakelocks and screen lock sound.

Suppose I should give 192 a spin.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] kmjo29:
Thanks yellowdie and Franco. Busybox did the job..:)
[Samsung Galaxy Nexus] franciscofranco:
Just pushed the so wanted update to the app to offer IO scheduler exchange support. Hope Google adds it fast to their servers.
[Samsung Galaxy Nexus] yellowdie:
Awesome! Thanks! Now I can get rid of Trickster. :)

This is in no way an eta request, but I am just curious how the sound mod is going? I know we've kept you pretty busy for the past few days. Lol
[Samsung Galaxy Nexus] RoscoeDpG:
ya we have but u know he is liking it :D crazy how many people are on to his ROM and Kernel
[Samsung Galaxy Nexus] franciscofranco:
Sound is fixed since r292, no more sound crapping itself or low call sound.
[Samsung Galaxy Nexus] shreddintyres:
I have noticed that occasionally if i have been using speakerphone in another call and receive another call i have to toggle speaker in order to get sound to return to normal volume. I am using AOKP so I am not sure if it is a rom issue or kernel issue.
[Samsung Galaxy Nexus] Antob125:
Oh noes a new option to learn! Should I google it or can you link me any references to the io scheduler

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] yellowdie:
:D Yeppers!

Ah, I remember that change, but I thought your fix was gonna be in the app. Cool beans! :)

Boss Man's only got two options: Deadline (default) and BFQ. Check out this for more info. :)
[Samsung Galaxy Nexus] cpom1:
Is anyone having issues with the franco app where the overclock settings dont stick?
[Samsung Galaxy Nexus] BigBake88:
Same with me as well. 295 is great, but I agree that the scrolling does seem to be a little more jittery in 295 at least in the browser
[Samsung Galaxy Nexus] yellowdie:
Install Busybox.
[Samsung Galaxy Nexus] osm0sis:
Seems to especially happen when it hits images as the scroll-fling is switching from fast to slow causing a "speed bump" jitter/microlag. I've tried changing schedulers back to bfq, no difference, and messed with all the tunables but couldn't come up with anything that tangibly helped more than the 5/5/9/3 someone else posted.

min 192MHz, UV'd to 725mV, max 1536, hispeed_freq still at 729 since upping it to 1036 didn't make a difference either. input_boost also at the default 1036 since I can't imagine wanting it higher.
[Samsung Galaxy Nexus] trailblazerz11:
App updated, works great.

I assume io setting stick on reboot.?

Was the issue with bootloop after flashing kernel with bfq fixed?

Since setting deadline default for kernel during compiling sets it as default for recovery ? (From what I remember building kernels)
[Samsung Galaxy Nexus] cpom1:
Thanks but I already have that installed. Am i missing a step?
[Samsung Galaxy Nexus] trailblazerz11:
But you may have an incomplete version of busybox. Maybe install again just in case.
[Samsung Galaxy Nexus] yellowdie:
I posted 5/5/9/3 earlier as a "high octane" performance setting, but it's probably gonna be a battery killer. But I just switched to it right now to see how it feels. :)

---------- Post added at 10:18 PM ---------- Previous post was at 10:16 PM ----------

Do you have the binaries installed to /bin or /xbin? I would install the app, then use the built in "uninstaller" then do a Smart Install into /xbin. :)
[Samsung Galaxy Nexus] Antob125:
Does this look right?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] yellowdie:
Yes, that is "high octane" mode. The recommend mode is 6/7/6/3. Take your pick. :)
[Samsung Galaxy Nexus] BigBake88:
"Speed bump/jitter/microlag" is def best way to describe it, and I did no see it in 290.

Edit: trying yellows high octane tunables. I'll see if I feel any difference and report back.
[Samsung Galaxy Nexus] tgyberg:
Well how is it? Did it blow yer hair back?! :cyclops:
[Samsung Galaxy Nexus] Jamdat33:
can we enable high performance sound now without diction messing up the words?
[Samsung Galaxy Nexus] Tommy_FIN:
Anyone?
[Samsung Galaxy Nexus] BigBake88:
Did you try bumping up the min CPU? That more likely is the culprit. If your min is 192 try going 384.
[Samsung Galaxy Nexus] Wh1t3Rose:
Oh and the 1st line of the OP made me LOL
[Samsung Galaxy Nexus] arhung:
Do you undervoltage ?
[Samsung Galaxy Nexus] osm0sis:
Got a random force close on boot with the new updater version, then I noticed my tunables didn't stick, so might be related to that somehow? Going to clear app data and cache and try again.

P.S. 4 hours screen on today even though my idle drain was higher than it's been in the last few builds (1%/h vs. 0.4%/h), we'll see how it does with "high octane" tomorrow on its second cycle. :)

Edit: Reinstalled the app as well and no force closes, but still can't get my custom tunables to stick. NM, just got another FC on boot as well :(
[Samsung Galaxy Nexus] Tommy_FIN:
Right now I'm using 192-1036 with no issues.

No.
[Samsung Galaxy Nexus] a5pe4:
Alright, now that is ridiculous.
[Samsung Galaxy Nexus] Wh1t3Rose:
No this is ridiculous. Stock battery
[Samsung Galaxy Nexus] ac3theone:
This happens to me from time to time also, I'm on rasbeanjelly. I thought it was a issue with a sound mod I have
[Samsung Galaxy Nexus] nuwan32:
Lol this is messed up. I just played gta 3 while being under clocked to 729 with 384 gpu and realized I'm running smoother or as smooth as my nexus 7 running Franco r23 @ 1.3 GHz And 484 gpu. I think Franco should take a look at the n7 kernel and put some of the galaxy nexus improvements in there :p
[Samsung Galaxy Nexus] Wh1t3Rose:
I have busybox and yes I did a fresh install in xbin but a lot of my settings in franco's app do not stick
[Samsung Galaxy Nexus] a5pe4:
That is also pretty ridiculous. But not as ridiculous as the guy with 4 hours screen on time and 50% battery left! Even if it's an extended battery. However, I haven't touched your screen on time since before I rooted my phone months ago... sigh
[Samsung Galaxy Nexus] alexdemo:
Hey Franco, your kernel f.u.c.k.ing rules.

M6 with stock 4.1.2 and stock battery.
[Samsung Galaxy Nexus] Wh1t3Rose:
Oh shoot forgot I got this yesterday
[Samsung Galaxy Nexus] louyaorong:
upgrading to 295 and 7.1.1 app, the governor control option doesn't stick after a reboot. it was ok when on M6 and 7.1
[Samsung Galaxy Nexus] IgnorantNerd:
What are your settings?

Swyped from my Galaxy Nexus using Tapatalk 2
[Samsung Galaxy Nexus] yodanutz01:
hey franco, can i use your kernel with stock deodexed 4.1.2 ?
[Samsung Galaxy Nexus] b1337:
Read the OP
[Samsung Galaxy Nexus] Shadow-Nexus:
This is what o got the other day

Best kernel ever!
[Samsung Galaxy Nexus] kompressorgpl:
Hello! I install V5 and now everytime that I rebbot my phone I get this message: Sorry. the Franco Kernel Updater as been interruped.
[Samsung Galaxy Nexus] Tarun95:
R295 is badass !!
[Samsung Galaxy Nexus] yodanutz01:
it says only 4.1/4.1.1/4.1.2. it doesn't say stock or anything...
[Samsung Galaxy Nexus] gm007:
So it works with all the rom available ;)
[Samsung Galaxy Nexus] yodanutz01:
anyone tried this with stock 4.1.2 ? is there any change in speed or smoothness ?
[Samsung Galaxy Nexus] b1337:
Way slower than stock its not for u man
[Samsung Galaxy Nexus] gm007:
You should try by yourself and sure you will like it :)
[Samsung Galaxy Nexus] Tarun95:
o_O
[Samsung Galaxy Nexus] yodanutz01:
thank you very much. you really helped me.
[Samsung Galaxy Nexus] Kappa Lamda:
You should try it for yourself and not listen to any of us. It's not such a big change! Make a nandroid backup... Flash franco's kernel and see the difference! Like it then keep it. Dont like it then restore nand backup.

So simple!

r295 really rocks. Smoothness and battery! Keep up the good work franco! :good:
[Samsung Galaxy Nexus] Fenvarien:
Same here, the gov. control settings don't stick anymore. This is the case since kernel r295.

Since app version 7.1.1 I get an FC on boot, like Osmosis already reported. My busybox ist 1.20.2-stericson.
[Samsung Galaxy Nexus] Culex316:
I am having the same issue with stock 4.1.2. Rom and 7.1.1.version of franco app.
[Samsung Galaxy Nexus] Nighthound:
Posted this sometime ago, but didn't get any replies, so I'm reposting this. Now I'm using r295 (384-1228), stock voltages, no power modes, 6/7/6/3. The problem still appears. Normally my phone will be very smooth, but some times I will notice my phone stuttering, and sure enough when I check, CPU1 is stuck in offline mode.
[Samsung Galaxy Nexus] Tommy_FIN:
I take it back. Sound is still there. Very random but still there. With 729-1036 issue is gone. Also the batterylife is about the same as 230-1036. Looks like I'm sticking with these speeds for now...
[Samsung Galaxy Nexus] dehein:
Some noon question here. I have not been undervolting my gnex, but since 295 I just tried it. Do I have to deactivate SR or something? What are some recommended values of you guys? Do you undervolt IVA or core? Or only CPU?

I am currently using these values:

192@ 800

384@ 950

729@1100

1036@1175

1228@1200

But I have some stuttering any suggestions? Although screen on time is so good!
[Samsung Galaxy Nexus] gialandra:
Is it a bad idea that someone makes a google spreadsheet where every user can put (and read for newbie) own UV settings?
[Samsung Galaxy Nexus] G-DannY:
R295 with 192mhz@725mv is EPIC.

Epic Battery life and Epic Smoothness.

now please franco allow to make UV setting stick at reboot and it will be perfect.
[Samsung Galaxy Nexus] kyokeun1234:
Anyone had signal loss issue with 192 mhz?

Swyped on my Galaxy Nexus running AOKP with Franco Kernel
[Samsung Galaxy Nexus] EDNYLaw:
He will not do that for many reasons. Make an init.d script and they will stick at a reboot. It take no time at all.

Sent from my Galaxy Nexus using Xparent Blue Tapatalk 2
[Samsung Galaxy Nexus] odin13:
Or use trickster mod ( paid version ) :D

Verstuurd van mijn Galaxy Nexus met Tapatalk
[Samsung Galaxy Nexus] gautam_nexus:
i am using trickster free...i can also select scheduler which is not there in franco app
[Samsung Galaxy Nexus] teriemer:
Fu.. r295/384gpu is fast and smooth. With my govenor setting (see my signature) it has set the bar at a new level.

So blazing fast and snappy - I can almost not believe it. You're the king Franco :good:

BTW - I don't OC or UV. My freq. is min 384 and max 1228.

Let's se about battery. So far I've got 19 hours and 65% left, screen on for 1:05. No playing, just phone, sms, gmail and checking XDA ;)
[Samsung Galaxy Nexus] supernova_00:
Completely agree!

Nope, no problems what so ever, even with UV to 725mV
[Samsung Galaxy Nexus] shawnaye:
I can only uv to 775 =( if I uv to anything lower and reboot. When my phone is done rebooting and the screen goes off. It can't come back on.
[Samsung Galaxy Nexus] Hans QC:
I have the same problem: at every reboot the Franco Kernel app force closes.