yashsingh1/xdaforums huggingface dataset:
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] Hookmt:
Another power related issue. This version of lineage either ignores or in some manner prevents/countermands the effect of the fastboot command "fastboot oem off-mode-charge 1", which should make it so the Pro1x can be plugged in to charge without booting. It worked when the Pro1x was on stock and it works on my Pro 1 with Lineage 20. But the Pro1x with lineage always boots if you plug in power to charge when it is off.

The danger of this is if you tend to let your battery to a maximum drain, it can fail to charge if it is trying but failing to boot. Not common, I'm sure, but if it happens you are bricked unless you open it up and provide a direct charge to the battery, which is not easy.

I reported it as an issue.

Phone Cannot Be Prevented from Booting When Charger Connected While Off (#5773) · Issues · LineageOS / issues / android · GitLab

Expected Behavior If you enter the following fastboot commands it should prevent the phone from booting up every time you connect...

gitlab.com

Seems odd to me that Lineage would affect this, but others in the community forum have reported it.

Any thought? @npjohnson @qsnc
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] SpocchioS:
Thanks for the build! I received my pro x yesterday and flashed your rom.

I have only 2 questions.

I failed to sideload gapps.

Can I flash them even if i have already booted the phone? Or have I to do a clean install?

Magisk works?
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] pak_man:
Here are some community posts showing what is involved if this does happen:

* Disassembly: https://community.fxtec.com/topic/3862-on-charging-a-depleted-battery/?do=findComment&comment=66139

* Charging: https://community.fxtec.com/topic/3862-on-charging-a-depleted-battery/?do=findComment&comment=66306

This makes me a bit nervous about flashing LOS until offline charging is fixed in LOS.
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] npjohnson:
Simple case of offline charging broken, we didn't break fastboot, offmode charge is a bootmode that isn't working. We will work on it.

No, you need to start over to use GApps.
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] Ronaldusmax47:
hello can anyone help me to install lineage os. i will be willing to pay to help me i cant figure out 2the whole abd file etc..... please email me if you can help i would really appreciate it

starsimmons72gmail.com

thanks

ron
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] npjohnson:
you really shouldn't use it if you can't recover from problems - you need to know that stuff to know how to recover - the wiki is pretty detailed, where are you getting stuck?
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] Ronaldusmax47:
Getting the abd installed. Seems I installed but stil shows triangles the yellow ones in. The device manager

Thanks
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] npjohnson:
Did you follow the guide to install the driver?
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] Ronaldusmax47:
I did. So just stuck so can't move forward very frustrating but maybe I'll try a Mac computer
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] npjohnson:
To be candid, there is no driver requirement on macOS, so it is easier in that sense.
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] Ronaldusmax47:
Ok ty. I am visual person of knowledge and training even though I am retired vet I would like to have. Video or pics showing each step
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] npjohnson:
Yeah, sorry, we don't do video guides. They end up outdated within a month.
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] Ronaldusmax47:
Totally understand I just wished someone could walk me through it via phone or video live but asking a lot there. I'll figure it out
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] jan4321:
hello,

pro1x campain newsletter points to this topic for reporting issues, therefore reporting this one...

there seems to be a bug that results in unusability of chrome, chromium, brave etc. due to fingerprint reader issue. it has been diagnosed as

"

This problem existed on the initial stock Android ROM, 2.1.2, but was fixed in the 2.1.5 gms-less Android ROM that was subsequently released.

For some reason, LOS devs must have been given the initial vendor blobs where the problem still existed.

"

steps to reproduce are described in https://community.fxtec.com/topic/3...t-reader-on-pro1x/?tab=comments#comment-66445
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] jan4321:
I am getting updater notifications which allows me to easily update LOS. Where can I found changelog of each release before installing it?
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] MisterPib:
LineageOS Downloads

download.lineageos.org
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] Jormsen:
I only recently noticed the fingerprint reader issue, that was fixed on stock android beta, being still there on LOS.

