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

[ROM][OFFICIAL] LineageOS 18.1 - Xiaomi Mi 8

Search This thread

Goalach

Senior Member
Nov 11, 2016
165
31
WTF....!!
Wipe cache and system
Flash ROM 29.5 and no more data.
Both SIM. @infrag

---------- Post added at 09:29 AM ---------- Previous post was at 09:10 AM ----------

Yes 100 Points
Restore full backup from 29.5 and still no data.
Tried SIM cards in another phone.
And...?
Both SIM cards dead.
WTF
How could it be ????
 

Barnir

Senior Member
Jan 13, 2016
192
49
Braga
Cant flash right from OTA Updater.. just a error without any code.. do we must have lineage recovery for this? orangefox does not work?
 

Goalach

Senior Member
Nov 11, 2016
165
31
Can anyone can tell me what happens?
I clean flashed version 29.5
Actually new is 6.2
Updates says 18.5
And no updates available.
 

Attachments

  • Screenshot_20200602-130106_Chrome.png
    Screenshot_20200602-130106_Chrome.png
    198.1 KB · Views: 213
  • Screenshot_20200602-130208_Updater.png
    Screenshot_20200602-130208_Updater.png
    73.2 KB · Views: 213

Goalach

Senior Member
Nov 11, 2016
165
31
Try to update manually

Thank you for this extremely qualified answer.

---------- Post added at 11:56 AM ---------- Previous post was at 11:39 AM ----------

I have already flashed manually and the problem still appears.

It is not a problem. Is that while the rom was compiling, there was the change of day.

It happens sometimes. It's always someone's turn. This time it's Dipper's turn.

And you have no problems with the SIM cards.?
Do you have two or one SIM?
 

Goalach

Senior Member
Nov 11, 2016
165
31
@infrag
I'm back from my carrier services.
Both SIM are defect.
Telephone is ok, but no data.
Next days I will get my new cards.
**** !!!
 

G A S T

Senior Member
Apr 20, 2018
220
97
Xiaomi Mi 4
Samsung Galaxy S6
@infrag
That's very disappointing. You are the maintainer of this ROM and could have reacted at least once.

I don't think that this is infrags fault, so stop immediately to blame him! Du hast wahrscheinlich selbst irgendwas verkackt bei deiner Installation...

Pls describe how you managed your Installation and plus the update and write me a PM if about it, if you want. Perhaps I can help yo to do it right.
 

infrag

Senior Member
Sep 3, 2008
1,628
4,376
Perth
In light of the last 2 pages of comments I've installed the second latest official build.
I then rebooted and checked for updates. It successfully showed and downloaded and then installed the 06/02 build.
I still have data. My phone still works like before. There is nothing showing in the logs that I can see that would be a concern.

So, If you have problems please provide logs or I more than likely cant help you.
 

infrag

Senior Member
Sep 3, 2008
1,628
4,376
Perth
@infrag I've downloaded LOS sources then edited Dialer package to change the CallRecordings source.
I've changed from "CallRecordings" to "Music/CallRecordings" the PUBLIC_DIRECTORY_NAME constant, that specifies the recordings pathname from /sdcard

[/code]

Hello
Thanks for your investigations into this.
Since these are official builds and there are other devs working on the dialer I wont be interfering with this. I can make a suggestion in team chat but thats about as far as I go as I dont have time to look at this particular problem right now.
My suggestion is to just wait till they have finalised their changes for this.
I wont be adding in device side changes that potentially need reverting a week or two later for official builds.
 

bartito

Inactive Recognized Developer
Dec 1, 2005
3,937
1,785
Hello
Thanks for your investigations into this.
Since these are official builds and there are other devs working on the dialer I wont be interfering with this. I can make a suggestion in team chat but thats about as far as I go as I dont have time to look at this particular problem right now.
My suggestion is to just wait till they have finalised their changes for this.
I wont be adding in device side changes that potentially need reverting a week or two later for official builds.

Thanks for your time. I appreciate too much.
I can wait until Dialer issue was solved by experts.
I just attach the Dialer.apk (in a zip file) from Apr 23 ROM, that is working well. Maybe can be useful to another user.
To install it, in recovery, replace the one at the attached zip by the one at /system/system/product/priv-app/Dialer then reboot

Code:
$> adb shell mount /system
$> adb push Dialer.apk /system/system/product/priv-app/Dialer/Dialer.apk
$> adb shell chmod 0644 /system/system/product/priv-app/Dialer/Dialer.apk
 

Attachments

  • Dialer.apk.zip
    6 MB · Views: 3
Last edited:
  • Like
Reactions: Adai0 and infrag

Goalach

