yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] madsurgeon:
You'll have to modify the updater script, I've modified mine so it allows me to flash the rom using normal twrp and latest bootloader.
[Nexus 5 Original Android Development] myfluxi:
I just understood the bug exists but was never able to reproduce it. Do you know of a method to trigger a crash 100%?
[Nexus 5 Original Android Development] playitlouder:
Lay phone screen up, camera down on a table, let camera overhang.

Turn flashlight on from notifications area.

Turn screen off wait a few minutes and it will crash the camera.

If not repeat a few times. Or reboot.

Be shure you are not connected to a charger.

But it certainly does not happen every time it just happens from time to time, if you really need a flashlight especially.
[Nexus 5 Original Android Development] myfluxi:
OK, get me a logcat and the output of dmesg when it happens.
[Nexus 5 Original Android Development] GiusGrec:
Hi! This is my favourite rom (no bugs and exceptional battery life). I would just ask two things:

1) Is it normal that, in the latest nightly, placing the phone in airplane mode, you then need to re-enter the PIN (as if the SIM had been switched off)?

2) What is exactly the function "Active profiles for app" which is located in battery settings?
[Nexus 5 Original Android Development] Blind55:
>> You'll have to modify the updater script, I've modified mine so it allows me to flash the rom using normal twrp and latest bootloader. <<

Thanks, madsurgeon, for the info...although now it gives me problems with the checksumming...
[Nexus 5 Original Android Development] Annita:
Have an issue with build 12.1-20150823-NIGHTLY and it's basically that after EVERY phone call, the phone gets rebooted and asks for the PIN. It's quite painful... Does it happen to anyone else? Any solution for this issue?
[Nexus 5 Original Android Development] andrei1015:
I also have a lot of random reboots (reason why I disabled my PIN) and [MENTION=4152171]myfluxi[/MENTION] said, and I tend to believe him for some reason, that it's something about my phone/its software. He recommended I do a clean flash, which I have to admit I've been too lazy to do as of now. But I will do it as soon as I gather enough power of will.
[Nexus 5 Original Android Development] Annita:
Can't confirm or deny if it's due to a software issue, but haven't done any installations or soft upgrades latelly (since install of CyanogenMod last version) and it's happenning. Going back to a previous version can't break it or make it worse, right??

I also know and would like to do a clean flash, but quite busy this days and unfortunatelly not much time :(
[Nexus 5 Original Android Development] madsurgeon:
I suppose you'll have to learn how to modify a zip file without altering it's integrity. I do it on the fly with zarchiver. For PC, 7zip works well.
[Nexus 5 Original Android Development] myfluxi:
The point is, "I have crashes" is totally useless for me and everyone involved. Another point is, a wipe, even of system, cured over 50% of all our device's reported strange issues so I don't ask anyone to start fresh without restoring data and installing all that random crap from Play Store without a reason. I've been there, done that as well.

Your observation may point to an error documented in https://jira.cyanogenmod.org/browse/NIGHTLIES-1718 and two other logs I got ahold of (one of which is the OnePlus One, which is always a plus when it comes to fixing bugs). If this is true, we have to act quickly, cuz only a phone you can make calls with is a phone.

Reproduce the bug, grab a full logcat, post it here, thanks.

I tried to crash it for 2hs, nothing. It throttles to 1.2 GHz at some point but the torch just works (I guessed it may have been the thermal management kicking in, triggering fps slowdowns and ultimately closing the cam). I'm afraid to damage my dev phone so I have to stop here.

Get me full logcats or another phone without possible hardware defects.
[Nexus 5 Original Android Development] andrei1015:
^ and this is the easiest way to get proper logs as far as I've seen.

AndyLog
[Nexus 5 Original Android Development] Annita:
I went back to build 20150814 which I had before and was working perfectly fine and phone "is back in business" (back to normal). Can make phone calls and no soft reboot.

I totally understand about the fresh install and been doing it for a while, as I'm a ROM user since my first Galaxy S 4 years ago, and used and changed multiple ROMs (and phones).

Could be related to that error documented (I don't have Xposed installed, but if cyanogenmod uses it, that could be...) https://jira.cyanogenmod.org/browse/NIGHTLIES-1718 All I can confirm for now is that a change between nightly 20150814 and 20150823 causes the random soft reboots during/after calls (which in my case are not just randoms, but after

EVERY

call).
[Nexus 5 Original Android Development] Fihlvein:
Unhelpful comment really since I have no logs, but first time since ages I also experience random reboots during some activities, it's usually always when idling. Yesterday (I got 3 of em all requiring PIN code, a record for me!) got one while Endomondoing a cycling session, today I received a phone call and got one right when I was about to answer (but didn't touch anything yet). Just an observation, since somebody said incoming calls caused reboots, and I've never experienced it during active use before. Sorry myfluxi, next time I'll comment about reboots I'm armed with logs.
[Nexus 5 Original Android Development] 8ternity:
Hi,

