yashsingh1/xdaforums huggingface dataset:
[OnePlus 5 & 5T Cross Device Development] Scream275:
@denisovich I'm on this ROM for the last three builds and it's working great so far. I'm having gapps, magisk, dotfix for the camera & gcam installed. No OTA-update problems so far (only flashing the ROM, nothing else).

There are only three issues I found, detailed here:

OnePlus 5T HD-Audio switch not availabe for HD-Audio headphones (aptx) (#3036) · Issues · LineageOS / issues / android · GitLab

I got Teufel Airy (2015) headphones which support the aptx codec. On OxygenOS 10.0.1 my 5T used the aptx codec (a aptx toast appeared), but on the latest...

gitlab.com

e-mail spinning infinitely on refresh of combined account view (#3040) · Issues · LineageOS / issues / android · GitLab

I'm having two e-mail accounts set up (both IMAP, both correctly configured). On each account separately the e-mail app works fine. The issue is only available for the...

gitlab.com

The third one was a frozen system where I had to force power off the device, but that did happen only once. So I haven't reported it. EDIT: happened now three times in about 1 month

I had one more issue with the last build, detailed here:

OnePlus 5T VoWifi stopped working with build from 20210202 (#3035) · Issues · LineageOS / issues / android · GitLab

Expected Behavior VoWifi is working like in build lineage-17.1-20210126-nightly-dumpling-signed.zip. If being in airplane mode & activating wifi, the mentioned build showed...

gitlab.com

I guess that was related to the sim-card stuff, other people wrote about. VoWifi is working again since the latest build.
[OnePlus 5 & 5T Cross Device Development] rphair:
Device MAC = random 1 of 2 choices every phone boot (?!)

My phone has two different possible MAC addresses that it can start with: sometimes one, sometimes the other (not hardware related because I never had this issue on LineageOS 16.0).

The device always connects to a WiFi network which I control, with WiFi settings always set to use "Device MAC" rather than a randomly generated MAC (default). WiFi connections always show the same MAC as in About Phone > WiFi MAC address... i.e., the same random one of the two addresses. Therefore I assume it's the device "WiFi MAC Address" itself that is inconsistent.

I've also looked in the developer settings and can't see what would cause this. We need a consistent IP address on this device but can't work around the problem on our OpenWRT router because reserving a single address for more than one MAC address hangs DHCP on the router.

If there is a bug report for this, or if I should file one, please let me know where or how. If there's no fix I'd be happy with a workaround for now. 🙏

Nightly LOS 17.1 dated 8 February 2021 + Magisk 21.4

Reimaged recently from a full wipe with no substantial settings changes from the default.
[OnePlus 5 & 5T Cross Device Development] zumi001:
Try going into the settings of your specific wifi network (not the generic wifi settings). There's a new (compared to LOS16) "Privacy" option there where you have to select "Use device MAC" instead of the default that randomizes your MAC address.
[OnePlus 5 & 5T Cross Device Development] rphair:
Correct. When my particular WiFi setting is set to "Use device MAC" that's what it always uses. However, as I said above, the Device MAC itself is potentially different with each Android reboot (being one of two possible values).
[OnePlus 5 & 5T Cross Device Development] zumi001:
Sorry, I missed the part that your actual device address is changing. This has not happened to me yet. As a workaround you can set a static ip for that specific network. Maybe check the dmesg for the kernel and look for the different MACs and see what's the difference in those lines when the kernel discovers the device. Is it done by the same driver in both cases? Might be some race condition.
[OnePlus 5 & 5T Cross Device Development] rphair:
You missed that part too :p ... I already tried that: as it says above OpenWRT doesn't accept duplicate MAC reservations of the same IP address (or maybe the same hostname; can't tell). Hangs the DHCP server & haven't been able to figure out why or how to avoid that (tips would be welcome).

Good idea & will try that next time I see the address flipping. If anything useful can be learned I'll post it here. 🙏
[OnePlus 5 & 5T Cross Device Development] zumi001:
Nah-ah, I did not miss it, not this time at least! :D I don't mean to set a static DHCP lease in your router, but to add the Wifi network on your phone with a static IP, instead of DHCP. When you try to add the network, click "Advanced options" and then change "IP settings" to "static". You have to forget your network and add it again, this doesn't show up when you edit an already added wifi network.

Then judging from you using OpenWRT I think you will be able to set the address/gateway/etc. according to your network. This way your router is not responsible to assign you an address, your phone does. Not ideal but should help you until you figure out the MAC address weirdness.

Good luck with the debugging. (y)
[OnePlus 5 & 5T Cross Device Development] rphair:
OOPS that's my mistake, you used the words "static IP" unambiguously for sure... I was just hoping to keep to our small office standard of one-IP-per-MAC kept in the router all in one place & backed up. Yes thanks you're right it would save some headache until that can be restored :love: ... I just ruled it out earlier since it masks the problem completely so we don't know if it's fixed in a future release.

If anyone knows what to look for in the logs please post an idea. The first time the Device MAC address itself appears in `dmesg` is when it's used as a MAC address to connect to a WiFi network. If assigned earlier than that in the boot process, it doesn't appear in `dmesg`.

From this initial log message of the wireless binding, I'm guessing `vdev-0` is the driver for this particular boot-up? (It doesn't show the android device MAC until a few lines later.)

[ 43.502209] [20210220_15:21:32.966692]@3 [wpa_su][1101258803][15:21:32.966687] wlan: [2767:I:SME] vdev-0: Connecting to MS5.0GHz d8:07:**:**:**:** rssi: -33 channel: 116 akm 9 cipher: uc 6 mc 6, CC: IN

Anyway I'll save our `dmesg` output & see if it looks any different when it's using the other MAC address. If we find evidence of a bug from all this, please let me know if/how I should report it (I haven't done that before).
[OnePlus 5 & 5T Cross Device Development] rphair:
p.s. I've found out that, while this is true if setting a duplicate MAC-to-IP assignment in the UI (which writes /etc/config/dhcp), you can instead put the phone hostname & IP address in /etc/hosts and then that hostname with as many MAC addresses as you want in /etc/ethers, which works & doesn't hang DNS & DHCP servers.

End of that off-topic workaround & I'll post anything here that sheds some light on the original issue (the inconsistent Device MAC).
[OnePlus 5 & 5T Cross Device Development] zumi001:
I'm out of my depth here, I know Linux but not Android too well. On a normal Linux system the network card would appear in the dmesg, but I can't find it in my own dmesg output either on my OP5. However I also don't have this issue, and I see "wlan0" with the proper MAC in the output of ip link command. My other (probably not useful) suggestion is to make sure there's no root app or any VPN apps that could screw with your MAC address.

Also if you can reproduce the problem you can check the "ip link" output and look around in that. There's also theoretically a way to change the address of your interface with ip link set dev wlan0 address XX:XX:XX:XX:XX:XX but I'm also not sure if this works under Android. If it does, you can correct it when you see that it's incorrect.

As for reporting the issue: https://wiki.lineageos.org/how-to/bugreport -- but I see T1mb3, the (awesome) maintainer for this version of LOS is here in, so if you find anything definitive he might be able to see and fix it.
[OnePlus 5 & 5T Cross Device Development] js-xda:
I am reporting two, appearing initially probably independent bugs where I suspect suspected initially a connection nevertheless. As I am running German GUI, translation of some menu entries or such might be not exact.

Running LOS 17.1 210208 (and later upgrade to 210222) on OnePlus 5 with TWRP 3.4.0, firmware 10.0.1 (01.09.2020), no Magisk, no microG but OpenGAPPS Pico.

---

1. Locking display directly vs. setting stating 5 second delay

I noticed since migrating from LOS 16.0 that the device locks right away upon screen off and not with the indicated delay of 5 seconds. I hadn't looked into it further until 1-2 weeks ago. Then I realized it is possible to regain the delay behavior when deactivating the function that power button locks straight away (default setting as far as I know). I decided to give it a try - noticing already the risk that I might re-activate the phone e. g. in my pockets within the 5 seconds period.

---

2. Phone rebooting (somewhat) at random pattern

Somewhat later, I noticed that the phone started rebooting at random pattern a few times per day. I noticed as the screen was empty at first upon entering the unlock PIN like after a full reboot when the device is decrypted. Odd thing was that (other for a normal reboot) the SIM PIN wasn't required! So, it wasn't about a power loss or something like that. I suspected/tried:

Flashing newer build 210222 - no change

Wiping Dalvik/ART cache - at first it appeared less but then returned to the usual frequency of two to three times per day

One more thing that I can't recall right now ... will add later if recalling ...

At some moment, I realized that the initial occurrence might coincide with the change done as described in the first part (deactivating power button locking straight away). So, I suspected at first that it was about me doing something by accident (e. g. in the pocket) but I could recall also definitely an occurrence where the phone had been laying on my desk and no touch for sure. I gave it a try and reactivated the power button locking straight away ... and the issue appears to be gone (more than 24 h without a single occurrence). Update 2.3.: Never mind - multiple reboots this morning not stopping until forced shutdown.

---

Has anyone observed same or similar behavior? I checked on this thread but couldn't find any matching reports.
[OnePlus 5 & 5T Cross Device Development] js-xda:
Last night, I flashed manually the latest LOS 17.1 build 210301 together with OpenGAPPS ARM64 Pico for Android 10 210303 - reboots occuring still. Updated also to TWRP 3.5.0.

Anyone an idea besides wiping everything and starting with a clean system to verify that it is (not) about the system or the hardware? Problem is that I have no guarenteed way how to reproduce.
[OnePlus 5 & 5T Cross Device Development] theShadow800:
[MENTION=7280252]T1mb3[/MENTION] I was trying to build the LineageOS kernel from your sources. I am using the protonClang toolchain and have successfully built other kernels but with LOS I am getting this error. Are you using a different toolchain? Could you help me resolve this error?

/home/pranav/kernelStuff/clang/bin/as: unrecognized option '-EL'
clang-12: error: assembler command failed with exit code 1 (use -v to see invocation)
make[3]: *** [../scripts/Makefile.build:283: scripts/mod/empty.o] Error 1
make[3]: *** Waiting for unfinished jobs....

I get like 3-4 of these and then the build fails
[OnePlus 5 & 5T Cross Device Development] :
op8998-ten wants GCC.

op8998-ten-upstream & op8998-eleven want Clang.

I use the Clang version Lineage provides by default when TARGET_KERNEL_CLANG_COMPILE is set.
[OnePlus 5 & 5T Cross Device Development] theShadow800:
Could you please link me to the specific clang version you're talking about?
[OnePlus 5 & 5T Cross Device Development] :
Any AOSP Clang version higher than 9 should work but here are the ones LineageOS uses:

- Clang version 11.0.2 based on r383902b for Android 11.

- Clang version 9.0.3 based on r353983c for Android 10.

You can find them in AOSP source: https://android.googlesource.com/platform/prebuilts/clang/host/linux-x86. Pick a tag according to Android version :).
[OnePlus 5 & 5T Cross Device Development] theShadow800:
Thanks! I'll try building it again.

Also, is it cool if I DM you if I run into some issues?
[OnePlus 5 & 5T Cross Device Development] :
Sure
[OnePlus 5 & 5T Cross Device Development] :
UPDATE

* Synced LineageOS sources

Download
[OnePlus 5 & 5T Cross Device Development] :
UPDATE:

This thread is moving to Oneplus5 & 5T cross device development for added support for 5T!

Download LineageOS 17.1 for Oneplus 5T: https://sourceforge.net/projects/lineageos-cheeseburger/files/LineageOS-17.1/Oneplus5T/

Required firmware: 10.0 Hotfix 1.

Also 5T is waiting for LineageOS approval to be official.
[OnePlus 5 & 5T Cross Device Development] InsaneNutter:
Thanks for the 5T support T1mb3, it will be great to have official builds of newer LineageOS versions.
[OnePlus 5 & 5T Cross Device Development] NazuNalika:
I've been running the 17.1 builds for a while. At one point I did a dirty flash from 16.0 over to 17.1. However, I ran into some weird file permission issues. For example:

Screenshots do not show up at the top of the list in the gallery

Pictures sometimes taken with the camera do not show up properly or show at the bottom of the list

Gallery doesn't update properly half the time

Timestamp of files are 1969

The one way "around" this is I just reboot and things are just fine right after. But it doesn't make sense why this started happening. I tried wiping cache, davlik, and the like. Same problems. I then did a full clean flash, same problems. I'm not entirely sure why any of this is happening. Any suggestions on where to go from here? This is an annoyance that is finally bugging me.
[OnePlus 5 & 5T Cross Device Development] TufTurf:
1. Will this unofficial get OTA updates ?

2. Can I dirty flash this build from Eric lev builds on 5t lineage 17.1 ?

3. Does this build change twrp recovery ? Or is it only in los18 ?
[OnePlus 5 & 5T Cross Device Development] :
1. No OTA updates. Only official builds get ota!

2. Propably yes, but if something breaks, you know where it happened.

3. This does not touch recovery if it is not enabled in dev settings.
[OnePlus 5 & 5T Cross Device Development] :
UPDATE:

* Synced LIneageOS sources (no big changes there)

* Improved device tree

* Less debugging --> 9000% better battery

Download Oneplus 5 & Oneplus 5T.
[OnePlus 5 & 5T Cross Device Development] so_bek:
Thanks [MENTION=7280252]T1mb3[/MENTION] for keeping dumpling alive!

What are the odds one could dirty flash this over official LOS16.0?
[OnePlus 5 & 5T Cross Device Development] frov:
Today, I was not so brave as to just dirty flash this 17.1 over 16.0 on my 5T (flashed it while ago as via current official Lineage download).

Instead, I totally wiped it all, including data and ultra-clean flashed this new 17.1 (20201018) onto it (and the new 10.0.0-H1 firmware).

Incl magisk 20.4; used SwiftBackup to restore apps. All worked / works fine: many thanks for this! :good:
[OnePlus 5 & 5T Cross Device Development] rustaman_89:
Alert slider not work in my dumpling after last update.
[OnePlus 5 & 5T Cross Device Development] :
Thanks for report. I'll look into it.
[OnePlus 5 & 5T Cross Device Development] frov:
Indeed, here same issue.

After my previous post I had updated dirty to that latest rom. Tnx!
[OnePlus 5 & 5T Cross Device Development] :
HOTFIX:

* Alert slider is back

Download Oneplus 5 & Oneplus 5T.
[OnePlus 5 & 5T Cross Device Development] rustaman_89:
I confirm. Everything works well. Many thanks!
[OnePlus 5 & 5T Cross Device Development] :
Surely sounds like your power button is a bit jammed and you unjam it by pressing it.

No other reports of similar behaviour has been reported. If you want to be sure, take a logcat at the time of the reboot and sent that for me.
[OnePlus 5 & 5T Cross Device Development] js-xda:
Thank you for giving my issue a thought! I understand fully where your line of thoughts comes from - and it matches that I had a lot cases when double-clicking on power (device in standby) for direct camera access. But I am not sure whether it is the right route. For clarification first what I refer to as "normal (re)boot)" and the type of "reboot I observe":

"normal (re)boot"

In between the Oneplus/Android screen, I am greeted by the warning that my device may be corrupted and so forth due to using custom recovery etc.

LineageOS animation will last around 5 sec.

SIM PIN is requested.

regular unlock

"screen waking up" (from slightly grayed out to colored and only then showing start screen icons)

"reboot I observe" (if I am lucky/unfortunate enough to witness it)

NO Oneplus/Android screen, NO warning.

LineageOS animation rather only 2 sec.

NO SIM PIN is requested (but unlocked later on).

regular unlock

"screen waking up" (from slightly grayed out to colored and only then showing start screen icons)

Also, when I keep the power button pushed (as if jammed), the phone will power off - not reboot. So, not sure - what do you think?

Besides, I am testing at the moment with performance set to "fast" (schnell) instead of default "balanced" (ausgeglichen) as I saw some vague indications of reboot/stall on LineageOS 17.1 for Samsung Galaxy S4 when forcefully pushing for it by setting it to lower performance and causing some more activity. So, I decided to do the opposite. And for about 24 h no issues anymore while it was at least 10 times/day the last days before.

If I observe further issues, I will check on the logcat.
[OnePlus 5 & 5T Cross Device Development] :
That sounds like a crashing SystemUI or something similar, you should be able to take a log even after the reboot.

Do you have Magisk or any other mods installed?

Edit: you mentioned earlier that you don't have Magisk, but there is no other user with similar issues, so it is very likely something wrong in your setup.
[OnePlus 5 & 5T Cross Device Development] SchroedingersCat:
Upgraded from official Lineage 16 to 17.1 without problems. But when opening the camera app I'll get an instant reboot. Any ideas?

EDIT: If I wipe the camera app's data, the camera works fine. But as soon as I enable the option to use GPS, it instantly reboots the phone.

EDIT2: Just updated to the new version of Lineage 17.1 released today and it fixes the reboot. However, even with GPS enabled in the camera settings, photos taken with the camera app won't have any GPS position embedded.
[OnePlus 5 & 5T Cross Device Development] js-xda:
Just out of curiosity: Is it a full/normal reboot or a reboot as I describe above (post #383 of this thread)?
[OnePlus 5 & 5T Cross Device Development] SchroedingersCat:
Yeah, its definately way faster than normal and it skips the warning screen before the lineage animation. Not sure about the PIN request as I now have the update installed.
[OnePlus 5 & 5T Cross Device Development] jochenn:
I have a similar issue as @js-xda describes here: https://xdaforums.com/t/rom-10-0-official-lineageos-17-1-for-oneplus-5-5t.4169147/post-84582691

In addition to his issues, I'm not able to connect to bluetooth devices. As far as I can tell it startet with the build from 20210208 but I have no way of confirming.

Right now I'm on the 20210308 build and Bluetooth is not working. If I try to connect to a device lineage tells me that this app (bluetooth) is not working anymore.

The reboots are quick, at random times and do not require SIM unlock.

Although, sometimes it seems like I can force a reboot by messing with connectivity to the web. For Example: I'm on wifi with cellular turned on. If I turn off wifi it crashes. After the reboot it reboot until I turn off cellular web access.

I'll try to collect some logs over the next days.
[OnePlus 5 & 5T Cross Device Development] js-xda:
This matches another observation of mine that I forgot to mention: Crossing borders (roamimg) did often result also in cascades of reboots until I was well clear of the boarder region.
[OnePlus 5 & 5T Cross Device Development] js-xda:
No bluetooth issues in my case.

Starting with 20210208 does match while having same issue of not being able to verify for sure.
[OnePlus 5 & 5T Cross Device Development] Eisfunke:
I'm having the same issue as @js-xda: random "reboots", but not actually reboots, the phone just crashes to lockscreen after a short Lineage Boot animation, no SIM unlock required. On a 5T (dumpling) though. No bluetooth issues.

It started with 20210223 for me, still happening on 20210309. Downgrading to 20210209 again fixes the issue again, no reboots at all, so something changed after 0209 that broke stuff. (disclaimer: I'm using magisk)

I'm back on 0209 now so my phone's usable, but next time I'll take some logs.
[OnePlus 5 & 5T Cross Device Development] SchroedingersCat:
I'm also observing these quick reboots at random while the phone is not in use.

Since I upgraded from Lineageos 16 to 17.1, the RAM usage from the developer options is reportedly about 5.7GB now, while it used to be around 3GB on Lineage 16.
[OnePlus 5 & 5T Cross Device Development] :
Please report your issues to LineageOS (https://wiki.lineageos.org/how-to/bugreport) with proper logcat and steps to reproduce (if any). I can't do anything without a log.

Also there are not many changes to the 17.1 branch, changelog for lineage-17.1-20210223-nightly-dumpling-signed shows 0 possible causes. I suggest to start by checking your environment; uninstalling all your mods (Magisk, ...), using supported Gapps, etc.
[OnePlus 5 & 5T Cross Device Development] jochenn:
I managed to capture some logs yesterday. They should contain me turning off WiFi and my phone rebooting when it tried to connect to the web via cellular network. After that it rebooted a few times until i turned off cellular network.

Pastebin Part 1: https://pastebin.com/XLDpREEJ

Pastebin Part 1: https://pastebin.com/5bmNPDxU

Pastebin Part 3: Pastebin thinks the third and last part is offensive and I can't find a way around it
[OnePlus 5 & 5T Cross Device Development] Eisfunke:
Could you post the logcat file in the LineageOS bug tracker like @T1mb3 suggested? (see https://wiki.lineageos.org/how-to/bugreport and https://gitlab.com/LineageOS/issues/android )?
[OnePlus 5 & 5T Cross Device Development] jochenn:
I created an issue here: https://gitlab.com/LineageOS/issues/android/-/issues/3144
[OnePlus 5 & 5T Cross Device Development] js-xda:
If I combine the above observations, could it be that there is a difference between cheeseburger (OnePlus 5, me and @jochenn using it) and dumpling (OnePlus 5T, @Eisfunke using it) on the builds which helps to pinpoint the issue to certain changes? For cheeseburger, it started with 20210208 while, for dumpling, 20210209 is still without the issue. I am testing currently on 20210118 (last build prior to 20210208 that I have at hand) but only for a few hours yet.
[OnePlus 5 & 5T Cross Device Development] Eric_Lev:
TWRP 3.5.1 Released​

TWRP 3.5.1 Released

TWRP 3.5.1 is out now for most currently supported devices.

twrp.me

Download twrp-3.5.1_9-0-cheeseburger_dumpling.img

Download page for twrp-3.5.1_9-0-cheeseburger_dumpling.img

dl.twrp.me
[OnePlus 5 & 5T Cross Device Development] SubNoizey:
Rom is great. just installed it and it's much smoother than OxygenOS. However, the slider is a little odd. For some reason, it has total silence (DND) and vibrates. It really feels like the slider should let you swap between system profiles. I think it makes much more sense and is closer to the original implementation of the slider.

@T1mb3

Considering it's a device-specific button is it possible that it can be used to swap between system profiles?

Also is there an option to unlock the device by using fingerprint?