yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] abhi08638:
‎(ﾉಥ益ಥ）ﾉ﻿ ┻━┻

You're so naughty
[ONE Original Android Development] Tzfardaya:
Yes... Yes, I am...

And that is why I'm loved.
[ONE Original Android Development] IllUMINATUz:
Hello Everyone, tried my first kernel on my OPO.. just beautiful.. now, I'm not sure whether the battery indicator is broken (showing 100% since a long time - 3.5 hours) or it's really a great kernel..

couple of quick questions..

- where do I see the settings/defaults etc? I am not able to find it. Did a search, leads to a post/thread started by someone else & I'm not able to understand.. please forgive me for that..

(I mean, what's the default governor/powersavings mode/lowest & highest CPU frequency etc.)

- is the paid-app the only way to change the governor and all the perks for this kernel? or can I use trickster mod or other kernel tweakers?

Update : Okay experimented using "Kernel Auditor" - Interactive governor not there.. I get only three options (with trickster also) : Conservative (default), powersave & performance.

am I missing something here?
[ONE Original Android Development] Vekhez:
I could almost gaurantee you that your battery indicator is not calibrated properly, the chances of you staying at 100% for 3.5 hours is very very very slim.
[ONE Original Android Development] Tzfardaya:
Battery has probably lost calibration, or you've added another mod that broke it. You can use most/all kernel config apps to tweak, fku (paid) is specific to the Franco kernels and has all his custom tweaks. I tend to use a mix of fku and tasker for all my kernel control needs.

I don't think Franco has removed the interactive governor, I do know that conservative is his default governor now for most devices (haven't checked the opo for a bit to see)
[ONE Original Android Development] IllUMINATUz:
Is there any specific app that you might recommend for battery calibration..?

Sorry for OT.. I'm currently on the AK kernel now.. Just experimenting with various kernels before I settle.. Loved the Franco kernel back from HTC one x..
[ONE Original Android Development] Tzfardaya:
Run the battery dead, turn phone off, charge to 100%, turn phone on and run dead /or near dead, 1-5% target, basically just need to show the Android system where the 0 and 100% marks are again..
[ONE Original Android Development] WhiteHartMart:
'Smoothness over Benxhmarks' I keep reading and didn't believe it.

I apologise for doubting - running r40 on CM12 nightlies for a few days now and my OPO feels better then ever.

Thank you Franco :)

Brought to you by a CM12 Lollipopped OnePlus One :)
[ONE Original Android Development] Doo Doo:
Is interactive governor missing in r40?
[ONE Original Android Development] cr723:
My screen is over exposed (burning) after flashing this kernel.. any solution?
[ONE Original Android Development] schaggo:
[MENTION=4625971]cr723[/MENTION] http://xdaforums.com/showthread.php?p=59560562
[ONE Original Android Development] AJ RIMMER!:
This is a cross post with the Slim LP thread.

The new 1.0.8 version of Slim LP seems to have a problem with r40. When I flash both, I get stuck on the boot animation.

R40 was working sweetly with Slim LP 1.0.7, but the new flash just doesn't like it.

I tried flashing a few times, in twrp, through fku and flashify, but all the same result.
[ONE Original Android Development] 1ceb0x:
[MENTION=3292224]franciscofranco[/MENTION] - can you please let me know what is the input_boost_freq for the governor in r40?

I switched roms (slimlp currently) and the input boost freq is set at 2.4ghz. Is that the default value?

What about load_threshold from the hotplug? Is that supposed to be 65 in r40?

Thank you!
[ONE Original Android Development] dickenam:
I have 2457 mhz and 65 respectively, both stock and untouched. I think he's patched/edited the gov since r39.
[ONE Original Android Development] Spl4tt:
Hahaha, you good xP

http://xdaforums.com/nexus-4/orig-development/kernel-franco-kernel-r208-t2002782
[ONE Original Android Development] franciscofranco:
Yes, it's gone.

It's called LiveDisplay. Look it up on Settings -> Display...

You gotta ask what the **** those Slim guys did, because I'm using the latest CM Kernel commits and the latest ramdisk.

input_boost_freq -> max freq

load_threshold -> 65
[ONE Original Android Development] Miraries:
Conservative, game not working

Not sure how long you plan on updating the kitkat kernel (if you do) but here's something interesting I noticed.

Game 'World of Goo' doesn't seem to respond to touches when I run your kernel. Just flashed the stock one and it's working again.

Could be due to kernel settings but I left them at default (tried different cpu governors just in case).