Somehow the reader seems to be constantly active, it causes page reloads on chrome if you touch it.

I don't know what the change on stock android was, but it fixed it for everybody. Maybe you could get more info on what was changed to also put that fix in LOS.
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] qsnc:
i can't reproduce this behavior, the fingerprint sensor works correctly on my device. are you running plain lineage without anything weird like some magisk modules, xposed, or something that enables fingerprint navigation?

also, maybe you are able to provide me with a full logcat, so i can see what's going on?
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] Jormsen:
Right now I have Magisk installed, but also before magisk it was like this.

It is a known bug on stock android only showing in google chrome.

On lineage it's also only in the play store chrome browser not in the lineage browser.

Open a page in chrome and touch your finger print reader and it will reload that page.

If you tell me how I can try to provide logs.
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] Jormsen:
Is it only me or did the latest build (2023-06-01) change anything about the fingerprint sensor?

It works fine after booting for some time, but keeps braking after some hours uptime. I can't unlock my phone after about 10h uptime by fingerprint. Also the the issues of reloading pages in chrome disappeares after that time.

Sensor tools recognize it being there but testing its function they don't recognize touching it.

If it's only me it's most likely a issue of my device or needs reflashing to fix it, but it happendd right after upgrading to the latest build.
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] qsnc:
thanks, that helps, a log will be unnecessary. actually i found the problem, we are currently testing a solution internally. should be available to everyone soon enough.
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] npjohnson:
https://review.lineageos.org/c/LineageOS/android_kernel_fxtec_sm6115/+/358195 - fixed
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] Jormsen:
It still stops working, but doesn't seem to be tied to uptime but to failed attempts.

Could some code to reset failed attempts be missing?

To my knowledge it should reset after reading the correct fingerprint and after unlocking by pin or pattern (I'm using pattern).

After some failed fingerprint attempts it stops asking for fingerprint and won't recognize touching the sensor.
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] qsnc:
nice hint, thanks. does that still happen with the latest update?
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] Jormsen:
Still happening on 2023-06-08 update (seems to be the latest one right now)

Edit: Though I can't reproduce it by giving it the false finger multiple times and then unlocking by code. But still after some time it stops reading the sensor. Does not read it when trying to unlock the phone nor when a app asks for fingerprint authentication.
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] Jormsen:
After 2 days uptime on the latest update (2023-06-23) it seems to be fixed.

Thank you!

By the way:

Someone told me the camera fix will also be in one of the next updates.

I still have to do it for every boot right now.

setprop vendor.debug.camera.eisv3enable 1 & killall -9 android.hardware.camera.provider@2.4-service_64

Is this planned to get fixed in one of the next updates?
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] Jormsen:
False positive.

After 77h uptime it died again.
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] ColdCamel:
hey have you seen that in the Beta folder there is a 2.1.7 build put there on June 15th? Oh, this build has "20230417" in the filename so I don't know if it is something new.

Anyway I'm a bit new here (I just bought a used Pro1x), so I wonder if this beta build is somehow helpful.

And second question: this forum thread is the official/main for Pro1x LineageOS right?
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] ColdCamel:
I would like to report that on my Pro1x the fingerprint sensor doesn't work on Lineage (

lineage-20.0-20230622-nightly-pro1x-signed.zip).

But the sensor works on my phone on stock Android 2.1.2 and 2.1.5

Also the sensor doesn't work on latest DivestOS build (divested-20.0.-20230621-dos-pro1x.zip which is based on recent state of Lineage - at least DivestOS maintainer says it is much newer than previous release lineage-20.0-20230608)

The problem:

when I want to enable finger scanner and proceed to setting it up, then after I touch my finger first time the UI advances to the screen for repeat touch but it is just keeps telling me to do this, everytime I touch it deosn't read.

So the fingerprint symbol inside the ring starts showing up in red and disappears, and then it tells me to lift my finger and try again, and it's like that forever.

