MULTI 4.7.18


Status
Not open for further replies.
Well, I hope they put 'Power Saving' mode/profile back in. Having only two modes doesn't make much sense after all.
 
The question is if they are well optimized. If they are, two could suffice. We will see. I do not think they will put three modes back.
 
Hi!! sorry for my bad english but I have a question: mako rom should be updated as usual? Because I'm in JB and this is KK version. I usually make a wipe cache / wipe dalvik cache then flash miui rom and kernel. I think that is necessary flash new radio (i'm in .84 )first of all but I'm not sure. So I think: wipe cache/dalvik cache, flash kk radio, flash rom, flash gapps, flash kernel, right?
 
The question is if they are well optimized. If they are, two could suffice. We will see. I do not think they will put three modes back.

Like I said before, from a logical standpoint, there have to be 3 different profiles.

1. Power Saving -> clocks are mostly low and never switch to highest rates (50-75% max.), switching to higher rates late
2. Normal/Balanced -> clocks switch between low and high, try to stay low but switch high when needed
3. Performance -> clocks stay (mostly) high, lower rates only after a few idle seconds

That's roughly what should happen. Do you see my point?
 
Last edited:
Like I said before, from a logical standpoint, there have to be 3 different profiles.

1. Power Saving -> clocks are mostly low and never switch to highest rates (50-75% max.), switching to higher rates late
2. Normal/Balanced -> clocks switch between low and high, try to stay low but switch high when needed
3. Performance -> clocks stay (mostly) high, lower rates only after a few idle seconds

That's roughly what should happen. Do you see my point?

That's how it has been till now.
But actually there's no logic to have three modes. What is logical about that?
If there are two optimized modes, there's no need for the third one.

One mode for light to medium use.
Second mode for medium to high.

The point is to have an optimal performance plus good battery life, that's all. It really doesn't matter how Xiaomi achieve that.

I read some negative comments before even anyone tried and check the impact of this "only-two-mode" on battery. If it's rubbish then we can discuss it.
 
Last edited:
  • Like
Reactions: ingbrzy
That's two different strategies to the same problem.

I prefer the diversity of three profiles. For the reasons stated above.
 
Last edited:
Acid,
I have reinstalled the rom but I didn't get back the Mikey and MiTransfer apps.

Sent from my Mi2S using Tapatalk
 
grab the two packages from the rom zip and install them.. much better than reinstalling the whole rom to get back two apps!!

edit: you can find them in data/miui/apps
 
  • Like
Reactions: graw2
Hi,

I'm using SGS2 and updated my MIUI to 4.7.18. I also use Mi-tools.

having some issue with network/wifi/carrier logo keep disappearing from status bar. if i change the status bar theme, it'll come back for few hours then disappear again.

kinda annoying. anyone else having this issue?
 
I've read on the german forum that the audio when recording video is supposed to be terrible with every version but the latest stable. Any thoughts or experience on that?
 
  • Like
Reactions: sprint82
with the MIUI 4.7.11 I had strange sound using the camera app to make a video. I sounds like under water, like a faulty sound codec (too much compression).

Can anyone confirm if the same issue is still present on 4.7.18? On the newest stable rom MI3W_KXDCNBE18.0 which I'm testing right now, the recorded sound is totally normal.

I don't know why, because the DEV roms are based on a stable, isn't it?
 
I have an other problem. I paid for real drift car racing game but I cannot play with this because of instant FC after start the game. Here is the bug report:

java.lang.Error: FATAL EXCEPTION [UnityMain]
Unity version : 4.5.2f1
Device model : Xiaomi MI 2S
Device fingerprint: Xiaomi/aries/aries:4.1.1/JRO03L/4.7.18:user/release-keys

Caused by: java.lang.Error: signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 00000050
Build fingerprint: 'Xiaomi/aries/aries:4.1.1/JRO03L/4.7.18:user/release-keys'
Revision: '0'
pid: 11957, tid: 11985, name: UnityMain >>> com.realdrift.sipon <<<
r0 6e2c1cb0 r1 00000000 r2 00000000 r3 00000002
r4 00000000 r5 00000003 r6 6e2c6dc4 r7 6e2bdc6c
r8 00000000 r9 03020100 sl 6e29c7a0 fp 00000000
ip 00000000 sp 6a8fa898 lr 6b82f429 pc 6b89ed72 cpsr 753a3831

at libsc-a3xx.0010ed72(Native Method)
at libsc-a3xx.000e0e25(Native Method)
at libsc-a3xx.000e67a3(Native Method)
at libsc-a3xx.000e6989(Native Method)
at libsc-a3xx.000a57f9(Native Method)
at libsc-a3xx.000a5bc9(Native Method)
at libsc-a3xx.000a5ee1(Native Method)
at libsc-a3xx.0009a297(Native Method)
at libsc-a3xx.0009c1d5(Native Method)
at libsc-a3xx.0009ba47(Native Method)
at libsc-a3xx.__link_shaders(__link_shaders:322)
at libGLESv2_adreno200.qgl2DrvAPI_glLinkProgram(qgl2DrvAPI_glLinkProgram:618)
at libGLESv2_adreno200.glLinkProgram(glLinkProgram:10)
at libunity.00387b48(Native Method)
at libunity.0038679c(Native Method)
at libunity.00386540(Native Method)
at libunity.001f61f0(Native Method)
at libunity.001f59e4(Native Method)
at libunity.0031e53c(Native Method)
at libunity.0032fbd4(Native Method)
at libunity.0032f820(Native Method)
at libunity.0032e4ec(Native Method)
at libunity.0032def4(Native Method)
at libunity.0032d648(Native Method)
at libunity.003301cc(Native Method)
at libunity.00301940(Native Method)
at libunity.00301c24(Native Method)
at libunity.002ec524(Native Method)
at libunity.0029cdf8(Native Method)
at libunity.0029a83c(Native Method)
at libunity.0029c404(Native Method)
at libunity.0029b638(Native Method)


Sent from my Mi2S using Tapatalk
 
In build.prop change debug.compositon.type=dyn to debug.compositon.type=gpu

And see if that helps.
 
  • Like
Reactions: graw2
hi, is there something for the HTC Sensation...

Sometimes we got Wifi turning-off. Maybe Kernel, i Dont know.
 
In build.prop change debug.compositon.type=dyn to debug.compositon.type=gpu

And see if that helps.
Thanks Acid,
I don't really understand. It seems it is deep water for me. Could you please explain to me what should I do how to do exactly.

Sent from my Mi2S using Tapatalk
 
Thanks Acid,
I don't really understand. It seems it is deep water for me. Could you please explain to me what should I do how to do exactly.

Sent from my Mi2S using Tapatalk

you have to edit the build.prop file you can find in /system in your phone
change the line acid suggested you..... you will need a root file explorer
 
  • Like
Reactions: graw2
you have to edit the build.prop file you can find in /system in your phone
change the line acid suggested you..... you will need a root file explorer
Thx a lot! I am checking...
I have root Explorer of course

Sent from my Mi2S using Tapatalk
 
Very good! I found the mentioned file in system folder and I found this line: debug.compositon.type=dyn
The question is how to modify and how to save. I opened with Root Explorer
 
Did you change your permission before edit? To read/write?

Verstuurd van mijn MI 2 met Tapatalk
 
Status
Not open for further replies.

Similar threads

Replies
103
Views
28K
  • Locked
HyperOS 1.0 24.3.4
Replies
150
Views
42K
  • Locked
HyperOS 1.0 24.2.26
Replies
161
Views
49K
Replies
259
Views
66K