yashsingh1/xdaforums huggingface dataset:
[ONE General] mauecky:
ZNH2KAS1KN + 5.1 boeffla-kernel + modded HAL + K2 flashable camera + 2.67 SuperSU works PERFECT !!!

SORRY EDIT

There's NO deep sleep at all ;(
[ONE General] asdf20:
CM 13.1 dirty flash on CM 13.0

I have MultiROM installed on my device. I am running CM13.0-ZNH0EAS2JK as main rom and CM 13 custom rom as seconday rom.

Can I dirty flash lastest CM13.1 on the main rom? Will it work?
[ONE General] asdf20:
Any suggestions??
[ONE General] Spannaa:
No, not from me - I don't have a OPO and I never used multi-rom when I did have one.

Why don't you ask in the multi-rom thread?
[ONE General] asdf20:
Already posted the same question in multirom-thread also but no reply.

Assume If don't have multirom, can I dirty flash CM 13.1 on CM 13?
[ONE General] Spannaa:
Yep, that should be fine.
[ONE General] NEMESIS_9000:
COS 13.1 extremely buggy

After updating to 13.1 I've got multiple bugs right away:

1. Audio sometimes won't play from audio jack, AudioFX won't detect headphones but the speakers go silent! (There is no dust or dirt involved)

2. On calls (outgoing or incoming) my earpiece sometimes completely silent (volume at max), I only can use the loudspeaker.

3. Screen rotation sometimes gets stuck in portrait mode (already 2 times), only a full reboot helps.

4. Boot time on cos 13.1 is almost 5 minutes or more (did not measure it exactly), with cos 13 it got just a little bit longer than cos 12 (between 1-2 minutes).

This is by far the worst / buggiest update I ever experienced!

