spam71

In my case it was definitely bad connection issue. If it was software, why would popping come only from one speaker, and why would it change on movement of USB cable plugged just by the speaker? But I'll definitely let you know if anything changes.

Hello. As I mentioned in some other topic, I received my Pro1X 2 days ago. It looks great, keyboard is even better than in original Pro1 - layout much closer to normal, much more tactile. As with every qwerty phone I started from rooting, and tweaking keyboard to Polish language (by the way, if there are any Poles here, I'd like to share my keyboard tweak as a Magisk module - it really makes a difference!). Unfortunately I encountered a problem with bottom (right) loudspeaker. Sound is intermittent, sometimes popping, sometimes sounds like reversed phase. It helped for a while w

Hello folks. Unfortunately, it's the same song again. I've just received my brand new Pro1X. It looks great, I find keyboard much better than in Pro1 (at least normal position of bracket keys, much better tactile feel). But the right speaker is producing distorted sound, sometimes popping, sometimes silent. Since the sound changes when I press firmly the cover where the speaker is, I'm almost sure the problem is due to poor electric connection. It's the same story I had with Pro1 - fingerprint reader was now working at all, but I gave up and didn't send it for repair for months.

Hello. It's like threads gravedigging, but just a week ago I finally brought my pro1 to life by replacing a broken display with Ulephone U one bought on ali (and it didn't require any "firmware update for the touch function to work correctly"). But the point is that just a few moments ago I think I managed to solve problems with too loud handset sound volume and distortion. I replaced "/system/vendor/etc/mixer_paths_tavil.xml" with a file from latest Google Pixel 2 LineageOS (it shares the same MSM8998 CPU). I didn't have much time to test it thoroughly, but sound seems to be much better.

It doesn't really matter if it ends with 622 of no Pro1 X at all, this means the end of fxtec. After changing promises with money collected, I don't suppose there will be many who can trust fxtec again. Me not. And since we are only ones who were willing to pay so much for a niche device, fxtec might be finished. They won't find more naive customers, especially when there are still more serious manufacturers. After a series of problems with Pro1, now that's Unihertz Titan which is my daily driver. With a lot of compromises, but the most useful mobile I had ever had. I waited for Pro1 X, but no

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. 😉

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

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.

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.

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.

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.

It's much better on current LineageOS. Headphones output is still much too loud, but at last earpiece is usable.

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.

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).

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.

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).

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.

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?

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. 😉

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.

Pro software is in beta state. Even crucial features. For example its awfully loud on talk through handset and through earphones. Only bluetooth earphones volume can be lowered enough. Priv's soft was in much more mature state. It's quite sad, because Pro1 has amazing hardware, but our Chinese friends messed up with soft.

@tdm Hello Since you're The Pro1 Developer, do you think it might be possible to add kernel support for "battery idle mode" - I mean the state with charger plugged in, when battery is charged to some level, for example 80%, but is neither charged up further nor starts discharging - phone takes energy from charger, but not from battery. There are apps that can utilize this mode to preserve battery life (i.e. ACC: https://github.com/VR-25/acc/ ACCA: https://github.com/MatteCarra/AccA). As for now, with these apps, Pro1 stops charging at given threshold, but instead of keeping this

Hello. Does anyone know how to get r/w permissions for /system? I tried to replace keyboard *.kcm file with one for Polish letters, but I couldn't mount system r/w even though I had root privileges.

Guys, do you know how to install Play Store in SailFishOS?

I think I was too fast to post success. Even if this app does something, it doesn't fix clicks in games, and also is not required for 24-bit output. If only I could lower headphones and handset volumes on call. Under lineageos they're lower, but in contraction you cannot raise volume. This phone is a very good hardware released with beta software.