Wheeljack

With or without HD audio my car connects using SBC. When I disable "media audio" I can't see it using any audio codec at all. Copy of phonebook and call controls work though.

@DieBruine and @Wasmachineman_NL My Senheiser PXC-550 II are supposed to support aptX and aptX-LL. Developer menu shows it connects with AAC only. And then there's the weird behaviour of my car's hands free where I can use the Pro1 as a music player but phone calls will use the phone speaker despite BT being set in the caller screen. Since the car is from 2010, there might be some older 2-way codec not working, too. But that already has it's own issue on GitHub. @_DW_ the game installed fine for me. Started okay and downloaded an additional package.

Yes that one. Weird. Had the phone on the charger and didn't bother it with other tasks. I took the time from "Install now" after downloading and stopped when it prompted to reboot.

OTA update went fine for me as well. Have set it to high priority, that cut down installation time to about 30 minutes.

I don't think ordering QWERTY instead of QWERTZ will get you a Pro1 any sooner.

Where would I run "tar" from? Within the adb root shell? How would I stop services? Do I need to be in system/bootloader/fastboot? Anyone willing to write that up in a bit more detail? I'd really like to test some bluetooth things on stock but would then want to return to the current state Lineage is in.

@Hook you need to reboot to bootloader and install the official boot.img to the active boot partition first before booting to recovery and sideloading.

Probably stating the obvious here, but the boot.img from the test-builds is not compatible with the official lineage installer. So doing the "fastboot flash boot <recovery_filename>.img" before going to recovery and sideloading lineage is mandatory when switching from test to official 😅 Other than that, everything went fine just as reported by @EskeRahn

Are you going to write a little tutorial for how to switch from test to official without wiping?

Tested muting, speaker, numpad tones - everything worked for me.

For whatever reason I expected the statusbar change to involve some gigantic fonts - but it's just a few pixels bigger with no change to the font. Nah... totally reasonable modification. 👍

Just in case you need a sample of a QWERTZ with WiFi issues, here's the output of mine. modemversion.txt

Sorry for the big delay between my updates: after taking the phone off the charger last night, it was not connected to WiFi and mobile again and it took on the same behaviour as before the changes to wpa_supplicant_overlay.conf. After turning on the phone this morning, WiFi was still spotty, so I tried flashing the the test19.img bootloader as suggested. Phone wouldn't start at all. Went back to test21.img and I'm relieved nothing is broken 😅 Now waiting for test22.

Could you point me to the directory where this file is supposed to be on my phone please? 😅 Edit: okay... found it in /vendor/etc/wifi Okay... added 6 lines since the first 3 were already there. Rebooted and checked, if the modification was still there. Will keep an eye on WiFi behavior. Edit 2: So WiFi is now indeed way more stable for me. I have yet to see the WiFi symbol with an X and mobile data activating LTE. There were still a few hiccups with youtube though briefly showing offline/reconnected during playback.

I see a lot of disconnects/reconnects with my WiFi as well. It's even happening while watching a YouTube video. Could this also be aggressive switching between 2.4 and 5GHz? Edit: I'm also getting a message to please disable airplane mode on my first call attempt after waking my phone.

test21 installed fine. Had to readjust display size down two notches since the "default" is now bigger. Trebuchet was also now 4x4 instead of 5x5. Now that everything is back looking like before, I can start looking for not so obvious differences 😉

For the average user the "Minimal adb and fastboot" installer looks like the way to go. It unpacks adb and fastboot to a specified directory and puts an icon into the start menu that launches a cmd shell in the proper directory.

I see TWRP in the installation instructions. Is that correct?

Can confirm QWERTZ layout is fixed. Big THX.

Like I said... hard to trigger. Usually both keyboards work fine. Just installed test17 without problems. SELinux shows as "Enforcing". Not seeing any new issues. Edit: Now that I'm trying to write from my phone, I notice the QWERTZ layout is shifted.

Noticed that happening too with every test build I used so far. Still unsure how to reproduce this, if it's a specific app or if it's just me and bad timing opening the physical keyboard while the virtual pops up.

Had pretty much the same happening with the app from the insurance "Signal Iduna" with all unrooted Lineage test versions I used so far. The app just said my device was rooted and wouldn't start for security reasons. So either their check is wrong or their message is lazy.

Which gapps did you install?

Corona-Warn is working for me. I´m on Play Services 20.21.17 Google-App is 11.14.6.21.arm64 lineage test13 - not rooted Trust data protection is deactivated for Google and Play-Services That´s about it what I believe could be different on your Pro1. Edit: do you see the Corona options under Settings -> Google ?

T-Mobile Germany was out last night. It's all over the news today.