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

Search This thread

ssaikia3

Senior Member
Jan 9, 2018
126
48
Hello everyone,
Just stumbled upon my first serious issue with this ROM: neither camera (stock *and*GCam) can *save* any pictures. What happens (with both of them, and in any mode) is that the picture is taken, and is shown in the small "thumbnail area" near the bottom right of the camera app's main screen; but when I click on the "thumbnail" to open the full photo, it is displayed for just a fraction of a second and then the last picture taken successfully (before this problem started) is shown instead.

Opening Gallery or GooglePhotos apps show only the pictures taken before the problem started.

I'm running the 2020-01-22 version of this ROM, which I clean flashed straight on top of the original Xiaomi MIUI.

Already tried:
- rebooting and power-off-and-back-on;
- clearing the apps' caches;
-rebooting to recovery and clearing dalvik/cache;

Can anyone help? Please *don't* tell me I'm going to have to reinstall everything -- on a data-capped cell plan right now, and doing that would be really expensive and painful.

Thanks in advance!
Just for the record, clearing/wiping the data partition can essentially be compared to a clean flash.

Files in system partition are usually left untouched, as it's supposed to be read-only. So any data required to be saved by an app are usually stored in data partition, So in theory, If you have not altered any data in system partition, by means of any root app or adb or stuff like that, than there is no need to format the system partition and flash the same zip all over again, just wipe the data partition, it'll act like a clean flash, and see if that works/solves your problem.

I'm not saying this can replace the process of a clean flash, but might be helpful in some situations where you're asked to reflash the same zip, and in a "capped data plan" situation.

I haven't dived into all the technicalities, this is just from my basic understanding, and a little experience, If I'm wrong feel free to correct me.
 

Antineutrino

Senior Member
Aug 7, 2007
163
13
Roma
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

Senior Member
Jun 12, 2013
73
13
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

Screenshot-20200227-111719-Settings.png
 
Last edited:

AmulyaX

Recognized Developer
Feb 12, 2015
1,002
4,677
22
Ghaziabad
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 ?
 
  • Like
Reactions: meindianbro

Antineutrino

Senior Member
Aug 7, 2007
163
13
Roma
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?
 

niix

Senior Member
Jun 12, 2013
73
13
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.
 

Ceejay343

Senior Member
Jun 9, 2016
163
52
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
 
Last edited:

titogsg

Member
Dec 28, 2009
37
4
Somewhere in Spain
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?
 

NamenIos

Senior Member
Nov 26, 2010
473
243
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.
 
  • Like
Reactions: kingfared

Top Liked Posts

  • There are no posts matching your filters.
  • 87
    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
    74
    zYkSW7S.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 10, 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
    • RIL (Calls, SMS, Data)
    • Fingerprint
    • Wi-Fi
    • Bluetooth
    • IR camera
    • Camera
    • Camcorder
    • Video Playback
    • Audio
    • Sensors
    • Flash
    • LED
    • GPS/GNSS
    • VoLTE

    Known issues:
    • You tell me (None)

    Instructions :
    • Reboot to Recovery (Preferably Ofox)
    • Wipe system, data, vendor, cache, dalvik
    • Now flash the LineageOS build and any other addons you want
    • You may flash OpenGapps and or Magisk
    • Reboot

    Note: If you're unable to download Netflix or some other app from Play Store and or if you're unable to use Widevine L1, please consider flashing Magisk.

    Downloads :
    • Official Build : Here
    • Firmware : All firmwares for lavender are supported (Prefer latest Global Stable)[/URL]

    XDA:DevDB Information
    LineageOS, ROM for the Xiaomi Redmi Note 7

    Contributors
    AmulyaX, xdatman
    Source Code: https://github.com/LineageOS
    Kernel Source: https://gitlab.com/kjjjnob/kernel_xiaomi_lavender_minimal

    ROM OS Version: Android 10
    ROM Kernel: Linux 4.x
    Based On: AOSP

    Version Information
    Status: Stable

    Created 2019-09-17
    Last Updated 2020-01-22
    40
    Changelog

    15/02/2020
    -February Security Patch
    -Fixed BT mic issues
    -Fixed some audio issues
    -Updated more blobs from latest CAF tag
    -Major stability and performance improvements from my previous releases
    -Merged with latest sources



    22/01/2020
    -Initial Android 10 release
    -January Security Patch
    -Android 10 Blobs from Lavender Release
    -Major stability and performance improvements from my previous releases
    -Merged with latest sources



    12/10/2019
    -October Security Patch Merged
    -Offline Charging Animation Added
    -Updated Vendor Security Patch string as people wanted it
    -FM has been fixed
    -Widevine L1 support added
    -WhatsApp VC Lag fixed
    -Major stability and performance improvements
    -Merged with latest sources



    16/09/2019
    -Initial Release
    -Elliptic Proximity Sensor has been thoroughly fixed
    -Rebased device tree on CAF
    -Major performance, battery and stability improvements
    31
    LineageOS 16

    Changelog
    -Initial Release
    -Elliptic Proximity Sensor has been thoroughly fixed
    -Rebased device tree on CAF
    -Major performance, battery and stability improvements




    1. Flash GApps along with ROM
    2. CLEAN FLASH ONLY.
    3. Build with Stock kernel, I recommend using Genom
    4. No restrictions on Firmware you want to use
    5. No need to flash vbmeta or Magisk (to boot), flash Magisk only if you want root



    27
    LineageOS 17.1

    WARNING: ANDROID 10 BLOBS require format /data after flashing build or data will be encrypted

    Changelog
    -Initial Android 10 release
    -January Security Patch
    -Android 10 Blobs from Lavender Release
    -Major stability and performance improvements from my previous releases
    -Merged with latest sources


    Please note:
    1. I prefer BiTGApps along with ROM ( https://t.me/bitgapps_downloads_official/320 , read carefully or you won't get Setup Wizard)
    2. BACKUP DATA as it needs to be FORMATTED.
    3. Built with Stock Minimal Kernel, do not use Custom Kernels as this uses new camera blobs, if you flash a custom kernel that doesn't support latest Xiaomi camera changes, camera won't work.
    4. No restrictions on Firmware you want to use
    5. Flash Magisk only if you want root


    Thanks to @kjjjnob for his 'original work' for lavender, this man works throughout his free time to improve development scenario for lavender, not talking about building ROMs using trees, talking about making the sources better and usable with time and changes.

Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone