yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] gsmyth:
Unfortunately, you have to unlock the bootloader to flash a custom recovery which will wipe. Once you unlock it you dont need to worry about it again and you can make a nandroid in case anything ever goes wrong or you fancy flashing a custom ROM. ;) You could try one of the root exploits (see below), so you can at least install titanium backup and backup your apps, theres another one called Framaroot if the one below doesnt work. Copy all of the other stuff of the internal storage to a PC, just copy and restore once you're done. Its that or wait for the fix to come down through an OTA and who knows how long that could take.

Kingroot

http://xdaforums.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
[ONE Android Development] bauner:
If any of the root exploits will work and you have root access it should be possible that you can install the kernel and a custom recovery with an flashing app like Rashr
[ONE Android Development] gsmyth:
I'm not sure this will be possible, I know people were previously able to install a custom recovery via adb or something. But this was patched after an update back in November time last year. The safest surest way is just to bite the bullet and unlock the bootloader, you then have the privilege of flashing your kernel very easily! ;)
[ONE Android Development] Omniscient:
Thanks for the responses guys, I'll see if I can be patient enough to wait for the OTA.
[ONE Android Development] bauner:
If it is possible to gain root access with an exploit it should work.

I have done it this way.

After the first official lollipop update I unlocked my bootloader and installed twrp recovery.

After this I relocked my bootloader and flashed supersu with the recovery.

I also disabled update cm recovery in the dev settings.

The recovery, kernel flasher apps and ota updates are working fine with the relocked bootloader
[ONE Android Development] bumbernut:
Just flashed V3 seems to be working well for the touch issue. My screen went super bright, had to turn off sunlight enhancement . Hopefully you can fix that bug .
[ONE Android Development] geowolf1000:
Deleted
[ONE Android Development] bauner:
For me the brightness is working as it should...

If it is too bright for you you can adjust the brightness level too (also with enabled Adaptive brightness).
[ONE Android Development] bumbernut:
Its not the brightness, its more of change in the color space . basically with sunlight enhancement turned on, the screen behaves like its in bright sun, even indoors, changing the brightness doesn't help. Colors are normal with sunlight enhancement turned off. So I have it off right now.

I'll reflash and see if that helps .
[ONE Android Development] geowolf1000:
You can download stock cos 12update

Unzip and rename this kernel to boot.img and paste to update unzip folder

And zip again

Put it to right folder and run install update from cm recovery

Done
[ONE Android Development] Omniscient:
That fails file signature verification with COS12.0
[ONE Android Development] --__LoRiS__--:
I think it works! Never had this screen on time with lollipop! I had touch issues since lollipop build 17L and previously I was on Franco r43.... I hope for COS12.1 official update very soon with this fix :)
[ONE Android Development] geowolf1000:
Did you download from official?

Link
[ONE Android Development] bumbernut:
Reflash didn't help. To test. Turn on adaptive backlight and sunlight enhancement . The colors get super bright and saturated .
[ONE Android Development] geowolf1000:
Low color temperature from 100% to 80%
[ONE Android Development] blahquader:
Hi,

after 24 Hours of using your V3 Kernel, i can confirm everything is working fine. No touchscreen issues, no battery drain. Dt2w & gestures are enabled.

I can't say anything about this sunlight enhancement, i don't use it, since it doesnt worked for me in the past (CM11).

Thank you very very much for this, makes the opo usable again.

Greetings
[ONE Android Development] ZioArturone:
Same situation on my device.

I had to disable all the features about adaptive backlight and sunlight enhancement.
[ONE Android Development] Omniscient:
Yip, that's the stock rom I used. Replaced the boot.img in that zip with bauner's v3 image. Fails verification.
[ONE Android Development] bauner:
adaptive backlight and adaptive brigthness can also be enabled. It will not change the colors and you can change the brightness level manually too.

With enabled sunlight enhancement the colors are ugly over saturated but better readable in direct sunlight
[ONE Android Development] NOSTALGIA:
your kernel is making me stay with cos12...

so amazing.. never felt this snappy...
[ONE Android Development] geowolf1000:
Can you install original update with out replace boot.img?

The trick is to erase the first line only from updater script

Go to Meta info/com/google folder and open update script and erase first line ONLY

You can use your device with text editor

But only suggest if i can not test it before

but my device is encrypt and cm recovery does not work for me

this update is big for my cache folder and unfortunately you are responsive for anything could happend

