phpolo
Members
- Jul 1, 2013
- 343
- 62
Permission changed to 0644 but problem is the same. No mikey apk displayed after rebooting....
Envoyé de mon MI 2 en utilisant Tapatalk
MULTI 5.7.9/10
- Thread starter ingbrzy
- Start date
- Status
Envoyé de mon MI 2 en utilisant Tapatalk
- May 17, 2013
- 4,332
- 322
1. Create a new folder inside of data\miui\app\noncustomized
2. Named the newly created folder to MiKey
3. Set Mikey folder permission: rwxr-xr-x (0755)
4. move MiKey.apk to MiKey folder
5. Set MiKey.apk permission: rw-r--r-- (0644)
6. Reboot phone
phpolo
Members
- Jul 1, 2013
- 343
- 62
Everything done as requested but same situation??
Why mikey is not a standard apk like mi-fit??
Envoyé de mon MI 2 en utilisant Tapatalk
StrangeOrange
Members
- Jan 27, 2015
- 33
- 30
Edit: Resolved. Click for the solution in a post below.
Hi and first of all thanks to the developers for all the continuing hard work!
On my "Dior" trying to open Additional Settings inevitably ends with a force-close. It was already happening with the last week's version, 5.7.2. The problem is resolved by replacing Xiaomi.eu's Settings.apk with the stock APK and ODEX files from miui_HMNoteLTE_5.7.9_0c14b1a79e_4.4.zip.
If you could take a look at your Settings.apk it'd be much appreciated. I'll try to investigate this in more detail later. The log dump is below:
Update: The problem remains after replacing Settings.apk with earlier versions from Xiaomi.eu releases 5.6.25, 5.6.18, 5.6.11 as well; and an even earlier release, 5.6.4, force-closes on startup. Could it be that there was some change to stock Settings.apk that is not reflected in Xiaomi.eu's release? Or perhaps it's a 4.4/5.0 divergence?
Hi and first of all thanks to the developers for all the continuing hard work!
On my "Dior" trying to open Additional Settings inevitably ends with a force-close. It was already happening with the last week's version, 5.7.2. The problem is resolved by replacing Xiaomi.eu's Settings.apk with the stock APK and ODEX files from miui_HMNoteLTE_5.7.9_0c14b1a79e_4.4.zip.
If you could take a look at your Settings.apk it'd be much appreciated. I'll try to investigate this in more detail later. The log dump is below:
Code:
I/Timeline( 5065): Timeline: Activity_launch_request id:com.android.settings time:291652
I/ActivityManager( 1047): START u0 {act=android.intent.action.MAIN cmp=com.android.settings/.SubSettings (has extras)} from pid 5065
W/Settings( 5065): Setting location_providers_allowed has moved from android.provider.Settings.System to android.provider.Settings.Secure, returning Secure URI.
D/SubSettings( 5065): Launching fragment com.android.settings.OtherPersonalSettings
D/AndroidRuntime( 5065): Shutting down VM
W/dalvikvm( 5065): threadid=1: thread exiting with uncaught exception (group=0x4173cd58)
I/KLO_Stability( 1906): [am_crash][1436613042]:[5065,0,com.android.settings,1086963269,java.lang.NullPointerException,Unable to start activity ComponentInfo{com.android.settings/com.android.settings.SubSettings}: java.lang.NullPointerException,PreferenceGroup.java,-1]
I/WhetstoneService( 1627): Receive am_crash event for pid: 5065
W/KloServer( 1627): Aborted broadcast does not supprt for: com.android.settings
E/AndroidRuntime( 5065): FATAL EXCEPTION: main
E/AndroidRuntime( 5065): Process: com.android.settings, PID: 5065
E/AndroidRuntime( 5065): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.android.settings/com.android.settings.SubSettings}: java.lang.NullPointerException
E/AndroidRuntime( 5065): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java)
E/AndroidRuntime( 5065): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java)
E/AndroidRuntime( 5065): at android.app.ActivityThread.access$800(ActivityThread.java)
E/AndroidRuntime( 5065): at android.app.ActivityThread$H.handleMessage(ActivityThread.java)
E/AndroidRuntime( 5065): at android.os.Handler.dispatchMessage(Handler.java)
E/AndroidRuntime( 5065): at android.os.Looper.loop(Looper.java)
E/AndroidRuntime( 5065): at android.app.ActivityThread.main(ActivityThread.java)
E/AndroidRuntime( 5065): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 5065): at java.lang.reflect.Method.invoke(Method.java:515)
E/AndroidRuntime( 5065): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:793)
E/AndroidRuntime( 5065): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:609)
E/AndroidRuntime( 5065): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime( 5065): Caused by: java.lang.NullPointerException
E/AndroidRuntime( 5065): at android.preference.PreferenceGroup.removePreferenceInt(PreferenceGroup.java)
E/AndroidRuntime( 5065): at android.preference.PreferenceGroup.removePreference(PreferenceGroup.java)
E/AndroidRuntime( 5065): at com.android.settings.OtherPersonalSettings.onCreate(OtherPersonalSettings.java:97)
E/AndroidRuntime( 5065): at android.app.Fragment.performCreate(Fragment.java)
E/AndroidRuntime( 5065): at android.app.FragmentManagerImpl.moveToState(FragmentManager.java)
E/AndroidRuntime( 5065): at android.app.FragmentManagerImpl.moveToState(FragmentManager.java)
E/AndroidRuntime( 5065): at android.app.BackStackRecord.run(BackStackRecord.java)
E/AndroidRuntime( 5065): at android.app.FragmentManagerImpl.execPendingActions(FragmentManager.java)
E/AndroidRuntime( 5065): at android.app.Activity.performStart(Activity.java)
E/AndroidRuntime( 5065): ... 12 more
W/ActivityManager( 1047): Force finishing activity com.android.settings/.SubSettings
W/ActivityManager( 1047): Force finishing activity com.android.settings/.MiuiSettings
I/libmc ( 1906): received event[index:0,mask:0x80,name:system_app_crash@1436613043059.txt]
I/KLO_Stability( 1906): get wanted event[mask:128, name:system_app_crash@1436613043059.txt] from the watchsetUpdate: The problem remains after replacing Settings.apk with earlier versions from Xiaomi.eu releases 5.6.25, 5.6.18, 5.6.11 as well; and an even earlier release, 5.6.4, force-closes on startup. Could it be that there was some change to stock Settings.apk that is not reflected in Xiaomi.eu's release? Or perhaps it's a 4.4/5.0 divergence?
Last edited:
phpolo
Members
- Jul 1, 2013
- 343
- 62
Dear ingbrzy and graw2 since all suggested test was without result I install again version 5.7.2
With this version I succeed installation of mikey. But now a pop-up alert exists sees screen copy.
I will be very happy if you can solve this problem.
Note for graw2 mikey.apk is under system/app directly with 7.5.5 permission as it was before.
Envoyé de mon MI 2 en utilisant Tapatalk
With this version I succeed installation of mikey. But now a pop-up alert exists sees screen copy.
I will be very happy if you can solve this problem.
Note for graw2 mikey.apk is under system/app directly with 7.5.5 permission as it was before.
Envoyé de mon MI 2 en utilisant Tapatalk
The new backup engine is false. After every new backup all my widgets are "dead"
Attachments
- May 17, 2013
- 4,332
- 322
Unfortunately, if you downgrade your system to any pervious release, you should make wipe all data after that for stable operation...Dear ingbrzy and graw2 since all suggested test was without result I install again version 5.7.2
With this version I succeed installation of mikey. But now a pop-up alert exists sees screen copy.
I will be very happy if you can solve this problem.
Note for graw2 mikey.apk is under system/app directly with 7.5.5 permission as it was before.
Envoyé de mon MI 2 en utilisant Tapatalk
Sent from Mi2S [MIUIv6-L] using Tapatalk
- Feb 11, 2012
- 11,601
- 322
Any other dior user with same FC?
Did you change something in our ROM? Build.prop specially?
~Tapatalk~
StrangeOrange
Members
- Jan 27, 2015
- 33
- 30
Edit: Resolved. Click for the solution in a post below.
Essentially, I'm using the stock build.prop with a few changes of my own, some of which I posted here before and you included in your version as well.
As I'm doing a dirty upgrade, it's entirely possible it's something specific to my device. Why would the stock Settings.apk work though? Confirmation or disproval by other "Dior" users would definitely shed some light.
Thanks for the response!
Yeah, I did. I can't see how it'd matter but here's the diff:
Code:
--- build.prop.xiaomi-eu Fri Feb 29 02:33:46 2008
+++ build.prop Sat Jul 11 12:27:31 2015
@@ -23 +23 @@
-ro.product.locale.region=UK
+ro.product.locale.region=US
@@ -235,9 +234,0 @@
-# ADDED BY XIAOMI.EU
-ro.rommanager.developerid=xiaomi.eu
-ro.modversion=MIUIAndroid-v4.7.0-EN-dior
-ro.goo.developerid=ibotpeaches
-ro.goo.rom=MIUIAndroid
-ro.goo.version=1436471389
-ro.product.mod_device=dior_mam
-persist.sys.timezone=Europe/Berlin
-ro.miui.region=UK
@@ -247,0 +239 @@
+ro.setupwizard.mode=OPTIONALAs I'm doing a dirty upgrade, it's entirely possible it's something specific to my device. Why would the stock Settings.apk work though? Confirmation or disproval by other "Dior" users would definitely shed some light.
Thanks for the response!
Last edited:
- Feb 11, 2012
- 11,601
- 322
Then use our build.prop as base for your changes and do not remove ours...
~Tapatalk~
- Aug 20, 2011
- 2,727
- 247
My advice:
Don't... mess... with...system files.
Especially if have no idea what are you doing.
Wysłane z MI Note Pro
Ravi Ranjan
Members
- Apr 30, 2015
- 93
- 30
Buenas tardes, me podria Decir o Pasar el enlace a la última estable multilanguage Redmi V6 párr 1s WCDMA.
Gracias.
Gracias.
Last edited:
I have the same problem on ALL MIUI v6 xiaomi.eu roms.
After update, cannot connect to MIPC suite (http://pcsuite.mi.com/).
WIPE ALL DATA resolve the problem, then after install next updates, problem comes back.
Please don't ignore...
Link to problem description:
http://xiaomi.eu/community/threads/dear-ingbrzy-mi3-mipc-suite-not-work-after-update.27818/
StrangeOrange
Members
- Jan 27, 2015
- 33
- 30
Settings.apk force-close when entering Additional Settings: Solution
As for the XML in Xiaomi.eu's version, the file is well-formed and validates correctly, so it's not as straightforward as I expected. The likely culprits seem to be the icon references in the form of:
Or perhaps just one of them. This is the only practical difference between the two files. Other than that, the stock file has one additional line but it is unlikely that the absence of a menu item would be causing a force-close:
This is where my investigation stopped but the other attachment has all I know to help with further nailing down the issue. Hopefully the developers could take it over from here.
As I was suspecting, the problem is caused by an XML resource file, namely res/xml/other_personal_settings.xml. Replacing this file, which is inside the APK, with the stock version resolves the issue. If there's anyone else also experiencing this, feel free to overwrite your Settings.apk with this version I made (hosted externally due to attachment size limit), and it should work just fine (disclaimer: do it at your own peril).
As for the XML in Xiaomi.eu's version, the file is well-formed and validates correctly, so it's not as straightforward as I expected. The likely culprits seem to be the icon references in the form of:
Code:
<Preference android:icon="@drawable/..." ... >This is where my investigation stopped but the other attachment has all I know to help with further nailing down the issue. Hopefully the developers could take it over from here.
It was reported before for 5.7.2 by Batsilos (link to post). I'll PM him to let him know a solution is available.
Last edited:
phpolo
Members
- Jul 1, 2013
- 343
- 62
I don't understand why I am the only one complaining against the suppression of mikey on the updates packages.
This configuration is specifically designed for MI2?
Or nobody use mikey?
Or other mikey.apk can be installed as standard apk (not in system folder)
This situation is more and more annoying
PLEASE HELP !!!
Last update is the worst one on this matter
Envoyé de mon MI 2 en utilisant Tapatalk
This configuration is specifically designed for MI2?
Or nobody use mikey?
Or other mikey.apk can be installed as standard apk (not in system folder)
This situation is more and more annoying
PLEASE HELP !!!
Last update is the worst one on this matter
Envoyé de mon MI 2 en utilisant Tapatalk
Can someone give me German language pack, is anywhere available? I see that it's not included in v6
- Feb 11, 2012
- 11,601
- 322
So you also edited our build.prop without any knowledge what you are doing or you get settings FC just after installing our ROM? It's very important to know because it's not just about that FC... You miss a lot of other functions on another places if you got that FC...
~Tapatalk~
Last edited:
PJzuza Sasa
Members
- Jun 16, 2014
- 68
- 30
I always add Mikey on my MI3W and I can install Mikey.apk and I don't have any problem with Mikey app so far.
@ingbrzy
On the last update(5.70 cancro) I now know the problem that why my Note system app always FC. It was app named "MaxLock" caused the problem so I am sorry to bother you that time
Sent from my MI3W using tapatalk
(I have 3 phones; Xiaomi Mi3W & IPhone5S & Samsung Wave II)
phpolo
Members
- Jul 1, 2013
- 343
- 62
Thank you for your answer but this mikey.apk problem is occuring on this last 5.7.10 release on aries lollipop one partition version.I always add Mikey on my MI3W and I can install Mikey.apk and I don't have any problem with Mikey app so far.
@ingbrzy
On the last update(5.70 cancro) I now know the problem that why my Note system app always FC. It was app named "MaxLock" caused the problem so I am sorry to bother you that time
Sent from my MI3W using tapatalk
(I have 3 phones; Xiaomi Mi3W & IPhone5S & Samsung Wave II)
Is there any other guy using mikey on Xiaomi Mi2 same configuration?
Envoyé de mon MI 2 en utilisant Tapatalk
i am on dior and backup does not work. last week it stored the back up file in the internal memory, this week it worked once, stored the back up on external sd, but the next day the back up stucks on 12% and keeps trying forever, no advance.
other than that all seems well, but back up is non operative as is, sorry.
thanks
j
other than that all seems well, but back up is non operative as is, sorry.
thanks
j
Hi ingbrzy, just another problem I've noted....my gucci stays all night turned on, but in the morning when I wake up, I see that wifi network has turned off. I need to power off wifi and then turn it on again. I've loocked at wifi settings and the option to keep always wifi on is activated.....any help would be grateful. Thanks.
- Status
