yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] franciscofranco:
It still amazes me that, after I get thrashed publicly, I go all the way to provide clear instructions and restore mechanisms and there are so many people asking stuff that is written in the OP.

It's simple, run the steps I provide. If you don't have the .bak thermal engine then there's NOTHING for you to do, just live your life happy, you're done. I know English is not the main language of some of you, but damnit, it's clear instructions.

Don't overly complicate what's easy.
[ONE Original Android Development] ChefChaudart:
e eu sou tão estúpido, e bebia muito vinho verde !
[ONE Original Android Development] kankuman:
Using Cyanogenmod 11 nightlies

Hi!

I am using Cyanogenmod 11 nightlies, and I wonder I should flash the kernel from the "For AOSP roms" link or from the one "For CM11S only" one. I want to give a try to this awesome kernel now that I own a Oneplus ;)

Thanks a lot,

Mikel
[ONE Original Android Development] franciscofranco:
Just flash whatever, they work the same now.
[ONE Original Android Development] Technecium:
Go outside or just look out your window. Look around your neighborhood. Look at the streets. Look at the cars. Look at the electrical poles. Look at the buildings. You know what's amazing? That it's all still standing and working seeing how nobody RTFM anymore. :D
[ONE Original Android Development] CtlAltDefeat:
I've tried to research this subject of CAF/CM11/CM11S/AOSP based kernels but I haven't been able to find any conclusive information on what it's all about.

Do all kernels nowadays support every ROM despite advertising for a specific type ROM? Why doesn't this kernel work on OmniROM for example? It's all very confusing to me, is there a chance you could give some kind of comprehensive explanation?
[ONE Original Android Development] J0ker 82:
Just a quick question.

I just installed 44s. Does r31 work on the last firmware version?
[ONE Original Android Development] Rycon33:
^^ yes
[ONE Original Android Development] mohd syafik:
Of course.. It works without any problem
[ONE Original Android Development] kaibosh99:
You don't need... to research... Just take a deep breath, and go over the very first post in this thread. All the information you need is right there. CM11S is the bone stock Rom from Cyanogenmod, and roms like Omnirom or Mahdi are AOSP. Know what Rom you are running or want to run, and just read the OP. I would guess you are already rooted and have an unlocked bootloader, make yourself a nice safe Nandroid in recovery and then jump in with both feet soldier.
[ONE Original Android Development] Hzu:
Rename /system/bin/thermal-engine.bak to thermal-engine.
[ONE Original Android Development] franciscofranco:
Just flash it, don't complicate.
[ONE Original Android Development] franciscofranco:
Mpdecision is disabled on FK...
[ONE Original Android Development] tiny4579:
I was referring to someone who was trying to go to stock or a different kernel. Though thinking about it, mpdecision can just be stopped for kernels using a different hotplug. It was the thermald which needed to be restored when flashing an ota or another kernel. That part has been mentioned in this thread.

