yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] mko000:
Do you use profiles by any chance? I tried profiles today and had that happen a couple of times when using them to disable the lockscreen.
[Nexus 4 Original Android Development] klickig:
Yes I'm using profiles and also using them to disable the lockscreen.

Thanks for the hint. It's a cm related bug. Searched for it and found that the oneplusone has the same problem

http://xdaforums.com/showpost.php?p=60522073&postcount=1116

. But it seems to be old which is weird. Got this problem with the last couple of nightlies with the nexus.

After reading this http://forums.androidcentral.com/android-5-0-lollipop/465232-lollipop-black-screen-3.html

I think this is even lollipop related
[Nexus 4 Original Android Development] mko000:
I think it's definitely related to that.
[Nexus 4 Original Android Development] Packsman:
I got the same bug when disabling lock screen. i wonder if its reported on gerrit or JIRA. Btw are you guys using xposed ? Because I recently started using some modules and i don't know if its related to that.
[Nexus 4 Original Android Development] klickig:
Opened an issue on jira with attached logs. Hope it gets fixed.

https://jira.cyanogenmod.org/browse/NIGHTLIES-1721
[Nexus 4 Original Android Development] Packsman:
https://jira.cyanogenmod.org/browse/NIGHTLIES-1260?jql=text ~ "profiles"

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

Think its supposed to be fixed already.About 3 months ago...
[Nexus 4 Original Android Development] klickig:
yeah saw that too. But in my case it is not fixed.
[Nexus 4 Original Android Development] Packsman:
Are you using xposed ?
[Nexus 4 Original Android Development] mundavincicode:
i use stock kernel CM12.1, when i called someone my sensor got problem, my screen just black and when i press power button it open only 1 sec and it turn to black back, i cannot end call until the other side press end and my fone back to normal, it just happen when call only. can anyone help me about this?
[Nexus 4 Original Android Development] mko000:
I'm not, same issue.
[Nexus 4 Original Android Development] klickig:
Nope
[Nexus 4 Original Android Development] sergio_f:
20150822 and i got a lot of random reboots, anyone?
[Nexus 4 Original Android Development] :
No reboots for ages.
[Nexus 4 Original Android Development] Packsman:
I have. Clean install...
[Nexus 4 Original Android Development] Nilsb7:
None here either, dirty flashing nightlies since like 3 months ago. Very stable.
[Nexus 4 Original Android Development] ahoyboyhoy:
On 8/23 nightly, I was getting reboots while on a phone call for more than a few minutes. Happened on three calls I made or received yesterday. Flashing 8/26 now.
[Nexus 4 Original Android Development] sergio_f:
me too, reboots got fixed on 8/24 to me, ill try 26
[Nexus 4 Original Android Development] 666biker:
met someone this kind of issue in this time? (me after 22082015 update).

when I have call, display goes ON( wake-up) after few seconds, meaning, when phone is ringing, I see black screen for approx. 4s and after that I see who is calling, buttons, ...)

it is some temporary issue in CM12.1 latest builds or how to fix it?
[Nexus 4 Original Android Development] Johnassel:
Since installing CM12.1 (clean install) I'm losing my SIM card then and now. The device simply doesn't recognize it until the device is rebooted. Before on stock 5.1.1 this issue didn't appear. I tried upgrading the radio to the latest version but that didn't help. Anyone with similar symptoms?
[Nexus 4 Original Android Development] Follomon:
I am on build 08262015 and chrome browser keeps crashing all the time. Unistalled the browser and reinstalled it. Same problem.
[Nexus 4 Original Android Development] nemanja066:
Same here.
[Nexus 4 Original Android Development] sigulda1:
I had reboots since 2015-08-23 (did not flash every version). Finally went back to 2015-08-18 which was fine before.
[Nexus 4 Original Android Development] mko000:
http://xdaforums.com/showpost.php?p=62514557&postcount=3669
[Nexus 4 Original Android Development] nemanja066:
Fix for Chrome FC in the next nightly. Thanks.

http://review.cyanogenmod.org/#/c/107747/
[Nexus 4 Original Android Development] Fossel:
Thx for the fix.
[Nexus 4 Original Android Development] dragos281993:
Is the latest nightly still as buggy and laggy as the last builds? For example, when the device is locked or you're in an app, or playing something, and someone gives you a call, does the device still freeze or turn black or the touchscreen becomes unresponsive and you can't answer it? I really need to know.
[Nexus 4 Original Android Development] Bad-Pixel:
Hello guys! Someone know how to add a searching bar on top of the home screen?

