[ROM][UNOFFICIAL] LineageOS 21 for Mi Max 2 - Kernel 4.19

Search This thread

HalifaxTe55

Senior Member
Mar 1, 2017
185
156
perth
A few more tests performed, news. Again I reinstalled the ROM (totaling 3 reinstallations in a row), to have the system clean. In the initial configuration step I just went ahead without contaminating the settings, not even wifi was configured. After booting the system completely, again mobile data did not work. The first procedure I did before any other was to disable "Use SIM", which by default is already enabled and then re-enabled. Then mobile data worked. This test I did because in the previous installation I tested several settings on the part of SIMs, only when I disabled and reactivated mobile data, it also worked. If I restart the system, mobile data stops working. Then I disable and re-enable "Use SIMs" and again it works again. I hope this can shed some light on this problem. I keep doing tests.
PM
 

iparout

Member
Nov 3, 2011
14
3
If the issue is solved, please reply here. I wouldn't mind having to disable and re-enable SIM in order to get mobile data, if this ensures the mobile data works until next phone restart. I rarely restart the phone so it's not a big issue. I prefer having an Android version higher than 7.0.
 

iparout

Member
Nov 3, 2011
14
3
A few more tests performed, news. Again I reinstalled the ROM (totaling 3 reinstallations in a row), to have the system clean. In the initial configuration step I just went ahead without contaminating the settings, not even wifi was configured. After booting the system completely, again mobile data did not work. The first procedure I did before any other was to disable "Use SIM", which by default is already enabled and then re-enabled. Then mobile data worked. This test I did because in the previous installation I tested several settings on the part of SIMs, only when I disabled and reactivated mobile data, it also worked. If I restart the system, mobile data stops working. Then I disable and re-enable "Use SIMs" and again it works again. I hope this can shed some light on this problem. I keep doing tests.
Does mobile data (4G) work normally until next phone boot when you enable and disable "USE SIM" ? If yes, that's not a big issue for me, I can disable and enable the option when I reboot the phone (which is not that frequent).
 

virtualhjs

Member
Jan 19, 2015
16
3
UPDATE : Disabling and re-enabling USE SIM doesn't work for me, unfortunately. I still get no mobile data.
Did you do any additional tests? Apparently the automatic management of the available network choice doesn't work well in some situations. You can disable auto pick, you can specify which networks to use, for example WCDMA (3G) and GSM (2G), or just WCDMA as LTE (4G) doesn't work for me, if I force to use only 3G I finally get some peace with it. But every now and then it crashes and I have to change the network to be used again, deactivate and reactivate. Anyway, it seems like a random solution, it's not something exact. I'm currently using the Pixel Experience ROM that has the same problem and I can mitigate it with the same procedures.

I'm going to test the new Pixel Experience release, if it works, surely the same adjustment made in Lineage will work too.
 

TorpedoJavi

Member
Dec 11, 2012
14
3
Spain
Hi, first of all thank you very much for your LineageOS rom.

I'm trying to "adapt" your rom to "LineageOS for microG" https://lineage.microg.org/ which is a fork of LineageOS with microG (without GoogleApps but that make many apps compatible with apps that require the Google APIs).

The porblem of microG is that it requires Spoofing if it's added to a standard LineageOS rom.

Could you make a fork of your LineageOS rom to LineageOS for microG rom?

Thanks with advance....
 

HalifaxTe55

Senior Member
Mar 1, 2017
185
156
perth
Hi, first of all thank you very much for your LineageOS rom.

I'm trying to "adapt" your rom to "LineageOS for microG" https://lineage.microg.org/ which is a fork of LineageOS with microG (without GoogleApps but that make many apps compatible with apps that require the Google APIs).

The porblem of microG is that it requires Spoofing if it's added to a standard LineageOS rom.

Could you make a fork of your LineageOS rom to LineageOS for microG rom?

Thanks with advance....
If you want to spoofing, visit the method provided in this thread to flash it yourself
SafetyNet
 
  • Like
Reactions: TorpedoJavi

virtualhjs

