yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] :
That's what I ment indeed. Thought about a combi of flip cover handling and dialogs myself where I had put dialogs and notifications under the same chapter.

You are probably right those are different.

Will do some extra testing tomorrow to see if I can nail down the combi which is giving this as a result.
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
I'm having the same issue since the juni LOS 17.1 builds

I've added some screenshots from what is missing.

I just get the notification in the status bar, from there I can click it and then the dialog for snooze and turn off is appearing.

But before, this screen came always.

And it doesn't matter if the screen is on or off and how long the phone rested in standby (set the alarm for this screens to 1 min later and it also didnt pop up)

edit: I have a second op3t with a los 17.1 build from befor this issue.

I'll make some logcats from both, maybe we can find any differences..

For me it looks like the clock app isn't allow to show the activity over the current app (but in settings the clock app doesn't exist for the special permission "overlay over other apps")

edit2: I added the 2 logcats

I'll also try to find differences..

I don't see the activity starting in the log with the issue, but in the log without issue it's there

ActivityTaskManager: START u0 {act=fullscreen_activity dat=content://com.android.deskclock/instances/1 flg=0x10040000 cmp=com.android.deskclock/.alarms.AlarmActivity} from uid 10116

the logcat without issue is from 20200423, the one with issue from 20200602
[OnePlus 3 & 3T Cross Device Development] :
I only have my phone here, so a little hard checking... though I noticed the line "AlarmActivity: Displaying alarm " in the log of the working phone and the line "AlarmManager: Unrecognized alarm listener" in the log of phone with issue. That's the same line I also see in my log though no idea if it means something...
[OnePlus 3 & 3T Cross Device Development] srb2020:
Sim Switching.

I'm not sure why, but this really appears to be an "elephant in the room issue" - I've searched hi and lo over the last few weeks and across every forum I can think of, lots of people are asking about this, but nobody appears to have a answer. Why has the ability to switch off a SIM gone missing ? I accept a lot of people here are experimenting and the One Plus 3 is not going to be their "daily driver" - but for me it is and this is a make or break issue. I have gone back to 16 because I really don't want to have to carry a work phone and my own phone around with me. If it is now a feature of Android 10 based Lineage that you simply can't switch a 2nd SIM off, fair enough, that's the way it is, but could someone please give a definite answer?
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
but this message with the alarm listener is also in the log without issue (line 20)

in the working logcat, there are e.g. more messages to the Activity

06-07 16:02:00.305 1225 8944 W ActivityTaskManager: Request to remove task ignored for non-existent task 7
06-07 16:02:00.308 9234 9234 W ActivityThread: handleWindowVisibility: no activity for token android.os.BinderProxy@4f6783a

I don't see these in the failing log.

But there is anothter message, from the DigitalWidgetProvider

06-07 15:58:00.225 21396 21396 I DigitalWidgetProvider: onReceive: Intent { act=android.app.action.NEXT_ALARM_CLOCK_CHANGED flg=0x21000010 cmp=com.android.deskclock/com.android.alarmclock.DigitalAppWidgetProvider }

But I also know too little about the system for interpreting things right.

And the second bad thing is that I cannot locate any change made between the 0429 and 0602 build that could cause this issue.

Edit:

DeskClock was brought to API Level 29 with some changes, I'll try to use the apk from the working build in the nonworking build to say if the Deskclock App itself is causing it or sth with media notifications etc.

https://review.lineageos.org/c/LineageOS/android_packages_apps_DeskClock/+/276041/

https://review.lineageos.org/c/LineageOS/android_packages_apps_DeskClock/+/276042/

https://review.lineageos.org/c/LineageOS/android_packages_apps_DeskClock/+/276043/
[OnePlus 3 & 3T Cross Device Development] :
In deed, but the intent is fired up in both cases and I don't see any hint why the Activity start is suspressed/not happening.

BTW: does anybody know if this is only on op3/t or on all (flip cover supporting) devices? Maybe https://review.lineageos.org/c/LineageOS/android_packages_apps_DeskClock/+/277201 is curing this

AlarmManager: Unrecognized alarm listener

---------- Post added at 18:12 ---------- Previous post was at 18:06 ----------

Good idea! In los16 there has been some trouble with sms/mms notifications after migrating Messages to api28. If I remember correctly some notification channel rework fixed it. On the other hand: it's not the notification missing, but the start activity for AlarmActivity - on the third hand: maybe it's interconnected.
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
Ok, I moved /system/product/app/DeskClock/DeskClock.apk from the working device (build 0429) to the non working device (0602) and voila: the alarm control screen (or how you wanna call it..) popped up again.

So it's 100% caused by a change at the DeskClock app itself.

Replacing the DeskClock.apk can be used as a very very temp fix. So I uploaded the working DeskClock.apk is sb needs it (@Johan2020)

(If you wakeup, it's better to have it in fullscreen,disabling it via wakeup the phone, pull down notfication bar und tap on the message is very hard if you're still half sleeping ;) )