I had never issues after updates before besides the battery drain of lollipop. Marshmallow sadly did not increase the screen on time from 3 hours (i miss 25R's sot with 5.5h to 7h even with gaming in between), strangely enough none of the major android developers prioritizes battery life.
[ONE General] Spannaa:
These bugs aren't normal - it sounds like your installation has serious issues.

Did you wipe data/factory reset when you updated?
[ONE General] atulclassic:
not a single issue from above..had a clean install using fastboot zip after a proper backup.
[ONE General] kas_27_es:
By the way, malfunction in audio fx IS a reported issue.

There's a workaround to make it works: source close audio fx, and restart it. If you experience problems, try to delete audio fx data after fc.

Enviado desde mi A0001 mediante Tapatalk
[ONE General] NEMESIS_9000:
I always wipe data and cache after flashing, factory reset is too cumbersome for me to set everything up again and moving 40Gb of my user data back and forth.

I installed this update from the signed zip as all previous updates and I only have issues with this update.
[ONE General] Spannaa:
Not sure what's wrong with your setup then if you wiped data when you flashed the full rom zip but your issues aren't normal.

Just for info: A factory reset via TWRP is the same as wiping data & caches - it doesn't touch your internal storage.
[ONE General] asdf20:
Thank you...I installed it went fine and i did not loose any data

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

I dirty flashed COS 13.1 on COS 13 and I don't have any of the issues you mentioned... Infact Battery Life seems to have increased a little bit

I guess something wrong with your setup........try clean install and check if it resolves
[ONE General] inzaghi89:
I've the same problems as mentioned before. They don't exist on previous version.
[ONE General] counterfeit187:
I've also experienced the problem with not playing audio through the jack. Stared because of audio from 2 sources ( podcasts and navigation) playing at the same time. Reboot fixed it and haven't experienced it again since.
[ONE General] NEMESIS_9000:
This did not happen right away in my case, only once after 1 or 2 reboots, that's why I thought it was a bug.
[ONE General] NEMESIS_9000:
I found another issue with COS 13.1: I had always set my theme for the status bar and controls to "system" (android native). Today I wanted to try the "default" (Cyanogen) theme. Upon rebooting all autostart apps and many system apps started crashing one after another. After reverting to "system" and rebooting all is fine again.

Did anyone experience this? People with constantly crashing apps could try to change the theme settings, maybe it'll help.
[ONE General] Matteo_666:
100% true. In installed dark Material theme (My fav) and it ended up in a mess. I never expected a theme/design to start thouse troubles. Running 'Material glass' now and everythings smooth and stable.

Gesendet von meinem A0001 mit Tapatalk
[ONE General] asdf20:
I changed the theme and controls couple of times but did not face any issue. I changed between System and Cyanogen themes.
[ONE General] spicediablo:
Sorry if this has been asked, I can flashed the signed zip in rooted phone?

Sent from Oneplus²
[ONE General] vickeye:
yep
[ONE General] NEMESIS_9000:
If I keep rebooting the device every day (at most every 2 days) everything stays fine. If cyanogen won't come up with a bug fix (many users are also complaining) soon I'll consider the clean install or maybe a roll back to COS 13 (sadly, for the first time ever, I forgot to make a full backup before upgrading).

Btw. what exactly is a clean install? I usually get the full signed zip and flash via TWRP, then I wipe dalvik and cache.
[ONE General] asdf20:
Factory Reset via TWRP and install the zip as usual. Factory reset will erase the installed apps but not files on internal storage.
[ONE General] Renosh:
Usually it's wiping everything except internal storage for a clean wipe; wipe system, data, dalvik & cache. Then install ROM + gapps.

Alternatively wiping system, dalvik and cache between ROM updates is a semi clean flash. Removes scripts and other mods that persist from a dirty wipe (wiping dalvik and cache only) like gapps scripts and SuperSU scripts etc
[ONE General] Spannaa:
No Gapps are needed with official Cyanogen roms - they're included ;)
[ONE General] Renosh:
Everyone knows that so didn't feel the need to explicitly state it :good:
[ONE General] Spannaa:
So why did your post mention gapps twice if everyone knows that they're not needed?

It could be misleading for people that don't know ;)
[ONE General] ritwik-garg:
Query regarding ROM installation

Firstly, thank you for creating this compilation.

Currently, I'm on Unofficial Euphoria ROM(5.1.1) with TWRP recovery. I'd like to know whether I need to return my phone to stock condition in order to flash the "Signed Flashable Zip" for CM 13.1 ZNH2KAS1KN or can I directly flash the ROM after wiping my system?
[ONE General] Spannaa:
If you're using the latest TWRP, you can just flash the zip after wiping data & caches.

A data wipe may not be necessary but, to be on the safe side, a clean flash is recommended.
[ONE General] ritwik-garg:
I'll wipe the caches, data and format system. I suppose internal storage need not be wiped. right?
[ONE General] Spannaa:
No, you shouldn't need to wipe internal storage.
[ONE General] Syssx:
Yo guys im on CMOS 13.1 And im having problems with my network connection. It keeps switching to EDGE even when there more than half of the signal available for HSDPA. The problem is that I have to switch to WCDMA only when I'm in town using data so I don't have Edge and I have to switch it to LTE/cmda/gsm when I'm home because there is only Edge and no HSDPA. Tried different modems with no luck.
[ONE General] Mydnytefantasy89:
13.1 should have flashed a new modem over your old one, so if you're not on the newest, you should reflash that to avoid any further problems. Aside from that, how did you flash 13.1? Dirty flash over cos13? Or clean flash/switched from another ROM?
[ONE General] Syssx:
Clean flash from CM13. I also flashed 4.0.1.c7-00011 modem.
[ONE General] Mydnytefantasy89:
Sorry for the delay, haven't checked here in a couple of days, and the app didn't make it seem like my comment even posted. Anyway, I came from CM13 nightlies myself, and the modem was my only problem(original owner hadn't updated phone since August). I have issues with Theme Chooser crashing, but I think others are dealing with this as well. I've tried coming up with as many answers as possible, and the only thing I can think of is that CM/COS uses different signal levels in the indicator(I.e. the number used for "full bars" is set higher than most stock ROMs), meaning you wouldn't be getting less signal, it would just look like it. I feel like this isn't your problem, however. If I were you, when you have time, make a backup, wipe, and start fresh again with the full zip, see if that fixes anything. Make it as clean a flash as you can, minus wiping internal data. Hope this helps.
[ONE General] :
[MENTION=2948558]Spannaa[/MENTION] I see a new incremental update coming out, 13.1-ZNH2KAS254

http://builds.cyngn.com/incremental/bacon/cm-bacon-ced5430fc0-to-9f339bddf2-signed.zip
[ONE General] Spannaa:
I see it too, but it's only 6:30 am here so it can wait a while!
[ONE General] Spannaa:
Added ZNH2KAS1KN -> ZNH2KAS254 Incremental update zip to post #1
[ONE General] inzaghi89:
Any news about changelog?

Wysłane z mojego ONEPLUS A3003 przy użyciu Tapatalka
[ONE General] Nico_FR:
Available on jira:

https://jira.cyanogenmod.org/projects/BACON/versions/13810
[ONE General] fozzie:
Are you sure? I don't see it ;)
[ONE General] Spannaa:
:o It is now... :good:
[ONE General] vlc_marcos:
Where can I see the change log for this update?
[ONE General] Spannaa:
Changelog:

https://jira.cyanogenmod.org/projects/BACON/versions/13810
[ONE General] Matteo_666:
New patch is online

Gesendet von meinem A0001 mit Tapatalk
[ONE General] Spannaa:
Full zips & img are up on the Cyanogen site:

cm-13.1-ZNH2KAS254-bacon-signed-fastboot-d194f46bee.zip

cm-13.1-ZNH2KAS254-bacon-signed-9fbe6186fd.zip

cm-13.1-ZNH2KAS254-bacon-boot-debuggable-b988e25b87.img

I'll get them mirrored ASAP.
[ONE General] Spannaa:
Added mirrors for ZNH2KAS254 signed fastboot zip, signed zip & boot debuggable image to post #1
[ONE General] XorPP:
Every time i install cm-13.1-ZNH2KAS254-bacon-signed-fastboot.zip trough fastboot my phone doesn't start. It stays stucked on the boot menu with the Oneplus One logo. Anyone knows how to solve this? Thanks!
[ONE General] kevinpunk:
Ohkay so this gps bug is annoying... It always searching for gps..

I tried sultan rom as well.. But the problem persist there as well..

Anyone know any fix...

Fly 2080->nokia 5800->galaxy s3->oneplus one
[ONE General] bibia:
guys (especially [MENTION=2948558]Spannaa[/MENTION] ), if I'm installing cm-13.1-ZNH2KAS254-bacon-signed.zip under TWRP (currently I'm on cm-13.1-ZNH2KAS1KN), do I need to wipe it all first?

Can I upgrade it without wiping to save time reinstalling all my apps?

I do understand it's not clean install. I just wanna save my time.

---------- Post added at 10:03 PM ---------- Previous post was at 10:00 PM ----------

did u also fastboot flash userdata ? So all internal also wiped.

I u didn't, better try it that way.

Make sure u have backup all necessary personal data.
[ONE General] hgmichna:
Android is designed to be updated without losing apps and user data. Consequently I always avoid wiping data for the reason you mention.

There are exceptions from this rule, like when changing from one Android branch to an entirely different one (for example, stock to CyanogenMod) or if a defect in a particular version of Android makes the normal update impossible.
[ONE General] XorPP:
Thanks for your answer.

Yes, I did, but the problem remains :( I think that there is a problem with the rom. I can't be the only one with this problem...
[ONE General] bibia:
Just want to make things clear. Was it stuck at Cyanogen boot screen, or the previous one?

If on Cyanogen boot screen, it does took around 2-3 minutes sometimes.

If problem persist, try download the previous version, to see if the problem with ur downloaded file, or ur phone.

I did dirty upgrade last night thru TWRP. So I can't confirm bout ur issue.
[ONE General] XorPP:
Hello, thanks four your answer.

What I mean is that the last update doesn't work on my phone. Wherever I run a clean install through fastboot, or I run an install through twrp, or I run an install through the incremental update on the android, my phone always installs the update, then it reboots by himself, and when shows the Oneplus logo, the phone bricks. It stays on that screen forever... I have even waited 20 minutes on that screen, and nothing happened.

This just happens with the last official cyanogen update ( July).

The previous versions works just fine.

The problem is that if I install the previous version, after I start my Oneplus One, the phone starts downloading automatically the last incremental update, and keeps asking me of I want to install it...
[ONE General] SkandaH:
[MENTION=2948558]Spannaa[/MENTION]

13.1-ZNH2KAS254 => 13.1.1-ZNH2KAS2X1 Incremental: http://builds.cyngn.com/incremental/bacon/cm-bacon-9f339bddf2-to-3c3f0aca9b-signed.zip

Mirror: https://www.androidfilehost.com/?fid=24665539028713577

Credit goes to arjanvlek & posters of this thread. Users of Cyanogen OS Update Tracker should also get the notification soon.
[ONE General] Spannaa:
ZNH2KAS254 -> ZNH2KAS2X1 Incremental update added to post #1 - thanks for the heads-up [MENTION=5301049]Titokhan[/MENTION] :)
[ONE General] rap_turkez:
can't install from adb... a lots of red line errorrs , i was on a custom rom but i have wiped from twrp data etc and via fastboot i have flashed latest fastboot zip.
[ONE General] ch-vox:
beware to flash everything in the ROM, including the recovery (in dev option you've got the option for flashing the updated recovery img), if you do not, you may encounter such issues during the upgrading process.

through TWRP flash stock recovery > reboot to stock recovery > flash full stock ZNH2KAS254 > then flash ZNH2KAS2X1 Incremental update and it should work.
[ONE General] :
That has something to do with adb drivers somehow. In my laptop I could never sideload the update immediately after flashing the full rom through fastboot, but in my office system I can sideload it without any issue. I tried with bunch of different adb/device drivers, finally one of them worked.

The options you're left with, flash full rom through fastboot, start the phone, once everything is set up, copy the update file, go to recovery and apply from storage, OR, keep trying with different drivers to check which one works.
[ONE General] Matteo_666:
Is there a changelog available?

Gesendet von meinem A0001 mit Tapatalk
[ONE General] fozzie:
Here, in due course.

https://jira.cyanogenmod.org/projec...-projects-plugin:release-page&status=released
[ONE General] FInixNOver:
Please correct the below info in the first post.

OTA incremental update zips

INCORRECT

ZNH2KAS254 -> ZNH2KAS2X1: cm-bacon-ced5430fc0-to-9f339bddf2-signed.zip

CORRECT

ZNH2KAS254 -> ZNH2KAS2X1: cm-bacon-9f339bddf2-to-3c3f0aca9b-signed.zip
[ONE General] Spannaa:
Apologies - the actual link was OK but the link text was wrong...
[ONE General] TheGreatSega:
TWRP Flashable

Hi

Are the OTA incremental zips flashable in TWRP 3.0.2.0? If not, how do I update the ROM with TWRP?
[ONE General] atulclassic:
OTA zips can't be flashed thru TWRP..wait for full flashable image..not yet available
[ONE General] TheGreatSega:
hmmm... ok so is there a way method that I can use to update it then? Please help me out
[ONE General] spicediablo:
Only flashable through stock recovery
[ONE General] TheGreatSega:
Tried

Yea... i tried that but every time i try and flash the zip the installation fails in cyanogen recovery. Is there something i'm doing wrong?
[ONE General] spicediablo:
Most probably you have made some changes to system. Flashed the previous build once and try flashing this Ota again.

Sent from oneplus²
[ONE General] TheGreatSega:
Could it be because I've rooted my device?
[ONE General] spicediablo:
Could be. Just follow the instructions I gave and you'll be fine...

Sent from oneplus²
[ONE General] evronetwork:
Yes rooted devices can't be updated through Cyanogen recovery ..that's why I'm waiting for a TWRP flashable :p
[ONE General] Matteo_666:
Full zips and img are out.

Gesendet von meinem A0001 mit Tapatalk
[ONE General] Spannaa:
Yep, I'm uploading the last one now...
[ONE General] Cholerabob:
Is there a change log somewhere ? What does the last incremental changes ? I remove the previous one because it was bugging out, failing calls, tuning off and not turning on for 30 min. and so on.
[ONE General] blackvector:
I have the same issue I had to revert back to ZNH2KAS254, perhaps I needed to try the debug boot image, but the phone was not charging so I had to revert back, let me know if you found a work around
[ONE General] nemesi54:
I'm on cm-12.1.1-YOG7DAS2K1

TWRP 2.8.6.0 - Rooted.

Can i flash cm-13.1.1-ZNH2KAS2X1-bacon-signed.zip directly skipping the other ones?

Do i need to change my TWRP to the latest one?

Main target is not to lose data, apps etc....
[ONE General] Spannaa:
CM 12 to CM 13 is a major version upgrade so wiping data is recommended to avoid issues.

I'd wipe data & caches, update TWRP, reboot TWRP and then flash the latest zip followed by the latest stable SuperSU if you want root.
[ONE General] hgmichna:
Android and all apps are designed to always update without losing user data. I don't know where the idea comes from that you have to do a factory reset.

But then every Android discussion forum has at least one user who recommends a factory reset as the solution to every problem.
[ONE General] Spannaa:
I didn't say that a factory reset is the solution to every problem.

I also realise that CM is meant to be upgradeable without wiping data but, in the real world, there are lots of users that upgrade and get bootloops that are solved by wiping data.
[ONE General] devilsshadow:
Can I flash the incremental update if I'm rooted and using custom recovery? Also have some apps frozen/uninstalled(only those that could be un installed, no force uninstalls)
[ONE General] Nichie:
You will need to use the signed version
[ONE General] hgmichna:
No. as soon as you change the system partition (for example, by rooting), you cannot use incremental updates.

Just wait for the full update ZIP on https://cyngn.com/support and flash that. Nothing else is needed, no Gapps.
[ONE General] Nichie:
It is out already

http://builds.cyngn.com/factory/bacon/cm-13.1.1-ZNH2KAS2X1-bacon-signed-704f3ea59b.zip
[ONE General] Spannaa:
It's been out for six days, as has the mirror of it in post #1 of this thread!
[ONE General] nemesi54:
[MENTION=561758]Spanaa[/MENTION] [MENTION=2893530]hgmichna[/MENTION]

Thank you both for suggestions.

I did flashed without wipes (only cache, dalvik) and up until now everything is OK. No problems at all.

Cheers to you both
[ONE General] Nichie:
I know. Just telling the guy above
[ONE General] Cholerabob:
Is there a change log we can see somewhere ? I had a couple of bugs whit the last update and didn't take it. i\d like to see what was done before moving to this one.
[ONE General] NEMESIS_9000:
Lucky you, I have to reboot my phone almost every day because something stops working:

1. Screen rotation gets stuck until a reboot fixes it. Sensor app shows all sensors still working perfectly fine after the rotation stops (autorotation toggle does nothing after the rotation stops working).

2. Headphones are not always recognised (especially not if the phone was on for a day or longer), the"small speaker" profile is applied and as a result the music sounds horrible. If I play around with the equaliser with bluetooth headphones, the changes get stuck, won't revert and get amplified when trying again (e.g. adding bass +3 and reverting gets stuck, even if the bar is on +0. Repeating the +3 prices amplified that to something higher. Since I was testing presets, they all got sick and mixed and amplified. It was horrible). Even disabling the equaliser or force closing it won't help, only a reboot fixes it.

3. Recently all my custom alarm sounds got cleared, instead of the name there was a long number in alarm settings.

All of these I experienced since COS 13. No clearing cache and data or formatting system and reflashing helped.

Does not work since forever:

4. Proximity sensor: it does not prevent wakeup. Sometimes it works when I cover it completely with my hand, but if I lift my hand even a tiny bit (a few millimetres) it won't work.

Because of this every time I receive a call in my pocket, the screen comes on, registers touches, ends / takes calls and keeps the phone busy by registering touches.

The screen should only come on when the phone is out of the pocket!
[ONE General] HannibalLecter:
I am rooted and currently on official CM13 nightly. Will flashing the latest build (ZNH2KAS2X1) through FASTBOOT also lock my bootloader?

TO root again and flash CM13 nightly, will I need to unlock my bootloader again>?

TIA
[ONE General] Spannaa:
Added ZNH2KAS2X1 -> ZNH2KAS3P0 Incremental update to post #1
[ONE General] anagramgenius:
It seems they've patched QuadRooter with this update.
[ONE General] cristian95:
And gave a few bugs such as no more heads up notification(alow peeking) for google play store, downloads , fb, messenger and that's all. Android core apps drain stilp not fixed.
[ONE General] Matteo_666:
Official zip and img are out

Gesendet von meinem A0001 mit Tapatalk
[ONE General] joeclark:
Thank you.
[ONE General] Anghirrim:
No, once you're unlocked, unless you manually re-lock, nothing will lock your device again.
[ONE General] Spannaa:
Added ZNH2KAS3P0 full zip, fastboot zip & boot debuggable image to post #1
[ONE General] HannibalLecter:
another update by Oneplus for bacon?
[ONE General] hgmichna:
No Cyanogen OS 14 for the OnePlus One?

Yes, but it was made by Cyanogen, not OnePlus. So far the update speed is excellent.

I hope it will remain so through Android 7 "Nougat", but there are ominous signs of QualComm not updating their 801 processor or its driver for Vulcan (graphics API), which, in turn, seems to be a requirement for Google's stamp of approval for Cyanogen OS.

So the current grapevine whispers that we may have to switch from Cyanogen OS 13 to CyanogenMod 14 (without Vulcan, because they cannot help it).

Does anybody here know more about this?
[ONE General] cristian95:
Most probably they won't update the driver, mainly because the 800 series are 2 years old. But let's hope for the best.
[ONE General] kryshnakishore:
Why cm-13.1.2-ZNH2KAS3P0-bacon-boot-debuggable.img is 40 kb?? Is it correct or corrupted?

---------- Post added at 08:07 PM ---------- Previous post was at 08:02 PM ----------

Instead of signed zip, I have downloaded signed fastboot zip. Is there any way to make changes in zip so that I can escape from downloading entire zip again. Any help [MENTION=2948558]Spannaa[/MENTION]
[ONE General] Spannaa:
Looks like the boot debuggable image got corrupted when I uploaded it. I've fixed it now :good:

You can use the fastboot zip to update - just don't fastboot flash userdata or recovery if you want to keep TWRP and your data.

Read [MENTION=4153349]Heisenberg[/MENTION]'s How-To Guide For Beginners - especially section #8
[ONE General] HannibalLecter:
This is so bad. Just 2 year old and they wont update the drivers. This is ****.

Mediatek's processors are ****, samsung exynos is **** and now even snappy

I do not like this on their part. SAD
[ONE General] cristian95:
It's not that they're ****ty, it's just them being a normal company. The benefits of the actual chipsets are far more better than the "oldies". Just like in other domains, something good gets replaced with something new and better, and the support for the oldies is going down.
[ONE General] hgmichna:
No Cyanogen OS 14 for the OnePlus One?

Let's wait first until this is confirmed. New OnePlus One phones have been sold until fairly recently. It would be outrageous to stop support so soon.

But I admit that everything is possible in these greedy times.