yashsingh1/xdaforums huggingface dataset:
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] qsnc:
Introduction

If you don't know LineageOS and would like to read about it before installing it you can take a look at the official Website.

Features

Individuality

Security

Longevity

Installation

If you are on stock OS, you need a custom recovery first. You can get the recommended recovery in the installation instructions below.

If you are coming from stock or other ROMs, you must do a factory reset. If you are upgrading from an older release in this thread, you do not need to reset!

As always, make sure to backup before installing this ROM.

More detailed instructions at:

Install LineageOS on pro1x.

Downloads

Download LineageOS 20

Google Apps package: MindTheGapps

Source code

All the source code for LineageOS is available in the LineageOS Github repo.

If you would like to contribute to LineageOS, please visit out Gerrit Code Review.

The device specific source code can be found in the LineageOS Github repo.

F(x)Tec Pro1-X device tree

F(x)Tec SM6115 kernel

Bug Reports

Please submit bugs and other errors in this thread.

Donate to support development

Donate via PayPal to vware

Or donate to LineageOS project: PayPal donation

Contributors

Georg Veichtlbauer

Sean McCreary

Nolen Johnson

And of course all LineageOS & Android contributors

Version Information

April 27

* Cleanups

* Fix A2DP

Spoiler content hidden.

OS Version: Android 13

Kernel: Linux 4.19.275

Created 2023-01-20

Last Updated 2023-04-21
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] npjohnson:
Woohoo!
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] Hubertus Bigend:
Excellent!
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] eltmosen:
Tested and works a treat!

Not afraid to play captian obvious or help new users here, so adding

Step 2 can be done in adb during android runtime if the finger combo did not work out:

adb reboot bootloader

Step 4 can be:

fastboot reboot recovery

Thanks a lot qsnc! Great work
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] dicer42:
Is it necessary to backup the persist partition like described here: https://community.fxtec.com/topic/3...o-the-pro1pro1x-available-for-download-links/

Or was that only a problem with early Ubuntu Touch releases?
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] eltmosen:
Its always advised to backup whatever we can before tampering with anything.

That put upfront. No, the persist problem is only reported to be UT and SFOS related. Since those write into persist while out of SELinux context. Which can easily be repaired when back on stock and rooted.

I have not tested for lineage but i assume it uses the SELinux correctly just like stock and thus no problem should® appear.

If i am wrong here, the fix for the persist problem is reliable and easy to do. Just go for it imo.
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] limited_imagination:
Awesome work, thank you!

I have a Pro 1x, and unfortunately it is completely useless for voice calls on LTE, and very unreliable for voice calls on GSM.

It's a notorious fact that at this point the Pro 1x is really just a small Android tablet with a mechanical keyboard, not really a phone at all.

I understand Fx Tec is working on new firmware to try to address the problem, but nobody knows whether that is actually going to happen, or when.

So my question to all who have flashed this version of LineageOS, are you seeing any better result with voice connections, or is that too much to hope for?

It would be so awesome if the LOS devs have solved what Fx Tec hasn't yet (or can't). Multiple beers/coffees would doubtless be forthcoming to them. :)
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] qsnc:
I am glad it's working well for you guys!

Regarding the call problem: could you describe in more detail whats wrong? If it's a hardware or modem firmware issue, there is nothing we can do. There are some things we can try if audio quality isn't good for you though. During development, calls have actually been decent for me, I did have trouble with signal strength (nothing we as LineageOS can do about that, unfortunately).
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] limited_imagination:
Lots of discussion on Fx Tec's own forum, it's a known issue for a huge percentage of users since they first shipped in August.

Strangely, some people don't have as much of a problem, and the reason for the difference in user experiences is not clear yet.

So it's interesting @qsnc has not experienced it noticeably. Was that also the case for you on stock Android, or only after you flashed it with LOS? If the latter, then that's really good news...

My experience is that with stock Android on LTE, only maybe 10% of the time can I place an outgoing voice call. There is just a "click" and dead air when I finish dialing. It's a much higher percentage of time that I can place calls when I set the phone to use only GSM, but people calling me on GSM usually get a "This user is not available" message, it doesn't even go to voice mail, and does not ring my phone. That is the message that callers get pretty much every time they call me, if the phone is set to use LTE.

