yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] G-Bus:
I lost sound completely out of the phones speaker after flashing r17.
[ONE Original Android Development] Deadpool253:
Everything is running perfect for me other than the audio bug Franco is fixing eventually so no complaints here. I was thinking of trying a new Rom though. Does anyone have a flashable update for the libs so I don't has artifacts when I reflash fk?
[ONE Original Android Development] samflorin:
If you use Synapse+UKM upgrade UKM.

Edit: get the latest one from here: http://xdaforums.com/android/software/zip-synapse-script-universal-kernel-t2736986
[ONE Original Android Development] ronieta:
Just root...unlock bootloader today, so one thing is missing.......

So hoje fiz root, so hoje mexi no oneplus, e sim, falta a parte da vibração, como tem no nexus5.
[ONE Original Android Development] samflorin:
Get CM Nightly (i use 20140911), flash kernel, profit,
[ONE Original Android Development] Krunk83:
Great work as usual Franco

Sent from The One+ One

---------- Post added at 04:42 PM ---------- Previous post was at 04:41 PM ----------

Try rebooting.

Sent from The One+ One
[ONE Original Android Development] franciscofranco:
Every other week :angel:
[ONE Original Android Development] deathdark:
Have some weird pixel glitches on right side of status bar and while typing or mostly by swiping. Updated from r16 to r17. downloaded via paid app and flashed via custom recovery twrp2.7.1. reverted to r16 glitches are gone.

edit:

Rom: PA 4.6 Beta1
[ONE Original Android Development] akarol:
The aosp ROMs need to be updated for glitches to be gone. I definitely notice a huge improvement with typing! Can't wait for Madhi to update. Valeu Franco!
[ONE Original Android Development] jdec529:
Read a few pages back. It been mentioned several times. Ur rom doesn't have updated libs
[ONE Original Android Development] i860:
Just order one OnePlus One Sandstone Black 64 GB
[ONE Original Android Development] mauaus:
Do i need to reflash vomer tweaks after v17?
[ONE Original Android Development] drdrewdown:
no
[ONE Original Android Development] mauaus:
thanks for the info. Loving v16 gonna give 17 a try
[ONE Original Android Development] digweed4me:
Just flashed r17 through Franco kernel updater and screen just went beserk lots of graphical glitches and color screen wouldn't set
[ONE Original Android Development] prioxxx:
Why you didn't read the previous pages?? Come on guys
[ONE Original Android Development] samflorin:
[MENTION=3292224]franciscofranco[/MENTION] : Given lots of people experience graphical glitches do you think it would be a good idea either to update the OP or build another release without the display commit that gives people issues? You'll get close to a milion reports that stuff is not working otherwise.
[ONE Original Android Development] Red5:
Yeah, like people read the OP. Thats the best place to keep a secret on XDA.
[ONE Original Android Development] samflorin:
Worth a shot though :)
[ONE Original Android Development] franciscofranco:
No point because then I would need, yet again, to maintain another branch. Besides CM nightlies dictate the releases, the other custom roms need to follow through and maybe this will force people to use real roms instead of some crazy compilations I see on XDA.
[ONE Original Android Development] LiquidSolstice:
Welp. Just found my new signature.
[ONE Original Android Development] jgcaap:
Just find the updater app... Isn't there any app where I can edit options? Thanjs
[ONE Original Android Development] jrollette:
Work with stock?

Just to be clear, firmware r17 works with stock 33R, as long as I am unlocked BL and rooted?
[ONE Original Android Development] sharp2G:
Yes CM 11S
[ONE Original Android Development] franciscofranco:
My app does...
[ONE Original Android Development] franciscofranco:
Yes. Root is not a requisite though.
[ONE Original Android Development] Tunasty:
[MENTION=3292224]franciscofranco[/MENTION], what rom are you running these days?

-Tunasty
[ONE Original Android Development] franciscofranco:
Stock.
[ONE Original Android Development] Savant:
Always on stock and it keeps you happy and mostly bug free.

Sent from my One-plus-one.
[ONE Original Android Development] akarol:
[MENTION=3292224]franciscofranco[/MENTION]: as usual, I did my research before inquiring about the graphical glitches. However, I understand that some people don't frequent the thread as they rely on your FKU app solely for their upgrading. Wouldn't it be a good idea to maybe, in the future, point out such issues (AOSP ROM compatibility with screen glitches) on the Release Notes of your app as well? Just a thought.

