Jump to content

spam71

Members
  • Content Count

    46
  • Joined

  • Last visited

Community Reputation

43 Excellent

Recent Profile Visitors

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

  1. I tried even older firmware (first version of fastboot restore), and the problem is there as well. I cannot register a single fingerprint. I'm afraid it's hardware related issue, but don't want to send the unit to repair again. I suppose that before fxtec can fix it, Astro Slide 5G will be already manufactured. 😉
  2. Hello guys. My problem is exactly as described in topic. When I try to register fingerprints, a screen with location of fingerprint sensor is displayed. When I touch the sensor, phone vibrates, so the sensor's working, at least it senses touch. But on next screen (asking to touch the sensor until I feel vibration) nothing happens. Pressing power button off and on doesn't help. After reboot, when I try to register fingerprints again - it's exactly the same. I tried different versions of original Android, tried also LOS - no difference. I'd like to mention, that the unit I have now is
  3. Hello. Does anyone have newer booi.img files from updates later than 2020.03.04? Or is it possible to install magisk using older boot.img files? Thanks in advance.
  4. Pro1 under LOS is great. Unfortunately just after I dealt with most issues (especially volume tweaking and forcing 24-bit headphones output), USB port broke I now I'm waiting for releasing lockdown in GB - support/repair center doesn't work until then.
  5. I've got a problem. Today USB port became loose and phone's not charging. I don't remember any serious force applied to port. It looks like soldering wasn't strong enough. What should I do now? Am I able to dismount phone myself? How to do it? Maybe USB port has only to be soldered to PCB, but if not, where to get spare parts? How to use warranty? I really like this phone, even it has some stability issues, but I didn't expect it to break with no obvious reason.
  6. Thanks @Craig! I couldn't play any games on nds and psx emulators, I thought it's caused by issues with Pro1 keyboard driver, but it was SwiftKey's fault. After I switched to LOS keyboard, everything's good.
  7. It's much better on current LineageOS. Headphones output is still much too loud, but at last earpiece is usable.
  8. I tested both official and LOS for quite a long time. Right now LOS is much better, has great support, has less issues, is fast and at least as stable, as official build. Good job tdm! Thanks to your work this phone gets almost perfect. Because what would be a great hardware with poor software? The answer is stock Pro1. Thank you very much. If there is a way to repay you for your work somehow (ie paypal account), please let us know, because at least me, I'd be glad to offer some money as donation for your effort.
  9. I've just found out that that's one of patches done by Magisk Audio Compatibility Patch module. I had it installed, and that's why I didn't have problems with distorted sound. Right now I tried to disable that module, and change files you mentioned manually, but they are read-only even with root priviledges. Vendor directory can be changed only by flashing boot image? Or is there any other way? I'd try to change other parameters also (want to have 24-bit default output to get rid of digital noise while listening with headphones at low volumes).
  10. Yes. Experienced the same. But maybe it's just a coincidence, because fingerprint sensor fails definitely too often. [edit] I mean problems with fingeprint reader are erratic and unpredictable. I miss reader in Key1 space bar. It was perfect.
  11. I have another request. In Pro1 both shift and both ctrl keys send the same keycode, so it is impossible do differentiate between left and right shift and ctrl. Could it be possible to assign different scan codes to be able to distinguish whether left or right key was pressed? It's useful for some games (ie Zen Pinball) and it would widen possibilities of keyboard customization (pressing one modifier key could take other action from the other modifier).
  12. For me, to deal with crackling sound, I have to install Magisk 'Audio Compatibility Patch', and I suppose the key is increasing audio buffer, but that is just a guess.
  13. I had problems with definitely too loud speakerphone and earphones sound on voice calls in stock firmware. In lineageos sound volume is lower - bearable, also in latest test build 9. I'm not sure if it isn't a hardware issue in your case. Also I found out that even full stock recovery flash doesn't erase everything - one time 128 GB of internal storage melted down to 16 GB - factory reset from system menu helped. Maybe it's something similar in your case?
  14. I found that Magisk + Riru's EdXposed doesn't pass SafetyNet check - so some apps (ie nfc in my banking app) don't work. In contrary, TaiChi exposed passes SafetyNet. A downside is that there are only a few xposed modules versions running with TaiChi - but for example GravityBox is running well. And in their web page almost everything is in Chinese. 😉
  15. Mr Laska's right. His workaround solves cracking sound issues. The Magisk module is available from Magisk Manager - it's name is "Audio Compatibility Patch". I run it with LineageOS, also with Viper4Android 2.7 (installed as Magisk module, but not available from Magisk Manager). Installer demanded also "Audio Modification Library" module for multiple patches to work together. As I found somewhere on the internet, the issue is caused by too small audio buffer - crackles happen on buffer underruns.
×
×
  • Create New...

Important Information

Terms