yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] szkorhetz:
For me kernel seems to make the most of the damage.

I have not seen this before r33.
[ONE Original Android Development] shure2:
What effects will this have on actual use? Thanks for the tip, I'm trying it...
[ONE Original Android Development] wajahebat:
You should use stock battery stat screenshot, on my experience no matter what kernel ive used, on GSamBattery Monitor, kernel is always at the top eventho i have good battery life, and it doesnt reflect to other battery stats especially stock.

The term itself is self explanatory, it will prevent the apps from WakingUp your device from Deep Sleep state, also prevent the apps to make such wakelocks and keeping your phone awake all the time
[ONE Original Android Development] shadow47:
This is the highest I got with this device. Thanks Franco. Running r33 on cm11s Xnph44
[ONE Original Android Development] hasnol143:
You leave data off?
[ONE Original Android Development] shadow47:
I have set up tasker script That syncs Data every hour. And also when I open particular apps.
[ONE Original Android Development] wrapcaesar:
I started having random reboots after installing r33 franco kernel....

How do I solve this??? I already installed stock kernel and it continues to do random reboots..

please help me
[ONE Original Android Development] kaibosh99:
Try booting into recovery and wiping dal/cache and then rebooting. If you still have problems do a full dirty flash of your rom (and another dal/cache) and try that. After that, you will need to do a factory reset and start from scratch.
[ONE Original Android Development] wrapcaesar:
Thanks!!! I'll try and tell if that did work...
[ONE Original Android Development] evanovici:
what are your settings? I'm using greenify+amplify, killing google services on my +1 but never ever got past 4-5h screen on time.
[ONE Original Android Development] shadow47:
I use greenify as well. I have denied "keep awake" for all Google services and Facebook in privacy setting.
[ONE Original Android Development] Hilmesh:
Hey shadow which Google services? Just Google play or other things also?
[ONE Original Android Development] jackmacbunton:
Cm Nightlys???

This might be a bit of a stupid question but, if i install the cm nightlys with franco r33 when i get a OTA nightly will it remove the franco kernel?
[ONE Original Android Development] pat7:
Hello:D,

following my first flash (official ROM + TWRP Recovery + Franco Kernel r24, r25, r30) when I éteignai my One, he only restart the battery icon! Tonight, with the r33 it works flawless. It remains to see the battery consumption to be thrilled.

Thank you.:fingers-crossed:
[ONE Original Android Development] latedays101:
yes you have to reflash r33 again everytime you install a new nightly.
[ONE Original Android Development] ChefChaudart:
But you are French !!! :laugh:
[ONE Original Android Development] pat7:
:highfive: Hi, yes mister, French. ;)
[ONE Original Android Development] effry:
A new touch firmware has been merged in cm12 it s possible to include it in the current kernel?

http://review.cyanogenmod.org/#/c/77918/
[ONE Original Android Development] sToRm1nG:
Already posted this. According to franciscofranco its only for a different panel revisions.
[ONE Original Android Development] effry:
If you read the commit comments it actually fixes an issue. I tested it on lollipop and the touch felt more responsive (placebo?)
[ONE Original Android Development] zephiK:
Franco said,
[ONE Original Android Development] Technecium:
I'm done with Sergio. He treats me like a ragdoll.

Sorry, couldn't help it.

But I would welcome any possible fixes that may be out there. Even a test kernel.
[ONE Original Android Development] rlex:
It seems like r33 doesn't have kexec support since multirom stopped working. Any comments?
[ONE Original Android Development] mmurphmsu:
Please search before asking the same question that has been asked at least 5 times in the last few pages.
[ONE Original Android Development] laulau42400:
Ok but there is there an answer?

OnePlus one et Tapaltak
[ONE Original Android Development] zephiK:
Yes there is. Search the thread on why it's removed, search the thread for the keyword kexec and you'll find it.
[ONE Original Android Development] laulau42400:
---------- Post added at 07:44 PM ---------- Previous post was at 07:26 PM ----------

ok
[ONE Original Android Development] Vonnegut:
http://review.cyanogenmod.org/#/c/77918/

