Development [ROM][OFFICIAL][alioth/aliothin][12.1] LineageOS 19.1

[eliezerjk90]

Hi.
I must retract my statement.
I run YASNAC to check SafetyNet and this failed.

View attachment 5643023

LOS 19.1 with Android 12.1 + Magisk 25.1 + Zygisk enabled + Universal SafetyNet Fix + MagiskHide Props Config + enforced Denylist + Google play services, Google Play Store and Paypal on the List...

And now the Paypal App is starting, but I can not login. After entering the login data, I come back in the empty input field. :/

And now I'm a little perplexed how to proceed.

The paypal app looping into login page is a bug I guess. I had it also eventhough I pass safetynet (with another rom). Try to clear data and cache, reboot, and login directly after restart. It does the trick for me. If we wait a bit after reboot then the problem would occur again (at least in my experience).

 

[Jabelor]

I am running syncthing-fork on los19.1 with microg and it works properly. i checked my logcat and I also got the same warning but i do not notice any effects.

What does not function for you in syncthing? i never used the vanilla syncthing, but I think syncthing-fork mainly has an extra gui that the vanilla version does not have. Maybe try syncthing-fork for debugging and import your config there?

Hi,

Sorry, I omitted that bit in my original post: I have tried syncthing and syncthing-fork and they are giving the same selinux error as shown in the original post. I have tried to set up new syncthing set of rules and to restore backup. Desktop syncthing can see new listener device however LOS blocks resolver so i cannot establish connection with my workstation and pull data to phone. I havent tried syncthing-fork in the latest LOS build from a few days ago. I might try again and I will post details.

I do run vanilla LOS, no Gapps of any sort.

p.s. There is this however i cannot really confirm or negate any relation to this report since i used syncthing from GPlay on certified android 11 device up until 2 weeks ago.

 

[Jabelor]

Hi,

Sorry, I omitted that bit in my original post: I have tried syncthing and syncthing-fork and they are giving the same selinux error as shown in the original post. I have tried to set up new syncthing set of rules and to restore backup. Desktop syncthing can see new listener device however LOS blocks resolver so i cannot establish connection with my workstation and pull data to phone. I havent tried syncthing-fork in the latest LOS build from a few days ago. I might try again and I will post details.

I do run vanilla LOS, no Gapps of any sort.

p.s. There is this however i cannot really confirm or negate any relation to this report since i used syncthing from GPlay on certified android 11 device up until 2 weeks ago.

I have tried syncthing-fork and it works. It shows the same errors related to selinux but it works. I might open an issue on github to see what syncthing folks are saying about this.

Thank you @barturblits : )

 

[CiupaSs]

@althafvly
Will you add an option which will block access to the quick menu if the screen is locked/blocked?
Thank you

 

[Boracho]

With the current release I have problems when using the front camera "couldnt open front camera multiple times. Try calibrating the camera". For some apps like whatsapp it is still working after closing the dialog. But lineage camera and gcam just close.

How ro fix that?

 

[krasny2k5]

For me everything is fine except one thing: the proximity sensor. I know that this phone does not have a proximity sensor and uses the gyro and the front camera as sensor but it is horrible to make a phone call without earphones because the screen is constantly waking up and pushing buttons.

Anyone has a fix for this? can be a problem of my unit? I don't think that this can be a rom problem because it is annoying as hell and I can't find posts regarding this issue.

 

[Boracho]

I have the same problem with calls.

What also annoys is that the fingerprint sensor is active when the phone is sleeping. I often accidentally touch it and then then random things are happening in my pocket lol. Correct way should be press power -> fingerprint active -> unlock in my opinion. For android 11 I used gravity box to override that behavior. For android 12 there seems to be no 3rd party workaround.

 

[avguser23]

I have the same problem with calls.

What also annoys is that the fingerprint sensor is active when the phone is sleeping. I often accidentally touch it and then then random things are happening in my pocket lol. Correct way should be press power -> fingerprint active -> unlock in my opinion. For android 11 I used gravity box to override that behavior. For android 12 there seems to be no 3rd party workaround.

Try this https://forum.xda-developers.com/t/app-alioth-software-proximeter.4454463/

 

[avguser23]

Do you guys have random screen clicks when you unlock the screen?

 

[erazemk]