Fx Tec rep @Casey at their forum states that this is known to be a notorious problem, and " it is our top priority issue along with the battery protection":

Pro1x - really poor connectivity to both wifi and cellular.

community.fxtec.com

Voice over WiFi seems to work more reliably, both for receiving and placing voice calls. Not perfect, but more reliably.

On those odd occasions where voice calls do connect, regardless of whether using LTE/GSM/VoWiFI, the volume is almost at 0 unless you trigger the speakerphone, then once so triggered you can go back to the normal microphone and it will usually be broadcasting at normal volume (though not always):

Pro1X: Internal microphone/speaker issues - low gain, sensitive feedback avoidance?

Two Pro1-X issues, possibly related. First, the built-in microphone gain is extremely low. it makes my spouse completely inaudible during calls and only barely audible using a sound recording app. When we attach a wired headset, the microphone gain is fine. Second, and this one is really weird, w...

community.fxtec.com
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] qsnc:
That sounds like a couple of compounded problems. Honestly, I did not use stock at all except for a quick functionality test.

So the connection problem could be firmware and/or antenna related, I heard some people have problems with signal strength, even on our dev team. Not much we can do about that.

The volume problem most likely is not firmware but OS related, and I have not noticed such an issue on Lineage. Have you? Has someone else?

Of course, only Lineage specific problems can be dealt with here...
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] limited_imagination:
I just flashed and tested it. Good news: it flashed perfectly and started right up. Thank you!

Bad news: voice telephony behaves just as bad as stock Android. On LTE, placing a call, it just gives a "call ended" message on the screen, and doesn't even try to connect. Also, it will not receive a call on LTE, it just goes straight to voicemail for the outside caller.

Voice calls will work using GSM, but a bit more flaky than stock Android. The phone will sometimes ring, but there is no way to answer an incoming call. After the caller hangs up, I can see their call on the recents list.

Screen touch is a bit odd w/r/t stock Android, too. Swipe up seems to either lag or not work quite often.

Thanks again for including the 1x as a project, and I hope you stick with it.

Also, hopefully Fx Tec deals with the stuff that is beyond the remit of LOS.
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] mccreary:
Could you tell us the signal strength reported by the pro1x when you are having trouble with voice calls? You can find this in Settings->About phone->SIM status->Signal strength, and it should be something like "-108 dBm 32 asu" (but hopefully better than that).
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] rasva1:
I must thank a lot for this release, it improved the user experience compared to 2.1.5 non GMS firmware I was using.

So far I observed two bugs:

- NFC cannot be turned ON.

- screen with pin code in landscape mode is distorted, but pin still can be entered on screen or via hw keyboard

As for LTE (and wifi) connectivity, I do not think lineage can fix this, it is either modem firmware (I hope so) or antenna issue (I am afraid of).

Myself I did some measurement and to me it seems the problem is only on some channels/frequencies. Looking at the details I posted in Fxctec forum:

Channel B1, B9, B20 are quite OK to signal level around -110dBm (B1 was far the best), Channel B3 was a big problem even at -85dBm.

The problem I see is that various people complain about "bad signal on LTE", but are not providing details.
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] qsnc:
new release is up, thanks for all the feedback! our team is working on an improved keyboard driver with more options coming, stay tuned!

see the first post for download options.
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] rasva1:
Thank you, NFC now works and actually is able to read the only NFC tag I have (it was broken on 2.1.5 stock)
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] KC_Cheung:
That's good news. Do you mind specifying what the NFC tag type was? This'll help us debug the stock firmware. Thanks.
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] rasva1:
It is Mifare Classic. On 2.1.5 I was getting someting like "NFC read error"
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] zstas:
thanks for the work!

one question, when keyboard is open and I use arrow keys for navigation - the direction is not right. up/down make left/right movement and vice versa (which kind of makes sense if you place the device vertically :) )

tried in launcher and terminal.

am I the only one who's experiencing this?
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] rasva1:
Wow, I am not using cursor keys much, but you are right, same here :)