@Matt this is specific to the Oppo Find7, which registers ghost touches and is unresponsive when using a screen protector. i talked to an Oppo engineer and he provided me this firmware, which fixed the issue for every user.
[ONE Original Android Development] effry:
i already noticed the "specific for find7"... so why it has been included even in the current cm12 kernel? maybe the touch panel is just the same and i can confirm that the touch is better with this commit
[ONE Original Android Development] 1/4 Life:
Touch panel is the same. The Find 7 and OPO share most base parts.
[ONE Original Android Development] Red5:
Im curious to know what Franco thinks about all this new touch panel firmware, and why it was merged into nightlys for our device.
[ONE Original Android Development] zephiK:
Its not merged yet, its under review.
[ONE Original Android Development] Solid-Dado:
Hi Franco, do you have any plan to make a compatible version of your kernel with the CM12 rom?

Thanks :)
[ONE Original Android Development] hughfollett:
Once the first ota come out, yes
[ONE Original Android Development] wrapcaesar:
Hey guys

Please help me

I started having random reboots after installing this kernel (r33). Then i did procedure to put the OPO everything stock... I unlocked bootloader and root and ****.....

After that I restored data and system through TWRP.. Maybe i shouldn't restore both.. maybe just data no??

PS: i still have random reboots when wifi is on :c all because i installed franco kernel!

Do you think i should do that again and only restore data?
[ONE Original Android Development] Wisiwyg:
Running r33 with Calkulin's OPlus v2.1 and all is working very well. I'm getting a 24 hr battery life with 35% still left with moderate usage.

Thank you Franco. Great work!
[ONE Original Android Development] NOSTALGIA:
noob question. will r31 work with multirom ?
[ONE Original Android Development] kairock:
help guys....so i just installed r33... and got a reboot soon after when playing a game.... i did wipe dalvik/cache as usual.

r32 was superb, i want to go back there, can i just reflash it back to r32 with the zip file? or do i have to restore a nandroid backup.
[ONE Original Android Development] UyEaH:
just flash r32 over it ....no problem
[ONE Original Android Development] JFK1997:
But remember video recording does not work on r 32!
[ONE Original Android Development] Red5:
Anyone know why we dont have the cast screen option on our phones? (I know this isnt kernel related, but the brightest people in the OPO forum all come to this thread)
[ONE Original Android Development] ek69:
I think that was the last kernel version that multirom worked with so yes.

After that it won't work
[ONE Original Android Development] zephiK:
Its present on the early CM12 builds :p haven't tried it yet though.
[ONE Original Android Development] mmurphmsu:
Are you talking about the option under Settings >> Display & Lights >> Cast screen?
[ONE Original Android Development] Martin-Doc:
Regarding the loss of the kexec hardboot patch - How many of you actually use encryption on your phone?
[ONE Original Android Development] Technecium:
I don't use either but encryption, which is a standard feature on Android and noted to be the default in the future, would seem to trump kexec hardboot.

Until the two can coexist, my vote is cast to not break encryption, as users would expect it to be available if they decide or are required to enable it.

Cherry-picking commits and rolling your own is not that hard.

Essentially, you're asking someone to break the locking mechanism all of your neighbors doors so that you can change your curtains if the mood takes you.
[ONE Original Android Development] zephiK:
So far only Nexus 6 and Nexus 9 have encryption by default and cannot be deactivated unless you use a custom kernel that disables force encrypt. The other devices such as Nexus 5, Nexus 4, Nexus 7 do not have encryption on, the user has to manually enable it.
[ONE Original Android Development] shadow47:
Hi guys. I am having a problem and I know it's not kernel related. I would like the experts here to point me in the right direction.

Check the image attached. I can't figure out from where this error is coming. It stays like that till I put the device to sleep. Sorry for this is OT.

Edit - I have cleared dalvik cache and checked. This error returns. I have a hunch that this is related to tasker and greenify.
[ONE Original Android Development] Tzfardaya:
His argument is that the option to enable it is part of the stock system, not that it's enabled by default... Multirom is not part of stock, and obviously not available out of the box.
[ONE Original Android Development] zephiK:
From my understanding of his words, it made it seem he was implying that encryption was enabled by default. I was just saying that it wasn't enabled by default unless its a N6/N9.

But yeah, if anything, its something that MultiROM needs to resolve in their kexec to not break the encryption feature.
[ONE Original Android Development] Black Forest:
Can I now encrypt my opo with r33?

And will the encryption wipe my device?

¹+¹
[ONE Original Android Development] Technecium:
Yes

