Name_not_avail

Thank you. Based on your reply, I tried it on a PC with a pretty fresh install of W11, USB 3.0, and no history of USB phone connections at all. Worked fine. Must be some weird driver issue with the W10 and W7 boxes. Thanks!

I plugged the 1x into a Windows 10 PC to grab some files from it, which is something I rarely do, and probably have not done since I reflashed to the stock GMS-less ROM. So there have doubtless been some Windows updates since then. Now I can't select "USB file transfer" on the 1x and get any connection to the PC. Device Manager on the PC shows a USB Composite Device with the error, "This device cannot start. (Code 10). A device which does not exist was specified." I then tried an "ADB devices" command, but no connnection. Then I selected USB PTP on the 1x, and like magic it con

@HookWhat batch is your 1x, and when did you receive it? Both of mine came in the first release, last August. Your connectivity experience is wildly at variance with mine. The GPS on both my 1x phones is so slow to get a fix as to be completely unusable. Here's an idea, in the interests of science. I will mail you one of my 1x phones, and you can do a comparative test of it with your 1x. That way a lot of variables could be ruled out with respect to sim card, tower location, band use, etc. if you get crap connectivity related to your 1x, science will be advanced! I'm willin

I am starting to reach that pessimistic conclusion, too, but I surmise that the glitch with the microphone not working until speakerphone is toggled, is a software problem amenable to an update. They seem like two distinct problems. If they could even fix just that microphone unreliability aspect of it, then I might have the patience to pull it out of the drawer and try it as a GSM or VoWiFi phone where that's feasible.

FWIW, i just did a long return drive from for almost the entire length of Interstate 5 on the West Coast of North America, Los Angeles to Vancouver BC, using my T Mobile sim card. i have never been able to rely on my Pro 1x, so left it in a drawer and used another phone with LTE Discovery running and logging. The following bands are the full scope of LTE bands that my 1x would have had access to, anywhere along the Interstate 5 corridor: bands 2, 4 (also 4 roaming on Telus in Canada), 12, 17, 66, and 71. The 1x specifications page does not list band 66 or 71 as available, but b

Just wondering if anyone has this issue, or could advise. I have a set of HyperX bluetooth headphones,and they pair easily to the phone, but there is no audio. The phone keeps "suspending" them and defaulting to its own internal speakers. I enabled a Bluetooth snoop log in the phone, and looked at the .cfa file with Wireshark, and I see that the phone keeps sending "Suspend" commands to the headphones as soon as I start to play audio. So in the log I see the phone as source issues "Sent Vendor dependent: Interim - RegisterNotification - PlaybackStatusChanged - PlayStatus: Playi

Nope, apparently not an option with this sim card. I guess I go back to manually switching to GSM Only when I hope to be able to receive calls, and then manually switching to LTE Only when I need to use data. Very clunky. I suppose it could be automated with Tasker or a root script in places like this that still have both GSM and LTE operational, but my hope is for the new Fx Tec firmware to address this glaring deficiency instead. And obviously places like the USA that no longer have GSM are screwed for voice calls on the 1x.

That does not appear to be the way these two 1x phones operate. If I allow all network types, then it prefers LTE for voice, but it doesn't drop back to GSM if it can't connect by LTE. It will not work for voice calls 90% of the time, whether taking or placing a call. Allowing all network types has the same effect as allowing LTE only... ie. it becomes a small Android tablet with a keyboard, not a phone.

Indeed @claude0001and @xhajt03you are both correct. Normally I use my 1x in the USA or Canada with a T Mobile (USA) sim card. In the USA, there is no 3G option anymore and voice calls are unuseable with the 1x on LTE, but with the same T Mobile sim card the phone defaults to 3G roaming in Canada and voice calls are suddenly useable. When roaming in Canada with my T Mobile sim card, I do not have the option to select LTE, so I am stuck on GSM because of the T Mobile roaming contract. However, I am currently on Grand Cayman with two 1x phones, one on 2.1.2 firmware, and one with versio

So one more comment about comparing firmware versions 2.1.2 and 2.1.5 and GSM vs LTE, if a Pro1x is set to "GSM Only", then it sucks the battery down notably faster than if it were set to "LTE Only". I understand the current firmware update boffins were focussed on battery draw instead of inability to carry voice calls on LTE, and I will now suggest these are problems that are two sides to the same coin. There is no difference between 2.1.2 and 2.1.5 phones in this battery draw regard, "GSM Only" always hits the battery harder. Frustrating to see some very acceptable data speeds

So I brought one Pro1x with 2.1.5 GMS-less, and one stock 2.1.2 Pro 1x, to the Cayman Islands, using a new Flow sim card in each one. Flow operates both LTE and GSM network service. After extensive trial and error, I am sorry to have to confirm that the only way to get voice service with these phones on Flow is to lock out LTE and select "GSM only". Allowing the phones to connect via LTE showed good signal strength, and SMS and data worked, but voice calls were unable to connect about 90% of the time. On the odd time that LTE would connect, the quality of the voice call was much bett

