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

Development [ROM][UNOFFICIAL][11.0][sweet][unified] LineageOS 18.1

Search This thread

Sagesaurabh

New member
Dec 14, 2017
4
1
Redmi Note 10 Pro
Thanks man for the latest update, feels faster than before(maybe placebo). Among all roms, your lineage build is most stable so far. Only issue i had that, flashing over the june build results in bootloop. Otherwise great work, would love to have official build for the device. Would definitely donate to if this gets official status.
 

McFlyPartages

New member
Jul 27, 2021
4
1
Finistere
Hello, thank you for this provision of linegaos on the redmi note 10.

I just have a quick question. Why not be in the official lineage? What is blocking or what is the problem of going official?

thanks in advance
 
  • Like
Reactions: Sam7a2

appro77

Senior Member
May 8, 2011
1,243
195
Mackay
Hello, thank you for this provision of linegaos on the redmi note 10.

I just have a quick question. Why not be in the official lineage? What is blocking or what is the problem of going official?

thanks in advance
This isn't an answer to your question but there is some interesting info here.....

https://www.reddit.com/r/LineageOS/comments/eqo90x
and here which is linked in that thread.....

 

iooxda

Senior Member
Dec 1, 2019
67
33
Hi Group,

I am going to purchase a Note 10 Pro. My goal is to go directly from stock to LineageOS 18.1 with TWRP.

I have a good undertanding of how to unlocking the device and installing TWRP but I am not sure about this instruction:

Flash proper vendor and firmware

I am new to the MUI world, could someone please explain this step further. Is the instruction to flash these files in TWRP before flashing the ROM?

Which exact version of the ''vendor' and 'firmware' are required for Lineage 18.1 and where can I get these files, can someone share a reliable link?

Thank you.
 

appro77

Senior Member
May 8, 2011
1,243
195
Mackay
Hi Group,

I am going to purchase a Note 10 Pro. My goal is to go directly from stock to LineageOS 18.1 with TWRP.

I have a good undertanding of how to unlocking the device and installing TWRP but I am not sure about this instruction:



I am new to the MUI world, could someone please explain this step further. Is the instruction to flash these files in TWRP before flashing the ROM?

Which exact version of the ''vendor' and 'firmware' are required for Lineage 18.1 and where can I get these files, can someone share a reliable link?

Thank you.
Post #9 indicates that it isn't necessary if coming from stock MIUI. That was my experience. I didn't flash vendor and firmware. I flashed LineageOS only.

I've tried almost every rom available for this phone and have never flashed anything but the rom. Incidentally, I've found LineageOS to be the best overall. :)
 

xfahim

Senior Member
Aug 18, 2012
193
29
New York City
Redmi Note 10 Pro
Post #9 indicates that it isn't necessary if coming from stock MIUI. That was my experience. I didn't flash vendor and firmware. I flashed LineageOS only.

I've tried almost every rom available for this phone and have never flashed anything but the rom. Incidentally, I've found LineageOS to be the best overall. :)
Compared to ArrowOS? The reason I ask is arrow seems like the most popular one.

Although for me I don’t care about customizations at all. All I want is stock android, running stable and smoothly.

Have you faced any dealbreaker issues with LineageOS? (Eg. drm, call quality, haptics etc.)
 

appro77

Senior Member
May 8, 2011
1,243
195
Mackay
Compared to ArrowOS? The reason I ask is arrow seems like the most popular one.

Although for me I don’t care about customizations at all. All I want is stock android, running stable and smoothly.

Have you faced any dealbreaker issues with LineageOS? (Eg. drm, call quality, haptics etc.)
I can't remember why now but I didn't like Arrow for some reason.
Compared to ArrowOS? The reason I ask is arrow seems like the most popular one.

Although for me I don’t care about customizations at all. All I want is stock android, running stable and smoothly.

Have you faced any dealbreaker issues with LineageOS? (Eg. drm, call quality, haptics etc.)
I can't remember why I didn't like Arrow. Sorry. I had a bit of a flashathon going for a while jumping between roms. :)

I've found no dealbreakers with LineageOS in my usage. I'm not using the phone as my daily driver at the moment. I'm using a Pixel 4a 5G running LineageOS. I swap my sim over to the Redmi periodically to give it a run and I've encountered no problems. HTH.
 
  • Like
