yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] Razer(x):
Anyone has issues with weird preview of photos made on CM13?
[Nexus 4 Original Android Development] KSLevel11:
I had the same problem at official 5.1.1, and I guess I have it now on CM13.
[Nexus 4 Original Android Development] thebrainkafka:
2G toggle not working, means no only 2G mode possible. Where to report ?
[Nexus 4 Original Android Development] mascolel:
Crap... Just received a message saying that there was a new ROM available for download.... downloaded it and installed. Just after all I reallised that it was a new version of the ROM. Now my mobile is not working and I will lose everything =,(
[Nexus 4 Original Android Development] VegetaSSJ5:
I have disabled the automatic updates (I decide when update the smartphone), but if you think that it is an important feature, you should check only for snapshot (or something that means "stable")
[Nexus 4 Original Android Development] KSLevel11:
Already fixed in newest nightly.
[Nexus 4 Original Android Development] drpfenderson:
Heads up, but LTE broke in CM13-20160105 for me. Baseband still looks like correct radio (ends in .33), APN set correctly, as well as "Preferred Network Type". However, "Testing > Phone Info" will not let me switch to LTE. The option is there, but selecting any of the LTE options does nothing at all. No change, no radio cycle, nothing. It has been working in every nightly since the 12.1/13 switchover so far.

EDIT: Turns out I needed to re-edit build.prop. I have never manually edited build.prop, and usually rely on an all-in-one LTE script (which is currently not working with MM).

I went in, deleted LteOnCdmaDevice, and replaced with

telephony.lteOnGsmDevice=1
ro.telephony.default_network=9
ro.ril.def.preferred.network=9

Went back to *#*#4636#*#* and swapped over to LTE/CDMA, and all is well. *wipes brow* Glad it was something simple.
[Nexus 4 Original Android Development] sergio_f:
solved??? want help?
[Nexus 4 Original Android Development] kino13:
Hello,

after a long time I decided to upgrade from 12nightly to 13... and it was a mess... even with a clean install.

Spent a lot of hours until I realized that the CM13 was not f2fs friendly.

I finally formatted my system, data and cache into ext4 and only then did the rom boot correctly.

So a few questions:

Has anyone tried to experiment with f2fs?

What's the deal with the superSu? I tried to install it... and got me a nice bootlop, yeah, I read that it is not recommended but wanted to see if titanium worked better with it.

Right now I used titanium to restore, well, most of my apps, only thing that still doesn't work is the "uninstall" option for system apps. I suppose I will have to use a file manager to remove the binaries from system from everything I don't use.

Has anyone had any more luck with either of these: titanium backup, f2fs or superSu?

Other than that, the rom looks estable (using opengapps pico), and battery life seems normal too.

Checked wifi, bluetooth, 3g... all correct for now.

Regards
[Nexus 4 Original Android Development] dragos281993:
1. Cm13 should work with f2fs. After you flash cm13, you need a custom kernel that supports that, like "Quanta kernel" or "Taurus kernel", so the kernel is the main thing that let's you use f2fs (for cache + data).

2. SuperSU from 2.56 to 2.66 are systemless root versions. Everything older is installed in the "system" partition while these newer versions are installed in "data"instead. You have to do a system wipe to be able to not end up with a bootloop. You can't upgrade from cm12 to cm13 just like that. You need to do a system + data + cache + dalvik cache wipe.

So if you want to try f2fs once more:

- format cache + data to f2fs, again.

- flash cm13

- flash Gapps (banks' Gapps are the best)

- flash SuperSU 2.66

- flash Taurus kernel or Quanta (make sure you download the CM version of which one of these 2 you prefer)

Reboot to system.
[Nexus 4 Original Android Development] kino13:
Thanks a lot Dragos, that explains quite a few things...

Yes, I was using Quanta when I was with the CM12, but I thought that the original kernel had support for f2fs, my bad.

I will try again with Quanta, and also will try the supersu, I must be confused because I thought that the last version was 2.52, I will check the changelog carefully this time.

Now, let's see how to add support to TWRP for f2fs again... (need to copy the mkf2fs manually into system)

Again, many thanks for the explanation!
[Nexus 4 Original Android Development] dragos281993:
You don't need to manually add an f2fs option to twrp. You have multirom twrp for that. Here's a tutorial to make everything easier.

http://xdaforums.com/nexus-4/help/guide-detailed-f2fs-manual-format-guide-t3264185
[Nexus 4 Original Android Development] trees247:
How can I chage the lock screen wallpaper if I can...
[Nexus 4 Original Android Development] insigma28:
Your welcome bud, I have always use custom kernel makes phone battery and performance better man.
[Nexus 4 Original Android Development] simmeone:
I tried it again and the same problem. With CM 12 no problems with Bluetooth and my car radio. CM 12.1 Bluetooth crashes while connecting to my car radio. Don't know if the problem is CM or my car radio. I did a downgrade to CM 12, all works perfect... F...
[Nexus 4 Original Android Development] Tubbby:
Hi all - I wanted to say I'd been having issues with Gmail not showing Exchange Accounts (the option wasn't available), Exchange was only available for the phone and the normal Mail app.

Not sure if I've been out of the loop with CM for so long, but seems like the correct Gmail version of Exchange Services (com.google.android.gm.exchange) isn't installed with any of the GAPPS packages I've tried. Instead, the normal Mail Exchange Services (com.android.exchange) service is.

Gmail doesn't play ball with this, and I needed to install the Gmail Exchange Services, from here to enable Gmail Exchange as an option. At the time of writing I installed this one.

I have tested this and it works fine on my Mako with Gmail. I even disabled the incorrect Mail Exchange Services APK and older Mail APK too, to me it's cleaner.

I've got to say though in general, the performance of this CM12.1 ROM is just incredible, especially with the Quanta V3 kernel as well. My battery life has never been so good, it's incredibly quick and so much better than stock 5.1.

Anyway, that's my (hopefully correct) understanding, and I hope it helps someone...
[Nexus 4 Original Android Development] samiam21:
Same here. I was wondering about that also...
[Nexus 4 Original Android Development] monal94:
Please provide the link for the Quanta V3 kernel for N4 compatible with CM12.1. Thanks!
[Nexus 4 Original Android Development] insigma28:
http://xdaforums.com/showthread.php?p=55053022
[Nexus 4 Original Android Development] c00ller:
This will always happen if you wipe your phone then reinstall the authenticator app without restoring data through e.g. Ti Backup. You need to go to your Google security settings on desktop browser and go through the Google 2-step authentication process again. The way to prevent having to do this every time in the future is to use an app called Authy, which uses the cloud to save your account info. It even works across multiple android devices (e.g. phone and tablet) for one account.
[Nexus 4 Original Android Development] killer_chickens:
Looks like next nightly will be 5.1.1?

http://review.cyanogenmod.org/#/c/95707/

Or am I missing something?
[Nexus 4 Original Android Development] stryderpoa:
3g bug

I"m having a little bug with my 3g.

After I spend more than 2 hours connected on wifi when I go out the 3g don't connect. I just put it on airplane mode for a few seconds and it connects.

It happens since CM 12.
[Nexus 4 Original Android Development] dragos281993:
I really hope that's true.
[Nexus 4 Original Android Development] mr_nguyen298:
Orange screen

I get a issue with my screen after I flash CM 12 Rom. My screen is so orange . It does not display true color.
[Nexus 4 Original Android Development] jr67:
Do you have night mode on? If you do that would explain the orange screen. Check under settings > Display & lights > LiveDisplay > Display mode. If that's not it then check the color and gamma calibration settings.
[Nexus 4 Original Android Development] rogers11:
It's true
[Nexus 4 Original Android Development] ahoyboyhoy:
CyanogenMod updates not being found

In the settings menu > About > CyanogenMod updates and when manually checking for updates, no updates are found. Prior to updating to 12.1, things worked fine and updates were found. I'm currently on 4-20 nightly and there have been updates since.

I dirtied flashed over CM12 and I'm guessing the repo or branch needs to be reset. How to?
[Nexus 4 Original Android Development] abhishekjain.ims:
Use cyan delta app, I'm getting regular updates
[Nexus 4 Original Android Development] abhishekjain.ims:
If I use your custom kernel over stock CM kernel, can I go back to my stock kernel again & what if I do a clean install of any CM over existing CM then will that custom kernel stay there or will it be replace by stock CM kernel ?
[Nexus 4 Original Android Development] jr67:
Simply flashing the full ROM again will overwrite the kernel so you'll be back to the CM kernel which is why you need to also flash the kernel again after each update.

Not sure what happens if you're using cyandelta to update.
[Nexus 4 Original Android Development] abhishekjain.ims:
Can you just confirm if there is also any wifi battery draining issue presented on this custom kernel because on stock kernel wifi draining issue is presented. If I switched on my wifi it keeps my wifi scanning on all the time which can be seen in the battery stats or by going to *#*#4636#*#* under wifi status.
[Nexus 4 Original Android Development] SpawNyK:
Hi guys !

Just installed cm 13 and its not suited as a daily driver for me and i want to go back to the latest cm 12.1 but there's a problem.

I cant seem to download the latest nightly, the links are not working for me.

Could someone upload elsewhere ?

Thanks in advance !

http://oss.reflected.net/jenkins/140352/cm-12.1-20151221-NIGHTLY-mako.zip

https://download.cyanogenmod.org/?device=mako
[Nexus 4 Original Android Development] sebastiandg7:
I'm also looking for latest CM12.1 nightly cm-12.1-20151221-NIGHTLY-mako.zip can someone please share it? For ROM purposes...

Thanks!! :good: ;)
[Nexus 4 Original Android Development] bfoos:
I'm in the same boat. Not really liking CM13 and could really use the cm-12.1-20151221-NIGHTLY-mako.zip file if anyone has it and would be so kind as to upload it.
[Nexus 4 Original Android Development] mx82:
Here is your download:

