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

Search This thread

GtrCraft

Recognized Developer
Jun 3, 2013
6,728
17,653
Moto G5 Plus
Xiaomi Poco F1
that would be nice to know why prime core is limited to 2,75GHz ?
maybe @GtrCraft could answer this ?
Xiaomi broke thermals/max frequencies in a recent update.
This commit sets dynamic thermal on boot to fix frequencies being underclocked:
 
  • Like
Reactions: Alvaro Recoba
Aug 26, 2021
18
3
Xiaomi Poco F3
I'm having issues with google map's compass not being to calibrate properly. It keeps showing accuracy low and won't calibrate no matter what. As a result google maps can't tell my orientation no matter what. Other map apps work fine tho. (magic earth, organic maps) I'm running Lineageos4Microg 18.1 on Poco F3. Thanks in advance!
 

polfrank

Senior Member
Jul 5, 2012
718
334
I want to thank all of the laos authors, its really great work!

I used laos for several months in Europe and never had any problems. However, I recently moved to mexico and have lots of problems with the network stability, especially inside buildings. It connects to to the network, but losses the connection after a few seconds again. This is going on all the time and drains the battery. My friends with the same carrier dont have those problems, so I think its caused by the firmware. I use the 12.5.4 global one and was very happy with it in europe.

Someone can suggest how I can solve this?
Hey. I would guess this has to do with the device hardware (which was built and optimised to work better in Europe, if you bought it there). In Mexico, there may be different LTE bands mainly used than in Europe. If your device modem is only capable of using some of those used in Mexico, it may have less connectivity options. This may lead to worse signal reception and higher power expenses to keep the connectivity as good as possible. Just a guess, though.

Do your friends use the same device model? And if it is so, is it the same region branding?
 

ale82to

Senior Member
Apr 7, 2014
400
82
Xiaomi broke thermals/max frequencies in a recent update.
This commit sets dynamic thermal on boot to fix frequencies being underclocked:
actually since I M very stubborn I finally found a solution to get full 3,2 ghz on snap 870 I simply replaced the two files marked in the screenshot and set correct permission ,everything was very smooth no bootloop or eccessive heat
 

Attachments

  • IMG-20220210-WA0000.jpg
    IMG-20220210-WA0000.jpg
    126.4 KB · Views: 103

PyrateVEVO

Member
Dec 20, 2021
6
1
I'm having issues with google map's compass not being to calibrate properly. It keeps showing accuracy low and won't calibrate no matter what. As a result google maps can't tell my orientation no matter what. Other map apps work fine tho. (magic earth, organic maps) I'm running Lineageos4Microg 18.1 on Poco F3. Thanks in advance!
since you don't have Google Services on your phone, GMaps may not work properly, I also get "poor accuracy" location on my other MicroG'd LineageOS but it's good enough for me
 

hhadi

Senior Member
Oct 7, 2009
84
10
Hello guys,
This ROM is simply awesome. The only issue I have is WiFi drops about every 10 mins. No matter if that's Wifi 5 or 6 or it is on 2.4GHz or 5GHz band. It just gets disconnected for 2-3 seconds and connects automatically again. Am I the only one experiencing this?
 

hhadi

Senior Member
Oct 7, 2009
84
10
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>
Thanks for the info on this. It works perfectly. Nevertheless, it is reset with each update. It seems that we would need a magisk module for this or we need to convince the maintainer to adjust the vendor files to better ones.
 

Exahope

Member
Dec 5, 2010
11
0
Hi. Great ROM. I was just wondering if there was any setting (or any plans to add one) which would allow for the fingerprint sensor to only detect when the power button has been pressed. This is because I will often find that when I reach for my phone out of my pocket, I will have already unlocked the phone, just by having my finger on the sensor, causing random apps to be opened from unwanted inputs.
Man been looking for a solution for this. I've been using this rom for months and very often where i keep my hand in my pocket then i find later that i've open differnt apps, browser, and one time pr0n page •~•
So plz devs, this feature and network indicator are very desired features.
 

Smultie

Senior Member
Apr 13, 2006
758
243
I'm currently waiting to unlock my bootloader.
MIUI is updated to the latest version (Global 12.5.7)

Anything I need to do, other than following the instructions?
TWRP still a no-go?
I see a lot of discussion on GApps. What's the best option?
 

Smultie

Senior Member
Apr 13, 2006
758
243
Is there another community discussing the Poco F3 with Lineage? This topic seems to be all questions, no answers... :(
 

Porpet

Member
Jan 10, 2013
14
7
Was anyone else thrown in a bootloop with 2022-02-19 los? I tried both OTA and recovery flash and got a bootloop.

I'm currently waiting to unlock my bootloader.
MIUI is updated to the latest version (Global 12.5.7)

Anything I need to do, other than following the instructions?
TWRP still a no-go?
I see a lot of discussion on GApps. What's the best option?
Be aware of the Important Note of post #2: * Required * firmware version must be based on MIUI 12.5.3.0 builds.

TWRP will be forever a no-go, as far as I know. Unless you want it for some specific reason, the LOS recovery is the supported option.

The best option for GApps is the one that works for you. Most people seem to be ok with Pico Open GApps, but I had to use MindTheGapps for some reason I don't remember. Is a bit of trial and error.
 

Smultie

Senior Member
Apr 13, 2006
758
243
Be aware of the Important Note of post #2: * Required * firmware version must be based on MIUI 12.5.3.0 builds.

TWRP will be forever a no-go, as far as I know. Unless you want it for some specific reason, the LOS recovery is the supported option.

The best option for GApps is the one that works for you. Most people seem to be ok with Pico Open GApps, but I had to use MindTheGapps for some reason I don't remember. Is a bit of trial and error.

MIUI 12.5.7 wasn't even available when post #2 was last edited I think.
https://wiki.lineageos.org/devices/alioth/install says nothing about 12.5.7 not working.

I'm almost more inclined to believe the Wiki over a post that's not being really updated.

Also: https://forum.xda-developers.com/t/...othin-11-lineageos-18-1.4313085/post-85798509
 
Last edited:

wingenieur

Member
Apr 14, 2019
26
8
Kassel
Was anyone else thrown in a bootloop with 2022-02-19 los? I tried both OTA and recovery flash and got a bootloop.


Be aware of the Important Note of post #2: * Required * firmware version must be based on MIUI 12.5.3.0 builds.

TWRP will be forever a no-go, as far as I know. Unless you want it for some specific reason, the LOS recovery is the supported option.

The best option for GApps is the one that works for you. Most people seem to be ok with Pico Open GApps, but I had to use MindTheGapps for some reason I don't remember. Is a bit of trial and error.
I can confirm the bootloop with latest update, came from 20220115, I think...
Will try to change the slot with fastboot in the evening to recover, waiting for fix or other solution...
 

Porpet

Member
Jan 10, 2013
14
7
MIUI 12.5.7 wasn't even available when post #2 was last edited I think.
https://wiki.lineageos.org/devices/alioth/install says nothing about 12.5.7 not working.

I'm almost more inclined to believe the Wiki over a post that's not being really updated.

Also: https://forum.xda-developers.com/t/...othin-11-lineageos-18-1.4313085/post-85798509
Thank you for this, maybe I'll try to update.

I can confirm the bootloop with latest update, came from 20220115, I think...
Will try to change the slot with fastboot in the evening to recover, waiting for fix or other solution...
That's what I did. Now I'm wondering if it's because my firmware is old.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 78
    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

    14
    Important notes:

    • * Required * firmware version must be based on MIUI 12.5.x 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.
    12
    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.