EskeRahn

(merged your thread into this larger one, let us hope that their latest December ETA will hold, so our long wait will soon be over)

There have been no new AICP updates in three weeks, and as I have not have found the time to install something else on the unit, I fetched and installed 20221123. Same issues as earlier. (including still reverted to Android 11)

...It is here today...

(Depending of program combos like Shift+Enter or Ctrl+Enter might send)

And https://browser.geekbench.com/search?utf8=✓&q=fxtec provides several tests from PRO1s (aka qx1000 internally), so roughly 1/4 slower, but there are huge variation in the numbers, so hard to say anything really fair. Search for qx10150 give other Pro1X tests in august, and they match your numbers rather close.

My thought exactly, was about to post something similar *LOL*

(split from https://community.fxtec.com/topic/3026-solved-lockedbroken-bootloader-press-volume-key-to-select )

Below 4 x WiFi-connected, reasonably stable. Though obviously not in any way a proof against drops

I have not got an answer, but note that things might work differently in different input fields. Especially if in something with it's own auto-correct or word prediction. So to be clear what you are seeing, try in something 'dumb' like a text-editor. (Please adjust the title to reflect that it is Pro1 and Lineage)

On unrooted devices I do not know of a solution on the phone. I believe that external electronic circuits exists, but I have not tried them. Using a slow charger as you do, is a very good start, as this prevent the battery from heating substantially - and that is the most important: Daily charges should start (and stay) at around room temperature, for the batteries to be happy. I use a 500ma or 1A charger, and often I forget to detach it, and just let it charge fully. Yet I see no deterioration in the stamina, after three years of daily usage of the pro1 (nor for the test-devices).

Thanks for sharing. I'm not sure if it is different versions of adb, or different phone versions that reacts differently on various syntax for on/off of the flags

(Nothing substantially seems to happen with the updates. Will still update the device, and report here if something new happens....)

I use 3C All-in-one toolbox, he also got the battery manager as an isolated product. Been using it for many years. Got some blah blah here

Usually that shift is invisble for the user though. As we have in another thread, some new charging related thing cutting the scharging has been added starting from Android 11. It MIGHT be the same that is causings issues here?

@Casey can you help us with info here?

Remember that when a theory can not be disproved, it does NOT make it correct. Religions and conspiracy theories usually relies on this kind of false 'logic'.

Intet dansk tastatur-tryk.... But you can get the Pro1X with a Scandinavian layout print. But selecting Danish also works, with other prints - despite a few keys then obviously got slightly wrong print Apart from the build in, have a look at the great FinQwerty by @Anssi Hannula (available in the usual android market, or from his site)

I use my Pro1 as my daily phone, primarily for SMS but also emails, browsing and calls. The Pro1X I plan shall take over from my Pro1, where after three years usage, the keyboard are beginning to not be 100% reliable. But I HOPE they soon will release the new software, with various fixes, and I'm 'holding my horses' a bit for that, before making the transition. Maybe I'll get too impatient and do it while still on the existing software....

I believe that is common practice if not even law. At the least the warranty could not possibly start before the item was sent. No matter how much before it was ordered.

I think the culprit can be identified by the difference here versus I have never heard of "boota" without an underscore. The big question is how it got in that weird state, but not most likely it was fixed by you changing: to Overwriting the weird value it had as read by "boot"....

Ah! It seems something is/was odd at @Name_not_avail's device as the quote said 'boota' and not 'boot_a' in his first attempt - I have no idea how that could be.

Are you sure your new device it is not a Pro1X. They look much the same, but the chipset is different, so the code is incompatible. Look here for various available downloads for the two models.

Unfortunately we have not seen @tdm active in here for quite a while, so I guess you should look for other sources (with a little luck someone saved a copy)

Ah Indeed, One could make a new hole. The case I'm using is only glued to half the shell, so by the rotation I get protection of the camera, at the price of needing to push the flap away, to get it free of the camera. But I much prefer that the camera is protected (as is the button side)

Allow me to suggest you to make the flip the other way round. Feels odd for westerners with a 'Japanese' book at first, but it works really well with the flap under the display, rather than dangling in front of the keyboard. See e.g. this. If you find a way to integrate the magnet in the shell, it would become even better.