yashsingh1/xdaforums huggingface dataset:
[Moto G 4G Android Development] ncc1701a:
Bug conditions for missed call light notification are more complicated:

- At first set normal (ring mode) and reboot the device. It is necessary for occurring of this issue;

- Make call from another device. Light notification does not shows missed calls.

- Then set device to silent mode, light notification shows missed calls properly.

- Then set device to ring mode again, light notification shows missed calls properly...

So, after reboot the bug will occur.
[Moto G 4G Android Development] IronTechmonkey:
Same here. After silent mode then missed call LED OK (even after leaving silent mode). After reboot, repeat.
[Moto G 4G Android Development] 239:
I could not reproduce it and was wondering until I remembered that I disabled some system apps like Calendar, Contacts, ..., Phone and replaced them with their Google counterparts from Play Store.

I guess it's the reason why the LED notification works after restart.

Tested again with stock Phone app and can also confirm the bug.
[Moto G 4G Android Development] damian3581:
Android oreo?
[Moto G 4G Android Development] IronTechmonkey:
[MENTION=5295657]ncc1701a[/MENTION], By the time I got to adding notes to the jira ticket, a fix was already committed: From a note posted by Gabriele M (who took a few extra steps for us) in the ticket: there is a link to this commit: https://review.lineageos.org/#/c/197446/. Thanks again for creating the ticket. As the commit works through the process it should appear in the Peregrine (https://www.cmxlog.com/14.1/peregrine) or general (https://www.cmxlog.com/14.1) change-log and then in the next weekly build. It might make it into this week's Peregrine build (and I'll be trailing along to test it in next week's Athene build).
[Moto G 4G Android Development] ncc1701a:
Thanks for information, testing and participation for debugging, IronTechmonkey.

Thanks to Gabriele M, I've get some experience for getting full logcat.

Perhaps you are right. According to this commit, problem has been found for android_frameworks_base. Maybe Google counterpart for Phone.app ignore (or override) global flag, which allow light notification. Thanks for testing too!

For this moment I investigate for another bug with Wi-Fi:

After some time (hours or even days), Wi-Fi does not auto-connect to saved network (after lost Wi-Fi signal, auto-connection does not work too, that is too sad: we can not watch for Wi-Fi state every time).

But it still possible to connect to saved network manually (from settings).

My router (TP-Link TL-MR3220 v2 ) has firmware: OpenWrt Barrier Breaker 14.07

I tried:

- to change SSID and password for Wi-Fi AP;

- to change security settings for Wi-Fi AP (open/wep/wpa);

- to clear all saved networks and connect again.

Nothing to help, but after reboot the device, auto-connection work properly for some time. There is familiar issue, but not the same.

For this moment. I've flashed back the clean lineage-14.1-20171124-nightly + addonsu-14.1 without any additional applications (who knows, maybe Samba or call blocker (both SU permitted), which I used, are causes of this bug). If this issue occur once again, I'll grab the logcat and create a new ticked at JIRA. But the steps for reproduce the bug are still unclear...
[Moto G 4G Android Development] cspiby:
Started getting more random reboots, this time due to a kernel panic, SD card is formatted aas portable and hadn't been an issue any longer.

Is the recent update causing it?
[Moto G 4G Android Development] galoneta:
Hi.

Reporting about lastest build from nov 24.

Clock from status bar sometimes does not sync with proper time, even not sync with other clocks (lock screen and widgets) in the same device: it just stops!

Clocks from lock screen and clocks in the desktop widgets are always sync correctly!

What app for cpu control \ under \ over clock have you guys used? SetCPU is not running fine! Old builds can run but with limited functions compared with actual app available!

Thanks
[Moto G 4G Android Development] IronTechmonkey:
None. This thread is for testing LOS ROM, which by definition means without custom kernels or CPU settings changes such as would be made with SetCPU. I would suggest starting with a SetCPU thread and then if you can establish this is actually an LOS issue, submit a bug report including description of how to reproduce issue in clean flashed ROM with no 3rd party modifications, and include a log.
[Moto G 4G Android Development] cspiby:
Getting the same behaviour with wireless on the last 2 builds.
[Moto G 4G Android Development] ncc1701a:
So, I've created new JIRA ticked for Wi-Fi auto-connect bug:

https://jira.lineageos.org/browse/BUGBASH-1263

Main reason for this bug occurrence is changed SELinux to permissive state.

And some news for another minor bug: according to this commit, for the next nightly build will be possible to disable "Blocked Numbers Storage" application safely. It might be useful if user have another call-filter app for improvement hung-up lag and for avoiding conflict between two apps with the same function.
[Moto G 4G Android Development] cspiby:
Mine is set to enforcing and I'm having issues with auto reconnect.

I usually have to toggle WiFi off and back on for it to work correctly again.
[Moto G 4G Android Development] ncc1701a:
Perhaps you have described another issue. Sorry, that sometimes I understand sentences too directly: after occurring the issue, in your case, you just have to toggle Wi-Fi state by pressing to Wi-Fi icon in the status bar (correct me, if i wrong, but with more details).

I could not reproduce your bug (in my mind). I've tested my peregrine for two cases:

- reboot Wi-Fi router, when my smartphone in sleep mode (Wi-Fi sleep policy (I set: "Keep Wi-Fi on during sleep: always") can change the behavior);

- reboot Wi-Fi router after wake up the device.

In my case, after occurring the issue, I have to select the saved network (even if there is only one saved Wi-FI AP) through settings -> Wi-Fi (or by long-pressing Wi-Fi icon in the status bar). Pressing to Wi-Fi icon in the status bar (after occurring the issue) does not change anything.
[Moto G 4G Android Development] 239:
No Wi-Fi connection issues here (SELinux enforcing).

Updated TWRP to 3.2.0 and installed 20171201 but SD card (internal storage) was ejected after a few minutes on every reboot.

Restored backup (20171124) for now but will try it again and look into the logs. Anyone else with similar problems?

Edit:

Second attempt, same result. Restored backup again, card works fine. Don't know if it's a hardware or software issue.

Will open a ticket and append log if there are similar reports.
[Moto G 4G Android Development] cspiby:
Still getting reboots due to kernel panics, any ideas?
[Moto G 4G Android Development] 239:
The logs aren't really helpful, I found no crashes/errors/exceptions. 20171124 is stable on my device so I guess it has to be something else.

If the reboots occur quite often I would start clean (without root) again for a day and see after which successive change (settings/apps) it gets unstable.

Restore backup afterwards and try to reproduce/eliminate it.
[Moto G 4G Android Development] cspiby:
I have now completely wiped the phone and installed the latest nightly with the micro gapps, shall see how it goes.
[Moto G 4G Android Development] 239:
Additionally you could let MatLog record the main/radio/events buffers to file (every 20-50 lines) and if you get lucky find out what's going on BEFORE it crashes.
[Moto G 4G Android Development] sevenrock:
Google released a new revision for Android 7.1.2:

https://android.googlesource.com/platform/manifest/+/refs/heads/android-7.1.2_r36
[Moto G 4G Android Development] ncc1701a:
One more question: which stock ROM did you have before LOS 14 has been flashed?

Some components (at least radio firmware) depend on previous stock ROM.

I prefer to have last radio firmware version (you can download it from this thread and flash through TWRP or fastboot).
[Moto G 4G Android Development] cspiby:
I had the latest stock ROM.
[Moto G 4G Android Development] mrLoma:
Does anyone use trusted face smart lock. It used to work. I tried using it on the last LOS, but the initialisation does not seem to get access to the camera.

Settings>smart lock>smart lock>trusted face>improve face matching...

Does this work for any one else (on the latest build)?
[Moto G 4G Android Development] IronTechmonkey:
FWIW, FaceLock is not present on devices where I use open gapps Pico. I'm not sure if it is present in the raw ROM and then removed by the Pico package or if it is not present in the raw ROM but then added by larger gapps packages.

In any event, keep an eye out for factors occurring between gapps and the ROM. Also, for what this is worth I've seen two reports this week of camera initialization issues which bear a vague similarity to your issue.

[EDIT] Links to previously mentioned camera issues from Athene thread:

https://xdaforums.com/moto-g4-plus/development/rom-cyanogenmod-14-1-t3522101/post74740170