I used ES File explorer for replacing it, but any root explorer, or TWRP is fine.

Just make sure the permission of the apk is set to 644 (rw r r)

You're right [MENTION=4405529]nvertigo67[/MENTION]: we should wait for a build with this merge https://review.lineageos.org/c/LineageOS/android_packages_apps_DeskClock/+/277201

or other DeskClock merges https://review.lineageos.org/q/DeskClock

But it's nice that they're working on the app - dark mode, navigation bar at bottom , notification channels etc...
[OnePlus 3 & 3T Cross Device Development] rohan164:
It's in advanced option.

You have to remove the sim

See screenshots.
[OnePlus 3 & 3T Cross Device Development] Eugeniu Vasilachi:
How to put blue accent in los17.1 like in pixels phones
[OnePlus 3 & 3T Cross Device Development] srb2020:
That's my point, in 16 you DIDN'T need to remove the SIM, you could just switch it off. That's why I've gone back to 16, who wants to keep taking SIM cards out when they are not at work?

---------- Post added at 10:27 PM ---------- Previous post was at 09:50 PM ----------

That's my point, in 16 you DIDN'T need to remove the SIM, you could just switch it off. That's why I've gone back to 16, who wants to keep taking SIM cards out when they are not at work?
[OnePlus 3 & 3T Cross Device Development] Sudhangshu:
Through styles and wallpaper settings.
[OnePlus 3 & 3T Cross Device Development] Eugeniu Vasilachi:
Here is more OOS color accent and I don't like it. I want pixel blue accent
[OnePlus 3 & 3T Cross Device Development] Sudhangshu:
It is what it is.
[OnePlus 3 & 3T Cross Device Development] rohan164:
Call recording is working now on latest build
[OnePlus 3 & 3T Cross Device Development] rohan164:
You dont like this blue. It is almost similar.
[OnePlus 3 & 3T Cross Device Development] knpk13:
Try a substratum theme if you don't like the built in color options.
[OnePlus 3 & 3T Cross Device Development] Eugeniu Vasilachi:
I found another solution https://xdaforums.com/android/apps-games/app-magisk-module-qacc-custom-accent-t4011747
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
After sleeping one night, the issue came back (the only thing that changed over night were automatic Do Not Disturb Profiles that got activated.. I think the bug is definitely in the new notification implemenation, with channels etc.)

