EskeRahn

You beat me too it by over a minute 😂

@Ralf as neither of us know what it is all about, it is much a guessing game. In a small company people have to fill a lot of slots. But it is not that everyone can fill every slot... So using marketing hands for say packing or service are not likely to be very effective way to use their resources. But sure we would all wish they were able to fulfil pending orders and service request faster, but as we do not know neither what is holding things up, nor what this new stuff is all about we have absolutely no idea if the same hands behind this could sensibly have been used for fulfilling

@Rud LineageOS got Sticky so you might consider that. But if on stock and rooted, it should be as simple as changing "Full" to "Alpha" for a kcm file, if I understood correctly what the ones that know what they are talking about are saying...

You got shift on both sides, so no acrobatics needed used two handed. See e.g this thread https://community.fxtec.com/topic/2282-sticky-modifiers Edit: Merged the threads....

(lineage-16.0-20201019-nightly-pro1-signed.zip on October security patch installed smoothly using sideload, with and without addonsu)

I would expect that they topped of their store of replacement units kept for service request with the July/August batch. It would be rather quick if it was one sent out in summer, sent back from a customer, repaired and sent out again late September. Not impossible of course.

Not quite sure what it should be catogrised as. "Support" perhaps? Strictly this is a more general Android question than a specific Pro1-issue. Anyway. When you chose to use it as removable, it is in a standard unprotected format, and the card can be moved to 'anything' that can read an SD-card, e.g. a PC. When you chose Internal, the card is used encrypted and as an extension of your normal storage (I do not know the finer details of this - never used it). The benefit obviously being the encryption if the data you want to put on the card are sensitive, the drawback obviously also th

Well they would still need to change some code from what Google made. Personally I would prefer this change too, but it would still be a change.

in the FinQwerty layouts the Esc-key acts as Esc if the app supports Esc, otherwise it has a fallback as Back. On the "fallback" all I know is what can be seen in the "Behaviours" section of this So maybe Chrome has implemented Esc as e.g. stop loading a page. In Stock layouts it just sends Back. But the fallback solution in FinQwerty makes Esc available to apps where it is crucial such as Termux.

Unfortunately no. Not all settings&data are restored. SMS&MMS is one thing they do not handle well...

I doubt very much that FxTec would like to mess with the OS to disable this, as their attitude has been to stay as close to stock Android as possible, only changing stuff where it relates to the Pro1 Hardware (particularly the slider functionality, as hardware keyboards are already supported in stock Android). This is certainly not the only annoying 'feature' in Android, and as far as normal third party apps can not fix them, LineageOS or rooting might be the way to go. Just a thought. Restricting what ever offers the sharing from accessing contacts MIGHT fix this particular issue. I

Would seem obvious, but it just might be a matter of some of the closed hardware driver code that does not work with / exist for 11 - just guessing.... ...and I now see @_DW_ already answered along the same lines...

Does this mean they sold 39? 😇

It sounds like a known software bug, that was improved but not totally fixed with the latest firmware update from August 25.

Updated reply with example, but yes, though in the other order, the .img first then the .zip

The crucial steps here are these, to start right fastboot flash boot_a [TheImageNameGoesHere] fastboot --set-active=a

I bet it is a matter of setting the right slot active before flashing - your data should still be there. I use this script, to help me remember what to do... With the images as parameters 1 and 2, e.g. LineageFLASH.BAT LineageOS\lineage-16.0-20201012-recovery-pro1.img LineageOS\lineage-16.0-20201012-nightly-pro1-signed.zip @ECHO off if %1.==. goto :EOF ECHO * Wait for boot to bootloader to finish (or do manually holding VolDown+Power) adb reboot bootloader pause fastboot flash boot_a %1 fastboot --set-active=a REM fastboot reboot recovery does not work, so do manually:

Interesting thing, I still did not immediately spot it even in you cropped image. I guess we simply do not expect Download to be top right? Allow me to suggest a little waste of screen estate:

Oh sorry, I completely forgot you made this. 😔

You think a phone with a good old hardware power off for the battery? That would be awesome. For my spare&emergency phones with removable batteries, I put in a small piece of plastic between the battery and the contacts, and this allows the battery to keep its charge for many many months

Just to make sure, please note that the side buttons as well as the small front support arm can rattle a bit, so try to put a finger on the arm of the opened Pro1, and 'shake' the phone, to make sure this arm is not what you are hearing. (that sound is easily remedied with a small piece of self adhesive rubber or felt in the 'groove' of the arm)

Alain Grange made a specific "Keyboard Browser", I must admit I haven't used it for quite a while. but it is clearly designed with a real keyboard in mind.

We know from elsewhere that contacting again make their mail system put the pending mails from you to the back of the queue. So if their mail back-log is longer than a week, they might not have seen your mails. (others more knowing in support-queues might better explain why it is set up this way. My guess is that if you found a solution to an issue yourself, and mail to say so, it makes sense to push back the original message so the two mails can be handled as one with less urgency. That is you can move yourself backwards not forwards in the queue)

Just tried it. Works fine here, both stock and LineageOS (not rooted) I uninstalled it again, as it requires a terrible amount of high privileges requires a REALLY long pull up of the 'pill' to work (as does default Android if you do not disable the "Swipe up home button" gesture)

Indeed, they can also be bad in the lack of shielding or twisted data-wires, not allowing high speed data... But the impedance obviously matter for fast charging.