[ROM]LineageOS 20 - Xiaomi Mi 8

Search This thread

matrix2012xman

Senior Member
Feb 25, 2015
128
31
40
cairo
Xiaomi Mi 8
Everything is more than ok but sound may need little bit enhancement
But you deserve more than thanks for your work ❤️
@infrag
 

Attachments

  • screen-20230125-183322.mp4
    22.4 MB · Views: 0
  • Screenshot_20230125-191112_SafetyNet Test.png
    Screenshot_20230125-191112_SafetyNet Test.png
    102.7 KB · Views: 128
Last edited:

jwit

Member
Jan 26, 2023
6
2
Flashing clean, I am in a noisy place, the sound from the microphone is broadcast to the upper speaker, it is impossible to talk

Hello, a few days ago updated to LOS 20 from 19.1. All working so far, main problem I found was that during calls it puts in the earpiece all ambient noise, all the background noise into my ear, it's very stressful, at least for me. Anyone noticed this?

I flash my Mi 8 international first to LOS 20 (lineage-20.0-20230119-nightly-dipper-signed.zip) following the instructions on
and

(xiaomi firmware update first and did a complete wipe/factory reset)

But I am still experiencing the microphone problem as described above, ie sound picked up by the microphone is broadcasted via the speaker.

Shouldn't this problem be fixed already?
 
  • Like
Reactions: Flaba

Mishi123

Member
Oct 4, 2014
5
1
There is something wrong in com.android.deskclock, I can't edit the alarm detailly, I think it work well in lineage-20.0-20230105-nightly-dipper-signed.zip, but after that something is broken in 20230112, 20230119, 20230126, and it also happend in google clock the same, the dropbox log is here:
Code:
Process: system_server
Subject: AlarmManager
Build: Xiaomi/dipper/dipper:8.1.0/OPM1.171019.011/V9.5.5.0.OEAMIFA:user/release-keys
Dropped-Count: 0

android.util.Log$TerribleFailure: Attempt to decrement existing alarm count 0 by 1 for uid 1000
    at android.util.Log.wtf(Log.java:315)
    at android.util.Slog.wtf(Slog.java:220)
    at com.android.server.alarm.AlarmManagerService.decrementAlarmCount(AlarmManagerService.java:5742)
    at com.android.server.alarm.AlarmManagerService.removeAlarmsInternalLocked(AlarmManagerService.java:4086)
    at com.android.server.alarm.AlarmManagerService.removeLocked(AlarmManagerService.java:4133)
    at com.android.server.alarm.AlarmManagerService.setImplLocked(AlarmManagerService.java:2336)
    at com.android.server.alarm.AlarmManagerService.setImpl(AlarmManagerService.java:2315)
    at com.android.server.alarm.AlarmManagerService$5.set(AlarmManagerService.java:2952)
    at android.app.AlarmManager.setImpl(AlarmManager.java:971)
    at android.app.AlarmManager.setImpl(AlarmManager.java:931)
    at android.app.AlarmManager.set(AlarmManager.java:859)
    at com.android.server.job.controllers.TimeController.updateAlarmWithListenerLocked(TimeController.java:383)
    at com.android.server.job.controllers.TimeController.setDeadlineExpiredAlarmLocked(TimeController.java:366)
    at com.android.server.job.controllers.TimeController.evaluateStateLocked(TimeController.java:164)
    at com.android.server.job.JobSchedulerService.evaluateControllerStatesLocked(JobSchedulerService.java:2558)
    at com.android.server.job.JobSchedulerService$ReadyJobQueueFunctor.accept(JobSchedulerService.java:2251)
    at com.android.server.job.JobSchedulerService$ReadyJobQueueFunctor.accept(JobSchedulerService.java:2240)
    at com.android.server.job.JobStore$JobSet.forEachJob(JobStore.java:1392)
    at com.android.server.job.JobStore.forEachJob(JobStore.java:321)
    at com.android.server.job.JobSchedulerService.queueReadyJobsForExecutionLocked(JobSchedulerService.java:2227)
    at com.android.server.job.JobSchedulerService.-$$Nest$mqueueReadyJobsForExecutionLocked(Unknown Source:0)
    at com.android.server.job.JobSchedulerService$JobHandler.handleMessage(JobSchedulerService.java:2102)
    at android.os.Handler.dispatchMessage(Handler.java:106)
    at android.os.Looper.loopOnce(Looper.java:201)
    at android.os.Looper.loop(Looper.java:288)
    at com.android.server.SystemServer.run(SystemServer.java:965)
    at com.android.server.SystemServer.main(SystemServer.java:650)
    at java.lang.reflect.Method.invoke(Native Method)
    at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548)
    at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:914)
 

ntnp

New member
Jan 29, 2023
1
0
Hey! I have an issue where I'm not getting any sound at all in calls, only speakerphone works. Bluetooth is off so it's not picking up anything there.

I tried doing a clean reinstall (format partitions & updated firmware), but the problem persists. Any ideas?
 
Last edited:

asdfuc

Member
Sep 8, 2013
40
8
How to make my mi8 pass safety net if I do not use gapps? After 2 succesful years with LOS, now I need to make my banking apps work with this phone.
 

mkz14

Senior Member
Feb 17, 2011
288
68
Is there any DAMN way to make "ok, google" working in LineageOS?

How to make my mi8 pass safety net if I do not use gapps? After 2 succesful years with LOS, now I need to make my banking apps work with this phone.
as far as I know you can't pass safetynet without having gplay services

