Development [ROM][R][OFFICIAL] LineageOS 18.1 for POCO X3 Pro [vayu]

Search This thread

HastaPasta

Member
Oct 11, 2021
37
8
Hi. After a recent telegram update the microphone went extremely low almost inaudible.

I played about with James DSP and it worked again.

Telegram got updated again today and same problem except can't fix it this time.

Any ideas or where to ask / look?

Many thanks
 

Faruk88

Senior Member
Mar 20, 2010
155
15
My banking app tries to read the device's IMEI, subscriber ID, and ICCID by attempting to open /sys/devices/platform/soc/2c00000.qcom,kgsl-3d0 but that triggers an SELinux rule, which causes the app to fail and shut down:

Code:
12-07 18:13:40.393  2153  2153 W RenderThread: type=1400 audit(0.0:79512): avc: denied { search } for name="2c00000.qcom,kgsl-3d0" dev="sysfs" ino=41048 scontext=u:r:untrusted_app_27:s0:c512,c768 tcontext=u:object_r:sysfs_msm_subsys:s0 tclass=dir permissive=0 app=com.scotiabank.mobile
12-07 18:13:40.439  1374  1498 I ActivityTaskManager: Displayed com.scotiabank.mobile/.MobileBanking: +451ms
12-07 18:13:40.985  2448  2731 W TelephonyPermissions: reportAccessDeniedToReadIdentifiers:com.scotiabank.mobile:getDeviceId:-1
12-07 18:13:40.988  2448  2731 W TelephonyPermissions: reportAccessDeniedToReadIdentifiers:com.scotiabank.mobile:getSubscriberId:1
12-07 18:13:40.993  2448  2731 W TelephonyPermissions: reportAccessDeniedToReadIdentifiers:com.scotiabank.mobile:getIccSerialNumber:1

I don't have this problem on my old LeEco Le Pro3 also running LineageOS 18.1. So I assume there is a difference in the SELinux policy? Would it be possible to fix this?
 

gringo80

Account currently disabled
Jun 8, 2018
743
652
My banking app tries to read the device's IMEI, subscriber ID, and ICCID by attempting to open /sys/devices/platform/soc/2c00000.qcom,kgsl-3d0 but that triggers an SELinux rule, which causes the app to fail and shut down:

Code:
12-07 18:13:40.393  2153  2153 W RenderThread: type=1400 audit(0.0:79512): avc: denied { search } for name="2c00000.qcom,kgsl-3d0" dev="sysfs" ino=41048 scontext=u:r:untrusted_app_27:s0:c512,c768 tcontext=u:object_r:sysfs_msm_subsys:s0 tclass=dir permissive=0 app=com.scotiabank.mobile
12-07 18:13:40.439  1374  1498 I ActivityTaskManager: Displayed com.scotiabank.mobile/.MobileBanking: +451ms
12-07 18:13:40.985  2448  2731 W TelephonyPermissions: reportAccessDeniedToReadIdentifiers:com.scotiabank.mobile:getDeviceId:-1
12-07 18:13:40.988  2448  2731 W TelephonyPermissions: reportAccessDeniedToReadIdentifiers:com.scotiabank.mobile:getSubscriberId:1
12-07 18:13:40.993  2448  2731 W TelephonyPermissions: reportAccessDeniedToReadIdentifiers:com.scotiabank.mobile:getIccSerialNumber:1

I don't have this problem on my old LeEco Le Pro3 also running LineageOS 18.1. So I assume there is a difference in the SELinux policy? Would it be possible to fix this?
What is your SafetyNet status ???
If you don't pass SN, no banking app will work !
 

Faruk88

Senior Member
Mar 20, 2010
155
15
What is your SafetyNet status ???
If you don't pass SN, no banking app will work !