I had two problems with my ROM, CM12.

When i press the power button, the screen shut OFF but the backlight are visible not closed. We see a small light (not happen on all tries, but once on 10).

It also happen when the telephone are under pocket, we finish a call and screen are shut off, but backlight aren't closed. (more often).

Can anyone help me with that please?

Thanks a lot! I really like this ROM. I want to keep it, but my battery goes to hell very fast (wont last a day) with theses bugs.

P.S. i've try with another ROM too "RESURECTION REMIX" based on the CM12 ROM was does the same.

Thanks.
[Nexus 5 Original Android Development] luca.giannatiempo:
i can say it is happening even with aosp version. since I had that 14/08 nightly it worked well, now with the 25/08 nightly I have some random reboots. before the 14/08 nightly I had one or two reboot in a month, now they are a couple per day..no exposed

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 5 Original Android Development] andprod:
Help Kernel

Hello guys, I have a problem I am using cm 12.1 'm trying to install the kernel blue spark but every time I install it not out of the Google screen, I do not know if it has anything to do over my nexus is Android 5.1.1 hammerheadcaf latest version of cm
[Nexus 5 Original Android Development] d1n0x:
Seriously? Come on. Please inform yourself before you post here.
[Nexus 5 Original Android Development] luca.giannatiempo:
as I know there are NOT compatible caf kernel..so this is the problem..

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 5 Original Android Development] fleischbanane:
Anyone else with Chrome constantly crashing with today's nightly?

Cleared data of Chrome and wiped cache and dalvik.

Want to know if it's an known bug before doing a clean flash.
[Nexus 5 Original Android Development] ssauger:
http://xdaforums.com/showpost.php?p=62514557&postcount=3669
[Nexus 5 Original Android Development] jclick555:
Hi just changed back over to cm from stock with xposed. I have updated bootloader and radio. All APN settings are correct but for the life of me I can't get data with Rogers and it was working fine before the switch. I have reloaded 2 times with the same result. I'm on latest nightly. Any suggestions would be greatly appreciated. Everything else is working great
[Nexus 5 Original Android Development] ryanmat:
It might be a long shot, but do you have "Data Connection" enabled from Settings -> Data Usage?
[Nexus 5 Original Android Development] jclick555:
Yeah that's enabled.
[Nexus 5 Original Android Development] ryanmat:
Is your IMEI number still there? If not then you may need to reflash your EFS. Here's a link to a guide with the Modems and EFS info: http://xdaforums.com/google-nexus-5/development/modem-nexus-5-flashable-modems-efs-t2514095
[Nexus 5 Original Android Development] jclick555:
The imei number is still there.
[Nexus 5 Original Android Development] Geo2160:
I have some strange mobile data issues since I installed this ROM (21/8 nightly). Pages load very slowly, even on 4g and facebook messenger doesn't work at all. It's stuck on "connecting". Speedtest.net reports <0.5mbps even in areas with good 4g reception. And no, my data plan hasn't ran out.

Since I've had to update the bootloader when I installed CM12.1, I also updated the modem. I thought that was the issue. But I've tried both the latest modem (2.0.50.2.26) and the modem that I was using before (2.0.50.2.25) to no avail.
[Nexus 5 Original Android Development] dannyella:
After my 3rd random reboot today. All happened while I was listening to music.

8/25 nightly.
[Nexus 5 Original Android Development] GiusGrec:
I can confirm that the latest nightlies have some bugs
[Nexus 5 Original Android Development] andrei1015:
This might be the best statement on XDA. Ever.
[Nexus 5 Original Android Development] reaperofwaywardsouls:
I too, can confirm that the latest nightlies seem to be experimental in nature and can cause unforseen glitches to occur intermittently, but sometimes not.

I wish I could get what I paid for this refunded to me.

:beer:
[Nexus 5 Original Android Development] GiusGrec:
Yes, I agree with you, from the developer point of view, my previous comment does not mean anything.