I doubt will be any but just in case ....
[ONE Android Development] skyguy126:
Thanks working perfectly using v3!!! (I also clicked that button :D )
[ONE Android Development] syuk84:
Thank dev.. It work nice for me.. Test 2 week already.. V2.. Gonna try v3..
[ONE Android Development] namnoops:
First thing's first: thanks!!!

I'm also seeing this issue:

I had sunlight enhancement on with no issue before installing the kernel (it's supposed to kick in only in super direct sun, it's a good feature for where I come from).

After installing the kernel it seems the sensors constantly "report" a very high light value and indeed my colors are now saturated and look awful as if I were under direct sun light.

I have (and had) adaptive backlight and adaptive brightness on as well.

Is there anything I could do to help debug this?
[ONE Android Development] Jaco2k:
Wish I could just +1 the post - I have the exact same issues. Also, experiencing some overheating, but it might be just some rogue process and not necessarily kernel related.

Still, I will investigate more.
[ONE Android Development] bumbernut:
I tried this kernel http://xdaforums.com/showthread.php?t=3059880

[Kernel] [Ofast Graphite] [06/06] Metallized [UBER 6.0] [CM12-12.1/CM OS12] [3.4.107]

Same issue with the sunlight enhancement . Maybe it's an issue with the new firmware?
[ONE Android Development] bauner:
Not from the touchscreen firmware but I think it is something related to the display drivers
[ONE Android Development] seanwlk:
The touchscreen issues are gone, no more ghost touch , but i noticed some over warming
[ONE Android Development] abhi08638:
All sunlight enhancement code was moved from kernel to rom about 2 months ago. The only way to get it to work is to run an older rom with the SRE still included.
[ONE Android Development] bauner:
Update4:

Kernel V4 with fixed Sunlight Enhancement is now attached in the first post
[ONE Android Development] inzaghi89:
Wow! :) thanks a lot

Wytapane na Oposie za pomocą SwiftKey.
[ONE Android Development] inzaghi89:
I can confirm now that this works like before on stock rom.

Wytapane na Oposie za pomocą SwiftKey.
[ONE Android Development] skyguy126:
Just for everyone else out there... It works!
[ONE Android Development] NOSTALGIA:
can anyone confirm that when updating an app on playstore and u turn the screen off the download is pausing and its unpausing after screen on?

wifi on when sleep is set to on already
[ONE Android Development] bauner:
Have you disabled wakeup and keep awake for the google play services?

If yes this can be the reason
[ONE Android Development] NOSTALGIA:
yes.. noted.. thats what i was also thinking.. thank you so much...

so do u advise having it awake for the meantime while downloading something then just turn it off once done?
[ONE Android Development] bauner:
You can do it as you like. I personally have it always enabled
[ONE Android Development] kyrgeo1978:
Great work mate but there are high temperature issues with V4. Any solutions?

Thank you.
[ONE Android Development] inzaghi89:
I can't confirm that. Using since released and no overheat.

Wytapane na Oposie za pomocą SwiftKey.
[ONE Android Development] geowolf1000:
I have use hydrogen modem and heat gone

Very quick response at least for my country

3G data plan
[ONE Android Development] kyrgeo1978:
Another friend of mine has the same problem. :confused:

I will give a try. Thank you.:)
[ONE Android Development] bL33d:
Any chance of a KitKat kernel or is that not doable.
[ONE Android Development] zacb:
testing this, my touchscreen was pretty severe, whenever it was warmer than +20c outside and i would be outside for a bit it would start touching all over the screen, phone even sent my boss a random letter spam text on a Saturday night. Here's to hoping this works :)
[ONE Android Development] seanwlk:
I have some overheating issues since V3 now i have V4 but overheat didn't solve and even my battery last less, so very quick battery drain, but at least no ghost touches.
[ONE Android Development] roastable:
This is glorious.

Typing is now working the way it should and no longer lagging or detecting gesture typing.

No more lag on the double home button press for recent apps.

Great job!
[ONE Android Development] ZigmunD:
Using v3 for 2 week and can confirm that touchscreen issue finally fixed for me. Had ghost touches every time I took phone from pocket since April (spring, warm days).
[ONE Android Development] peroksid:
Under v3 everything was ok. Upgrading to v4 made it worse (still better than old driver, though) ... Multitouch Visualizer registers horizontal multitouch with v3, but not with v4.
[ONE Android Development] bauner:
There should be no difference from v3 to v4, but if you don't need the sunlight enhancements you can go back to v3 again
[ONE Android Development] ironm:
Hi,