I was aware this kernel doesn't use mpdecision but rather a custom hotplug driver.
[ONE Original Android Development] rajesh1136:
Ya. It was for me to go back to stock. you said restoring boot.img will not give mpdecision need to dirty flash ROM :)
[ONE Original Android Development] franciscofranco:
You dont need to reflash everything, just stock boot.img then another Kernel of your choice, or another Kernel that ships with the ramdisk.
[ONE Original Android Development] tiny4579:
I was wrong :(

But thermal-engine.bak would need to be renamed back.
[ONE Original Android Development] CtlAltDefeat:
But it doesn't work on OmniROM :(
[ONE Original Android Development] dafonehacker:
Omnirom is incompatible with most kernels.
[ONE Original Android Development] tiny4579:
Yeah they use a lot less caf/cm in their device and kernel. So that doesn't surprise me.
[ONE Original Android Development] luv4greenleaves:
Okay, lots of things going around here.

Do I need to or not rename the thermal engine back to the. Bak extension or not after 44S OTA and flashing 31???
[ONE Original Android Development] ravvio:
Renaming and flashing wifi stock drivers has to be done only before you flash modded OTA zip i.e. when you are on 38r. After flashing the modded OTA zip you just need to flash supersu zip reboot and then flash franco kernel. I performed these steps everythings working good.
[ONE Original Android Development] jark99:
Does anyone know why WiFi drops in and out? I've only been on 38R since release and the last few kernel updates seems to drop WiFi connection.
[ONE Original Android Development] tiny4579:
I've had WiFi drops on stock. Where it doesn't connect and you have to toggle it but it shows enabled?
[ONE Original Android Development] Galactus:
The WiFi drops I get are understandable since my 5ghz connection struggles to pass through in to my kitchen. What annoys me is when I am within range of the signal and it doesn't reconnect unless I go in to the WiFi settings menu
[ONE Original Android Development] Funk Wizard:
Installation

I am Running Mahdi Rom 2.9 on my OPO and was looking to flash the Franco Kernel,

Have downloaded R31 AOSP version zip of Franco Kernel

Do i just flash the zip through TWRP and then wipe the data or is there more to the installation? Also do I need to backup the ROM before flashing R31. Please suggest.
[ONE Original Android Development] PaoloMix09:
Just flash the kernel through TWRP; no need to wipe anything.

Sent from crispy tocino
[ONE Original Android Development] omino323:
So I'm on 38r with Franco r31 on my oneplus and for some reason every call incoming or outgoing get dropped the minute they get connected... So frustrating... Not like this could be kernel related right?... I only ask bc it started happening after flashing r31...
[ONE Original Android Development] edgie168:
Try flashing r30 then r31.
[ONE Original Android Development] Vonnegut:
Just the restore the backup you made just before installing the R31 and check.
[ONE Original Android Development] Hzu:
We had to rename it to flash the 38R OTA previously so that it would not fail.

Do it before performing the update.
[ONE Original Android Development] luv4greenleaves:
I understand that.. What I'm asking if I have to rename it back after doing the OTA and flashing the kernel?
[ONE Original Android Development] drewbot95:
Don't know why every time a new OTA comes out, there's always the same questions about updating the kernel.

Instructions are clear, works every single time

Sent from my OnePlus One
[ONE Original Android Development] franciscofranco:
Absolutely unrelated to the Kernel.

Dude, no. If it you had to do that I would've written it in the instructions.
[ONE Original Android Development] Tzfardaya:
Yes, the metaphor was supposed to stink...

And you come across as someone who doesn't actually take the time to comprehend what was written... So I'll repeat myself, just for you...

I know that bugs won't hit every device, however, the difference between the devices that are hit and are not hit is usually the hardware or additional software.

Those of us who aren't affected and can't replicate the bugs can't test for the causes.. So... We need you to run the tests to help narrow down what the possible causes are...

So, keep whining that the rest of us are treating your problem like it's imaginary, or, you can help us diagnose it for you.
[ONE Original Android Development] Technecium:
Please please get into the habit of making backups. It only takes a minute or so but can save you so much time and effort later.

You can flash through twrp but I would suggest buying FKU from Play.

It has already been said but, no, you don't need to wipe anything.
[ONE Original Android Development] oneplus:
Phone runs slow with this kernel.
[ONE Original Android Development] Andrew025:
Lol
[ONE Original Android Development] Technecium:
Then it should be easy to catch.

BA-doom, Ching!
[ONE Original Android Development] kaibosh99:
Jesus... There is a pretentious whiff in this thread that isn't warranted. I understand the annoyance of people asking questions over and over again when the answers are clearly spelled out either in the OP or two posts above theirs. My post still stands as defense for the people who *do* know what they are doing, who have read all the pertinent info, and yet they have a pretty nasty bug that ONLY pops up when updating the kernel and nothing else. For the most part these are people that are well aware of checking for 'other causes', people that shut off all xposed modules, people that have been in this scene as long as you and I. Also, for the record do your own reading because as I have said many times I have never, ever had a single problem with mahdi rom, this kernel, or any combination of dirty flashing in whatever order. I come from a long history of Note 2 roms where sometimes the solutions to weird glitches didn't make sense, and yet they worked. As an example some issues very similar to these could be solved instantly by doing a battery pull, even a hard shutdown and reboot wouldn't do it. Doesn't make sense, right? Too bad, it worked. After troubleshooting computer problems since the days on a Pet 2001, I can assure you oddball glitches do not always follow the rules of pure logic that one would assume devices like this should adhere to.

In general franco's snarling responses to questions answered over and over again are warranted, but this thread in general is a little too quick to jump on people who have serious problems pop up *directly* as a result of flashing a newer version of the kernel and doing nothing else to explain it. Again, these people aren't n00bs, they just want a little advice/help before they undertake the rather drastic step of formatting the internal SD. And yes, I said *format*, because in some case factory wipes do not fix the most stubborn of glitches.
[ONE Original Android Development] Tzfardaya:
And you're missing my point that just because the problem occurs upon updating the kernel does not always mean that the kernel *alone* is at fault. For a bug to hit device 'a' and not device 'b' means that something between the two is different, either a difference caused by hardware tolerances, or by installed software. (and no, just "turning off" xposed modules does not always return the system to a proper pre-xposed state)

A good way to verify that the issue is truly due to the kernel would be a full clean wipe (test for issue on unmodded rom of choice) then Franco kernel install (no other mods)

Yes, that is a fairly extreme step, but with proper off-device nandroid backups, not a completely irreversible one. It is also the quickest way to determine if the problem is (likely) solely the fault of the kernel.
[ONE Original Android Development] kaibosh99:
I will not argue with the awesome insurance that regular nandroids give us. I backup mine directly to a USB drive and sleep well at night as a result. *However*, there are a lot of us who use our phones as serious gaming machines, and between Nandroids and the clunky mess of Titanium Backup it is still best to try everything a person can to solve problems without having to resort to full scale thermo-nuclear wipes in order to test theories. Most of these kinds of problems were invariably blamed by people not completely clearing out 'set on boot' kernel tweaks while swapping kernels in the past, now the new demon seems to be GAPPS that somehow cause untold headaches beyond what you consider possible, and with the OPO in general it seems like there are endless touchscreen and wifi issues even for people who have done the homework, followed the instructions to the letter, and are more than willing to do various levels of wipes/formats/EMP attacks upon their poor phones to solve their problems. Another thing I find baffling is that many people are stating as gospel that you don't need to wipe dal/cache for most changes, well that may be true for some things but honestly this is still the quickest way (along with 'per-app' cache wipes) to try and exorcise ghosts from the system for a LOT of problems out there. Wiping the dal/cache from recovery certainly will never hurt, and has cured many issues in the past.
[ONE Original Android Development] Rycon33:
Alright, this is only my 2nd full-charge cycle after 44s update with the r31. My light/medium usage and on-screen time looks good.

Display on auto-brightness, google and email accts all synced, mainly hangouts, g+ and internet browsing usage with few minutes of watching videos. Been outside on LTE for a little while as well but mostly on WiFi.
[ONE Original Android Development] aznflawless:
I was already on franco 31r and i tried to install the update but twrp comes up then nothing happens. After that I tried the rename /system/bin/thermal-engine.bak to /system/bin/thermal-engine and flashed the WLAN_stock_firmware.zip. After I download the 44R OTA, I click install, and it goes to twrp and then nothing happens after that. Just shows all the options what to flash, etc. I just reboot my device after that.
[ONE Original Android Development] Rycon33:
^^ try manually flashing the update file instead.

So long as you didn't tinker with system files before on your previous firmware, updating manually won't give you problem. You already renamed the thermal-engine file and flashed the stock WLAN zip, should be no problem updating manually. Download the file from here in xda or OnePlus forum if the file isn't there anymore on your cache folder.
[ONE Original Android Development] silvan g:
Dial *#*#4636#*#* and turn off lte only?

Sent from bacon
[ONE Original Android Development] gpelekanos1:
Guys, can 31r kernel be flashed on 44s cm11s latest update? Thanks.
[ONE Original Android Development] shadeofgrey:
If you read back, you'd come to the conclusion that - yes, it's fine.
[ONE Original Android Development] gpelekanos1:
Many thanks. ?
[ONE Original Android Development] Tzfardaya:
Great... Now you're confusing diagnostics with fixes....
[ONE Original Android Development] franciscofranco:
Let's all take a chill pill ok? It's sunday, we should be drinking beers and rest.
[ONE Original Android Development] TiVON:
"Should"... Some of us have work to do :(

Verstuurd vanaf mijn A0001 met Tapatalk
[ONE Original Android Development] shure2:
In Germany it's the day of rest, you're supposed to do f*** all and rest which is what I do
[ONE Original Android Development] LoveMyNewTelephone:
I've flashed 44S stock rom, and 31r FK on both my wife's and my phone. And everything seems to be working fine.

However I don't understand why there was a thermal-engine.bak file on my wife's phone (which I renamed, as instructed), but there was no such file on my phone.

I don't understand, because I've always done the same things on both phones.

Can someone explain, and is this of consequence?
[ONE Original Android Development] LoveMyNewTelephone:
[MENTION=3292224]franciscofranco[/MENTION]

Very funny, I think you've already had your beers [emoji6]

But a would appreciate a real answer. I've bought your app for both phones.
[ONE Original Android Development] franciscofranco:
No offense, but that doesn't mean you'll have a different treatment from anyone else on this forum - but I appreciate it deeply :)

I sincerely have no idea about what you described, and I wouldn't worry about it a single second if I were you :good:
[ONE Original Android Development] LoveMyNewTelephone:
Thanks! That is all I needed to hear! Back to your beers now [emoji6]
[ONE Original Android Development] dipaolnv:
The file wasn't there for my phone either. I still had to flash the WLAN Stock Firmware after the 44S OTA.
[ONE Original Android Development] Blue Winter:
I just can't understand why, if i will open Franco Kernel updater it will show "Your Device is Not Supported"
[ONE Original Android Development] kaibosh99:
After looking for a thermal.bak file for several hours I have initiated an RMA with Cyanogenmod, enough is enough already.
[ONE Original Android Development] Tzfardaya:
I think the beer drinking was part of the problem... ;)
[ONE Original Android Development] Spannaa:
Free version?

