Jump to content

Search the Community

Showing results for tags 'lineage'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

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

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


About Me

Found 6 results

  1. Just a thread for questions about Lineage OS custom builds. See: https://lineageosroms.com/pro1/#build See also: https://slions.net/threads/lineage-os-for-f-x-tec-pro1.90/ ROM update process: Sideload ROM Reboot to recovery Sideload GApps Sideload Magisk Reboot
  2. 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
  3. I've put together a guide from knowledge I gathered over the last couple of weeks as I eventually got around trying Lineage OS on my F(x)tec Pro¹: https://slions.net/threads/lineage-os-for-f-x-tec-pro1.90/ It takes you through the installation process from Windows setup to Magisk root and SafetyNet validation to working around prominent issues. It will also take you through the build process from Windows environment setup to development and code contribution. Also taking this opportunity to mention how awesome it is to be able to update, use and customize almost every aspect o
  4. 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
  5. 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
  6. Alright, after toying with it for a few days I have cracked dual booting and decided to write up the steps myself. YOU WILL LOSE YOUR DATA DOING THIS. Credit to @order#10248 for proving the concept. First thing you will want to do is re-flash stock android on your phone. There isn't an official repo for this yet but @Waxberry has kindly provided one on this post. Download and extract the files from there and run the script fastboot_all.bat or you can download my modified linux version flash_all.sh. While that is flashing, download the latest version of Lineage here. Yo
×
×
  • Create New...

Important Information

Terms