I flashed your kernel a few days ago (v4) on my OPO and there are no touchscreen issues or display illumination, but I do have a battery drain issue. My phone barely lasts from morning to sundown.

I remove the charger at 6:30AM - do some Facebook browsing & gaming (BoomBeach) for max 30min (on WiFi) and then from 7:30AM to 6:00PM i have nonstop LTE data on and just do some Whatsapp conversation, short calls or facebook messages.

With these activities I get home with about 20% battery which then I turn on the WiFI and lasts me until around 10PM...

Isn't this small battery time???

Btw, and don't take it as an offense, I got the same battery on Franco's Kernel r43.

Anyway, now I hear that OPO launched OTA update for touchscreen issues. My questions are:

- now, with my phone rooted and unlocked, can i get and install the OTA?

- if I install the latest OTA will my phone unroot/lock?

- when searching for updates i get the message:

Update Cyanogen recovery

Warning: Update Cyanogen recovery is disabled. This may cause problems...blabla

Please enable UCR in dev option.

Will OTA work if recovery is disabled?

- can I ReLock the bootloader and UnRoot the phone and still be able to flash your Kernel?

Thanks for the time,

M.
[ONE Android Development] Loreane Van Daal:
Yes, you can install it. I did it yesterday. There are two ways, tried both. First is to dirty flash full stock rom, via TWRP, from http://builds.cyngn.com/cyanogen-os...0bd462d41/cm-12.0-YNG1TAS2I3-bacon-signed.zip and than root again. Thats faster way. Second way is to flash stock recovery first, than flash OTA from http://builds.cyngn.com/fota/incremental/bacon/cm-bacon-e816218e8a-to-30bd462d41-signed.zip and reflash TWRP back and root. And that's it.

I flashed this kernel after update, just to see is there any conflicts and for now there is none. So I will continue to use it. Regarding battery life, with far more heavier useage than yours (excluding gaming) i still have at least 45% at evening. Maybe you have some battery draining app. Beter battery stats is ok app to see what is draining juice.

Why would you relock BL and unroot?
[ONE Android Development] ironm:
Can't i just wait for the OTA to appear on my phone?

I don't want to use again TWRP because I don't want my phone erased again. I just want a simple update (be that either from OPO or a custom kernel) that solves my battery issue.

I will try the app to see what's draining the battery....

I want to relock and unroot...just to be on the safe side :) I never used to root until now (and now i did it because of touchscreen issues)...
[ONE Android Development] Loreane Van Daal:
You can wait, but can't apply it with TWRP. Only with stock recovery. That's why i wrote how to apply update. Regarding erasing of phone, TWRP don't do it by itself, someone has to issue a command ;) . And your phone will be erased in relocking bootloader process, AFIK.
[ONE Android Development] ironm:
No, you missunderstood me:

1 - i want to wait for the OTA to show up on my phone and install it from there (not manually through your 2 methods). Will this be possible?

2 - I was refering that TWRP will erase my phone if i try any of your methods of getting the latest OTA update

3 - i would like to relock the BL and reroute so I won't get some virus/malware/...whatever that might screw the phone
[ONE Android Development] Loreane Van Daal:
1. As i said, you can't if you have TWRP

2. It will not

3. No comment ;)
[ONE Android Development] ironm:
:) Ok, so let's get back to the OTA:

Now I have root + twrp + bauner kernel v4.

I want to install the latest OTA WITHOUT loosing my data from the phone (or needeing to reinstall enything). And not to install the whole ROM.

Can you walk me again with the needed steps?

Thanks

P.S.: but first, is it worth installing? Is better than franco r43 or bauner v4?
[ONE Android Development] blahquader:
Just download the full rom (cm-12.0-YNG1TAS2I3-bacon-signed.zip), reboot to twrp, wipe cache/davlik, flash rom, flash supersu, reboot, done.

No Data will be lost. Works fine here.

Well, its your descision. franco has battery drain and sunlight enhancement bug imho, bauner works nice.
[ONE Android Development] ironm:
Thanks for the walkthrough!!!

