yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] hughfollett:
In the first page of this thread, click on the link under "For AOSP roms".

It's not that difficult, you'll do it on your own next time. :)

Keep the default kernel settings, che t'è good as they are now [emoji106]
[ONE Original Android Development] shaker2k:
Madi is AOSP based. If you look in the OP you will see Franco has links to the aosp version.
[ONE Original Android Development] FAdrums:
Hey guys,

Well just a quick question: is there a version of the CM version that can be used with the 30O that doesn't have the drain bug?

Thanks

Ps. I might go for PA and AOSP version soon...getting bored of CM! :cool:
[ONE Original Android Development] MICa.fighter:
Yep, try r12.
[ONE Original Android Development] FAdrums:
Thank you dude!
[ONE Original Android Development] Ky0sHiR0:
Sorry, but r12 doesn't protect from drain battery bug. ( 7 - 10 mA vs 18 - 30 mA in idle ). I think that kernel gotfix only for proximity sensor. CM CEO said that was two problems about battery bug. One related to proximity sensor and other to low-bus or something like this.
[ONE Original Android Development] MICa.fighter:
There are more than one bug as you said, franco kernel doesnt have fox for all fo them yet.
[ONE Original Android Development] Laum:
So, possible touchscreen firmware fix is here https://github.com/CyanogenMod/andr...mmit/ba4b329fe0c7a6d6342b0adfb60d47e5c3041a04 ?
[ONE Original Android Development] sash89:
u guys having problems too with touchscreen freezes?what do you do to solve it temporarily?cuz reboot does not work
[ONE Original Android Development] AcmE85:
There is no fix to solve this issue yet. Hopefully those new merged commits (new touchscreen firmware) will fix this.

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

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

The comments sound promising
[ONE Original Android Development] zephiK:
Nothing. It's pretty much, deal with it and be patient. The fix will come soon. No etas
[ONE Original Android Development] dayanandgp:
Battery drain fix ?

Hi guys, One small doubt. Was the battery drain issue CM11s introduced from ROM or from kernel ? As per R12 release comments, battery drain issue is fixed which makes me wonder if waiting for OTA from CM11S makes sense.

the reason i ask is , i am losing 16% battery in 9 hours during night with Flight mode enabled. In the morning when i checked the battery stats , its was 75% due to " Phone Idle " task which brings me back to my original question , what exactly has R12 fixed with respect to battery drain ?

Should i still need the OTA from CM11s to completely fix ? OR Is 16% in 9 hours in flight mode normal ?

Thanks for your help !
[ONE Original Android Development] paychex:
the proximity sensor is not a bug! Stop saying it is. It draws .37ma (while the N5 draws 12ma). And the only way you are getting drain that low is on the charger. Seriously 30ma would give you over 100 hours on battery

---------- Post added at 02:34 PM ---------- Previous post was at 02:31 PM ----------

what does BBS say?
[ONE Original Android Development] LookedPath:
Has anyone experienced SoD with this kernel? I experienced one after 1 hour I Flashed this kernel and for now it's the only one...

I even noticed that the phone gets hot during charge with Wi-Fi on and I wasn't using it, nothing to worry about but it never happened with stock kernel...
[ONE Original Android Development] dayanandgp:
sorry, what is bbs? Do you mean battery stats? It says 85% phone idle and rest screen... When I checked wake locks, Google search had highest with around 100 instances if I recall correctly
[ONE Original Android Development] paychex:
yes better battery stats. clear the data in google search and see if that helps. if not check your alarms in bbs and see whats there
[ONE Original Android Development] shaker2k:
Do you have Google Now(search) always listening from any screen, and lock screen activated? That would do it.
[ONE Original Android Development] Ky0sHiR0:
Sorry but i didnt agree. On 25R we Got 7- 10 mA per hour in ile with Double tap 2 wake
[ONE Original Android Development] MICa.fighter:
I also get 5-10 mA drain in idle on stock 25R. With Wifi / 3G + Sync enabled, it is pretty much the same. During night I loose 1% if wifi/data is off, (no airplane/flight mode), and I loose 5% if wifi or data + sync enabled. The point is, stock 25R idle is pretty good.
[ONE Original Android Development] Ky0sHiR0:
So we are all waiting for new update. CEO said that we will got better battery performance :)
[ONE Original Android Development] paychex:
you really think that's your idle draw? you think idle your phone will stay on for 310 hours?
[ONE Original Android Development] MICa.fighter:
5 - 10 mA is a raw estimate, mine is based on samples taken on a few minitues frequency, I use 5 minitues polling. A nonstop polling of samples with an app would not make it more accurate, because if you use an app for measurement, higher poll rate means the app itself uses more battery, increasing your drain. To answer your question, I am not sure. What I am sure of is that my One is pretty good on idle. During idle my battery history is a flat line, regardless of wifi and data connection. I usually loose 1% over night, with network on and data off. BTW I use Battery Monitor Widget Free for measurement, and as far as I know chamonix, the developer of BBS uses Battery Monitor Widget for measurement too. If he thinks its good for measurement then I think it is.

