yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] schaggo:
Once I started the RMA process (back in March) there was no word of a new touchpanel driver. As pointed out, touch is perfect when running the new drivers.

When running a kernel with the old drivers, I have a completely dead spot about 1cm from the top right corner. No touch at all is registered there. When dragging stuff there or when scrolling in a browser and touching that spot with the finger, the scrolling stopps or the icon/item gets "dropped" at that position and can barely be removed, as the spot is dead and the touch does not get registered.

Apart from that, the typing experience is awful. I write in Swiss German where no dictionary exists, so I have to manually type each and every letter, no auto-complete etc. The German language has a couple characters which belong together, such as CH, CK, NG, EI, EU etc. and when typing fast, these get consistently replaced with a single letter. CH becomes F or G, EI becomes a T etc. Appart from that I have ghost touches, so when typing a text and waiting for a moment, the device would operate the keyboard by itself and type random letters. Or the device would turn itself on with DT2W enabled because a ghost touch in quick succession would trigger the double tap activation. I had the device make calls on itself while laying on the table etc. I could from time to time not operate nor restart the device as it was, in quick succession, tapping everywhere else so that the touches I actually made with my finger, were not registered at all. I had the device hang up a call I was in, I had the device turn the speakerphone on and off in quick succession until the device crashed mid-call because of a bug this triggered, I also could regularily not unlock my device because the lockscreen would not react to my touches and I could not end a call because the device tapped a recently called contact when I was trying to browse the recently called list, and I could not hang up as the screen was totally irresponsive. I had to force shutdown the device by holding the powerbutton.

This will be my last answer regarding this, as this has barely anything to do with Francos kernel anymore and thus we are Off Topic.
[ONE Original Android Development] jgcaap:
The issue is hardware. I've been there.sent to RMA and they got me back. Took 1 week precisely and was totally worth it.
[ONE Original Android Development] KingBeike:
Did the same. Best decision
[ONE Original Android Development] JoeCastellon:
Can anyone tell me if there is any benefit to flashing the Franco Kernel on CM11S, with NO root ? (I need my phone unrooted to run company software)
[ONE Original Android Development] hughfollett:
Franco is mainly a flash and forget kernel, so you should still see a better battery life

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Original Android Development] anjo88:
I did the same the new phone as touch issues again
[ONE Original Android Development] inzaghi89:
I've understand you properly - you've same touchscreen issue with new OPO? I've contacted with support under RMA and at one moment left this, because I've read that new OPO have same issue with touchscreen. So if new devices have this, how this can be hw issue? I'm still on r43 and no problem with screen. Really. I've also enabled double tap, no drain. only google play service eat energy a lot, so i've turned off some options in privacy guard. Now battery life is ~2 days with normal usage and playgin games.

Also screen light & brightness. I've switched to manual settings instead of automatic bright & light.
[ONE Original Android Development] xflowy:
i read the last pages but can't find definite info on if r43 includes the touchscreen fix!? thx!
[ONE Original Android Development] jiznon:
The entire point of r43 is the touchscreen fix.
[ONE Original Android Development] anjo88:
Now with r43 issue dissappear ao is not a hardware problem is a software
[ONE Original Android Development] jiznon:
Or its a software workaround that is nulling some inputs it deems "incorrect".

After the fix, the swipe-to-delete in SwiftKey barely works. I'm guessing that this is due to the fix nulling the repeated swipes.
[ONE Original Android Development] xflowy:
and where can i find r43? it isn't in downloads.
[ONE Original Android Development] schaggo:
[MENTION=4122762]xflowy[/MENTION] use the search my son. Or use the "previous page" links. You shall find it this way.
[ONE Original Android Development] obtained:
It's something like 15 pages back. http://xdaforums.com/showthread.php?p=60747459
[ONE Original Android Development] paolodeni:
r43 worked for me too

R43 worked for me too! The only trouble is double tap (to wake and to sleep) disabled to prevent battery leak.

Anyway, with this kernel my OPO is usable again!
[ONE Original Android Development] Nichie:
Is it even possible to flash it without root?
[ONE Original Android Development] 1337jay:
You don't need root for flashing, you can access recovery even on a 100% stock phone for flashing updates (CM11S to CM12S for example).
[ONE Original Android Development] lokesh.3440:
But unfortunately he won't be able to flash it without custom recovery as Stock recovery won't allow Kernel/OS level modifications . So he will have to unlock bootloader and flash custom recovery like TWRP first. And yes through stock recovery flashing official signed zips will be possible.
[ONE Original Android Development] JoeCastellon:
Yeah that's what I did, unlocked bootloader because I kept trying several roms to see which was stable enough while being able to run DME for company email (phone must not have root for this app to work).