It's not about SafetyNet - the app (Scotiabank) works fine on my Le Pro3, which is also just running a vanilla, official build of LineageOS 18.1 (no Magisk or anything like that). The issue is the SELinux policy that is causing the error in the logcat messages that I posted. As far as I can tell, the required fix is to update the policy to allow the app permission to read the sysfs entry.
 
Last edited:

Faruk88

Senior Member
Mar 20, 2010
155
15
My banking app tries to read the device's IMEI, subscriber ID, and ICCID by attempting to open /sys/devices/platform/soc/2c00000.qcom,kgsl-3d0 but that triggers an SELinux rule, which causes the app to fail and shut down:

Code:
12-07 18:13:40.393  2153  2153 W RenderThread: type=1400 audit(0.0:79512): avc: denied { search } for name="2c00000.qcom,kgsl-3d0" dev="sysfs" ino=41048 scontext=u:r:untrusted_app_27:s0:c512,c768 tcontext=u:object_r:sysfs_msm_subsys:s0 tclass=dir permissive=0 app=com.scotiabank.mobile
12-07 18:13:40.439  1374  1498 I ActivityTaskManager: Displayed com.scotiabank.mobile/.MobileBanking: +451ms
12-07 18:13:40.985  2448  2731 W TelephonyPermissions: reportAccessDeniedToReadIdentifiers:com.scotiabank.mobile:getDeviceId:-1
12-07 18:13:40.988  2448  2731 W TelephonyPermissions: reportAccessDeniedToReadIdentifiers:com.scotiabank.mobile:getSubscriberId:1
12-07 18:13:40.993  2448  2731 W TelephonyPermissions: reportAccessDeniedToReadIdentifiers:com.scotiabank.mobile:getIccSerialNumber:1

I don't have this problem on my old LeEco Le Pro3 also running LineageOS 18.1. So I assume there is a difference in the SELinux policy? Would it be possible to fix this?

Update: I looked at the SELinux policies from my LeEco Le Pro3 and from my Poco X3 Pro.

When I grep for sysfs_msm_subsys, nothing comes up in the Le Pro3 policies. But in the Poco X3 Pro's policies, there are a few occurrences in /vendor/etc/selinux/vendor_sepolicy.cil.
 
Last edited:

gringo80

Account currently disabled
Jun 8, 2018
743
652
It's not about SafetyNet - the app (Scotiabank) works fine on my Le Pro3, which is also just running a vanilla, official build of LineageOS 18.1 (no Magisk or anything like that). The issue is the SELinux policy that is causing the error in the logcat messages that I posted. As far as I can tell, the required fix is to update the policy to allow the app permission to read the sysfs entry.

PS. If you have a few phones you may be interested in testing the app yourself also (you don't need to log in or anything - on first launch it gives a warning about running on an unlocked device, but after that it works normally): https://play.google.com/store/apps/details?id=com.scotiabank.banking&hl=en_CA&gl=US
ok good luck
bye
 

Faruk88

Senior Member
Mar 20, 2010
155
15
Thanks, I figured out the problem.

Turns out when I was transferring my settings and reinstalling my apps on the new phone, for some reason Play Store decided to install an old version of the banking app from 2019 (I have a theory about this - looks like the app name changed from com.scotiabank.banking to com.scotiabank.mobile), and Play Store wasn't showing that there was a newer version available.

So I uninstalled the app, reinstalled it again and this time it installed the latest version. The banking app works now. My guess is that the old version of the app was just incompatible with this recent set of SELinux policies.
 
Last edited:
Apr 9, 2012
9
0
Bogor
Hi, installed this ROM last night didn't install magisk and stuff but my banking app won't work cause it detect the phone as rooted, maybe I can get a hand on this?
 

Zeokat

Member
Jul 29, 2021
16
6
Hello, i have an old CrDroid version runing on my phone. I have some questions:

1) How can i check which firmware version is installed on my phone?
2) Should i update the firmare of the phone to latest version first?
3) Any guide that i can follow to update my phone?

I'm totally lost. Thanks.
 