EDIT: I wrote about the conservative governor but it seems it's there on your cm12 kernel

(And I haven't tried the lolipop kernel so keep that in mind)
[ONE Original Android Development] MBurns2:
sorry but why no interactive governor ?

thanks for the hard work
[ONE Original Android Development] DerRomtester:
Because conservative seems reacting sensitive to CPU loads and it is tuned for touchboost.
[ONE Original Android Development] MBurns2:
thanks for the explanation.

If it is possibile, isn't better to leave interactive anyway ? I think that there are a lot of people that love interactive.

just my two cents :)
[ONE Original Android Development] DerRomtester:
Just trust francos work. He knows what he is doing.
[ONE Original Android Development] GRMrGecko:
Is kexec-hardboot support going to be added back to the lollipop versiobln? I need it personally.
[ONE Original Android Development] Nebulino:
I want to know if someone else has the problem of "changing screen density" ,in the Rom who have the option, does not apply!

Thanks

I tried the rom + another kernel and it works! :(
[ONE Original Android Development] i2k13:
any tips to making r35 any snappier? i like all the extra's [touchscreen, speaker boost..]

but i feel it's slower than the stock kernel [44s]
[ONE Original Android Development] silvagroup:
ditto ???
[ONE Original Android Development] GRMrGecko:
I meant version. I was typing using my opo.
[ONE Original Android Development] Mayex:
Use APP textdroider_dpi
[ONE Original Android Development] Tzfardaya:
I use root browser myself...
[ONE Original Android Development] danieldmm:
Just create a local.prop file in the root of /data with the screen density you want.

Enviado do meu OnePlus pelo Tapatalk.
[ONE Original Android Development] Tzfardaya:
Ooh, that's probably better for OTA than straight editing build.prop like I do....
[ONE Original Android Development] danieldmm:
No, it's not good because OTA will change build.prop to stock by this returning to the stock DPI, local.prop in /data it will not change by OTA

Enviado do meu OnePlus pelo Tapatalk.
[ONE Original Android Development] Tzfardaya:
That's why I said it would be better for OTA... And with all the changes I make to build.prop it takes a while to edit them back in after OTA (assuming that the OTA hasn't failed because build.prop has been changed.)
[ONE Original Android Development] danieldmm:
Did not understand, you say that it's better build.prop or local.prop? And sorry to [MENTION=3292224]franciscofranco[/MENTION] by the offtopic it's getting here.

Enviado do meu OnePlus pelo Tapatalk.
[ONE Original Android Development] Tzfardaya:
I said local is better... I said I had been using build because I didn't know about local.
[ONE Original Android Development] Hanny:
When you've gotten the yellowish thing, were you under bright sunlight? Its 0% related to kernel because that's how the CM feature - Sunlight Enhancement works. I was also surprise by it the first time I saw it, and I've disabled it since then :)

Without following your N6 development I already upped input boost to 1958 since r38 o.o

heheh, thought that was necessary for a 40k only duration :D especially when I've made my animations 0.5x

