tdm

I just put up an incremental ota with the keyboard settings fix. I don't have time to test it myself right now so you guys are the guinea pigs. 🙂 Please let me know if it works. No need to futz with gapps, just install and reboot.

Yeah it's probably related to the different way of doing custom settings. I'll get that done next build.

The device specific keyboard settings are a bit hidden because AICP does not use the same methods for adding to the settings menus. So I'll have to check on that.

What? AICP should behave the same as Lineage. The kernel is exactly the same code.

sdcard should work, but I haven't personally tried. Yes you need a gapps that matches your android version. So, for example, opengapps for Android 10 (and arm64, of course). Don't forget to switch slots with reboot/recovery before installing gapps.

I think I've found where the issue is in the QWERTZ settings. I have a patch up to fix it now. If anyone is interested... https://review.lineageos.org/c/LineageOS/android_device_fxtec_pro1/+/292350

Interesting. The code is still there, and apparently still being built. @npjohnson do you know anything about this?

The 16.0 recovery should be able to flash 17.1. Give it a try. The keyboard driver in 17.1 is the same as 16.0, as far as I know. I suspect something is preventing the qwertz flag from taking effect for @EskeRahn ... logs would help with that.

If you sideload, gapps does not migrate, so you do not need to remove anything. I do not believe major updates are distributed as OTA so that path is not possible. I cannot say why your upgrade failed without a log, and that is no longer available I guess.

Lineage upgrades should always succeed without wipe, even major versions. This is independent of gapps though, you are responsible for that. Keep in mind that first boot after a major upgrade takes a long time. I would give at least 5 minutes before giving up.

The first Lineage 17.1 build has been posted on the official download site. Please note, I have not really been involved with this version and I am not running it on my device, as I prefer AICP. I would suggest @EskeRahn create a discussion thread. I'll probably monitor that in case any issues arise and need pointed out to the current developers.

The Lineage keyboard driver tries to make the keyboard look like a "normal" keyboard to Android. Because the print is in German, the default QWERTZ layout is the same as a German keyboard. I would be happy to work with you to adjust this for Swedish. Please send me a PM.

I'm using opengapps nano for Android 10 on AICP Q. It works fine. So I'm sure it will work fine on Lineage 17.1 also.

Only 17.1 will build now, but you are free to keep 16.0 as long as you wish, and even build yourself when new security updates come in.

Is anyone actually running this? I don't see any evidence, so I am not putting any effort into it. I found an issue with WiFi not connecting, but I don't know if it is just my device or not. The issue was some unrecognized data in a WiFi data file. I upgraded from AICP P without wiping my data, which I know users never do... right? right? 🙂 🙂 🙂

Sorry I am not familiar with the hardware on this level. It is possible that the new screen is different in some subtle way. Or perhaps it is possible you got a defective screen. I know others have changed screens without any apparent issues.

No but if I can get the issue sorted out and fixed I'll get that change in both versions. Are you willing to test?

I'm not super familiar with Intl keyboard layouts, but my guess is that keyboards for these languages are different than German. I setup the key map to match the labels, which I believe is German. Since the key map is fully customizable, I could add options for the language in settings. Say, qwerty, qwertz/German, qwertz/Swedish, etc. But I would need help getting those right.

Maybe, if I can find the time.

Are you using gapps or not?

These tools change the way Android works. If they have a bug or if they are misconfigured, it is difficult to track down the issue. So users will frequently file bug reports against the device in Lineage and waste developer time trying to reproduce an issue that doesn't really exist. For me, personally, I don't like to give that kind of power to any program that I have not personally built and reviewed. And both of these tools are complex enough that I'm not going to go through their source code. Further, they both have a modular system where anyone can contribute. This means

There were two changes around the location provider overlay about 2 weeks ago. But I don't think that should affect your ability to get a lock.

Good question. I had not actually checked. It seems "su" is present in their sources, but does not build by default. This is the good old bog standard "su" that ships with AOSP, no integrations with Privacy Guard or anything like that. So I have to assume everyone who uses AICP and wants "su" is running magisk. But I'll look into it some more, as I refuse to install magisk on any of my devices.

I will be maintaining AICP for a long time, I'm sure.

For those asking why AICP, I personally have two main reasons: It has more customization options than Lineage. It is more fun to work on, Lineage takes themselves too seriously. I've been using custom ROMs on my devices since my first Android phone in 2012. I have always run AOKP for the above reasons. But AOKP is gone now and AICP fills the same needs for me. That said, I'm aware Lineage is perfectly fine for a lot of folks. That's great. The beauty of it is that you can choose what you like. 🙂