Member
Jan 19, 2015
16
3
Is there something wrong with OTA update? I got the update from 8/27/22, but after numerous attempts, the system seems to get stuck on the 8/20/22 version. When tapping install the system restarts in TWRP, a system is installed, restarts, but when I check I see that it is still at version 20-08-22. What can it be? Installation is done from above, no data cleaning, it doesn't make sense to erase everything and start over from scratch just to update is it? Another question, can OTA update damage something in the system? Something like drivers or specific things that maintain compatibility between Mi Max 2 and LineageOS 19 offered in this thread? Is it always worth keeping updated via OTA in our case?
 

HalifaxTe55

Senior Member
Mar 1, 2017
185
156
perth
Is there something wrong with OTA update? I got the update from 8/27/22, but after numerous attempts, the system seems to get stuck on the 8/20/22 version. When tapping install the system restarts in TWRP, a system is installed, restarts, but when I check I see that it is still at version 20-08-22. What can it be? Installation is done from above, no data cleaning, it doesn't make sense to erase everything and start over from scratch just to update is it? Another question, can OTA update damage something in the system? Something like drivers or specific things that maintain compatibility between Mi Max 2 and LineageOS 19 offered in this thread? Is it always worth keeping updated via OTA in our case?
I have never released a version of 0820, you probably have a test version installed. ota will not damage your system.
 

virtualhjs

Member
Jan 19, 2015
16
3
Yes it's true. Sorry for not detailing this earlier. In fact, I don't think I know how to check if the system is up to date or not. See the screenshot, is the version I have installed on the green or red line? See the other image in the update part, in the red line I believe it is the version I currently have (08/20), just below a version from the 08/27 (green line) that even after installing it is available to install and the date on the red line it doesn't change, it's always at 08/20, on this screen it doesn't seem to show that it's updated. Confused. Any help to understand all this I would be grateful.
 

Attachments

  • Polish_20220901_132210475.png
    Polish_20220901_132210475.png
    191.6 KB · Views: 29
  • Polish_20220901_132335781.png
    Polish_20220901_132335781.png
    109.3 KB · Views: 31

HalifaxTe55

Senior Member
Mar 1, 2017
185
156
perth
Yes it's true. Sorry for not detailing this earlier. In fact, I don't think I know how to check if the system is up to date or not. See the screenshot, is the version I have installed on the green or red line? See the other image in the update part, in the red line I believe it is the version I currently have (08/20), just below a version from the 08/27 (green line) that even after installing it is available to install and the date on the red line it doesn't change, it's always at 08/20, on this screen it doesn't seem to show that it's updated. Confused. Any help to understand all this I would be grateful.
Ignore dates on red line.
 
  • Like
Reactions: virtualhjs

virtualhjs

