MIUI 14 MIUI 14 STABLE RELEASE


Status
Not open for further replies.
mobileman88 said:
Would moving from a weekly based on Miui13 A12 to Miui14 A13 Stable be considered downgrading? Since both Miui and Android will be of a later version?
Click to expand...
Yes...

Weekly MIUI 13 (Xeu) to Stable MIUI 14 (Xeu) would be a downgrade.

Data wipe is recommended.

--
Sent from my Mi 11 Ultra (star)
 
donmarkoni said:
Yeah, that's the reason why I asked... You are telling everybody they should format data, but I did dirty flash and everything is working fine.
Click to expand...
"Working fine" as far as you can tell?
There are 2 main reasons we insist on clean flashing:
1) It may not even boot due to potentially older security patch level on the Xiaomi.eu ROM.
2) If it boots, the system is still misconfigured because the Global ROM system apps are not the same as the system apps we use. So if you get any crashes or unexpected behavior, you know what to do.
 
  • Like
Reactions: Einar, donmarkoni, gogocar62 and 1 other person
Igor Eisberg said:
"Working fine" as far as you can tell?
There are 2 main reasons we insist on clean flashing:
1) It may not even boot due to potentially older security patch level on the Xiaomi.eu ROM.
2) If it boots, the system is still misconfigured because the Global ROM system apps are not the same as the system apps we use. So if you get any crashes or unexpected behavior, you know what to do.
Click to expand...
Yes, as far as I can tell and I was not born yesterday. ;)
1. I'm aware.
2. If I get any unexpected behavior, I'll find out why and fix it, as I did for last 14 years.
As an ex Team Venom beta tester, I clean flashed 2, or maybe 3 times, when I tried really unstable custom ROM versions and knew there is probably no way back.

Cheers!
 
My all photos in dcim/camera directory are gone after update.

I have Xiaomi 12s ultra, which had 14.0.10 miui eu, then with this 14.0.12 update they are gone about 1.000 photos of 2 months. And they are not in recycle.

Restoring from google photos do not bring full size or raws.
 
kcorrea1 said:
Yes...

Weekly MIUI 13 (Xeu) to Stable MIUI 14 (Xeu) would be a downgrade.

Data wipe is recommended.

--
Sent from my Mi 11 Ultra (star)
Click to expand...
I back up my important stuff and did a dirty flash. Seems to be ok so far. Photos app process is the only one running with lots of cpu when I checked with adb. Hopefully that's temporary.
 
Hi, I have a bluetooth issue with my Redmi Note 10 Pro, with a bluetooth device connected, sounds come out of both phone and bluetooth device
I can't choose or nothing
It happens with most apps, only pure music apps work, I tried to click the audio output button from the dropdowwn menu but it just opens the mini player

Thanks in advance
 
Last edited:
donmarkoni said:
Yes, as far as I can tell and I was not born yesterday. ;)
1. I'm aware.
2. If I get any unexpected behavior, I'll find out why and fix it, as I did for last 14 years.
As an ex Team Venom beta tester, I clean flashed 2, or maybe 3 times, when I tried really unstable custom ROM versions and knew there is probably no way back.

Cheers!
Click to expand...
Sooo, why did you even ask here if you know better?
 
  • Like
  • Haha
Reactions: ov1lord, MeiGuddet, biscoot and 1 other person
I think I bricked my 12S pro. it is stucked in fastboot and it won't boot up in any other mode (pwr+vol up doesn't bring me in recovery)
Can sbd please help
 
SleepyAsh said:
I think I bricked my 12S pro. it is stucked in fastboot and it won't boot up in any other mode (pwr+vol up doesn't bring me in recovery)
Can sbd please help
Click to expand...
1) It's not related to this thread.
2) You did not say what you did to get it bricked.
3) If you can still boot to fastboot, then it's only a soft-brick, which is recoverable.
 
donmarkoni said:
To prove a point.
Click to expand...
More like to brag about how clever, supposedly, you are.
You've proven no point. We never said that it's absolutely impossible to dirty flash between different MIUI ROMs.
We said that it's what you're always supposed to do when switching to a different ROM, because it's an ultimate remedy for everything that could go wrong if dirty flashing. So yes, I'm "telling everybody they should format data", and it's non-negotiable. It's simply correct.
This discussion is over.
 
  • Like
Reactions: ov1lord, hasan41, Imtuga and 6 others
Igor Eisberg said:
More like to brag about how clever, supposedly, you are.
You've proven no point. We never said that it's absolutely impossible to dirty flash between different MIUI ROMs.
We said that it's what you're always supposed to do when switching to a different ROM, because it's an ultimate remedy for everything that could go wrong if dirty flashing. So yes, I'm "telling everybody they should format data", and it's non-negotiable. It's simply correct.
This discussion is over.
Click to expand...
Well, I have the bragging rights. :cool:
But, obviously, I come from some different time, when users talked with developers, developers explained stuff, users were willing to learn, to test, to try to fix stuff... Developers respected users, as users were not the mindless bunch.
Now, different times have come... Sad times... :emoji_confused:
 
  • Like
