[ROM][UNOFFICIAL][10][lavender] LineageOS 17.1

[Antineutrino]

I'm having an issue with the device not going in deep sleep state.
I clean flashed the ROM with these steps:
- Flash latest firmware blobs 20.1.21
- Format /data
- Flash lineage-17.1-20200215-UNOFFICIAL-lavender.zip
- Flash latest BiTGApps-arm64-10.0.0-v0.1_signed.zip
- Reboot
- Flash Magisk
- Reboot
- Restore Call Logs and SMS using Titanium Backup
- Install BBS

 

[niix]

Hi.
I used to run the lineage 16, as a daily driver, from AmulyaX, October build. After a data loss, due to encryption, I had to download the ISO again from this link: https://sourceforge.net/projects/lavenderreleases/files/LineageOS/

The weird thing is that the build now has February android security patches and ctsprofile validates (it didn't before without the patch).

So, how is this possible? AmulyaX replaced the ISO without changing build date, modification date and filename? Or there is another explanation to this?
Could Magisk or bitgapps modify android security patch?

Modified:2019-10-12
Size:819.6 MB
SHA1:f81ce3967069c9fbc955655ae27eeb2b09430386
MD5:81a156165ddc6dd65ef9555b690bbe4b

 

[AmulyaX]

Hi.
I used to run the lineage 16, as a daily driver, from AmulyaX, October build. After a data loss, due to encryption, I had to download the ISO again from this link: https://sourceforge.net/projects/lavenderreleases/files/LineageOS/

The weird thing is that the build now has February android security patches and ctsprofile validates (it didn't before without the patch).

So, how is this possible? AmulyaX replaced the ISO without changing build date, modification date and filename? Or there is another explanation to this?
Could Magisk or bitgapps modify android security patch?

Modified:2019-10-12
Size:819.6 MB
SHA1:f81ce3967069c9fbc955655ae27eeb2b09430386
MD5:81a156165ddc6dd65ef9555b690bbe4b

Someone reported a similar issue when I had vince.
It's due to some Magisk module that you are using! It's indeed weird though ?

 

[jpdoliveira]

I have an issue with hotspot. I just clean flashed and when i create an hotspot and connect with other phone, my phone just reboots.

 

[Antineutrino]

I have an issue with hotspot. I just clean flashed and when i create an hotspot and connect with other phone, my phone just reboots.

Try disabling Tethering hardware acceleration in developer options.

 

[jpdoliveira]

Try disabling Tethering hardware acceleration in developer options.

Yea that look's like its working. Thanks

 

[VincentJoshuaET]

Any news for official support?

Sent from my Xiaomi Redmi Note 7 using XDA Labs

 

[SykoraLukas]

Any news for official support?

Sent from my Xiaomi Redmi Note 7 using XDA Labs

There won't be any.

Odesláno z mého Redmi Note 7 pomocí Tapatalk

 

[Antineutrino]

I'm having an issue with the device not going in deep sleep state.
I clean flashed the ROM with these steps:
- Flash latest firmware blobs 20.1.21
- Format /data
- Flash lineage-17.1-20200215-UNOFFICIAL-lavender.zip
- Flash latest BiTGApps-arm64-10.0.0-v0.1_signed.zip
- Reboot
- Flash Magisk
- Reboot
- Restore Call Logs and SMS using Titanium Backup
- Install BBS

Still having this problem...
I tried everything. No deep sleep at all. Am I missing something?

 

[isaiah17]

Does parrot gcam works with this rom?

 

[niix]

Someone reported a similar issue when I had vince.
It's due to some Magisk module that you are using! It's indeed weird though

I wasn't using anything special. Just Magisk, busybox Magisk module, systemize and YouTube vanced. On top of that bitgapps. That was a couple of days old setup.

Could it be something done by google?
Anyway, I got scared and changed ROM. Just in case I got some kind of malware.

 

[atendedor_de_boludos]

Does parrot gcam works with this rom?

Nope, it didn't work for me

 

[bahman_0121]

parrot gcam doesn't work plz fix
all music player lag and stop play
xiaomi parts not work

 

[Ceejay343]

Sensors don't work, clean flash. That is, app reports no sensors are working is it that it don't support Android q? Which test app can I try?

Edit search tells all nvm

 

[Namaless]

Thanks

 

[titogsg]

Hello there.
I have a stranger problem. I do a install clean, configure the rom and seems all ok. When i try to remove any apk that i don't use, for example, gallery or browser, (using root uninstaller or system apk remover), in the next reboot, the phone boot in fastboot and get bricked.
And i don't remove any problematic or system apk, just, screen recorder, or gallery or similar, and always have the same result, when i reboot the phone.... zas! fastboot. 3 times i tried and 3 times bricked, just for remove a simple apk?
Why?

 

[macpla]

I don't know why, people here don't want to do checksums it may be the most common issue with flashing ROM.

 

[NamenIos]

Hello everyone!
Before this thread gets plagued with questions like what's different in this LineageOS build, let me clear everything up for you!

Current Development Scenario for Lavender

• More buildbots than developers
• Device sources do not have a proper commit history, and is little bloated
• There are major battery issues with current sources
• Elliptic Proximity Sensor doesn't work as it should
• Unable to use full potential of sdm660, as it has full CAF support, yet currently we use everything from MIUI
• People are taking the only few developers for granted, I have seen the community doesn't want to contribute at all by testing builds, and this is due to the increasing number of buildbots here
• People working on private sources, these guys use stuff from all Open Source Developers yet keep their work private, I am strongly against such people, I started my work a month ago, and everything was public on GitHub

What happened here?

• I started working on a CAF rebase a month ago, and now finally I have fixed all bugs that occured, CAF rebase is basically cloning trees that CAF releases for sdm660 devices, and doing bringup for lavender, so these trees are built from scratch
• Proper Commit history with proper authorship to all my fellow developers
• Elliptic Proximity Sensor has thorougly been fixed, you won't face any issues, no need to reboot or anything
• Battery issues might have been dealt with, don't expect extreme difference
• Sources are public, my fellow lavender developers can freely fork a copy of my trees and carry on development, I do not want any kind of fame or attention by keeping stuff private.
• Users can feel the snappy performance as I didn't add a lot of stuff from MIUI, just selective, most of it is still from CAF.

So here you go, feel free to make your own changes, all I want is lavender to stand back up because right now, its really going down due to some retards here in the community. Users need to contribute more, not financially but help developers with testing and some support rather than supporting people who encourage use of private sources.

Device Tree: https://github.com/AmulyaX/android_device_xiaomi_lavender (-b lineage-16.0)
Vendor: https://github.com/AmulyaX/proprietary_vendor_xiaomi_lavender (-b lineage-16.0)

Credits:
For bringup references: Bladeyy and GuaiYiHu
For helping me throughout and maintaining commit history: @xdatman
For testing (few godly users who were sensible and smart enough to help with testing): @JSPiRiT , @Lone Soul , @Electro CZE and @christopaul97

Can you please refresh the device, kernel, vendor trees? I always have trouble building lineage from your repos for myself due to some mismatch in your repositories. Your current status on Github doesn't build with any combination of branches.

 

[charliesheen]

any viber users here??
i cant register viber in this rom.
i get resource not found exception but nothing on the syslog

 

[AmulyaX]

Can you please refresh the device, kernel, vendor trees? I always have trouble building lineage from your repos for myself due to some mismatch in your repositories. Your current status on Github doesn't build with any combination of branches.

Well, it's not my fault you don't stay updated with the thread, I have made announcements in the past regarding how and which branches to use along with the kernel I am using. -b lineage-17.1 and Minimal kernel, you'd face 2-3 build errors which should be easy to fix.