Updated to build 0806 then, problem persists (but this patch is also not inlcuded yet https://review.lineageos.org/c/LineageOS/android_packages_apps_DeskClock/+/277201)

So let's wait for it..

There are also 2 similar bug reports for this - we should upvote them if the patch doesn't fix it..

https://gitlab.com/LineageOS/issues/android/-/issues/2020

https://gitlab.com/LineageOS/issues/android/-/issues/2041

Another issue I have since LOS 17.1:

My (stock) gallery app timeline isn't sorted right. WhatsApp Videos, Panorama Photos taken by GCAM etc - they are all sorted to the date I installed LOS 17.1 (or to the date I cleared data from media provider app - see link to the post 1 line below...)

But this seems to known. Media Provider seems also broken as it doesn't update deleted photos, files etc. right (thanks to [MENTION=2911853]BillGoss[/MENTION] and [MENTION=6991637]christantoan[/MENTION] for mentioning this https://xdaforums.com/showpost.php?p=82758587&postcount=1400

There are even 3 bug reports for this.. We should also upvote them..

https://gitlab.com/LineageOS/issues/android/-/issues/1857

https://gitlab.com/LineageOS/issues/android/-/issues/1986

https://gitlab.com/LineageOS/issues/android/-/issues/2042
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Revert "Gallery2: Sort media by DATE_ADDED"

* Media provider has been fixed.

https://review.lineageos.org/c/LineageOS/android_packages_apps_Gallery2/+/276936
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
I also saw this, but it doesn't fix all sorting. It fixed for example the Screenshot folder, but not the panorama images etc. I mentioned the post before.

Edit: Ah, thats the revert of https://review.lineageos.org/c/LineageOS/android_packages_apps_Gallery2/+/276724 - didn'T noticed this before.

Ok. Then I'll wait till this gets merged. I hope it will fix all problems with sortings - but I'm confident as Media provider was the faulty thing
[OnePlus 3 & 3T Cross Device Development] DivintyQQ:
I want to upgrade to 17.1 but unfortunately the mirrors for the SAR recovery are dead. Alternative mirror would be greatly appreciated!
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
https://androidfilehost.com/?fid=4349826312261695823

==> https://xdaforums.com/oneplus-3/one...ment/rom-lineageos-17-0-oneplus-3-3t-t3990061

---------- Post added at 14:47 ---------- Previous post was at 14:44 ----------

https://review.lineageos.org/c/LineageOS/android_packages_providers_MediaProvider/+/276929 ... Merged.

==> Works for OP5T.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Just built to check it ... lineage-17.1-20200609-UNOFFICIAL-oneplus3.zip ... ;)

Read this post before flashing : https://xdaforums.com/showpost.php?p=82566633&postcount=1178
[OnePlus 3 & 3T Cross Device Development] :
Are you still building daily? Normally weekly or even monthly builds are fine to keep in line with latest security updates, though sometimes changelog does have new stuff or bugfixes when it is nice to have a daily build (for example the change to Etar, the black theming or fixes).

Btw, what is the reason we have to remove fingerprint and screenlock before going back to official? Does something change after switching to the unsigned build iand back n fingerprint or screenlock?
[OnePlus 3 & 3T Cross Device Development] Botzer:
I also experience the GPS issues, it barely detects my position but not exactly so Maps/Waze aren't working. Also the compass seems weird...

Rebooting ? Doesn't work.

Sad Lineage isn't that stable compared to other ROMs... We lost privacy guard and many useful features for a less stable ROM, I give up. I cannot use it as a daily driver.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Only for testing. For a daily OP3/3T build ==> https://lineageos.wickenberg.nu/oneplus3/

I build LOS 17.1 only for OP5/5T every two or three days (It depends on the merged commits) because these two devices are not yet officially supported.

Note a LOS 17.1 build takes 2H30-3h00.

The removal of fingerprint and screenlock before going back to official build is optionnal... Only a precaution for locked BL and encrypted data.
[OnePlus 3 & 3T Cross Device Development] punio4:
There is something seriously wrong with the audio stack. Bluetooth is working _sometimes_, audio playback is juddery, and the microphone stops working every now and then.

Anybody knows if some other ROM has this bit fixed, or have they all just merged LOS 17.1 upstream?

I'm thinking about going back to android 9.
[OnePlus 3 & 3T Cross Device Development] mk_1996:
No problem here with the bluetooth. All works fine. The bluetooth battery stats is a little wonky i must say. But other than that, everything works fine. Tested with OnePlus Bullets Wireless Z
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
About DeskClock : https://review.lineageos.org/c/LineageOS/android_packages_apps_DeskClock/+/277201

