yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] zephiK:
Nope only paid. Even if the free version supported the OPO it would only have the functionality of notifying you when theres a new update; whereas, the paid version has access to the full app where you can tinker with every setting possible.

So when the free version does support OPO, you will still have your money's worth :)
[ONE Original Android Development] vikash0513:
no it doesnt you can still send it back if you got any problems with hardware or software
[ONE Original Android Development] skydayzer:
He knows that... that was just sarcasm...lol
[ONE Original Android Development] Tzfardaya:
Anyone worried about warranties shouldn't be messing around with roms, kernels, and mods...
[ONE Original Android Development] tehpud:
This.

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

I bought the paid fku for two reasons.

1. Support our kernel developer.

2. Support our kernel developer.
[ONE Original Android Development] danyvw:
I bought it for the same reason.
[ONE Original Android Development] vikash0513:
well i am worried cause i dont want to throw away my phone when it is bricked i have read that i can still send it to opo to repair it
[ONE Original Android Development] zephiK:
If you're worried then you should stay using the phone as it is. Chances are if you read instructions carefully you won't brick your phone. Nowadays it's hard to brick a phone, almost everything is recoverable just have to read and not flash zips not for opo
[ONE Original Android Development] MICa.fighter:
Opo will repair your bricked phone but brick repair is not covered by warranty so you will have to pay for the repair.

Swyped from my Oneplus One
[ONE Original Android Development] zephiK:
I heard it takes awhile too as you have to ship your phone all the way to China to have it repaired.
[ONE Original Android Development] jarylw:
I'm only able to get 800-ish mAh charging speed. Is this normal? Else I'll probably have to enable force fast charge (if this feature exists, I'm not seeing it in FKU).
[ONE Original Android Development] tehpud:
There was an earlier post on how. I tried but didn't see the option either. Cuious to know myself.
[ONE Original Android Development] Tzfardaya:
What charger are you using? What's the output on it?
[ONE Original Android Development] jarylw:
Samsung, nvm I posted too quick. Ran some tests and apparently it's the OPO not liking the lengthy samsung cable.
[ONE Original Android Development] zephiK:
Use the stock charger and USB. They matter, see https://forums.oneplus.net/threads/oneplus-one-charging-cable-alternative.68517/

Wish the usb cable was longer but yeah you definitely need to use the stock charger and USB otherwise expect slow charging.
[ONE Original Android Development] _Beni_:
no, using a 1A charger should be enough, i never have seen it charging more than 1A.

U just need the original OPO cabel
[ONE Original Android Development] zephiK:
That's not the point, my point was that if anyone is encountering any slow charging then that's the reason why. Because they're using a charger that is low amp.

At the end of the day, a higher amp charger will charge faster and there isn't any reason not to use the stock opo wall charger, I understand using the non stock USB but the wall charger is a must need.
[ONE Original Android Development] paychex:
I use Blackberry folding blade chargers. 1.8A and a nice long cord. Cheap as hell on eBay as well
[ONE Original Android Development] zephiK:
I have those too from my Nexus 5 days, I gave the second charger to my dad. Not as quite as fast as the regular OPO charger but it still charges very quick. And for sure I love how long these cords are, I can walk as far out as possible in my room and it would still be fine. http://xdaforums.com/google-nexus-5/accessories/hands-best-fastest-cheapest-nexus-5-t2729066 is the thread for those interested $5 for 2.
[ONE Original Android Development] xXghostXx313:
lol I bought them when it was $6 for 3 and I bought it like it five times
[ONE Original Android Development] Jayception:
Would there be any reason for load_threshold under Hotplug Control being the only setting that won't stick after reboot even after setting it to boot? Using FKU by the way.
[ONE Original Android Development] mbudden:
Charging at a max of 1800mA here on my DV8P's wall socket.
[ONE Original Android Development] Android-Andi:
[MENTION=3292224]franciscofranco[/MENTION] Omni seems to use find7 kernel, not sure if interesting. OnePlus One called "find7op" on OmniRom.

https://github.com/omnirom/android_device_oppo_find7op/blob/android-4.4/BoardConfig.mk#L8

https://github.com/omnirom/android_device_oppo_find7op/blob/android-4.4/omni_find7op.mk#L51

Send from OnePlus One using Tapatalk
[ONE Original Android Development] ak:
Have you try this kernel on cm11s 25HR?
[ONE Original Android Development] Android-Andi:
[MENTION=3685904]ak[/MENTION] no, running everything Stock atm, still locked bootloader

Send from OnePlus One using Tapatalk
[ONE Original Android Development] zephiK:
Gummy was doing this for awhile too but it seems like they reverted back to using cm due to errors,

http://xdaforums.com/showpost.php?p=54536420&postcount=51
[ONE Original Android Development] ryaneu:
Any idea how to make this Franco Kernel work in the Mokee rom?
[ONE Original Android Development] zephiK:
Wouldn't you just flash the AOSP version? The OP of Mokee ROM says

Or are you having problems having it boot with franco aosp?
[ONE Original Android Development] ryaneu:
I flashed the AOSP version and it does not work. Get a lot of forces closes.
[ONE Original Android Development] kecinzer:
I know, that it was written here a lot, but I still have question about franco's branches.

I want to compile this kernel with AOKP that uses CM11 kernel - https://github.com/CyanogenMod/android_kernel_oneplus_msm8974 on cm-11.0 branch. So I need to use cm-11.0 branch on franco kernel or aosp one?

I'm very confused :(.
[ONE Original Android Development] Setting.Out:
I think Mokee modifies their CM kernel...
[ONE Original Android Development] Tzfardaya:
It's more of a cm11s (stock rom) kernel, and a "try on everything else" kernel (everyone's calling it aosp)