I have an app called PPPreferences in Battery stats that apears to be draining most of my battery. Any ideea what it is and how to disable it?
[ONE Android Development] Naman Bhalla:
That is a CM Bug .. The app you are seeing is actually Android System and not PPPreferences .. A bug changes the icon ... Sometimes I get dialer icon. Sometimes ANT HAL there ...
[ONE Android Development] inzaghi89:
I'm know that this is thread about modified COS12 kernel version, but... yesterday I've flashed my OPO with new OTA. And what I observe is that power consumtion is lower on stock COS12 than modified. On V4 I've 3-4%/3 hours. Now I've 1-3%/3 hours. This is huge difference. BUT for me touchscreen works better on V4 than on stock in latest OTA.
[ONE Android Development] bauner:
The kernel source and the touchscreen fix is the same as in the new ota. But maybe they have changed something in the ramdisk or in the rom.

I will extract the ramdisk from the new kernel and compare it with the older one soon
[ONE Android Development] ironm:
I just flashed the ROM with the new update included (Friday) and ever since the battery drain is even higher.

Please let us know If you found new things in the latest update.

I'll keep it like this for a few days more and then i'll try a custom kernel...maybe i'll get some decent battery :(
[ONE Android Development] Loreane Van Daal:
With this kernel i have lower battery drain. To put aside that i have greenify and amplify xposed modules cause i used them on stock too. Deep sleep is cca 0.4% per hour, stock was cca 0.6%. Today i ended with 83 min call time, 4G always on, 253 min screen on and 42% of battery left. I don't see any side effects with latest ROM update, so it might be worth trying.
[ONE Android Development] ironm:
Are you talking about Bauner's kernel on the latest ROM or just the stock ROM?
[ONE Android Development] Loreane Van Daal:
About Bauner's kernel on a lastest stock rom :) .
[ONE Android Development] ironm:
Indeed, i just flashed v4 and battery with about 15-20% less drain. But still little battery time...

I'll keep on testing...
[ONE Android Development] bauner:
A kernel for CM11s XNPH05Q is now attached to the first post too
[ONE Android Development] comexx:
I installed the V4 but OTA keeps showing up. What to do for that?
[ONE Android Development] NOSTALGIA:
disable OTA
[ONE Android Development] comexx:
OK, is there any convenient way to keep up with the updates? Say, for this ROM/FIX?
[ONE Android Development] NOSTALGIA:
subscribe to the thread
[ONE Android Development] karthiksitian:
everything works fine,can u add support for KCAL ...color control so than i can reduce the Blue to 210
[ONE Android Development] erdal67:
is it possible to make a stock kernel and hardboot patch without the fix?
[ONE Android Development] bauner:
Why you don't want the touchscreen fix?

There are no problems with it and it is now also included in the current stock kernel
[ONE Android Development] erdal67:
Edit:

Duplicate
[ONE Android Development] erdal67:
I meant the latest official kernel with the official fix already applied, I find it stable enough but I have to change to other kernels for multirom support
[ONE Android Development] bauner:
The latest v4 includes the same fix as the stock kernel of the latest update +hardboot support.

I use it myself on YNG1TAS2I3
[ONE Android Development] mdavario4:
Hi, I am using the latest V4 kernel with COS12. Since some time I have this OTA message popping up and today I thought, ok.. let's try it although it's the same fix I already use. I have TWRP and did wonder why it rebooted to the default twrp screen, looking into the recovery log did show :

Verifying current system...

script aborted: Package expects build fingerprint of oneplus/bacon/A0001:5.0.2/LRX22G/YNG1TAS17L:user/release-keys or oneplus/bacon/A0001:5.0.2/LRX22G/YNG1TAS2I3:user/release-keys; this device has oneplus/bacon/A0001:4.4.2/KVT49L/XNPH25R:user/release-keys.

Package expects build fingerprint of oneplus/bacon/A0001:5.0.2/LRX22G/YNG1TAS17L:user/release-keys or oneplus/bacon/A0001:5.0.2/LRX22G/YNG1TAS2I3:user/release-keys; this device has oneplus/bacon/A0001:4.4.2/KVT49L/XNPH25R:user/release-keys.

???... no idea why it has this old release key?? and what to do?

Any advice available here?

Michael
[ONE Android Development] Loreane Van Daal:
Read this: http://xdaforums.com/showthread.php?t=3137841
[ONE Android Development] snip3:
Wow, this kernel really helped the lag on my phone. Any idea if it will work on 12.1 ROMs?
[ONE Android Development] Jessetatum1337:
Just making sure but this kernel will fix touchscreen issues on cm11s 4.4.4 kitkat?? Thanks for any help!
[ONE Android Development] bauner:
Yes the cm11s kernel should fix the touchscreen problems in the stock cm11s rom
[ONE Android Development] EasyGoingXD:
yes running it with 05Q since 2 weeks :)
[ONE Android Development] GPSMapper:
Hi Friend,