Ended up going back to CM11S and flashed the Franco kernel, but I was wondering if it made any difference considering my phone is unrooted.

My main goal is battery life. I even downgraded the processor performance to 1190 MHz maximum cpu frequency. So far I have not felt the slightest impact on performance, but I do notice my phone doesn't get as warm as it used to when playing Clash of Clans, which is awesome. I'm also noticing an improvement on battery life.
[ONE Original Android Development] schaggo:
There is a special build of DME to work on rooted devices. Ask your IT department. If they say no, be insistent, there REALLY IS a DME build for rooted devices.

And yes, the Snapdragon 801 is a hell of a beast. Don't really get it why everybody runs for the immensly wasteful (and therefore stupid) newer Snapdragons when the "old" ones are perfectly capable to run the newest full blown Android when capped to half the speed...
[ONE Original Android Development] JoeCastellon:
*sigh* I'm afraid it's company policy, and in a multinational enterprise, insisting will get me nowhere.

I just installed CM12.1 nightly and used "Simply Unroot". My phone appears to be unrooted, but DME still refuses to run :(
[ONE Original Android Development] anjo88:
No news on battery drain fix?
[ONE Original Android Development] schaggo:
Check for yourself every now and then: http://www.cmxlog.com/12.1/bacon/

Except you mean a different source of drainage.
[ONE Original Android Development] anjo88:
I'm referring about the touch fix battery drain
[ONE Original Android Development] Nichie:
Last I read cm hasn't fixed it yet.. Their suggestion was to revert the touch screen fix to fix the battery drain
[ONE Original Android Development] FloorFox:
Is this kernel dead?
[ONE Original Android Development] oscarmalo:
probably... maybe... AK kernel is better ;)

Enviado desde mi A0001 mediante Tapatalk
[ONE Original Android Development] silvan g:
It is not. Franco is busy with his new app.

Please don't say things like this. it's very rude to the dev
[ONE Original Android Development] zattack97:
no Franco Kernel is best kernel
[ONE Original Android Development] FloorFox:
I agree. He's a very skilful developer
[ONE Original Android Development] andefil:
Clarification

Hi guys,

I downloaded the boot.img. I want to install it using fastboot.

i have to put the OPO in fastboot mode, is that right?
[ONE Original Android Development] Vivek_Neel:
Yes. And then type

fastboot flash boot nameofthebootimg.img
[ONE Original Android Development] 604:
What is his new app? :confused:
[ONE Original Android Development] silvan g:
Its a gallery app called focus.

https://play.google.com/store/apps/details?id=com.franco.focus
[ONE Original Android Development] Lovatastic:
Tried to flash this in Fastboot and it just got stuck at the boot screen? :/

Edit: Nevermind I'm on 5.1.1 that's why.
[ONE Original Android Development] inzaghi89:
http://review.cyanogenmod.org/#/c/99607/ hope that we can see an update soon :)
[ONE Original Android Development] anjo88:
I hope so I need my battery life back without "ghosts"
[ONE Original Android Development] Izachii:
[MENTION=3292224]franciscofranco[/MENTION], there is already a new update for of the touch panel. Can update to is? Cause it won't drain that much battery. Thanks!

Here the link : http://review.cyanogenmod.org/#/c/99607/
[ONE Original Android Development] Vivek_Neel:
You need to join the beta community to have access to that app.
[ONE Original Android Development] 604:
Thanks :)
[ONE Original Android Development] inzaghi89:
Okay guys. I've flashed my boot with cos12 stock with applied patch and... my observations are as follow:

1. No touchscreen issue;

2. With doubletap enabled no drain battery;

3. Everything works perfectly, no overheat or something;

4. Only sunlight enhancement doesn't work.

http://xdaforums.com/showpost.php?p=61092260&postcount=65

Hope that soon we'll see an update of franco.kernel.
[ONE Original Android Development] iMario999:
Sounds like a good kernel I should try it, maybe it will fix my Sleep Of Death problem that I had for over 5 month.
[ONE Original Android Development] Nami_Girl:
Problem with app Franco Kernel Updater [SIZE]