(in DivestOS it is a bit different - when I start the setup of fingeprints, then immediately at the moment of starting of the process there is the error "Enrollment was not completed: Fingerprint enrollment didn't work. Try again or use a different finger".)

I am new to this "alternative OS" stuff, but I gathered some logcats (for the first time hehe), should I somehow present them?
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] MrMEEE:
I'm having issues with calls, especially on gsm..

Also, I have gotten Google Wallet to run, but nothing happens when I try to tap-to-pay.. have anyone gotten it to work??
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] ColdCamel:
I am using a degoogled OS (DivestOS and if LineageOS then also degoogled), so I am not interested in paying and I don't remember correctly, but I think that I've seen someone talking about this.

So remember to look on the official forum (community.fxtec.com) and on unofficial community chats (Telegram and Discord)
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] qsnc:
heya, yeah, please send me a link to your logs privately.

also, the fp works fine for me
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] ColdCamel:
I tested this 2.1.7 and the connectivity problems seem to be the same, I am going back to testing LineageOS for now and later I will be also testing DivestOS

@qsnc so is any of these beta builds helpful in anyway to Lineage? I mean it is closed source, but perhaps you sometimes take out some updated blobs or something? :)
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] ColdCamel:
oh noooo.... I was mistaken. The fingerprint sensor does work in LineageOS! :)

It's just that the UI of the circle was weird visually so I thought it was not progressing while scanning.... but the circle does progress and it scans, and the fingerprint does work! And fingeprint also works in 2.1.7 stock beta.

So the issue is only in DivestOS. Sorry for the mistake!
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] qsnc:
we are well aware of these builds, but so far: no, not helpful at all, there have been no noteworthy updates other than 2.1.7 including exFAT support, which allowed us to enable it for LineageOS too (thats a licensing detail).

i should probably add this: do not get your hopes up, the conectivity problems are not software related...

no worries :) good to know its working!
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] ColdCamel:
Thanks. I don't have high hopes, I know the radios are weak but I just experienced that LineageOS definitely has less calling&audio problems than stock Android
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] qsnc:
strictly speaking, there is an antenna problem... if anyone can remember the iphone 4's antennagate... ;)
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] limited_imagination:
Thank you @qsnc and @npjohnson and @mccreary and everyone continuing to support this project.

I noticed that your current version of LOS 20 has solved some problems with Bluetooth HD codecs that were present in the Fx Tec stock Android roms, and the earlier unofficial LOS 20 builds. I'm not sure at what stage that fix was done, but thanks very much, it makes the device much more useable.

Pro 1x sends constant "Suspend" commands to Bluetooth headphones

Just wondering if anyone has this issue, or could advise. I have a set of HyperX bluetooth headphones,and they pair easily to the phone, but there is no audio. The phone keeps suspending them and defaulting to its own internal speakers. I enabled a Bluetooth snoop log in the phone, and looked at ...

community.fxtec.com

I'd like to suggest an additional Bluetooth tweak, if it's possible and you have the time. The problem affects a lot of people with cars and head units built before 2016, who want to pair their phones and have incoming SMS messages read through the head unit of the car.

In the bad old days before Android Auto, say pre-2016, a lot of car manufacturers made use of the Bluetooth Message Access Profile (MAP) in phones, in order to get the car's head unit to read out SMS messages hands free.

I have a Parrot Asteroid Smart in my car, that works the same way as it does for these car manufacturers' head units.

Whenever I have had a new phone do a Bluetooth pair with the Parrot, I'll get a popup on the phone to confirm that the Parrot may have access to the phone calls and contacts list.

But on Android 6 and earlier phones, the phone popup would

also

request access to "Message Access", so that the SMS reader on the Parrot would work.

I suspect that at some point in Android development, in Nougat or newer, Google locked down permissions for Bluetooth MAP and MAS connections by default. Web searches show an explosion of complaints about five-ish years ago, where car owners started complaining that the SMS feature suddenly stopped working with newer phones.