Member
Jan 19, 2015
16
3
Will be fixed in the next update.
Hello, if you can check the functioning of the camera. I'm having problems with the bank's facial recognition application for example. The application takes a selfie, but the captured image is blurred, preventing recognition and the application not fully functioning. The native app is able to take a selfie with normal quality, but other apps are getting a blurry picture.
It took me a while to realize this, I had a big argument with the bank support claiming that the app was having a problem. But a while later, the same problem with another application from another bank, only this one shows the photo that was captured and says that it is not possible to identify it, asking to try again.
Grateful for the support to our dear Mi Max.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 15
    1654054452255.png

    LineageOS is a free, community-built, aftermarket firmware distribution of Android 14 (U), which is designed to increase performance and reliability over stock Android for your device.​

    Code:
    /*
    * Your warranty is now void.
    *
    * We are 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 us for messing up your device, we will laugh at you.
    *
    */

    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. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

    What's working?
    Fingerprint
    RIL
    Mobile data
    DT2W
    Camera
    GPS
    Lights
    Sound / vibration

    Known issues
    Front camera video

    Downloads
    LineageOS 21
    Recovery
    Stay tuned
    Device support channel

    Flashing Instructions:
    DO NOT use any custom recovery

    - Flash the recovery
    - fastboot wipe-super super_empty.img
    - Reboot to LOS recovery
    - Select `Factory reset" --> "Format data/factory reset`. You phone should say that /data, /cache, and /metadata have been formatted.
    - Go back to main menu and select "Apply update" --> "Apply from ADB"
    - Connect your phone to a computer
    - Run `adb sideload rom_file_name.zip` in your cmd/powershell/terminal and wait until it finishes
    - Reboot and enjoy

    Reporting Bugs
    • DO NOT Report bugs if you're running a custom kernel or you installed Magisk module
    • 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.)
    If you like my work, consider a donation! MY PAYPAL

    Contributors

    me-cafebabe
    8
    Changelog for Android 14( LoS 21.0)
    February 15

    • Merged february security patch
    • New boot animation
    • Fixed some bugs regarding downloading files
    • Kernel upstreamed to 4.19.306
    • Other minor issues fixes

    January 15
    • Merged January security patch
    • Fixed DT2W issue
    • Add OTA support
    • Kernel upstreamed to 4.19.303

    December 31
    • Initial Android 14

    ===================================

    Changelog for Android 13( LoS 20.0)
    November 2

    • Merged october security patch
    • Based on new kernel 4.19
    •(los20 has been discontinued, 21 will be released next )

    September 9
    • Merged July security patch
    • Update Chromium Webview to 117.0.5938.60
    • Automatic translation import

    July 9
    • Merged July security patch
    • Fixed regulator reference section mismatch
    • Fix format zero-ed out SD card
    • Update Chromium Webview to 114.0.5735.196
    • Add additional NTP server for China region

    June 25
    • Merged June security patch
    • Android 13 QPR3
    • Update IMS related blobs to LA.UM.9.6.3.r1-06200-89xx.0
    • Build Lineage Health HAL
    • Bring back the hardware key and lights

    May 5
    • Merged May security patch
    • Fixed FMRadio crash
    • Fixed x25 socket not accept on connect
    • Simplified Build Number information
    • Fix potential issues with power
    • Backport network related patches from 4.14
    • Other minor issues fixes

    April 17
    • Merged April security patch
    • Add back FMRadio
    • Other minor issues fixes

    March 20
    • Merged March security patch
    • March 2023 Quarterly Platform Release (QPR2)
    • Use AOSP aptX/aptX HD

    February 13
    • Merged February security patch
    • Pass CTS/Play Integrity by default under non-root
    • Switch back to release-keys tag
    • All system apps support Android 13 dynamic Themed icons
    • Fix call echo for some users (untested)
    • Fixed f2fs scanning NAT block infinite loop issue
    • Other minor issues fixes

    January 09 (2023)
    • Merged January security patch
    • Fixed screen recording issue
    • Fixed USB dac
    • Update keymaster to V4
    • Kernel upstreamed to 4.9.337
    • Updated to the latest mainline exFAT driver

    December 14 (2022)
    • Fixed the issue that the screen cannot be turned off
    • Fixed an issue where audio was blocked during a call for some users
    • Other minor issues fixes

    December 10
    • Merge Android 13 QPR1
    • Merged December security patch
    • Enable LLVM Polly optimizer for kernel
    • QPR1 new media player
    • Enable compressed APEX
    • Fix undefined behavior in bit shift for AUDIT_BIT
    • Updated to the latest mainline exFAT driver
    • Kernel upstreamed to 4.9.335
    • More performance improvements
    • Other minor issues fixes

    November 09
    • Merged November security patch
    • Migrate to QSSI build (Recommended to wipe the vendor partition before flashing)
    • Update Graphics from LA.UM.10.6.2.r1-01600-89xx.0
    • Fixed LQI recording
    • Fix BUG when iput after ocfs2_mknod fails
    • Fix initial connector audio value
    • Remove some unnecessary configuration and optimize rom size
    • Kernel upstreamed to 4.9.332
    • Other minor issues fixes

    October 19
    • Fixed picture and Night Light flickering
    • Fixed Jelly browser storage permission
    • Update aptX from raven
    • Update USB configure from LA.VENDOR.1.0.r1-17200-WAIPIO.QSSI13.0

    October 08
    • Fixed bluetooth calling
    • Restoring the Jelly browser (Please flash gapps in advance instead)

    October 06
    • Merged October security patch
    • Temporarily use DuckDuckGo instead of Jelly browser (because permission problem)
    • Upstreamed Pixel power HAL to the latest android 13 tag
    • Fixed SD card mount issue for exFAT filesystem
    • Added OTA support
    • Update kernel to 4.9.330

    September 26
    • Fixed fingerprint issue
    • Fixed no network connection

    September 25
    • Initial Android 13

    ===================================

    Changelog for Android 12.1( LoS 19.1)
    October 11

    - Merged October security patch
    - Discontinued, no follow-up maintenance

    Changelog for Android 12.1( LoS 19.1)
    September 24

    - Added Singapore network support
    - Enable new Power implementation
    - Kernel upstreamed to 4.9.329
    - Synced latest LineageOS sources

    September 11
    - Merged September security patch
    - Fixed an issue where goodix fingerprints could not be deleted
    - Fixed refcount leak
    - Use navbar by default
    - Merged LA.UM.10.6.2.r1-02500-89xx.0 tags
    - Kernel upstreamed to 4.9.327

    August 28
    - Fixed Bluetooth calling issues
    - Fixed some user sensors issues
    - Fixed Ok Google functionality
    - Added Brazil Vivo VoLTE support
    - Kernel upstreamed to 4.9.326

    August 10
    - Merged August security patch
    - Added JIO carrier support
    - Update some blobs from FP
    - Updated media codec

    July 30
    - Fixed call speaker volume is too low
    - Fixed an issue with low speed adapter charging
    - Added WireGuard
    - Increase wifi scan results
    - Updated wifi stack (LA.UM.9.6.3.r1-06200-89xx.0)
    - Updated some blobs (LA.UM.9.6.3.r1-06200-89xx.0)
    - Update Kernel to 4.9.325

    July 13
    - Merge July security patch
    - Fixed an issues with intermittent calls
    - Updated aptX blobs
    - Kernel upstreamed to 4.9.323

    June 29
    - Switch to enforcing
    - Update DRM to v 1.4
    - Kernel: Merge tag: LA.UM.10.6.2.r1-02200-89xx.0
    - Enable LTO Optimize the kernel
    - Enable lz4 compression zram
    - Turn off volte notification by default

    June 24
    - Fixed notification LED
    - Add hardware keys backlight

    Note:
    You can update it directly in Settings/System/Updater.

    June 23
    - Add in-system OTA support ➤Screenshost
    - Re-enable hardware keys

    Note: Needs wipe system, vendor to flash in.

    June 21
    - Fixed Auto brightness
    - Fixed Dirac backend
    - Fixed Google recorder
    - Add more Dirac presets
    - Update Graphics stack to LA.UM.10.6.2.r1-1900-89xx.0 (thanks zeelog)
    - Update Vulkan driver to latest
    - Update vendor security peach level
    - Update Chinese translation
    - Synced kernel with latest AOSP 4.9.319

    June 17
    - Fixed IR blaster

    June 14
    - June Security Patch
    - Fixed fpc fingerprint
    - Fixed fast charging

    June 10
    - Enable userdata partition encryption
    - Fixed Microphone issue
    - Fixed WIFi connection issue
    - Update kernel to 4.9.317

    June 01
    - Synced latest LineageOS sources as of 30 May 2022
    - Fixed HeadsUp notifications from previous release
    - Add system-wide rounded corners
    - Fix Dirac switch
    - Add Game Space support (App section)
    - Add support for repainter app
    - Fix user avatar
    - Default gesture navigation, this is not a bug
    - Debug version, many functions are enabled by default, if you mind, wait for the next version
    4
    2023/12/31
    Changelog:
    • Initial Android 14
    4
    Changelog for Android 13( LoS 20.0)
    October 19

    - Fixed picture and Night Light flickering
    - Fixed Jelly browser storage permission
    - Update aptX from raven
    - Update USB configure from LA.VENDOR.1.0.r1-17200-WAIPIO.QSSI13.0
    4
    2023/02/13
    Changelog:

    • Merged February security patch
    • Pass CTS/Play Integrity by default under non-root
    • Switch back to release-keys tag
    • All system apps support Android 13 dynamic Themed icons
    • Fix call echo for some users (untested)
    • Fixed f2fs scanning NAT block infinite loop issue
    • Other minor issues fixes