Leaderboard

Hi @Laska, The keyboard driver for the Pro1 has been completely rewritten by @tdm when he did the original port of LineageOS. The keymap file in LOS 16 is located in /sys/bus/i2c/drivers/aw9523b/6-0058/keymap. However, any changes to that file are not persistent across reboots. If you have root, the easiest way to make changes persistent is the following: Install the app Run Userinit from F-Droid. Execute Run-Userinit once and grant it root privilege. Next, place your modified keymap e.g. in /data/system/keyboard/keymap (you may have to create the "keyboard" folder

(lineage-21.0-20240316-nightly-pro1-signed.zip on Feb 5 security patch installed smoothly (*) using adb sideload and MindTheGapps-14.0.0-arm64-20231025_234300) And we still can only select one keyboard layout, so no easy layout switching, for multilingual usage.

OK, I ventured a down that rabbit hole somewhat, and it turns out you are, in a sense, both right. In fact, phones had, and still have, a real time clock (RTC) that is able to keep time even with the device powered-off. However, as I learned from here and here, the RTC on Qualcomm devices is read-only. Upon the very first power-on, it initializes itself at 1st January 1970, 00:00:00 UTC ("Unix epoch"), and then just counts from there onwards through the lifetime of the device. Indeed on my (rooted) Pro1, the RTC clock returns rostkatze1:~ # hwclock -r 1973-09-11 08:31:30.407

One possibility is to find a small bluetooth keyboard that can fit inside normal phone case. Then you could just buy 2pcs of cases and put phone and keyboard to own cases. In the end you could build the sliding mechanism with magnets (see Jolla the other half keyboard) or something else. Here is video and couple pictures if the idea. https://youtu.be/FqYX0ZbC5uA?si=itPnKwmK2GAorypX I think that another Rii keyboard could be usefull (‎4.3 x 2.3 x 0.4 inches so 10,9 x 5,8 x 1,0 cm) https://www.amazon.com/Rii-Bluetooth-Rechargeable-Handhelds-PS3-BLACK/dp/B0B46F8RS6

Lineage-21.0-20240316-nightly-pro1-signed.zip on February 5 (2024) security patch, installed smoothly* using OTA *Boot time about 3min. (only the first start after update) (while the LOS-Update, I stopped all other updates or backups)

Oh, I can see how that could be a major pain in the bum if you bootup somewhere without a trustable useable wifi signal. Fascinating, I always presumed mobile phones had either a little lithium battery or a big capacitor holding up the clock while powered down or rebooting or such. @claude0001Some interesting reading in those links on your post, and this behaviour apparently going back some time. @EskeRahnGPS sync is an interesting idea, hadn't thought of that. @LaskaOr could you hotspot off another sim card e

This is not rom-specific. There are no internal clock in any smart phone I know of, so it needs to fetch the time from some external source. But if it got neither WiFi nor a sim, who could it ask? We had that in some threads here some four or five years back.... It COULD flash the time somewhere in going down so it was not extremely wrong when booting, but would still be wrong, and might be worse if people was unaware that the time slipped backwards each time. So the risk of people thinking the time was right would be higher They could activate GPS and try to get the clock that

Hi Laska, Indeed, what you observe is expected behaviour if "System > Date & time > Automatic date & time" is disabled and/or if automatic syncing of the clock is not possible because of lack of network coverage or because no SIM is inserted in the device. I do not know if this behaviour is specific to my ROMs or if it is a general thing with Android 9/Lineage 16 and the realtime clock. I did not (consciously) change anything in the code with respect to this. A quick internet search suggests it is quite widespread behaviour for Android devices to just assume