Could you please enable "fingerprint wake and unlock" in the overlay file when compiling. This would prevent accidentally unlocking the phone when touching the fingerprint sensor.

According to this reddit post, this has already been implemented in LineageOS and just needs to be enabled for each specific device (check the original thread, not the embed, first comment explains it): https://www.reddit.com/r/LineageOS/comments/qxcfyc

 

[Boracho]

Could you please enable "fingerprint wake and unlock" in the overlay file when compiling. This would prevent accidentally unlocking the phone when touching the fingerprint sensor.

According to this reddit post, this has already been implemented in LineageOS and just needs to be enabled for each specific device (check the original thread, not the embed, first comment explains it): https://www.reddit.com/r/LineageOS/comments/qxcfyc

Yeah, this it what you could override using gravity box in Android 11. I never had any issues.

 

[krasny2k5]

That's a good idea, but we still need a fix for the proximity sensor during calls which is terrible annoying.

 

[Boracho]

Are there any open source ROMs that handle the proximity better? I personally never used a different ROM besides lineage, including MIUI.

 

[dash199t]

HI,
has anybody the problem, that when connected via Bluetooth to a car, no songnames are shown and the controls aren't working?

A normal Bluetooth headset works just fine, at least for the controls

 

[Rstment ^m^]

New lineage-19.1 builds has increased touch polling rate feature. Try using that. Settings-> Display -> High touch polling rate

Sry to blast your dms too just trying to make sure you'll see:

Touch polling fix is pretty nice and it alleviates lot of issues with the touch but sadly it doesn't fix the underlying issue with it -the touch recognition is skewed. Touch itself feels "alien" lol

I explained in dms like this:
I managed to figure out what's going on this time and it's not latency issue. It happens when you put your finger on the screen and hold it in place for a really really short time - like 200ms or less (0.2s)

Once you start moving finger after that short hold the touch recognition goes bonkers and tries doing a skewed swipe:

In pics above you can see what's going on - I am 100% sure it's not my finger moving at all. I only hold it in place for a short time then try to swipe up and this happens...

In daily use it is noticable during swiping/scrolling - and only happens on the initial swipe ! It looks like delayed swipe - as in your finger moves up but the screen is refusing to move for the short duration ( As you can see above most likely it's registering as a short swipe sideways , so that's where the lag is coming from ) then after that delay it starts working properly... Feels like a sluggish swipe - as in first half a second of swipe is not responsive then it wakes up and starts working properly

If you're swiping without removing finger at all it's practically impossible to get this skewed swipe to occur, it only occurs in the very first moments of swipe and as you can see in pics it happens randomly

I'll leave my guess here and say it may have to do with touch going to sleep after you lift your finger off the screen , then next time you place the finger back on the screen it ramps up and makes a mistake where touch >hold > swipe up is recognized as touch>hold>swipe sideways>swipe up

Low latency makes it feel less pronounced but it's still happening and the touch itself feels really weird and unnatural ...

 

[Rstment ^m^]

As much as I like your rom I can't bring myself to use it...

Hope it get's fixed Thanks

 

[Rstment ^m^]

Arrow - I haven't been able to replicate lineage issue at all , touch feels as good as stock

 

[don.nasco]

Could you please enable "fingerprint wake and unlock" in the overlay file when compiling. This would prevent accidentally unlocking the phone when touching the fingerprint sensor.

According to this reddit post, this has already been implemented in LineageOS and just needs to be enabled for each specific device (check the original thread, not the embed, first comment explains it): https://www.reddit.com/r/LineageOS/comments/qxcfyc

I just did this https://review.lineageos.org/c/LineageOS/android_device_xiaomi_alioth/+/333557
Not sure if it is correct and if it will get merged.

 

[Boracho]

I just did this https://review.lineageos.org/c/LineageOS/android_device_xiaomi_alioth/+/333557
Not sure if it is correct and if it will get merged.

Great!

BTW: Some guys are trying to port gravity box to Android 12. With this module you can also override the setting: https://forum.xda-developers.com/t/unofficial-gravitybox-s-version.4456047/
But its very experimental right now, I won't install this on my phone for now. But maybe some of you want to give it a shot.

 

[confluced]

In the installation wiki,I need to flash the copy-partition zip,but in the wiki for update,it seems I needn't flash it as this step doesn't appear at all ,that's confusing,should I flash it when update?