Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by Name_not_avail

  1. 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.
  2. 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.
  3. 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
  4. 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
  5. 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
  6. 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.
  7. 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.
  8. @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
  9. 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!
  10. 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?
  11. 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?
  12. 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.
  13. 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).
  14. 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.
  15. 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!
  16. 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
  17. 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
  18. 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
  19. I just tried logcat, but there are no interesting messages related to HDMI. It's a really short output log, nothing like as detailed as what I expect dmesg to look like. That said, unfortunately I was not able to replicate the navigation bar glitch again when plugging in the HDMI cable, so logcat wouldn't have picked up anything interesting anyway for me. Disappointing, but still I'm hopeful something comes of this in a firmware update.
  20. FWIW, I tried connecting my Pro1X to a USB C - HDMI adapter hub, where HDMI always output works with my Galaxy S21 5G as long as put an external power source to the USB hub. The first thing that happens on the S21 when I do this, is that a new symbol appears on the bottom navigation bar, referring to display controls relevant to HDMI. Interestingly, a somewhat similar thing happens to the Pro1X when I first plug it in to the HDMI adapter hub. The "auto rotate" symbol briefly flashes at the bottom right of the nav bar (to the right of the square), but then immediately disappears. If
  21. Thanks very much for your help, all. You put me on the road to figure it out, without flashing and without even doing a factory reset. I had installed Button Mapper, version 3.09 (current version) on both the phones, and used it to disable the shutter button on the bottom right of the phone. Once I uninstalled Button Mapper, the physical keyboard behaved as expected, and the question mark key worked again. So I guess there's no free lunch at present. I can choose to avoid all those accidental triggerings of the camera button, but only at the cost of losing some of the fun
  22. No worries, Hook. Thanks for the reply, if only to bump the thread! Here is a photo (taken on an inferior device, ha!), of the Pro 1X keyboard. So you see that it would be kind of weird to have to hit a key combination to get the question mark. I would have expected the semi-colon to be CTRL-L, but that gives nothing at all. The semi-colon is created by pressing the "?" key.
  23. Thanks, but that doesn't work. I have tried holding each of the following keys with the "?" key, and none of them results in a "?" Caps, Shift, Ctrl, yellow arrow, "F", Alt, Sym So there's at least two 1x phones like this, maybe more (all?). Did the Pro1 have a separate "?" key? The Pro 1x does, which would make it strange that it's necessary to do a key combination for it.
  24. Does anyone have their question mark key working on the physical keyboard on the Pro 1X? I have tried both US and English keyboard layouts, on both my own and my wife's Pro 1X, and I just get a semi-colon when I press the ? key. Tried it in several apps, but always the same issue. Also, I can't seem to make the software keyboard stop popping up when I open the physical keyboard, but it's usually just for a second or two before the prawn realizes I'm using the physical keyboard. Hopefully this is addressed in an OTA update, if these are universal problems. The physical keyboard
  • Create New...

Important Information