• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

Development [ROM][OFFICIAL][alioth/aliothin][11] LineageOS 18.1

Search This thread

vander13

Senior Member
Aug 28, 2010
74
7
Open Magisk > click check safetynet button
That easy? Oh no, I don't have this button!

Please describe it for someone that don't know magisk. I open magisk I see version infos and a menu on the bottom. There I can choose home/root progs/logs/extensions. On home screen settings menu is also no button.

Does SAR mean safety net? It says 'yes' but no button.
 

Ran94

Member
May 20, 2017
10
0
OnePlus 3
That easy? Oh no, I don't have this button!

Please describe it for someone that don't know magisk. I open magisk I see version infos and a menu on the bottom. There I can choose home/root progs/logs/extensions. On home screen settings menu is also no button.

Does SAR mean safety net? It says 'yes' but no button.
Are you using magisk canary? I think canary won't have this option. But if you're using stable build, your home screen should be similar to this (version numbers may vary but there should be check safetynet button as shown below)
Magisk-v21.jpg
 

frama001178

New member
Nov 27, 2021
1
3
Hi,
Speaker sounded terrible with this ROM compared to stock MIUI: noisy/low quality esp. on high volume w/ the top speaker.
  • Headphone is not affected.
  • Before I flashed this ROM I'd been on stock 12.5.4.0 and not 12.5.3.0 as instructed here (didn't know because I only checked lineageos wiki).
  • I tried disabling AudioFX, didn't help.
  • The speaker sounded as intended with latest xiaomi.eu ROM.
 

ale82to

Senior Member
Apr 7, 2014
370
78
double tap to wake is very, very unreliable for me (it almost always requires 3/4 taps to actually wake the phone).
Does anyone have enabled it WITHOUT AOD and /or ambient display on?
it's my only complaint about this phone and I'm probably selling it because of this.
I also tried dot os 5.2 and exactly same problem.
if I enable aod + show notification (screen always on) double tap to wake is super reliable but battery drain is insane about 7-8% per hour.
thanks for anyone giving feedback /advice on this small issue.
 

blasev

Senior Member
Apr 30, 2006
1,190
21
double tap to wake is very, very unreliable for me (it almost always requires 3/4 taps to actually wake the phone).
Does anyone have enabled it WITHOUT AOD and /or ambient display on?
it's my only complaint about this phone and I'm probably selling it because of this.
I also tried dot os 5.2 and exactly same problem.
if I enable aod + show notification (screen always on) double tap to wake is super reliable but battery drain is insane about 7-8% per hour.
thanks for anyone giving feedback /advice on this small issue.
I never had aod and notification on, but always got D2W working consistently using miui.eu and AICP with their default kernel
 
Aug 26, 2021
15
3
Xiaomi Poco F3
Any updates on the modem crash bug causing random reboots while using LTE? After many months it's still happening. Only fix was to force to 3G which is painfully slow.

When will this be fixed? It's been getting really frustrating.
 
  • Like
Reactions: marcomartinelli

ale82to

Senior Member
Apr 7, 2014
370
78
Any updates on the modem crash bug causing random reboots while using LTE? After many months it's still happening. Only fix was to force to 3G which is painfully slow.

When will this be fixed? It's been getting really frustrating.
actually it's very easy to fix just flash drunk kernel! it even detect if you have Magisk installed and automatically patch it
 

bcnpmt

New member
Apr 29, 2019
2
0
Sorry for the audacity ..
Is there a forecast of Lineageos Android 12 for Poco F3 ?.
Thanks
 

BTW lover

Senior Member
Apr 27, 2010
82
13
Hit there everyone. I've just flashed my brand new f3 with lineage after waiting a week for the bootloader unlook. Installation went fine but after a day of use I've noticed some very strange battery behaviour. If I plug the phone in, the charge does not seem to increase and the phone battery is eaten very quickly. After the phone turned itself off, seemingly because it was out of juice, I turned it back on after charging for a few minutes and all of a sudden it was back to 89%.

Seems like the battery reading is a bit off. Any idea how I can fix this?
 

damonke

Member
Sep 30, 2021
12
3
Xiaomi Poco F3
Hit there everyone. I've just flashed my brand new f3 with lineage after waiting a week for the bootloader unlook. Installation went fine but after a day of use I've noticed some very strange battery behaviour. If I plug the phone in, the charge does not seem to increase and the phone battery is eaten very quickly. After the phone turned itself off, seemingly because it was out of juice, I turned it back on after charging for a few minutes and all of a sudden it was back to 89%.

Seems like the battery reading is a bit off. Any idea how I can fix this?
wait it out, the battery system is still a bit confused. preferably give it one or two full charges where you leave it charging for 1 hour after it reaches 100%
 

BTW lover

Senior Member
Apr 27, 2010
82
13
Jeah I hope it's just that. Either that or I found the secret to unlimited energy:

Phone was at 10% just now so I turned it off to see what the charging indicator says when I plug it in turned off (you know that inidicator you get when plugging in your phone turned off) and this told me it was already almost full. Turned it back on and BOOM, back to 99%!?

That fast charging technology sure is pretty fast ☺️
 
