tdm

Nice! Note that 17.1 will be relatively easy with 16.0 working. It should be ready within a week or two. Nolen and Ethan are making great progress.

I don't know, I don't use a keyboard mapper because the keyboard works as it should in lineage. My impression is that most people use a keyboard mapper on the stock pro1 only because it is so broken. But that could be off.

I think you misunderstood my point. When you press '/' on a normal keyboard, you don't do it with Fn down. That is incorrect behavior from the keyboard driver. An app would be within reason to interpret this as Fn+'/' and do something unexpected, or nothing at all. That said, it is very much possible to make the slant arrow into Fn modifier for the keys without yellow labels so you could press eg. Fn+1 and get F1. In fact this is one of the standard customization options on Lineage. You can do this with any key(s) that you choose.

Which missing standard functions are you referring to? The only yellow labels I see that isn't on a standard PC102 keyboard are the emoji label on Alt and the WWW label on the spacebar. Both of these are functional on Lineage.

I am pretty sure it's not. Try running getevent on stock and then pressing Fn+P to get a forward slash. You should see key down for Fn followed by key down for '/' or something similar. The Lineage kernel tries to emulate a normal keyboard as much as possible because the stock way of doing the keyboard is pretty awful. You must leave keyboard layout unconfigured or things break. Which is very confusing to many users because Android tells you to configure the keyboard layout. Further, because of this, you cannot leverage any of the locale specific keyboard layouts that ship wit

Okay, a few things to note here: The slant arrow is not a standard key. Unless I missed something, it is never stated anywhere that the slant key is supposed to be a Fn key. Certainly most keyboards have a Fn key. But it was not on the original PC102 keyboard and it is not difficult at all to find a keyboard today that lacks one. Now, as for actually handling the slant arrow key: (1) How would you propose to do make it behave such that one can make it both act like a Fn key and have the yellow labelled keys be available without extra keystrokes being repor

Keyboard mapping is fine with kcm files. You can map characters in both stock and lineage. Find the people that use FinQwerty, they can probably tell you more.

Thanks for noting that. Now it is clear why developers don't like nor support magisk. My fault for not asking if you had it installed.

It is possible that the Lineage GPS configuration files are not optimal for certain areas. Me or one of the other devs can look into that.

There are several GPS test apps in the Play Store. I use "GPS Test" by Chartcross Limited. No reason for that particular one, really, except it's the first one I found years ago when I first started developing for Android. Another one I always have installed is "Sensor Box for Android".

I can get a fix -- possibly a bit slow, but it works. Any one else having issues?

Let's not spam users with dev stuff. PM me if you need further help.

adb should be enabled, you just need to auth. Extract your boot image, add your host adb key to /adb_keys, repack, and flash. Alternatively, instead of adding your key, you can disable adb auth in default.prop.

Sorry, I misspoke. Yes, there is an RTC. Yes, it can be programmed to power on for an alarm. No, it cannot keep time while off.

Yes, you would run from the adb root shell. You stop services exactly as I said, with "stop". It is assumed that you would be running Android (which is the only place where you have both an adb shell and unencrypted data). I haven't really tried this, so if your data is important, it may be wise to boot into recovery and save off a "dd" copy of the userdata partition just in case it doesn't work. That is a challenge in itself, though, because there isn't any place on the device to put that amount of data. You need to have a large enough sdcard to hold the data or stream it to y

The SMS/MMS issue is most likely an issue with your operator/carrier. But even if it is the phone, all of the radio code is closed source and copied exactly from stock. So I almost surely could not fix it. Unfortunately, Qualcomm devices do not have an RTC. So the date/time needs to be set at each boot. Normally, the date/time can be set via either a broadcast from your operator/carrier or via NTP with a WiFi connection. But when neither are available, the date/time is indeterminate. Qualcomm does make some attempt to save the current date/time at shutdown, but this code is c

Does AT&T VoLTE work on stock?

Thanks for the detailed info. Unfortunately, I don't see anything specific to Lineage that could be causing your issue. The RIL handler is closed source. The only thing you could try is replacing your libril with one from an older build and see what happens. But the issue might just be your provider. Nothing uses 3G anymore. You should be fine. But VoLTE is working on Verizon, I believe, so it will probably also work on AT&T. Give it a shot.

Note: This thread maintains the full factory packages with a user friendly tool: https://community.fxtec.com/topic/2559-factory-restore-tool/ It uses EDL which can be finicky, scary, or otherwise problematic for some folks. So a fastboot flashable zip with a script is nicer for many users.

Yes, you could. But I have the original factory package (from @Waxberry) which was used to make my factory restore package. It is much quicker and easier to make a fastboot package directly using the original factory package. Plus you get the original sparse images which are much smaller than full images. So either I could give you the images from the factory package with Chen's approval, or he could go ahead and make another fastboot zip like he did before. Yes, this does work. You just "dd" the userdata partition. The encryption footer is on the userdat

Okay, I can see this conversation taking up several dozens of messages in this thread. Please contact me in PM and we can find a way to chat without spamming users.

I don't see the point. Once you get the DT compiled, how are you going to generate the overlay? And then how are you going to generate the initrd and the boot image? The only practical way, really, is to use the Lineage source tree. So if you are already using things from the Lineage source tree, you can use the Lineage DT compiler also. And as long as you are at it, you might as well use the Lineage cross compiler.

Hmm, thanks, I'll take a look. Note the /persist partition is not wiped when you do a factory reset. I have a script in Lineage that deletes /persist/data/fingerprint at boot when the Android fingerprint data does not exist (eg. after a factory reset) so that Android and the fingerprint HAL can stay reasonably in sync. The fingerprint HAL should be re-creating that directory when you first enroll a fingerprint. EDIT: Also note that the fingerprint HAL is entirely closed source. The only possible changes have been in updating the vendor blobs from the 6/22 OTA and the

Yes, an entry in the settings app to toggle sticky fn. Because surely some users will want it and other users will not. I'll try to think of a way. But I do not know of any other Pro1 group except on telegram. I do sympathize with you, though. I really don't like giving my phone number for internet chat. It is just that with all other modern privacy and security concerns, it seems a small thing in comparison.

First, thank you for volunteering to contribute. I've been working my figurative butt off for months and I'm getting tired, to be honest. Which is why Nolen is doing Lineage 17.1. More inline... Check the keyboard files. This is probably in the KCM file, if it can be changed at all. Notice the keyboard is declared type ALPHA. If you declare it type FULL, I believe both autocapitalization and the symbol popup will go away. Certainly. And add a device specific setting to toggle sticky fn, I assume. Build it in a Line