https://xdaforums.com/moto-g4-plus/development/rom-cyanogenmod-14-1-t3522101/post74750652
[Moto G 4G Android Development] mrLoma:
Good point, I'll try flashing gapps again. Don't think I did that after the last LOS update.

Update:

Just installed the stock gapps. Didn't fix it.?
[Moto G 4G Android Development] cspiby:
Updated my radio and it seems to have improved things, thanks.
[Moto G 4G Android Development] ncc1701a:
That is odd... Technically, radio firmware is just part of original stock ROM (if you flashed the latest stock ROM, you already have the latest radio firmware). Only test for a long time will show the result.

P.S. Sometimes, the repacked ROM (for flashing with TWRP) does not include any additional components, except system folder and boot image.

And about the problem with Wi-Fi auto-connection: I sprinkle my head with ashes.

After uninstalling Samba file sharing (SU permitted) and Clock Sync (SU permitted to set RTC), there are was not any issues with Wi-Fi (UpTime is more than 4 days).

Sometimes, an obsolete app with SU privilege is the worst evil for the system stability...
[Moto G 4G Android Development] IronTechmonkey:
True but, at certain points in the progression of devices & ROMs, when a custom ROM is a later version of Android than the last stock image was, it is not uncommon to have to flash other components like radio. If I'm understanding the Peregrine landscape correctly, some Peregrine devices have required the radio flashed and others have not. When I tried to flash the radio when first flashing CM/LOS on Peregrine there was an error and it seemed as if the flash did not complete but everything still worked okay. Going farther back into the time machine for another example: There was a change to the bootloader during the transition from Jelly Bean to KitKat which had to be accounted for in ROMs of later Android version than last stock image.
[Moto G 4G Android Development] macmobile:
Sudden Reboot occurred here also.
[Moto G 4G Android Development] dom001:
Hello

I installed lineage-14.1-20171208-nightly-peregrine-signed (with full-wipe before). Everything seems to work fine, except sd card access: I cannot write to sd card. I tested 3 different cards with fat32, exfat, ext2. I can see and open all the files, but not delete/create/modify files and directories.

I also tried fresh formated cards (without any .android_secure directory) without luck. Anymore hints?

Thanks in advance,

Dominik

BTW: With root-filemanager I have write-access, but I need as normal user. And I don't want to use sd cards as internal memory, because I'm using several cards. I never used lineage os before!
[Moto G 4G Android Development] cspiby:
48 hours uptime now and auto reconnect is behaving itself since flashing the radio :)
[Moto G 4G Android Development] ncc1701a:
Agree, that in general, it is not necessary to flash other components like radio.

Actually, I do not know: there are too many nuances. Perhaps, something depends on flashing method.

For clean flashing stock original (untouched) ROM for peregrine, I've used fastboot script for flashing process, because it fully controllable and there are not any side effect (except roll-backing cases). According to script, radio FW flashed every time:

fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn

But most repacked/optimized ROM (from this thread) for flashing through custom recovery, does not have radio FW, but there are separated archives with radio FW. This method if fully controllable too. But sometimes after flashing only custom ROM, some side issues may occur, for example, with GPS (to fix it required only "erase modemst" fastboot commands).
[Moto G 4G Android Development] cspiby:
I had to use fastboot method as TWRP errored.
[Moto G 4G Android Development] 239:
Can you test if 20171124 behaves differently?
[Moto G 4G Android Development] ncc1701a:
Oops, I remembered something: after flashing twrp-3.2.0-0-peregrine.img, I could not restore the backup, which has been created by twrp-3.2.0-0: restoring process has froze, no errors messages, only power off has helped. But I could restore the previous backup, which has been created by twrp-3.1.1-0. After that I flashed back twrp-3.1.1-0.

Sorry for disturbing, did you have the similar issues?

---------- Post added at 01:16 PM ---------- Previous post was at 12:45 PM ----------

239, wait: do not wipe data.

Some confirmation of this TWRP bug for other devices:

https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1101

239, I hope, that my request did not harm to your device. Perhaps, it would be better for you to create additional backup by Titanium Backup before any backup/restore operation with twrp-3.2.0. Once again, I apologized for disturbing.

To all: do not update TWRP to 3.2.0-0 version. Instead of that, use 3.1.1-0.
[Moto G 4G Android Development] IronTechmonkey:
Thanks. There have been report in other threads about this as well.