EDIT: Solved... I needed to install Google search!

Inviato dal mio Nexus 4 utilizzando Tapatalk
[Nexus 4 Original Android Development] n0b0dy666:
I've never experienced such bug and I've been using nightlies for the past ~3 months.
[Nexus 4 Original Android Development] Fossel:
Got that behavior even on stock 5.1.1. Doesn't change in cm12.1 for me. It's about 3 out of 10 calls that are “bad". Living now with it. Great phone anyway
[Nexus 4 Original Android Development] dragos281993:
I didn't have until a few build ago when all sorts of bugs appeared. I never had that issue with the calls. There was a little delay between the moment when the phone started ringing and the screen turned on but that was it. The latest builds have been messed up completely. Now I'm on Chroma and everything works perfectly fine. I was curious to see of anyone reported that behaviour.
[Nexus 4 Original Android Development] klaust58:
Never had sucht Problems. My N4 runs like lightning since the last xxx nightlys :cowboy:
[Nexus 4 Original Android Development] 666biker:
what is the experimental version (YOG6N0X00M) for mako?
[Nexus 4 Original Android Development] Bastlwastl2010:
+1
[Nexus 4 Original Android Development] sergio_f:
27082015 another RR when skype video call
[Nexus 4 Original Android Development] dragos281993:
What's RR?
[Nexus 4 Original Android Development] sergio_f:
Random Reboot
[Nexus 4 Original Android Development] dragos281993:
LOL. I figured it out after I left the comment. Thanks anyway !
[Nexus 4 Original Android Development] sergio_f:
yeah.. anyone tried this?
[Nexus 4 Original Android Development] Bastlwastl2010:
I see this:

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

Put out my crystal ball and say:

I think this is a first test for the m or stable release
[Nexus 4 Original Android Development] 666biker:
have someone test it? experimental release?
[Nexus 4 Original Android Development] sergio_f:
me! but tried update an app(swype kb) and got a random reboot, so i installed 2808
[Nexus 4 Original Android Development] cewrld:
I don't know why but my headphone mic (Creative HS-660-I2) does not work with CM on Nexus 4, but works on stock ROM, Chroma, Purity and my tablet N5100 with CM12.1.

Is there a fix for that?
[Nexus 4 Original Android Development] pakistanish:
What will happen if I flash a CM12.1 nightly on CM12.1 ROM with F2FS conversion?

Will I lose everything on my phone?
[Nexus 4 Original Android Development] dragos281993:
If you change the "system" to f2fs, it's gonna change back to ext4 after you flash the ROM, unless you modify the ROM to do that. Only the "data" and "cache" partitions will remain on f2fs after the "transition" but when as soon as you change "data" to f2fs all the data will be lost. So copy all your important files first. cause you'll lose them.

So, to make it short, format only "data" and "cache" to f2fs, then flash cm12.1 + a custom kernel that supports f2fs, otherwise you'll get stuck with a bootloop. I suggest you flash "Quanta v6". And you're all set. But just so you know, I haven't noticed a single difference in performance between ext4 and f2fs.
[Nexus 4 Original Android Development] ahoyboyhoy:
I've had similar problems since about 8/23 unfortunately. Considering rolling back to a prior build.
[Nexus 4 Original Android Development] dragos281993:
Glad to see I'm not the only one.
[Nexus 4 Original Android Development] Bastlwastl2010:
here is a good guide:

