EskeRahn

On this special kit, I would rather have had a kit with Battery + USB PCB + a keyboard foil + Keyboard of the users choice. The screen is (still) really easy to find on-line.

Have a look over here, where a browser have troubles saving using 10.0 , Could be the same issue that @Slion got with his browser.

Depending on humidity my screen can be activated a few mm above the display, but nothing as far as an inch

My install OTA gave a boot loop. But booting to the fastboot menu, and just Start, and it boots. I can see the package is downloaded and ready to install. (trying once more gave the same result)

Yes then I misunderstood. I believe we can disassemble the phone with screws only, if you see the frame, the key-pcb and the keyboard as one unit.

Nice review. A tiny detail. The keyboard is not held by the two screws at the front. The keyboard is attached with some adhesive.

Is it just me, or are anyone else plagued by a series of spontaneous boots with 17.1? Even in complete idle on a desktop. It is new for 17.1, I did not see this on 16.0. On this unit I did NOT do a wipe during the upgrade. Note that the AICP-Q, that is supposed to be rather similar, on another unit is NOT plagued by this. ADD: This seems to be related to apps see later posts.

This is intended as a central entry point with links to known ROMs for the PRO1/PRO1X. You will need android adb / fastboot tools that officially can be found here (Windows / Linux / mAc) Important step BEFORE changing from Android initially!! If you want to ever be able to change the phone back to the state it had when you received it with stock Android, there is an important step that is needed before flashing any non android-based ROM, That is to backup the persist partition. If the device is unlocked and a recovery boot is present a fairly simple partition backup method (fo

Yes, was too hasty. Sorry, The keyboard has an odd state that can be entered in two ways 1) Press Sym and get the symbol-selector and do NOT select a symbol, but press Sym again, to have the selector go away 2) Press Sym+Key where nothing is assigned, e.g. Sym+J It leaves the keyboard in an odd state, ignoring normal letter presses. To get out of this state either a) Press Sym, Press e.g. a letter key, Press Sym again b) Press Sym+Key with an assigned key (e.g. 2)

Note that in AICP @tdm has already handled this so Sym+2 gives us a @ 🙂 So pressed alone Sym gives the symbol-list as on LOS, but it can ALSO be used as a modifier. 😎

A TINY bug that I guess is AICP and not in any way related to the implementation by @tdm (might even be a bug inherited from AOSP) The system guesses a language on first boot and suggests that in the Wizard - and that is just fine, I chose proper English, and continues. BUT the "Settings SanDisk SD card Tap to set up" notification is fired before that, so I got this in Danish.... Ignoring it and rebooting, it reappears in English. so not in anyway a big thing.

Is the qwertY/qwertZ setting available somewhere, or is it on a TODO-list? Found it! Searching for "qwert" it pops up as a setting I do not know where though! ????►Additional buttons►Layout 🙂 Searching for "Additional Buttons" does not give anything... (and does not seem to be in Auxiliary Buttons)

I was even more optimistic and tried without wiping from LineageOS 17.1 - and well no surprise it told me data was corrupted, so wiped, and it booted (currently in the setup wizard) 🙂 ADD: I got an "Authentication error" on first WiFi-connection attempt, but reentering the password made it happy. (I had used Show Password, so 99.9% sure it was correct), just reporting if anyone sees he same initially. It is currently adding my apps , and all seems fine. Thanks 🙂

Here my slightly adjusted helper batch-script. Takes date YYYYMMDD as a parameter and assumes, the img, zip, and the nano is in a LineageOS subdirectory. (Note that I do not plan to download and change the OpenApps package each time, so the 20201110 is fixed here, And obvious if you want say the pico and not the nano, the name should be adjusted) An example of a call: LineageFLASH171.BAT 20201110 @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 LineageOS\lineage-17

I would download the opengapps for Android 10, as the one you are using currently are likely to be for 9. I have not tried from SD, only ADB. But doubt that will make any principal difference - obviously given it can read the SD.

Sorry, Did not guess that it was moved to Settings ► System ► Buttons ► Extra ► Additional buttons, 🙂

The settings section where we could set the layout and other keyboards options seems omitted in the 17.1 Found it deeply buried in another menu....

It looks like the one @tdm made, but it seems to be without the qwertZ support...

I do not know if you NEED it, but it looks substantially different, so I would suggest so, unless someone can say explicitely that they know you do not need it.

Done, went super smooth and fast 🙂 IF we got mindthegapps while on 16.0 It seems to be important instead to install opengapps during in the 17.1 process. (That is as Mindthegapps in this version is not supported on 17.1, we can not leave it there, but have to have opengapps replacing it - as @Wheeljack did above too )

I waited about half an hour or so... After a wipe it booted quickly. Will try the Pre-production unit too without the wipe, as this got qwertY. Do we need to remove the mindthegapps while still on 16.0 before the upgrade? Or should installing opengapps in the 17.1 process fix it?

Accepting a factory reset, things seems to work, except the keyboard.... Currently useless EDIT: FinQWERTY can make it working on qwertZ too, for the supported layouts. At the least to some degree. Some symbols like @ is inaccessible, unless you use the fake keyboard OR make a language swap with Ctrl+Space to a language supporting @, and then back.

I am loosing mine, but this is a test device. Others will have to answer if there is a way to keep stuff.... Non-destructive, see below

I was super optimistic and downloaded the two 17.1 files, flashed the loader as usual and sideloaded the zip, over the 16.0 with mindthegapps. WITHOUT wiping anything. And well the flashing went smoothly, but it did not work.... It seems 'stuck' at the loader screen. I do see the circle move over the blue sad mouth, but it does not seem to move forward from that.... So will repeat the same with a wipe.... (and opengaps - thanks @_DW_ )

A question for @tdm Is this the right one to download?