Jump to content

EvilDragon

Members
  • Content Count

    58
  • Joined

  • Last visited

  • Days Won

    1

EvilDragon last won the day on November 17 2020

EvilDragon had the most liked content!

Community Reputation

142 Excellent

Recent Profile Visitors

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

  1. 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
  2. Hm, weird indeed. Maybe it has something to do with the Bluetooth protocol used... Which one age you using?
  3. 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'
  4. Yep, I'm a retailer and will offer replacement screens and repairs ;D
  5. 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
  6. 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 😄
  7. 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 😕
  8. 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 :)
  9. 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.
  10. Has anyone found out how to enable the keyboard backlight? Or is this a missing feature?
  11. Just flashed it and can confirm that Magisk works fine as root 🙂 Now, onto restore all my apps... 😄
  12. 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.
  13. 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 🙂
  14. Sure, unless I forget it, I can do that within the next few days.
×
×
  • Create New...

Important Information

Terms