Senior Member
Nov 11, 2016
165
31
I didn't want to attack anyone. I was just pretty annoyed at the moment. I've been installing ROM for over 10 years. This has never happened to me before. I downloaded and installed the ROM as normal. Of course, I don't have a log because I restored a Friday backup. Of course, something can happen during installation. I may have been sitting in a neutrino field. Or solar winds have disturbed the magnetic field. For me it was a faulty ROM at first. But it doesn't matter, both SIM cards will be replaced.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Seriously. The point of using a custom rom is to have a lighter os, more secure and updated code, but adapting all hardware functionality. I paid 400€ three years ago to have a top performing phone with good sound chip, and this phone does sound good. I have 300€ headphones that sound great out of this phone. Almost as good as my desktop amp. And Android provides a sound server, Audioflinger which can offload mp3/flac/vorbis/aac/wav decoding bypassing Android software mixer and resampler, if you listen to 44.1 Khz music, which is 99% of all mp3, as well as spotify and streaming services (except youtube on opus codec). If you switch offload and android mixer on your phone, you will find out it sounds better.

    As much as other hardware of this phone is configured to this rom and tree to make it work, like gps, sensors, speaker, touchscreen.. using binary blobs/drivers and updating caf and linux code in the kernel, Qualcomm provides some av-framework code into the rom that Xiaomi adapts to route offload and direct-pcm out, that I'd like to be ported to a custom rom like Los.

    The difficulty with this Qualcomm Caf patch, according to a kernel developer, is that if you patch it directly it may break compatibility with other devices in the rom repository. But a rom maintainer may build a local rom and if it works it could be merged upstream serving other devices aswell. However neither Los or PE has made it yet, so it must be hard.

    I am using MIUI actually and it does give me the same performance and battery level as custom roms, I run it tweaked with many xiaomi packages disabled so it runs fast and low memory usage, but I'd like to move to Los in the future, because I prefer a light customised rom.
    1
    I have trouble installing LineageOS rom. I tried multiple builds. I even tried a different rom PixelExperience.

    I wiped Dalvik/Cache/System/Data. and installed latest Xiaomi firmware, latest TWRP 3.5.2_9

    When I reboot, it doesn't even show boot animation. It shows MI logo, blanked once and reboot to TWRP.

    The only rom that work is the xiaomi official rom.

    Any clue what step am I missing? Thanks.

    "Important notes:
    * Required * firmware version must be based on MIUI *-based builds.
    Formatting data (all user data is wiped, including internal storage) is a must if MIUI was previously installed and device was encrypted."

    Formatting data.
    Not only wipe.
    1
    Has anyone ever installed @infrag 's kernel over LOS 18.1 official successfully? I've just moved from unofficial to official (to get security patches). I don't want root but do want Gpay and banking so need to hide the open bootloader, hence want to use the unofficial kernel (boot.img) linked in #1. If, however, I flash it to the /boot partition using official TWRP, the device doesn't boot but stalls at the mi logo. Boots ok with official kernel. What am I missing?
    Sorry havent updated kernel in a while.
    Can do a new build soon.
  • 70
    https%3A%2F%2Fimg.xda-cdn.com%2Fy-LtXHGCDBH0KxFw9MxWAPF3guk%3D%2Fhttp%253A%252F%252Fi.imgur.com%252F2okPze5.png

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

    Base source code is available in the LineageOS Github repo. And if you would like to contribute to the project, please visit our Gerrit Code Review.

    GPL compliance:


    Device tree source code: LineageOS/android_device_xiaomi_dipper
    Kernel source code: https://github.com/LineageOS/android_kernel_xiaomi_sdm845




    Compatibility:
    Compatible with Xiaomi Mi 8
    Builds are based off the Xiaomi's Android 10 firmware.
    Downloads:
    Official download links: https://download.lineageos.org/dipper

    Lineage 18.1 Kernels:
    15/06/2021

    Lineage 18.1 Unofficial builds:

    Build 15/06/2021



    Recommended firmware is latest MIUI stable firmware.



    Notice:
    No custom kernels are supported in this thread. Only stock kernel and official builds will be supported. No bug reports if that's not the case.

    Installation:
    Reboot to recovery (TWRP recovery for Mi 8)
    Format /system, /data and /cache
    Install MIUI firmware
    Install LineageOS zip package
    Install [optional] a Google Apps package of your choice

    Important notes:
    * Required * firmware version must be based on MIUI *-based builds.
    Formatting data (all user data is wiped, including internal storage) is a must if MIUI was previously installed and device was encrypted.

    All LineageOS team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
    19
    so the newest build 04/11/2019 uses Xiaomi Q blobs.
    Therefore it has some bugs:
    I havent got bluetooth audio working yet. Bluetooth calls seem to work fine though.
    Sound: Speaker works if you make a phone call first and switch to speaker during the call. After that everything else starts working.
    Edit: fixed. - GPS all satellites should show up now.
    Android Auto fixes probably havent been added yet to lineage but when anything shows up I'll add it.

    The reason this build took so long to be released is that Q radio blobs kept causing a reboot when data was used and switched to low power mode. I believe I have fixed this.


    https://drive.google.com/open?id=1bhurP2zIyZf93jJzSN1IBbiMBhmbSd_h

    Edit: Uploaded the correct build now. Also added in gps fix
    17
    Also fyi I'd hoped to have anther build up by now but since lineage has changed to 17.1 branches instead of 17.0 my build system is a bit of a mess. Waiting for all the repos to be updated to 17.1 before releasing anything. Hopefully it wont be too long...
    15
    18/12/2019 finally a working q build with q blobs and working audio.
    havent tested it a lot so any bugs let me know. There will be a v2 of the audio fix/change. This fix was just to make it work. :)
    14
    new build in OP.
    For android auto users unless I say otherwise I have not fixed your problem yet. :|