So, if you're on any rom other than stock... Try the "aosp" one...
[ONE Original Android Development] zephiK:
Also to note, Liquidsmooth (possibly Omni as well) won't boot with Franco anymore.

Its not Franco's fault either, Liquidsmooth derived away from CM and is using a find7 kernel. Just throwing that out there incase anyone comes here with this question, hopefully they see this post.

Kind of unfortunate that these ROMs are deriving away from cm causing more fragmentation with kernel compatibility.
[ONE Original Android Development] kecinzer:
We use CM kernel directy from CM repo, so with AOKP franco's aosp will work I think (didn't try it - my One is on the way).
[ONE Original Android Development] zephiK:
It should work, the non-AOSP kernel here pretty much only boots with CM 11S. Nice to see you get a One as well.
[ONE Original Android Development] Tzfardaya:
Thanks s because it's not aosp/cm... It's cm11s/try with everything else...
[ONE Original Android Development] zephiK:
I know :p I was just sticking to the wording of op.
[ONE Original Android Development] shiakap:
i realized that PA superuser access in 4.5-BETA1 is not working after installing r10..after re-flashing same ROM superuser access is back but i have to stick with the stock oneplus one PA kernel..
[ONE Original Android Development] clock51:
I can use this kernel and MultiROM. and keep as 11s CM rom primary?
[ONE Original Android Development] zephiK:
Franco did not include the init.superuser.rc in the ramdisk so therefore you can't user the built-in superuser. If you want to use Franco on PA to have root access then you need to flash Franco as well as SueprSU and then root will work.

Franco just got back from vacation, probably by the next kernel release, r11... it will have MultiROM support. Currently franco r10 does not have multirom feature just yet. Thats something to really ask http://xdaforums.com/oneplus-one/development/mod-multirom-v26-t2835738 there though.
[ONE Original Android Development] chr0m:
Not sure if this is related to this kernel, but I kept having touch screen issues. Sometimes it would stop responding completely until I powered off and on. Other times it would go crazy opening apps and swiping by itself. I've gone back to stock kernel now and the issue hasn't happened since.
[ONE Original Android Development] Tzfardaya:
Going crazy while plugged into a charger?
[ONE Original Android Development] chr0m:
Nope. The first time it happened I was out at a pub on Saturday night. Then the next day it stopped responding completely. I rebooted it a few times and it still wouldn't work, then finally it started working again, then a few hours later it stopped responding again. So far I've been back on stock kernel for 12 hours and it's been fine.
[ONE Original Android Development] MICa.fighter:
Most probably not kernel related. Unfortunately the One suffers from touchscreen issues, there are a couple of jira threads about touchscreen issues like the bacon-55, it seems the touchscreen firmware is the culprit. CM is working with the firmware provider to fix it. Until a final fix we will get a temporary bandage for the problem. We are supposed to get 2 OTA updates in august, the second one will include the temporary fix.

Tapatalk'd from my 1+1
[ONE Original Android Development] chr0m:
I get this a bit too. I was getting it with the stock kernel as well though.
[ONE Original Android Development] jlevy73:
R10 seems to help my screen unresponsive issues (with PA beta1). Thanks for the nice kernel.
[ONE Original Android Development] zephiK:
Looks like ota is coming our today. https://forums.oneplus.net/threads/what-happened-to-the-update-at-the-end-of-july.70989/page-11
[ONE Original Android Development] jarjar124:
time to start spamming check updates :P
[ONE Original Android Development] zephiK:
I'm just looking to rip the radio from the update :p I don't have any signal problems but would love to see what the new radio can do compared to the current.
[ONE Original Android Development] _Beni_:
I too have it, but not so often after deinstalling Xposed.