Reactions: Ekksman and Smaritz
donmarkoni said:
Well, I have the bragging rights. :cool:
But, obviously, I come from some different time, when users talked with developers, developers explained stuff, users were willing to learn, to test, to try to fix stuff... Developers respected users, as users were not the mindless bunch.
Now, different times have come... Sad times... :emoji_confused:
Click to expand...
It's not about developers respecting users when an user acts like he's the most clever person in the world. The developers have been working on this since the beginning and I never had any issues with them and you come here as some person that suddenly knows more than developers themselves. It's just sad that people like you even exist in this world.
 
  • Like
Reactions: ov1lord, MeiGuddet, biscoot and 2 others
donmarkoni said:
Well, I have the bragging rights. :cool:
But, obviously, I come from some different time, when users talked with developers, developers explained stuff, users were willing to learn, to test, to try to fix stuff... Developers respected users, as users were not the mindless bunch.
Now, different times have come... Sad times... :emoji_confused:
Click to expand...
In addition to what Spookie said, this forum is not a developers' community, and we are not teachers.
Most of our users are just that - users - and they just want to use the ROMs in a stable state, not to read pages upon pages of technical jargon.
You might be willing to go into the technical and complicate things, but again, here is not XDA.
 
  • Like
Reactions: ov1lord, MeiGuddet, Spookie and 4 others
SpookieGames said:
It's not about developers respecting users when an user acts like he's the most clever person in the world. The developers have been working on this since the beginning and I never had any issues with them and you come here as some person that suddenly knows more than developers themselves. It's just sad that people like you even exist in this world.
Click to expand...
I don't have issue with developers. I'm just showing another way, for those not bling to see.
And... Your perception of me is who I am. I don't mind.
 
Igor Eisberg said:
In addition to what Spookie said, this forum is not a developers' community, and we are not teachers.
Most of our users are just that - users - and they just want to use the ROMs in a stable state, not to read pages upon pages of technical jargon.
You might be willing to go into the technical and complicate things, but again, here is not XDA.
Click to expand...
Well, yeah... My expectations were wrong... I'll avoid posting here and stick to XDA. Although, XDA is not what it used to be.
 
I can not open messages on Diting, I clear cache data,what should I do? How to use it .. it crash couple days after using ROM.
Clean install. Data format. Everything.
 

Attachments

  • Screenshot_2023-04-11-01-23-28-554_com.miui.home.jpg
    Screenshot_2023-04-11-01-23-28-554_com.miui.home.jpg
    817.8 KB · Views: 193