This doesn't support the OnePlus One.

Sent by Bacon...
[ONE Original Android Development] lordlambda:
Do you use ART or dalvik?
[ONE Original Android Development] Rycon33:
^^On ART
[ONE Original Android Development] shoman94:
What are people's thoughts on kernel samepage merging?
[ONE Original Android Development] rani9990:
I'm pretty sure it's completely unnecessary for a phone like this with 3GB of ram.
[ONE Original Android Development] suaverc118:
That is amazing battery life! Stock Franco settings? I can never get these numbers with any kernel.
[ONE Original Android Development] Rycon33:
^^yes, stock settings
[ONE Original Android Development] Red5:
Good luck. I hope you have more success than I did. They basically told me no.
[ONE Original Android Development] 1337jay:
ART and not Dalvik tho.
[ONE Original Android Development] Technecium:
With the recent talk of thermal and thermal.bak, I decided to peek and see if I had one. I had thermal-engine but no thermal and no thermal.bak.

However, I have just auto-flashed r31 via FKU. I see /system/bin/thermal-engine but I was under the impression that it gets renamed to thermal-engine.bak which effectively disables mpdecision or whatever the default thermal driver is called.

Should I manually rename thermal-engine to thermal-engine.bak?
[ONE Original Android Development] fkrone:
As long as franco kernel does not rename it automatically you should not do that.
[ONE Original Android Development] Technecium:
I was just confused. I wasn't sure if it was supposed to be renamed and it didn't happen for some reason or another, or if something had changed in the ramdisk. I've found the commit from 11/2 that removes the renaming from the ramdisk.