I'm loving the responsiveness of the screen. I just hope Madhi updates tonight as the glitches are quite annoying. =/
[ONE Original Android Development] franciscofranco:
I didn't even know it would happen as I was pretty sure most roms would already be pulling from the latest HEAD or users would just use the latest CM nightly. I can't be watching out for everything all the time :p
[ONE Original Android Development] Vortex1969:
Not your fault. You did a great job getting the update out. The ROMs for the One have to be updated more often than say the nexus line. When CM makes a change like this people just have to wait for the ROM dev's to catch up. Its in there hand now. Sorry to say.
[ONE Original Android Development] zephiK:
As a workaround go into Settings -> Developer Options -> Disable HW Overlays (Enable)

And then the graphical glitches are gone. The colors are a bit brighter than usual but thats probably because of the ROM not being updated on their part yet.
[ONE Original Android Development] Vonnegut:
:laugh::laugh::laugh::laugh::laugh::laugh:

---------- Post added at 03:37 AM ---------- Previous post was at 03:33 AM ----------

Along with the "call synaptics" post, this post made my day.

:good:
[ONE Original Android Development] HiDEFF:
Is Mahdi one of these real roms? Cause I'm experiencing the same display glitch with Mahdi latest.

If Mahdi isn't, which rom do you recommend?
[ONE Original Android Development] zephiK:
When he means "real" roms, I believe he means "Original" ROMs such as CM/PA/etc.

Mahdi isn't really a "real" ROM as it just takes features from every ROM out there and puts the best features. I'm not saying that its bad to do that but thats what franco meant by "real" roms. At least thats the way I see it.
[ONE Original Android Development] akarol:
Gotcha. Makes sense. I'm anxiously waiting for Madhi to update. Can't go back to the ****ty touchscreen after having experienced this. It's finally like my N5 is in terms of responsiveness.
[ONE Original Android Development] noobhero:
any one of u guys on this kernel using battery monitoring apps?

are your battery flow normal?

i am getting negative battery flow during charging... is that normal?
[ONE Original Android Development] teh_g:
You are the best franco. I can finally fast type!
[ONE Original Android Development] Kerjifire:
Amazing. No more SwiftKey ghost swype. You have me stunned. Thanks cm, Franco etc. Amazing work. Speeed all the way woohoo
[ONE Original Android Development] MICa.fighter:
Just to add my two cents: you dont need to flash a recovery. Its enough to boot into one for ex twrp with fastboot boot recovery.img, then you can adb sideload a rom zip. [On 25R you can flash a custom rom this way without even unlocking the bootloader (yeah..) but I wouldn't recommend it though. 30O and up you need an unlocked bootloader to use fastboot boot command.] If you don't like the included recovery then you can flash your choice of recovery any time.
[ONE Original Android Development] zephiK:
By doing fastboot boot recovery.img, you are "flashing" a recovery, its just temporary whereas the fastboot flash would be flashing permanently. Both of them are still flashing.

I'd personally just keep it simple and permanently flash it, you can sideload/flash OTA updates in recovery anyways. Chances are, the OTA link will be starring at you before the OTA link actually is pushed to your phone. Which if you want to flash, you'd need a custom recovery anyways.
[ONE Original Android Development] MICa.fighter:
You are right :) i just prefer fastboot boot and adb sideload for flashing a rom because its more convinient for me than flashing the recovery, rebooting the phone, pushing the rom.zip, then rebooting manually to recovery to flash the rom.zip. I usually do fastboot flash recovery recovery.img as you, but if i want to flash something through recovery too then i just do a fastboot boot recovery.img :)
[ONE Original Android Development] Beaster:
Thank you Franco.

Working great.

Stock CM11s
[ONE Original Android Development] kokocabana:
Great update. r17 has halved the power draw for my phone while sleeping. Ever since updating to 30O and 33R, it's been around 20-30mA. Now it's back to what I had at 25R at <10mA.
[ONE Original Android Development] chr0m:
Any idea what could be causing audio glitching? I would get the occasional glitch in poweramp so switched to gonemad and the problem seemed to go away until now. I installed r17 earlier and heard my first gonemad glitches just now. Probably coincidence, but could this sort of thing be kernel related? With poweramp I would get the glitching on stock kernel and Franco.
[ONE Original Android Development] oleg44:
am i the only one who still have these touchscreen issues?
[ONE Original Android Development] alesfot73:
With PA glitch screen don't work...
[ONE Original Android Development] anjo88:
Do you still have the same issues?
[ONE Original Android Development] oleg44:
yes, ghost swipes are still here, can't type fast. already tried kernel cleaner script, tried to reinstall the kernel and tried other kernels with the new touchscreen firmware - still the same.
[ONE Original Android Development] noobhero:
i still have it too.

