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

Search This thread

karlmorgan92

Senior Member
Dec 9, 2013
137
37
Sorry but isnt clear.
I've to write this lines from Android Terminal or from PowerShell?

Thanks

$ adb root $ adb shell 'sqlite3 /data/data/com.google.android.gsf/databases/gservices.db \ "select * from main where name = \"android_id\";"'
Just install an app called Device ID and copy the Google Framework id, it's easier.
 

CardenasXDA

New member
May 15, 2022
2
0
82131659-64E6-4D05-B937-72AC62E78CB6.png


Are these safe to ignore?
 

althafvly

Recognized Developer / Recognized Contributor
May 28, 2014
1,651
3,343
Malappuram
Moto G 2015
Google Pixel XL
The ROM isn't PLay Certified, so you need magisk to use GPay.
Not a big deal, but there's a way to do it without Magisk?
By default lineageos don't pass safetynet, why?- its explained here https://lineageos.org/Safetynet

You can pass safetynet by an unofficial way, using ih8sn
This might help to pass SafetyNet without Magisk/Root

1- Extract attached ih8sn_lineage.zip somewhere.
2- Connect phone with USB debugging mode and rooted debugging enabled in developer options.
3- Then run push script (.sh/.ps1/.bat) or manually enter whats in it.
4- Reboot

Note:
- Adding 60-ih8sn.sh file will keep the spoofing stay in ota updates, use only if needed

Source: https://github.com/althafvly/ih8sn/commits/alioth
 

Attachments

  • ih8sn_lineage.zip
    2.2 MB · Views: 104

avguser23

Senior Member
May 31, 2019
65
16
Does anyone get the error "Intent Verification Filter keeps stopping" at each boot? I have stock LOS no gapps no microg.
 

maniacbb

Member
Mar 6, 2018
22
3
Is it possible to manually select networks in this version and also does the "ok google" command work?
 

heaven-dub

Senior Member
Jan 30, 2011
51
41
Xiaomi Poco F3
By default lineageos don't pass safetynet, why?- its explained here https://lineageos.org/Safetynet

You can pass safetynet by an unofficial way, using ih8sn
This might help to pass SafetyNet without Magisk/Root

1- Extract attached ih8sn_lineage.zip somewhere.
2- Connect phone with USB debugging mode and rooted debugging enabled in developer options.
3- Then run push script (.sh/.ps1/.bat) or manually enter whats in it.
4- Reboot

Note:
- Adding 60-ih8sn.sh file will keep the spoofing stay in ota updates, use only if needed

Source: https://github.com/althafvly/ih8sn/commits/alioth
Thank you for the script. I have used the provided .bat file, it works.

I have only one question: is it normal that after every reboot this setting turns on again?

Screenshot_20220515-234421_Settings.png


It's not a big deal, I'm just asking to know if it's the intended behavior. Also I have removed the line to push 60.ih8sn.sh, not sure if that's the reason.
 

CHGICEMAN

Senior Member
@ althafvly

Thank you and your colleagues for the work you have done to program this great software.

One small thing I've noticed so far. In previous LOS versions you could customize the status icons. Apparently not with this version or I'm just too stupid to find it. could you give me an answer on that?
 

R!ffRaff

Senior Member
Oct 21, 2019
281
79
@ althafvly

for me, everything runs as it should, but works with an extension because I do not use gapps.
This magisk extension installs the Google Swipe/Swipe function into the linegae. It works here on all other device LOS18.1 & 19 only not with alioth.

can you help me where the error is or what needs to be adjusted? Is there a special feature of the alioth?

please help me
 
Last edited:

CHGICEMAN

Senior Member
@althafvly
I think I found a bug with Android Auto.
I have Android Auto set, which starts Android Auto even if the smartphone is locked, see image.
But since the upgrade from 18.1 to LOS 19.1 it doesn't work. Android Auto only works after unlocking my phone.

Maybe someone else who also uses Android Auto can confirm this.
 

