Leaderboard

Certainly not my experience with their repair service. Have you emailed them recently? The pic above just looks like confirmation that it was sent. Has the courier provided any documentation or other proof that it was delivered? I understand your frustration, but I really don't think they have any interest in stealing customers' phones. @Erik, can you be of any help here?

Just to add to what already was said – In a heavily used smartphone, depending on what you use the card for, it might make sense to make sure the card (i.e. the card's controller) does wear levelling. I'm not sure whether there still are cards available which don't, but I already managed to quickly wear down two cheaper, smaller cards (of renowned brands, though) which I used as the main storage in a Raspberry Pi. That said, I haven't had a defective card in any of my Android devices yet.

(lineage-18.1-20210607-nightly-pro1-signed.zip on May 5 security patch installed smoothly using adb sideload and MindTheGapps-11.0.0-arm64-20210412_124247) Please note: On keyboard layout selection issues, see this thread.

Sent you a PM with link for download. Feel free to pass it on if it's useful. You're the only one to ask for it in 5 months, I doubt my server is going to be flattened by download requests 😀

Keep in mind that you'll need to format it with FAT32. exFAT is not supported. If you plan to switch the card between camera and a phone, probably you'll be stuck because of lack of exFAT support. If your use case is only with the phone - take the cheapest one (from reputable Brand/Store, there are many fake cards from China)

Any microSD card should be compatible. I tend to get Sandisk (currently 256 GB) and I stick to Ultra rather than Extreme because the Pro1 doesn't really get the benefit that some high end DSLRs might. Frankly, as long as it is a Class 10, you should be fine. But I'm no expert. Others here are likely to know more.

Thanks, I'll keep that in mind...

It's not that hard but you have to be VERY careful with fingerprint reader connection ribbon.

Thanks, that was my hope! I already found the connector in the service manual – thanks to @raymo –, it's what's in the tweezers in step 23. Then again, looking at all those steps before step 23 (ok, I obviously can leave the battery alone), the disassembly looks more complicated than I would have liked... Which made me try something else right now, before starting the disassembly: applying substantial pressure with my thumb on the back cover at the exact place where that connector must be underneath. And what shall I say, for the time being the camera is back working! 🙂

In principle, yes. Note, however, that some hardware components are likely to never be supported by open-source drivers within the realistic lifetime of the Pro1. For orientation: The Nokia N900, a relatively popular hacker's phone from 2009 (!), still has only 80-90% of its hardware supported by the mainline Kernel (personal estimate). And that's despite the fact that it originally shipped with an OS that was quite "open" compared to today's Android ...

Well, not quite (as we discussed above). With Lineage you get the Android framework fixes from the AOSP security bulletins, but no patches to the Linux kernel or the binary driver blobs, as these are supposed to be implemented and distributed by the SoC manufacturer. That's what LineageOS calls the "vendor security patch level". As you confirmed yourself, that one is stuck at 04/2020 in LineageOS, too. It must be, as the binary bits are taken directly from Stock.

Some do stick out a bit more than others but I believe in also using a good case. Good cases are often and big as the plug so with the case on it is way less noticeable if at all

I think the connection with mainboard is deattached. It happen to me after I've dropped my phone. You have to disassembly back cover and reattach it.

Oh, and Fidor Bank just answered my support request, apologized for not supporting my phone and changed the account from pushTAN via app back to mTAN via SMS, even though this isn't officially available anymore. So while this isn't the best of all possible solutions and will only be supported, as they say, for a limited time, for the time being I can now do everything with the Pro1! And the Moto Z3 Play can finally go back into the drawer, as soon as my employer's fine tech support people will have bound my Pro1 to that VPN token account... 🙂

Solved it. It probably wasn't Magisk itself but an incompatible module that was still installed. Moved everything that looked Magisk-related (find / -iname '*magisk*' 2>/dev/null, same with riru) to the sdcard, rebooted into recovery, sideloaded Magisk-v23.0.zip and it works now.

No troubles with Magisk 23.0 and the 31May update here, so I suspect something went awry with making that big of a jump.

Not resolved, no answers yet. dirty company