But PageUp, PageDown, Home and End seem to work correctly.
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] qsnc:
and another one for the weekend, guys. see the first post.

we will work on the keyboard once our improved driver is done, which should be soonish.
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] kevgrig:
Just got my Pro1X and ran through these instructions and it worked! Just installed the 01/27 build. This is my first time doing this, so not sure if this is normal or not, but just wanted to note that the progress for step 5 was at 47% for many minutes (maybe ~5), but it ultimately worked:

# adb sideload lineage-20.0-20230127-UNOFFICIAL-pro1x.zip

serving: 'lineage-20.0-20230127-UNOFFICIAL-pro1x.zip' (~47%)

[...] After some minutes, it updates to the following and the phone shows the reboot option [...]

Total xfer: 1.00x
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] kevgrig:
I'm testing the 0127 build and overall it works great! However, using the physical keyboard, I cannot type any of the symbols on the number keys. With the stock OS, I would hold down the yellow arrow key and press a number. For example, holding down the arrow key and pressing 1 should type an exclamation point. The right arrow key also doesn't work. See attached video.
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] mccreary:
This is an unfortunate interaction with how Android applies language-specific key maps. Until we switch to the new keyboard driver, you must not "Configure the physical keyboard" by selecting a language and layout despite what the notification says. Just dismiss that notification by sliding it to one side.

To fix this problem, turn off all switches in Settings->System->Languages & input->Physical keyboard->Fxtec Pro1->Set up keyboard layouts, and reboot.
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] kevgrig:
That worked, thanks!
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] kevgrig:
BTW, in case this isn't already on your radar, one feature I would love to see with the physical keyboard is the ability to toggle keys like Shift, the arrow key, etc. For example, sometimes it's more natural to want to type a capital letter on the left side of the keyboard with just my left hand so I'd like to be able to click Left Shift with my left hand and then click a letter. Right now, I have to hold down Shift. I know there are the same buttons on the right side of the keyboard to do the same, but that's not always convenient.
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] fuqqer:
I installed LOS20 a week or so ago. Whenever I make a phone call using my car's bluetooth handsfree feature, the bluetooth disconnects from the stereo and I can only make calls over speaker. I made sure in the LOS20 bluetooth settings that the car is enabled for phone calls, media, contacts, and text messaging. How can I fix this?

Also, how do I "upgrade" to the latest build without losing all my apps/settings/messages etc?
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] mccreary:
Start at step 4, but skip the factory reset.
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] qsnc:
small update for people with wired headsets :)

... or with prototype screens
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] npjohnson:
;p
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] qsnc:
he who shall not be named
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] vollkorn:
Hi,

I noticed that the camera is not working in many apps. For example, in Signal Messenger when trying to take a photo from within the app or when using Threema and trying to scan a QR code from within the app (to connect with the Threema desktop app). Most of the times the camera picture is just plain dark as if the camera is not sending any images. Sometimes one frame loads, but is then stuck.

The on-board camera app works fine, though.
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] vollkorn:
Another bug I noticed is with USB. When I connect the phone to a computer and select "Data transfer" in the notification menu on the phone, it shows up just fine on my computer as an external harddrive. I can download files just fine, but when I upload more than a few small files (about 400 files/17 GB), the connection resets as if the USB cable was disconnected. My computer (Ubuntu) gives the following error message:

```

libmtp-Fehler: Could not send object info.

```
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] vollkorn:
Also, SafetyNet fails completely on this ROM. Is this expected?
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] kevgrig:
Confirmed trying to take a picture in Signal. Kernel warnings (cam_sensor_core_power_up), CamX error (camxopenode.cpp) and a SIGSEGV crash (com.qti.node.dewarp.so). adb logcat: https://pastebin.com/hn0hM7tS
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] kevgrig:
I'd like to upgrade LineageOS for the first time. What's the proper way to do a backup of my data first? I searched but couldn't find anything.
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] vollkorn:
For upgrading you usually flash the newer LineageOS ROM to your phone like you did with the first install. Make sure to install all parts of the ROM and install again MindTheGapps, Magisk, and/or other apps you had installed via fastboot or adb sideload.
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] vollkorn:
Oh, I just realized I misread your question. I use TitaniumBackup for backing up all my data. It requires having a lot of free space on your phone to put your backup in or you have to pay for unlocking the upload options.
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] mccreary:
Note that the pro1x has a Caps Lock key, and it should work in most cases where Shift would be used. Also, the default key character map we are currently providing defines parallel combinations for most of the yellow glyphs printed on the keyboard, so you can use either 'Fn' (the yellow arrow keys), Shift, or Caps Lock to type them. Unfortunately there are a few cases where this wasn't possible, e.g. '\' and ';'.