It gets too hot so since yesterday i undervolted it by -88mV :D (PVS7)
[ONE Original Android Development] jarjar124:
https://forums.oneplus.net/threads/cm-11s-30o-ota-slowly-rolling-out.83394/

It's happening!
[ONE Original Android Development] Elvecio:
Just refresh that thread :'D

1 question, did this custom kernel resolve the ghost swipes? Or we have to wait the new touch firmware to see improvements?

Inviato dal mio One utilizzando Tapatalk
[ONE Original Android Development] zephiK:
Clear Image looks nice!

Changelog looks interesting.

Increased capacitive button illumination

Edit: We're so spoiled,

Two OTAs this month.
[ONE Original Android Development] paychex:
Anyone know how they work on this device. Do we need to be completely stock?
[ONE Original Android Development] jarjar124:
Very nice indeed. CM is really working hard on fixing these bugs as well as innovating new features!
[ONE Original Android Development] cyablo:
You need at least stock recovery. OTA should auto-flash the included Kernel, so any Custom Kernel will be overwritten i think.
[ONE Original Android Development] acuicultor:
No stock recovery needed to flash the ota.
[ONE Original Android Development] hughfollett:
And you should keep root too
[ONE Original Android Development] cchant:
I'm not sure but with the new update being 4.4.4 we'll need a new update from Franco as well.
[ONE Original Android Development] cyablo:
Thats what they at least stated within CM Jira: https://jira.cyanogenmod.org/browse/BACON-49

"OTAs are targetted at unmodified systems."
[ONE Original Android Development] jlevy73:
Yep, you need stock recovery and unmodified /system otherwise the OTA will fail. You can be rooted though as the OTA doesn't check that.
[ONE Original Android Development] Tzfardaya:
Yay, two reasons the OTA will fail on me... :(
[ONE Original Android Development] dafonehacker:
When you're rooted your /system is modified as it contains the su binaries. I think the requirement is that you didn't remove/edit any files from /system.
[ONE Original Android Development] zephiK:
Surprised that you stayed on 11S for that long :p
[ONE Original Android Development] Tzfardaya:
Why? I don't flash roms... But I do make Edits to the build.prop file... Which cause ota's to fail..
[ONE Original Android Development] skydayzer:
Will be goin back to stock??
[ONE Original Android Development] Tzfardaya:
I never left stock..
[ONE Original Android Development] skydayzer:
Noticed... It's zephiK I was asking
[ONE Original Android Development] zephiK:
Should be pretty easy to revert back to the stock :p ahh.. I thought you did flash ROMs.

No why would I? I'll just wait for my respective custom ROM to be updated. Its not like we're getting the big Android L update. Most of the changes in the next OTA are already present on our custom ROMs.
[ONE Original Android Development] Tzfardaya:
Nah, only non "stock" rom I've flashed (aside from a couple troubleshoot flashes) was the L update for the n5
[ONE Original Android Development] skydayzer:
Yea... No Need to.. Even with the Android L, I dont think you'll be going stock... because by then the Custom Roms will be updated to it already... lol
[ONE Original Android Development] pekeltje:
Got my Oneplus One today, and flashed Franco Kernel from the paid FKU app, R10.

It has stock CM11S, default theme, its rooted (Supersu 2.02 from chainfire).

Everything worked well, but suddenly the WiFi stopped working.

It looks off, but the color is lighter as bluetooth wich is off.

Also i cant enable it.

Anyone else got this?
[ONE Original Android Development] Tzfardaya:
Known Rom issue, reboot or three should fix.
[ONE Original Android Development] zephiK:
https://www.androidfilehost.com/?fid=23610159112653774 tzfar theres ur ota file.
[ONE Original Android Development] Tzfardaya:
Thanks...

Quick find...

<10 downloads..
[ONE Original Android Development] zephiK:
Hope you feel special :p

Edit: seems like the 4.4.4 radio is the same radio as before.
[ONE Original Android Development] Tzfardaya:
Not sure, but it flashed a radio in the update....
[ONE Original Android Development] zephiK:
Yeah it did. Its weird because every CM nightly/milestone, a radio is included in the zip. Its the same one as the 25R. I was hoping that the new OTA would include a new radio.
[ONE Original Android Development] danyvw:
Me too. Maybe will flash radio from CM nightlies on top of this OTA update
[ONE Original Android Development] zephiK:
They're both the same radios even in nightlies.
[ONE Original Android Development] danyvw:
Thanks for the info

Sent from my Oneplus One
[ONE Original Android Development] david23c:
after flashing the OTA I flashed r10 without thinking, and it bricked my phone and I couldn't get into bootloader unless I rebooted into it using TWRP (odd...). Is anybody using r10 with the OTA? I was really dumb for not checking compatibility...
[ONE Original Android Development] danyvw:
I can confirm CM11S r10 does not work with new OTA

Sent from my Oneplus One
[ONE Original Android Development] Tzfardaya:
I'm not surprised r10 doesn't work, given the number of changes underlying os/system in the update...
[ONE Original Android Development] david23c:
yea, coming from a Nexus 5, I never had to worry about this when I updated from 4.4.2 to 4.4.3 to 4.4.4 and I kinda forgot about it.
[ONE Original Android Development] Tzfardaya:
Only because the stock kernel on the n5 was the same between those... ;)