Attachments

  • Screenshot_20220516-173459_Android Auto.png
    Screenshot_20220516-173459_Android Auto.png
    196.3 KB · Views: 56

althafvly

Recognized Developer / Recognized Contributor
May 28, 2014
1,651
3,343
Malappuram
Moto G 2015
Google Pixel XL
@althafvly
I think I found a bug with Android Auto.
I have Android Auto set, which starts Android Auto even if the smartphone is locked, see image.
But since the upgrade from 18.1 to LOS 19.1 it doesn't work. Android Auto only works after unlocking my phone.

Maybe someone else who also uses Android Auto can confirm this.
If it's mindthegapps, report it here https://gitlab.com/MindTheGapps/vendor_gapps/-/issues
@ althafvly

for me, everything runs as it should, but works with an extension because I do not use gapps.
This magisk extension installs the Google Swipe/Swipe function into the linegae. It works here on all other device LOS18.1 & 19 only not with alioth.

can you help me where the error is or what needs to be adjusted? Is there a special feature of the alioth?

please help me
That's way to old to work with alioth
 
  • Like
Reactions: duttyend

E jP

New member
May 16, 2022
1
0
Is there a way to disable system apps from showing the green privacy indicator or stop it for accessing location?
Screenshot_20220516-230729_Permission controller.png
 

AzureusPT

Senior Member
Feb 27, 2008
494
56
I've just flashed LOS 19 on my phone and it works really well, but I'm unable to install Magisk successfully.

I've tried patching the boot images either directly (getting the image from the device via dd) or using the one inside the lineage-*.zip payload file. The patch appears to complete successfully as well as the flash of the boot image, but upon restart Magisk will display Zygisk as No and some entries in the settings are grayed out (I suppose for the absence of Zygisk).

I've also tried renaming the .apk to .zip and flasing it via sideload. The only error I got was the one regarding its signature, but upon restart its the same, Zygisk appears as No.

Also I flashed vbmeta with the flags requested by the installation process.

Is this the actual behavior over LOS 19.1 or do I need to perform any other step in order to be able to have Magisk working?
 

AzureusPT

Senior Member
Feb 27, 2008
494
56
@althafvly
I think I found a bug with Android Auto.
I have Android Auto set, which starts Android Auto even if the smartphone is locked, see image.
But since the upgrade from 18.1 to LOS 19.1 it doesn't work. Android Auto only works after unlocking my phone.

Maybe someone else who also uses Android Auto can confirm this.
I can confirm this on a fresh LOS 19.1 install. Once Android Auto is setup in both car and device, the next time you plug the phone in it works depending on the following:
  • If the phone screen is locked, the screen turns on, you can see a notification for Android Auto trying to start, but it ends in an error. In my case the phone displays a notification from Android Auto telling that it wasn't possible to start AA and to check the cable.
  • If the phone screen is unlocked and you plug in, AA starts normally.
In my test the cable was obviously the same, so there might be some glitch or issue there.
 
  • Like
Reactions: CHGICEMAN