There are also a few other changes from stock: The 'F' logo key is now Meta, which means the old function of this key has moved to Meta+Enter (instead of the key being dedicated to bringing up the home screen). This enables all the other Android shortcut keys, which can be listed with Meta+'/'. This list of shortcuts changes based on context, so be sure to check it in each app to discover what new shortcut key combinations are defined (if any). We have also remapped Sym so it now generates AltGr (ralt), which is used by many of the native Android language overlays to type special characters. Just remember that if you enable any lanugage overlay, the Fn mappings will be overwritten and you won't be able to type '\' or ';' at all :(.

One final note: Android uses Alt+Meta internally for 'Caps Lock', and because they are adjacent on the pro1x it is easy to accidentally type both keys at the same time. If you notice that Caps Lock is stuck on even though the LED on the Caps Lock key is not lit, try typing Alt+Meta to turn it off. This one drove me crazy on the pro1 until I figured out the cause ;)
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] atomickarma:
Probably a silly question, but does Lineage enable HDMI-via-USB-C?
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] rasva1:
AFAIK this is a hardware limitation of SD662, cannot be resolved by LOS.
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] qsnc:
will try to reproduce that, so far it seems fine for me.

yes that is completely expected. lineageos by principle does nothing to hide the fact that it's not a first party os. there are plenty of ways to accomplish that, but none of them are within the scope of this thread, sorry :)

no, it does not.
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] atomickarma:
Expected as much, but I was given the impression fxtec could fix that shortcoming. as it was pretty much my only reason for backing the phone (beyond the keyboard). Disappointing.
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] deppiedave64:
Thanks for the ROM! It works great for me, except for one thing. I think I'm experiencing the same problem as described here:

It's similar with my Bluetooth headphones. Whenever I try to play some media while the headphones are connected, the media controls show that it is playing for a very brief moment, then switch back to pause. At the same time, the audio output switches back to the speakers, and in the Bluetooth settings my headphones change from being listed as a media device to being listed under "other devices". Any idea what might be causing this?
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] kevgrig:
I just noticed a major issue: When using the normal phone, the other person can't hear me. I don't use the phone much, so I hadn't seen this before. I'm confident I didn't have this issue with stock. But it has happened with multiple callers both with WiFi Calling enabled and disabled. I'm using the 20230130 build. I can call over Whatsapp no problem, so the microphone is fine. I tested this with my Mom many times and gathered adb logcat: https://github.com/kevgrig/Pro1X/blob/main/callingissue.txt?raw=true

Here are the timestamps:

$ date # Phone restarted fresh

Thu Feb 9 12:46:45 PM CST 2023

$ date # Checking WiFi calling and it's on

Thu Feb 9 12:47:19 PM CST 2023

$ date # Starting phone call

Thu Feb 9 12:47:42 PM CST 2023

$ date # Call finished, other person couldn't hear me

Thu Feb 9 12:48:11 PM CST 2023

$ date # Disabled WiFi calling

Thu Feb 9 12:48:25 PM CST 2023

$ date # Starting phone call again

Thu Feb 9 12:48:40 PM CST 2023

$ date # Call finished, other person couldn't hear me

Thu Feb 9 12:49:00 PM CST 2023
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] qsnc:
New build is up. Have fun!

If you know how, please create a full log of the call and send it to me privately, I will take a look.
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] kevgrig:
I'm glad to do that but how do I do it? I'll also first upgrade to the Feb 9th build. Thanks!
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] npjohnson:
Damn, okay, we will look into it - the logs below are helpful.

