Leaderboard

To keep on improving on our Lineage OS keyboard driver implementation here is a proposal about Fn passthrough. At the moment Fn modifiers AKA Yellow slant arrows are being handled internally by the driver and not passed as such to the application layer. Which on one hand is needed, notably to generate the proper key scan code without modifiers, think / and ?, however on the other hand it starves the application layers from an otherwise perfectly valid modifier which could be used in custom KCM layout notably to improve international characters support on thumb keyboard. Therefore thi

Again, as far as I can tell, this is controlled by the the soft keyboard. AOSP keyboard has sticky shift (but no setting for it) but it does have an autocapitilization toggle. If you turn it off in the soft keyboard, the hardware keyboard no longer does it.

This could be a red herring / I could be misremembering something but I thought the settings for external keyboards and/or the way the device driver manifest thingy is set, the keyboard is an ALPHA mode vs FULL keyboard mode, and ALPHA will auto-caps first letters for you. per @EskeRahns 2 year old comment.

Welcome. Both on stock Android, LineageOS 18.1 and AICP Q, the Pro1 got a stamina around 10 days connected but idle. So much a matter of what you want to run on it, and how much screen-on time your usage pattern requires. It also matters if your normal usage is mainly outdoor in the sun or indoor, as brightness affects the power usage. There are other threads on Pro1 stamina in here.

Battery life is pretty good on Pro1 and should get even better on Pro1X. You can easily go through a day of normal use with a full charge. Two if you are being careful.

"Oops". I have opened a change with this keymap fix at https://review.lineageos.org/c/LineageOS/android_kernel_fxtec_msm8998/+/315195 I think the problem is that none of us actually have a QWERTZ layout Pro1, so the keymap may not have been well tested 😞 I can revise that change with any other mapping errors you find.

it's definitely done in software as it depends on the app used

Thanks. My point is that while I want sticky modifiers, i don't want autocapitalization 🙂 so switching back to full doesn't do the trick

Having done this before, the changes are straightforward. See: https://review.lineageos.org/c/LineageOS/android_kernel_fxtec_msm8998/+/315183

For me, the biggest annoyance of the Pro1 keyboard is that it's impossible to turn off autocapitalization. Some time ago I took a quick look at the sources but I didn't find the root cause. This seems to be done by the Android userspace. Did anyone find a root cause or a workaround?

Hi there, newbie here. Just wondering if there is any feedback from users of the existing product on battery life and particularly if any 'experts' have an opinion of the likely battery performance of the new model due in November. The specified battery seems a little light by today's standard. Or does the de-cluttered linux OS take away much of the background battery consumption?

It built alright in the LOS 16 tree. Flashed it some minutes ago. Fn-Tab and Fn-Shift-Tab work as expected. I could not spot any regressions up to now. I will keep this build for the weekend and report.

Yellow arrow

I obviously don't build LOS, but I've never had a problem with Gapps showing up when sideloading LOS via ADB. I have always used @tdm instructions, as mentioned by @EskeRahn. I adb sideload the latest LOS nightly, then reboot to recovery, which changes you from the a/b partition you were on to the other a/b partion where the update was installed. Then I adb sideload Magisk and Gapps (in that order, if it makes a difference-- I don't think it does).

On the subject of "it's obsolete the day it's out", well yeah, it's true and the price is a little bit out of touch compared to Samsung mega factories, but it's not the same production scale, and we have enough alternatives if we must. But this obsolescence is not very surprising tbh: I never bought a phone people were not scoffing at one year later, asking me when I'll upgrade... at best. Most times they look at you with pity you couldn't buy the latest iphone the day you got your normal "I'd rather buy cheap phones I can break than break a 1.2k iphone and have to pay hundreds for a new scree

SafetyNet was passing, Google Play said I was certified but still I could not find Netflix in the store. Changed my spoofed fingerprint to Samsung Galaxy S21 SM-G991B (11) did the data reset and reboot et voilà... Netflix is there!

I got a response from Fxtec on my support ticket: Hopefully they do fix it for the Pro1, and not just the upcoming Pro1 X!

Just got the Pro1 today and somehow got it working on Verizon based on the instructions here. Context: I have an existing account with Verizon. I've been swapping my sim to new devices for years. I've been carrying my sim from Droid Turbo, Turbo 2, Moto Z force, Moto Z2 force, Pixel 3 and now to the FXtec Pro1. Steps I took: Insert existing active sim from Pixel 3. Skip initial setup step to setup network Connect to wifi Update to latest update go to dialer enter *#*#4636#*#* Enable all toggles under phone 1 Set network to LTE only

There is but it doesn't provide any autocapitalization setting