But we kinda getting OT. I don't wanna make franco facepalm.
[ONE Original Android Development] hughfollett:
He already got a red face thanks to facepalms, in this thread and a lot others [emoji12]
[ONE Original Android Development] MICa.fighter:
I was afraid so..
[ONE Original Android Development] SleemLDJ:
Excuse me if this has been addressed before but the AOSP version of Franco kernel can be used on CM11 Nightlies yes?
[ONE Original Android Development] zephiK:
CM11S: CM11S only

AOSP: everything else other than CM 11S.

Yes
[ONE Original Android Development] SleemLDJ:
Thanks. Can i install it through the Franco paid app like I usually do on Cm11s..... Or it has to be done via fastboot?
[ONE Original Android Development] zephiK:
If you're not using CM 11S, you will have to download it manually. Just flash it through recovery, get the flashable zip
[ONE Original Android Development] SleemLDJ:
Cheers. I will flash with recovery and then control it with the Franco app.

?
[ONE Original Android Development] franciscofranco:
Just pushed r13 which has a newer Touch Panel firmware from CM. Touch sensitivity seems much improved, which is a VERY welcomed plus. Also added support for PS3 controllers via OTG. I'll add MultiRom support on r14. Enjoy!
[ONE Original Android Development] drdrewdown:
you are always just full of awesome. thanks!
[ONE Original Android Development] nneves:
Thanks Francisco

Working like a charm.
[ONE Original Android Development] franciscofranco:
Don't thank me, Synaptics worked on this new firmware and CM pushed it (after passing through their quality control). :)
[ONE Original Android Development] FAdrums:
Tomorrow I shall unlock my BL and come home to FK...yes...I took that long... *ashamedly goes to sleep*

PS. Awesome work as usual Francisco! BTW when can we beta test the new sweet and tasty FKU?

Enviado do meu A0001 através de Tapatalk
[ONE Original Android Development] black nebur:
It's at these moments that I'm really proud in being a Portuguese!

Well done! Always in and at the right time! :good: :D

Congrats by your extraordinary work with OnePlus One and others.

Oh just a little question, after using the R12 I noticed that wireless, even after being disconnected continued draining battery!!!

Is that normal!? Did it happened with anyone???

The next images will "explain" the situation...

Thanks in advance.
[ONE Original Android Development] franciscofranco:
Hmm... if all goes according to plan, maybe 1 week and I'll start the betas. It's still too soon though, I'm wasting a lot of time in the details.
[ONE Original Android Development] franciscofranco:
Hi :) you probably have the Always Scanning something option enabled on Wi-Fi -> Advanced, otherwise it wouldn't be with that blue line.
[ONE Original Android Development] zephiK:
Settings -> WiFi -> Advanced -> is scanning always available enabled? .. if so uncheck it

ps. the FKU screenshots look amazing. cant wait for the new revamped ui
[ONE Original Android Development] srps:
You have Location Settings on Battery Saver mode, which means it's probably using Wi-Fi data for location estimates, hence the battery drain.

Try looking in Advanced Wi-Fi settings for the "Scanning always available" option. If it is turned on, then there you have your culprits.
[ONE Original Android Development] therebel88:
Bloody Nora this is SOOOOO much more responsive now. Thank heavens for this fix. And thanks Francisco for getting it merged into your kernel so quickly!!
[ONE Original Android Development] Sheeezy:
Excuse me for asking this:

I tried out ColorOS and after restoring my nand backup my boot animation changed from the white 1+ and "powered by android" to

The chinese red 1+ logo an no powered by android.

Is there some kind of officail installer or complete factory image .zip which includes the boot animation ?

Sorry again for the unrelated question but here are the people who are the most active.
[ONE Original Android Development] black nebur:
Thanks by your fast answer, but unfortunately it isn't that issue... Tried that right away... And the option marked was "only when switched on" and it was switched off!!! Anyway I've tried to deactivate it selecting "never on, it consumes mire data" (or something like that ;p) and in battery status the Wi-Fi was still on???

