Hook

If I'm not mistaken, I don't think they can and still release properly certified Android.

You could try uninstalling apps one at a time, ones that aren't challenging to set up and see if the keyboard works okay afterwards. A long process possibly, but maybe you can guess at possible culprits.

There is no official set of downloads yet. @EskeRahn has rounded up guides, official OS and alternate OS from various threads in this forum which has pretty much everything currently available for both the Pro1 and the Pro1x., but it is not official. Hope this helps.

I'll just note that I never do this. I don't trust Google back ups, precisely because, especially with a new phone, I worry about bringing in some element that is no longer compatible. I don't enable Google backups and I never allow Google to reinstall apps on a new or wiped phone. I will use app backups, so I'll let Nova use a saved Nova backup, and I will let Aquamail import it's own account backups, etc. I just don't trust Google and will do the extra work myself to retrieve and set up apps. Often results in house cleaning as I realize I don't need certain apps. 😄 This is also wh

I personally believe that we will. This is mostly hope, not evidence based, but in my experience, while they may take time, FxTec always delivers. But I'm sure I have a reputation for being overly optimistic. 😉

Please do keep us posted, but might be good to do it in the dedicated thread here. Just indicate that you have the Pro1 X and not the Pro1.

Please share details on connecting to Verizon-- did you use a method posted here for the Pro1 or did you do something else? I assumed you had a sim from a previous Verizon phone that you used? What steps did you take. I'm interested in whether there's something about the Pro1x that makes it easier than it seemed to be on the Pro1. Do be aware that it might not last. Verizon is becoming more aggressive about blocking non-approved phones, especially as they take down their CDMA network. Keep us posted if anything happens.

I understand the concern and I don't want to tell you not to worry because stuff can always happen. But there are a lot of good solutions in this thread if you really want a phone like this. I'm someone who never uses cases or screen protectors (it's a quirk that everyone has tried to talk me out of since my Palm PDA days). The only thing I did for the Pro1 is to put a matte black textured skin (I used one from Dbrand that was intended for the Note 10) because it provided just enough texture that the phone doesn't easily slip from my hand. Maybe I'm just not rough enough on my devices, 😄

If you really aren't interested in the phone, leave it closed box. As @EskeRahnsaid, FxTec will honor the warranty for the new owner. If you don't know if you want the device or not, but are worried that open box and tested will lower the value, I wouldn't worry. Take it out, try it out, see if it might be something you want after all. I don't think there is any reason to charge less for open box and tested (again, the warranty will still be good for the new owner), and, who knows, maybe you'll change your mind. 😉

On the Pro1 QWERTY with Stock Android, unless Finqwerty was installed, the keyboard layout was required to be set to "default." Has that changed? I'm assuming so, but just checking. I can't wait for that new version of QWERTY(assuming it works 😄 ).

Sorry, I haven't gotten my Pro1X yet and I haven't seen a good representation of the new keyboard yet, I should also ask if you are Qwerty, Qwertz or some other layout. I'll leave this for someone with a Pro1x rather than jumping the gun.

To get the question mark or or forward slash, you have to hold down the yellow arrow key (also referred to as the Fn key). I'm assuming this hasn't changed from the Pro1.

I'm sure these are linked somewhere way back in this thread, but these are still available, it seems, so for newcomers: https://www.amazon.com/fitBAG-Tailored-Germany-Microfibre-Cleaning/dp/B07XHN486C They are quite nice. I have one, though I never use it (I don't like or use cases or screen protectors and haven't since my Palm days). Very nice material, gives some padding, easy to pull the pro 1 out, yet holds pretty well. Pro1(X) won't slip out unless you hold it upside down, although I have a slightly textured skin on the back of my Pro1 so I am not sure with the unmodified bac

Hope does strange things to perception. 😉

Thanks to @mosen, this link... https://www.protectionfilms24.com/article/2x-brotect-flex-full-cover-screen-protectorfxtec-pro-1-x-5145664.html

Sorry, we'll just have to agree to disagree. Where you see "intentional false information," I see overly-optimistic estimations, which, when they don't pan out, they get beat over the head with it. No wonder they kept communication less frequent until they got close to a real production phase. And of course hardware "quirks" would affect software, if the software has to use that hardware that is being fixed. My guess would be a that pre-production models went out in June. I don't know this, but that seems to be about when hardware tweaking was mostly done and the big concern was g

I assume you have gone to Settings, apps, Advanced, default apps and specifically set your "Home app" to Nova? I don't usually have to do that with Android 11 and before, but I did have to do it with Lineage 19, so I wonder if Google has changed something up.

Okay, an hour later 😄 ,,, The OTA update to the 20220615 nightly went smoothly (took the full hour, which is, sadly, normal). Has the 05 AUG security patch. Only odd thing is it added a second time and date widget to my Nova Launcher and asked me to set up Google (which I declined). Never seen those things happen after fist install. So far, everything seems good.

I'm trying this now just OTA. I'll report back my result (but you know this takes a while, lol). You mentioned something about a 3 part flash. I was getting that from AICP-S. AICP-R and Lineage has always given me a 2 part flash when flashing from recovery. Don't know if there's any relationship.

Might also see if @Sean McCreary has any clues he can give us.

For what it's worth, Key Attestation" on my Pro1 with Lineage and Magisk shows "Not supported by this device." Not a big surprise. It has had Lineage or AICP on it since early 2020 and I've never gone back to Stock, so of course I've never noticed. It will likely be the same with my Pro1x. I will probably keep it on stock until Lineage is available. I plan on using my Pro1 as my experimental device (read that learning device). If I find a setup I really like and is stable on the Pro1, then I will try to bring it to the Pro1x. I will see if I can backup the persist partition when I get

This is how it was with the Pro1. Took me a while, but then it became second nature. Lift slightly in back and push, as @brunoais mentioned, is easiest. I can now even do it one-handed (though I don't recommend that if you haven't done something to make the back less slick. I have a skin on the back of mine,).

I believe we do know the screen assembly is the same

First thing I did on my Pro1 in 2019 😄