Hmmm.. For some reason I can't anymore autorise my card in Google Pay
Always last 10 times i have updated my firmware, i went to /data/data/com.google.android.gms and deleted this folder.
This time after deleting it seems this method don't work anymore.
Any idea how to fix it?
Most of the strings translated into Russian language for the previous build are missing in this build. Why?
The translation was saved in the repository on the night from Wednesday to Thursday, before the build started.
I am translating the firmware into Russian.
I do all this in my personal time and free of charge, raising popularity among Russian-speaking users. And I want to do it well.
To check the correctness of the translation, I often have to recompile applications with added translation. The problem is that some applications are not recompile correctly.
[*] Recompile Settings
I: Using Apktool 2.4.1_0303
W: Could not find sources
I: Checking whether resources has changed...
I: Building resources...
W: W/ResourceType( 5032): DynamicRefTable(0x10): No mapping for build-time package ID 0x10.
W: W/ResourceType( 5032): e[0x01] -> 0x01
W: W/ResourceType( 5032): e[0x7f] -> 0x7f
W: E/ResourceType( 5032): Failed resolving ResTable_map name at 2144 with ident 0x100b0015
W: W/ResourceType( 5032): DynamicRefTable(0x10): No mapping for build-time package ID 0x10.
W: W/ResourceType( 5032): e[0x01] -> 0x01
W: W/ResourceType( 5032): e[0x7f] -> 0x7f
W: E/ResourceType( 5032): Failed resolving ResTable_map name at 3664 with ident 0x100b0010
W: W/ResourceType( 5032): Attempt to retrieve bag 0x1001004f which is invalid or in a cycle.
W: warning: Package not found for resource #1001001a
W: warning: Package not found for resource #1001004f
W: warning: Package not found for resource #1001004f
I: Building apk file...
I: Copying unknown files/dir...
I: Built apk...
DONE
Total time: 14 min. 4 sec.
Can you suggest a way to correctly recompile or how to visually check the translation?
You can leave me a private message.
Most of the strings translated into Russian language for the previous build are missing in this build. Why?
The translation was saved in the repository on the night from Wednesday to Thursday, before the build started.
I am translating the firmware into Russian.
I do all this in my personal time and free of charge, raising popularity among Russian-speaking users. And I want to do it well.
To check the correctness of the translation, I often have to recompile applications with added translation. The problem is that some applications are not recompile correctly.
[*] Recompile Settings
I: Using Apktool 2.4.1_0303
W: Could not find sources
I: Checking whether resources has changed...
I: Building resources...
W: W/ResourceType( 5032): DynamicRefTable(0x10): No mapping for build-time package ID 0x10.
W: W/ResourceType( 5032): e[0x01] -> 0x01
W: W/ResourceType( 5032): e[0x7f] -> 0x7f
W: E/ResourceType( 5032): Failed resolving ResTable_map name at 2144 with ident 0x100b0015
W: W/ResourceType( 5032): DynamicRefTable(0x10): No mapping for build-time package ID 0x10.
W: W/ResourceType( 5032): e[0x01] -> 0x01
W: W/ResourceType( 5032): e[0x7f] -> 0x7f
W: E/ResourceType( 5032): Failed resolving ResTable_map name at 3664 with ident 0x100b0010
W: W/ResourceType( 5032): Attempt to retrieve bag 0x1001004f which is invalid or in a cycle.
W: warning: Package not found for resource #1001001a
W: warning: Package not found for resource #1001004f
W: warning: Package not found for resource #1001004f
I: Building apk file...
I: Copying unknown files/dir...
I: Built apk...
DONE
Total time: 14 min. 4 sec.
Can you suggest a way to correctly recompile or how to visually check the translation?
You can leave me a private message.
We have our own private Apktool for the decompile/recompile procedure, so I can't answer that.
I'm not sure which strings you're referring to, but Dev ROMs are quite chaotic when it comes to strings.
android.content.ActivityNotFoundException: No Activity found to handle Intent { act=com.miui.cloudbackup.settings }
at android.app.Instrumentation.checkStartActivityResult(Unknown Source:128)
at android.app.Instrumentation.execStartActivity(Unknown Source:210)
at android.app.Activity.startActivityForResult(Unknown Source:23)
at android.app.Activity.startActivityForResult(Unknown Source:1)
at android.app.Activity.startActivity(Unknown Source:7)
at android.app.Activity.startActivity(Unknown Source:1)
at android.preference.Preference.performClick(Unknown Source:55)
at android.preference.PreferenceScreen.onItemClick(Unknown Source:28)
at android.widget.AdapterView.performItemClick(Unknown Source:14)
at android.widget.AbsListView.performItemClick(Unknown Source:198)
at android.widget.AbsListView$PerformClick.run(Unknown Source:62)
at android.widget.AbsListView$3.run(Unknown Source:46)
at android.os.Handler.handleCallback(Unknown Source:2)
at android.os.Handler.dispatchMessage(Unknown Source:4)
at android.os.Looper.loop(Unknown Source:208)
at android.app.ActivityThread.main(Unknown Source:107)
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:274)
Mi Mix 2 with and without Magisk - no more "Device storage is corrupted..." message, that was being displayed on the previous week version.
So something has been fixed, nice.
I use OrangeFox recovery and got "Can't mount vendor" during updating. When mounted vendor manually before flashing zip I got "Can't mount cust".
What is this part of the installation for? Anyway the phone runs correctly, just asking. I'm using OrangeFox because of using encrypted storage.
I think they set both mount point to the same partition within fstab. TWRP is limited to connect only one mount point to a partition.
There are several possible reasons to leave the possibility active to mount two different mount points to one partition - the common one is to keep compatibility to older ROMs that need one of both mount points connected to a read/writable partition.
(short) Tutorial in getting your Xiaomi Mi MIX2 encrypted with latest Android 9 (Pie) ROM released by xiaomi.eu (and propably also with the beta ROMs released by Xiaomi/miui.com) Preparations: - your phone is unlocked - a custom recovery is...
On my Mix 3 all seems to be okay. I´ve downloaded it over my smartphone and installed it. Have to set again TWRP to english and enter my password for decription. But installation runs well (i always wipe cache/ dalvik and system, but not data) and the Mix started without problems. Thank you for your effort.
With the previous ROM AdAway 4.1.0-2ba17108 worked regularly. With this update it says insufficient space in the partition. I tried to update to the latest version but it's the same. I have Mi Mix 3 with the latest Magisk
With the previous ROM AdAway 4.1.0-2ba17108 worked regularly. With this update it says insufficient space in the partition. I tried to update to the latest version but it's the same. I have Mi Mix 3 with the latest Magisk
It means, note 7 can get maximum 8 hours in normal usage. I am also getting the same what you said on official 10.3.5 without root. I was thinking to move to EU rom.
I was getting 9 to 10 hours on redmi note 5 pro. I thought, i should get the same on note 7.