Reactions: xfahim

iooxda

Senior Member
Dec 1, 2019
67
33
Post #9 indicates that it isn't necessary if coming from stock MIUI. That was my experience. I didn't flash vendor and firmware. I flashed LineageOS only.

I've tried almost every rom available for this phone and have never flashed anything but the rom. Incidentally, I've found LineageOS to be the best overall. :)
Thank you, this is very helpful.

So should I update stock to the latest version then switch to Lineage or can I go directly to lineage from whatever I get when I first turn on the phone?

Another question about Lineage, can I set 60hz as the maximum refresh, is that a toggle in the settings? I am much more interested in great battery life than high refresh rate.
 

appro77

Senior Member
May 8, 2011
1,243
195
Mackay
Thank you, this is very helpful.

So should I update stock to the latest version then switch to Lineage or can I go directly to lineage from whatever I get when I first turn on the phone?

Another question about Lineage, can I set 60hz as the maximum refresh, is that a toggle in the settings? I am much more interested in great battery life than high refresh rate.
I'm not sure about if you should update MIUI first. It likely wouldn't hurt.

Yes, you can choose between 60hz and 120hz.
 

gstla

Member
Aug 26, 2019
8
2
How to get Signature Spoofing working on LineageOS Roms that have no support for Signature Spoofing?

First of all Flash your ROM and Magisk (you need to download the latest version to get Magisk)

Magisk Link: https://github.com/topjohnwu/Magisk/releases/

Go on Settings -> About Phone -> Click on Build number (7x) to enable Developer Options

After that enable USB Debugging in LineageOS go to Settings -> System -> Developer Options

So Lets go this is the more complicated part. but also really easy if you done it once.

You need to have ADB installed on your System tho.

ADB link: https://adbdownload.com

First of all you need to download this 4 Files:

https://gitlab.com/oF2pks/haystack/-/raw/11-attempt/spoof_AVDapi30.zip.ONLY'MAGISK&ANDROID-STUDIO?inline=false
https://github.com/microg/GmsCore/files/5652857/microG_AVDx86api30_magiskMaRViN.zip
https://gitlab.com/oF2pks/haystack/-/archive/11-attempt/haystack-11-attempt.zip
https://github.com/DexPatcher/dexpa...nload/v1.8.0-beta1/dexpatcher-1.8.0-beta1.jar

Rename "spoof\_AVDapi30.zip.ONLY'MAGISK&ANDROID-STUDIO" to "spoof_AVDapi30.zip"

Now unzip the "haystack-11-attempt.zip" and put the "dexpatcher.jar" file into to Folder.

This part I use Bash shell in Linux.

Code:
Bash:
adb pull /system/framework/services.jar
(put the "services.jar" in the folder where you extracted "haystack-11-attempt.zip" )

If you are using Windows install Java first https://www.java.com/fr/download/ then run cmd
Code:
and run the command:

java -jar dexpatcher-1.8.0-beta1.jar -a 11 -M -v -d -o ./ services.jar 11-hook-services.jar.dex 11core-services.jar.dex

(After that Command you should have 4 files all named "classes*.dex")

Code:
Bash:
mkdir repack
zip -j repack/services.jar classes*.dex


Windows Users:
Put the 4 files "classes*.dex" you generate on the phone then
Install "Termux" on your phone.
from Termux run the command: su
then accept the root part.
Now navigate to the folder where you have your 4 "classes*.dex files" then run the command

Code:
mkdir repack
zip -j repack/services.jar classes*.dex

After that you should have a new services.jar in your repack Folder.

Now You need to open the "spoof_AVDapi30.zip" and go in /system/framework/ and delete the old services.jar and put your own file services.jar that's in your repack Folder.

Don't ruin the zip-format of the file tho because otherwise Magisk will cry while install.

After that put your "spoof_AVDapi30.zip" and your "microG_AVDx86api30_magiskMaRViN.zip" on your Phone and Flash via Magisk, to do it click on the little Puzzle part in the down right cornet and chose "install from storage" then run the 2 zip files

Reboot and you hopefully have Signature spoofig working.