No
[ONE Original Android Development] Tzfardaya:
Yeah, re-read that section you quoted/highlighted from him... Standard feature.. Default in the future...
[ONE Original Android Development] Black Forest:
I encrypted my opo now, but after a reboot it stuck at the decryption.
[ONE Original Android Development] miv_3180:
Hi guys. Yesterday I've installed Google Play Services 6.5.86 and today I noticed that Android OS chew more battery than the screen wich never happened before. Have you tried the new google play serviced app? What's your experince? Thx. I'm om 33R btw.
[ONE Original Android Development] lordlambda:
Get warlock detector. I had massive drain on wearable/services. Disable these services solved my drain. You can google it for further details.

Pls use next time the search function and post in related threads. Here Pls only kernel related stuff.
[ONE Original Android Development] mamba720027:
Also try Follow this fellow recommendations in quote below which is found on Page 721. I tried both and took it a step further with applying it to some additional apps and getting the pro version of that exposed module and just applying recommended settings. Had 0.4% drain in betterbatterystats while I had left device battery at 96% and leave it just sitting their for over 4 hours and remained at 96% after wakep. So a 0% drop in that time period. Android OS has been lower ever since.
[ONE Original Android Development] miv_3180:
I've already blocked "wake up" and "keep awake" the google play services in guard privacy. Never had this behaviour before. It's strange, every time I've been checking the battery stats screen was on top with the biggest drain ofcourse. Tomorrow I'll give it another go. Also updated Google Play Services to 6.5.87 version. Lets see how it goes.
[ONE Original Android Development] paychex:
My experience is manually updating Play Services eventually leads to problems. Especially since there are multiple different versions now with each update
[ONE Original Android Development] gbbaran:
USB Mass Storage Mode

Hi [MENTION=3292224]franciscofranco[/MENTION]

Looks like There is a new support for UMS(USB Mass Storage Mode when connected to PC) in the latest nightly... Can you make an r34 and include that? Thanks :)
[ONE Original Android Development] Vonnegut:
You don't really have the slightest clue about kitkat, do you?
[ONE Original Android Development] gbbaran:
Would you like to explain anything regarding this then please go ahead!!! Thanks

---------- Post added at 04:37 PM ---------- Previous post was at 04:15 PM ----------

For Mr.Vonnegut who has all the worldly knowledge about Android... Oh and Especially kitkat

http://review.cyanogenmod.org/#/c/77001/

http://review.cyanogenmod.org/#/c/78212/
[ONE Original Android Development] Technecium:
It's quite simple and doesn't require an explanation. It's just not part of the kernel.
[ONE Original Android Development] gbbaran:
Thank you for your reply... I like your attitude which is unlike others who just put up some rhethorical question. Much appreciated!!!
[ONE Original Android Development] Vonnegut:
Read throughly both articles...

http://teamw.in/DataMedia

http://www.howtogeek.com/192732/android-usb-connections-explained-mtp-ptp-and-usb-mass-storage/

...then come back and answer this easy question: Why is not possibile to mount a single EXT4 folder (namely the /data/media/0) in USB mode?
[ONE Original Android Development] aex90832:
Stupid question: No MultiRom support in r33?
[ONE Original Android Development] laulau42400:
No

OnePlus one et Tapaltak
[ONE Original Android Development] superiscch:
Stupid question: did you even try entering 'multirom' in the search?
[ONE Original Android Development] ivan0909:
Is it or is it possible to increase the intensity of the vibration? My OPO has a very low vibration.
[ONE Original Android Development] zephiK:
Use FKU (or any other kernel related app or do it manually -- google on how to do it manually) and change the vibration intensity from 25 (default I believe) to 31 (maximum).
[ONE Original Android Development] lordlambda:
Next time Pls use the search fiction and don't spam threads with questions that are a 100times answered.
[ONE Original Android Development] ivan0909:
Yes, i have it on maximun 31, but it isnt enought. And no one kernel has more than 31 option.
[ONE Original Android Development] lordlambda:
sys/devices/virtual/timed_output/vibrator/vtg_level or increase vtg_max probably will help
[ONE Original Android Development] zephiK:
31 is the maximum value on this phone. That's why you can't exceed it. The oneplus one vibrator motor isn't the same motor youd normally see on Samsung devices where the phone rattles.
[ONE Original Android Development] hasnol143:
Can we just get r34? It will be exactly like r33, but now i'll have a newer number to flash lol
[ONE Original Android Development] Technecium:
Francisco, I have been using a Lollipop beta by k900 for the last 24 hours and just wanted to comment that all of my touch related issues are gone.

I don't know if this is a result of firmware, the OS, or a combination of both. However, it might be worth looking. It really is a world of difference.