https://www.dropbox.com/s/c19h3zaf8ercpbv/cm-12.1-20151221-NIGHTLY-mako.zip?dl=0

Greetings

PS: I use this version (dirty flash installation), sometimes the phone freezes.
[Nexus 4 Original Android Development] tvisforme:
Do you really need to wipe /data to upgrade to CM13? Or are you referring specifically to the f2fs process?
[Nexus 4 Original Android Development] bfoos:
I had to clean install CM13 coming from CM12. Otherwise I either got a bootloop which I think was supersu related or tons of force closes which I believe were gapps related. The only way I could get CM13 to play nice was clean install, use updated 6.0 opengapps and do a systemless supersu install. I believe I am now done with CM. The unofficial Pure Nexus + Taurus kernel fit my needs far better.
[Nexus 4 Original Android Development] cb474:
I theory you don't need to. Here's what the Cyanogen blog said, when 13 was release:

I think this was already mentioned above in this thread. But it does sound like different people are having different experiences. I would make a nandroid backup, try the dirty flash first, following the procedures the Cyanogen blog describes, and if that doesn't work either revert to your previous install or go ahead and do the full clean install.
[Nexus 4 Original Android Development] rogers11:
I had a lot of SODs with the 01/11 and 01/12 nightlies. Never had them before. Anyone else with this problem? Everything is fine again with the older 01/09.
[Nexus 4 Original Android Development] sigulda1:
I am on 01/12 without issues.
[Nexus 4 Original Android Development] rogers11:
I tried again with 01/14 today.

