EskeRahn

First of I can confirm that the bug is not ALWAYS there - I have no idea what triggers it.... Yes I agree, Mono would do just fine for me too. Turning down the volume sort of do that IF the source is Mono. But if the source is Stereo we get only one channel so not a too good workaround. The big question is what is going on, and how they can fix it.... A wild guess is that it could be related to some circuitry intended to avoid feedback-looping between mic and speaker during calls. Obviously it should not be active during ordinary playback. Just my wild guess though.....

I remember very early on on the Preproduction union of the Pro1, an explicit factory reset was needed after the flash, to report the correct amount of memory. Could that be similar? Or it could be the lack of a backup/restore of the persist partition, mentioned in other threads that are making problems here too?

I'm pretty sure @esialb has a very valid point here in that scratches in the surface may lead to the glass as a whole being weakened compared to an intact display. Think of what you do with a normal glass cutter and plain glass, you basically make a scratch in the surface, and a break then easily occur along this line. And though Gorilla Glass is more complex it is still glass, so some of the same behaviour may be expected.

I have seen the same for the Pro1. Fastboot is a LOT more picky on the connection. Often a USB2 works better than USB3 (!) So in general I suggest to try various cables and various ports on the device. If that does not work, try with a hub I was completely unable to connect using my Lenovo Yoga X1 gen 6 20XY but using a port of the front of their ThunderBolt4 'docking', it works like a charm, (even with a cable with a magnetic connector) And on top of that the driver can bee an issue too.... See also this thread

It is NOT a push parallel to the screen. Please see this

As other have already said, The pro1X was INTENDED to be a Pro1 with very minor adjustments, and additional roms available in collaboration with XDA. And yes it would have caused less confusion if they after they were swindled had also decided to call it e.g. Pro2. And I agree that the text ought to be changed, e.g. With the Pro1 X you have the flexibility with the unlocked bootloader enabling you to loadother popular OS’s such as Lineage and Ubuntu Touch. to With the Pro1 X you have the flexibility with the unlocked bootloader enabling you to loadother popular OS’s such

I agree. One last thing could be to try to hold power and volume down pressed while connected to powered, as this should make it boot into the bootloader menu, that is more likely to work than a full boot, IF it is the battery that is depleted, and not something more severe that has gone awry. ADD: It is a silly default, that it is NOT set to charge, but boot when power is applied in power off state. I will STRONGLY suggest anyone to do this: adb reboot bootloader Wait for the boatloader menu fastboot oem off-mode-charge 1 fastboot reboot (the adb/fastboot package

Indeed. I struggled with the Pro1 initially, especially holding it in portrait in the left hand (for operating with the right), But as I almost immediately started using shells, and then flip-cases, the problem disappeared. But without a case it is as aPple would put it: "You are holding it wrong" *LOL* It will simply take a while to getting used to a grip avoiding inadvertently touching the fingerprint-reader. I'm pretty sure that if you delete all you fingerprints (Setting►Security►Fingerprint) it will effectively be disabled. The slick design where the fingerprint-reader is almo

Thanks, i know next to nothing on edl. Could you please make a full guide of how to get edl, And how to use it for backup and restore of the persist. Preferably in a separate thread, I can link to.

If not connected and you hold volume down and power you will get the bootloader menu (that accepts fastboot commands from a pc if connected), One of the entries in this menu (cycle with volume up/down to see in the top line) is Recovery. Booting into Recovery gives you a new menu from where you among other things can wipe the userdata and sideload (with the adb sideload command on a pc)

not recovery but the fastboot mode. (From where recovery can be selected among others). You will see the bootloader menu, somewhat similar to this.

If you disconnect, and hold down the power for a long time - say 10s, do you get anything on the screen? You should see a logo. Unless the battery is completely depleted.

Added 'something' at the top of this on backup of the persist partition. https://community.fxtec.com/topic/3207-various-roms-available-to-the-pro1pro1x-available-for-download-links/ Please correct me if what I wrote was wrong. @mosen, @ducksoup, @steeb and I will have it changed ASAP.

Yes, but note that this is a user-to-user forum where FxTec only occasionally are active. But sure would be preferable if they provided the info. I will add 'something' for now....

Maybe you should make a separate thread on what to do switching FROM stock Android, that I can link to in the ROM thread? As this seems generally crucial/useful.

Not ALL parts are the same, but many are, would be nice with a list of what is identical, and what is not..

I'm pretty sure that the popping sounds are related to the clipping, so no clipping means no popping I tried it with some talk radio, and gone at max vol, and on the other hand when the level is below about 50% all sounds (including pops) seems completely gone from the right side/bottom speaker

Sad. Then something is stuck between the case and the button. So the only thing to do is to have it opened and have whatever it is removed. So await what support suggest you to do. IF they suggests you to open it your self, and you feel comfortable doing so, then please take (and share) some photos doing so, as we have only the FCC images of the interior of the Pro1X, there should be some visible differences compared to the Pro1.

With newest platform tools gives fastboot: error: Unable to get max-fetch-size. Device does not support fetch command. On both Pro1 and Pro1X

Not that it is an actual fix, but is a functional workaround: If you use a shell (or flip) case, the chance of accidentally triggering the fingerprint reader is practically eliminated. (There is a loooong thread on (primarily) DIY cases here, a short summary is that any soft case fitting the Huawei P20 Pro, is likely to be a good base for a Pro1(X) case. I also made my own thread here.

Looks fine to me. One minor detail. Flashing AICP, the 47% blah blah click yes is on the main zip, and does not appear again on the Gapps zip. So Lineage and AICP acts slightly different here.

The Pro1X stock Android comes with a preinstalled FactoryKit app. (Similar for the Pro1, See this) It is not launched the same way as on the Pro1. Actually I have not found the correct way to start it! Though by using an app like "Activity Launcher" and selecting a shortcut for "FactoryKit" sub-item "FactoryKit", I can launch and get the following list, and some can be started, and some crashes direcrly. Launching it the above way make the app crash or halt after the test that works are finished, so you are likely to need to swipe it away from the app-list after ea

Sounds like a software issue. Will try if I can reproduce... ADD; Yes I got the same (on a before retail sample) (Add II: Headset not affected by this bug)

It works on the Pro1X too 😀

I will highly recommend NOT omitting this tiny step. Remember that an OTA update swaps what is active between A/B so could easily become a mess Alternatively flash the boot image to booth boot_a and boot_b, so it is in whatever is active.