Nov 18, 2021
12
7
Xiaomi Poco F3
Any updates on the modem crash bug causing random reboots while using LTE? After many months it's still happening. Only fix was to force to 3G which is painfully slow.

When will this be fixed? It's been getting really frustrating.
Thanks for the fix by the way!
 
  • Like
Reactions: thelegendaryharold

Leejhay1714

Senior Member
Apr 2, 2015
328
56
Hi good day everyone, please help I can't pass safetynet ctsprofile, and the playstore is not certified
 

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    Thanks for the support of LOS on the Poco F3 :giggle:(y)
    The default minimum volume settings are a bit too high as the Poco F3 has some powerful speakers.
    I suggest lowering the volume values in audio_policy_volumes.xml and default_volume_tables.xml.

    These values worked fine for me...

    audio_policy_volumes.xml:

    <volume stream="AUDIO_STREAM_VOICE_CALL" deviceCategory="DEVICE_CATEGORY_SPEAKER">
    <point>0,-3600</point>
    <point>33,-2400</point>
    <point>66,-1200</point>
    <point>100,0</point>
    </volume>

    <volume stream="AUDIO_STREAM_VOICE_CALL" deviceCategory="DEVICE_CATEGORY_EARPIECE">
    <point>0,-3600</point>
    <point>33,-2400</point>
    <point>66,-1200</point>
    <point>100,0</point>
    </volume>

    <volume stream="AUDIO_STREAM_RING" deviceCategory="DEVICE_CATEGORY_SPEAKER">
    <point>1,-4455</point>
    <point>33,-3015</point>
    <point>66,-1530</point>
    <point>100,0</point>
    </volume>

    <volume stream="AUDIO_STREAM_ALARM" deviceCategory="DEVICE_CATEGORY_SPEAKER">
    <point>1,-4455</point>
    <point>33,-3015</point>
    <point>66,-1530</point>
    <point>100,0</point>
    </volume>

    <volume stream="AUDIO_STREAM_NOTIFICATION" deviceCategory="DEVICE_CATEGORY_SPEAKER">
    <point>1,-4455</point>
    <point>33,-3015</point>
    <point>66,-1530</point>
    <point>100,0</point>
    </volume>

    default_volume_tables.xml:

    <reference name="DEFAULT_SYSTEM_VOLUME_CURVE">
    <!-- Default System reference Volume Curve -->
    <point>1,-3120</point>
    <point>33,-2340</point>
    <point>66,-1560</point>
    <point>100,-780</point>
    </reference>
    2
    According to the installation instructions on the wiki, the firmware should be the latest version. However when looking at recent changes I can see this pull request mentioning blobs from V12.5.4.0.RKHMIXM. However the latest stable firmware version for global devices is V12.5.5.0.RKHMIXM and for European ones it's V12.5.7.0.RKHEUXM. Given that I'm on the latest LineageOS nightly build, I have an European device and I'm on firmware V12.5.6.0.RKHEUXM, should I update it to the latest version? Or should I install the global firmware, and in this case which version should I pick?
    Currently, there is no need to update. Once the blobs are updated to later version, then yes, you should. If I were you, I'd update the firmware only without going through the struggle of flashing full MIUI image.
    2
    hi,
    I'm wondering if you have been able to sort this out
    thanks in advance.
    Hi!

    Yes, I was actually able to install this LineageOS rom without any problem following the instructions given in the official website to install this rom. Finally, what I did is to try it with the MIUI13 beta rom that I had at that time and the firmware that was in that ROM, and everything worked out well in the end!

    Hopefully, it should be the same for you.
    1
    When that happens should I install the global or the European firmware? My device came with the European ROM.
    Always go with the one that your device shipped with.
    1
    Hi. Thank you for your work.
    I recently bought a Poco F3, unlocked the bootloader and installed the build lineage-18.1-20220115-nightly-alioth-signed.zip.
    Everything works fine but I have the same problem of pixelated corners described here.
    I don't know if it's just me, maybe I have screwed up something during the installation.
  • 72
    2okPze5.png



    LineageOS is a free, community-built, aftermarket firmware distribution of Android 11, 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 restores 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 our Gerrit Code Review. You can also view the Changelog for a full list of changes & features.

    What's not working :
    • You tell me ;)
    Instructions :
    Check #2 post before installation

    Downloads
    :

    Reporting Bugs :
    • 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.)
    Kernel Source :

    Remember to provide as much info as possible. The more info you provide, the more likely it that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.

    Code:
    What is your--
    LineageOS version:
    LineageOS Download URL:
    Gapps version:
    
    Did you--
    wipe:
    restore with titanium backup:
    reboot after having the issue:
    
    Are you using--
    a task killer:
    a non-stock kernel:
    other modifications:
    
    Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:

    Credits :

    althafvly

    SebaUbuntu

    12
    Important notes:

    • * Required * firmware version must be based on MIUI 12.5.3.0 builds.
    • 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.
    11
    Note:
    Flashing LineageOS through TWRP is NOT SUPPORTED and NOT ADVISED, do with your own risk. 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.
    10
    THREAD LOCKED

    @Sahil_Sonar Please PM me when the build is available for download and I'll be happy to unlock this thread for you. Placeholder threads aren't permitted.

    Regards,
    shadowstep
    Forum Moderator

    EDIT: Thread re-opened.