9.8.29/9.9.3/9.9.6 - Last MIUI 10


Do you like this MIUI version?

  • Total voters
    594
Status
Not open for further replies.
marcel112 said:
I am curious what the next step will be:
are the devs waiting for release from china, or is there problem with building..

its not that I am asking when release, but just curious what's going on
Click to expand...
Waiting for official miui11 release. It is in closed beta at this point. We just have to be patient and wait a week more or two.
 
  • Like
Reactions: JimmyKowalski
stathis95194 said:
So the ROM flash successfully, boots, everything works ok except fingerprint?
Maybe it's a hardware issue? Can't think of anything else

Sent from my MI 8 UD using Tapatalk
Click to expand...

Yes, everything works fine except fingerprint.
Is not a hardware issue because i install again ( to check if its hardware) android 10 and the sensor works fine!
 
Today i flashed latest version of my Mi8... and it's working fine....... thank for this amazing MiuI
 
amit337 said:
I.m On 9.8.21 Build on my mi 8.... bt fingerprint scanner is works fine for me
Click to expand...

It works fine for me too, but then i decided to try the new android 10 but realized that i prefer miui 10 :)
After i did a clean flash the fingerprint stop worked, install android 10 and works, go back to miui and don´t work, everything works fine, but not the fingerprint, dont know why though
 
MagicPTUSER said:
Mi8
Click to expand...
Im using the latest build on my Mi8.... and my fingerpr
MagicPTUSER said:
It works fine for me too, but then i decided to try the new android 10 but realized that i prefer miui 10 :)
After i did a clean flash the fingerprint stop worked, install android 10 and works, go back to miui and don´t work, everything works fine, but not the fingerprint, dont know why though
Click to expand...
which rom did you flashed?
 
  • Like
Reactions: MagicPTUSER
I have the Redmi Note 7 Global HMNote7 and i have a question about this
"
ROMs for devices with locked bootloader:
  • Unlock your first bootloader here http://en.miui.com/unlock/
  • Install TWRP via Fastboot mode, then install our ROM
  • Code:
    fastboot flash recovery twrp.img
    fastboot boot twrp.img
  • TWRP Recovery Zip DOWNLOAD or TWRP.ME
  • FORMAT /data partition (NEVER wipe System or Persist!)
  • Copy our ROM to the internal storage
  • Install our ROM
  • Reboot
  • done
Installation via TWRP:
- Download zip to internal storage
- Updater - Menu (...) - Reboot to Recovery
- Install - Select zip
- Reboot
- Done
"

why cant i wipe system and/or persist?
 
xMarvin732 said:
I have the Redmi Note 7 Global HMNote7 and i have a question about this
"
ROMs for devices with locked bootloader:
  • Unlock your first bootloader here http://en.miui.com/unlock/
  • Install TWRP via Fastboot mode, then install our ROM
  • Code:
    fastboot flash recovery twrp.img
    fastboot boot twrp.img
  • TWRP Recovery Zip DOWNLOAD or TWRP.ME
  • FORMAT /data partition (NEVER wipe System or Persist!)
  • Copy our ROM to the internal storage
  • Install our ROM
  • Reboot
  • done
Installation via TWRP:
- Download zip to internal storage
- Updater - Menu (...) - Reboot to Recovery
- Install - Select zip
- Reboot
- Done
"

why cant i wipe system and/or persist?
Click to expand...

Format your data partition first then try again. Be sure to flash magisk right after flashing rom to keep your custom recovery.
 
I was able to get a log from my error!
Code: 
(...)
java.lang.RuntimeException: An error occurred while executing doInBackground()
    at android.os.AsyncTask$3.done(Unknown Source:27)
    at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:383)
    at java.util.concurrent.FutureTask.setException(FutureTask.java:252)
    at java.util.concurrent.FutureTask.run(FutureTask.java:271)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
    at java.lang.Thread.run(Thread.java:764)
Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'int com.android.internal.widget.VerifyCredentialResponse.getResponseCode()' on a null object reference
    at com.android.internal.widget.LockPatternUtils.verifyCredential(Unknown Source:13)
    at com.android.internal.widget.LockPatternUtils.verifyPassword(Unknown Source:8)
    at com.android.settings.eq.a(Unknown Source:0)
    at com.android.settings.ek.b(Unknown Source:8)
    at com.android.settings.ek.doInBackground(Unknown Source:2)
    at android.os.AsyncTask$2.call(Unknown Source:20)
    at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    ... 3 more
 