Eric_Lev

Senior Member
Jan 27, 2019
1,277
2,429
Angers
androidfilehost.com
Hello, i have an old CrDroid version runing on my phone. I have some questions:

1) How can i check which firmware version is installed on my phone?
2) Should i update the firmare of the phone to latest version first?
3) Any guide that i can follow to update my phone?

I'm totally lost. Thanks.
Install LineageOS on vayu:

Warning: Before following these instructions please ensure that the device is on the latest Android 11 firmware.

Latest firmwares:

Possible GCam apps:
 

d_g_m_2000

Senior Member
Jul 6, 2015
439
105
Samsung Galaxy S9
Xiaomi Mi A2
Hello, i have an old CrDroid version runing on my phone. I have some questions:

1) How can i check which firmware version is installed on my phone?
2) Should i update the firmare of the phone to latest version first?
3) Any guide that i can follow to update my phone?

I'm totally lost. Thanks.
from what i konw:
1) firmware version is the one you had with stock rom before flashing custom rom. if you don't remember which one you can try "fastboot getvar all" command in fastboot mode.
2) some devs recommend that, indeed, you should update your phone to the latest version.. read op or custom rom's web site to more info.
3) the official miui update guide is good to go < https://c.mi.com/es/miuidownload/detail?guide=2 > double check your device version before proceed. also there are many tutorials in youtube that you can follow to update or restore to stock rom
 
  • Like
Reactions: Zeokat

Zeokat

Member
Jul 29, 2021
16
6
from what i konw:
1) firmware version is the one you had with stock rom before flashing custom rom. if you don't remember which one you can try "fastboot getvar all" command in fastboot mode.
2) some devs recommend that, indeed, you should update your phone to the latest version.. read op or custom rom's web site to more info.
3) the official miui update guide is good to go < https://c.mi.com/es/miuidownload/detail?guide=2 > double check your device version before proceed. also there are many tutorials in youtube that you can follow to update or restore to stock rom
But i don't want to restore MIUI, i want to update to LineageOS.
Maybe are you saying that i have to install MIUI before install LineageOS?
 

TheMrTesla

Member
Aug 22, 2021
15
5
Xiaomi Poco X3 Pro
yes, in order to have your device updated with the last firmware, you'll need to flash the lastest stock rom and then flash lineage os.
well.. that's is how i do it.
You don't have to, if you have TWRP or adb you can flash the firmware-only zip and update your firmware with that.

As for checking firmware version: check your baseband version and compare to this.
 

Attachments

  • New Text Document(1).txt
    576 bytes · Views: 44

Kowalskid

New member
Dec 15, 2021
2
0
Hi there,
I need some help. I installed lineageos 18.1 on my poco x3 pro and I noticed that the phone is not vibrating. It did before and still does as a conformation when shut down. But no message or call or feedback while typing is working. I switched on every "vibrate" I could find and switched off every energy saving and do not disturb. Does anybody got a hint what I can do? Thank you very much
 

HastaPasta