From Danny Baumann :

Patch Set 16: Much better.

Results from testing:

alarm behavior seems fine now

stopwatch is fine

timer elapsed notification is fine

background timer notification (the one created when sending the app to background with a timer running) should _not_ have sound

So except that timer notification, everything else seems to me now.
[OnePlus 3 & 3T Cross Device Development] :
Have you tried the ccache complier cache? It reduces the build time from ~260 min to ~75 min for los 16 (cache dir on ssd).
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
in my ~/.bashrc file :

# enable ccache
export USE_CCACHE=1
# export CCACHE_DIR=${HOME}/.ccache
export CCACHE_DIR=/my_SSD/.ccache
export CCACHE_EXEC=/usr/bin/ccache
# ccache size
ccache -M 50G

in my bash :

repo sync --force-sync
ccache -C
rm -fr ~/android/lineage_17/out/
....
source build/envsetup.sh
breakfast dumpling
croot
brunch dumpling
find ~/android/lineage_17/out/ -name "lineage-17.1*" -exec mv {} ~/Bureau/ROM/OP5T/ \;
find ~/android/lineage_17/out/ -name "recovery.img" -exec mv {} ~/Bureau/ROM/OP5T/ \;
ccache -C
rm -fr ~/android/lineage_17/out/
....
source build/envsetup.sh
breakfast cheeseburger
croot
brunch cheeseburger
find ~/android/lineage_17/out/ -name "lineage-17.1*" -exec mv {} ~/Bureau/ROM/OP5/ \;
find ~/android/lineage_17/out/ -name "recovery.img" -exec mv {} ~/Bureau/ROM/OP5/ \;
ccache -C
rm -fr ~/android/lineage_17/out/
....

Did I make any mistakes?

