tdm

@EvilDragon: For the battery drain, you can start by getting a logcat and looking for something crashing constantly, or perhaps get a shell and run "top". For the fingerprint reader, it sounds like your persist fingerprint data is full. Try deleting /persist/data/fingerprint (you will need root) and then reboot. Now you should be able to enroll fingerprints and have them saved.

Well that was fast. I'm in the AEX dev group already. 😁

Nope, you can install LineageOS from a factory fresh state. But please do post LineageOS questions in the LineageOS thread. Thanks!

Looks like both AospExtended and AICP have Lineage compatible device trees. So I can look into building those.

Yes that is interesting. I have used the earlier package myself and I have reports that that later one works also. Perhaps you could try Chen's fastboot package and see if that works?

Are they lineage compatible? If so, it shouldn't be hard to build. Also aokp should have those features. I'll be making pro1 official for aokp soon.

I wrote code to rate limit the fingerprint reader in order to reduce that eagerness. But since the fingerprint hardware driver is closed source, I had to put this between the driver and Android. This means the fingerprint driver is still detecting your finger and (trying to) pass that information up, but I'm discarding it. It is possible that the driver has some limit where it disables itself. Or perhaps I made some mistake in my rate limit code.

I see this issue. But my device is preproduction so I thought it might be fixed in production devices. Guess not. Does this happen on stock? I haven't run stock in..... well, ever, really.

Pull quick settings down and tap the pencil looking icon on the bottom right to edit.

Lineage has a quick settings tile to keep the screen on. It looks like a coffee cup. Not exactly the same but it might work for you.

That works out to an average of about 32mA draw. I would expect around half of that for a well behaved device mostly sleeping. Indeed, I just checked my device and it is 91% after 17 hours of sitting. So that is pretty close to ideal. I have not turned on battery saver either. The ROM you are running should not have an appreciable (or any) impact on the battery draw when sleeping. It mostly affects power vs. performance while in use.

FYI ... "custom keymap" is a bit misleading... If you do have a custom keymap file in /persist, this option allows you to control whether it is loaded at boot or not. If you do not have a custom keymap file in /persist, this option does nothing.

It is interesting and sad to hear that CBB is acting this way. I thought the US was the only country in which most carriers sold phones and supported only their own phones.

It may be clearer to read and follow this (but use the official build files, not mine): https://files.nwwn.com/android/pro1/lineage.html

After loading lineage, reboot into recovery again to switch slots. Then load gapps.

I detailed the procedure somewhere in the lineage test thread but I'm on mobile and don't want to look it up right now. Perhaps it would be easier just to tell me which key on the us-intl keyboard you press to make the symbol. I can translate from there.

@FlyingAntero and @EskeRahn thank you for the detailed explanations. However, I am not familiar with these languages nor their keyboards. I rely on pictures of keyboards to see how keys map to symbols. So if you want different layouts for different languages, it would be convenient for you to provide me with the key mapping information rather than the actual symbols. I would prefer a keymap line that I can use directly, but the physical key map would also work. And I assume the same changes apply to both qwerty and qwertz layouts. correct? Here is a keymap example for Y <-&

Odds that this would ever be fixed on stock are slim to none. Odds that it works properly in LineageOS are fairly high.

@Alex the stock software has known issues, including the ones you mention. The OTA updater is an app from a company called AdUps. It has known problems. The usual workaround is to clear the app data for it and retry. I believe the latest update (7/7/2020 I think?) fixes at least the WhatsApp issue. And finally, you may want to give LineageOS a shot. Most or all of these issue are fixed and it will be nicer than stock in other ways also.

You can generally assume that if the card does not work in two separate devices, the issue is with the card. But if it works in one device but not another, the issue is with the device.

For what it's worth, I have been using TP-Link for several years. They have always treated me well and usually are able to run OpenWRT. I bought an Archer C7 a few months ago because my ancient Netgear router died, and it has been fantastic. Currently on Evil Amazon for $65 or Office Depot for $69.

The Lineage keyboard implementation is entirely different from stock. So the FinQwerty data is not really useful. But this should not be hard -- there are likely only a couple of keys that need to be changed. My paypal is https://paypal.me/tdmcode

Then it is most likely a hardware issue. Try different cables and a different USB port, and even a different host PC. Many folks find that host USB-C ports do not work properly, they must use a host USB-A port.

For users other than English and German, note... https://community.fxtec.com/topic/3050-yellow-arrow-key-different-usage-in-stock-and-lineageos/?do=findComment&comment=51003

For those using languages other than English and German on LineageOS, it would be possible to create additional keyboard maps in the kernel to match the expected keyboard layout for your language. If anyone is interested, let me know and I can work with you.