Strange isn't it!

Once again thanks for your help.
[ONE Original Android Development] FAdrums:
Awesome! Take your time...I guess I'm just too excited for that beauty of an app! ?

Enviado do meu A0001 através de Tapatalk
[ONE Original Android Development] zephiK:
Download the official CM11S fastboot images. Extract the zip file and use fastboot then flash

fastboot flash logo logo.bin (from the extracted fastboot image zip)

When you flashed ColorOS, it replaced the logo to the Chinese version. In the Chinese variant of the OPO, they don't ship with Google Apps (I'm pretty sure they don't) so they are not required to follow Google's guideline for "Powered by Android." When you flash logo.bin it should show the regular 1+ and powered by android that you'd normally see.
[ONE Original Android Development] black nebur:
Hi, did you tried already to change the boot animation in the theme definitions to the holo??? There may reside the answer... ;)

Good luck. :fingers-crossed:
[ONE Original Android Development] sharp2G:
Is there a download link to the stock kernel on 4.4.4 August 11 build date?
[ONE Original Android Development] zephiK:
Hes not talking about the bootanimation, he's talking about the prequel to the boot animation. But anywho, I already answered his question.
[ONE Original Android Development] Sheeezy:
[MENTION=1978554]zephiK[/MENTION] [MENTION=444027]black nebur[/MENTION] thanks for the fast responses and the help !

And again sorry for interrupting the discusion on a completely different topic.
[ONE Original Android Development] zephiK:
Not a problem, I think of the Franco thread to be more than a kernel thread.

Its more of a community thread that helps/discusses things outside of Franco Kernel as well. Thats just my way of seeing it, also nice to see familiar faces from 1 Franco thread in one particular device to the next. :D

Plus at the same time, it makes people like Franco Kernel because of the strong community within that kernel.
[ONE Original Android Development] HiddenSanctum:
Any news from the CM team with regards to the headphone with mic issue where sound only come out of speaker? Does r13 anything besides the new touchscreen firmware?
[ONE Original Android Development] zephiK:
According to the changelog, r13 is only touch screen. I've tried with r13 and I have the same problem. For the time being, I'm doing the workaround that another user discovered. The headset controls and microphone work perfectly fine.

The workaround is.

- have auto play music on when the media player detects headphones being inserted

- plug the headset in half way, you will hear a static sound then music will play.

- wait 2-3 seconds and then plug it in fully.

... you'll have to do this every time when you disconnect/connect the jack

This isn't exclusive to music either, exclusive throughout the OS.
[ONE Original Android Development] sharp2G:
Is there a stock kernel download link for the new 4.4.4 update?
[ONE Original Android Development] zephiK:
http://www.androidfilehost.com/?fid=23622183712458985 just uploaded it for you. XNPH30O stock kernel.
[ONE Original Android Development] sharp2G:
You are the best!

---------- Post added at 06:36 PM ---------- Previous post was at 06:30 PM ----------

Can this be packaged into a .zip and flashed via TWRP?
[ONE Original Android Development] zephiK:
It could be, yeah I can't do it right this second. Use flashify from the play store to flash it unless somebody else puts it into a zip file.
[ONE Original Android Development] elementalfusion:
Is there fast charge on this kernel? My phone doesn't seem to charge more than 1A even with the stock AC adapter and cable. On stock ROM 25R and Franco r10 here. Flagged back stock kernel still same, average 800+mah charging. My G2 could do 1600mah even from my macbook
[ONE Original Android Development] paychex:
Sorry I can do simple math. But if you want to believe you have almost two weeks of standby, go ahead
[ONE Original Android Development] sharp2G:
I used an online tool to convert the file you linked me to into a .zip. That should do the trick correct?

Thanks for all your help!
[ONE Original Android Development] Homeless2:
Is it just me, or do I not notice any touch difference in r13?
[ONE Original Android Development] chr0m:
I'm hoping it fixes my issue of the touchscreen freezing and not responding until I power off for a few seconds and back on.

Ironically the touchscreen stopped responding while I was halfway through the swipe to confirm flash in TWRP.

It still seems to detect fast typing as swipes in SwiftKey. It does seem a bit more responsive though, it might be placebo, time will tell :)
[ONE Original Android Development] bradm23:
Big difference for me especially in the typing and accuracy of touches. I'm very happy
[ONE Original Android Development] SleemLDJ:
Help guys. I'm having issues with root whenever I flash AOSP version of Franco kernel to cm11 nightly....

