[ROM][SEMI-OFFICIAL?][6.0.1][Nexus4/Mako] CyanogenMod 13 Nightlies

[Nilsb7]

CyanogenMod is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device.

 * Your warranty is now void.
 *
 * We are not responsible for bricked devices, dead SD cards,
 * thermonuclear war, or you getting fired because the alarm app failed. Please
 * do some research if you have any concerns about features included in this ROM
 * before flashing it! YOU are choosing to make these modifications, and if
 * you point the finger at us for messing up your device, we will laugh at you.
 *

CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.

All the source code for CyanogenMod is available in the CyanogenMod Github Repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.

CyanogenMod 13 Changelogs

Instructions
First time flashing CyanogenMod 13 your device, or coming from another ROM?
Official long version:
Installing CyanogenMod from recovery

Short version:
1. Download the zip(s) from the download section below.
2. Install a compatible Recovery
3. Perform a NANDroid backup of your current ROM (Optional)
4. Perform a Factory reset (wipe data & cache partitions of your device)
5. Flash your CyanogenMod zip file
6. Optional: Install Google Apps

Downloads
Official CM13 Nightlies
TWRP Recovery
Official Open GApps (Choose the nano version or smaller. The other versions won't fit.)
Open GApps XDA-Thread
Note: Some GApps are very basic & will give you only Google app & Google Play Store. The rest of the apps can be downloaded directly from the Play Store as per your need after signing in to the Google. If calender syncing is not working so there is an additional script for that, just flash it & voila it will start working.

Bugreports
On nightlies, you don't have to report bugs here, if you wish to, you can do that here.

Thanks!
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy.

PS: I have not built this rom, I don't even know if I can post this here, it's mostly a copypaste from another CM thread. If you want me to edit/remove this just tell me.

 

[Nilsb7]

Current nightly status

I'll use this post for the current nightly build status, wether it has major issues or not. I'll try to keep this updated based on the communities replies, no guarantees though.

Current 20160219 build status: GOOD

20160129 nightly causes bootloops and was removed from get.cm. The build from 20160127 is fine, so use that instead.

 

[sigulda1]

Thanks for opening this thread!

Just a little note. From my experience it is quite important to wipe system as well, if you plan flashing a new ROM. Of course this depends on the previous ROM. Most of the times it might not be necessary, but for me it is "best practice".

 

[bringonblink]

Might need to get the AOK from mods about this thread, but hopefully will be ok, makes sense to get cm13 one by now.

 

[hozjacz]

Hi, thx for this thread. I love Cyanogenmod from version 6 and I was very happy, that came CM13 MM, but with a few last builds I have trouble with lags. After reboot is several hours everything OK, but after that I have several seconds lags when I want run some application (or wake from recent apps).

The same trouble was in last builds CM12.1. Let me know, if exist some solution? Now I must left CM13 (to Chroma and lags are gone), but I want come back, but without lags...

Do you have some of you the same trouble?

Odesláno z mého Nexus 4 pomocí Tapatalk

 

[Nilsb7]

Thanks for opening this thread!

Just a little note. From my experience it is quite important to wipe system as well, if you plan flashing a new ROM. Of course this depends on the previous ROM. Most of the times it might not be necessary, but for me it is "best practice".

Had to research it because I wasn't sure about this part either (I copy pasted it from the old thread..) but apparantly a Factory reset is the way to go as CM installs wipe the system partition anyways. Manually wiping the system partition actually seems to cause some issues. The official instructions don't mention wiping system either. Thanks for the feedback though.

 

[bringonblink]

Manually wiping the system partition actually seems to cause some issues.

Huh? Never heard that before, any sources?


Sent from my Nexus 4 using Tapatalk

 

[xWolf13]

Had to research it because I wasn't sure about this part either (I copy pasted it from the old thread..) but apparantly a Factory reset is the way to go as CM installs wipe the system partition anyways. Manually wiping the system partition actually seems to cause some issues. The official instructions don't mention wiping system either. Thanks for the feedback though.

Huh? Never heard that before, any sources?


Sent from my Nexus 4 using Tapatalk

Manually wiping the system partition causes no problems at all. It simply wipes the ROM, and when flashing a new build, will replace it. Unless you are using CyanDelta, wiping the System should not cause any problems. I, for one has not gone through any problems while wiping my system partition.

 

[Nilsb7]

Huh? Never heard that before, any sources?


Sent from my Nexus 4 using Tapatalk

Manually wiping the system partition causes no problems at all. It simply wipes the ROM, and when flashing a new build, will replace it. Unless you are using CyanDelta, wiping the System should not cause any problems. I, for one has not gone through any problems while wiping my system partition.

Had some problems with this myself when trying to update from CM12 to CM13, I tried to only wipe /system though, because I was trying to get rid of a buggy/unkown gapps installation, and this caused error messages to pop up when trying to flash the CM13 version in TWRP. Can't find any sources for this besides this one though, this was the only one I found when searching before so I assumed it was right.
Guess I was wrong? .

 

[bringonblink]

Had some problems with this myself when trying to update from CM12 to CM13, I tried to only wipe /system though, because I was trying to get rid of a buggy/unkown gapps installation, and this caused error messages to pop up when trying to flash the CM13 version in TWRP. Can't find any sources for this besides this one though, this was the only one I found when searching before so I assumed it was right.
Guess I was wrong? .

Oh if you're flashing different android versions without doing a full wipe, yeah you're gonna get problems

 

[Nilsb7]

Oh if you're flashing different android versions without doing a full wipe, yeah you're gonna get problems

Dirty flashing was approved/recommended officially see here.

Back on topic, anyone tried the 20160201 nightly yet?

 

[bringonblink]

Dirty flashing was approved/recommended officially see here.

Back on topic, anyone tried the 20160201 nightly yet?

I'm using it, no problems so far

Edit

Seem to be getting a huge "sns_async_ev and sns_periodic wakelock" wakelock. Actually not letting the device sleep at all. Looks to be related to the hardware sensors.

Can anyone else check if they have this?

Sent from my Nexus 4 using Tapatalk

 

[Nilsb7]

I'm using it, no problems so far

Edit

Seem to be getting a huge "sns_async_ev and sns_periodic wakelock" wakelock. Actually not letting the device sleep at all. Looks to be related to the hardware sensors.

Can anyone else check if they have this?

Sent from my Nexus 4 using Tapatalk

I'm on 20160201 and I don't have that issue. Here's a screenshot of my battery stats, the long wake periods are caused by my audiobook player.

 

[bringonblink]

I'm on 20160201 and I don't have that issue. Here's a screenshot of my battery stats, the long wake periods are caused by my audiobook player.

Something strange is going on, just did an hour test, where the phone did not go into deep sleep at all (from the wake lock, however drain seemed good at -1%an hour.

You can see from the pic it stays awake, but no battery drop off :s



Sent from my Nexus 4 using Tapatalk

 

[Nilsb7]

Something strange is going on, just did an hour test, where the phone did not go into deep sleep at all (from the wake lock, however drain seemed good at -1%an hour.

You can see from the pic it stays awake, but no battery drop off :s

View attachment 3631357

Sent from my Nexus 4 using Tapatalk

Have you tried rebooting it at least once after flashing the nightly?

 

[izuels]

I´m having problems enabling the WIFI after 4 days using the CM13.... it is very strange.

What I have tryed,

-Fly mode on - off
-Flashing the Radio
-Wiping cache with TWRP

Still not working

You can find some screenshots attached....

 

[Nilsb7]

I´m having problems enabling the WIFI after 4 days using the CM13.... it is very strange.

What I have tryed,

-Fly mode on - off
-Flashing the Radio
-Wiping cache with TWRP

Still not working

You can find some screenshots attached....

Try the latest nightly, this might be related.

 

[izuels]

Try the latest nightly, this might be related.

That was.... now after installing the last Nightly it works :/

I found also that the APP which is giving problems is https://play.google.com/store/apps/details?id=com.ryanamaral.wifi.passwords

 

[AJ205]

im on the 20160202 nightly and everything seems fine except for the user profiles, it looks like they dont do much, i set a profile that toggles from 3g to 2g when connected to wifi but nothing happens. what else... the weather isn't displayed in the status bar and in the clock widget... multiple APN for the same carrier that sometimes disables the whole network until setting up the correct APN... but other than that its flawless. i rather stick to cm13 nightly than going LL or custom MM.

Sent from my Nexus 4 using Tapatalk

 

[mx82]

I installed nightly 2016-02-06. Everything looks fine since 24hours.
But CM has chosen the wrong APN : Wap.vodafone.de instead of web.vodafone.de