Installed, put it beside (on), waited until auto off, tried to switch it on again -> SOD

Back to 01/09 again. :(
[Nexus 4 Original Android Development] sigulda1:
Have you tried with system formated?

I came from CM 12.1 and formated only system, dalvik and cache. Tried nearly every nightly (downloading 01/14 right now). Using the phone as daily driver. Works without a flaw.
[Nexus 4 Original Android Development] rogers11:
CM13 was a clean install. The problem started with 01/11 and the following Nightlies. Going back to 01/09 always fixed it. So I do no think that formating /system will help much. Currently testing 01/10 to file a report somewhere.
[Nexus 4 Original Android Development] Razer(x):
I had the phone in my pocket, i took it out and it was optimizing applications, now it won't boot anymore
[Nexus 4 Original Android Development] thebrainkafka:
Damn pocket......

Just choking. Tell us more details if we should be able to help
[Nexus 4 Original Android Development] mascolel:
I'm using cm 13 and it is working fine until now.

I have few suggestions for the developer that are not urgent:

- On the lockscreen, allow insertion of PIN without having to press SEND BUTTON (as on cm 12.1)

- Use camera with panoramic pictures

- My screen seems to take 1 second to turn on/off after clicking on power button. If other ppl are having the same issue, than it would be interesting to decrease this period.

Congratulations for the job! :good:
[Nexus 4 Original Android Development] underskyzx:
Quick Unlock... I miss this
[Nexus 4 Original Android Development] KSLevel11:
I have this problem after newest nightly flash. How I can fix this?

Wysłane z mojego Nexus 4 przy użyciu Tapatalka
[Nexus 4 Original Android Development] maxauvy:
Hi there,

my GF's Nexus 4 really wants to upgrade from CM12.1 to CM13, but when I try to do this, after optimizing apps, CM13 just can't stop sending me some "com.android.phone has stopped". No PIN-entry, no network, just a design paper-weight.

What I did : wipe system, cache and dalvik cache, install CM13 zip + opengapps 6, reboot...

As the owner has a lot of apps and data, I would prefer not to factory reset... How can I do?

Thanks a lot :)
[Nexus 4 Original Android Development] n0b0dy666:
It's a known issue and they're working on it. You can hold settings (gear) icon and add your tiles but they won't restore after reboot.
[Nexus 4 Original Android Development] rogers11:
Already fixed in today's Nightly.
[Nexus 4 Original Android Development] n0b0dy666:
It should be but it's not, tiles still don't show up after reboot.