The very long power button hold did not work the first time I tried it. Only after twice doing the "3 fingered salute" I described, did the power button hold (alone) suddenly work. Something weird about those brief boot attempts with the 3 fingered salute, seems to have enabled the long power button hold afterwards.

I have had the phone suddenly go black brick for no apparent reason, after leaving it on the table with a 70% or better charge. In my case, what worked was holding all three buttons (both volume and power) for about 30 seconds. That seemed to start a reboot cycle, as the Android image flashed up for a fraction of a second, but then stopped. I did the same again, and again I got the brief Android flash, then nothing. I then held the power button alone for about 30 seconds, and the phone booted normally. It showed 76% battery or something at that point. Good luck.

@EskeRahn please move this post if appropriate, I know there has been thread drift in the last 6 posts but I didn't find another thread where it seemed to fit, and I have what I think is useful info to share. I have now updated to build 2.1.5, but because I am still roaming on Canadian GSM service, I won't be able to say whether LTE reception has been improved for a couple of weeks. The most noticeable improvement of this build is that touching the fingerprint reader does not cause wild scrolling behaviour the way it did in build 2.1.2, so that is a much appreciated improvement. Be

I was just in the process of the factory reset when you posted. Score, it's reading normal again. If I could hit "Thanks" 10 times for the speed of your reply, I would do so. Thanks again!

So I followed that guide, and flashed the phone with Pro1-X_Stock_Android_OS_GMS-less_v2.15. But now the phone shows a storage space of only 8 GB. It physically has 256 GB. Any help here? WTF?

You have a point there. Is 2.1.5 available for downloading anywhere obvious, or do I have to get an invitation to a Telegram group, or some other similar quasi-secret source?

As I understand it, that preferred network type setting would lock out LTE. So you're not ever using LTE with that setting. I am still on the original build 2.1.2, and the LTE connection is appallingly bad, but it seems fine on GSM. The big problem is that in the USA, GSM is almost entirely deactivated and LTE is all there is, now. IIRC there are some mixed reviews here about whether the beta 2.1.5 build improves anything for LTE on the Pro 1x, so I haven't bothered to update yet. Hopefully Fx Tec is still working on an OTA update that fixes the LTE problem for everyone.

Geekbench 5 results on my Pro 1x are here: https://browser.geekbench.com/v5/cpu/18809529 The biggest downgrade is the unusable microphone while making LTE voice calls (but to be fair I never had a Pro 1 to compare that problem with).

I want to add some observations about microphone performance here, because I now have experience with the Pro 1x on both sides of the Canada/US border, using a T-Mobile (USA) sim card in the phone. The microphone volume is terribly poor when trying to call through the T-Mobile network in the USA. People can hear me only very, very faintly unless I switch the phone to speakerphone mode, at which point the microphone becomes normal. My voice is so faint that I cannot leave a voicemail for anyone (their system just clicks off), and many people just hear dead air when they answer me.

NB - I just tried to do this, and the command "fastboot oem off-mode-charge enable" does not work. It generates "FAILED (remote: Invalid input entered)". So instead, I tried "fastboot oem off-mode-charge 1", and that worked. I just switched off the phone and plugged it in, and it did not boot into Android. It just gave me an image of a battery with percentage of charge in it. Success!

Holy cow, this should be a sticky at the top of this forum page!!! I was surprised that my 1x turned itself on every time I tried to charge it when it was currently switched off, but I just found that quirky without understanding the implications of it. If I understand you right, it is not possible to charge the phone when it is switched off, unless this default setting is changed. And further, if the phone is off and the battery is discharged to the point that the device cannot power up when it's plugged in to charge, then it simply will not charge in the "off" state. Wow

I don't see how I could have been in the wrong fastboot screen. I didn't touch any of the buttons on the phone to change anything. The phone was completely stock, and I followed the PDF instructions to the letter, with one exception: I was using "Minimal ADB and Fastboot" to issue the terminal commands. That's been on this PC for a few years for other Android projects, but I don't see that being likely to change anything. Maybe, I guess. I will be interested to hear from @Casey about the difference between slot a and slot b, and whether I have screwed something up for future

NVM, I fixed it.

So I eventually decided that I might as well root my PrawnX, and tried to follow Casey's instructions here: https://community.fxtec.com/topic/3690-pro1-x-rooting-with-magisk/?tab=comments&_fromLogin=1 I got to the point of flashing the patched boot image back from my PC to the phone, and hit an error: So then I did this: Made me a bit nervous, because Casey's instructions of the PDF suggest that the file flashes to boot_b automatically. But whatever, I went with what getvar returned, and entered this: Then I did the "fastboot reboot", and voila, the