I never expected the current kernel to work after am os update... If you remember the 4.4 kernel didn't work on the 4.4.2 update either... (airc)

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

However, this OTA *should* bring the cm11 and cm11s repos back in line again... For at least another day or so...
[ONE Original Android Development] MICa.fighter:
Those who already recieved the OTA, do you mind giving a shot for the "aosp" version of franco kernel? It worth a try :) If the repos are in line it might work.

Tapatalk'd from my 1+1
[ONE Original Android Development] MICa.fighter:
Edit: i see you edited, i guess you found the answer :)

Tapatalk'd from my 1+1
[ONE Original Android Development] zephiK:
To add on to that point. Use nandroid backup to backup "boot." If the phone doesn't boot using Franco "aosp" then boot back into recovery and restore your "boot" backup that you made from before.
[ONE Original Android Development] Tzfardaya:
There's a link posted earlier to download the OTA directly and apply... I never got the OTA, but downloaded from ap..
[ONE Original Android Development] SleemLDJ:
Yup... I tried to be so fast that I didn't think you'll see it... Lol
[ONE Original Android Development] danyvw:
AOSP r10 kernel does not work on new OTA either.
[ONE Original Android Development] Tzfardaya:
That's a little surprising, since I thought it was synced with the cm11-nightly repo... But not that much...
[ONE Original Android Development] franciscofranco:
The attached Kernel is compatible with the latest OTA. Don't flash it with anything else. The fragmentation is even worse now... oh well. I'm exhausted, I'll push this through the app tomorrow morning.
[ONE Original Android Development] danyvw:
Thank you franco. Muchas gracias

Sent from my Oneplus One
[ONE Original Android Development] SpOuK-3-:
Still in bootloop with the image... Not sure I understand why... Can this be flash thru the fku app? Weird...
[ONE Original Android Development] zephiK:
Its for XNPH30O only. Flash it using Flashify https://play.google.com/store/apps/details?id=com.cgollner.flashify
[ONE Original Android Development] tehpud:
Thank you!

Now for mahdi to follow up with update and I'll be golden.
[ONE Original Android Development] danyvw:
Flashed with flashify. Working ok. Hurrah!!! Thanks franco.

Sent from my Oneplus One
[ONE Original Android Development] naruto.ninjakid:
edit: got it used trikstermod

anyway to modify headphone output?
[ONE Original Android Development] SpOuK-3-:
Well, I used fku and then choose the boot image in his file manager... Did a auto-flash but... Still bootloop... Am I the only one?

I flashed a lot of img like this from franco... It must be me ? I'll wait till tomorrow... Maybe I'm too sleepy to flash a kernel

---------- Post added at 09:57 PM ---------- Previous post was at 09:53 PM ----------

Sorry man... Maybe it's just me ... have a good night... It's not a rush... Well, not for me ;) Thanks for the great kernel, i'm flashing it since ... Since I don't even remember what Nexus I had ...

LOL...

Good night franco!
[ONE Original Android Development] zephiK:
The kernel that works with 30O is not on FKU yet. Franco simply posted it here to have people get a sneak peek.

What you flashed was the kernel for 25R (r10) on 30O which caused your phone not to boot loop.