edit: it should finally be fixed in the next nightly link
[Nexus 4 Original Android Development] cb474:
Does anyone know if this 0day exploit in the linux kernel has been patched in CM13? I don't see it in the changelog, but maybe I'm missing something.

http://perception-point.io/2016/01/...f-a-linux-kernel-vulnerability-cve-2016-0728/

http://arstechnica.com/security/201...f-millions-of-pcs-servers-and-android-phones/

It's an extremely bad bug that can allow complete root access to a third party on a device.
[Nexus 4 Original Android Development] BlackJack313:
I am running the most recent CM13 nightly (cm-13.0-20160120-NIGHTLY) on a Nexus 4 and and recently discovered system profiles. I have found that I am unable to change my lockscreen in those profiles due to the following error:

http://imgur.com/8GNXQtQ

I have tried clearing the security credentials, checking trust agents, removing any VPN profiles and any guest users (at some point I accidentally created one), besides wiping the device does anyone have any suggestions?
[Nexus 4 Original Android Development] Nilsb7:
http://www.androidpolice.com/2016/0...-believe-many-android-devices-are-vulnerable/

Short answer seems to be:
[Nexus 4 Original Android Development] cb474:
The people who discovered the exploit, Perception Point, found in the first link I provide, clearly state that most Android devices are vulnerable. In fact, it is only very old versions of Android that are not vulnerable. But they believe about two thirds of all Android devices are vulnerable.

They explain that SELinux helps mitigate the vulnerability, but does not totally solve the problem. Adrian Ludwig at Google replied saying they think fewer devices are affected than Perception Point states, but Ludwig merely says they "believe" that and provides no basis for his assertion. See: https://plus.google.com/+AdrianLudwig/posts/KxHcLPgSPoY It comes accross as if Google is just trying to down play the problem.

Perception Point has not walked back from their claim that 66% of Android devices are vulnerable.

The obvious solution is to patch the kernel. Linux Distros like Debian and Arch did it the day the problem was announced. That's what people who take security seriously do. Google obviously is very slow to issue updates. But Cyanogen has nightlies, so they could do it right away. So I'm still wondering if Cyanogen has patched the problem. I don't see anything in the Cyanogen changelog that cleary shows they have issued a patch. But maybe I'm missing something.

Anyway, I would not take lightly a bug that can allow complete root access to a device. Obviously the Linux distros addressed it right away, as should be the case. This is a classic example of the fundamental security problems with Android, that receives updates so infrequently.
[Nexus 4 Original Android Development] Nilsb7:
Ah you're right, I did not know that.

For anyone else who wants a less onesided view on the point than my previous source. See here.

There are some mentions of KEYS in the commits of cm-13.0-20160117-NIGHTLY-mako.zip, but I don't know wether the issue was even known 5 days ago & there's no mention of the CVE in the commit messages either..

http://review.cyanogenmod.org/#/c/128567/

http://review.cyanogenmod.org/#/c/128566/

http://review.cyanogenmod.org/#/c/128565/

http://review.cyanogenmod.org/#/c/128564/

http://review.cyanogenmod.org/#/c/128563/

http://review.cyanogenmod.org/#/c/128562/
[Nexus 4 Original Android Development] cb474:
It looks like Debian actually patched the kernel for this problem on January 2. Often security researchers give affected parties a heads up long before they publically announce a vulnerability. That way there is not an automatically built in lag time between when the vulnerability is publically known and when it's patched. So the vulnerability has been known by some for a while, I think.

I wonder if it's true that Perception Point didn't contact Google, if they were giving others a heads up. I take everything Google says with a grain of salt. They seem to be contradicted in their assertions by many others. And Google really has not taken security very seriously for a long time. As I said above, when you look at how quickly Linux distros get patched and then look at the months it can take for Android, I just don't know what Google's deal is. (To be fair, Apple is often not much better. Ironically, Microsoft is probably the most responsive of the big three OSes.)

