EvilDragon

Oh, dear... I had multiple broken screens myself until I modified a case... this worked so good that the screen never broke again, even though I regularly throw it on the ground. I don't have a screen protector. This is the case I use: https://www.amazon.de/gp/product/B07BQQ8JCC/ref=ppx_yo_dt_b_asin_title_o02_s00?ie=UTF8&psc=1 You only need to cut out the credit card storage case that's inside the case (then it has the perfect size for the thickness of the phone) and cut a few holes in the silicone so you can access all ports.

Https://www.dragonbox.de if you want to get it from Europe..

Aaaand done! Here is the replacement display: https://www.dragonbox.de/en/spare-parts-tools/lcds/fx-tec-pro1-replacement-lcd And here the service, in case we should do that for you (display included in the price): https://www.dragonbox.de/en/repair-mod-services/after-warranty-repairs/fx-tec-pro1-display-replacement-service

Yeah, I've got around 20 - but didn't put them in the shop yet. Will do that later today. II'm based in Germany.

Anyone else here having a very bad reception with LOS18? I can't even do phonecalls inside my house (I do remember last year I had similar issues, probably with LOS17). With AICP it works perfectly fine even deep inside the house, LOS18 doesn't even work reliable standing right at an open Windows.

I am having that issue as well - and it drives me insane. On lineage OS, the call screen appeared, I could see who's calling and pick up the phone without any issues. On AICP, most of the times the screen stays black and I need to press the power button to make it appear. If I press the power button too long, the camera comes up without any way going back to the call screen... I missed quite a few calls because of that even though I had the phone right in front of me... Does anyone know how to fix that? Maybe it's a setting? Otherwise, I hope AICP R won't be too far away and ma

Hm, weird indeed. Maybe it has something to do with the Bluetooth protocol used... Which one age you using?

I noticed one issue, but I'm not sure if that's an easy one to fix as it seems to be common with other Android versions as well: The microphone of a Bluetooth headset only works for phone calls. Whenever you use some other app (audio recorder, WhatsApp, Skype, etc.), the microphone is not available - it only works with normal phone calls. There's an app called "Lesser AudioSwitch" which can force the apps to use the bluetooth microphone - but it's a bit flakey (doesn't work all the time) and it seems to switch back to internal speakers as soon as the microphone is enabled. It'

Yes, please send me a PM 🙂

Yep, I'm a retailer and will offer replacement screens and repairs ;D

I'm not sure if it's for newer systems, as the driver is dated from 2019. Maybe it was too sensitive for the screens they got while it works fine with the ones that have a bit more insensitive edges? I don't have an older display here so I can't test right now if it still works. It probably works but might react even more to edge taps than the current one. Probably not a problem if you're using LineageOS or AICP, as there you can set you own margin, but that's just my guess. I'm not using stock, but I don't think it will break SafetyNet. To me it sounds like it's installed inside t

Thanks - the screen was fine. I had 20 of those, so I could test a few 😉 But an update: A fellow member sent me the instructions and files he received from F(X)Tec - and it worked fine! And the best thing is: It's really painless if you have a rooted OS. No debug firmware needed, no reflash, no wiping of data. Just one single APK, a firmware file and access via adb to change some permissions for the touchscreen driver files. So if anyone has the same issues: With a rooted OS, it takes 2 minutes to fix it 😄

Heh, and here I am... unbootable state and I need backup my userdata before reflashing. Sooo... yeah, TWRP would be nice here 😕 EDIT: Okay... managed to get it back into working state this time... phew 😕

Has there been any news here? I would also love to have the possibility to decrypt my userdata if the system is in an unbootable state. I like to experiment a lot, so this could easily happen :)

Hmm, and it seems the haptic feedback for the virtual keyboard keys can't be deactivated. Or it has a hidden setting for that which I didn't find yet.