http://obihoernchen.net/1032/convert-your-nexus-4-to-f2fs-without-loosing-data/
[Nexus 4 Original Android Development] dragos281993:
Actually, I haven't payed attention to what you said in the comment. So you're ALREADY converted to F2FS, right? In that case, it means your "data" and "cache" partitions are on F2FS and the "system" is on ext4. When you flash a nightly, only the "system" partition suffers modifications (updates, etc). So the answer to your question is YES, you can flash nightlies everyday, just like before, without losing anything.
[Nexus 4 Original Android Development] pakistanish:
Yes that's what I was asking about. However, I flashed the nightly yesterday and on it I flashed the Quanta V6 kernel. That way I'm able to access my F2FS partitions.
[Nexus 4 Original Android Development] 666biker:
have someone also issue with screen on during incomming call? in my case, when someone is calling me,my phone is ringing, led is blinking, but my screen is off and its turn on after 3-4s.. it is some current build issue? proximity sensor issue? should be fixed somehow? have someone met this also?
[Nexus 4 Original Android Development] dragos281993:
Yeah. It's been around for a while. Is not present on AOSP though. What you said happened to me and the most annoying thing of all is the one where you use the device for anything and suddenly someone calls. You see that person calling you, but the device simply freezes and it takes a few second for it to start working again, and if you manage to answer before whoever is calling ends the call, you can't heart anything and the person on the other end can't hear you as well, for a few second. So, a pain in the ass. Too bad I can't report that to the CyanogenMod team. They need you to tell them about the bug but they also need a build of their cm12.1 that didn't have this behaviour, and I can't recall the last working build.
[Nexus 4 Original Android Development] pakistanish:
Yes it has been there in the nightlies. I hope that they solve this problem in the upcoming release.
[Nexus 4 Original Android Development] 666biker:
i think it was working fine in builds before 20.8. i update my N4 with 20150822 nightly and this issue starts. So fromg begining of august it was working fine.. also i have one reboot after using gps and traceker apps.
[Nexus 4 Original Android Development] pakistanish:
How much time does it take to lock in GPS. Mine takes forever! It's too slow
[Nexus 4 Original Android Development] 666biker:
gps is located as usual, in few seconds, but after 20150823 update i met random reboot when using gps tracking app during my workout (only one reboot while using gps tracking) but each day if i use it.
[Nexus 4 Original Android Development] ahoyboyhoy:
Does anyone have a build that doesn't have the random reboot or incoming call issue (08.18 maybe?). The CM download links are returning 404s
[Nexus 4 Original Android Development] dragos281993:
That's exactly the build I was thinking about. I remember that my phone worked great on that build, but unfortunately, I can't find it on the CM download page.
[Nexus 4 Original Android Development] Grimlock42G1:
+1

Gesendet von meinem Nexus 4 mit Tapatalk
[Nexus 4 Original Android Development] ahoyboyhoy:
Out of curiosity, please respond to the following if you have been experiencing the random reboot and incoming call issues:

1. Did you format your /data and cache to F2FS? (I did around the time the issue appeared)

2. If using a custom kernel, which? (I'm using Quanta v6test3)
[Nexus 4 Original Android Development] 666biker:
i have cm12.1 without any other modification (default kernel, no F2FS)
[Nexus 4 Original Android Development] dragos281993:
No, you're fine. I tested every single possibility, ext4, f2fs, always complete wipe, even flashing back the stock ROM and starting "clean". The same issues. I haven't experienced but maybe 2 random reboots in a period of a month but the calling bug... well, that's just always there. It's frustrating to not be able to answer a call properly or at all when you most need it.

So, again, it's a coincidence that the bug appeared right when you made the transition to f2fs.
[Nexus 4 Original Android Development] scufita.rosie:
Hello everyone, attached the 20150817 nightly. I dont have the 18 but this one works just fine ;)

https://www.dropbox.com/s/uvqk4dna8gj4b1z/cm-12.1-20150817-NIGHTLY-mako.zip?dl=0
[Nexus 4 Original Android Development] 666biker:
it is enough just to install via recovery? from newer nightly to few days older? without any problems and loosing data?
[Nexus 4 Original Android Development] dragos281993:
Of course it's OK. Flash the ROM then do a cache + dalvik cache wipe, just in case.
[Nexus 4 Original Android Development] klickig:
Experiencing the same behavior. Tried to report the issue but couldn't tell which nightly was the last-known-good. The issue got closed. https://jira.cyanogenmod.org/plugins/servlet/mobile#issue/NIGHTLIES-1722

In my case this happens when pop up notifications are disabled.
[Nexus 4 Original Android Development] dragos281993:
OK, so I clean installed the version from 17th this month, and everything worked great in pretty much all the scenarios I could think of, regarding the incoming calls issue. The only bug left, which was present since forever, is the >screen on delay (~4 seconds)< when receiving a call. I pointed them in the right direction, but something tells me that will stay there forever.

Here's the issue I opened: https://jira.cyanogenmod.org/browse/NIGHTLIES-1758
[Nexus 4 Original Android Development] acejavelin:
Finally had to switch away from CM this weekend... The black screen and delays on an incoming call, added to the small delay for the screen to wakeup on an incoming call that Hellscore kernel gives you, finally frustrated me too much, so I switched to Purity plus Hellscore and its been rock solid and battery life is improved.