Top Liked Posts

  • 1
    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?
  • 4
    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.
    3
    In last release (today's one), security patch level is still 2022-05-05 despite in changelog it's reported June security update.
    Is someone experiencing the same?
    Hello,
    "332260: Jun 2022 Security update & Feature drop" commit, is related to android_vendor_lineage.
    POCO F3 vendor Security update level is still 2022-04-01 for me.
    332260 commit seem to be only related to the Google devices. And as there is no vars/alioth in this commit, there is no vendor security patch level update flag for alioth.
    3
    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
    2
    In last release (today's one), security patch level is still 2022-05-05 despite in changelog it's reported June security update.
    Is someone experiencing the same?
    2
    Just flashed the version from "2022-05-28".

    Taking pictures with the provided android cam or gcam look somewhat blurry/photoshopped/filtered.
    Anyone else having this?
    • Android camera2: version 2.0.002
    • Google camera: version 4.4.020.163412804
    Using the latest Gcam build seems to solve the issue:

    Tested it with pictures of hairy legs. Before the body hair looked like some weird blurry paste. Now the body hair looks sharp. I guess that's good :p
  • 29
    lineageos-png.5317459
    LineageOS is a free, community built, aftermarket firmware distribution of Android 12L (Sv2), 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. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

    Base source code is available in the LineageOS Github repo. And if you would like to contribute to the project, please visit our Gerrit Code Review.

    GPL compliance:

    yG18r6g.png


    Working:
    • Camera (and flashlight)
    • WiFi
    • Bluetooth
    • Telephony (Calls)
    • Audio (Record and Playback)
    • Video Playback
    • Sensors
    • GPS
    • VoLTE/VoWifi
    Bugs:
    • Nothing (?)

    Downloads:
    Wiki:
    Installation :
    Note:
    • Required firmware version must be based on MIUI 13.x.x builds (Based on Android 12).
      • V13.0.5.0.SKHCNXM 12.0 China
      • V13.0.4.0.SKHINXM 12.0 India
      • V13.0.3.0.SKHMIXM 12.0 Global
      • Others flash region specific firmware MIUI 13.x.x.x 12.0 (eg: Europe, Indonesia, Russia, etc..)
    • GApps can only be flashed on clean installs.
    • Formatting data (all user data is wiped, including internal storage) is a must if MIUI was previously installed and device was encrypted.
    • Flashing LineageOS through TWRP is NOT SUPPORTED and NOT ADVISED. **
    • No custom kernels are supported in this thread. Only stock kernel and official builds will be supported.
    ** Please use LineageOS Recovery instead. Right now, Lineage Recovery is really only intended to be used on devices with Seamless Updates (aka A/B partitions) and, in that role, it is only intended to be embedded within the OS's normal Boot image. While flashing TWRP, it replaces boot image's ramdisk (possible security risks, coz it runs SeLinux permissive on recovery). That's why it's not recommend to use with A/B devices.

    Bug reports: https://wiki.lineageos.org/how-to/bugreport#reporting-a-bug
    • DO NOT report bugs if you're running a custom kernel or you installed Xposed.
    • Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.).

    Credits & collaborations:
    All LineageOS team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!

    Credits :

    @SebaUbuntu

    @Sahil_Sonar


    DONATIONS : Paypal
    15
    LineageOS 19.1 official build is out

    Make sure follow steps before upgrading to lineage-19.1

    - Follow this fresh install https://wiki.lineageos.org/devices/alioth/install
    - Follow this for upgrade https://wiki.lineageos.org/devices/alioth/upgrade

    - Install Android 12 Gapps after installing rom (if you use)
    - Update firmware to required firmware version MIUI 13.x.x builds (Based on Android 12).
    V13.0.5.0.SKHCNXM 12.0 China
    V13.0.4.0.SKHEUXM 12.0 Europe
    V13.0.4.0.SKHINXM 12.0 India
    V13.0.2.0.SKHMIXM 12.0 Global
    7
    Updated build is UP (Check OP for link)

    - Based on android-12.1.0_r2
    - Some features are up (like expandable volume panel)
    - Fixed recovery assert issue
    - https://download.lineageos.org/alioth/changes/
    6
    The ROM isn't PLay Certified, so you need magisk to use GPay.
    Not a big deal, but there's a way to do it without Magisk?
    By default lineageos don't pass safetynet, why?- its explained here https://lineageos.org/Safetynet

    You can pass safetynet by an unofficial way, using ih8sn
    This might help to pass SafetyNet without Magisk/Root

    1- Extract attached ih8sn_lineage.zip somewhere.
    2- Connect phone with USB debugging mode and rooted debugging enabled in developer options.
    3- Then run push script (.sh/.ps1/.bat) or manually enter whats in it.
    4- Reboot

    Note:
    - Adding 60-ih8sn.sh file will keep the spoofing stay in ota updates, use only if needed

    Source: https://github.com/althafvly/ih8sn/commits/alioth