After this I update microg core https://github.com/microg/GmsCore/releases (Without this my microg was crashing)
then I install all those modules to enable the GPS and Fake Shop
https://github.com/microg/RemoteDroidGuard/releases
https://github.com/microg/FakeStore/releases
https://github.com/microg/android_packages_apps_GsfProxy/releases
https://github.com/microg/NominatimGeocoderBackend/releases
https://github.com/microg/IchnaeaNlpBackend/releases

Open "UnifiedNlp" app then click on "Configure location backends" and check the box do the same on "Configure address lookup backends". Restart the phone and Open back "UnifiedNlp" and click on "Self-check" and try to enable everything (for me the "UnifiedNlp is resgistered in system" can't be enable)

When done open "microG settings" and go on "Self-Check" same try to enable all

It's looks to works for me.


Thanks to Kingslayer9988 for the original guide and I also want to credit the real developers of this
on xda: Lanchon (DexPatcher & Haystack)
https://forum.xda-developers.com/m/lanchon.4141005/
 
Last edited:
  • Like
Reactions: NahKinn and xfahim

McFlyPartages

New member
Jul 27, 2021
4
1
Finistere
How to get Signature Spoofing working on LineageOS Roms that have no support for Signature Spoofing?

First of all Flash your ROM and Magisk (you need to download the latest version to get Magisk)

Magisk Link: https://github.com/topjohnwu/Magisk/releases/

Go on Settings -> About Phone -> Click on Build number (7x) to enable Developer Options

After that enable USB Debugging in LineageOS go to Settings -> System -> Developer Options

So Lets go this is the more complicated part. but also really easy if you done it once.

You need to have ADB installed on your System tho.

ADB link: https://adbdownload.com

First of all you need to download this 4 Files:

https://gitlab.com/oF2pks/haystack/-/raw/11-attempt/spoof_AVDapi30.zip.ONLY'MAGISK&ANDROID-STUDIO?inline=false
https://github.com/microg/GmsCore/files/5652857/microG_AVDx86api30_magiskMaRViN.zip
https://gitlab.com/oF2pks/haystack/-/archive/11-attempt/haystack-11-attempt.zip
https://github.com/DexPatcher/dexpa...nload/v1.8.0-beta1/dexpatcher-1.8.0-beta1.jar

Rename "spoof\_AVDapi30.zip.ONLY'MAGISK&ANDROID-STUDIO" to "spoof_AVDapi30.zip"

Now unzip the "haystack-11-attempt.zip" and put the "dexpatcher.jar" file into to Folder.

This part I use Bash shell in Linux.

Code:
Bash:
adb pull /system/framework/services.jar
(put the "services.jar" in the folder where you extracted "haystack-11-attempt.zip" )

If you are using Windows install Java first https://www.java.com/fr/download/ then
Code:
and run the command:

java -jar dexpatcher-1.8.0-beta1.jar -a 11 -M -v -d -o ./ services.jar 11-hook-services.jar.dex 11core-services.jar.dex

(After that Command you should have 4 files all named "classes*.dex")

Code:
Bash:
mkdir repack
zip -j repack/services.jar classes*.dex


Windows Users:
Put the 4 files "classes*.dex" you generate on the phone then
Install "Termux" on your phone.
from Termux run the command: su
then accept the root part.
Now navigate to the folder where you have your 4 "classes*.dex files" then run the command

Code:
mkdir repack
zip -j repack/services.jar classes*.dex

After that you should have a new services.jar in your repack Folder.

Now You need to open the "spoof_AVDapi30.zip" and go in /system/framework/ and delete the old services.jar and put your own file services.jar that's in your repack Folder.

Don't ruin the zip-format of the file tho because otherwise Magisk will cry while install.

After that put your "spoof_AVDapi30.zip" and your "microG_AVDx86api30_magiskMaRViN.zip" on your Phone and Flash via Magisk, to do it click on the little Puzzle part in the down right cornet and chose "install from storage" then run the 2 zip files

Reboot and you hopefully have Signature spoofig working.

After this I update microg core https://github.com/microg/GmsCore/releases (Without this my microg was crashing)
then I install all those modules to enable the GPS and Fake Shop
https://github.com/microg/RemoteDroidGuard/releases
https://github.com/microg/FakeStore/releases
https://github.com/microg/android_packages_apps_GsfProxy/releases
https://github.com/microg/NominatimGeocoderBackend/releases
https://github.com/microg/IchnaeaNlpBackend/releases

Open "UnifiedNlp" app then click on "Configure location backends" and check the box do the same on "Configure address lookup backends". Restart the phone and Open back "UnifiedNlp" and click on "Self-check" and try to enable everything (for me the "UnifiedNlp is resgistered in system" can't be enable)

When done open "microG settings" and go on "Self-Check" same try to enable all

It's looks to works for me.


Thanks to Kingslayer9988 for the original guide and I also want to credit the real developers of this
on xda: Lanchon (DexPatcher & Haystack)
https://forum.xda-developers.com/m/lanchon.4141005/
Thanks for the How To
 
Jul 30, 2021
1
0
Hello Guys!

Thanks for the LineageOS rom, seems to work great. The only problem I have is that the FakeGApps application does not seem to enable signature spoofing. Does anybody know why that is?

I tried following the guide from the post above, but the java part gets a bit to techy. Is there an easier way, or a noob proof explanation on how to do this? Thanks!
 

1emrys1

Senior Member
May 29, 2013
758
562
Most of ROM proposing vanilla version do. So far from viable ROMS I've tried supporting Signature Spoofing for MicroG are:
- CherishOS
- OctaviOS
- DotOS

It baffles me that a rom pretending to be LineageOS doesn't include that simple option that all other ROMs are including (cf screenshot). Lineage OS stands for privacy and anonymity. They even develop ROMs in collaboration with microG (https://lineage.microg.org/) . But this unofficial version hasn't got a clue. Utterly baffling !
That lineage microg link that you posted isn't associated in any way with official lineage. It is another team which takes official lineage roms and turns them into microg versions.

Lineage officially doesn't support any kind of spoofing or bypassing safety net. If you would have spent some time learning about all this then you would know everything that I just wrote.

But instead you come here with half baked knowledge to criticize a dev who works on this project as a hobby.
 
  • Like
Reactions: appro77

Nocturne_

New member
Aug 1, 2021
1
0
Is anyone else having issues with fastcharging? On MIUI it works fine however on LOS it looks like its only charging at 5V 2.5A with the official charger. Another charger I have that shows QC3 status shows that it enables breifly at the start (and on the lock screen it says "Charging") but then disables (and on the lock screen says "Charging rapidly")
 

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    Hmm, is the protocol relevant?
    I'd rather check all that IPs you got.
    I'm using the f-droid version.
    Why is blocking all traffic important? Does the traffic not show in the log, if it gets through?
    I am blocking all traffic because this is a new device so I am monitoring all of the outgoing traffic from a base install to get an understanding of what is on the phone and where it is reaching out to. So far I can account for everything else except these entries that constantly show up. I think AFWall only logs denied packets, not sure if you can set it to log everything.

    The protocol is important because it is very unusual. I don't even know if a phone would normally have any software using this protocol. The only thing I found for protocol 128 is this:

    x80128SSCOPMCEService-Specific Connection-Oriented Protocol in a Multilink and Connectionless EnvironmentITU-T Q.2111 (1999)

    List of IP protocol numbers - Wikipedia


    I will try to report more addresses but I have larger issues, I am looking at logcats and trying to figure out why my phone keeps crashing when I turn on WIFI.

    Also, have you noticed that this ROM is super aggressive at killing apps? If I switch an app to the background then 1 min later to the foreground it reloads and I have lost the data. I don't think I can keep using this ROM if I can't get this under control. I have > 5GB RAM and only running 2 apps, nothing should get killed.

    I am on this build now and so far 3 builds I have tried all suffer from this: lineage-18.1-20210807-UNOFFICIAL-sweet-VANILLA.zip
    2
    I have installed Lineage:
    - lineage-18.1-20210610-UNOFFICIAL-sweet-VANILLA.zip

    and this vendor/firmware:

    on my sweet, first clean install directly from stock.

    I installed two apps from f-droid
    - AFWall (firewall)
    - PCAPdroid (packet capture)

    I let AFWall monitor all outgoing traffic for 24 hours and found some unusual results.

    AFWall continuously logs packets from an unknown app going out to various IP addresses with protocol 128 so not TCP.

    Here is an example:

    AppID: -1
    App Name:
    [128] 111.13.191.244:0
    [128] 184.131.145.255:0

    I have recorded a constant stream of over 50 different IP addresses over 24 hours and I can't figure out what is generating this traffic.

    I have run Lineage 17.1, 18.1 on several different devices and so far and I have only seen this traffic on sweet.

    Another user also saw this traffic on a different device back from Lineage 16: https://forum.xda-developers.com/t/...s-16-0-20200107.3923203/page-53#post-81084669

    So I do not believe it is an issue specific to our ROM. @grewal09 do you have any insight into what could be generating his traffic on a fresh Lineage install with no apps? Seeing as it appears to be an issue for an issue for at least two at different Lineages perhaps an upstream developer can lend insight, any idea who would be familiar with this I could ask?
    Hi,
    Your post made me nervous, because 111.13.191.244 belongs to China Mobile Communications Corporation.
    See: https://ipinfo.io/AS9808/111.13.0.0/16-111.13.190.0/23.
    So I thought this could be some potential bloatware or spyware.
    I did the same test with the latest build and global vendor image, just with gapps, magisk and tons of stuff installed and was not able to reproduce it.
    Can you try to reproduce it with the latest image?
    2
    I have installed Lineage:
    - lineage-18.1-20210610-UNOFFICIAL-sweet-VANILLA.zip

    and this vendor/firmware:

    on my sweet, first clean install directly from stock.

    I installed two apps from f-droid
    - AFWall (firewall)
    - PCAPdroid (packet capture)

    I let AFWall monitor all outgoing traffic for 24 hours and found some unusual results.

    AFWall continuously logs packets from an unknown app going out to various IP addresses with protocol 128 so not TCP.

    Here is an example:

    AppID: -1
    App Name:
    [128] 111.13.191.244:0
    [128] 184.131.145.255:0

    I have recorded a constant stream of over 50 different IP addresses over 24 hours and I can't figure out what is generating this traffic.

    I have run Lineage 17.1, 18.1 on several different devices and so far and I have only seen this traffic on sweet.

    Another user also saw this traffic on a different device back from Lineage 16: https://forum.xda-developers.com/t/...s-16-0-20200107.3923203/page-53#post-81084669

    So I do not believe it is an issue specific to our ROM. @grewal09 do you have any insight into what could be generating his traffic on a fresh Lineage install with no apps? Seeing as it appears to be an issue for an issue for at least two at different Lineages perhaps an upstream developer can lend insight, any idea who would be familiar with this I could ask?
    Yes I am on the latest image now, the EEA version. I have installed and tested the base ROM with just the single AFWall app 6 pr 7 times. Those firewall entries always show up in the log constantly. Many different addresses, all the time. The strange thing is I don't know what they are, they aren't TCP they are protocol number 128 and I do not know what that is.

    A user in the AFWall thread think it could be a bug in the logging app but but definately not sure. The dev of AFWall has not commented yet.

    Are you running the f-droid version of AFWall? I install it and block all traffic and just watch what shows up in the log.
    2
    Yes I am on the latest image now, the EEA version. I have installed and tested the base ROM with just the single AFWall app 6 pr 7 times. Those firewall entries always show up in the log constantly. Many different addresses, all the time. The strange thing is I don't know what they are, they aren't TCP they are protocol number 128 and I do not know what that is.

    A user in the AFWall thread think it could be a bug in the logging app but but definately not sure. The dev of AFWall has not commented yet.

    Are you running the f-droid version of AFWall? I install it and block all traffic and just watch what shows up in the log

    Yes I am on the latest image now, the EEA version. I have installed and tested the base ROM with just the single AFWall app 6 pr 7 times. Those firewall entries always show up in the log constantly. Many different addresses, all the time. The strange thing is I don't know what they are, they aren't TCP they are protocol number 128 and I do not know what that is.

    A user in the AFWall thread think it could be a bug in the logging app but but definately not sure. The dev of AFWall has not commented yet.

    Are you running the f-droid version of AFWall? I install it and block all traffic and just watch what shows up in the log.
    Hmm, is the protocol relevant?
    I'd rather check all that IPs you got.
    I'm using the f-droid version.
    Why is blocking all traffic important? Does the traffic not show in the log, if it gets through?
    2
    I have installed Lineage:
    - lineage-18.1-20210610-UNOFFICIAL-sweet-VANILLA.zip

    and this vendor/firmware:

    on my sweet, first clean install directly from stock.

    I installed two apps from f-droid
    - AFWall (firewall)
    - PCAPdroid (packet capture)

    I let AFWall monitor all outgoing traffic for 24 hours and found some unusual results.

    AFWall continuously logs packets from an unknown app going out to various IP addresses with protocol 128 so not TCP.

    Here is an example:

    AppID: -1
    App Name:
    [128] 111.13.191.244:0
    [128] 184.131.145.255:0

    I have recorded a constant stream of over 50 different IP addresses over 24 hours and I can't figure out what is generating this traffic.

    I have run Lineage 17.1, 18.1 on several different devices and so far and I have only seen this traffic on sweet.

    Another user also saw this traffic on a different device back from Lineage 16: https://forum.xda-developers.com/t/...s-16-0-20200107.3923203/page-53#post-81084669

    So I do not believe it is an issue specific to our ROM. @grewal09 do you have any insight into what could be generating his traffic on a fresh Lineage install with no apps? Seeing as it appears to be an issue for an issue for at least two at different Lineages perhaps an upstream developer can lend insight, any idea who would be familiar with this I could ask?
    That's really scary! Data leakage from ROMs.
    Is there a process here @ xda to check these ROMs for data leakage/malicious software being slyly slipped into ROMs while being compiled?
  • 35
    1200px-Lineage_OS_Logo.png

    Code:
    /*
    * I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
    * Please do some research if you have any concerns about features included in the products you find here before flashing it!
    * YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
    * Your warranty will be void if you tamper with any part of your device / software.
    * Same statement for XDA.
    */

    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 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.


    What's working :

    • Boots
    • DT2W
    • RIL (Calls, SMS, Data)
    • Fingerprint
    • Wi-Fi
    • Bluetooth
    • Camera
    • Camcorder
    • Video Playback
    • Audio
    • Sensors
    • Selinux Enforcing
    • Flash
    • LED
    • GPS
    • Volte
    • VoWifi


    Known issues:
    • You tell me

    Instructions :
    • Download the latest build
    • Reboot to recovery
    • Flash proper vendor and firmware
    • Flash the latest build and GApps if needed
    • Format data
    • Reboot

    Note: These Builds are unified for both Redmi Note 10 Pro and Note 10 Pro Max

    PS
    : Please Use proper vendor and firmware of your device of stable miui rom for eg: if your device is eea so use eea vendor and firmware if your device is Indian variant use Indian firmware and vendor and same is the case with Chinese version please don't cross flash vendors and firmware. To use this rom please Flash Android 11 firmware and vendor

    Downloads :
    Lineage Recovery : Image
    build : Sourceforge

    Telegram Groups



    Source Code: Kernel
    8
    Update Time
    Changelog
    • We are now enforcing
    • April Security Patch
    • Fixed Volume steps in calls
    • Fixed the yellow tint
    • Fixed Earphone Volume Control
    • Fixed DT2W
    • Added option for Android 10 Media Player
    • Added Colour Calibration option in LiveDisplay
    • Added face unlock
    • Added Dirac Sound Enhancer
    • Added per app Thermal and Touch profiles
    • Added option to wake the screen instead of pulsing ambient
    • Inject Doze Preferance at correct place
    • Added support for 108/64 and Portrait mode in ANXCamera
    • Added Google recorder support
    • Added Network Traffic indicator
    • Added Dynamic VoLTE/VoWiFi icon
    • Enabled Text Clock
    • Enabled Night Light
    • Enabled Blur

    Builds can be grabed from op
    Thanks
    7
    New builds are up
    Changelog:
    • Addressed more SELinux denials
    • Switched to QTI power hal
    • Switched to a better Implementation for dt2w
    • Allowed setting lowest brightness even lower
    • Tweaked Auto-Brightness
    • Tweaked Vibration feedback
    • Upstreamed with LOS source

    Builds are dated 25/04 and can be grabbed from op
    6
    Update TIme XD

    Change log: https://telegra.ph/LOS-June-Update-06-11

    Links are Updated in op
    5
    New builds are up
    Changelog:
    • Added Snap Cam as the default camera
    • Added DC Dimming
    • Added Wireguard
    • Added 3 finger Screen Shot
    • Added a couple more Lock screen clocks
    • Better RAM management
    • Set Default Refresh Rate to 120hz
    • Switch to a source built kernel
    • LOS Upstream
    • Misc Stuff & Cleanup