EskeRahn

Thanks. Both Google and the fruit company are crooks!! I got an ancient Iphone 6, That I played around with a few days ago, and the funny thing is that if you try to turn it "off", it drains from fully charged to 0% in less than a day. If you keep it "On" and just let it go into the normal standby, it's consumption is roughly 20% per day!!!! So God NSA only knows what they are wasting my battery for when "Off"!!! Maybe it is not NSA, but just aPple that want to completely deplete the battery to better shorten its lifespan?

So you are saying that we actually need to open the phones and add some contacts to disconnect the WiFi and GPS antennas when WE do not use them.... YIKES!! I knew they were crooks, but not that it was THAT bad... 🤬 It is what I would expect from the scrupleless fruit company.

I haven't read it, but guess it in many words says "We will track you, and steal all your data, without asking again, and you have to pay for the data transfer doing so".

As I see what goes on on the screen, the button seems to have two connections and an open state in between. That is unpressed it obvously is in the 'unpressed' state And as soon as your finger press releases it from its 'unpressed' state, you are in the 'half pressed' state. And pressing it fully unsurpringly gives the 'pressed' state, That is, as there is no middle 'point' creating a contact, there is no felt feedback reaching it.

What you see is commonly referred to as Bootloader mode. And from here you can add software with the fastboot command from a pc. Unfortunately we do not yet have a guide on what parts of the supplied file that should be loaded nor in what order. The over all principle is that from the old Pro thread here. The newest version of the needed official adb/fastload software can be fetched here..

Yes a rough draft would do fine for now, it can always be 'polished' later. @Casey, could you help out here? Just a list of the needed files in the correct order would be a great help.

On the Pro1 it got two steps BUT you can not feel the half-pressed, you will have to rely on visual feedback from the photo app. OpenCamera e.g. gives a square frame.

I'm not sure Google allow that for stock Android 11, So you would have to use some AOSP based like LineageOS or AICP when they become available.

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...)