I see that "READ_SMS" is now a "hard restricted permission" with a protection level of "dangerous".

https://developer.android.com/reference/android/Manifest.permission#READ_SMS

When connecting my Pro 1x on LineageOS 20, the Parrot only reports that it has "Phone, Multimedia" connections, but with my old Blackberry Priv with Android 6 (Marshmallow), the Parrot would report "Phone, SMS" connections. The Priv is the last phone I've had that worked properly with Bluetooth MAP and MAS on the Parrot.

It would be awesome if the Pro 1x could have its Bluetooth MAP be made to work with all these older car head units and my Parrot.

I've done a Bluetooth HCI snoop and looked at what happens when the Pro 1x initially pairs with the Parrot, and there are clearly attempts being made to access the MAP profile. Happy to upload that log if you would find it useful, but the most interesting entries to me are these (MAC addresses removed):
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] dicer42:
Any news on this? I tried enabling the charge mode like this:

fastboot oem enable-charger-screen
OKAY [ 0.000s]
Finished. Total time: 0.000s
fastboot oem off-mode-charge 1
OKAY [ 0.000s]
Finished. Total time: 0.000s

but no luck so far with the latest lineage builds.
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] stasila:
Hello!

Is anyone using pro1x with LOS as a daily driver? 🧐

I'm running it for over 3 months. There are 2 very annoying problems:

1. Fingerprint sensor sometimes stops to work. Randomly. Only reboot helps.

2. Sometimes UI hangs somehow related to lock/unlock. If power button is pressed - display shows only status bar and bottom white line. I can pull drop-down menu, but can't do anything. If i press power button and then chose "Lockdown" and later unlock - sometimes it works again, like entire UI restarts. Threre are no previously used apps visible, but apps are running. Sometimes only reboot helps.

I'm running always latest build.
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] dicer42:
I don't use the fingerprint sensor, but I have never seen your second problem and I do use my pro1x with Lineage as a daily driver. so probably some additional software you installed.
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] stasila:
I reported the problem before: in official LOS 20 ui is crashing from time to time. I found the reason for that.

It looks like LMKD misbehaves or works too aggressively.

I was able to reproduce the problem.

If i open several heavy applications at some point the lowmemorykiller kills com.android.launcher3 and all dependencies.

lowmemorykiller: Kill 'com.android.launcher3' (17383), uid 10167, oom_score_adj 0 to free 86564kB rss, 6016kb swap

After manipulations with lockdown and unlock at some point UI is responsible again.

I killed /system/bin/lmkd process and now the phone is working as expected.

in the getprop output i have several lmk related settings:

adb shell getprop | grep lmk

[init.svc.lmkd]: [running]

[init.svc_debug_pid.lmkd]: [18357]

[lmkd.reinit]: []

[persist.sys.lmk.reportkills]: [true]

[ro.boottime.lmkd]: [4019922966]

[sys.lmk.minfree_levels]: [18432:0,23040:100,27648:200,32256:250,55296:900,80640:950]

[sys.lmk.reportkills]: [1]

Any ideas how to fix that?
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] qsnc:
that message hints at extreme memory pressure, that should not happen on a device with 6gb ram unless you have something that eats away at it...

for further info, send me a pm with outputs of the following (you are going to have to run some of them as root):

free -h

ps -A --sort -rss

cat /proc/sys/vm/swappiness
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] stasila:
Sent to the private conversation.
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] stasila:
Hello @qsnc, @npjohnson and @mccreary!

Do you have any advice how to debug and fix the lowmemkiller issue in LOS 20.

This issue was as well confirmed by other user in the telegram channel fxtec community.

Im not an android developer, but familiar with Linux.

Please let me know how I can contribute to the problem resolution.

Thanks in advance!
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] stasila:
Looks like i found the workaround.

Try to run from adb root shell:

setprop ro.lmk.kill_heaviest_task true
setprop lmkd.reinit 1