Note dumpling (LOS 16.0) passed in 2h10 (https://buildkite.com/lineageos/android/builds/24425) and oneplus3 (LOS17.1) in 2h21 (https://buildkite.com/lineageos/android/builds/24407).

About my computer:

- DELL Optiplex 5070 Micro

- Linux Mint 19.3 on SSD 512Go M.2 PCIe NVMe Classe 40

- cache dir on SSD 860 EVO SATA III

- 16Go (2x8Go) DDR4 2666MHz non ECC

- Intel Core i5-9500T
[OnePlus 3 & 3T Cross Device Development] :
[MENTION=9708417]Eric_Lev[/MENTION]:

Looks good to me.

I'm on amd AMD FX(tm)-8150 Eight-Core Processor (overclocked to 3.9 GHz - thermal throttle at 62 C°), 1866 MHz DDR 3 and OCZ-VERTEX4 ssd with ext4. los 16 ~75 min. I use similar env vars:

export USE_CCACHE=1
export CCACHE_DIR=~/.ccache
export CCACHE_MAX_SIZE=50G
ccache -M $CCACHE_MAX_SIZE

You can always check the stats (especially cache hits and misses) from an other terminal:

CCACHE_DIR=/my_SSD/.ccache ccache -s

I wouldn't have expected the fx8150 is about 2 times faster on compiling then i5-9500T. Probably compiling scales really well with more physical cores...!?!
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
About GPS:

Many of us have noticed that GPS is not as good with LOS 17 as with LOS 16 ... nevertheless, it works ... but sometimes it is very difficult (or even impossible) to fix the GPS signal ... isn't it !

I ran a few tests... Note all the GPS tests were carried out under the same conditions (obviously).

Test 1:

clean flash to install LOS 17.1

1- Flash twrp-3.3.1-1-oneplus3

2- Format data and wipe all partitions

3- Boot to TWRP

4- Flash LOS 17.1 (lineage-17.1-20200530-nightly-oneplus3-signed) + nano open gapps (0606)

5- Reboot to System (twice)

6- install SatStat (F-droid)

7- Test GPS

==> GPS fix = not very fast and even slow ... as expected

Test 2:

clean flash to install LOS 16.0

1- Boot to TWRP

2- Format data and wipe all partitions

3- Boot to TWRP

4- Flash LOS 16.0 (lineage-16.0-20200325-nightly-oneplus3-signed) + nano open gapps (0606)

5- Reboot to System (twice)

6- install SatStat (F-droid)

7- Test GPS

==> GPS fix = very fast ... as expected

Test 3:

dirty flash to install LOS 17.1

1- Boot to TWRP (from Test 2 - LOS 16)

2- Wipe cache + Dalvik + System

3- Flash LOS 17.1 (lineage-17.1-20200530-nightly-oneplus3-signed) + nano open gapps (0606)

4- Reboot to System (twice)

5- install SatStat (F-droid)

6- Test GPS

==> GPS fix = very fast as with LOS 16... good news but very surprising !

7- update build via OTA

8- Test GPS with build 0608

==> GPS fix = very fast as with LOS 16 !

7- install Magisk (flash in TWRP)

8- Test GPS with build 0608 + Magisk

==> GPS fix = very fast as with LOS 16 !

[MENTION=9350973]All[/MENTION], [MENTION=5091734]dianlujitao[/MENTION] : Question is why?

EDIT: I've just redone test 1 with the latest official version (lineage-17.1-20200608-nightly-oneplus3-signed) ... and no trouble with GPS fix !

Previously, it was with lineage-17.1-20200530-nightly-oneplus3-signed.
[OnePlus 3 & 3T Cross Device Development] :
It might be due to SMT or hyperthreading on intel wording side

9500t doesn't have it, while 8150 has
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Maybe .... but I'm still surprised by the difference because dumpling (LOS 16.0) passed in 2h10 (https://buildkite.com/lineageos/android/builds/24425) and oneplus3 (LOS17.1) in 2h21 (https://buildkite.com/lineageos/android/builds/24407). In my case, oneplus3 (LOS 17) passed in 2h44 yesterday ... only 23 min longer than the LOS build server.
[OnePlus 3 & 3T Cross Device Development] :
Check the code which is build for both devices. A rough hint can be the overall count of files while brunching. Maybe something for op3/t is build from source, which is used as prebuilt (blobs) for op5/t; perhaps because of treble (op5/t is treble since oos 5.1.5, isn't it?).
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Not by the difference between dumpling and oneplus 3 ... between our build times ... ;)
[OnePlus 3 & 3T Cross Device Development] dianlujitao:
So...is SatStat the only thing made the difference on 17 in your experiments? I think the conclusion is incorrect because it couldn't be possible
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
For me, GPS fix is only the time required to obtain a position fix ... To avoid misunderstanding.

Note:

- I did these tests because I have two OP3T with LOS 17.1: my son's has a dirty flash and mine has a clean flash. My son has no GPS fix issue, unlike me.

- All the GPS tests were carried out under the same conditions on my OP3T.

Test 1 : clean flash to install LOS 17

GPS fix was not very fast and even slow with SatStat, Maps and Here ... but it works for navigation.

Test 3 : dirty flash to install LOS 17

GPS fix = very fast (as with LOS 16 ) with SatStat, Maps and Here. I just checked.

I was surprised by these results, hence my question ... but you think the conclusion is incorrect because it couldn't be possible.

---------- Post added at 18:15 ---------- Previous post was at 17:29 ----------

I've just redone test 1 with the latest official version (lineage-17.1-20200608-nightly-oneplus3-signed) ... and no trouble with GPS fix !

Previously, it was with lineage-17.1-20200530-nightly-oneplus3-signed.

So right ... my conclusion was incorrect because it couldn't be possible... Sorry !
[OnePlus 3 & 3T Cross Device Development] BillGoss:
I've noticed poor GPS fixes since the problem was mentioned in this thread. So I decided to replicate [MENTION=9708417]Eric_Lev[/MENTION]'s tests.

Note: I use GPS Status as my app and I always reset the AGPS status so that the first fix isn't using cached data.

Here are my results:

Los 17 200608 dirty (before): this is what I am currently running. The time for a fix is very quick - about 2-5s - but none of the satellites have a lock and the total number of satellites is low - 0/18. Waiting longer to get a satellite fix makes no difference.

NLos 16 200607 clean: clean install with only Magisk and no Gapps. Time to fix is again fast - 2-5s - but this time I get a good lock on the satellites - 16/33 and the satellite count is nearly doubled.

Los 17 200608 clean: clean install with only Magisk and no Gapps. Result is similar to Los 16: time to fix is fast - 2-5s - and I get a good lock on the satellites - 13/34.

Los 17 200608 clean, Gapps: clean install with Magisk and Gapps. Result is similar: time to fix again is fast - 2-5s - and I get a good lock on the satellites but not as many - 8/34. I'm sure if I waited a bit longer I'd get more satellites locked.

Los 17 200608 dirty restored: restored the backup of my dirty install so I'm back to where I started. But this time I'm getting good results: time to fix again is fast - 2-5s - and I get a good lock on the satellites - 17/34.

So, go figure. I've made no changes to my system between the first and last test, yet now GPS is working fine.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
[MENTION=8423339]Johannes1098[/MENTION] :

DeskClock:

==> Come to the dark side... https://review.lineageos.org/q/topic:"10-clock-redesign"+(status:open OR status:merged)
[OnePlus 3 & 3T Cross Device Development] Joshmccullough:
Is there an NFC quick settings tile that's available for the pulldown/status bar? I could've sworn I saw it there once upon a time, but I'm looking through various settings and not finding it.

If it's not there, no worries, at least I'll know I'm not crazy!
[OnePlus 3 & 3T Cross Device Development] BillGoss:
It's there (screenshot) in 200608.
[OnePlus 3 & 3T Cross Device Development] :
This morning I woke up with the new deskclock. And though the notification popup is working again normally, though I think they messed up something with theme colors.

A yellow notification screen with white text after pressing snooze is probably not what they had in mind.... ;)