Btw bug report. I've gotten multiple non-waking screens since r40. Double tap/power button both couldn't wake the screen. I waited for ~20 seconds then I force rebooted the device. There was one occasion the screen wakes after 10 seconds. No logs grabbed since they were force reboots :( Here to see if anyone has gotten that too.

Nightly 0320

No UV - all default kernel settings

Ambient Display - off

Double tap to wake - on
[ONE Original Android Development] Renosh:
Have you updated the per-app mode app lately [MENTION=3292224]franciscofranco[/MENTION]? Been using it for ages and liked using the dedicated app when I don't wanna mess with kernel settings or when on different kernels. Per app profiles work perfect on the FKU app so not in a hurry just curious. Anyway r40 works fantastic on latest 03/24 nightly though I changed input_boost_duration to 500000 or 0.5 secs for better smoothness. Stock kernel probably boosts for like 2 secs so will save battery either way. Great kernel and love your work.
[ONE Original Android Development] Nebulino:
It doensn't stick
[ONE Original Android Development] MBurns2:
with latest version i had screen flickering after wake up the device with double tap. it happened only once, i had -25 uv, maybe it was related to this ? ty
[ONE Original Android Development] wingsaber:
System UI not responding

Hi Guys,

I am On CM 12 nightly. I am on 23032015 update and I had flashed franco kernel today but after wiping cache and dalvic cache and restarting OPO it gives me unfortunately System UI is not responding error. Please help guys i wanna save battery at the cost of 0% performance drain.:(
[ONE Original Android Development] tsiftsism:
I found this answer on Cyanogen's Community inside G+ and it seems that it's working for many users facing the same issue as you.

Maybe you should try it out.

"Try this, it worked for me. Switch SElinux to permissive, change the vibration intensity, then set SELinux back to enforcing."
[ONE Original Android Development] wingsaber:
HI There,

Tried with above settings but id didnt helped.... any other settings?....Tried with changing SElinux to permissive then changed insanity and then again set SElinux to enforcing but still shows me same error. Please help some body
[ONE Original Android Development] schaggo:
[MENTION=5105112]wingsaber[/MENTION] update the CM build you're using. The kernel is 3 days (and prolly a ton of relevant commits) younger than the rom you use.
[ONE Original Android Development] dud3me:
I've got the same issue! I haven't had to reboot but it sometimes takes 10-20sec of repeatedly pressing the power button to wake the screen. I'm on sundays nightly.
[ONE Original Android Development] Hanny:
Follow up:

Just encountered it, and actually I'm still experiencing it as I type. Power button + double tap are both not working in every trial whenever I turn off the screen with whatever means - power button / double tap status bar / lock screen app.

The way to wake my device up is to charge it, so it will wake up due to charging started. 100% reproducible before I reboot. Not sure if its the digitiser not working, but since the power button also doesn't work, it might as well be a software "wake up the phone" problem in ROM.

Nth fancy is currently running in the background, that would even stop the power button from functioning (only for wake, but still working for sleep). No extra waking apps using any sensors, except dt2w from cm12 settings. And nothing fancy like smartlock or whatever crazy lock / security that I'm using to protect my lock screen.

Putting this here because one of the recent r40 changes is about updating dt2w for CM nightlies. But if Franco didn't do much but just to follow some stuff CM has made to their ROM, then the kernel should have nth to do with it. It may also be helpful if we look at the commits that require custom kernels to change something and adapt, but I don't know where they are. Any input is appreciated, thanks in advance!
[ONE Original Android Development] prox4ion:
removing franco kernel?

Hi I'm on the current 11S 05Q and want to remove franco kernel in preperation for 12S. Can someone elaborate on what procedure I should follow?

My concern is that last time, when I upgraded to 11S 05Q, I was getting weird wifi issues until I flashed the franco kernel. (I've been using franco prior to 05Q). So I want to return to the stock kernel. Much thanks for any help.
[ONE Original Android Development] G-DannY:
had the same problem with r40.

Solved by going back to cm12 stock kernel.

So it's definetly something related to r40.
[ONE Original Android Development] danieldmm:
Lattest jours there been changes over kernel in cm12 source.

Enviado do meu OnePlus pelo Tapatalk.
[ONE Original Android Development] Davisk8:
Moved from cm11s powered by your kernel to bliss pop...flashed r40, everything seems to work really well, no lag, no issues, trying to slight undervolt now... As always thanks for the great work [MENTION=3292224]franciscofranco[/MENTION]
[ONE Original Android Development] Bh4i:
Anything known about 5.1 support? Updated to Euphoria 5.1, and the kernel does not work.
[ONE Original Android Development] MCam435:
I'm running the 5.0.2 Alpha of PA at the moment. Am I right in thinking I can't use franco yet?
[ONE Original Android Development] 1337jay:
It's not updated yet, 5.1 is a whole rebase.

I'm pretty sure you can use r40 for PA 5.0.2.
[ONE Original Android Development] DerRomtester:
No rebase is necessary for 5.1. You only need to update the ramdisk.
[ONE Original Android Development] Bh4i:
I tried flashing it on 5.1, it ended up in a boot-loop :)
[ONE Original Android Development] 1ceb0x:
You will need a kernel which uses any. Kernel ramdisk to work on 5.1
[ONE Original Android Development] DerRomtester:
You dont need a kernel with anykernel ramdisk. You can use any kernel that supports 5.1 e.g. Tyr
[ONE Original Android Development] 1ceb0x:
Strange. AK doesn't support 5.1 yet AFAIK but it works on 5.1 ROMS :)
[ONE Original Android Development] DerRomtester:
It is not strange. It just works because of the anykernel ramdisk. Anykernel ramdisk grabs the ramdisk of the current kernel and packs it with the zImage into a boot.img. A normal kernel has its own ramdisk e.g. Franco kernel. With this normal ramdisk he is able to tweak it more.
[ONE Original Android Development] 1ceb0x:
You are contradicting yourself and ended up to what I said earlier.

I knew AK uses any.kernel ramdisk but I didn't want to come into franco's thread and say "hey, you will need a kernel that uses any.kernel ramdisk for 5.1. try AK because it works" - common courtesy to not mention other kernels here, even though we did.

Thanks for the laughs dude :)
[ONE Original Android Development] DerRomtester:
Ups :)
[ONE Original Android Development] Zach1928:
Can anyone attest to the benefits of ART on r35?
[ONE Original Android Development] usmani:
No.
[ONE Original Android Development] N.Tesla:
Beautiful! Thank you very much! :good: :victory:
[ONE Original Android Development] kumarsid7:
I flashed it and I do not find any change in my battery life. It might even be getting worse. Running liquidsmooth ROM. I'm getting like 5 hours. Any suggestions? Is there a problem with that ROM or something
[ONE Original Android Development] DrNinjaa:
Then please consider going back to ur stock kernel .....because this kernel is awesome and always will be awesome .... i would request u to read the thread religiously and u can know what r u missing in getting the best from this kernel