---------- Post added at 06:36 AM ---------- Previous post was at 06:29 AM ----------

D'oh! A correction. I was misremembering: It was the Peregrine bootloader update (which fixed a screen flicker that occured till first screen off/on cycle after each boot) which in turn required (at least in some instances) the radio update. https://xdaforums.com/moto-g/general/falcon-bootloader-upgrader-tool-t3093793.
[Moto G 4G Android Development] 239:
I had the same problem while restoring with 3.2.0 but it finally worked for me after I tried several times. I guess the workaround was probably to create a minimal backup first or clearing "mount system as read only".

Restored backup twice successfully after trying the December builds so I kept the new TWRP version. I was confused by the SD card issue and forgot the restore bug. Thanks for reporting/confirming it!
[Moto G 4G Android Development] dom001:
Tested, unfortunately no different behavior :(

But with filemanager from lineage os I can write to fat32+exfat sdcard, but not to my big 64gb ext2 card!

With Ghost Commander I cannot write to any sd card. Also the 'osmand' app cannot create its folders and files to download maps :(

Formerly I used CM12.1, where everything worked without problems.
[Moto G 4G Android Development] 239:
Thanks for checking!

Did you try to format the cards from Storage settings (format as internal then portable again)?

Are you sure that these apps have storage permissions? You probably need to force stop and restart them.
[Moto G 4G Android Development] ncc1701a:
Sorry for off-topic. According to my memory, Google restricted external SD-Card access for Android >= 6.

Perhaps, you need app like that:

https://xdaforums.com/xposed/modules/xposed-marshmallow-sd-fix-write-t3403263
[Moto G 4G Android Development] dom001:
The apps have already storage permissions (Settings -> Apps -> Ghost Commander -> Permissions -> Storage).

I also tried to format a small 2GB card as internal and then as portable again. I still cannot create folders or copy files to it with ghost commander.

With linage os filemanger 'Files' the sdcard is named "sdcard1". With ghost commander or osmand. External Card is names /storage/88C2-161C/. My ext2 sd card has a much longer cryptical name (UUID?). At CM12.1 every card were named '/storage/sdcard1'

It's a pitty :(. Seems I have to go back to CM12.1, because I really need portable sd support

---------- Post added at 03:45 PM ---------- Previous post was at 03:07 PM ----------

Thank you for the hint. I tried out this "Marhmallow SD fix" app. I enabled it for ghost commander and rebooted. But still I cannot write to sd :(

I think an external OTG Cardreader also won't help?
[Moto G 4G Android Development] 239:
I don't think that it's a portable/internal storage issue.

What about other file managers like FX or Amaze? Same problem? At least GC seems to have issues with SAF migration:

https://sourceforge.net/p/ghostcommander/bugs/42/

Did you restore app data from a backup? (http://osmand.net/help/faq.html#change_maps_dir)

SD cards up to 32 GB are supported on this device.
[Moto G 4G Android Development] dom001:
Sorry, but I won't use other apps. I installed a fresh f-droid and took the latest ghost commander from it.

My osmand data (maps, tracks, etc) are on my osmand sd card in osmand/ folder. I try to change map dir and get an error "maps cannot be created in specified directory". It doesn't matter, if I choose a new dir or my old existing osmand dir. I have many more apps and sd cards. And this device definitely support 64gb cards against specification! I'm using a 64gb samsung micro sdxc with ext2 fs and large wikipedia zim-files for years without problems! And I could read that card with lineage os too, but unfortunately not write. :(
[Moto G 4G Android Development] Rob...:
I use mixplorer and everything works. Last lineage with dirtyflash.
[Moto G 4G Android Development] IronTechmonkey:
FWIW, that's a possible symptom of impending drive corruption (which may play out differently depending on the file system(s)). I once saw those symptoms a few days or weeks before Sandisk's native data protection, detecting impending failure, wrote a dirty-bit to the beginning of the drive. The dirty-bit prevented anything from writing to the drive, which meant that CM/LOS could not access the drive (except to detect insertion) but data could be recovered via USB on a computer. Of course this may not be the case for you but it might be worth doing some diagnostics on the drive. Also, as this does not seem to be an LOS ROM issue we might be getting a bit off topic.

[EDIT] Rereading your previous report, I've used 64GB SD card (containing one partition created and formatted as fat32 in GParted) as portable storage successfully in LOS 14.1. That being said, another perhaps more likely possibility is that something in the drive's history of partitioning and formatting has left it outside of what LOS expects. Again veering OT, but if you think that is a bug in the ROM then file a report at LOS Jira.
[Moto G 4G Android Development] Rob...:
According to your description, Android Secure should be at fault. Had the same on my device. The folder 'Android Secure' was not there. The folder was not displayed on any Android device, first on the PC. Folder deleted and good it was.
[Moto G 4G Android Development] IronTechmonkey:
Logs? (not just a hint, but an actual expectation ;))

I wasn't speaking to .android_secure, which I know well and which was obviously not a factor in my case (scratching head - I clearly described a dirty-bit created by Sandisk's built-in protection). Nor would it have been a factor in your tests on freshly formatted SDs. If it was, a factor then you were not using clean SD.

Apart from providing a bug report, you could explore other methods of partitioning and formatting, as well as confirming the step by step details of your clean flash process (and perhaps tweak that process).

Also, it stands to reason that the clean flash and clean SD with most common formatting would have to coincide in order to make the testing results viable.
[Moto G 4G Android Development] dom001:
Firstly thanks for your support guys! I gave up :(

With some special apps like on-board filemanager "Files" or surely your other named filemanager apps, you can indeed write to portable storage. With my important app "osmand", I can write to [sd-root]/android/data/net.osmand.plus/files/ folder, but not to [sd-root]/osmand anymore.

With termux (a mighty terminal emulation app), I cannot even list files on sd card as user anymore. I can change the directory "cd /storage/88C2-161C" and show it with "pwd", but a simple "ls" says "ls: can't open '.': Permission denied".

Logs: I know to less how to make logs: Kernel buffer with "dmesg" shows nothing, If I got a "permission denied".

Maybe it's an android and not a lineage os issue. Sorry for the offtopic. Whatever I cannot work with such a restricted system.

One last question: I wonder, what data will be stored to sd-card, if I format it as inernal. What happend with this data, when my phone got defective or I just want to flash a new image? Can I read data from the internal storage sd anymore (especially on pc)?

Thank you very much and excuse my bad english,

Dominik
[Moto G 4G Android Development] IronTechmonkey:
Not just off topic but extremely off topic for a Peregrine LOS 14.1 thread. There are many other threads where such a discussions would be appropriate.

[EDIT] Just to add that I did not mean that dismissively. I (and most likely others) am curious about the issue and scenario you've described, but this isn't the place to work through it. If you find and comment in more appopriate thread please do link to it here and some of us might jump in.
[Moto G 4G Android Development] cspiby:
Gutted, few days of flawless operation and I've just had another reboot.
[Moto G 4G Android Development] 239:
TWRP 3.2.1 available:

* minui fixes (cryptomilk)

* Better android-8.0 compatibility in ROM trees (Dees_Troy)

* Fix missing library in android-8.0 (nkk71)

* Fix inconsistent SDCard naming (DevUt)

* Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot (jlask)

The last one probably fixes the restore freezing.
[Moto G 4G Android Development] galoneta:
About clock sync in LOS 14.1

Hi. Report about same problem reported here: https://xdaforums.com/showpost.php?p=74691360&postcount=1087.

Latest build from dec 08 still has sync problems in the status bar clock ONLY! The other clocks from widgets and from the lock screen have good sync with real time, see the screens. Time from status bar sync again only when carrier signal is present, but other clocks are always sync!

CM 13 was always with good sync. Is this a bug ? Think so.

Thanks.
[Moto G 4G Android Development] 239:
Updated to latest nightly but SD card got removed again after a few minutes on startup.

Restored backups and and tried something different many times, was about to give up and go back to the November build but the last attempt turned out successful.

It seems that NOT wiping Dalvik/Cache after flashing LOS/GApps makes the difference. It's strange since I updated exactly the same way many times this year without having any issues.

Does anyone know why this can cause trouble? I always wiped caches while updating on different devices but now I'm not sure if it's the right thing.

(TWRP backup/restore worked for me again.)