And why yellow as color, where I have set blue as the theme color for my setup?

But nice to see they are working on integrating the dark side.... :o
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
The nice theme looks very very nice.

And that the notification popup is back - is also great.

Yellow? Doesn't mind as long as it's there... :p

No, seriously, I am conviced that this will also get fixed very soon

[MENTION=9708417]Eric_Lev[/MENTION] did you build the 0612-unoffical again by yourself? If so, could you please share the link for me :)

Edit: [MENTION=10511117]Johan2020[/MENTION] I see a picture in your last post with a custom theme in the design and wallpaper app . Did this app crash before in your system, after applying a custom theme?

See my post #1442 for details..
[OnePlus 3 & 3T Cross Device Development] highdiver_2000:
I just discovered using NitrogenOS, GPS Test cannot locate satellites with TPG mobile data

M1 works fine. There is no problems using either with Oxygen OS. What a strange finding!

What telco are you using?
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Only built for testing the dark side of DeskClock ...

==> https://androidfilehost.com/?a=show&w=files&flid=313645

[MENTION=4405529]nvertigo67[/MENTION]:

Intel Core i5-9500T 6-Core Processor (2.2 GHz) vs. AMD FX(tm)-8150 Eight-Core Processor (overclocked to 3.9 GHz)

==> Hence the difference in build time ... ;)
[OnePlus 3 & 3T Cross Device Development] :
That was my first guess:

HT and mother board chipset may explain the rest of the difference. (Board: sabertooth v1 fx990)
[OnePlus 3 & 3T Cross Device Development] remedya:
Yesterday it took 8h42 to build on an old laptop with i7-3520M, 16gb RAM and 500gb Samsung EVO 860 SSD with ccache running.