8.1.11 V2


Do you like this MIUI version?


  • Total voters
    267
Status
Not open for further replies.

tutek

Members
Jun 15, 2017
24
15
titaniumbackup do not work on Mi6, here is bug code:
Code:
java.lang.RuntimeException: Unable to start activity ComponentInfo{com.keramidas.TitaniumBackup/com.keramidas.TitaniumBackup.MainActivity}: android.database.sqlite.SQLiteCantOpenDatabaseException: unknown error (code 14): Could not open database
    at android.app.ActivityThread.performLaunchActivity(Unknown Source:524)
    at android.app.ActivityThread.handleLaunchActivity(Unknown Source:30)
    at android.app.ActivityThread.-wrap11(Unknown Source:0)
    at android.app.ActivityThread$H.handleMessage(Unknown Source:80)
    at android.os.Handler.dispatchMessage(Unknown Source:21)
    at android.os.Looper.loop(Unknown Source:139)
    at android.app.ActivityThread.main(Unknown Source:71)
    at java.lang.reflect.Method.invoke(Native Method)
    at com.android.internal.os.Zygote$MethodAndArgsCaller.run(Unknown Source:11)
    at com.android.internal.os.ZygoteInit.main(Unknown Source:200)
Caused by: android.database.sqlite.SQLiteCantOpenDatabaseException: unknown error (code 14): Could not open database
    at android.database.sqlite.SQLiteConnection.nativeOpen(Native Method)
    at android.database.sqlite.SQLiteConnection.open(Unknown Source:16)
    at android.database.sqlite.SQLiteConnection.open(Unknown Source:5)
    at android.database.sqlite.SQLiteConnectionPool.openConnectionLocked(Unknown Source:6)
    at android.database.sqlite.SQLiteConnectionPool.open(Unknown Source:3)
    at android.database.sqlite.SQLiteConnectionPool.open(Unknown Source:16)
    at android.database.sqlite.SQLiteDatabase.openInner(Unknown Source:22)
    at android.database.sqlite.SQLiteDatabase.open(Unknown Source:0)
    at android.database.sqlite.SQLiteDatabase.openDatabase(Unknown Source:5)
    at android.database.sqlite.SQLiteOpenHelper.getDatabaseLocked(Unknown Source:234)
    at android.database.sqlite.SQLiteOpenHelper.getReadableDatabase(Unknown Source:2)
    at o.dg.ˊ(Source:191)
    at com.keramidas.TitaniumBackup.MainActivity.onCreate(Source:361)
    at android.app.Activity.performCreate(Unknown Source:3)
    at android.app.Instrumentation.callActivityOnCreate(Unknown Source:3)
    at android.app.ActivityThread.performLaunchActivity(Unknown Source:466)
    ... 9 more
 

Harald1234

Members
Sep 15, 2017
17
15
Telegram Notifications:
System notification run
Own notification not


Same as some Versions before.
Now i search about this version, where the own notifications run.

No reaction about this problem again, i dont understand and makes me angry
 

Redmi3Pro

Members
Apr 7, 2016
40
20
mido, updated this morning (dirty flash+magisk 15.2), seems good battery after a workday of use.
40 min waze, 5% battery decrease. Verified adaway works fine with magisk 15.2 at first install. did not try new magisk 15.3.
continue testing ...

Thanks devs for the builds !
Could you let me know what version the security patch is? Thanks.
 

0kti78

Members
Dec 24, 2016
180
40
titaniumbackup do not work on Mi6, here is bug code:
Code:
java.lang.RuntimeException: Unable to start activity ComponentInfo{com.keramidas.TitaniumBackup/com.keramidas.TitaniumBackup.MainActivity}: android.database.sqlite.SQLiteCantOpenDatabaseException: unknown error (code 14): Could not open database
    at android.app.ActivityThread.performLaunchActivity(Unknown Source:524)
    at android.app.ActivityThread.handleLaunchActivity(Unknown Source:30)
    at android.app.ActivityThread.-wrap11(Unknown Source:0)
    at android.app.ActivityThread$H.handleMessage(Unknown Source:80)
    at android.os.Handler.dispatchMessage(Unknown Source:21)
    at android.os.Looper.loop(Unknown Source:139)
    at android.app.ActivityThread.main(Unknown Source:71)
    at java.lang.reflect.Method.invoke(Native Method)
    at com.android.internal.os.Zygote$MethodAndArgsCaller.run(Unknown Source:11)
    at com.android.internal.os.ZygoteInit.main(Unknown Source:200)
Caused by: android.database.sqlite.SQLiteCantOpenDatabaseException: unknown error (code 14): Could not open database
    at android.database.sqlite.SQLiteConnection.nativeOpen(Native Method)
    at android.database.sqlite.SQLiteConnection.open(Unknown Source:16)
    at android.database.sqlite.SQLiteConnection.open(Unknown Source:5)
    at android.database.sqlite.SQLiteConnectionPool.openConnectionLocked(Unknown Source:6)
    at android.database.sqlite.SQLiteConnectionPool.open(Unknown Source:3)
    at android.database.sqlite.SQLiteConnectionPool.open(Unknown Source:16)
    at android.database.sqlite.SQLiteDatabase.openInner(Unknown Source:22)
    at android.database.sqlite.SQLiteDatabase.open(Unknown Source:0)
    at android.database.sqlite.SQLiteDatabase.openDatabase(Unknown Source:5)
    at android.database.sqlite.SQLiteOpenHelper.getDatabaseLocked(Unknown Source:234)
    at android.database.sqlite.SQLiteOpenHelper.getReadableDatabase(Unknown Source:2)
    at o.dg.ˊ(Source:191)
    at com.keramidas.TitaniumBackup.MainActivity.onCreate(Source:361)
    at android.app.Activity.performCreate(Unknown Source:3)
    at android.app.Instrumentation.callActivityOnCreate(Unknown Source:3)
    at android.app.ActivityThread.performLaunchActivity(Unknown Source:466)
    ... 9 more