Tested by reinstalling the rom without the kernel and it was fine until I flash kernel again.

What can I do please?
[ONE Original Android Development] drdrewdown:
you need to install the latest supersu, franco kernel breaks root on some roms.

http://goo.gl/dRuuFs
[ONE Original Android Development] HiDEFF:
Noob question: do we flash this in recovery?
[ONE Original Android Development] drdrewdown:
yes, it's a flashable zip from chainfire's download site.
[ONE Original Android Development] FuzeLearner:
I would like someone to confirm an issue I'm having. Running 30O stock rom, r13. I use the "Headphones volume boost" and "Mic gain" and they work but if I put them to "set on boot" and reboot my phone, the audio no longer works on my phone speakers or headphones. If I uncheck them and reboot, my sound comes back. If I turn the "set on boot" back on and set them to a non zero number, the sound goes away again (I have been using the values 15 and 5 respectively). If you just set one on boot I do not have the problem, it's when both are set and then reboot. All other settings in the app are set to r13 default. If you have any questions let me know! Thanks

Edit: P.S. Thanks for an awesome kernel and extremely quick updates!
[ONE Original Android Development] epicnoob66:
Touch issues seems worse with r13/cm11s.
[ONE Original Android Development] Red5:
*sighs*

No examples? No illustrations? No logcats to back up your claims?

Don't be a complainer, be a helper.
[ONE Original Android Development] epicnoob66:
Sorry, I wasn't complaining. No PC for the cat, but examples I can do.

Scrolling my g+ feed, I would estimate half of the swipes registered as taps.
[ONE Original Android Development] HiddenSanctum:
Yeah I saw, still no where near ideal though. I'll wait for CM to fix it.
[ONE Original Android Development] chr0m:
Yeah mine seemed good initially then it went terrible. It hasn't stopped responding completely, but a lot of missed taps. Typing a massive chore.

Went good again after a few minutes. Not sure this is a software issue though, because when my touchscreen stops responding a reboot doesn't always fix it and it stops responding in TWRP which I didn't think would even be touching the kernel
[ONE Original Android Development] wp7chris:
This kernel is beautiful with paranoid android
[ONE Original Android Development] Laum:
Bloody hell. Tried r13 and the touch was better at first, but then ghost swipes started again. My phone must be broken then.
[ONE Original Android Development] Тhe Dark Knight:
It seems like ghost swipes bug is hardware problem
[ONE Original Android Development] nicholaschum:
Just flashed the Synapse UKM last night for ak to check out the settings - but I always jump kernel so last night was a different step taken.

Can anyone confirm that if you install Franco without uninstalling UKM, there would be no adverse effects?
[ONE Original Android Development] toge64:
Question already answered

Sent from my OnePlus One
[ONE Original Android Development] cyablo:
The new Firmware seems to work for me. Multitouch is working much better now and can detect much more Fingers. Tried 5 and 6 which worked quite good compared to the old Firmware. Phone was lying on an isolated Surface (Table) and has a Silicon Case.
[ONE Original Android Development] sash89:
where did u get the new firmware downloaded?
[ONE Original Android Development] DerRomtester:
I think new firmware is in the latest kernel.
[ONE Original Android Development] sash89:
but in the latest nightly's changelog i see no input or tp firmware!
[ONE Original Android Development] barrymossel:
Franco kernel r13 can be used.
[ONE Original Android Development] nicholaschum:
https://github.com/franciscofranco/one_plus_one/commit/195c7a15d4ca15a05efb7666e86ed9f630ee6f0a

Check his github for latest commits: https://github.com/franciscofranco/one_plus_one/commits/cm-11.0
[ONE Original Android Development] barrymossel:
Lol, I thought I was in the PA thread. I was already in the Franco thread. Cuckoo, I said nothing!
[ONE Original Android Development] cyablo:
Using Franco r13 Kernel which has the new Firmware included.
[ONE Original Android Development] sash89:
i am on cm11 nighlty...the r13 touch firmware on aosp is included?
[ONE Original Android Development] cyablo:
Is there anything new regarding Volume-Control in r13? I can only change the Volume if the Staus-Bar is pulled down, on normal Launcher Screen, the Volume-Buttons dont work. Someone else?