Hi , I have the full app FK Updater . I set Power Saving profile but I do not know why sometimes are not observed only the maximum frequencies of the CPU 1 . I also installed Kernel Adiutor but the result does not change . I share screenshots of example :

Inviato da Mountain View
[ONE Original Android Development] 7ewis:
Sorry to bug you, but will the encryption issue be resolved any time soon?

I have to have my phone encrypted for work, and having Franco Kernel installed puts it in a bootloop every time, even the beta version.

Battery on stock really is quite bad too!
[ONE Original Android Development] slamdunksaliby:
Quick update to r44 for the touchscreen fix introduced in the latest nightly June 2nd [MENTION=3292224]franciscofranco[/MENTION]?? :)
[ONE Original Android Development] hasnol143:
Yeah I am excited for this too
[ONE Original Android Development] XBrav:
Quick question Re: r42 and beyond: Is there any way to modify the display's refresh rate? I have a bunch of 2D games that are failing down to 30fps, and no governor mods / GPU rendering forces cause them to consistently run above 30fps.

I have some video using GL Tools which shows the clamp to 30fps on Final Fantasy Record Keeper. Occasionally I'll get a buttery smooth 60fps, but it seems to drop and stay down during certain checks (not sure how to capture more debug information): https://www.youtube.com/watch?v=qd_FRCCTgtg

I have a decent hunch that since the OPO's refresh rate is 63Hz, it does not register as a 60Hz device, so the app fails back to 30fps. I'd be curious to see if there is a way to "trick" the OS into thinking the display refreshes at 60Hz, or even reduce the refresh rate of the display itself (I'm assuming the Adreno 330 can handle multiple rates?). Do we know if the refresh rate is locked into a binary blob?

Thanks in advance!
[ONE Original Android Development] adlx.xda:
Hi Franco,

I've noticed the following changes in CM12 today:

Project kernel/oneplus/msm8974

44ce264 synaptics: Use per-panel firmware loading

66b024f Revert "synaptics: Update firmware to 14001227"

Would you consider building maybe a r44 with them in? (in case they makes any sense to you).

Thanks for your great kernel!
[ONE Original Android Development] ashish2sharma:
Hi

I reverted back to official CM12s (12.0-YNG1TAS17L) build. My device is encrypted and I am suing Franco Kernel Updater app full version.

After updating , the device is in boot loop after showing pattern screen. Found a problem similar as mentioned in post #8889.

Is there any other update ? or should I use R41 only.
[ONE Original Android Development] anjo88:
Will not be Franko kernel update in while
[ONE Original Android Development] zattack97:
Why?
[ONE Original Android Development] dwolder:
I think he was just making a comment to the effect that there hasn't been an update to the posted version in a while.
[ONE Original Android Development] Mr_Cyrus:
Focus.
[ONE Original Android Development] SairesArt:
XPosed Additions Incompatibility and Key signals while Screen off

Hey, im on CM12 (OPO) with fk.

I installed "Xposed Additions" (Xposed Module for key remapping)

and it works awesome and everything is fine and cookies.

However, once fk is flashed certain things/bugs happen:

You cannot assign ScreenWake to the 3 Navigation Buttons (Home Button doesnt wake screen). This has been reported quite often and seems to be a kernel issue. FK does not appear to send Key Signals for the 3 Nav buttons while the screen is off (Battery saving decision?) Question being, can you reactivate this? Is there a hidden kernel command meebee to allow this?

The combo of fk and Xposed Additions breaks Double tap to wake. CM11+XpAdd works CM12+XpAdd works, but using fk on either disables double tap to wake, no matter what. Also reported quite often. Is a fix possible? If not enabling nav buttons to wake would be a good trade off.

Why this is important for me:

I listen to music a lot and use CM's Volume key media control. But it only works while screen off. So you put the OPO in your pocket, in there the power button is pressed, wakes screen and goes to lockscreen. Then I long press in my pocket for next track, Volume jumps to 100% and RIP Headphone user. ALL THE TIME. Also turning screen of or doing pull down to change track is annoying and being able to long press for next track while browsing is a GOD sent. So I use that and its awesome, but It brakes double tap to wake, so I stopped, since I use double tap to wake all the time. (I'd be OK with long press home but too )

