Jump to content

EvilDragon

Members
  • Content Count

    54
  • Joined

  • Last visited

  • Days Won

    1

EvilDragon last won the day on November 17

EvilDragon had the most liked content!

Community Reputation

139 Excellent

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Yep, I'm a retailer and will offer replacement screens and repairs ;D
  2. 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
  3. 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 😄
  4. 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 😕
  5. 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 :)
  6. 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.
  7. Has anyone found out how to enable the keyboard backlight? Or is this a missing feature?
  8. Just flashed it and can confirm that Magisk works fine as root 🙂 Now, onto restore all my apps... 😄
  9. Well, I did send them my email over a week ago 😄 So yeah... not that fast 😕 But thanks, I'll try the support section as well.
  10. Ooooh... nice 🙂 I prefer AICP to LOS as well, just found the thread 🙂 I wonder how a dirty flash from LOS16 would turn out... I'd backup everything before that, of course 🙂
  11. Sure, unless I forget it, I can do that within the next few days.
  12. As I have some apps that need root: Has anyone tried rooting 17.1? If yes, how did you do that?
  13. Unfortunately not. They look exactly the same, the silk on the PCBs is also the same. They have different batch codes on them, but that's pretty normal.
  14. I don't have a problem wiping everything, though it would be weird, as the driver should sit on one of the internal partitions and you should be able to reflash that one without touching the others. The bigger problem seems to be to find out what's wrong and how to get the fix 🙂
  15. Well, it's not a single screen, it would be a batch of screens. The ones I bought in March worked fine - but the new batch I recently bought has that issue. All of them, so it's not just one that is defective. Seems like this is a new revision - and the distributor told me it works fine on the Elephone U Pro. That seems to confirm that more recent batches have that behaviour. Maybe the screen was updated as it was oversensitive at the edges and that's now on top of the Pro1 own driver code to make it less sensitive. About dropping: I'm using a slightly modified leather case f
×
×
  • Create New...

Important Information

Terms