Edit: Working again after Reboot.
[ONE Original Android Development] spacemanvt:
I have the same question, I have the latest cm11 nightly (seems to have fixed my crippling touchscreen issue), so the franco kernel includes that too?

Also, I am coming from running CM11 on my Nexus 4 , which wasnt compatible with franco kernel......on the OPO CM11, I can run the franco kernel without all those problems?

thanks guys!
[ONE Original Android Development] hellfire666:
flashed the r13 while back it was good at first....then the touch responsiveness issues started coming back

I disabled the doubletap to wake that seems to fix it

Will test further and update the post
[ONE Original Android Development] barrymossel:
Flashed r13 while not having (much) issues op standard PA kernel with having screen gestures turned off. After flashing swiping seems to be off, still while gestures off.
[ONE Original Android Development] fiz:ik:
I'm facing the same issue.
[ONE Original Android Development] boober78:
Wow, that was just the answer I was looking for. Should I know say thanks? Nah.
[ONE Original Android Development] cybertlc:
Hmmmm.....I'll hold off on flashing R3 until the connectivity bug is fixed. Glad the gyro is fixed, though!
[ONE Original Android Development] fiz:ik:
I cleared cache with fastboot erase cache (it gave me a bootanimation loop lol), afterwards I cleared dalvik cache and normal cache through CWM and it seems to work properly. Did 5 reboots and connectivity stays :good:

LOL NOPE, the sixth reboot made the connectivity fail, crawling back to r2 :D
[ONE Original Android Development] shapethelola:
I had exactly the same Bug with wifi and cell

Gesendet von meinem iPad mit Tapatalk
[ONE Original Android Development] Wombat:
The answer is don't reboot the phone :) I've not seen any probs with Franco kernels r1,2,3, probably coz I don't reboot it every 10 seconds for no reason :)

Sent from Uranus via OnePlus :)
[ONE Original Android Development] DesignGrits:
Once I updated to r3 I have not had the ability to access the WiFi settings. It fc everytime for me. I can't say that it is for sure r3 or not but it started happening around the same time. Since, I have reflashed CMS and have started over from scratch.
[ONE Original Android Development] shapethelola:
So your solution is to not reboot at all, great
[ONE Original Android Development] Expliciate:
Not sure why, but I find that I get better battery performance from r2.

Using r3, 1 hour of idling depletes 10% of my battery.

After flashing back to r2, 1 hour of idling (same scenario) yields only 2% battery consumption.

Not sure if it's just me, can anyone else confirm?
[ONE Original Android Development] franciscofranco:
Look I don't know what you guys are doing with your phones, Wi-Fi stack is 100% stock, no changes what-so-ever. The cell signal comes from the radio/baseband, which has nothing to do with the Kernel. The Kernel only hosts the actual driver that connects the hardware radio to the upper layer, which is RILD. That Kernel driver is also 100% stock.

Besides between r2 and r3 there are only three commits, one that reverts a feature on the display driver which was causing an idle consumption regression, one to fix the gyroscope and another to add undervolt. There are no other changes in the Kernel code what-so-ever. So my guess is that you guys must be running some other crazy **** on your phones. This is made for CM11S ONLY. If it works with other roms good, if it doesn't, then its your own problem.

To the guy above that says r2 has better batteryz than r3 because idle, then you must've had some crazy app keeping your phone awake.
[ONE Original Android Development] DerRomtester:
Franciscofranco you are the kernel god thank you very much :thumbup:

From my i9000
[ONE Original Android Development] blkghost22:
Question.... Will u be making one for the cm11 not the cm11s
[ONE Original Android Development] franciscofranco:
I'm just a normal guy ;)

Why would I? CM11S is stock experience, that's what counts for me.
[ONE Original Android Development] fiz:ik:
I agree with you, kernel has nothing to do eith wifi or radio :) it's really weird. Back on r2 everything works fine. I use Xposed but I disabled it on r3 - still connectivity issues. I don't know what could be the problem. Im on CM11S XNPH25R, the latest update and I only have a few apps installed :/ really interesting what is going on here :cool:
[ONE Original Android Development] Deadpool253:
You just answered your question. Exposed.
[ONE Original Android Development] fiz:ik:
But I D I S A B L E D it completely :) including uninstall the apk
[ONE Original Android Development] Deadpool253:
Is this kernel already undervolted by default and if so by how much?
[ONE Original Android Development] shapethelola:
I had the same problem and I had a almost clean install running. Just too Bad I just bought the updater but I will just wait for the next update