Not saying its the answer for everyone, but remember there are tons of other ROMs out there that might work for you as well.
[Nexus 4 Original Android Development] dragos281993:
I reported the bug on the "cm regression page", gave a build that didn't have the bug, so the "issue" is valid, which means they'll make it go away in the upcoming builds.
[Nexus 4 Original Android Development] gioxoid:
Is there a way to automatically update also the CM recovery in pair with nightlies?
[Nexus 4 Original Android Development] pakistanish:
Yes you can do that by going into developer settings and selecting Update Cyanogen Recovery.
[Nexus 4 Original Android Development] gioxoid:
I did it but it seems that it doesn't download the updated recovery img alongside with the rom .zip :confused:
[Nexus 4 Original Android Development] alexandreantunez:
Snapshot is up

https://download.cyanogenmod.org/?device=mako&type=snapshot
[Nexus 4 Original Android Development] azrash:
has anyone updated to the CM12.1 snapshot from the last CM11 snapshot just fine? still on the last CM11 snapshot, with little free space on the phone.
[Nexus 4 Original Android Development] GallStones:
Hmmm.... I just tried a dirty flash of the latest cm12.1 snapshot over the 0830 nightly and I got stuck in a boot loop.

Providently I made a nandroid before, so I restored it.

I doubt you'll manage to boot if you update CM11. If you want to risk , make a backup and give it a try!
[Nexus 4 Original Android Development] ahoyboyhoy:
Dirty flashing resulted in "com.android.phone" crashes and an unusable phone. I haven't verified whether my data partition is corrupt or not by flashing the latest nightly yet.
[Nexus 4 Original Android Development] azrash:
that is probably because the snapshot is older than the 0830 code tree. normally they freeze the code for some time for snapshot and iron out the bugs. not sure which code tree they are using for the snapshot release, probably from a week or two ago. if you are dirty flashing from a nightly that is before the snapshot code freeze, it'll upgrade fine.

I dirty flashed from CM11 M12 to the CM12.1 snapshot, rebooted fine. ART is taking its time to build the cache, i have tonnes of apps. lol. 391 packages to cache. halfway there
[Nexus 4 Original Android Development] 666biker:
have someone try cm12.1 snaphshot 20150901? update from latest nightlies (e. g. 20150830 or 20150831?) and wipe cache and dalvink?

it is working fine? or better to not install?
[Nexus 4 Original Android Development] gioxoid:
Don't do it. Snapshot is older than 0830 you will get bootloop very probably. Snapshot only as clean install
[Nexus 4 Original Android Development] xWolf13:
The latest snapshot is newer than the 0830. It's a 0901 build. A dirty flash will do fine....
[Nexus 4 Original Android Development] azrash:
It really is not. Look at my post, a few posts before this, on snapshot code freeze.
[Nexus 4 Original Android Development] scissorscrush:
Can you believe this...
[Nexus 4 Original Android Development] rogers11:
It's Kitkat? :)
[Nexus 4 Original Android Development] scissorscrush:
Yes... Kitkat... ?
[Nexus 4 Original Android Development] Jean_85:
Anyone still having random reboots with the latest nightlies?
[Nexus 4 Original Android Development] 666biker:
i have random reboot mostly while using GPS tracking
[Nexus 4 Original Android Development] suomii:
Yes I'm agree with you : dirty flash on nightlie 0827 makes "com.android.phone" crashes

A dirty flash nightly 0827 over it and it's working again
[Nexus 4 Original Android Development] xxmarkosxx:
hello, i have 12.1-20150706 nightly (yeah don't laugh, it was the best with almost no bugs, but I think there is some battery leak), does it worth updating in new snapshot? or in the newest nightly? or do nothing? :P
[Nexus 4 Original Android Development] dragos281993:
Of it's working perfectly fine, you better stay there, and forget about the newest nightlies. They're mostly buggy and you'll be disappointed that you updated. For example, I downgraded to the build from 17th (this month), cause I could near seeing random reboots (3 in a day on the one from 30th), and the bugs related to the heads up notifications.

As for the battery drain, I'm sure it's all about the governor you chose to use. I'm sure that, with a bit of tweaking, you'll manage to preserve the battery a lot better.
[Nexus 4 Original Android Development] xxmarkosxx:
thanks for the info.

i have hellscore kernel and the governor is ONDEMAND. Any better to suggest? As I don't play games (although Facebook is really heavy nowadays) I think that I could also undervolt or lower cpu frequencies

oh and I have version b80 and latest is b81, worth the update?
[Nexus 4 Original Android Development] vampire36:
Use conservative governor with b81 :)
[Nexus 4 Original Android Development] dragos281993:
I'm on hellscore too. Flash b81 and chose "hellsactive" as governor. It's great, it's the best in the list, and it's balanced properly for performance and good battery life. On demand always drained my battery a lot faster than the other governors.
[Nexus 4 Original Android Development] xxmarkosxx:
thanks guys. I'll try both :)
[Nexus 4 Original Android Development] 666biker:
currently I have (testing :) ) CM12.1 20150902, but there are still bugs with screen on delay while incomming call and random reboot.. I have one older version 20150718 ..should I normally install this version via recovery? or it is not safe to jump back to more than one month? ..without losing data, etc...
[Nexus 4 Original Android Development] pakistanish:
Why can't I flash Snapshot 20150901 over my nightly? Whenever I flash it I get android process has stopped error and the phone reboots.
[Nexus 4 Original Android Development] dragos281993:
Someone already said that to make it work properly, you need a clean install, which consists of a data wipe.

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