Since COS 12.1 official was just released (YOG4PAS1N0) - wondering if you can release stock 12.1 YOG4PAS1N0 kernel with kexec-hardboot patch only?

Would be greatly appreciated as I need MultiRom support while I'm not really happy using customized kernels (Franko, AK, etc) and prefer keep all stock as mush as possible.

Many thanks in advance!
[ONE Android Development] bauner:
Already done...

http://xdaforums.com/oneplus-one/development/kernel-t3186870
[ONE Android Development] erdal67:
i'm sorry to bug you again, cos12.1 is out and I dont know if the kernel has updated but if it is, is it possible to add hardboot patch to the new kernel?
[ONE Android Development] bauner:
Already done. Please read my last post...
[ONE Android Development] guillermorojaz:
Regards.

Tell me where to download the stock 12.1 YOG4PAS1N0 kernel?

Thanked.
[Motorola Droid RAZR] bab1c:
Hello,

I've get a old razr and want to sell it. But i need to get back to GingerBread before.

I don't know if it's possible.

My Razr is under CM12.1 with the last safestrap and Fasboot v0A.77.

Another question, where can i find the sbf files for GB ? All links are dead.

Thanks for answer.
[Motorola Droid RAZR] welder73:
If your stock rom was GB then you can flash GB sbf file but if you upgraded to ICS or JB you can't go back,it's impossible.

Here is everything you need :)

http://xdaforums.com/showthread.php?t=3023837

Sent from my Razr XT910
[Motorola Droid RAZR] bab1c:
Thanks,

I've already update to stock ICS and stock JB before install CM12.1

So i can't get back to GB....
[Motorola Droid RAZR] welder73:
No,you can't,sorry...

But why it matters?Flash JB with Rsd Lite and the phone will be clean,you can sell it like that...

Sent from my Razr XT910
[Motorola Droid RAZR] bab1c:
The buyer want a Razr with GB, i don't know why but....

Thanks
[MX Player] Rumus.A:
Hi

About the recent A-B repeat feature. I encounter some bug.

To reproduce just follow these 3 simple steps.

- set MX player to play even if mobile screen is off

- activate A-B repeat

- turn the screen off

What will happen?

The player will totally skip the B point and continue playing further.

It will jump back to A point when you turn on the screen again.
[Nexus 4 Q&A, Help & Troubleshooting] Rainshine:
I've had my Nexus 4 for a couple years I believe now, and overall it's been a nice device. I've had occasional issues now and then with software (Camera not available message, random powerdowns) but no hardware issues. A couple weeks ago, part of my display stopped responding. The LCD itself shows everything, there's no bars, no visible cracks in the screen. but the left hand side of the screen, I'd estimate about 1/5 the screen in width, no longer responded to touch. The far far left edge, along the very edge of the display, registered, and on the other side of that 1/5 worked fine. The area that was giving me issues was right about where the 'a' key on the keyboard is in portrait mode -- the only location I could press to get an 'a' registered an 's' as well.

This is all being tested with the developers Show Screen Touches and Show Pointer Information turned on.

Then, the end of this past week, it got worse. The entire left half of the display still shows fine, but almost never responds to touches -- maybe 1 in 100 times it will. Thankfully, I was able to get in one of those times and disable my screen lock. It seems to be able to register as far left as an x value ~418. This means the back button in portrait mode, for example, no longer works. To make me even more confused, it seems to register phantom presses. The device can be lying, powered on on my desk, no touching it, and the display starts showing screen touches -- the most common one I see is right about where the word Google is in portrait on the stock main screen. These will continue indefinitely.

All this to say, I suspect my digitizer has had a mechanical failure. Does that seem a reasonable conclusion to you? I like the four inch form factor of the device, and with most new smartphones getting larger and larger, I'm shying away from changing to another device. I've looked briefly at replacing the digitizer -- it seems you can purchase either the digitizer alone or with the LCD, and that when replacing just the digitizer it's easy to accidentally create problems with the existing LCD. Is that true?

Also, the part about having to use a hair dryer to pull the components apart makes me a little nervous. Screws and cables I can handle, but a hair dryer?
[Nexus 4 Q&A, Help & Troubleshooting] nutt_case:
I would say it's most likely a hardware problem with the digitizer. The lcd/digitizer assembly is glued together so it's very difficult to separate the two without damaging the lcd.

Unless you have the tools to separate them properly, it's alot less headache to get the entire assembly already glued together.