But I have the same impressions of [MENTION=4157910]reaperofwaywardsouls[/MENTION] : there aren't systemic problems, so they're aren't "reproducible" to make a log
[Nexus 5 Original Android Development] :
[MENTION=6155426]GiusGrec[/MENTION]: Did you even feel the irony in [MENTION=4157910]reaperofwaywardsouls[/MENTION] post? :D

*cough* "nightly" *cough*
[Nexus 5 Original Android Development] GiusGrec:
Ops :D Blame of my poor understanding of english language
[Nexus 5 Original Android Development] vercety974:
Do you suggest to make a clean install or dirty flash is quite improved to avoid bugs ?

Envoyé de mon Nexus 5 CAF en utilisant Tapatalk
[Nexus 5 Original Android Development] ryanmat:
This is straight from [MENTION=4152171]myfluxi[/MENTION] "Another point is, a wipe, even of system, cured over 50% of all our device's reported strange issues"

Clean flash is probably the best way to go to avoid any strange bugs. But, some people dirty flash everything and never have issues, as always your mileage may vary...
[Nexus 5 Original Android Development] :
I think only wiping /system, /cache and /dalvik can still be considered as 'dirty-flash' since /data and internal storage stays untouched... I'm using this procedure over months now and never had issues - except the ones that actually were system-related (like the Chrome issue in yesterdays nightly). It's fixed with todays nightly and everything's fine :)
[Nexus 5 Original Android Development] vercety974:
Does the cm-updater wipe system and cache when updating from a nightly to another ?

Envoyé de mon Nexus 5 CAF en utilisant Tapatalk
[Nexus 5 Original Android Development] Annita:
Updated to last nightly (cm-12.1-20150828-NIGHTLY-hammerheadcaf.zip) and still the same issue with Android restarting after every call!!!! Quite anoying!!!! Tried to go back to nightly 20150814 and constant reboots due to 'process kill phone', so have to stick with 20150828 (with the reboots after the calls, of random reboots) until have time to do a clean install and full clean installation.... :( :crying:

Not complaining (well, a bit ;) ) as I knew what I was into when installing ROMs and you guys doing a great job with CyanogenMod for Nexus 5 CAF, but just letting you guys now in case you can fix it...

Now I have a phone that does not work like a phone LOL
[Nexus 5 Original Android Development] vercety974:
No reboot after call on the 08.29 nightly for me.

Envoyé de mon Nexus 5 CAF en utilisant Tapatalk
[Nexus 5 Original Android Development] lcrponte:
You're the only one with that problem so... It's up to you to get past it with a clean flash.
[Nexus 5 Original Android Development] davewilliam:
I had several instances of reboots while starting to listen to music/audio. This morning I flashed to the 8/28 nightly and haven't had a problem since.
[Nexus 5 Original Android Development] razorloves:
No. Nothing is wiped. It just flashes it.
[Nexus 5 Original Android Development] funkyslap:
.... well, where are logcat and last_kmsg? If you want to help dev fixing bugs just do it in the proper way.

Inviato dal mio Nexus 5 CAF utilizzando Tapatalk
[Nexus 5 Original Android Development] Annita:
Well, that is good (perfect) news as I'm planning on doing a clean flash today/tomorrow and as I seem to be the only one, hope that fixes everything!!! If it does, happy days then!!! :o :)

Need to learn how to do them, but of course will send them if continues :p ;) Wanna help devs to fix it!
[Nexus 5 Original Android Development] kenshin33:
yes it doesn wipe system. But before doing so it looks in /sysyem/addon.d fot backup/restore scripts.

the cache in the cache partition is invalidated it will be rebuilt (which happens alomost everytime : android is updating)
[Nexus 5 Original Android Development] razorloves:
you're mistaken.

he asked if the cmupdater does any wiping.

the cmupdater app does not do any of that.
[Nexus 5 Original Android Development] kenshin33:
pedant much?

"when updating" means the phone reboots into recovery and executes the updater-script found in the zip. That wipes the system partition

1st command in system.transfer.list