Boot your phone up. Download the attachment Franco posted, download Flashify. Use Flashify to flash the boot.img that was attached in Franco's post.
[ONE Original Android Development] Tzfardaya:
See what happens when you support non-nexus devices... ;) thanks for the kernels.
[ONE Original Android Development] zephiK:
Shh I want Franco to keep supporting OPO ;)
[ONE Original Android Development] SpOuK-3-:
Nah! I downloaded the image and flash it with the file manager in the fku app... I know the r10 can't be flashed on the new OTA... Let me check this tomorow, i'll try to figure this out...
[ONE Original Android Development] zephiK:
Try using Flashify to flash the image.
[ONE Original Android Development] treChoy:
I test drove the unofficially released 30-O optimized Franco kernel, and it's very unstable, from my usage. Whenever I try to use a gesture whilst the screen is off, there's a 50-50 shot of the phone rebooting. Franco, please don't stop supporting this device. This kernel literally is what sometimes prevents me from throwing this phone out the window in anger.
[ONE Original Android Development] tpboi:
there is a new incremental patch to today's big patch, is it compatible with r11?
[ONE Original Android Development] zephiK:
See http://xdaforums.com/showpost.php?p=54766165&postcount=1364
[ONE Original Android Development] cybertlc:
I thought the same thing.........but when I flashed back to the CM kernel the gyro issues are gone......as soon as I flash back to Franco, they're back. Apparently his R2 is missing the fix.
[ONE Original Android Development] Wombat:
?? Cardboard works fine for me on r2...
[ONE Original Android Development] Ok_Kaleidoscope5109:
The app opens, but when you spin around the gyro won't pick up your rotation and let you select which menu option by turning your head.

I seem to have lost my cardboard mount, but I have the app open on my N5 and OPO, and the N5 picks up rotation, but the OPO does not.... Lemme go dig around the house some more. I hope my rabbit didnt chew up this thing....
[ONE Original Android Development] Wombat:
Works fine here I can move/rotate in Google earth etc gyro works as it should...
[ONE Original Android Development] linkinorton:
Looks cool! I'm on XNPH25R, wanna give it a try. Where can I find the stock XNPH25R kernel in case I want to flash the stock kernel back? Thanks!
[ONE Original Android Development] fiz:ik:
The free version of FKU is not compatible with the One, right? So I have to buy the pro version? :)

[MENTION=3292224]franciscofranco[/MENTION] are you having the yellowish hue? I had it and managed to make it almost invisible by using a little workaround I made and your kernel. Could you give it a look if this issue could be kernel-related?
[ONE Original Android Development] linkinorton:
If you're talking about the yellow hue at bottom of the screen, it's not kernel-related, it's the screen OPO uses, lots of complains in China. OPPO Find 7 uses the same screen so Find 7 has the same yellowish hue problem too.

Although, I'm still curious...What did you do to make it almost invisible? :)
[ONE Original Android Development] fiz:ik:
I know. But I managed to get it away, better: to make in invsisible :) with my workaround here and this kernel. It's almost gone, no yellow visible. It's hard to take pictures of it, my girlfriends iphone 5s wasn't able to catch it properly :(
[ONE Original Android Development] linkinorton:
Thanks! I'll have a look, will try to do the same on my opo, hope it will work on mine too.

I want to try the franco kernel, but I don't know where I can get stock CM11S kernel, just in case I want to flash the stock kernel back later.
[ONE Original Android Development] fiz:ik:
Reflashing the original firmware should bring back the stock kernel and I think your data wont be deleted! :) It would be like an update, so no data loss. But no warranty haha :angel:
[ONE Original Android Development] linkinorton:
Thanks! I'll give it a try, fingers crossed~~
[ONE Original Android Development] fiz:ik:
I don't think you want to downgrade back to the stock one :) Franco did a really god job :good:

Can anybody assure that FKU Pro will work with OP One? :)
[ONE Original Android Development] cybertlc:
Except the gyro bug not being fixed......I had to go back to stock for that reason. Half the time the gyroscope initializes, half the time it doesn't (a CM bug). Apparently Franco hasn't incorporated the fix into his kernel yet......but when he does I'm reflashing!!
[ONE Original Android Development] fiz:ik:
Can you explain what kind of bug the gyro has? I'm not facing any bug - or better: I don't notice any :D
[ONE Original Android Development] cybertlc:
It's a confirmed bug by Cyanogenmod........the gyroscope fails to initalizes randomly, which then disables features like Photosphere, etc. They just released a fix in their last update, but Franco's kernel doesn't have the fix at this point.

---------- Post added at 02:11 PM ---------- Previous post was at 02:10 PM ----------

Download the stock Google camera and you'll notice sometimes Photosphere is available.......sometimes it's not (depending on the gyro initalization bug.)

You probably just haven't noticed yet.