All good now.

---------- Post added at 04:38 PM ---------- Previous post was at 04:30 PM ----------

Not sure if you're being sarcastic so... for what it's worth.

See my recent post about thermal-engine.

First, it's /system/bin/thermal-engine not /system/bin/thermal.

Second, the ramdisk has been changed and as of 11/2 and thermal-engine is no longer renamed.
[ONE Original Android Development] SinPalabras:
Anyone has stock 44s kernel zip? Couldnt find it anywhere
[ONE Original Android Development] gianton:
Here you go,

https://mega.co.nz/#!wdxw0L7A!Nufx_2iklNQ-hjl-qcsgPXP9nPyZ1u_t6sa7nWsOF8E
[ONE Original Android Development] SinPalabras:
Thnx
[ONE Original Android Development] Spannaa:
Is that the boot.img from the 38R -> 44S OTA update zip?

It's larger in size and has a different CRC32 checksum to mine...
[ONE Original Android Development] gianton:
Yes taken from the OTA 44S zip.
[ONE Original Android Development] franciscofranco:
It's a bit unnecessary with 3Gb of ram and it gives a bit of overhead, but it won't hurt if you enable it.
[ONE Original Android Development] suaverc118:
Impressive. I'm not running that kernel but would like to know what the settings are, all of them please. Thanks.
[ONE Original Android Development] RoundBagel:
WiFi Hotspot