Also I completely deactivated the Hardware power button. Sounds dumb? But it's awesome and I couldn't look back. But again, no way to turn screen on, since double tap to wake is broken.

Xposed Additions unrelated:

CM12 brought its own version of low Power mode, which promts you to activate it when below 15% battery (disabling app sync and more) and then there is fk power save mode, which I set to activate [MENTION=5181762]10%[/MENTION] battery. Is it possible to unify these? Make them avalible as one setting instead of two?
[ONE Original Android Development] devilsshadow:
Just to clarify, Franco has dropped support for Bacon?
[ONE Original Android Development] jukiewalsh:
Since when? Just because there's not a new kernel every day it doesn't mean there won't be any more. Things have just slowed down a little because bacon hasn't been his main device and he's been working on his awesome new apps
[ONE Original Android Development] sunscape:
Ok, enough of the fanboi-ism. I purchased fku, an app that provides a custom kernel for opo. I don't care what other work Franco is doing because I didn't buy it. It's not relevant because fku is, at least should be treated by Franco as, a separate responsibility.
[ONE Original Android Development] devilsshadow:
Since his kernel put my phone into a bootloop because I had the audacity to assume that it was still being updated.

And just t clarify, CM12.1 has been available for quite a while. His last kernel update was almost two months ago. I've been following Franco's work for a while so i know that when updates stop, they pretty much stop for good. Like the poster above me said, I'm not a groupie, I simply asked a basic "yes"/"no" question. No need to put on your fanboy pants and go for my throat.
[ONE Original Android Development] jukiewalsh:
His kernels for cm12s only, did you even read the first page? Cm12.x isn't supported. When we see an ota we'll see an update.

---------- Post added at 10:23 AM ---------- Previous post was at 10:22 AM ----------

Responsibility?! He builds the kernel in his free time when he feels like it, you might've purchased his app but its not as though you're paying him wages to build kernels all day. And I only mentioned the other (free btw) apps he's been working on to explain that that's what he's been spending time on so his development has slowed. Also, not a fanboy. I don't even use Franco kernel but don't say something's been abandoned unless you see the OP say something about it first.

---------- Post added at 10:25 AM ---------- Previous post was at 10:23 AM ----------

Sorry I guess he didn't say it in the op but he posted somewhere in here if I'm not mistaken that now only the official cm 12s Roms are supported

---------- Post added at 10:30 AM ---------- Previous post was at 10:25 AM ----------

https://plus.google.com/+FranciscoFranco1990/posts/irFLT6FRdqG
[ONE Original Android Development] YudmudTR:
This is old touch drivers. They drain battery a lot. He didn't relased a kernel with new touchscreen drivers.
[ONE Original Android Development] sunscape:
Please don't post anymore. You are ridiculous. Arguing with you would be a waste of time.
[ONE Original Android Development] devilsshadow:
I'm sorry I missed that somewhere in the 900+ pages of comments.

As for the OP, it's been somewhat neglected. I mean, the R43 build is buried in the comments.

So let's not say it's been abandoned, let's just say development for the OPO has stagnated for the foreseeable future. I don't expect any official updates for CM12S any time soon, what with the OP2 gearing up for it's big marketing push. And as such no FK updates either. Just calling it how I see it. Doesn't change the value or performance and stability of Franco's kernels for the ROMs it still works on.
[ONE Original Android Development] Nichie:
The fku app is not just for OPO. It's for every phone that has a Franco kernel
[ONE Original Android Development] Brembo109:
Had no reboot too. Either on 6,7 or 8

Gesendet von meinem One mit Tapatalk
[ONE Original Android Development] Jeanxito:
Same thing..no reboots on r7 or r8..franciscofranco, thank you for all your hard work and attention to details on this kernel, I am loving it.

Keep the good job and just don't listen users that have a bad behavior and don't appreciate your work at OPO community.
[ONE Original Android Development] zephiK:
Thats the way of life, usually the people who have bad experiences tend to be the more vocal ones. The ones with good experiences usually tend to be quiet because theres not much to really say, the number of people with good experiences tend to be a lot more than the bad experiences but it appears more as bad experience since they're more vocal.
[ONE Original Android Development] Dzhedaj:
It's great some of you are having no issues, it could be that your phone simply does not face the conditionsto cause the reboot.