Member
Oct 11, 2021
37
8
Hi there,
I need some help. I installed lineageos 18.1 on my poco x3 pro and I noticed that the phone is not vibrating. It did before and still does as a conformation when shut down. But no message or call or feedback while typing is working. I switched on every "vibrate" I could find and switched off every energy saving and do not disturb. Does anybody got a hint what I can do? Thank you very much
Hi. Push volume up and an oblong volume scale shows on the screen with a small square with an icon in it directly above. Tap the square to switch to vibrate
 

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    Then use my TWRP version as it allows flashing MOD "properly" and manage everything in /data. It has been already mentionned Up. I did that 1 billion times with no issue.

    OrangeFox is may be bugged now ... who knows, i don't use it !

    If you feel that flashing is too hard for you, take your time to learn from google step by step everything you need before !

    Edit :
    the errors you got are because you didn't read the features.txt
    You must reboot to TWRP again after flashing your nightly build, then you can flash the whole MOD ... it's mentionned.

    Next time read the instructions !

    (y)
    Well I'm flashing devices a long time now, clearly, that doesn't make me a professional.

    I appreciate the solution you propose but its something that I couldn't get to work and I'm not prepared to spend more time on. Just to add, I did actually read your instructions in the text file, this is how I knew there were 3 folders to be deleted after flashing your mod. As Tomo123 noted, I'm sure somebody will find your solution helpful. Thanks for sharing.
    So.. latest build did the job well. Why not try Fork Lineage 19 ? Please ..
    I just noticed this is sebaubuntu telegram
    2
    Exactly! For me, that is a serious issue, as anyone standing near me can hear everything being spoken on the other side. And call volume is quite loud, even on lowest setting.

    How come ArrowOS 11 got that fixed, but not LineageOS? It's been reported quite a while back...
    I will repost the full audio fix again here, (posted months ago ... i don't remember wich page to link !)

    Here are the features :

    - fix "Earpiece" volume
    - fix voice over handset (Telegram, Duo & Signal)
    - Audio recording : use HQ mic (no more muffled sound / loud & crystal clear)
    - Video recording : use high audio bitrate
    - Speakers : use true 24-bit stereo playback
    - Bluetooth : aptX™ HD [up to 48KHz/24-bit]
    - SoundFX : use them corretcly with AudioFX app (effects were inverted when switched ON !)
    - audio daemons : lower CPU usage in background

    I stronlgy recommend to use my TWRP version wich allows flashing MODS "corretcly" ... LOS recovery is not recommended !

    If you are interested to my full LineageOS 18.1 MOD for [vayu/bhima], go here ... but read the features.txt before !
    1
    Thx. So not format Data at the end ? You are on Official 18.1 ? Or Fork Los 19 ?

    Can you post your batterystats later on ? I'm hesitating between Los and Crdroid.

    You should format Data after flashing ROM before booting for first time.
    1
    Had the devil up my ass for the last few hours, so I decided to flash ArrowOS 11 and see if the same problem exists in there.

    Nope, ArrowOS has no issues with high call volume, even on the lowest setting. In fact, on the lowest setting you can barely hear the call.

    I am staying on ArrowOS until this is solved. Sad thing is that I really, REALLY wanted to use LineageOS, but having NO PRIVACY during calls is no-go for me...

    Really hoping dev @SebaUbuntu looks into the issue.
    1
    Tried this mod from gringo80 on latest lineageos 18.1 build and latest orange fox recovery. It did install but not without errors.. Also I could not delete the folders advised due to a similar error. This then caused my phone to bootloop. Well, phone loaded in and worked for about 15 seconds and then it froze up.

    I reflashed latest lineage nightly and it seems to have fixed everything. Probably won't try this mod again! I should mention too, I am using no gravity kernel 2.2.1 so maybe that caused issues with this mod? Not sure.

    Was thinking to try arrowos 12.1 or crdroid 12.1 to resolve small sound bug but I don't think its worth the PITA of backing up everything and starting fresh. Imagine lineageos 19.1 will appear soon
  • 49
    2okPze5.png


    LineageOS is a free, community built, aftermarket firmware distribution of Android 11.0 (R), which is designed to increase performance and reliability over stock Android for your device.

    LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

    All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.

    Downloads
    Here

    Flashing instructions
    Here

    Sources:
    LineageOS

    Happy modding!
    11
    Thanks for finally releasing LineageOS, but you devs are 3 months too late... ArrowOS has inadvertently stolen my heart in your absence, lol.
    Someone asked?
    9
    New update out
    8
    Thanks for finally releasing LineageOS, but you devs are 3 months too late... ArrowOS has inadvertently stolen my heart in your absence, lol.
    5
    The next build should be official (thanks to SebaUbuntu) - https://www.lineageoslog.com/18.1/vayu