how to make the 18.1 support the NTFS flash drive? i tried the below magisk module, but failed. thank you.
OK so the bummer of this is that after I OTA upgraded, the Miui camera just vanished from the phone. That's going to be a problem. @NeoArian, any idea on how to avoid that?
One page back... 7th comment (by me...)... 4th Line. Shouldn't be too difficult to find.Thank you so much, @NeoArian ! The latest global stable firmware for android 9 (V11.0.6.0.PCAMIXM) works well with this version of LineAge OS?
One page back... 7th comment (by me...)... 4th Line. Shouldn't be too difficult to find.
Guys, please read the comments before asking. People take their time to write them, you should take your time to read them...
vibration is still there.Has anyone updated to the last lineage-18.1-20210617-nightly-sagit-signed.zip build?
if so? have you lost vibration?
cheers
Just sharing my experience in case is useful for others.Yes i was coming from official lineage 17.1. No, at first i didn´t install any other gapps with 18.1, i wrongly thought that i didn't need to do that cause i already had them in 17.1
With location, i'm still having issues i CAN grant permissions to apps that need lotacion but the apps doesnt seem to be able to use it. I might try different gapps as this ones are giving me trouble.
If that doesn't fix it , i may aswell try to install everything from scratch.
I updated to 20210617. I still have vibration.Has anyone updated to the last lineage-18.1-20210617-nightly-sagit-signed.zip build?
if so? have you lost vibration?
cheers
Just updated to '20210624' and vibration is fine.Has anyone updated to the last lineage-18.1-20210617-nightly-sagit-signed.zip build?
if so? have you lost vibration?
cheers
I think I owe you an explanation, I own two devices both are on 18.1, I updated my first device (not Sagit) and lost vibration, so did not want to lose it also on mi6 hence my question, since the vibration issue affected devices only using the Qualcomm 8250 chipsets which has been fixed since.Just updated to '20210624' and vibration is fine.
But on charging I now get a vibration when I attach the cable. Even though under "Charging sounds" -> "Vibrate" is turned off. But I have the same issue on another device using 18.1. So maybe that's a general issue. I don't midn much.
Thanks for your great work @NeoArian !
same as you, I cleaned everything , installed this nik gapps , updated all the apps as soon as the system started and the localization worked , I 'm not sure but it seems that mindthegapps sometimes has a problem with permissions .Just sharing my experience in case is useful for others.
At the end i had to clear data again (tried reinstall with latest nightly and gapps and had a bootloop) and reinstall everything with nikgapps and latest build. It didn't give me any more problems grating permissions and everything worked good since the begining. Location is obtained instantly now from apps with permission.
Thanks for the replies @NeoArian and others. I finally had time to look into it again and try the suggestions.On boot the date and time are reset to the day and time when the system was installed/updated.
You're right, the erroneous time after boot indeed represents the build date and time.
It made no difference.If you have root, can you try to set persist.vendor.delta_time.enable=false? It's currently set to true from venor/build.prop.
I've confirmed the mac-address is the same as it was when the phone was running the official firmware.An easy indicator for you persist partition being intact is that the wlan and mac adresses are shown correct (correct as in it's the proper mac adress from factory.
Yes, I've attached it. What stands out to me is it starts with date 02-20, then changes to 12-13 at some point, then 06-24 at these lines:Can you get a logcat from boot until the device has booted? We can check for selinux denials then.
I hope the full logcat provides a clue!12-13 22:29:00.959 1307 1307 I AlarmManager: Current time only 1607894940959, advancing to build time 1624524164000 12-13 22:29:00.959 1307 1307 D AlarmManagerService: Setting time of day to sec=1624524164 06-24 10:42:44.000 1307 1307 W AlarmManagerService: Unable to set rtc to 1624524164: Invalid argument
Due to the QPR2 update (the march security patch/pixel feature drop) introduced some breaking changes, which deprecated our radio hal. We try to get sagit, and other devices with the same issue, supported again but in order to not hold newer devices from shipping with newer security patches again, the affected devices have been removed from the build list for now.
[COLOR="Purple"]#include <std_disclaimer.h>[/COLOR]
[COLOR="Navy"]/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* 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.
*/[/COLOR]
If you don't know LineageOS and would like to read about it before installing it you can take a look at the official Website.LineageOS, an open-source Android distribution, is available for several devices,
with more being continuously added thanks to the biggest, yet ever growing, Android open-source community.
Join us and breathe new life in your device, be it old or new.
SecurityCustomization is paramount to productivity.
That’s why LineageOS promises to push for user personalization and preference.
Everyone is unique and your device should be too.
LongevityYour data, your rules. With powerful tools such as Privacy Guard, you are in control of what your apps can do whenever you want.
Trust will help you understand the security of your device and warn you about possible threats.
We take security very seriously: that’s why we deliver security updates every month to all our supported devices.
And to make your device more secure, lock everything behind an enhanced lock screen.
LineageOS extends the functionality and lifespan of mobile devices from more than 20 different manufacturers thanks to our open-source community of contributors from all around the world.
Due to the QPR2 update (the march security patch/pixel feature drop) introduced some breaking changes, which deprecated our radio hal. We try to get sagit, and other devices with the same issue, supported again but in order to not hold newer devices from shipping with newer security patches again, the affected devices have been removed from the build list for now.
LineageOS 20.0 for Xiaomi MI 6 (sagit)
Build date: 2023-01-03
Security patch: 2022-12-05
Variant: VANILLA
Changelog (https://raw.githubusercontent.com/arian-ota/changelog/lineage-20/sagit.txt)
Download
lineage-20 (https://github.com/arian-ota/ota/re...5e/lineage-20.0-20230103-UNOFFICIAL-sagit.zip)
⛭ GitHub release / additional files (https://github.com/arian-ota/ota/releases/tag/20.0-sagit-704da75e)
SHA-256 checksum
704da75ed57272b438699cc1d0b918626335aced126d05a4971d045bb71351ac
#sagit