tdm

Doesn't the auto rotation quick toggle do what you want?

I'm implementing the UI for device specific features. So a couple of questions... The keyboard map option should show a few common, sane, useful options. Like, say, making FN plus top row keys send F#. What other useful options do you think should be there? Currently the keyboard backlight stays on while the screen is on and the slider is out. Would it be useful to have an option to time out the keyboard back light after a period of inactivity? Any other interesting ideas?

https://github.com/tdm/android_device_fxtec_pro1/issues/31

Alright things are moving right along now... I've got the touch screen margin/deadzone implemented and a nice little settings preference for it. The display margin will not happen until later, if at all. That's much more difficult to implement and intrusive to the system (it will likely require a reboot to take effect). I'll be adding a keyboard layout setting (qwerty/qwertz) next. Then I'll see what I can do with the fingerprint reader mitigations.

There is an add-on su package for Lineage. See the extras download page.

Lineage has a persist facility that is used by gapps, the su package, etc. I haven't run Sailfish yet, but my understanding is that it's more like a traditional Linux distro than Android. So it surely has root facilities built-in.

Retractable micro laptop? 🙂

You can scroll with a vertical swipe anywhere on the screen for that. The scroll bar is just a visual indicator of your position in the list. I couldn't imagine requiring the user to hit that tiny scroll bar with their finger.

I could extract images from the current stock and make a EDL package and/or a fastboot package. But I've been rather busy and quite honestly it's not a priority. The only use I have for stock is extracting vendor blobs for the Lineage build... 😄

I'm not as familiar with how the physical resolution is presented to apps. But I'm not sure that will really be necessary. Playing around with a dead zone of 32 pixels feels pretty good and does not seem to impair anything. The screen is supposed to be capable of dt2w. I'll have to dig into the BSP history to see what they did to disable it.

If you want to run stock, you play by the rules of stock. The only way to install updates with a modified system partition is for someone else to provide the data to flash manually via fastboot. I haven't personally seen any factory packages provided since the 2019-12-03 release. If you want to root your phone and be freed from this nonsense, don't run stock. Lineage is coming along nicely and Sailfish is supposed to be rather good as well.

Poking around a bit in the touchscreen driver. Adding code for the side dead zones is trivial and it works here. Hooking it up to a sysfs node and adding a setting item in the settings app will be a bit more work, but very doable. Not sure about the fingerprint reader yet. I may implement two options: one to only activate the reader when the screen is not off and one to limit the amount of time between reads. I personally like the latter -- I love to be able to unlock the device without pressing any physical keys. But I'm not really sure exactly how to implement either of them

The AdUps updater is provided to the OEM as a binary package so I can't say for sure what reason 20 is. However, I can say that any modification to the system or vendor partition will cause an update to fail. This includes even mounting the partition read/write once. The only way to get back to a state where OTA updates will succeed is to replace your modified partition with a pristine, bit-for-bit copy. Reading behind your fail dialog it looks like you are on 2019-12-03 right now. The fastboot package for that is probably floating around somewhere. If not, let me know and I can provide

Alright, so time to vote on issues to work on. Assuming that audio generally works (reports indicate it does in test7) and a2dp works (it will in test8), what is your biggest issue with running Lineage? Here's a list to start, mostly cribbed from the issues page: * FM Radio does not work. * WiFi signal strength broken. * SELinux is permissive. * Notification LED and/or vibration issues (anyone other than @Polaris see this?) * ExFAT support for large sdcards (generally 64gb+). * Allow dead touch zones on screen edges. * Mitigate accidental fingerprint

Holy crap, I finally got a2dp working. That took waaaaaaay too long, but it's working now. Next build will have it, probably tomorrow since I am a bit busy today and there's some other stuff I want to fix/add also.

I don't use or support magisk, sorry.

Key 9 is index 13, KEY_9 is 10 (0x0a), KEY_F9 is 67 (0x43), so "13:0a:43". I'll let you figure out the rest. 🙂 As for the GUI, I'm intending to have something relatively simple. Perhaps pick from a handful of canned layouts, and maybe a few tick boxes for modifications (like your F# keys). PS1: if you mess up, you can always echo "qwerty" > layout and it will reset. PS2: you can diff the original keymap file and your changed one to see what you have modified. PS3: you do not have to have a full keymap in your file, only the changes that you want to ma

I would like to see proof of people using aptX on stock. Because I do not see the aptX libraries in the stock image. So unless Qualcomm has embedded the aptX libraries somewhere unexpected, or someone has added them manually, I don't see how it is possible for aptX to work on stock. It is LineageOS policy to include only what stock includes. This is to avoid any potential issues with licensing. So i cannot add aptX on LineageOS (officially anyway).

No, I had intended this to be fronted by a GUI. But I can add the ability to ignore comments. KEY_F6 is 64, so that should be 19:0007:0040 Thanks. 🙂

The pro1 doesn't have an aptX license so that property should not be set.

Okay well if you could share those lines from build.prop that might help. I'll look into those audio libs... my device tree started life as a copy of the 1+5/5t device tree, which is also msm8998 so the libs list should be pretty close to accurate.

test7 is up. This has some missing audio libs that should make audio behave better. Please test and let me know. a2dp is still broken but other bluetooth functions seem to be okay (tested file transfer). @EskeRahn this will hopefully make android.hardware.audio@2.0-service behave better. @EskeRahn no I didn't do any screen calibration that I'm aware. @Kabbone yes double tap to sleep works.

@Craig I'll respond once here... In theory gapps should persist from install to install. If that is not working, someone may need to investigate. You do not need to re-install the recovery once you have it. I'll try to get the instructions updated. The slant arrows are fully dead keys in the current Lineage build. I would like to make them customizable but haven't gotten there yet, as there are higher priority issues. After they are customizable, however, you will still need to keep at least one key as KEY_FN (or whatever I decide to make it) for a fully dead modif

The libs I found are vendor/lib/libgcs*.so. I already had the 64-bit versions of those, but apparently the 32-bit versions are also needed. What a2dp items did you find? I'm still not getting a2dp to work. 😕

The keyboard character map file determines the type, FULL or ALPHA. It is loaded at boot and cannot be changed after. Perhaps I could implement an option in settings to switch. The documentation is here. I am currently placing the default kcm file in "/vendor/usr/keychars/DEVICE_NAME.kcm". The setting could place a modified keymap in, say, "/data/system/devices/keychars/Vendor_XXXX_Product_XXXX.kcm".