Anyway, thanks for the links. I can't see anything in those committs that clearly look like they address the issue, but maybe I don't know how to understand them properly. But given that Google as of yesterday has issued a patch, Cyanogen really ought to incorporate it right away. It's too bad they don't have a better way of communicating to users about security issues like this.
[Nexus 4 Original Android Development] zwliew:
That security vulnerability doesn't affect any kernel version below 3.8. Nexus 4 uses a 3.4 kernel. In fact, Nexus 4 doesn't even compile the affected code.
[Nexus 4 Original Android Development] cb474:
Ah, thanks, that's a relief. So the kernel varies depending on the device? Marshmallow or Lollipop on one device does not use the same kernel as Marshamallow or Lollipop on another? CM 13 uses 3.4 on the Nexus 4, but on the Nexus 6P is uses some other newer kernel? Is that right?
[Nexus 4 Original Android Development] arjundas86:
Nexus 4 was released with Jelly Bean (4.2), which was built on Linux 3.4 kernel.

KitKat (4.4) was built on kernel version 3.10, and subsequent Android versions were built on higher kernel versions.

Nexus 5 shipped with Lollipop, and that should be built on 3.16 based Kernel.

As far as I've read, when a device is released with specific android version and kernel, and later the android version is updated by manufacturer, the kernel version is mostly kept at initial version with patches. If this is true, then Google never updated Kernel source for Nexus 4 beyond 3.4, and all current Nexus 4 kernels (including custom kernels) are still based off Linux Kernel 3.4.x. So even if you're running a Marshmallow Rom (at which point, Google dropped support for Nexus 4 anyway), your kernel is almost certainly based off Linux Kernel 3.4.x. You can go into "About Phone" in settings to see what your kernel version is.

Hope that clarifies things a bit...
[Nexus 4 Original Android Development] linuxdep:
why CM12.1 last nightlys not online on original CM site?

i have upload my last nightly for a friend, so someone need also the nightly you can download.

http://www.share-online.biz/dl/Z3BNLM1O1HX

Name: cm-12.1-20151220-NIGHTLY-mako.zip

MD5: 5ca0f671c27a782eec4f4cc93418f58b

Size: 251MB
[Nexus 4 Original Android Development] Packsman:
Do not flash 20160129 nightly. Some kernel related changes here will get you into the bootloop.
[Nexus 4 Original Android Development] hal9008:
Bootloop here too in 20160129.

Enviado de meu Nexus 4 usando Tapatalk
[Nexus 4 Original Android Development] delisahip:
probleme bootloap

I 'm also bootloap.what to do?
[Nexus 4 Original Android Development] bokagavrilov:
the 0129 build was removed , flash 0127 or wait for todays build
[Nexus 4 Original Android Development] bringonblink:
Is there a separate thread for cm13?
[Nexus 4 Original Android Development] sigulda1:
Not yet. But it would make sense.
[Nexus 4 Original Android Development] Nilsb7:
I made one just to keep the discussions seperate.

http://xdaforums.com/nexus-4/orig-development/rom-cyanogenmod-13-nightlies-t3305271

I'm not affiliated with CM in any way, just doing this to help a little.
[Nexus 4 Original Android Development] :
Hello

Because of important security updates I made a build with the Android security patch level February.

For the critical bugs that got closed look at this link. [Note that not all bug might concern the Nexus 4]

I did not make any modifications - this build is from the official sources.

Make sure you got a backup before using this build - you never know ;)

Filename/Version:

cm-12.1-20160203-UNOFFICIAL-mako.zip

Download:

https://www.sendspace.com/file/why8zw

SHA256-sum:

a423ffb95d0545b1211731309399a9582a4d1521e27c067750af166c8f3f515e
[Nexus 4 Original Android Development] 666biker:
Hello, is latest cm13 nightly for mako (nexus 4) stable for daily use? battery life, calls, wifi, Bluetooth, gps,... all main daily features no reboots,... ?
[Nexus 4 Original Android Development] aney1:
Generally the cm13 nightlys are stable, but there are occasional issues you have to expect.

Bluetooth LE was broken for a while, then the Quicksettings disappeared, after that one nightly didn't boot at all. Todays nightly seems to have some issues with 3G.

Those are just regressions, so they happen only in specific nightlys.

If you don't want to be forced to downgrade to last days nightly from time to time, you should wait for M1. It should come pretty soon.
[Nexus 4 Original Android Development] bedalus:
Confirmed working build. Thanks for making the effort to share this.
[Nexus 4 Original Android Development] cb474:
Is there a new bootloader to be used with Marshmallow/CM 13? Or is the makoz30f bootloader from 5.1 still the latest bootloader?
[Nexus 4 Original Android Development] nitin.chobhe:
That's the latest one ?