I can't replicate this - any chance it's the host/cable?

Yes - we don't do anything to force it to pass.

Damn, okay, we will look into it.

For now, flash ROM from recovery, flash MTG, reboot, profit.

No, this is a hardware limitation, but DisplayLink (which is what FXtec supports) does work.

See above reply, yeah - is the case.
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] kevgrig:
Upgraded to 20230209 but still have the same issue that people can't hear me on a regular call. I've got it rooted so glad to gather any data you'd like. I'd like to make some calls soon so I'm glad to test custom ROMs with more debug, etc.

On the bright side, the fingerprint reader seems better.

Trying to take a picture in Signal no longer crashes but just shows a black screen from both cameras. This is low priority for me but just an FYI. Pastebin: https://pastebin.com/JnmWZvfc
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] kevgrig:
I was looking through the logcat I linked before for the phone call audio issue and this seems potentially related with maybe a microphone failure (to emphasize, audio works fine in Whatsapp, for example):

02-09 12:47:44.032 0 0 E bolero-codec soc: qcom,msm-audio-apr:qcom,q6core-audio:bolero-cdc: ASoC: PRE_PMU: Digital Mic0 event failed: -22

I can see the same in the logcat from my last test.

Other errors around the above:

02-09 12:47:44.009 0 0 E send_afe_cal_type: No cal sent for cal_index 1, port_id = 0xb037! ret -22

02-09 12:47:44.032 0 0 E msm_cdc_pinctrl_get_gpiodata: device node is null

02-09 12:47:44.032 0 0 E msm_dmic_event: gpio set cannot be activated dmic_gpiod

02-09 12:47:44.032 0 0 E bolero-codec soc: qcom,msm-audio-apr:qcom,q6core-audio:bolero-cdc: ASoC: PRE_PMU: Digital Mic0 event failed: -22

02-09 12:47:44.099 0 0 E afe_get_cal_topology_id: cal_type 8 not initialized for this port 45104

02-09 12:47:44.099 0 0 E : send_afe_cal_type cal_block not found!!

02-09 12:47:44.119 0 0 E voice_get_cal: No cal data for cal 8!

02-09 12:47:44.119 0 0 E voice_send_cvs_register_cal_cmd: Voice_get_cal failed for cal 7!

02-09 12:47:44.120 0 0 E qdsp_cvp_callback: cmd = 0x11371 returned error = 0x2

02-09 12:47:44.120 0 0 E voice_send_cvp_register_dev_cfg_cmd: DSP returned error[ADSP_EBADPARAM]

02-09 12:47:44.121 0 0 E voice_get_cal: No cal data for cal 5!

02-09 12:47:44.121 0 0 E voice_send_cvp_register_cal_cmd: Voice_get_cal failed for cal 2!

02-09 12:47:44.121 0 0 E voice_get_cal: No cal data for cal 6!

02-09 12:47:44.121 0 0 E voice_send_cvp_register_vol_cal_cmd: Voice_get_cal failed for cal 3!

02-09 12:47:44.123 0 0 E qdsp_cvp_callback: cmd = 0x112c2 returned error = 0x1

02-09 12:47:44.123 0 0 E voice_send_vol_step_cmd: DSP returned error[ADSP_EFAILED]

02-09 12:47:44.123 0 0 E : voice volume failed

02-09 12:47:44.131 0 0 W HTB : quantum of class 10010 is big. Consider r2q change.

02-09 12:47:44.138 0 0 E qdsp_cvp_callback: cmd = 0x112c2 returned error = 0x1

02-09 12:47:44.138 0 0 E voice_send_vol_step_cmd: DSP returned error[ADSP_EFAILED]
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] vollkorn:
For a comparison, I used the same host and same cable with a OnePlus 5T to copy the same data in both directions. No problems. I left the table, so that any possible mechanical contact problems won't occur because of me touching the device, cable, or shaking the table.

In the end I copied the data via `adb push` without a hitch.

I believe it's a problem with the phone and am happy to debug, if you let me know what info you need. I work as an Android pentester and know my way around an Android quite okay.