Search results

  1. U

    Post [ROM][10.0] crDroidAndroid v6.5 for Redmi Note 8/8T [Unified][Official]

    Hello, I don't know how to fix this but as workaround you could turn off VoLTE and fallback to 3G voice. Could I ask where are you from? I think this happens in some special cases.
  2. U

    Post [ROM][OFFICIAL][ginkgo][10] LineageOS 17.1 for Redmi Note 8 / 8T

    Wow, this ROM doesn't have a call log bug when using VoLTE. (Other AOSP based ROMs had an issue for me, caller's number always showing with my number when incoming call) Thank you so much to the dev.
  3. U

    Post [ROM][10.0] crDroidAndroid v6.5 for Redmi Note 8/8T [Unified][Official]

    I'm from South Korea (Carrier is LG U+). I think he or she is also Korean, because that post mentioned about the 010 number. All new mobile numbers in Korea are starting with 010
  4. U

    Post [ROM][10.0] crDroidAndroid v6.5 for Redmi Note 8/8T [Unified][Official]

    Same here. However it's not just crDroid's problem. I found this also happens with other custom roms Seems like an upstream issue (AOSP or LineageOS) Because of this I moved to Xiaomi.eu :(
  5. U

    Post Paranoid Android Quartz 4/5 DEV - Xiaomi Redmi Note 8/8T

    That's too bad. :( I'm sorry and hope you find another way to resolve it. In my case, even installing the first global firmware (V10.3.1.0 / MIUI10) and locking bootloader didn't solve my problem. So I had to unlock my bootloader again. When I install AOSP based ROMs, NFC works out of the box...
  6. U

    Post Paranoid Android Quartz 4/5 DEV - Xiaomi Redmi Note 8/8T

    I also went through the same situation as you and found a temp solution. 1 - Open /system/build.prop 2 - Find something like "ro.nfc.port=I2C" 3 - Edit that line to a comment or delete 4 - NFC should work fine after reboot Currently I'm using latest xiaomi.eu ROM and this worked for me. Hadn't...