I will try to track down the source code that was used for this build and compare but I'm off to work and just don't have time.
[ONE Original Android Development] omvir:
I'm assuming you flashed his v8?
[ONE Original Android Development] BrianAllred:
K900 cherry picks an updated firmware provided to CM from an Oppo engineer. I'm unsure if Franco uses this in his kernel, but it's here: http://review.cyanogenmod.org/#/c/77918/
[ONE Original Android Development] djsarab:
Hi, I have a quick question. I'm on stock 44s and would like to flash this kernel, would it affect my chances of getting OTA's (there was something abt it in the OP, but was not really sure).
[ONE Original Android Development] jasonsaw96:
does anyone having the issue being unable to upload videos on instagram? i have been having this issue for a long time...it stucks in the middle
[ONE Original Android Development] Vonnegut:
If i'm not wrong, it still does change the name of one binary that could lead to the abortion of the next OTA.

You have 3 easy ways to cope with that before installing the next OTA:

A) renaming thermal-engine.bak back to thermal-engine

B) make a full nandroid backup or even a partial one including only boot + system. That way you'll be able to restore your beloved brand new system to the stock one whenever you want to.

C) downloading the official 44S fastboot zip, then flashing both the boot and the system images.
[ONE Original Android Development] djsarab:
Cool, thanks a lot mate, that answers my question perfectly. I have a nandroid backup, i'll go with the renaming engine. But in any case a new CM update doesn't seem to be in the horizon :)
[ONE Original Android Development] Vonnegut:
Yep...next stop will be the Lollipop station IMHO.
[ONE Original Android Development] razer_ins:
Energoefficiency awesome. Thanks Francisco. My phone lives 3+ days with it.
[ONE Original Android Development] szkorhetz:
Screen On Time is a better measurement.
[ONE Original Android Development] Technecium:
I'm not set up to build at the moment but it may be worth my time just to test.
[ONE Original Android Development] Hana88:
How can i renaming the name file?
[ONE Original Android Development] Spannaa:
Like it says in the first post:

Use root explorer or similar.
[ONE Original Android Development] BrianAllred:
I went from rooted 44S with Franco's R33 to my own build of Lollipop with that cherry pick and haven't noticed any difference. But then again, my touch issues were never as bad as some others have reported in this thread.
[ONE Original Android Development] maximosm:
The following changes only apply if you have the referenced files, otherwise this is not for you.<br />

1 - Rename /system/bin/thermal-engine.bak to /system/bin/thermal-engine etc....

I can't understand. If we have this file without .bak what we doing?
[ONE Original Android Development] Spannaa:
It's quite simple...

If you have /system/bin/thermal-engine.bak, rename it to /system/bin/thermal-engine

If you don't, then miss out step 1. and move on to step 2.
[ONE Original Android Development] Hana88:
But after these 2 change, we have to reflash the stock kernel before the ota or not?
[ONE Original Android Development] Spannaa:
No, the OTA doesn't check which kernel you have - it'll replace it with the stock kernel anyway.
[ONE Original Android Development] ivan0909:
I Cant increase it.
[ONE Original Android Development] Technecium:
I'm setting up to build a test kernel to try out the touch firmware that seems to help my device. I haven't worked with this kernel code so I have a few questions.

Which repo branch Franco is currrently using for 44r 11S kernel, asop, cm-11.0 or cm-12.0?

aosp last commit was 11/08

cm-11.0 last commit was 10/07

cm-12.0 last commit was 11/18

Since the latest kernel changelog is 11/17 it leads me to believe he's using cm-12.0 but I just want to make sure.

And which defconfig, franco_defconfig or cyanogenmod_bacon_defconfig?

Thx
[ONE Original Android Development] BrianAllred:
You can't necessarily go by commits. The whole purpose of cherry picks is to integrate a change that hasn't been committed to a repo yet, and Franco cherry picks his touch screen firmware. You'll have to ask Franco what he's cherry picking to know for sure.
[ONE Original Android Development] Technecium:
I'm asking which of Franco's branches, not cyanogen.
[ONE Original Android Development] DerRomtester:
Franco is currently using cm-12 branch. Because the kernel version is 3.4.67. A higher version number than cm-11 or aosp branch.

For the defconfig you have to ask franco yourself ( i think he forgot to push it to his git account, because on cm11 and aosp branch he is using his own franco_defconfig)

But i can say for sure that he isnt using cyanogenmod_bacon_defconfig because franco has disabled some schedulers in his kernel but they are enabled in cyanogenmod_bacon_defconfig.
[ONE Original Android Development] Hana88:
if i flash the stock kernel, i have to flash the WLAN stock driver anyway?
[ONE Original Android Development] 1/4 Life:
This is incorrect for what he's looking to do.