Hey Franco!

Have been using this kernel since 38R alongside your FKU app.

Decided to update to 44S and applied your kernel as instructed in the OP.

My hotspot used to work but I recently found that my hotspot can't be detected

I reverted to stock 44s kernel to see if it worked and it does... so I went again and installed this kernel without success

Do you have any suggestions to how I can get it to work again? everything else works well

Thanks!
[ONE Original Android Development] Rycon33:
lol man, I meant stock settings of Franco kernel ofc. I just flash it and forget, I don't have any app or script for kernel control. No xposed something, no battery guru, no task killer, etc. On ART runtime, though not sure if it does improve battery anyway.

---------- Post added at 12:13 AM ---------- Previous post was at 12:03 AM ----------

I tried just now to test my hotspot as well, running fine here.
[ONE Original Android Development] rogi19:
After clean flashing 44s over 38R with a full wipe, i wanted to flash Franco kernel because i already had good experience with it on 38R. I had no thermal-engine.bak so i had nothing else to do than to flash 44S and then the Franco kernel, but the first thing i noticed is that the Boot animation was very laggy and the phone was hot on the top back. Also the battery drain was very high, i got about 1% drop with 3 minutes sot opposed to 5-6 minutes sot on 38R. Now i clean flashed 44S again and i have no laggy Boot animation and not such high battery drain with stock kernel (around 4 minutes sot per 1%). I would really like to be able to use your kernel with 44s also, because it gives better battery life than stock kernel, but could you tell me where this battery drain is coming from? I also used BBS and there are no suspicous wakelocks, the CPU states are also normal, it isnt running in highest frequency, most of the time its at 300mhz or deep sleep..
[ONE Original Android Development] mamba720027:
Here's to 2 new color profile settings I have been tweaking to bring out the best of the oneplus screen with Franco kernel.

Color Pure - The RGB sliders are adjusted to reduce over saturated colors and bring out clarity. Details in textures for gaming are more apparent,pictures look closer to true color and overall UI in general looks cleaner.

Super Color Burst - These settings is the best I could bring the screen colors out compare to the previous color burst settings I posted which makes the previous look like a far cry. Colors are sensibly hyped in general to satisfy especially those coming from a super amoled screen :thumbup: :D

Link of these 2 settings and previous color profile settings with explination below.

https://www.dropbox.com/sh/g0d975789dq22m9/AAC6nOKVvb2K5RoYk3_i_8bsa?dl=0

http://xdaforums.com/showthread.php?p=56258583
[ONE Original Android Development] franciscofranco:
Good stuff. Currently working on the Display Calibration part of the next-gen FKU, here's a sneak peak of ongoing work.
[ONE Original Android Development] dafonehacker:
Are you doing that on Jelly Bean? ?

Looks nice btw
[ONE Original Android Development] BrianAllred:
I must be too used to default because these are just way too blue for me.
[ONE Original Android Development] mamba720027:
Thanks and that looks great :o . More possibilities

:D

You can be right about some as the blue tends to bring out that luminosityness of white and overall brightening. But defaults are way off of satisfactory colors. Yea it does take time for the eyes to adjust :thumbup:
[ONE Original Android Development] franciscofranco:
On the Galaxy Nexus yes - starting with that one because it has the simplest RGB and Gamma interfaces, then I'll move up to the N7, N4/N5 and Bacon.
[ONE Original Android Development] franciscofranco:
I'm not a psychic I can't guess what's happening on your phone. The Kernel is the same on both 38R and 44R, I'm pretty darn sure you have something keeping your device awake (hint: an app).
[ONE Original Android Development] rogi19:
Psychichs aren't experts in phones and kernels, but from a developer you should expect at least a hint of a clue what may be causing the problem when using his kernel, after an exact description . I haven't installed any apps as it happens already during the first boot, as i already wrote..