EskeRahn

Indeed, but the keyboard drivers of the Pro1 are not part of stock AOSP. So @tdm is not messing with the Android stuff here. On the contrary he is trying to make the Pro1 hardware to work better with the hardware-keyboard support present in native android. AND doing this in a way so what is printed on the keys are still respected when US Qwerty is selected. And this also allows for selecting any of the other native android key-layouts. SURE there might be custom layouts that does a better job for a specific language than what the default android offers in LOS. But on the contrary to what Stoc

Obviously more users are using Stock, so it is either to have two set of code, or to argue that the two Android-branches should work equally. And personally I hope that stock will look at LineageOS more than the other way round. As you say the model of DE-selecting all layouts is an odd idea. With Stock FinQWERTY is a must, but it is a MUCH more clever solution to make the base standard, so all the existing stock language layouts give something reasonable. It will still allow anyone to make their custom layouts. Yes indeed this 'steals' the yellow arrow to fixup the keyboard to standard.

A very major reason for using LineageOS currently is that it fixes a lot of what is broken in the Stock Android implementation.... One could even says that @tdm's take on the Yellow arrow is ALSO in "fixing what is broken", as it allows for the few billion users not using English as their primary language to better use the device... As it standardise the qwerty, so standard 'language packs' can be used on top. So it might not be a bad idea at all to include that too in a future Stock OTA....

Just been offered a new official OTA. I will attempt to let it do it OTA on one of them..... (it has gone up a substantial 50MB, so would be interesting to know what has been added) ADD I: Download and manual flashing worked fine. ADD II: OTA download&update took an hour, but it got through this time.

I have tried to split the discussion on the the Yellow arrow key usage into a different thread:

The thread is going far astray from display into keyboard land.... I wonder if it should be split, or these post merged into a different thread. Any good suggestions of a destination thread? Anyway I think that @Hook has the main point in this. The shifted Qwerty is not an optimal starting point, and that is what @tdm have found a quite clever way to work around so the keyboard acts like a (shifted) standard keyboard, that then can use standard language layouts on top. But I personally find that using qwertY on the qwertZ keyboard as done by FinQWERTY is a better starting point. Incl

...And can be combined with shift for marking. (You have to press shift before Ctrl)

Interesting. Here I with stock see GPS+Glonass+Gallileo+Beidou, With Lineage 'only' GPS+Glonass

I can get a fix too, but it is clearly worse than stock,placed side by side in the middle of the garden. BUT the fix the very first time gps is used is always VERY slow (minutes), and this goes for LinieageOS too. I have a suspicion that Lineage does not use all the non-US sats. Stock claims that 39 satellites could be in view, where Lineage claims 12. On stock I might have 3m accuracy and on Lineage 50m (And yes I have checked the settings of GPS test, and no filters active)

+Ubuntu

...Just ordered a new SIM from a provider I'm certain offers VoLTE, so will know in a few days if it works on Lineage (and stock), selecting LTE only as band. 🙂

https://wiki.postmarketos.org/wiki/Qualcomm_Snapdragon_835_(MSM8998)#:~:text=MSM8998 (or Snapdragon 835) is,towards the end of 2018. Real-time clock (RTC) The RTC module found on the PM8998 PMIC block works with CONFIG_RTC_DRV_PM8XXX enabled. It can be easily tested from userspace like so: # cd /sys/class/rtc/rtc0/ # echo $((`cat since_epoch`+120)) > wakealarm After running that and fully powering down the device it should power on by itself soon afterwards (2 minutes later to be exact).

I would really wish for some more user friendly flexible solutions. So you could easily use fast charging when you need it, and avoid it in daily usage. Sure you can just use different chargers, but the average user is not going to mess with that. It would be better if you only had one fast charger, and when connecting we would get a pop up with some objective message like "Fast charging shortens the overall battery life. Do you need the charging to be fast this time Yes/No" And perhaps with some estimates helping people to decide related to the actual situation.

Well we are in the guessing game here. It might just as well be the delivery of parts to the assembling factory that have delayed things, and if so we can hardly blame the assembling factory.

@DieBruine Thanks. 🙂 I took the liberty and moved your post to the more official (but locked) thread here:

The carrier should support VoLTE, but I have no idea if it is active on Lineage.

On mine it is opposite, they are greyed on stock.

Hmm I'm not sure if the Pro1 got VoLTE or not. Have a look at these two images from a Pro1 on Lineage (Dark) and stock (light) - same sim moved over, same place. Notice how it is greyed out in stock. PS the "Preferred network type" follows the sim. Inserting another sim in Stock it says "LTE/WDCMA"

This sounds like a quite dangerous sort of 'backup'. If your phone is lost or damaged, your 'backup' is worthless.... It can of course be fine for a short term backup before 'messing with things'.

The Wireless charger may pull all the power, but it will not be transfer all of it wireless Even in ideal condition and with a common iron core (like a transformer) magnetic transfer will have substantial loss. (Unless we are talking generally and include super conductors). But obviously the phone must be able to handshake through a protocol supported by the charger, e.g. Qi. We do not know what protocols the Pro1 supports here. It might only be some so basic that it can not request a reasonable amount of power from the charger.

I have no issues with fingrprints on official Lineage, and they survives boot nicely. How odd they reacts differently-.

To see what charge is sentto/pulled fromthe battery, you con try to install an app like 3C Battery Monitor (also part af a larger all-in-one toolbox, i can also highly recommend) It does NOT tell how much gets delivered to the port though.

You might have to roughly half the charger output to what the phone recieves wirelessly - at best 75% (hence the heating with wireless charging) but I know that the phone can charge slowly with 5V 500ma. I will see if I can find an old 300ma charger in a drawer...

Sure we could close it, but I see no harm in it being open, I think the recommendation of the link to the new thread would suffice. Don't you? I guess once test-builds for 17.1 appear, we would have a new thread for that too, that should also be recommended. I mean if someone (for whatever reason) prefer one of the old 16.0 test builds it would be natural for anything related to that to be in here. (not that any support on the old test builds could be expected from the developers, but there still might be sharing between users)

Ah... So that was It, too bad... 😥 I was sure I read somewhere that someone had done it. ☺️ Just a guess. Could it be that the metal back disturbs the magnetic field so it can still 'see' it but can not really transfer power? For the test it could be interesting to see if it charges free in the air not attached to the back (though obviously useless for real usage).