[OFFICIAL] LineageOS 20 for Pro1-X

[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.

 

[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?

 

[Jormsen]

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?

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.

 

[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.

 

[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.

 

[npjohnson]

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.

https://review.lineageos.org/c/LineageOS/android_kernel_fxtec_sm6115/+/358195 - fixed

 

[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.

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.

 

[qsnc]

nice hint, thanks. does that still happen with the latest update?

 

[Jormsen]

nice hint, thanks. does that still happen with the latest update?

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.

 

[Jormsen]

nice hint, thanks. does that still happen with the latest update?

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 [email protected]_64

Is this planned to get fixed in one of the next updates?

 

[Jormsen]

False positive.
After 77h uptime it died again.

 

[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?

 

[ColdCamel]

nice hint, thanks. does that still happen with the latest update?

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?

 

[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??

 

[ColdCamel]

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??

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)

 

[qsnc]

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?

heya, yeah, please send me a link to your logs privately.
also, the fp works fine for me

 

[ColdCamel]

hey have you seen that in the Beta folder there is a 2.1.7 build (...)

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

(...) so I wonder if this beta build is somehow helpful.

@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?

 

[ColdCamel]

I would like to report that on my Pro1x the fingerprint sensor doesn't work on Lineage (...)

Also the sensor doesn't work on latest DivestOS build (...)

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!

 

[qsnc]

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?

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...

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!

no worries good to know its working!

 

[ColdCamel]

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

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