just install magisk, install hide props module and safetynet fix, and you will be able to use banking apps and download Netflix.
 
  • Like
Reactions: asdfuc

jwit

Member
Jan 26, 2023
6
2
I flash my Mi 8 international first to LOS 20 (lineage-20.0-20230119-nightly-dipper-signed.zip) following the instructions on
and

(xiaomi firmware update first and did a complete wipe/factory reset)

But I am still experiencing the microphone problem as described above, ie sound picked up by the microphone is broadcasted via the speaker.

Shouldn't this problem be fixed already?
Today I flashed my backup Mi8 phone straight from LineageOS 16 to LineageOS 20 by first flashing the firmware update (following https://wiki.lineageos.org/devices/dipper/fw_update ) and then LOS 20 (following https://wiki.lineageos.org/devices/dipper/install )

I am experiencing the microphone problem on this phone too. When making a phone call sound is broadcasted via the speaker creating high pitched sounds (feedback loop), making it impossible to have a conversation.

Please advice on how to fix this problem.
 

haxnhaxn

Member
Dec 6, 2011
34
8

G A S T

Senior Member
Apr 20, 2018
263
109
Xiaomi Mi 4
Samsung Galaxy S6
Thx. But found it already.
The Problem here is that that when I install TWRP 3.7.0-12.1 V2 at first, I will not be able to Upgrade to LOS 19.1, because it won't decrypt the existing LOS 18.1 Installation any more.
When I perform the Upgdate to LOS 19.1 with my older TWRP 3.7.0_9-0, it won't decrypt vice versa on the new er LOS-Installation and I can't replace TWRP. This is bogus.
 
Last edited:

haxnhaxn

Member
Dec 6, 2011
34
8
Unfortunately, I know too few about the en/decryption part. I'm not sure if you can upgrade to Android 12 without format data and keep file access in twrp.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 15
    Please note: I no longer maintain this ROM as my phone screen has cracked and I've moved on to a different device. Bgncm will probably continue to maintain it for mi8 as its similar to his other devices. Thanks for those that supported in the past and perhaps we will meet again in the future on a different device.
    8
    Please note: I no longer maintain this ROM as my phone screen has cracked and I've moved on to a different device. Bgncm will probably continue to maintain it for mi8 as its similar to his other devices. Thanks for those that supported in the past and perhaps we will meet again in the future on a different device.
    Hi @infrag

    Thank you for having supported this device for so many years!

    This is something that is not common these days and highly appreciated.

    Please share the information for which phone(s) you are the maintainer, so that we people know which phone(s) to favor.

    May God bless you, guide you and reward you for contributing to sustainability and enjoyment!
    6
    Last year I figured out the cause of the issue and I informed Qualcomm and Linux kernel maintainers, I didn't want to keep you folk waiting for them to fix it so I'd made a temporary fix.
    It seems that they have fixed it in both the upstream kernel and the CLA audio-kernel now, but they didn't backport it to a sdm845 tag!
    I've made an experimental build with the required fixes backported. If all goes well, I'll submit a patch to Lineage Gerrit.
    I've attached the build below, you'll have to flash it as a boot.img via recovery or fastboot, let me know if it fixes the problem.
    I haven't had much time to test it, so make sure you're on lineage-20.0-20230216.
    3
    Just a message to say thanks to the all maintainers for keeping that devices alive.

    It's the first time I kept a smartphone THAT long (5 years?) and I hope it will continue as I'm not confident enough to try to do build Lineage myself.
    1
    Hi there, after an update to Lineage OS 20, the high pitch noise problem during calls is back. Everything is ok when I call with signal or telegram, but the high pitch noise starts when I do regular calls. Anybody experiencing the same? The discussion of the problem from March 2022 is here:

    https://forum.xda-developers.com/t/...eageos-18-1-xiaomi-mi-8.3973189/post-86537587
    Last time, I made a patch to change the audio mixer control behaviors back, it probably got lost during a recent merge. It wasn't meant to be a permanent solution anyways.
    I can try updating our device's mixer file to fix the noise problem this time.
    The actual cause of this problem is that the ASoC controls weren't documented well and for some reason the levels in mixer files of most devices don't match the actual range in the Qualcomm codec.
    The kernel used to allow the incorrect ranges before 2022, so it used to work, either mixer files have to be updated or the Qualcomm codec has to be modified in upstream kernel.

    EDIT: Clarification.
  • 32
    Please note: I no longer maintain this ROM as my phone screen has cracked and I've moved on to a different device. Bgncm will probably continue to maintain it for mi8 as its similar to his other devices. Thanks for those that supported in the past and perhaps we will meet again in the future on a different device.

    LineageOS is a free, community built, aftermarket firmware distribution of Android 12, 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: https://github.com/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.



    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
    Format /system, /data and /cache
    Install MIUI firmware
    Install LineageOS zip package
    Install 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!
    15
    Please note: I no longer maintain this ROM as my phone screen has cracked and I've moved on to a different device. Bgncm will probably continue to maintain it for mi8 as its similar to his other devices. Thanks for those that supported in the past and perhaps we will meet again in the future on a different device.
    11
    Dear @infrag

    I have a big smile on my face ... because I see that the NFC change was merged a couple of hours ago.


    Was this the merge you were waiting for?
    Yes. NFC should now work fine in official builds so now can be promoted to 19.1 builds once accepted. I've lodged the request so should hopefully not be too far away.
    8
    Lineage-19.1 builds in OP.
    8
    @infrag thanks a ton for spotting the changes.
    Please thank @UnluckyPoet also as he did most of the work.