EskeRahn

Reboots about every second hour or so, will try to re-flash, if that does not help, factory reset is next. 16.0 worked really well, but the upgrade to 17.1 was bad. But pretty sure it is the lack of a wipe that is at the root of it. As AICP-Q on what I believe is the same port is stable after a wipe. ADD: This seems to be related to apps, see later posts.

@pebert FinQwerty is not designed for Lineage&AICP, that uses a principally different handling.

....we are drifting off topic here though....

I tried in KeyEvent under AICP-Q and LineageOS, no code returned from the Logo key. In Lineage 17.1 Logo+Enter is Home, but nothing happens in AICP-Q In Lineage 17.1 Logo+BS is back but nothing happens in AICP-Q Other listed shortcuts like Logo-N works on both, but is handled so deep that no KeyEvents are fired. On qwertZ Logo+Minus shows the shortcut list, on shifted QwertY it is Logo+Fn+P.

@netman and @internationaltraitor not to be a spoil sport but you are not only out f topic of the thread, more like out of topic of the forum *LOL*

And well Got he reboot again... ADD: This seems to be related to apps, see later posts.

(lineage-17.1-20201116-nightly-pro1-signed.zip on November security patch installed smoothly using sideload, No spontaneous reboots .... yet)

Yes, under network, you can select LTE as the only allowed band for the sim

I just meant that just some of the keys got the yellow foil, any other keys will be white, unless they made a different version of the base. The currently announced can all be made with same base and different black.

Well, as said earlier on, most likely we would have to operate under a harder constraint of only the physical keys with secondary print on the existing qwertZ layout can have have secondary print, and in yellow, without the requirement of changing det underlying keytops. But if we can persuade them to change that too, it would obviously leave us more options. But it would add extra expenses to have to produce two types of base keys, so we would have to argue harder.

Well, SBC is listed in AICP-Q Settings,developer options, Bluetooth Audio Codec. I have- no idea if it works though

It seems to be stabilising itself, the spontaneous reboots have been getting less frequent 😁 ADD: This seems to be related to apps, see later posts.

I remember a case some decades ago where one of my customers had an official software package with an unlocking diskette (long before usb-dongles) placed at each workstation, but they actually used the pirated version of the same software, to avoid the hassle with the diskette... Seems somewhat similar.

For stock Android Pie, you could try the solution @Slion linked above Apart from that you could go for some of the Android 10 (AKA Q) distributions, where this option is build in, e.g. Lineage 17.1. (Settings►System►Gestures) You can start here to look at available alternatives.

(Installed smoothly here too, and yes Backlight and November, thanks 😎 )

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