I have no problem with TB.

Tapatalk - Xiaomi MI 6
 

wonderfulme

Members
Nov 22, 2017
19
5
The same thing happened to me, the phone charged 0.5A.
I solved it by starting at TWRP, without disconnecting the charging cable, and then started charging at 1.5A (2.5A with the original charger tested later). When restarting the operating system it continued loading to 1.5A and the problem was solved.

Xiaomi Mi6
Didn't think of that, rolled back to 7.1.1 to be on the safe side.

To those who consider the same path, be wary that dirty flashing 7.1.1 over 8.0 doesn't work; at least it didn't in my situation. Had to wipe the device clean and painfully restore everything manually.

Will probably give it another try once 8.0 hits stable, too buggy for everyday use at the moment.

Mi6 6/64.
 
  • Like
Reactions: ivan.martinko
Aug 26, 2016
532
102
Telegram Notifications:
System notification run
Own notification not


Same as some Versions before.
Now i search about this version, where the own notifications run.

No reaction about this problem again, i dont understand and makes me angry
Notifications is a "Minor" bug, see a full explanation at https://xiaomi.eu/community/posts/403653/

In this context, could you tell me how a notifications bug could be anything other than Minor.

If it is a deal-breaker for you:
1. Hire your own developer to fix it for yourself,
2. Take your anger somewhere else, use their free ROM and deal with their bugs, or
3. Be patient and wait for a correction, without incessantly spamming the forum like some other impatient souls.
 
Z

zeork

I think Mi6 rom China was very Buggy and They dont release 8.1.11 to public. Its still close beta.
 

Redmi3Pro

Members
Apr 7, 2016
40
20
Still December.

Envoyé de mon SGP611 en utilisant Tapatalk
Thanks, I'm on the 7.12.21 rom that has the November patch that brought the horrific battery issues, I get half the battery life I used to get. I might update and see if it's fixed, not sure whether to wait until the double notification bug is sorted though.
 

Nuno Cardeira

Members
Jan 13, 2018
6
13
Mi Remote error report


java.lang.UnsatisfiedLinkError: No implementation found for java.lang.String com.xiaomi.shop2.util.DeviceUtil.getDSid() (tried Java_com_xiaomi_shop2_util_DeviceUtil_getDSid and Java_com_xiaomi_shop2_util_DeviceUtil_getDSid__)
at com.xiaomi.shop2.util.DeviceUtil.getDSid(Native Method)
at com.xiaomi.mishopsdk.plugin.PluginSyncUtils.addRequestAllPluginInfoToQueue(Unknown Source:105)
at com.xiaomi.mishopsdk.plugin.PluginSyncUtils.access$000(Unknown Source:0)
at com.xiaomi.mishopsdk.plugin.PluginSyncUtils$3.run(Unknown Source:2)
at android.os.Handler.handleCallback(Unknown Source:2)
at android.os.Handler.dispatchMessage(Unknown Source:4)
at android.os.Looper.loop(Unknown Source:139)
at com.xiaomi.mishopsdk.util.DispatchQueue.run(Unknown Source:19)
 

ivan.martinko

Members
Nov 17, 2016
199
40
This is not the time to use version 8.1.11 on Mi6, at least for me.
I did a clean installation (i made a wipe system, cache + data) and still lots of FCs.

The error happens when I click to select a WIFI network

I've still tried to see the error in "View Summary", but it returns to the lock screen.

And still other problems that do not happen in Android N. For example, if i have an adb shell open and an app requests ROOT access ,and the screen of the device is blocked, i can not unlock (it does not respond when I try to unlock the screen) and need to disconnect the USB cable before.

I will restore a backup with v7.12.7.
Has anyone had success with 8.1.11 on Mi6?
Agree. It is early beta. Should wait month or two when that bugs will be fixed. I return too to latest Nougat beta..
 
  • Like
Reactions: Rogerio Lucas

Soebianto

Members
Sep 15, 2017
1,146
222
  • Like
Reactions: Harald1234

Smooth_gl

Members
Jul 3, 2017
52
20
I actually didn't read at all. I just used logic.
Failed to provide an accurate reason but I was right about not being a bug.
Next time, when you ask a question and you receive an answer try being more polite and then maybe you will get other replies and feedback. Especially when nobody owes you anything and everything here, starting with the updates and ending with the support are FREE services... You are welcome anyway.
Best regards, sir !
Actually your first reply was meaningless. He wanted to know why he has to setup again some apps after update and your answer was "just setup again the apps". Doh...

After he said that your reply was not an answer to his question you started with lame jokes about being a "bug"...
So "sir" please gtfo...
 

HidRo

Members
Mar 30, 2017
92
20
Is there anyone experiencing a hissing sound of recordings?
Redmi Pro x20

Sent from my Redmi Pro using Tapatalk
 
Status
Not open for further replies.