deepblue2000
Members
- 14 Apr 2017
- 947
- 182
Wipe cache and dalvik in recovery
after a reboot my mi6 did fast charge again.
but I hope there will be a fix soon for the non working notifications
Wipe cache and dalvik in recovery
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
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 !
I have no problem with TB.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
Didn't think of that, rolled back to 7.1.1 to be on the safe side.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
Still December.Could you let me know what version the security patch is? Thanks.
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
Never say never :-D. Sooni think never!
I will try this before go back to 7.12.7. Thanks!
I know how to bypass this, but it should work without this workaround. This bug exists for ages now and was reported several times!Disable miui optimization, install from Amazon and enable again.
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.Still December.
Envoyé de mon SGP611 en utilisant Tapatalk
Working fine on my phoneMi Remote do not work on Mi6, any fix?
Thanks
Agree. It is early beta. Should wait month or two when that bugs will be fixed. I return too to latest Nougat beta..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?
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
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...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 !
We use essential cookies to make this site work, and optional cookies to enhance your experience. Cookies are also used for ads personalisation