Leaderboard

Bump, a batch has just been shipped from HK.

(lineage-16.0-20201005-nightly-pro1-signed.zip installed smoothly using sideload, with and without addonsu)

Got my stock allocation last monday and shipment tracking today, currently in "shipment exception" on the tracking. Gonna ping off an email to info@fxtec to see if they have any details for me, but I'm very excited

I already stated this in the "WaitTime" thread, but yes I got my FedEx tracking info this morning! :) Due to arrive on Wednesday! 😍

@tdmDone, I give it a try and I tell you what. This is writed using boot-stock-kbd-2.img with QWERTZ layout Thanks !

@DieBruine @raymo and everyone else with keyboard issues... here is an updated boot image. This has all Lineage keyboard code except for the aw9523 key handler. I also fixed the FN key handling. The QWERTZ setting (and everything else) should work now. If this still works properly for you, I will start modifying the aw9523 key handler code to see where the Lineage driver is broken. Boot image: http://files.nwwn.com/android/pro1/boot-stock-kbd-2.img Code: https://github.com/tdm/android_kernel_fxtec_msm8998/tree/lineage-16.0-kbdtest

FedEx Scheduling GET! ETA Wednesday! O_O O_O O_O

Hello after some quiet time. Since last time I have cleaned space of the update app, I got spurios long presses again. Not that often, but I did. At last I probably found out, what is the problem. Ive been using the Fx Service app and had set the automatic sync within specifiaed intervals. Seems, like that made the mess. Since I turned off this service, everything is OK and no spurious long presses any longer. Probably it was affected by system actualisation too, but that was the second thing on the list. In my opinion it is caused by Fx service autoupdate, what turns on the update service and

No, the only change you will see is that FN key is exposed.

Order #46XXX (QWERTY) was placed on December 28, 2019 and allocated 2020-09-28 at 11:54. Monday , 10/05/2020, 9:54 pm LANTAU ISLAND HK, At local FedEx facility Scheduled delivery:Wednesday 10/07/2020 by 6:00 pm. Super swell for a simple saint!

No, it is not feasible to keep both drivers in the kernel. My feeling has always been that the FN key should be used for the keys marked with yellow symbols. But I do understand that there are only two keyboards available and this leaves many languages without proper support. So I can look into making the FN key "un-dead". That is: Send FN key press and release as any other key. When FN key is pressed and a key is pressed that has a yellow marking, send the following two events: (1) release KEY_FN, (2) press the yellow marked key. When FN key

@daniel.schaaaf the response that @Gigadoc2 has above is spot on. I would only add that instead of requesting changes in the OS to accommodate older apps, it is much better to use updated apps. Unmaintained apps can be a security risk. I know that is not always desirable or even possible, but it will surely be the official position of both Lineage and Google for this issue.

I don't think the official LineageOS would ever merge such a change, as the restrictions (you mention it yourself) are put in place there for a reason: Apart from no permissions on FAT32 or exFAT, saving onto a FAT-formatted SD is also unencrypted, while saving to the internal storage by default is encrypted. Someone could make a downstream fork of LineageOS for the pro1, but I doubt that @tdm (or anyone else) could get such a change upstream. You could make direct SD access a manually grantable permission, but LineageOS will most likely not accept that either, see the eternal debate abou

I used the included two sided tape from the kit. It's been holding just fine. I don't have any real tips for applying it beyond "be careful".

Sorry for the late reply. Many apps do use the Android way to gain write access to a certain folder on the external SD-card through the documents UI. But there are still some apps that have their own file browser or where you type in a specific path. These apps get write access denied by Android. ScummVM is one of those apps, if you want to see for yourselves. My reasoning for having direct write access to the external SD-card is that apps that have not been updated to the newest Android API, and that might never get an update because they have been abandoned, will never be able to write

Switch the keyboard to type FULL. Get an adb root shell and run: mkdir -p /data/system/devices/keychars cp /vendor/usr/keychars/Builtin_Keyboard.kcm /data/system/devices/keychars/Vendor_181d_Product_5018.kcm sed -i 's/type ALPHA/type FULL/' /data/system/devices/keychars/Vendor_181d_Product_5018.kcm You can also edit the keymap to your liking. @3zet recently did this.

Thanks for the thought. It's mostly just me and @npjohnson but I'm not sure about his feelings on donations. We have both received devices for development, which I personally consider due reward in itself.