Jump to content

Search the Community

Showing results for tags 'pro1-los'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • F(x)tec Community
    • Documentation
    • General Discussion
    • Pro1 - Thoughts & questions
    • How Tos
    • Support
    • Bug Reports

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start



Found 7 results

  1. Greetings, I have one of the fancy Pre-Christmas devices (Lineage). I had horrible problems with ticks and poor sound quality upon recording (mainly uneven recording levels, distortion to the point of being unintelligible). Fxtec asked that I return the device (at my cost) and was told the sound card was replaced. The recording issues remain. There is no answer for 45 days despite repeatedly responding to the last message from Fxtec support on 21JUL21 of: "Dear Gene, We're sorry to hear about this. Different microphones are used to record different things. When you use the voice
  2. I've implemented a new feature in Lineage OS Pro¹'s keyboard driver to be able to use Fn+Tab as Alt+Tab as this is most convenient for multitasking with two thumbs. This thread is to track that issue specifically so please stay on topic. I'm trying to contribute this back to official Lineage repository. Here is my change request on Gerrit: https://review.lineageos.org/c/LineageOS/android_kernel_fxtec_msm8998/+/315155 There was also a pull request on GitHub but that's just going to be closed as the GitHub repositories are just mirrors I guess: https://github.com/Linea
  3. On Lineage OS 18.1 I keep getting in situations where the fingerprint sensor won't work until I unlock to phone with PIN. That was somewhat of an issue before but since I changed my case it's annoying to the point where the fingerprint sensor is almost useless. I'm assuming most those issues are related to the fact that the fingerprint sensor gets temporary locked after 5 failed attempts and permanently locked after 20 failed attempts. Though on stock it would show a message on the lock screen telling you your fingerprint sensor is disabled, on LOS I don't get such message. My new case en
  4. On stock Android I was using Fx Service color filter feature to basically implement my own Night Light version. With Lineage OS we can look at it from a device manufacturer perspective and better customize Night Light as explained there: https://source.android.com/devices/tech/display/night-light My goal would be to make it darker than it currently is at maximum intensity, by either just changing the temperature range or even fine tuning those equations parameters. I'm also not that crazy about the Amber offset so I guess I would try to make sure it's not too pronounced. Moreover may
  5. 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
  6. While working on our keyboard I could not help but noticed those oem_halla and oem_hallb GPIO events definition: https://github.com/LineageOS/android_kernel_fxtec_msm8998/blob/lineage-18.1/arch/arm/boot/dts/qcom/msm8998-qrd-skuk-t5.dtsi As I'm the developer of Fx Service which provides smart case functionalities for Pro¹ I can tell oem_halla is the case close event and I'm guessing oem_hallb is the case open event. @Sean McCreary Is there any chance we could reroute those events to Android Sensor API somehow? I reckon that should make them more useable especially the case o
  7. Just wanted to provide links to source files that makes our Pro¹ keyboard. That can be used as reference for anyone wanting to understand and customise Pro¹ keyboard experience by building Lineage OS. From low to high level files we have identified the followings key components: Device Tree Structure Include, contains GPIO pin mapping to scan codes: https://github.com/LineageOS/android_kernel_fxtec_msm8998/blob/lineage-18.1/arch/arm/boot/dts/qcom/msm8998-qrd-skuk-t5.dtsi Permalink Driver, brings together GPIO and aw9523b controller input to define the scan codes sent to user space: h
  • Create New...

Important Information