The CM11 branch is no longer used, AOSP is the current release branch for all OPO Franco Kernels.

CM12 is for lollipop and more than likely incomplete since it has not been released.
[ONE Original Android Development] UyEaH:
hey hey
[ONE Original Android Development] DerRomtester:
Cm12 branch isnt incomplete. Franco used this branch for r33 . He rebased his complete kernel to cm12 branch. ( but this kernel will not work on cm12 because of the cm11 ramdisk)
[ONE Original Android Development] Technecium:
FWIW, I decided that easiest way was to just reuse the .config and ramdisk from r33. I'm building against cm-12.0 branch. If it builds and boots, I'll try the patch from cyanogenmod.

Today my touch seems to be ok, maybe it's a weather thing, or aliens. Most likely it's just because it's Tuesday. I like Tuesdays.

EDIT 1: Daahh.. failed to build. Oh well.

EDIT 2: Just flipped back to the Lollipop to enjoy the lack of wonky touch, and had wonky touch.

So it appears the firmware nor Lollipop help. It's either aliens or Tuesday. I hate Tuesdays.
[ONE Original Android Development] maximosm:
Is there any one know what is this wakelock eventx-xxx. I have the in my 1+ with stock Rom and Franco kernel.
[ONE Original Android Development] djsarab:
Yeah with the frequency of updates stretched far and wide Lollipop could be very well the next stop. But since the stable CM12 build slated to come out in Feb, there might be a minor release after all. Gotta get a taste of Lollipop and fast :)

There was no .bak file so I guess nandroid backup it is.
[ONE Original Android Development] szkorhetz:
R33 is way off. Antutu battery tester, shortest version got 9500 point with R33, 10600 with stock. I got just 4 hours of SOT, while I used to have 6. No other gimmicks, just kernel change..

Back to stock for a while then, I guess.
[ONE Original Android Development] DerRomtester:
Could you pls post partitial wakelock? I dont think it is a kernel problem
[ONE Original Android Development] chenrp:
what about fast charging. i don't see any option of that.

i am running 33 and mahdi rom and not been able to see the charging rate nor option to fast charge.

thanks
[ONE Original Android Development] kaibosh99:
It has been mentioned many times, I don't think franco considers it a priority. Honestly, even if you have have lost all your wall warts how many people actually have the ability to push more than 440mA out of their pc's USB ports?
[ONE Original Android Development] Tzfardaya:
Apparently anyone with USB 3, and those of us with USB charge ports (mine is capable of putting out 1.2A)
[ONE Original Android Development] pat7:
I've realized that the OPO original charger with the USB cable, charge four times faster than with any other charger (less than two hours).

:D
[ONE Original Android Development] chenrp:
i am getting 300ma from usb2 and 700ma from usb3 on a short cable.
[ONE Original Android Development] n0rmal90:
I don't know how but this kernel fixed my problem with wifi crash/drop connection. Thanks :)
[ONE Original Android Development] ek69:
How are you checking this?
[ONE Original Android Development] N.Tesla:
[MENTION=253258]3c[/MENTION] Toolbox works fine. :good:

Free: https://play.google.com/store/apps/details?id=ccc71.at.free

Pro: https://play.google.com/store/apps/details?id=ccc71.at
[ONE Original Android Development] Tzfardaya:
Sounds about right with the phone on/used.
[ONE Original Android Development] paychex:
Kernel wakelocks don't tell you much. Anything abnormal in partial wakelocks?
[ONE Original Android Development] 1337jay:
It's has 2.0A output, all other chargers you tried probably had 1.0A or 1.5A output.
[ONE Original Android Development] Galactus:
6ft blackberry playbook charger for £3 charges just as fast :p
[ONE Original Android Development] zephiK:
I wonder if I used my Turbo Charger on the OPO if it would charge as fast as a Turbo Charged device. Makes me wonder why OPO isn't on the list as it does use a Snapdragon 801 and other 801 devices are on it. https://www.qualcomm.com/products/snapdragon/devices/all?feature=Quick Charge 2.0
[ONE Original Android Development] 1337jay:
I think I've read somewhere it works, not sure though. You should try and report back!
[ONE Original Android Development] Tzfardaya:
Not just the soc, requires more hardware as well. Specifically in the charge circuits. Probably missing from the opo to keep costs down.

But test and let us know.