erase 2,0,262144
[code]
meaning erase -- via a call to BLKDISCARD ioctl-- block 0 through 262144 (of 4096 bytes each, 1Gb of data, which is about around the size of /system partition) --cf: https://android.googlesource.com/platform/bootable/recovery/+/android-5.1.1_r1/updater/blockimg.c:717--.
Bu yeas you're right, the updater script mealry initiates the update procedure if the user asks for it (one way or the other)
[Nexus 5 Original Android Development] dannyella:
Unfortunately, still having the reboots. It seems like it's not specific to nexus5. Been seeing similar reports on G+ lately.
[Nexus 5 Original Android Development] myfluxi:
This happens all over CM atm and as a user there is nothing you can do about it (except for using an older build).
[Nexus 5 Original Android Development] archish:
Was about to report this issue as i had multiple reboots today. Do you need a log cat?
[Nexus 5 Original Android Development] ryanmat:
Not sure if your data issue was fixed, but I happened to see this commit for Rogers LTE, might be helpful to your case. Hopefully, it will be included in the next nightly: http://review.cyanogenmod.org/#/c/107809/
[Nexus 5 Original Android Development] archish:
can anyone please upload august 1st week build? I didn't find any latest nightly to be stable.

Thanks.
[Nexus 5 Original Android Development] jclick555:
That looks exactly like the issue. I did however find a fix by just removing all APN'S6 in the list except for the ltemobile APN and make sure the recommended setting is not LTE global but LTE recommended. Everything now works like a charm and a permanent fix on the way. Thanks for the followup.
[Nexus 5 Original Android Development] andrei1015:
We have a "release" build which was marked as "Good to go" by our [MENTION=4152171]myfluxi[/MENTION]. Thanks!

https://download.cyanogenmod.org/ge...0150901-SNAPSHOT-YOG4PAO238-hammerheadcaf.zip

EDIT: Flashed over last nightly and phone iz kill. Trying to revive it.
[Nexus 5 Original Android Development] myfluxi:
It might not even boot because our build system only took the AOSP kernel tree. Whatever, it wouldn't have been "stable" in the true meaning of the word anyway.

Just forget about it or copy the boot.img file of a current nightly into the install ZIP.
[Nexus 5 Original Android Development] andrei1015:
Would've been useful to know before lol. Meh, I'll get it working even if I'm at work.

EDIT: problem solved. If anyone does the same stupid **** I did, boot into bootloader (power and volume down for 8 seconds) and go into go to recovery. Once in recovery, you should be able to use push to /sdcard to upload an older build (if you've already deleted it like I did).
[Nexus 5 Original Android Development] jdprocks:
So when will caf get its working snapshot??
[Nexus 5 Original Android Development] myfluxi:
a) What do you expect of a snapshot? Just another flash as if there wasn't a new one every day?

b) I don't like the demanding tone. Stuff like that always makes me want to answer "never".
[Nexus 5 Original Android Development] jdprocks:
Sorry if i offended u in anyway i really appreciate all the hard work u r doin

Was just asking about if there will be an another snapshot of this or will continue with the nightlies
[Nexus 5 Original Android Development] one7dchevy:
Had a unexpected reboot (829 nightly) while updating app via play store. Last_kmsg and logcat attached, hope they help.

Also last night had a reboot when receiving a call, didn't pull logs from that one, but will next time it happens.
[Nexus 5 Original Android Development] Annita:
Yesterday (finally) I was able to do a clean install of Nightly 20180531. Mobile works better than before and now it's not rebooting after every phone call, but random reboots (3 or 4 today, and 1 of them in the middle of a phone call, after 15mins talking approx)....

In order to help the devs, how do I log this in the phone to send it over? I saw one7dchevy logs, but might be also good to have more... :)
[Nexus 5 Original Android Development] one7dchevy:
I used logcat extreme from the play store to pull the logcat. Then used a file explorer to copy the last kmsg from /proc
[Nexus 5 Original Android Development] myfluxi:
I understand that users have a desire for "stable" CM builds in the hope for - *gasp* - more stabilty. This hower is an illusion, there won't be a stable 12.1 release. By the time the worst bugs are killed, we'll have introduced more bugs and Marshmellow will be around. Which means, everybody will start working on M.

The Snapshot build will have less new and more old bugs. I can say for hammerhead and hammerheadcaf that our device-specific bugs are minimal (e.g. slight distortions on the speaker with a handful of sucky notification sounds or very rare occasions where the backlight will stay on after a message on Active Display). To comments on these two, the first can worked around be chosing a different notification tone or by tuning volume a tad down. The latter is a race condition in our/AOSPs/CAFs framework and an easy fix would be to switch off Ambient Display, personally I had that bug twice in almost a year...

CM is moving fast, damn fast. But we are a community based project, we are not a big OEM. Yet it appears users confuse us sometimes. You expect a perfect system and full support. We don't have that. In my opinion, we have great CM devices (hh and hhcaf), some of the best out there function-wise. Even better than the commercial devices from .inc and the first thing that happened when I tried AOSP-L for a few days was a panic after the modem crashed.

