EskeRahn

I haven't seen this at OTAs, but I have seen it when restoring from Google. I'm not sure if is related. One of the apps that very often is omitted is K9 Mail. And though numbers are unusual in names, t is not always omitted, just frequently. I can easily go to Android Market, and select the Library tab, and the app is listed and can be installed with no hassle. It can happen for other apps too.

@bamboozle I repeat myself here.... Look back at the crashed Moto Mod Keyboard Indiegogo project by Chen. He offered ALL over money back OR a voucher valid for the Pro1 (Actually with $100 even for a larger amount than what we invested in the project!). The project was crashed due to Motorola, with a lot of money wasted, and he could just have said too bad, the project failed money spent, but being the honest guy he is, he paid us back from his own money(!) - and now -again- we see people questioning his/their new project.... If you want to be absolutely sure to get something use a phys

Though I like the principal idea, not all would be happy with the blue over the black, and as you said, they might have some parts already in stock. I do not know how the manufacturing process is, but as the key-mat can be put on as the very last thing, the various keyboards are not likely to be a big complication, as they can produce the base Pro1 finished and tested less the key-mat.

Thanks for the tip. Could well be related. It works fine on AICP-Q though, restoring Google's own extremely limited backup (from Stock Pie). The difference is that I upgraded 16.0 to 17.1 without a wipe, but I did do a wipe from 16.0 to AICP-Q, before the restore through the wizard. So could be some settings from 16.0 that survived. For now it seems stable after the AutoNotification uninstall, will report back after some time if it is merely luck that it has not booted (yet), or I found the culprit...

If I actively try to put it to sleep with the power button, and not just wait for it to time out, it most often boots... I had a suspicion to Greenify, that acts in this scenario, but stopping it before, does not change the behaviour. ADD: Tried to disable the Accessibility of any apps granted that (3C battery monitor, Greenify, Android Assistant) - no difference. Any logs that could benefit anyone before I wipe it clean? Went one step further and stopped every user app running, and found the culprit AutoNotification, that came in with my backup from Stock, after uninstall, and re

No luck. Still there with opengapps-nano-20201119 though ADD: This seems to be related to apps, see later posts.

That was quick, it just rebooted again - WiFi disabled, will try Aeroplane-mode.... ADD: This seems to be related to apps, see later posts.

Interesting Idea. I have just tried to disable WiFi, and will report if it helps. But the same issue is NOT affecting your AICP-Q ADD: This seems to be related to apps, see later posts.

The "Emergency" function added on the Power button, is there a way to get rid of that? (it is optional on AICP-Q) Or does it at the least have some sort of confirmation dialogue? I have not (yet) accidentally activated it, but would just hate to waste their time due to some not thought through phone-function... Do not get me wrong, the idea with easy access to emergency is fine, but it is not fine if we end up wasting their time with accidental calls.... If each of us do this accidentally say every three years, that is almost 1000 random calls a day in a one-million-city....

Hmm, maybe wipe is not the solution for me then - could be related to the crashes I get. (note that a six day newer Lineage exists 20201116) Add there are also newer OpenGapps available, with a little luck that makes a difference...

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