EvilDragon

Do you happen to have the links / information available somewhere? I'm not sure how fast the team does reply these days :) Haha, I know what you mean 😄 I would agree (and love the margin function on Lineage), however, the margin is WAY too much here, about 7 - 9mm margin. I can't even properly use the WhatsApp record button anymore 😉

While it's not directly related to LineageOS, I thought I might ask here as well, as it might be something that can be added: You can read more details about my issue here: Basically, I bought replacement screens from China from multiple vendors. They work fine, but they don't react to touches on the edge of the screen. I first thought the touchscreen is unresponsive - but that's not it: when I enable the function in the developer mode that shows the coordinates and draws your touches on the screen, I noticed that I can slide to the edge of the screen without any issues and 100

Oh, interesting information. I'm on LineageOS, so I'll ask if there's a way to fix this without a full reflash by just updating the driver. What's interesting is that I have multiple screens here. Some work without any issues - and some have exactly that issue. With the same OS. So it seems there's a different model and they updated the driver later on... hmm.. Thanks for the information :)

I received a Pro 1 back from a customer with the exact same issues: Microphone issues and non-working hall-sensor. I completely disassembled it. The good news: The hall sensor (and probably also the microphone, didn't check) is sitting together with the USB port on an extra PCB which is connected to the mainboard. That's an awesome design - as it means that you can even fix ripped out USB ports easily by simply replacing that small extra PCB! Now... we just need to get hold of the PCBs. I've contacted the team a week ago, as I want to stack them so I can offer replacement p

Hm, this is becoming a bit of a problem it seems. I have 15 replacement screens here, from two different china distributors. They work - but don't react to taps on the curved edges, which is very weird. An earlier sample I got from China worked fine - so I guess the hardware has been changed. The weird thing is: Only taps are affected. If you touch the screen at the edge, it will show no reaction. But if you touch it in the middle and slide to the edge, the edges work fine and accurately (can be tested with the developer settings in Android). I wonder how this can be... c

My Opel works flawlessly with Android Auto as well.

We're based in Germany. And yes, that unbricking was me (with help from tdm :))

I will also have replacement screens in my shop including a replacement service soon. Also, if you use a case which covers the screen (I can take some pictures of it), then the screen is perfectly safe. Cracked mine a few times before I got the case, after that, it never happened again.

SE215 Wireless, from 2019 Supports Qualcomm aptX, aptX HD, aptX Low Latency, AAC and SBC.

I'm not sure if this is related to LineageOS or something else, but I have a small problem with Bluetooth: I've got a headset (Shure) which is also recognized as headset (you can see that from the symbol). However, all apps (Audio Recorder, WhatsApp, etc.) I tried always use the internal phone microphone instead of the headset one. When I connect a wired headset, this works fine - it's only an issue with Bluetooth. Any ideas?

Hm, I did this via sideload, and even with recovery reboot, it killed the gapps. Didn't even know these nightlies can be updated via OTA (afair, OTA said there's no update available...?), but I'll try that next time.

Ha, thanks a lot! Both worked. I tried top before - but didn't see anything special. But checking the log for crashes I could see that Android Auto was constantly crashing... removing and reinstalling it stopped the battery drain and made it work again. Totally forgot about that as I didn't use my car since then 🙂 So yeah, it seems the update made all Google Apps crash. Is there a reason to prevent that? Reinstalling the Google Apps each time wouldn't be an issue - but I need to redo the configurations each time as well, which is a bit annoying :)

Okay, I'm not sure what I am doing wrong, but it seems I still have quite a bit of issues. My upgrade path was a long way... from early testing builds until the first official nightly and two days ago, I flashed to the latest nightly. The first nightly was working pretty good for me. Long battery time, no real bugs. I have never used the fingerprint reader though. Seeing that the fingerprint reader should work pretty well with the latest nightly, I decided to upgrade, and that's where my issues begin. First: What's the best way to upgrade? I simply tried to update the roo

Hm, what's so complicated about it? Took me about 20 minutes to setup everything the way I like after installation... and then you never need to do it again.

That's why I switched to Total Launcher where you can define two totally different layouts for portrait and landscape. Way better than Nova 🙂

Yes, I did that, but for some reason, it still happened. But as mentioned, that was fixed by reinstalling the programs, no big deal. The problem with hearing calls is that I have no idea how to troubleshoot that on Android. On Linux, I would simply test all output devices to see if it might be the speaker that's faulty, but with Android, I don't even know where to start 🙂

Oookay, I updated Test 13 to Test 15 which really has messed up the installation a bit. All Google apps (and a few others like Skype) stopped working and crashed all the time. The fix was to remove and reinstall them all, so that is okay now. However, one issue remains: In phone calls, I can only hear the called when I switch to speaker mode or use a headset. The internal speaker is disabled for some reason. Any idea how to troubleshoot or fix this?

Okay, did the update and think I fixed most of the issues. The Corona App did work after I manually updated the Google Play Services using the latest APK from apkmirror. No idea, why it didn't work before though, probably a bug in the Play Services version I was using. Additionally, I reinstalled supersu - which made the AudioDAC Booster work again. I do remember that I installed this as someone suggested that this can fix some audio issues - so this probably was what fixed the WhatsApp issue I had (I need to check and confirm this though). If that's the case, then there's a bug

Thanks, will update right away :) Quick question: I know the first flash will be done on Slot A. But what about the update? Should I flash to Slot A or B?

The ones that are linked directly from tdm´s download page. EDIT: So basically MindTheGapps. But yes, I can try reinstalling them.

Nope, I don´t even have the settings, they don´t pop up. Hm, maybe I´ll reset to factory settings. Never did that since intalling my first LineageOS build... I always simply upgraded.

Hm, I'm getting the error: "CAUSE: 3 Something went wrong Error when communicating with Google API(17)" Details say: "Nearby.EXPOSURE_NOTIFICATION_API is not available on this device. Connection failed with: a(statusCode=UNKNOWN_ERROR_CODE(39507), resolution=null,message=null)" and a lot more stuff. That happens right after installation when it tries top open the API. I'm on Google Play Services 20.21.15, so it's even more recent than yours. Hm, maybe it's some of the Google stuff I froze (Google Partner Setup?) - but, hey, flashing test13 did remove my

Maybe someone here knows: I´ve installed the official Corona warn app from german government which uses the new expose notification framework from Google (implemented in play services 17.x and higher - I´m running the latest 20.x version). However, it complains that it can´t find the api - and the same seems to happen for all Xiaomi users. Does anyone know what´s missing here? Is this something that can even be fixed with an OS like Lineage?

Of course :D I need a phone with a keyboard. Got a multiple-times-cracked screen (as it fell down multiple times on the ground without a protection... now I've got a nice leather cover :), but it's still working. And I've ordered a new screen already (and will also offer a replacement service later on). Just waiting for the team to catch-up with the orders so they can deliver more units to distributors. I'll try to find that out... I think I was on test12 before, as I always try out the latest version, but if it just had fixes I wasn't interested in, I might've skipped.

Great to see you´re doing fine and that things are moving again :) I flashed Test13 and the keyboard on my German version is a lot better. I think the only wrong key is the apostrophe on L now. However, I now have the issue that recording WhatsApp voice messages (at least with my cable headset) has problems. It heavily stutters. I´m not sure which version I used before (but it was one which had the audio fix already), but it worked fine before. Has anything been changed in that area?