Last edited:
Igor Eisberg said:
What is the crash summary?
Click to expand...
Code: 
java.lang.ClassCastException: android.widget.LinearLayout cannot be cast to android.view.ViewStub
    at com.android.mms.ui.ConversationListItem.a(Unknown Source:556)
    at i.b.c.a0.s2.a(Unknown Source:253)
    at i.b.c.a0.f5.b(Unknown Source:14)
    at i.b.c.a0.u6.b(Unknown Source:50)
    at androidx.recyclerview.widget.RecyclerView$f.a(Unknown Source:26)
    at androidx.recyclerview.widget.RecyclerView$u.a(Unknown Source:1142)
    at androidx.recyclerview.widget.LinearLayoutManager$c.a(Unknown Source:58)
    at androidx.recyclerview.widget.LinearLayoutManager.a(Unknown Source:0)
    at androidx.recyclerview.widget.LinearLayoutManager.a(Unknown Source:44)
    at androidx.recyclerview.widget.LinearLayoutManager.c(Unknown Source:793)
    at androidx.recyclerview.widget.RecyclerView.f(Unknown Source:38)
    at androidx.recyclerview.widget.RecyclerView.d(Unknown Source:40)
    at androidx.recyclerview.widget.RecyclerView.onLayout(Unknown Source:5)
    at com.android.mms.util.EditableListViewV2.onLayout(Unknown Source:7)
    at android.view.View.layout(Unknown Source:81)
    at android.view.ViewGroup.layout(Unknown Source:21)
    at miuix.springback.view.SpringBackLayout.onLayout(Unknown Source:40)
    at android.view.View.layout(Unknown Source:81)
    at android.view.ViewGroup.layout(Unknown Source:21)
    at android.widget.FrameLayout.layoutChildren(Unknown Source:160)
    at android.widget.FrameLayout.onLayout(Unknown Source:6)
    at o.n.d.a.onLayout(Unknown Source:0)
    at miuix.nestedheader.widget.NestedHeaderLayout.onLayout(Unknown Source:0)
    at android.view.View.layout(Unknown Source:81)
    at android.view.ViewGroup.layout(Unknown Source:21)
    at android.widget.FrameLayout.layoutChildren(Unknown Source:160)
    at android.widget.FrameLayout.onLayout(Unknown Source:6)
    at android.view.View.layout(Unknown Source:81)
    at android.view.ViewGroup.layout(Unknown Source:21)
    at android.widget.FrameLayout.layoutChildren(Unknown Source:160)
    at android.widget.FrameLayout.onLayout(Unknown Source:6)
    at android.view.View.layout(Unknown Source:81)
    at android.view.ViewGroup.layout(Unknown Source:21)
    at android.widget.FrameLayout.layoutChildren(Unknown Source:160)
    at android.widget.FrameLayout.onLayout(Unknown Source:6)
    at miuix.appcompat.internal.app.widget.ActionBarOverlayLayout.onLayout(Unknown Source:0)
    at android.view.View.layout(Unknown Source:81)
    at android.view.ViewGroup.layout(Unknown Source:21)
    at android.widget.FrameLayout.layoutChildren(Unknown Source:160)
    at android.widget.FrameLayout.onLayout(Unknown Source:6)
    at android.view.View.layout(Unknown Source:81)
    at android.view.ViewGroup.layout(Unknown Source:21)
    at android.widget.LinearLayout.setChildFrame(Unknown Source:4)
    at android.widget.LinearLayout.layoutVertical(Unknown Source:184)
    at android.widget.LinearLayout.onLayout(Unknown Source:5)
    at android.view.View.layout(Unknown Source:81)
    at android.view.ViewGroup.layout(Unknown Source:21)
    at android.widget.FrameLayout.layoutChildren(Unknown Source:160)
    at android.widget.FrameLayout.onLayout(Unknown Source:6)
    at com.android.internal.policy.DecorView.onLayout(Unknown Source:0)
    at android.view.View.layout(Unknown Source:81)
    at android.view.ViewGroup.layout(Unknown Source:21)
    at android.view.ViewRootImpl.performLayout(Unknown Source:32)
    at android.view.ViewRootImpl.performTraversals(Unknown Source:2580)
    at android.view.ViewRootImpl.doTraversal(Unknown Source:36)
    at android.view.ViewRootImpl$TraversalRunnable.run(Unknown Source:7)
    at android.view.Choreographer$CallbackRecord.run(Unknown Source:20)
    at android.view.Choreographer$CallbackRecord.run(Unknown Source:20)
    at android.view.Choreographer.doCallbacks(Unknown Source:110)
    at android.view.Choreographer.doFrame(Unknown Source:524)
    at android.view.Choreographer$FrameDisplayEventReceiver.run(Unknown Source:11)
    at android.os.Handler.handleCallback(Unknown Source:2)
    at android.os.Handler.dispatchMessage(Unknown Source:4)
    at android.os.Looper.loopOnce(Unknown Source:182)
    at android.os.Looper.loop(Unknown Source:82)
    at android.app.ActivityThread.main(Unknown Source:123)
    at java.lang.reflect.Method.invoke(Native Method)
    at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(Unknown Source:11)
    at com.android.internal.os.ZygoteInit.main(Unknown Source:312)
 
JosepAlbert95 said:
Any feedback onew F3 build 14.0.6? I'm still on stable MIUI 13 waiting for MIUI 14 notifications/Safety net issuea I read about in last pages to be fixed
Click to expand...
In my case notifications issue is fixed. Also OK Google works when phone is locked. I didnt format from miui 13 to 14. This build should be the first safe update for us.
 
  • Like
Reactions: qu4k3r
Status
Not open for further replies.

Similar threads

ingbrzy
  • Sticky
HyperOS 2.0 HyperOS 2.0 STABLE RELEASE
Replies
926
Views
381K
HyperOS
Samac
Samac
ingbrzy
  • Locked
HyperOS 1.0 24.7.28 (Final)
Replies
292
Views
338K
HyperOS
Igor Eisberg
Igor Eisberg
ingbrzy
  • Locked
HyperOS 1.0 24.7.1
Replies
54
Views
44K
HyperOS
Mistery88
M
ingbrzy
  • Locked
HyperOS 1.0 24.7.22/25/26
Replies
51
Views
45K
HyperOS
Ahaba
A
ingbrzy
  • Locked
HyperOS 1.0 24.7.15/17
Replies
87
Views
54K
HyperOS
KGVER
KGVER
Top Bottom
Back