#HappyFlashing#
[ONE Original Android Development] kumarsid7:
But the thing is the thread is spread out on all the versions. It'll take me days to read all the posts, filter the unwanted ones and understand the whole concept. Anyway I'm going to try tweaking things a little bit maybe that'll help.
[ONE Original Android Development] DrNinjaa:
Use the "search in this thread" option provided by xda to narrow down ur search .

#HappyFlashing#
[ONE Original Android Development] slebit:
I am having great battery life with the default settings. Its really stable for me.
[ONE Original Android Development] Mayex:
Same here! Great kernel
[ONE Original Android Development] soorajnambala:
kexec-hardboot patch ??

kexec-hardboot patch ??

can i use this with multirom ??

sorry if im dumb.... anybody >...
[ONE Original Android Development] NuLLV01D:
Not in Here. Dev removed it due to compatibility issues
[ONE Original Android Development] oscarandjo:
Which was the last version supporting it?
[ONE Original Android Development] NuLLV01D:
It was during the early releases which didn't even support Lollipop.
[ONE Original Android Development] ChriKn:
So that others don't do the sme idiocy as myself...

Franco r40 doesn't work with OxygenOS v1.0.0. You get stuck at boot screen...
[ONE Original Android Development] Mayex:
[MENTION=3292224]franciscofranco[/MENTION]

Are you going to make kernel for Oxygen ? It has strange colors saturation and I hope with franco kernel we would change it. Hope it won't take much time.
[ONE Original Android Development] NuLLV01D:
For that he needs the appropriate kernel sources
[ONE Original Android Development] Blackfireball5:
I seem to be missing my thermal-engine.bak file. Could someone send me theirs or point me to where I can find that come without having to wipe?
[ONE Original Android Development] octagonPerfectionist:
I guess oxygen os won't be getting a franco kernel as they won't be releasing the source code. That's too bad, but I guess not much can be done about that.
[ONE Original Android Development] bpear96:
They are required to release the kernel source because it is licensed under GPL. That I'd all Francisco would need. They are not planning to open up the main ROM source code. But they legally have to release kernel source.
[ONE Original Android Development] octagonPerfectionist:
Oh, that's good to know then. Forgot about GPL. I hope he works on this at some point then, although I can't imagine too many people will be using oxygen os on a daily basis yet so there isn't much incentive to do so right now.
[ONE Original Android Development] bpear96:
Yeah really looking forward to Franco + OxygenOS.

I use to love Paranoid Android. Ran that along with Franco kernel for most of my nexus 4s life. Didn't hesitate at all to flash today's OxygenOS release. Can tell its the paranoid guys working on this. Such a nice experience so far. Minimal but just seems more thought out.
[ONE Original Android Development] octagonPerfectionist:
Yeah I actually really love it so far. It's very smooth and so far very stable. It doesn't have hundreds of unnecessary features and is definitely an excellent base for future updates. The only thing that's missing I guess is Franco Kernel, so I'm definitely looking forward to an OOS version whenever Francisco decides to work on that.