You won't lose anything of you downgrade to am older version. As long as you do a cache wipe, you're good.
[Nexus 4 Original Android Development] klickig:
can you upload 20150718 somewhere please
[Nexus 4 Original Android Development] dragos281993:
You can use the build from 17th. It's basically the same thing, and it works perfectly fine.

http://xdaforums.com/showthread.php?p=62593375 [MENTION=4239604]scufita.rosie[/MENTION] needs all the credit and thanks for providing that build.
[Nexus 4 Original Android Development] klickig:
but you can't tell if this bug https://jira.cyanogenmod.org/browse/NIGHTLIES-1721 doesn't exist in the nightly, don't you??
[Nexus 4 Original Android Development] dragos281993:
I'm not using profiles, so I can't say. But, compared to the latest nightlies, the build that I gave you, has a lot less bugs anyway, so you can use it without problems until the cm teams fixes the ones that are everywhere in the latest versions.
[Nexus 4 Original Android Development] Jean_85:
To me, they happen while using Podcast Addict (no streaming, just listening to downloaded episodes)
[Nexus 4 Original Android Development] pakistanish:
Is there any other kernel besides Quanta that supports F2FS for CM 12.1?
[Nexus 4 Original Android Development] sigulda1:
[MENTION=6061016]666biker[/MENTION]:

You could go back to 2015-08-18 (last stable for me). At least going back a few days is no problem. And as somebody else already wrote: Delete Cache and Dalvik and you should be fine.

(This was meant to be an answer to 666biker in http://xdaforums.com/showpost.php?p=62632177&postcount=882, but I did not quote him by accident.)
[Nexus 4 Original Android Development] 666biker:
can you upload 20150818 nightly version? or it is still available somewhere?

thanks
[Nexus 4 Original Android Development] dragos281993:
Try this build. It's from 17th, a day older. This guy was kind enough to upload it on dropbox. In currently on this build and all's nice and well, with no annoying bugs.

http://xdaforums.com/showthread.php?p=62593375
[Nexus 4 Original Android Development] bla_laber:
You can try hellscore or Matr1x for example. I'm using hellscore and quite happy with it. But usually devs offer two versions: CM-version and AOSP-version, so make sure to download the correct one.
[Nexus 4 Original Android Development] AnaguaMateus:
I made like you said. Reverted from 02 Sept to this one.

Cleaned in recovery cache and Dalvik cache.

A process called com.*****don't remember***.phone is always crashing.... :(
[Nexus 4 Original Android Development] 666biker:
here is CM12.1 20150718-NIGHTLY (mako) if someone want to try it / use it

https://www.sendspace.com/file/21398e
[Nexus 4 Original Android Development] dragos281993:
666biker uploaded the version from 18th. Try that. What you said you got, I mean that error, never happened to me, and I updated or downgraded many times. What i always do is wipe cache+dalvik cache before flashing the ROM, then flash the ROM, and right after, I wipe again cache + dalvik cache.I always pay maximum attention when I flash stuff, and I do the necessary wipes before and after a major flash.

---------- Post added at 04:09 PM ---------- Previous post was at 04:06 PM ----------

Hellscore does not support f2fs. Hellsgod didn't think it was necessary, so he didn't implement what needed to be added to make it compatible with f2fs.

Change cache+data to f2fs, then flash the ROM and hellscore, and you've just got the nicest bootloop ever.
[Nexus 4 Original Android Development] mx82:
[MENTION=4239604]scufita.rosie[/MENTION]

Thanks for the 2015-08-17 -nightly.

If checked the md5sum: 40c280e37c9cf5a4ce0485e403d1ba879066eea5 . It's correct.
[Nexus 4 Original Android Development] pakistanish:
I flashed hellscore and got frustrated when the phone got stuck in bootloop. Thanks for the information. Is there any other kernel besides quanta that supports F2FS?