After that phone behaves as expected even if i try to open all existing apps in sequence. Launcher runs and phone works.
[F(x)tec Pro1-X ROMs, Kernels, Recoveries, & Other ] npjohnson:
this is fixed in builds fwiw - was long ago.
[Xiaomi Mi 9 Questions & Answers] fjsn:
Hi, developers, can you share with me your blobs you're using to build your roms for this phone?

I'll extract them from my phone and check if I can contribute to them if possible also I want to try by myself build lineageOs.

Thnks in advance and greetings c:
[Touch Pro CDMA] cd85233:
Hey guys, I ran into quite a predicament today. As I was walking to work, I fell something fall out and slide half way across the parking lot. I felt me phone case (the crappy one that came with the phone), looked down on the ground and noticed it was my AWESOME Sprint Touch Pro. With the site of my phone moving in a hockey-like manner, I finished cursing and decided that I don’t want to have such an amazing phone looking like a piece of crap.

So here is where I am at. I need to get this phone fixed. I think that I might have a few options, but I want to know what you guys think. Originally, I bought this phone from a guy of Craigslist; it was $240, if you can believe it. Now, the phone had never been activated, so it was as if I was the original owner. Additionally, I never got a phone from sprint, but I am under contract. That means, according to sprint, that I am eligible for a new to get a new phone at anytime. Thus, I reach my questions and request for opinions.

Option 1 (least likely): Since the phone was never activated, can I still claim the 30-day phone guarantee from sprint? Meaning, can I return the phone as if it was defective?

Option 2 (What I will probably have to do): Should I buy a phone, get the equipment protection plan, and then process my touch pro as a defective phone. This seems like a relatively good idea, because I can get a phone pretty cheap (like the rant) and sell it on Ebay. So in the end, I make money off of this idea. The only down side is that my contract restarts, but I have only been with sprint for about four months. Also, I was going to save my free phone upgrade for next year so I could get a brand spanking new phone.

Option 3 (Don’t want to do this): Suck it up, and get a silicon case that covers the scratches. The scratches are only around the shiny part on the perimeter of the screen, which, by the way, says a lot about the quality of the screen.

Option 4 (Too much trouble): Sell it on eBay for as much as I can, and since it’s probable less than $300, put the rest out of pocket and buy a brand new touch pro from sprint.

Option 5 (Does it exits?): look for replacement housing. Since the phone is new, I don’t know if it’s even out there yet.

Thanks for all your input guys. I really hope to hear from some Sprint Reps or something. Meanwhile, I am going to try to sucker Sprint into helping me out.

P.S Yes, I know what I am doing is unethical, and that the phone is not really defective, thus I should not be returning it as defective.
[Touch Pro CDMA] thacounty:
I think I am having trouble understanding what happened. You have scratched your touch pro that you bought from someone else, I got that.

You never activated the phone on sprint? You should go ahead and put the phone one your account and get insurance immediately!

If you have only been with Sprint for 4 months how are you eligible for an upgrade?

If it is only chrome scratched my TP came like that. Look at the chrome around the keyboard section. At all 3 corners, excluding the Stylus one check for a "Seam" in the chrome, if it has this you can take it in and exchange at a Sprint store.

A scratched phone on Ebay will go for MUCH less than a regular one.

I am not here to tell you whether you are ethical or not, but you should exhaust all options that seem less unethical first before trying to make someone else pay for your mistake. That being said, I think everyone in the world would try to get a new phone for free, so I wouldn't feel too bad.
[Touch Pro CDMA] cd85233:
The phone is activated on sprint, but the person that sold it to me never activated it. It has been only a few days since I activated, can I still add the TEP? And are they going to charger a deductible, cuz they'll charge me $55 to fix it.

I am eligible for an upgrade cuz I never got a phone from sprint.

So if it has some defects I could take it back, even though I have no TEP? Unfortunately, the phone is flawless other than my stupid scratches.

TBH, I don't fell doing this to sprint. They have screwed me over many times over. This would just even it out.