Last edited by a moderator:
MagicPTUSER said:
I was able to get a log from my error!
(...)
java.lang.RuntimeException: An error occurred while executing doInBackground()
at android.os.AsyncTask$3.done(Unknown Source:27)
at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:383)
at java.util.concurrent.FutureTask.setException(FutureTask.java:252)
at java.util.concurrent.FutureTask.run(FutureTask.java:271)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at java.lang.Thread.run(Thread.java:764)
Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'int com.android.internal.widget.VerifyCredentialResponse.getResponseCode()' on a null object reference
at com.android.internal.widget.LockPatternUtils.verifyCredential(Unknown Source:13)
at com.android.internal.widget.LockPatternUtils.verifyPassword(Unknown Source:8)
at com.android.settings.eq.a(Unknown Source:0)
at com.android.settings.ek.b(Unknown Source:8)
at com.android.settings.ek.doInBackground(Unknown Source:2)
at android.os.AsyncTask$2.call(Unknown Source:20)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
... 3 more
Click to expand...
Not trying to be captain obvious, but did you try removing all fingerprints and reregistering them?

Sent from my MI PAD 4 using Tapatalk
 
stathis95194 said:
Not trying to be captain obvious, but did you try removing all fingerprints and reregistering them?

Sent from my MI PAD 4 using Tapatalk
Click to expand...

Well, i did a clean flash, so all fingerprints registed was deleted!
And in my settings also says that the fingerprint unlock is deactivated ( cant activate because cant put my fingerprint)
 
MagicPTUSER said:
Well, i did a clean flash, so all fingerprints registed was deleted!
And in my settings also says that the fingerprint unlock is deactivated ( cant activate because cant put my fingerprint)
Click to expand...
Strange indeed. Ok one last suggestion in case it's a TWRP issue. Download the stock fastboot ROM and flash with Mi Flash Tool. Check if fingerprint works like this and then flash Xiaomi.eu

Sent from my MI PAD 4 using Tapatalk
 
  • Like
Reactions: MagicPTUSER and Ajoy30
I'm on a Mi 9 running the Android Q based 9.9.6 ROM.

For whatever reason, notifications are now completely broken for me since yesterday. Before they worked perfectly. Basically I get no notifications displayed on the lock screen or notification shade, also I don't get vibrations or sounds either, so I'm now missing all messages I receive in Whatsapp and other apps. If I go to Settings > Notifications, I can see the notifications there, but they don't get displayed.

Looking at logcat, this is clearly the problem:

Code: 
NotificationService: Cannot find enqueued record for key: 0|com.android.providers.downloads|1089|3:org.telegram.messenger:success|10069
09-14 12:21:36.182  1621  1621 I
NotificationService: Cannot find enqueued record for key: 0|com.android.providers.downloads|1089|3:com.google.android.apps.photos:success|10069

I get a similar line for all notifications. So clearly they are trying to be displayed, but then somehow the notification objects cannot be found.

The beginning of the PostNotificationRunnable runnable class looks something like this:

Code: 
protected class PostNotificationRunnable implements Runnable {
    private final String key;

    PostNotificationRunnable(String key) {
        this.key = key;
    }

    @Override
    public void run() {
        synchronized (mNotificationLock) {
            try {
                NotificationRecord r = null;
                int N = mEnqueuedNotifications.size();
                for (int i = 0; i < N; i++) {
                    final NotificationRecord enqueued = mEnqueuedNotifications.get(i);
                    if (Objects.equals(key, enqueued.getKey())) {
                        r = enqueued;
                        break;
                    }
                }
                if (r == null) {
                    Slog.i(TAG, "Cannot find enqueued record for key: " + key);
                    return;
                }

So clearly it's trying to display the notification but then can't find it and bails, so I never get to see or hear them.

Is anyone else seeing the same issue? Any idea how to fix it? I'm not sure how it broke, they were working fine the first week I used this ROM.
 
Status
Not open for further replies.

Similar threads

ingbrzy
  • Sticky
HyperOS 1.0 24.4.8/15
Replies
142
Views
30K
HyperOS
linuxghost
linuxghost
ingbrzy
  • Locked
HyperOS 1.0 24.3.25
Replies
169
Views
63K
HyperOS
c4rdix
C
ingbrzy
  • Locked
HyperOS 1.0 24.3.18
Replies
115
Views
42K
HyperOS
StrangerFox
S
ingbrzy
  • Locked
HyperOS 1.0 24.3.11
Replies
128
Views
44K
HyperOS
cyclonemax
C
ingbrzy
  • Locked
HyperOS 1.0 24.3.4
Replies
150
Views
46K
HyperOS
Kwanice
K
Top Bottom
Back