Reading through the thread on the oneplus forum almost gave me cancer though. The oneplus following must be some of the most entitled brats in the android world.
[ONE Original Android Development] bpear96:
Yeah exactly. Its great right now and you can see how much it can improve. Really liking it over cm12. I know exactly what you mean. I don't bother reading most of the stuff there.
[ONE Original Android Development] f41lbl0g:
franco said that he will put it in the next build.
[ONE Original Android Development] raidel00:
Anyone with OxygenOS experiencing ghost swipes and unresponsive taps? I didn't have it on CM12 nightlies, so I attribute it to OxygenOS, but I just can't see how they wouldn't have noticed it throughout their testing and/or how they could not be using the touchscreen firmware that the CM12 nightlies are using. I'm assuming a kernel with the updated touchscreen firmware would possibly fix that right up...so here's to the next franco update! ::D
[ONE Original Android Development] epiquiem:
CM12 nightly 4-4, MultiROM is telling me I don't have kexec hardboot. Using r40. Anyone else have this issue?
[ONE Original Android Development] mchauhan:
I guess Franco Kernel does not supports Multi ROM.
[ONE Original Android Development] hasnol143:
Franco doesn't support multirom

---------- Post added at 11:20 AM ---------- Previous post was at 11:18 AM ----------

Anyone running CM12 04-05 nightly with Franco? Just recently updated my nightly build and wanted to see how its holding up
[ONE Original Android Development] epiquiem:
He said he added support r14.
[ONE Original Android Development] ImbaWind:
If I remembered it right, he removed it later on.
[ONE Original Android Development] epiquiem:
Welp, turns out I went stupid and didn't read all the search results. Only got as far as the one saying it was added in r14. :p

http://xdaforums.com/showpost.php?p=59578831&postcount=8597
[ONE Original Android Development] hasnol143:
Yup he actually removed it later, it was too unstable
[ONE Original Android Development] Hyper4mance2k:
Touch screen input issues.

I'm on CM 12 nightly, no one night seems to be any different than another. If I force reboot the phone it works fine for a few hours then ghost inputs are rampant & it won't recognize touch. I'm on r40.
[ONE Original Android Development] DerRomtester:
This isnt a franco kernel problem.
[ONE Original Android Development] schaggo:
Had them since weeks on every rom I tried. Still have them on OxygenOS. Has nothing to do with neither rom nor kernel. Either the digitizer firmware is full of sh** or its a hardware problem manifesting itself all over the place. Its a most common Oneplus One problem, google for it.

As per the above, I have exactly the same, no matter what rom or kernel I'm on. A reboot fixes it for a couple hours, the most. But as stated, most likely neither a rom nor a kernel problem. I'll know more once my RMA because of this got through.
[ONE Original Android Development] .psd:
Really looking forward to franco for non-cm oneplus one ROMs. I need to get off CM onto a stock ROM so scribd doesn't stop every 120 seconds when the display is off, but I refuse to use any ROM that can't handle franco kernel.

Keep up the good work, franco. From a LONG time customer.
[ONE Original Android Development] AirRailey:
hello

I can flash the r40 on 5.1 Reseurrection ?
[ONE Original Android Development] DerRomtester:
No
[ONE Original Android Development] MKX scorpion:
oxygen os

is there 1 for oxygen os?
[ONE Original Android Development] DerRomtester:
No custom kernel is compatible with oxygen os at the moment. We need the source code for the oxygen os kernel first to build a custom kernel.
[ONE Original Android Development] hasnol143:
I was on latest CM 12 nightly and r40, and was experiencing a lot of wifi signal drops. had to go back to stock kernel.
[ONE Original Android Development] lerkin:
+1. May be merging recent patches in new version of the kernel will help.
[ONE Original Android Development] uragan1987:
ui_print("Installing a virus...");

ui_print("23%...");

ui_print("50%...");

ui_print("77%... There's no escape now, allyourbasearebelongtous!");

ui_print("100%...");

hehe :)

lets see what score comes at antutu with this kernel

---------- Post added at 08:35 PM ---------- Previous post was at 08:04 PM ----------

tested franco kernel, not mine,

with cyanogen kernel, score 45000

with franco 42000-43000 :(
[ONE Original Android Development] jgcaap:
Niceeeeeee ui print hehe

Don't look to benchmarks. This is one of the best kernels I had the opportunity to have flashed on my phone. Is a more efficient kernel.
[ONE Original Android Development] uragan1987:
how you can be so sure about it?

i have to compile this thinks, and only benchmarks like antutu can make a comparison

maybe this kernel nice for save battery
[ONE Original Android Development] DerRomtester:
Use Performance governor for benchmarks
[ONE Original Android Development] jgcaap:
already used this kernel, and was a very happy user with it. everything will depend on the type of system you wish to have delivered. This one if very efficient.
[ONE Original Android Development] lerkin:
Hey, [MENTION=3292224]franciscofranco[/MENTION], can you please take a look at the new Wifi drivers from 12.1 branch, looks like they fixes those Wifi authentication problems.

Edit: tested kernels with new Wifi drivers - still authentication problems are here.