AsI already said - I am running completely stock, only a few apps installed, no system tweaks or kernel settings touched. With stock kernel I have not had a single reboot. With franco I'd get a few per day while playing Shadow Fighter 2.

So please keep the "user error" comments to yourself.

Anyway, I am grateful the kernel is being developed and I hope it works fine for 99% of the users, keep up the good work, franco :)
[ONE Original Android Development] kecinzer:
[MENTION=3292224]franciscofranco[/MENTION]

I'm trying to build this kernel and ending with this:

drivers/video/msm/mdss/mdss_mdp_overlay.c: In function 'mdss_mdp_overlay_start':
drivers/video/msm/mdss/mdss_mdp_overlay.c:956:4: error: 'kcal_pdata' undeclared (first use in this function)
drivers/video/msm/mdss/mdss_mdp_overlay.c:956:4: note: each undeclared identifier is reported only once for each function it appears in
make[4]: *** [drivers/video/msm/mdss/mdss_mdp_overlay.o] Error 1

Do you have same error, or I just doing something wrong?

BTW. I'm compiling with default toolchain and default configs.

EDIT: Just figured out, you didn't update your defconfig.
[ONE Original Android Development] ~MaX~:
Sorry if i missed the answer if its in the thread but, when will the fku app be compatible with bacon?
[ONE Original Android Development] Klarooo:
You need the paid app...
[ONE Original Android Development] Tzfardaya:
So, rather than complaining about us saying "user error" why not try to determine exactly what about your setup is causing the reboots.... Fresh wipe/factory reinstall of the stock rom, add Franco kernel (no rooting required), add shadow fighter 2, check for reboots.... Slowly re-apply your apps, root and whatever else, and see where the reboots start, then Come back and say with this, this, and this applied, device reboots randomly in this situation...

Don't just whine that the kernel doesn't work for you, test the exact conditions you need t reproduce the reboots, once you marrow it down exactly, we may have a better chance of helping to diagnose...
[ONE Original Android Development] dankatz1:
Each phone is unique and we all know it already. The best example is when undervolting, each phone reacting differently.

I also have some reboots. I'm not going vocal, and I really hate those that think they deserve Something from free development.

I had nothing but good experience with franco's kernel on past devices, and I only hope that it will change for the best with this phone as well.

You CAN say it's kernel issue when you run the exact same conditions and change only one variable.

If I, or Anyone else, have reboots with this variable And no reboots without it... Say what you want but its the kernel issue.

As I said before, we already know that each device is unique.

I don't know if it's related or not but I checked and my binning speed is slow. I decided to Try and keep all the 4 cores up with "low_threshold = 0" and ever since (today) I have no reboots.

Now to slowly underclock it. :)
[ONE Original Android Development] paychex:
[MENTION=3292224]franciscofranco[/MENTION] got a random reboot. Only UV'ing the 300 mhz step to 750. I'll raise it up and see if that is the culprit
[ONE Original Android Development] jessesam:
Can anyone tell me rgb values to make my One plus one screen look like amoled screen??
[ONE Original Android Development] zephiK:
See http://xdaforums.com/oneplus-one/themes-apps/screen-color-setting-t2823879

Theres a AMOLEDish like setting in there.
[ONE Original Android Development] N4Solomon:
Weird issue.... Flashed the r8 kernel and now my WiFi settings crash every time I attempt to open it.
[ONE Original Android Development] Tzfardaya:
Let me guess, using a theme?
[ONE Original Android Development] N.Tesla:
Hi [MENTION=3292224]franciscofranco[/MENTION] ! I could not wait for the upgrade of FKU free, after reading about his work on the Nexus range my conclusion is that buying FKU is a good investment. Thank you so much!

I upgraded to R8, premiering FKU, clean and fast installation, no doubt R8 comes with very significant improvements, my battery life is better, even the CPU temperature dropped about 10ºc less. :victory:

An excellent job.:good:
[ONE Original Android Development] N4Solomon:
Well what the hell.... Switched back to stock theme and WiFi is working again... How did you know it was the theme?
[ONE Original Android Development] xXghostXx313:
Happen to me as well. The theme engines need some bugs fix or the theme?
[ONE Original Android Development] acuicultor:
That is said more than 1000 times in xda threads.
[ONE Original Android Development] N4Solomon:
That's really strange