but i've learned to live with it already
[ONE Original Android Development] marinespl:
Are you sure you have franco #17 kernel version in "About phone" menu?
[ONE Original Android Development] Chikko:
After kernel update ghost swipe are gone... Now all seems to work perfectly. I have just grounding issue but at 8th touch, not lesser!
[ONE Original Android Development] famonaco:
I put franco 17 on my cyanhacker rom and my opo screen freeze :(solution?
[ONE Original Android Development] nosidefcp:
me too. r17 not working fine in cyanhacker
[ONE Original Android Development] sash89:
It is not the final solution to touchscreen but is a solution from cyanogenmod!so this is not a final fix!correct me if i'm wrong franciscofranco!
[ONE Original Android Development] ravearamashi:
Anybody here using R17 with Temasek? Pretty sure there's no artifacts right?
[ONE Original Android Development] famonaco:
With cyanhacker have screen problems, but the touch is amazing :)

Btw i must return to ak ....pls franco solve it THX :)
[ONE Original Android Development] hughfollett:
Franco doesn't have to solve anything. Your rom needs to be updated
[ONE Original Android Development] wp7chris:
So if this only works for cm11s stock firmware and not the latest cm nightlies as some are saying, does that mean cm11s is not caf like regular cm????? What the hell?
[ONE Original Android Development] f100cleveland:
Has anyone tried compiling a kernel from his source yet? Just wondering if its make defconfig cyanogenmod_bacon_defconfig or what the make file is? I keep getting errors so I'm assuming that isn't right?
[ONE Original Android Development] Deadpool253:
Franco only develops for Nexus and stock CM11S if that's not acceptable, flash something else. He doesn't owe anyone anything and does this for free.
[ONE Original Android Development] kufikugel:
Well the question is more why again fragmentation happens which is not needed.

To answer the question above stock and nightlies are using both "caf" trees. There are basically two commits which breaks the compatibility at the moment due that the nightly builds are ahead. If you are lucky it will go into stock if not then fragmentation goes on
[ONE Original Android Development] Spl4tt:
[MENTION=3292224]franciscofranco[/MENTION] What is your maindevice now? You'll stick to the Nexus5 or the OPO?
[ONE Original Android Development] Naddict:
Thread lightly cleaned of off topic and unnecessary comments. Members are reminded that respect is a rule here. Time for a redo and reset in here.
[ONE Original Android Development] jejemc:
Hi all would it be possible to overclock the kernel? thank you to you ;)
[ONE Original Android Development] sien1996:
Just curious but isn't our device snappy enough? 2.5GHZ! [emoji106] Isn't under clocking more appropriate? Just asking though, I'm sure you have your reasons. :p
[ONE Original Android Development] akarol:
I've been using r4 for a week now and I noticed my OPO won't charge past 93%. Is it the kernel?
[ONE Original Android Development] jejemc:
hi I personally install and I is not what are the problems
[ONE Original Android Development] paychex:
Try a reboot
[ONE Original Android Development] Wombat:
Use battery calibration app to delete the battery stats file and drain to 1-3% then recharge...

Sent from Uranus via OnePlus :)
[ONE Original Android Development] drakester09:
No need to delete/reset battery stats. That won't do anything.
[ONE Original Android Development] zephiK:
Are you using the stock charger that came with the phone?
[ONE Original Android Development] Wombat:
Worked for me....

Sent from Uranus via OnePlus :)
[ONE Original Android Development] tpcrackpipe:
My guess is he isn't. Mine did this with my stock nexus 5 charger
[ONE Original Android Development] zephiK:
Yup.. the Nexus 5 charger is only 1.2A or 1.3A, the charger that came with the OPO is 2.0A. The charger I bought for my N5 was 1.8A and it still charges fine.

I really like the OPO stock charger but the USB cable is short so would definitely have to use another cable for longer length although the OPO USB is really nice designed.

tl;dr.. use the stock charger that came with the phone as older chargers have less A which will have a problem charging this phone causing slower charging speeds.
[ONE Original Android Development] paychex:
But it's an XDA urban legend!

---------- Post added at 03:50 PM ---------- Previous post was at 03:49 PM ----------