The build system does not understand the branching of our kernel repo (neither does cmx-log). I'm not sure if I can get it fixed and I don't see why tbh, for the reasons mentioned above. The monthly concept of cm-11 wasn't working as well. Keep track of a nightly that works for you. Don't always install the latest Gapps instead enjoy a working build, don't install each and every crappy app the play store (the free ones that don't look crappy are usually those that suck all of your personal data...). And live happier - when we finally fixed the soft-reboots and profiles stuff.
[Nexus 5 Original Android Development] ChongoDroid:
Crushing bugs is half the fun, what are you gonna live forever? If your phone didn't have a conniption fit every once in a while, life would be boring. Its the reason we flash nightlies, it's the reason we have chrome beta/dev instead of the regular version.

Bleeding edge for life

:)

---------- Post added at 04:09 AM ---------- Previous post was at 04:01 AM ----------

So, so true. I've been with Android since the get and I can honestly say after you mature as a user, the concept of "less is more" is more and more apparent. From apps, usage, hell even theming I find myself becoming more minimalist.
[Nexus 5 Original Android Development] NOWE:
com.android.phone has stopped

I had to delete these folders via adb shell to solve the issue "com.android.phone has stopped".

I don't know exactly which folder does the trick.

I'm quite sure one of them would be enough.
[Nexus 5 Original Android Development] one7dchevy:
Reboot when receiving a call.. Hopefully these are helping. Will try a clean flash when I get back home from traveling..
[Nexus 5 Original Android Development] ryanmat:
This is most likely a database issue, I've had it in the past. A clean flash works, or deleting the data as you did above. Just be sure to backup all of your messages, since they will be deleted by doing this.
[Nexus 5 Original Android Development] archish:
On which nightly?
[Nexus 5 Original Android Development] one7dchevy:
Guess that will help, its on the 829 nightly
[Nexus 5 Original Android Development] archish:
Try 2nd Sep one, no reboot so far.
[Nexus 5 Original Android Development] -SmOgER:
Ok, tried a few ROMs out there and this one seems to be the one to go with personally for me. Chroma follows closely behind, yet this one is somewhat faster when it comes to browsing (scrolling) and 3D performance. Impressions for 08.31 nightly.
[Nexus 5 Original Android Development] one7dchevy:
Awesome will update soon..
[Nexus 5 Original Android Development] adeptustech:
Never ask for eta of release. ?
[Nexus 5 Original Android Development] xdaboobs:
Hmm something funky is up with my swiftkey after flashing latest version! But found a way to fix it.

http://imgur.com/8HksaNS

1) it fixes when i tilt phone to letterbox then phone back to upright. but have to do this every time the keyboard pops up.

2) i dirty flashed

3) before flashing my screen density was set to 400dpi

so, i went to look at screen setting and noticed it is set to 480dpi (even tho everything actually looks like 400dpi, exactly same size as it was before flashing). i set it back to 400dpi and all is good now :good:

The other thing i find is there is a tiny bit of keyboard lag with both swiftkey and the stock keyboard between input/tapping and when it actually shows up on screen. anyone else get this? i can say this is not exclusive to the 05/09 nightly but goes back to some time i can't remember. maybe it's just my issue but the lag is tiny so can live with it, don't care. however, it seems like it is noticeable.
[Nexus 5 Original Android Development] jixbo:
Why did the hammerheadcaf snapshot is not available anymore?

Was it bad?
[Nexus 5 Original Android Development] andrei1015:
yes, it had a nasty bootloop. From what I understood, this was because all the "stable" builds were ... built using the AOSP code, and we need CAF.
[Nexus 5 Original Android Development] californicated:
Although I'm a really picky and performance-driven person, I don't notice any lag with stock keyboard on my phone. Swiftkey is always some kind of laggy. That's the reason why I'm not using it anymore ;)
[Nexus 5 Original Android Development] Bloch_hd2:
I have the same issue as u show on the picture, but with touch pal keyboard, in a month or two. no big problem though, I'm just reporting :)
[Nexus 5 Original Android Development] Daniel 123:
Anyone having issues with applocks on latest nightly.

Sent from my Nexus 5 CAF
[Nexus 5 Original Android Development] d1n0x:
Are you a wizard?
[Nexus 5 Original Android Development] archish:
Nothing on 2nd August nightly