EskeRahn

If I recollect correctly we had similar reports in here on the Pro1. Though not as bad as @RichC73 reports.

Could be. But before opening I would contact FxTec ( https://www.fxtec.com/support ) and hear their opinion on the subject - as a user to user forum, it is never sure if FxTec sees a post (or even thread) in here.

I hope you are right. We will have to wait and see to we have more units delivered to see if this is for a specific unit, or a general issue. Though at the least for the Astroglide, radio firmware is bit more complex to update, according to the EE section of their update - it might or might not be the same for Pro1X.

I moved your post into this quite large thread, as the same covers and screen protectors should work equally well for both models.

(lineage-19.1-20220808-nightly-pro1-signed.zip on July 5 security patch installed smoothly using adb sideload and MindTheGapps-12.1.0-arm64-20220605_174313) Still with the keyboard bug introduced that messes accessibility apps (works on AICP R/S based on Android 11/12) see e.g. this.

Over at IGG, "Buffer Bear" was charged "UK. Duty of £51.45" so it seems to vary quite a bit...

The Pro1X was PLANNED to be a Pro1 eXtended with more ram, and changed key-layouts.... But after they were swindled, they had to redo the whole thing with a different chipset, and this is why the old code was supposed to have worked (almost) unchanged on the planned Pro1X, but will not work at all on the actual.

Well IF your unit proves to have faults and you have sold it unopened, you could clearly say to be in good faith, and any complaints be between FxTec and the new owner.

It should be fairly easy to sell it for more than the customs amounts to. What key-layout have you requested? The Pro1s have had a high resale value on e.g. ebay used. And if unopened, it should be even easier.

Yes let us hope they found a more serious and honest subcontractor this time.

If the double shift in LOS had activated caps-lock, so Caps key could release it also, it would be a lot less confusing, than release by a single shift. Currently if you click Shift and regret, you have to click TWO more times to cancel it (one to enter pseudo-caps, and another to exit). Had it required the two clicks on shift within say half a second to get pseudo-caps, it would be natural to after a slight hesitation a second click on shift just released the sticky.

I was trying to describe how to get things on the stock Pro1 (though I use FinQwerty on the Pro1). I expect it is related on the Pro1X, though somewhat different without the shifted layout.. On the Pro1 stock layout see the more complete descriptions also included here: https://android.onse.fi/finqwerty/#pro1 It also describes how to get accents for the stock layouts E.g. Alt+U followed by an e gives ë

Actually I just today found out that it is not as bad as the initially transition led me to assume.

Screenshot is indeed available, but it enters a mode where you can select what to save, clicking and dragging, and the default is NOT the entire screen. Until selected only a cancel 'button' is available. Once dragged both an accept and the cancel buttons are available.

...And you do not have to root it to try another ROM. Though you might need to, to trick some banking apps to work under e.g. LineageOS AICP-R is also an interesting alternative to LineageOS. The AICP-S is still very early, with some initial oddities. The keyboard-handling messed up in Lineage 18&19 preventing some accessibility dependant apps from working is a LineageOS only bug. These apps works fine on both AICP-R and AICP-S.

Now that is just an awesome workaround! Thanks. Though people should make sure to backup as much as possible first. as the workaround relies on the stock android failing to use the current userdata without destroying anything, and that might not always go so smooth.

Minor issue: Screenshot works a bit oddly, as it seems you need to mark the portion of the screen you want to copy every time. It could be me that just have not guessed how to easily get the entire screen,... (double tap does not work, gives a miniature cut of the rectangle between my two taps...)

I Just tried to reflash AICP-S on top of AICP-S, with NO factory reset, and this goes much better, though not 100% smooth. It still enters a boot-loop attempting to boot after the flash is done... BUT it eventually DO boot into AICP-S with things preserved from last time. 😁 It still present the splash screen that something is terribly wrong on boot... BUT after that, things seem to work fine (until you do the next boot). 😁 So though severe bugs they are NOT show-stoppers any more. You will still need a factory reset going from AICP-R to AICP-S, But though sad, that is

I personally use the below batchfile on Windows to help myself doing things correctly, without forgetting something. Called with two parameters. [1] recovery image to flash and [2] the main zip to flash. Followed by other packages needed, e.g. GAPPS. LineageOS supply both as a pair, for other OS it might be different. @ECHO off if %2.==. goto :EOF ECHO * Wait for boot to bootloader to finish (or do manually holding VolDown+Power) adb reboot bootloader pause echo * sending %1 fastboot --set-active=a fastboot flash boot %1 REM fastboot reboot recovery does not work, so do manu

Welcome on board 🙂 I have not got a Pro1X my self (yet), but from the Pro1, indeed the software is very close to stock Android with only minor differences for handling the slide out and the keyboard, and a few other details. And I expect the same for the Pro1X For the Pro1 we need to use the Yellow arrow (fn) key, to access the yellow symbols. I expect the same goes for the Pro1X. How FxTec handled different language layouts this time I do not know, but I expect we have got rid of the odd problems related to the letter shift of the original Pro1 qwertY layout. But do not know yet.

I use the one linked next to the large zip here: https://download.lineageos.org/pro1 I always download both (it is quite small), though they are not identical, I expect they might work within he same android version , I use a batchfil to remember the right steps. See the comment here https://community.fxtec.com/topic/3207-various-roms-available-to-the-pro1pro1x-available-for-download-links/

Thanks, link added to

Apart from the obvious of writing to FxTec, I would suggest that you also contact FedEx and have them halt the parcel, so it is not delivered, until things are cleared up. Then Fedex can contact FxTec, and have them contact you to verify the typo. Unless someone with the same name live at the other address, I assume Fedex will be cooperative in clearing up the matter. For obvious reasons they are unlikely to just take your word for it, unless you got a really unusual name.So they will have to verify backwards to the sender, and worst case return it..

We do not know how big a part of batch 1 FedEx actually have processed yet. So we could still be in Batch 1 without knowing.. In the 'voting' less than a score has 'voted', and similar numbers posted on IGG (of whom some can be the same) so likely only a fraction of batch 1 have got the mail yet.

Well the difference in delivery between first and last within batch one was likely expected to be in days, so hardly worth the trouble, to split it further. As so many times before this project was hit by unexpected delays, this time of the shipping out being slow..... The main point is that all the old orders should be handled in the first batch, so handled before the majority of the IGG perks. I doubt that FxTec has any influence on how Expansys/Fedex handle stuff in their queues, including the order. Most likely they handle stuff from various sources to the same country/region collectively,