Blackberry folding blade chargers! You can get six of them for like 15 bucks on eBay
[ONE Original Android Development] zephiK:
Yup thats exactly what I used! Saw the thread on N5 XDA, they're 1.8A. I love them, so cheap and the wire is so long. I charged my OPO with it and it still seemed quick. I need to run that app to see the charging rate compared to the OPO stock charger and the blackberry folding ones.
[ONE Original Android Development] LiquidSolstice:
No, it didn't "work for you". Deleting battstats doesn't do anything but remove all the information inside the battery history section of Settings.

A Google engineer herself came out and debunked it. https://plus.google.com/u/0/105051985738280261832/posts/FV3LVtdVxPT
[ONE Original Android Development] famonaco:
So is a rom problem
[ONE Original Android Development] anjo88:
omg is it possible that they never will fix the touch?
[ONE Original Android Development] Doo Doo:
Look Here - - > http://xdaforums.com/showpost.php?p=55387435&postcount=3075
[ONE Original Android Development] shure2:
Are you on AOSP or Cm11 / 11S? I've heard reports from many on AOSP that it hasn't made a difference but after nearly a day on CM11 nightlies I havent got a swipe issue yet
[ONE Original Android Development] franciscofranco:
That's all bull****. The touch firmware works the same regardless of the rom, it's a simple binary.
[ONE Original Android Development] Gwanatu:
This is the new firmware from Synaptics, not CM.

My phone doesn't have ghost swipes anymore. It's possible that there are still panel issues but this completely fixed the problem for me. Been rocking it for almost a full day now and my performance hasn't degraded as others have said. I'm hoping it doesn't.
[ONE Original Android Development] anjo88:
Do you have the one? Fix your touch?
[ONE Original Android Development] shure2:
I am merely stating what I have seen on the forum. If it makes no difference then thank you for clarifying. The people having problems still must have a little hardware issue then?
[ONE Original Android Development] franciscofranco:
What? I'm using the same r17 as the one I shipped. My touch response is fine.
[ONE Original Android Development] skaburn:
Opo whit 11s 33r and r17,

Swiftkey ghost swipes still there. :'(
[ONE Original Android Development] Kerjifire:
11S, 33F, r17, no ghost swipes with Swiftkey
[ONE Original Android Development] skaburn:
Sorry for my NOOB question, it's few days that I have opo. Where can I find 33F? It's a previous version?
[ONE Original Android Development] Kerjifire:
Typo, duh. 33R*
[ONE Original Android Development] skaburn:
Also the fast press of f and h letter doesn't make ghost swipes?

I don't know how to solve. I pass to Kii keyboard that is less sensible but I still miss Swiftkey.
[ONE Original Android Development] zephiK:
The user made a typo, 33R is what he meant to say.

I'm using cm nightlies with r17 and typing is night and day. Glad that it's finally resolved and I can type as how I normally do.
[ONE Original Android Development] dev0lver:
If you don't use swipe, disable it, and you can type without any problems

For me that works better then I thought
[ONE Original Android Development] skaburn:
I did it, but I love swipe more than Swiftkey, and I solved whit Kii keyboard that is way less sensible to ghost swipes.
[ONE Original Android Development] Chikko:
Hey [MENTION=3292224]franciscofranco[/MENTION], is it possible add the feature swipe to unlock over softouch keys? I remeber it was a pretty feature over sensasion...but i don't know if it is only a kernel feature
[ONE Original Android Development] tee00max:
Are most of you guys just running the r17 kernel straight out the box or do you always apply vomer tweaks? Im running stock CM11S and I am so glad that I can type fast as my little fingers can go without it lagging on me!
[ONE Original Android Development] anjo88:
I'm On stock and I don't wanna lose everything and stay at same point
[ONE Original Android Development] dmarden:
I just run it straight up. Everyone's habits and phones are different, but I get such ridiculous battery life without any tweaking that I just don't see the point.
[ONE Original Android Development] tee00max:
Thanks for the input, me personally I just like to run stock smooth roms with a great kernel and set it and forget it. Thanks again.
[ONE Original Android Development] franciscofranco:
Nope, I hate those features.
[ONE Original Android Development] Calkulin:
[MENTION=3292224]franciscofranco[/MENTION], I see you finally added the SU daemon to the kernel so we can use the built in root but on r17, the permissions are slightly off, so it's not executing(should be 750). So can you fix it when you get a chance
[ONE Original Android Development] franciscofranco:
I didn't add any daemon anywhere :confused:
[ONE Original Android Development] famonaco:
no chance to use your awesome kernel in cyanhacker rom :(
[ONE Original Android Development] ravearamashi:
I realised that the Intensity, Saturations and so forth are not in FKU since it's in Screen Color setting of the phone. Only thing is, it's broken on Temasek's ROM though, and I'm wondering where it's located as I know it's not in sys/devices/platform/kcal :)
[ONE Original Android Development] oleg44:
I'm using cm11s. first 30 minutes touch is almost ok, i can type fast and etc, and later it becomes even worsted than before i flashed new firmware. Also after 3-4 hours touch becomes totally unresponsive. so i have to reboot phone to make it work.
[ONE Original Android Development] zephiK:
Its not franco's fault, talk to the developers of the ROM to update their ROM to the latest CM sources.

I went back to CM11 for the time being, may stick with it as it has all the features I want. Only thing missing is Navigation Bar Height/Width change but I use the hardware buttons so its not a big deal.

Added a couple init.d scripts and all is good now.
[ONE Original Android Development] Calkulin:
The init.superuser.rc, which is the daemon for the stock root is now in your kernel(It wasn't last time I looked and I even asked you to include it back on July 11 here) but like I said, the permission to execute is not there, so it's not working. Having that just saves having to use a third party app to get root when CM already includes it in CM11S, you just need the daemon in the kernel, su binary and persist.sys.root_access=1 set in the build.prop
[ONE Original Android Development] HiDEFF:
Zep, would you mind pointing me to the CM nightly you're using? I can't seem to find it.

Thank you in advance!
[ONE Original Android Development] coc014:
Hi, i'm still on 25r , i tried to flash the latest r17 but it stucks to oneplus logo, so i flashed the original firmware again. Is there a way to make it work without wiping or updating to 33r ?
[ONE Original Android Development] Red5:
Duct tape.
[ONE Original Android Development] zephiK:
Yeah sure, sorry for late reply. Here it is if you still need it, http://download.cyanogenmod.com/?device=bacon&type=nightly

XNPH25R does not work with new kernels, its been like this for awhile. Update to XNPH33R.

XNPH25R is apart of the past. The battery problems have been resolved for awhile now.
[ONE Original Android Development] malefixz:
same for me

Same for me, I would like to have a BATTERY SAVER GOVERNOR so I could connect it to the icon in the RAPID SETTINGS when I have LOW battery percentage (as in the stock kernel)

p.s. 11S, 33R, r17, no ghost swipes with original keyboard and swipe on
[ONE Original Android Development] zephiK:
Battery life is subjective. Just because your friend got 7 hours of on screen time, doesn't mean you will either. There are many factors that play into this.

- What are you doing? Playing games? Texting? Browsing? Navigation? .. etc. Playing games etc will lower battery life obviously. Same with playing music, etc.

- Cellular Signal.. better signal, better battery life, and vice versa.

- Wakelocks

.... Battery life isn't even a problem on a OPO coming from a N5. The difference is night and day, I'm sure other people from their prior phones can vouch for this even if their phone wasn't the N5.

If you're looking to maximize more of your battery life. Take a look at http://xdaforums.com/android/software-hacking/vomertweaks-perfect-balance-performance-t2873369

Out of the box, OPO has great battery life... if you don't have good battery life its due to userspace wakelocks etc. But even with those wakelocks you still have great battery life.
[ONE Original Android Development] coc014:
thanks for your replies , yes i was on 25r because of the battery drain but if it's working normal on 33r i'll update.
[ONE Original Android Development] zephiK:
Yep its normal, and even if it wasn't... I'm sure the pros outweigh the cons with not having to worry about mistakes while typing ;)
[ONE Original Android Development] Krunk83:
I can't seem to get this running on Slim. I've tried the AOSP version. Dunno what's goin on.
[ONE Original Android Development] coc014:
I was wondering, does the kernel affect twrp too ? when i flashed franco kernel but my phone wasn't restarting properly , i tried to sideload the original 25r many times without success (at the end i finally managed to do it) , my OPO became hot and the touchscreen was not working properly in TWRP. So does the r17 kernel fixes that to ? I really believe it's a hardware issue :confused:
[ONE Original Android Development] SleemLDJ:
For the first time, i can type very very very fast without ghost touches or some random buttons entering themselves twice.....

Basically, I don't want to smash my OnePlus One over the wall anymore. Thanks [MENTION=3292224]franciscofranco[/MENTION] and of course, synaptics....

Nb: If you're running any of the AOSP roms that don't have the latest commits yet, you can still run R17.

After flashing, just go to developer settings and tick "disable HW overlays" ...... You'll have to do this on every reboot till your respective developer updates his/her rom...

?