Guys, I did a short analysis on the apps in firmwares 1.2.3 and 1.3.0n. The results were pretty surprising:
The Chinese one is more advanced adn much newer (as was already known)
The Watchfaces app contains the SAME drawings in both versions (except the English one having less watchfaces). That means: The Chinese version does have e.g. English weekdays available (stored at the same locations) as the English version has. It probably was just disabled in the code to use the right coding!
One gets the clear indication that they worked on a joint firmware and then at some 70% got the strategic directions to split the firmware.
I am currently doing some tests to modify the apps and load them on the Chinese version. Maybe a Chinese version with English translation is better than the official English version.
Yes, in this moment i think that the china version with hack is better that English version
Wonder if it's worth flashing Chinese ROM to English version and then changing to English?
or, would you expect English version will catch up soon?
I'm disappointed so far with this watch (or rather the very very simple support from the APP on your phone)
You can't even look at the step or sleep data on your phone?!?!?
Nothing wrong with the hardware but it seems they rushed out this awesome device not really thinking about the supplementary app to go with it.
shayne77 said:
Wonder if it's worth flashing Chinese ROM to English version and then changing to English?
or, would you expect English version will catch up soon?
I'm disappointed so far with this watch (or rather the very very simple support from the APP on your phone)
You can't even look at the step or sleep data on your phone?!?!?
Nothing wrong with the hardware but it seems they rushed out this awesome device not really thinking about the supplementary app to go with it.
Click to expand...
Click to collapse
To sync sleep and steps on phone, you need Chinese Amazfit and MiFit apps, login with same Xiaomi account
Inviato dal mio D6633 utilizzando Tapatalk
Pi3rluigi said:
To sync sleep and steps on phone, you need Chinese Amazfit and MiFit apps, login with same Xiaomi account
Inviato dal mio D6633 utilizzando Tapatalk
Click to expand...
Click to collapse
I saw that tutorial on YouTube but I couldn't get MiFit to show data (it seemed to read it, sync ok but not display anything?)
Need help from app developer
Ok, I decompiled one of the Huami apps ("WearSports"), changed a small text in the resources ("Trail Run" -> "Berg Run"), compiled the app again (using apktool), signed the apk and exchanged the original apk with the modded one.
The watch starts ok. When swiping left, one gets to the Sports app, which does indeed show "Berg Run" instead of "Trail Run" (hurray). But when I want to enter one of the sports, the app force closes with the following error:
Code:
D/HmSport ( 9704): HmSportProvider -- today distance:0.0
I/slog ( 9704): 已经有文件存在于: /sdcard/.springchannel/com.huami.watch.sport , 旧文件可能被覆盖或删除呢.
E/DatabaseUtils( 9128): Writing exception to parcel
E/DatabaseUtils( 9128): java.lang.SecurityException: Permission denial: writing to secure settings requires android.permission.WRITE_SECURE_SETTINGS
E/DatabaseUtils( 9128): at com.android.providers.settings.SettingsProvider.checkWritePermissions(SettingsProvider.java:313)
E/DatabaseUtils( 9128): at com.android.providers.settings.SettingsProvider.insertForUser(SettingsProvider.java:1110)
E/DatabaseUtils( 9128): at com.android.providers.settings.SettingsProvider.call(SettingsProvider.java:801)
E/DatabaseUtils( 9128): at android.content.ContentProvider$Transport.call(ContentProvider.java:370)
E/DatabaseUtils( 9128): at android.content.ContentProviderNative.onTransact(ContentProviderNative.java:283)
E/DatabaseUtils( 9128): at android.os.Binder.execTransact(Binder.java:446)
E/AndroidRuntime( 9704): FATAL EXCEPTION: global-work-thread
E/AndroidRuntime( 9704): Process: com.huami.watch.sport, PID: 9704
E/AndroidRuntime( 9704): java.lang.SecurityException: Permission denial: writing to secure settings requires android.permission.WRITE_SECURE_SETTINGS
E/AndroidRuntime( 9704): at android.os.Parcel.readException(Parcel.java:1546)
E/AndroidRuntime( 9704): at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:185)
E/AndroidRuntime( 9704): at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:137)
E/AndroidRuntime( 9704): at android.content.ContentProviderProxy.call(ContentProviderNative.java:645)
E/AndroidRuntime( 9704): at android.provider.Settings$NameValueCache.putStringForUser(Settings.java:1094)
E/AndroidRuntime( 9704): at android.provider.Settings$Secure.putStringForUser(Settings.java:3173)
E/AndroidRuntime( 9704): at android.provider.Settings$Secure.putFloatForUser(Settings.java:3459)
E/AndroidRuntime( 9704): at android.provider.Settings$Secure.putFloat(Settings.java:3453)
E/AndroidRuntime( 9704): at com.huami.watch.sport.db.DataManager.setTodayDistance(DataManager.java:370)
E/AndroidRuntime( 9704): at com.huami.watch.sport.db.SportContentProvider.updateTodayDistance(SportContentProvider.java:95)
E/AndroidRuntime( 9704): at com.huami.watch.sport.db.SportContentProvider.access$000(SportContentProvider.java:24)
E/AndroidRuntime( 9704): at com.huami.watch.sport.db.SportContentProvider$1.run(SportContentProvider.java:57)
E/AndroidRuntime( 9704): at android.os.Handler.handleCallback(Handler.java:739)
E/AndroidRuntime( 9704): at android.os.Handler.dispatchMessage(Handler.java:95)
E/AndroidRuntime( 9704): at android.os.Looper.loop(Looper.java:135)
E/AndroidRuntime( 9704): at android.os.HandlerThread.run(HandlerThread.java:61)
The mentioned permission is in the AndroidManifest.xml (as it was decompiled from the original app).
I need help from an experienced developer. If we could get this fixed, we can setup our own custom ROM, based on the most current Chinese version, including all English translations and what else we want to.
Neuer_User said:
Ok, I decompiled one of the Huami apps ("WearSports"), changed a small text in the resources ("Trail Run" -> "Berg Run"), compiled the app again (using apktool), signed the apk and exchanged the original apk with the modded one.
The watch starts ok. When swiping left, one gets to the Sports app, which does indeed show "Berg Run" instead of "Trail Run" (hurray). But when I want to enter one of the sports, the app force closes with the following error:
Code:
D/HmSport ( 9704): HmSportProvider -- today distance:0.0
I/slog ( 9704): 已经有文件存在于: /sdcard/.springchannel/com.huami.watch.sport , 旧文件可能被覆盖或删除呢.
E/DatabaseUtils( 9128): Writing exception to parcel
E/DatabaseUtils( 9128): java.lang.SecurityException: Permission denial: writing to secure settings requires android.permission.WRITE_SECURE_SETTINGS
E/DatabaseUtils( 9128): at com.android.providers.settings.SettingsProvider.checkWritePermissions(SettingsProvider.java:313)
E/DatabaseUtils( 9128): at com.android.providers.settings.SettingsProvider.insertForUser(SettingsProvider.java:1110)
E/DatabaseUtils( 9128): at com.android.providers.settings.SettingsProvider.call(SettingsProvider.java:801)
E/DatabaseUtils( 9128): at android.content.ContentProvider$Transport.call(ContentProvider.java:370)
E/DatabaseUtils( 9128): at android.content.ContentProviderNative.onTransact(ContentProviderNative.java:283)
E/DatabaseUtils( 9128): at android.os.Binder.execTransact(Binder.java:446)
E/AndroidRuntime( 9704): FATAL EXCEPTION: global-work-thread
E/AndroidRuntime( 9704): Process: com.huami.watch.sport, PID: 9704
E/AndroidRuntime( 9704): java.lang.SecurityException: Permission denial: writing to secure settings requires android.permission.WRITE_SECURE_SETTINGS
E/AndroidRuntime( 9704): at android.os.Parcel.readException(Parcel.java:1546)
E/AndroidRuntime( 9704): at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:185)
E/AndroidRuntime( 9704): at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:137)
E/AndroidRuntime( 9704): at android.content.ContentProviderProxy.call(ContentProviderNative.java:645)
E/AndroidRuntime( 9704): at android.provider.Settings$NameValueCache.putStringForUser(Settings.java:1094)
E/AndroidRuntime( 9704): at android.provider.Settings$Secure.putStringForUser(Settings.java:3173)
E/AndroidRuntime( 9704): at android.provider.Settings$Secure.putFloatForUser(Settings.java:3459)
E/AndroidRuntime( 9704): at android.provider.Settings$Secure.putFloat(Settings.java:3453)
E/AndroidRuntime( 9704): at com.huami.watch.sport.db.DataManager.setTodayDistance(DataManager.java:370)
E/AndroidRuntime( 9704): at com.huami.watch.sport.db.SportContentProvider.updateTodayDistance(SportContentProvider.java:95)
E/AndroidRuntime( 9704): at com.huami.watch.sport.db.SportContentProvider.access$000(SportContentProvider.java:24)
E/AndroidRuntime( 9704): at com.huami.watch.sport.db.SportContentProvider$1.run(SportContentProvider.java:57)
E/AndroidRuntime( 9704): at android.os.Handler.handleCallback(Handler.java:739)
E/AndroidRuntime( 9704): at android.os.Handler.dispatchMessage(Handler.java:95)
E/AndroidRuntime( 9704): at android.os.Looper.loop(Looper.java:135)
E/AndroidRuntime( 9704): at android.os.HandlerThread.run(HandlerThread.java:61)
The mentioned permission is in the AndroidManifest.xml (as it was decompiled from the original app).
I need help from an experienced developer. If we could get this fixed, we can setup our own custom ROM, based on the most current Chinese version, including all English translations and what else we want to.
Click to expand...
Click to collapse
UPDATE:
I can grant the app the WRITE_SECURE_SETTINGS permission, and then it indeed works (command "pm grant <package name> android.permission.WRITE_SECURE_SETTINGS"). The question is now, why do I need to grant that manually, when this is in already in the AndroidManifest.xml???
Is possible change millas to km??? Thanks for you work
sakilxda said:
Is possible change millas to km??? Thanks for you work
Click to expand...
Click to collapse
With this approach, yes. I need to get this running first, though...
Perfect, many people hope this
And do you think is possible put the original Chinesse firmware?
Change the English to Chinese after of Chinese to english
Return to previus version again
I am currently working on a "non-intrusive" custom-rom. That is using the Chinese version on the watch, booting with a special (temporary) boot image and running translated (and modded, if needed) apps. So, a simple reboot, and you would have back the original Chinese version.
I think I can get this running. I exchanged one app with this method, so It could be done with all apps. But I am still having some problems to solve first. And I don't have much time (actually, currently, nearly no time at all ).
Neuer_User said:
I am currently working on a "non-intrusive" custom-rom. That is using the Chinese version on the watch, booting with a special (temporary) boot image and running translated (and modded, if needed) apps. So, a simple reboot, and you would have back the original Chinese version.
I think I can get this running. I exchanged one app with this method, so It could be done with all apps. But I am still having some problems to solve first. And I don't have much time (actually, currently, nearly no time at all ).
Click to expand...
Click to collapse
Really appreciate your work for our watch, I'm willing to help in translating this watch into some language, but I'm not a developer, and it would be nice if we can enable language setting in option for our future custom rom, so we can choose the language we want.
big thanks Neuer!
Neuer_User said:
Ok, I decompiled one of the Huami apps ("WearSports"), changed a small text in the resources ("Trail Run" -> "Berg Run"), compiled the app again (using apktool), signed the apk and exchanged the original apk with the modded one.
The watch starts ok. When swiping left, one gets to the Sports app, which does indeed show "Berg Run" instead of "Trail Run" (hurray). But when I want to enter one of the sports, the app force closes with the following error:
Code:
D/HmSport ( 9704): HmSportProvider -- today distance:0.0
I/slog ( 9704): 已经有文件存在于: /sdcard/.springchannel/com.huami.watch.sport , 旧文件可能被覆盖或删除呢.
E/DatabaseUtils( 9128): Writing exception to parcel
E/DatabaseUtils( 9128): java.lang.SecurityException: Permission denial: writing to secure settings requires android.permission.WRITE_SECURE_SETTINGS
E/DatabaseUtils( 9128): at com.android.providers.settings.SettingsProvider.checkWritePermissions(SettingsProvider.java:313)
E/DatabaseUtils( 9128): at com.android.providers.settings.SettingsProvider.insertForUser(SettingsProvider.java:1110)
E/DatabaseUtils( 9128): at com.android.providers.settings.SettingsProvider.call(SettingsProvider.java:801)
E/DatabaseUtils( 9128): at android.content.ContentProvider$Transport.call(ContentProvider.java:370)
E/DatabaseUtils( 9128): at android.content.ContentProviderNative.onTransact(ContentProviderNative.java:283)
E/DatabaseUtils( 9128): at android.os.Binder.execTransact(Binder.java:446)
E/AndroidRuntime( 9704): FATAL EXCEPTION: global-work-thread
E/AndroidRuntime( 9704): Process: com.huami.watch.sport, PID: 9704
E/AndroidRuntime( 9704): java.lang.SecurityException: Permission denial: writing to secure settings requires android.permission.WRITE_SECURE_SETTINGS
E/AndroidRuntime( 9704): at android.os.Parcel.readException(Parcel.java:1546)
E/AndroidRuntime( 9704): at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:185)
E/AndroidRuntime( 9704): at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:137)
E/AndroidRuntime( 9704): at android.content.ContentProviderProxy.call(ContentProviderNative.java:645)
E/AndroidRuntime( 9704): at android.provider.Settings$NameValueCache.putStringForUser(Settings.java:1094)
E/AndroidRuntime( 9704): at android.provider.Settings$Secure.putStringForUser(Settings.java:3173)
E/AndroidRuntime( 9704): at android.provider.Settings$Secure.putFloatForUser(Settings.java:3459)
E/AndroidRuntime( 9704): at android.provider.Settings$Secure.putFloat(Settings.java:3453)
E/AndroidRuntime( 9704): at com.huami.watch.sport.db.DataManager.setTodayDistance(DataManager.java:370)
E/AndroidRuntime( 9704): at com.huami.watch.sport.db.SportContentProvider.updateTodayDistance(SportContentProvider.java:95)
E/AndroidRuntime( 9704): at com.huami.watch.sport.db.SportContentProvider.access$000(SportContentProvider.java:24)
E/AndroidRuntime( 9704): at com.huami.watch.sport.db.SportContentProvider$1.run(SportContentProvider.java:57)
E/AndroidRuntime( 9704): at android.os.Handler.handleCallback(Handler.java:739)
E/AndroidRuntime( 9704): at android.os.Handler.dispatchMessage(Handler.java:95)
E/AndroidRuntime( 9704): at android.os.Looper.loop(Looper.java:135)
E/AndroidRuntime( 9704): at android.os.HandlerThread.run(HandlerThread.java:61)
The mentioned permission is in the AndroidManifest.xml (as it was decompiled from the original app).
I need help from an experienced developer. If we could get this fixed, we can setup our own custom ROM, based on the most current Chinese version, including all English translations and what else we want to.
Click to expand...
Click to collapse
So, I now got the the cause of the problem:
Code:
W/PackageManager( 432): System package com.huami.watch.sport signature changed; retaining data.
W/PackageManager( 432): Package com.huami.watch.sport desires unavailable shared library com.google.android.wearable; ignoring!
W/PackageManager( 432): Unknown permission com.huami.watch.companion.permission.READ_SETTINGS in package com.huami.watch.sport
W/PackageManager( 432): Unknown permission com.huami.watch.companion.permission.WRITE_SETTINGS in package com.huami.watch.sport
W/PackageManager( 432): Not granting permission android.permission.WRITE_SECURE_SETTINGS to package com.huami.watch.sport (protectionLevel=50 flags=0x8be45)
W/PackageManager( 432): Not granting permission android.permission.CHANGE_CONFIGURATION to package com.huami.watch.sport (protectionLevel=50 flags=0x8be45)
W/PackageManager( 432): Not granting permission android.permission.DEVICE_POWER to package com.huami.watch.sport (protectionLevel=2 flags=0x8be45)
W/PackageManager( 432): Not granting permission com.huami.watch.permission.READ_USER_SETTINGS to package com.huami.watch.sport (protectionLevel=2 flags=0x8be45)
W/PackageManager( 432): Unknown permission com.huami.watch.companion.permission.READ_SETTINGS in package com.huami.watch.sport
W/PackageManager( 432): Unknown permission com.huami.watch.companion.permission.WRITE_SETTINGS in package com.huami.watch.sport
W/PackageManager( 432): Not granting permission android.permission.WRITE_SECURE_SETTINGS to package com.huami.watch.sport (protectionLevel=50 flags=0x8be45)
W/PackageManager( 432): Not granting permission android.permission.CHANGE_CONFIGURATION to package com.huami.watch.sport (protectionLevel=50 flags=0x8be45)
W/PackageManager( 432): Not granting permission android.permission.DEVICE_POWER to package com.huami.watch.sport (protectionLevel=2 flags=0x8be45)
W/PackageManager( 432): Not granting permission com.huami.watch.permission.READ_USER_SETTINGS to package com.huami.watch.sport (protectionLevel=2 flags=0x8be45)
So, that is why the application is force closing, ok. Now the question is, how to solve this. I would like to have an experienced ROM developer help me here.
OK, if someone is interested: I now understand why the permissions are not granted. It is the signature of the apk (which I needed to resign). For some permissions this signature must be identical with the signature of the platform. This key only Huami has.
So, what can be done? I am currently thinking of patching the PackageManager, so that it will not deny the permission. Not sure, if this is possible, but I will try.
Neuer_User said:
OK, if someone is interested: I now understand why the permissions are not granted. It is the signature of the apk (which I needed to resign). For some permissions this signature must be identical with the signature of the platform. This key only Huami has.
So, what can be done? I am currently thinking of patching the PackageManager, so that it will not deny the permission. Not sure, if this is possible, but I will try.
Click to expand...
Click to collapse
I can't help you to develop, I have no knowledge, but I can be a tester when ready!
Inviato dal mio D6633 utilizzando Tapatalk
Pi3rluigi said:
I can't help you to develop, I have no knowledge, but I can be a tester when ready!
Inviato dal mio D6633 utilizzando Tapatalk
Click to expand...
Click to collapse
Thanks for the offer. Main work currently is getting the knowledge on howto deodex files, mod them, re-odex them. Then I can try to exchange the Package Manager on my watch. All of this is only temporary, so even if nothing will work afterwards, a simple reboot will fix it.
Some more info, on how my planned "non-intrusive" changes will work:
- The watch will need to be booted via a fastboot command. That loads a customized boot image. The boot image will mount all filesystems and then start the processes.
- However, after all filesystems have been mounted, it will mount the custom rom over the system partition. So, instead of using the system image, the watch will use the custom ROM.
- The custom ROM will reside as one single file on the /sdcard. So there are no modifications to the system partition (and neither to the boot partition).
- After a reboot, the normal boot image is booted again, which will also not mount the custom ROM.
- If you reboot via fastboot, the modded boot.img can be booted, which will mount the custom ROM again.
The nice thing with this is, that all modifications are temporary. If something is borked up, the device cannot boot or goes into a boot loop, it doesn't matter. You simply turn the watch off and on again, and everything is back to unmodified.
So far, this seems to be working. I now need to get a working custom ROM. That is, I need to understand how to modify the apps, so deodexing, decompiling, recompiling, signing, etc.
I will probably open an open source GitHub project, as soon as I have something usable. Then people can contribute translating and modding.
Neuer_User said:
Some more info, on how my planned "non-intrusive" changes will work:
So far, this seems to be working. I now need to get a working custom ROM. That is, I need to understand how to modify the apps, so deodexing, decompiling, recompiling, signing, etc.
Click to expand...
Click to collapse
Hi!
I've just translated chinese fw to russian and switched watch to kilometers everywhere and resolve some interface bugs. )) It was easy and i can give some advices if you need.
silver-alx said:
Hi!
I've just translated chinese fw to russian and switched watch to kilometers everywhere and resolve some interface bugs. )) It was easy and i can give some advices if you need.
Click to expand...
Click to collapse
If you could describe, how you did it, that would be very helpful. Maybe even upload your original and modified firmware, so we can take a look at the differences?
Thanks!
Related
I'm sure this is thr wrong section but its hard finding the right forum on this app so I'm sorry to any mod to has to fix that.
Im using cyanogenmod 5.0.8 for quite a long
time now but suddenly youtube app keeps
force closing, i solved this by going to system/
apps and just reinstalling it but now its going
back to force closing as soon as iv exited it and
relaunched it...
I then tried restoring a backup but this has not
worked, i then updated the youtube app to the
new youtube app from gingerbread or froyo
cant remember but this does the same thing,
fix permissions just totaly f**ked my phone
and i had to restore my backup again.
So does anyone know how i can fix this issue?
Sent from my HTC Dream using XDA App
This is the red errors from logcat moments after it force closing, iv discovered that the you tube app seems to work fine so long as I'm not signed in but as soon as iv signed in with my gmail account and iv exited the app I imedidiatly tested it and its back to force closing.
W/dalvikvm( 5831): threadid=3: thread exiting
with uncaught exception (group=0x4001e178)
E/AndroidRuntime( 5831): Uncaught handler:
thread main exiting due to uncaught exception
E/AndroidRuntime( 5831):
java.lang.IllegalArgumentException: activity is
null
E/AndroidRuntime( 5831): at
android.accounts.AccountManager.getAuthToken
(AccountManager.java:503)
E/AndroidRuntime( 5831): at at.run
(SourceFile:406)
E/AndroidRuntime( 5831): at
android.accounts.AccountManager$9.run
(AccountManager.java:812)
E/AndroidRuntime( 5831): at
android.os.Handler.handleCallback
(Handler.java:587)
E/AndroidRuntime( 5831): at
android.os.Handler.dispatchMessage
(Handler.java:92)
E/AndroidRuntime( 5831): at
android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime( 5831): at
android.app.ActivityThread.main
(ActivityThread.java:4363)
E/AndroidRuntime( 5831): at
java.lang.reflect.Method.invokeNative(Native
Method)
E/AndroidRuntime( 5831): at
java.lang.reflect.Method.invoke
(Method.java:521)
E/AndroidRuntime( 5831): at
com.android.internal.os.ZygoteInit
$MethodAndArgsCaller.run(ZygoteInit.java:860)
E/AndroidRuntime( 5831): at
com.android.internal.os.ZygoteInit.main
(ZygoteInit.java:618)
E/AndroidRuntime( 5831): at
dalvik.system.NativeStart.main(Native Method)
Sent from my HTC Dream using XDA App
hey guys it's been like 2 days no when i try to unlock my phone the screen freezes..
sometimes i get this?
java.lang.SecurityException: Permission Denial: opening provider com.google.android.gm.provider.MailProvider from ProcessRecord{407c6ed8 1761:com.sec.android.app.twlauncher/10032} (pid=1761, uid=10032) requires com.google.android.gm.permission.READ_GMAIL or com.google.android.gm.permission.WRITE_GMAIL
at android.os.Parcel.readException(Parcel.java:1322)
at android.os.Parcel.readException(Parcel.java:1276)
at android.app.ActivityManagerProxy.getContentProvider(ActivityManagerNative.java:1882)
at android.app.ActivityThread.getProvider(ActivityThread.java:3351)
at android.app.ActivityThread.acquireProvider(ActivityThread.java:3376)
at android.app.ContextImpl$ApplicationContentResolver.acquireProvider(ContextImpl.java:1826)
at android.content.ContentResolver.acquireProvider(ContentResolver.java:748)
at android.content.ContentResolver.query(ContentResolver.java:256)
at com.sec.android.app.twlauncher.Launcher.onGmailChanged(Launcher.java:30)
at com.sec.android.app.twlauncher.GmailObserver.onChange(GmailObserver.java:23)
at android.database.ContentObserver$NotificationRunnable.run(ContentObserver.java:43)
at android.os.Handler.handleCallback(Handler.java:587)
at android.os.Handler.dispatchMessage(Handler.java:92)
at android.os.Looper.loop(Looper.java:130)
at android.app.ActivityThread.main(ActivityThread.java:3687)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:507)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:842)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:600)
at dalvik.system.NativeStart.main(Native Method)
I'm running Stock 4.1.2 with busybox installed, root, and XposedFramework.
Last night my device froze so I had to hard-reboot it. I turned it off then turned it on, it was late so I went to bed. I woke up in the morning went to pick it up and it was still on the boot screen. It was hot and after booting into recovery it said that I had only 15% battery left. I was dumbfounded. I tried to boot again, and it got stuck again. After all the trouble shooting I could think of(Including disabling and removing Xposed), I wiped my /system partition and flashed the Stock /system image. Sadly that didn't help. It seems the problem resides on my /data partition somewhere but obviously if I'm wiping that I might as well start from scratch.
Below is my Logcat. If you can gleam anything from it please let me know. I'm pretty-tech savvy but I still have zero expirience reading Logcats. At the very least I'd like to know what the error is exactly so I can endevor to avoid it in the future.
japzone said:
I'm running Stock 4.1.2 with busybox installed, root, and XposedFramework.
Last night my device froze so I had to hard-reboot it. I turned it off then turned it on, it was late so I went to bed. I woke up in the morning went to pick it up and it was still on the boot screen. It was hot and after booting into recovery it said that I had only 15% battery left. I was dumbfounded. I tried to boot again, and it got stuck again. After all the trouble shooting I could think of(Including disabling and removing Xposed), I wiped my /system partition and flashed the Stock /system image. Sadly that didn't help. It seems the problem resides on my /data partition somewhere but obviously if I'm wiping that I might as well start from scratch.
Below is my Logcat. If you can gleam anything from it please let me know. I'm pretty-tech savvy but I still have zero expirience reading Logcats. At the very least I'd like to know what the error is exactly so I can endevor to avoid it in the future.
Click to expand...
Click to collapse
Hi there ! This seems to be the problem in your case :
Code:
Sending signal. PID: 349 SIG: 9
E/AndroidRuntime( 349): *** FATAL EXCEPTION IN SYSTEM PROCESS: ActivityManager
E/AndroidRuntime( 349): java.lang.ArrayIndexOutOfBoundsException: src.length=8192 srcPos=1 dst.length=8192 dstPos=0 length=-1
E/AndroidRuntime( 349): at java.lang.System.arraycopy(Native Method)
E/AndroidRuntime( 349): at org.kxml2.io.KXmlParser.fillBuffer(KXmlParser.java:1489)
E/AndroidRuntime( 349): at org.kxml2.io.KXmlParser.skip(KXmlParser.java:1574)
E/AndroidRuntime( 349): at org.kxml2.io.KXmlParser.parseStartTag(KXmlParser.java:1049)
E/AndroidRuntime( 349): at org.kxml2.io.KXmlParser.next(KXmlParser.java:369)
E/AndroidRuntime( 349): at org.kxml2.io.KXmlParser.next(KXmlParser.java:310)
E/AndroidRuntime( 349): at com.android.server.am.UsageStatsService.readHistoryStatsFLOCK(UsageStatsService.java:376)
E/AndroidRuntime( 349): at com.android.server.am.UsageStatsService.readHistoryStatsFromFile(UsageStatsService.java:357)
E/AndroidRuntime( 349): at com.android.server.am.UsageStatsService.<init>(UsageStatsService.java:274)
E/AndroidRuntime( 349): at com.android.server.am.ActivityManagerService.<init>(ActivityManagerService.java:1534)
E/AndroidRuntime( 349): at com.android.server.am.ActivityManagerService.<init>(ActivityManagerService.java:160)
E/AndroidRuntime( 349): at com.android.server.am.ActivityManagerService$AThread.run(ActivityManagerService.java:1405)
E/AndroidRuntime( 349): Error reporting crash
E/AndroidRuntime( 349): java.lang.NullPointerException
E/AndroidRuntime( 349): at com.android.internal.os.RuntimeInit$UncaughtHandler.uncaughtException(RuntimeInit.java:76)
E/AndroidRuntime( 349): at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:693)
E/AndroidRuntime( 349): at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:690)
As you can see the lines start with E:/ which stand for error .
V stands for Verbose
I for information
D for Debug.
And some others . more about these.. I suggest you Google. Now you will ask how I found out the error ? Well if you take a closer look to the log you will notice that once the kernel is initialized ( which happens at the Google logo ) the netd framework starts booting by the kernel.
Normal boot sequence is kernel > its init.rd and init.rc then the init.d and then the framework. How I came to know all this ? Take a log of a normally booting ROM
If you again carefully observe the log .. You will notice log re iterates. It goes on an infinite loop. Hence the term boot'loop'.
The start of the loop is
Code:
AndroidRuntime( 369): >>>>>> AndroidRuntime START com.android.internal.os.ZygoteInit <<<<<<
D/AndroidRuntime( 369): CheckJNI is OFF
And this Is the dead / bad code
Code:
ygote ( 369): Exit zygote because system server (508) has terminated
I/ServiceManager( 118): service 'sensorservice' died
I/ServiceManager( 118): service 'entropy' died
I/ServiceManager( 118): service 'power' died
That's roughly how you read a logcat.
And about your problem. I suggest a clean wipe and reflash the ROM. Its always better to keep backing up your data from time to time. I also ensure I wipe clean even during flashing nightlies .
Sent from my HTC using xda app-developers app
Thanks for the reply. Nice crash course on log reading I have gone ahead and flashed a fresh install of PA ROM.
I really just wonder how the error might of happened. It occured at a bad time for me where my External Harddrive died on me taking my backups with it, and leaving me with nowhere to put new ones. My new Laptop with a 1TB drive is coming in August so I was planning on backing up and Flashing a Custom ROM then. But this error took out my device before I could make a backup. Oh well, I managed to scavenge most of my apps and hopefully will be able to restore them. Sadly I lost a day off to resuscitating my Nexus
Red Devil said:
Hi there ! This seems to be the problem in your case :
Code:
Sending signal. PID: 349 SIG: 9
E/AndroidRuntime( 349): *** FATAL EXCEPTION IN SYSTEM PROCESS: ActivityManager
E/AndroidRuntime( 349): java.lang.ArrayIndexOutOfBoundsException: src.length=8192 srcPos=1 dst.length=8192 dstPos=0 length=-1
E/AndroidRuntime( 349): at java.lang.System.arraycopy(Native Method)
E/AndroidRuntime( 349): at org.kxml2.io.KXmlParser.fillBuffer(KXmlParser.java:1489)
E/AndroidRuntime( 349): at org.kxml2.io.KXmlParser.skip(KXmlParser.java:1574)
E/AndroidRuntime( 349): at org.kxml2.io.KXmlParser.parseStartTag(KXmlParser.java:1049)
E/AndroidRuntime( 349): at org.kxml2.io.KXmlParser.next(KXmlParser.java:369)
E/AndroidRuntime( 349): at org.kxml2.io.KXmlParser.next(KXmlParser.java:310)
E/AndroidRuntime( 349): at com.android.server.am.UsageStatsService.readHistoryStatsFLOCK(UsageStatsService.java:376)
E/AndroidRuntime( 349): at com.android.server.am.UsageStatsService.readHistoryStatsFromFile(UsageStatsService.java:357)
E/AndroidRuntime( 349): at com.android.server.am.UsageStatsService.<init>(UsageStatsService.java:274)
E/AndroidRuntime( 349): at com.android.server.am.ActivityManagerService.<init>(ActivityManagerService.java:1534)
E/AndroidRuntime( 349): at com.android.server.am.ActivityManagerService.<init>(ActivityManagerService.java:160)
E/AndroidRuntime( 349): at com.android.server.am.ActivityManagerService$AThread.run(ActivityManagerService.java:1405)
E/AndroidRuntime( 349): Error reporting crash
E/AndroidRuntime( 349): java.lang.NullPointerException
E/AndroidRuntime( 349): at com.android.internal.os.RuntimeInit$UncaughtHandler.uncaughtException(RuntimeInit.java:76)
E/AndroidRuntime( 349): at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:693)
E/AndroidRuntime( 349): at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:690)
As you can see the lines start with E:/ which stand for error .
V stands for Verbose
I for information
D for Debug.
And some others . more about these.. I suggest you Google. Now you will ask how I found out the error ? Well if you take a closer look to the log you will notice that once the kernel is initialized ( which happens at the Google logo ) the netd framework starts booting by the kernel.
Normal boot sequence is kernel > its init.rd and init.rc then the init.d and then the framework. How I came to know all this ? Take a log of a normally booting ROM
If you again carefully observe the log .. You will notice log re iterates. It goes on an infinite loop. Hence the term boot'loop'.
The start of the loop is
Code:
AndroidRuntime( 369): >>>>>> AndroidRuntime START com.android.internal.os.ZygoteInit <<<<<<
D/AndroidRuntime( 369): CheckJNI is OFF
And this Is the dead / bad code
Code:
ygote ( 369): Exit zygote because system server (508) has terminated
I/ServiceManager( 118): service 'sensorservice' died
I/ServiceManager( 118): service 'entropy' died
I/ServiceManager( 118): service 'power' died
That's roughly how you read a logcat.
And about your problem. I suggest a clean wipe and reflash the ROM. Its always better to keep backing up your data from time to time. I also ensure I wipe clean even during flashing nightlies .
Sent from my HTC using xda app-developers app
Click to expand...
Click to collapse
Hi!
I changed chrulri's DroidTV DVB viewer application to my needs:
1. Changed dvb stream backend from dvblast to MuMuDVB (changed udp unicast to http unicast)
2. Did not try anymore to play the channel on app, now you can choose the video player (no codec problems, Brazilian ISDB-T latm-aac/AVC support)
3. Reception status information displayed
4. Notification to rapidly stop the stream server.
What you need to run:
1. Rooted phone
2. DVB-T (ISDB-T) kernel module drivers (loaded!).
How:
1. Plug your dvb device (with a otg cable)
2. Run the program
3. Grant root access
4. Scan for channels
5. Select a channel to stream
6. Touch on "open player"
7. Select the player to use (I like bsplayer)
8. Enjoy live FTA DTV
*** All thanks to chrulri!!!
Source: https://github.com/OuNao/droidtv/tree/mumudvb
getting FC with this apk:
D/ChannelsActivity( 3136): watchChannel(0): BBC ONE Lon
I/Timeline( 3136): Timeline: Activity_launch_request id:com.chrulri.droidtv time:23860947
I/ActivityManager( 2588): START u0 {cmp=com.chrulri.droidtv/.StreamActivity (has extras)} from pid 3136
E/dalvikvm( 3136): Could not find class 'android.support.v4.app.NotificationCompat$Builder', referenced from method com.chrulri.droidtv.StreamActivity.addNotification
W/dalvikvm( 3136): VFY: unable to resolve new-instance 24 (Landroid/support/v4/app/NotificationCompat$Builder in Lcom/chrulri/droidtv/StreamActivity;
D/dalvikvm( 3136): VFY: replacing opcode 0x22 at 0x0000
D/dalvikvm( 3136): DexOpt: unable to opt direct call 0x0020 at 0x02 in Lcom/chrulri/droidtv/StreamActivity;.addNotification
D/StreamActivity( 3136): onCreate
D/AndroidRuntime( 3136): Shutting down VM
W/dalvikvm( 3136): threadid=1: thread exiting with uncaught exception (group=0x416d2ce0)
E/AndroidRuntime( 3136): FATAL EXCEPTION: main
E/AndroidRuntime( 3136): Process: com.chrulri.droidtv, PID: 3136
E/AndroidRuntime( 3136): java.lang.NoClassDefFoundError: android.support.v4.app.NotificationCompat$Builder
E/AndroidRuntime( 3136): at com.chrulri.droidtv.StreamActivity.addNotification(StreamActivity.java:212)
E/AndroidRuntime( 3136): at com.chrulri.droidtv.StreamActivity.onCreate(StreamActivity.java:94)
E/AndroidRuntime( 3136): at android.app.Activity.performCreate(Activity.java:5231)
E/AndroidRuntime( 3136): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1087)
E/AndroidRuntime( 3136): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2169)
E/AndroidRuntime( 3136): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2271)
E/AndroidRuntime( 3136): at android.app.ActivityThread.access$800(ActivityThread.java:144)
E/AndroidRuntime( 3136): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1205)
E/AndroidRuntime( 3136): at android.os.Handler.dispatchMessage(Handler.java:102)
E/AndroidRuntime( 3136): at android.os.Looper.loop(Looper.java:136)
E/AndroidRuntime( 3136): at android.app.ActivityThread.main(ActivityThread.java:5146)
E/AndroidRuntime( 3136): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 3136): at java.lang.reflect.Method.invoke(Method.java:515)
E/AndroidRuntime( 3136): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:796)
E/AndroidRuntime( 3136): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:612)
E/AndroidRuntime( 3136): at dalvik.system.NativeStart.main(Native Method)
W/ActivityManager( 2588): Force finishing activity com.chrulri.droidtv/.StreamActivity
W/ActivityManager( 2588): Force finishing activity com.chrulri.droidtv/.ChannelsActivity
according to http://igordcard.blogspot.co.uk/2013/05/android-latest-sdk-javalangclassnotfoun.html To fix this, developers must now explicitly export the Android Private Libraries.
Fix:
Open the properties of your Android projects (even the ones that are included by other projects), select Java Build Path, Order and Export, and finally check Android Private Libraries.
I am new to android development, I have android studio though, is the above correct and easy to do?
well to answer my own post, I fixed that problem and rebuilt the apk, vlc and mxplayer are offered as media players when the stream starts by neither can play it. I have bsplayer installed but that is not offered as an option for some reason. I believe that dvb-t in the uk is mpeg2, so either none of the players can play the stream or the kernel modules that I built are streaming garbage. the dongle works find on my linux laptop with me-tv.
going to try some other players now, not sure how to check a valid stream is being produced though.
Could you please share your repaired apk? thank you
scote said:
well to answer my own post, I fixed that problem and rebuilt the apk, vlc and mxplayer are offered as media players when the stream starts by neither can play it. I have bsplayer installed but that is not offered as an option for some reason. I believe that dvb-t in the uk is mpeg2, so either none of the players can play the stream or the kernel modules that I built are streaming garbage. the dongle works find on my linux laptop with me-tv.
going to try some other players now, not sure how to check a valid stream is being produced though.
Click to expand...
Click to collapse
Thank you for the tip. I will change de code.
The streamActivity initiate a intent with a url of type video/mpeg, any program with intent filter set to get a http (mumudvb branch, not master!!!) url of video/mpeg type must be offered...
What kernel version you are using. I compiled the mumudvb binary with kernel 3.4 headers. Maybe the mumudvb backend used can´t work with your kernel modules...
sfortier, could you rebuild all native binaries adding to CFLAGS and LDFLAGS "-fPIE -pie", so your setup would run on any Android 5+?
I already did that for w_scan, dvblast and dvblastctl, but since you did not include instructions how to download and build MuMuDVB for android I can not do it myself.
Thanks in advance.
t_i_t_o said:
sfortier, could you rebuild all native binaries adding to CFLAGS and LDFLAGS "-fPIE -pie", so your setup would run on any Android 5+?
I already did that for w_scan, dvblast and dvblastctl, but since you did not include instructions how to download and build MuMuDVB for android I can not do it myself.
Thanks in advance.
Click to expand...
Click to collapse
Hi,
MuMuDVB repository now has instructions to build for android...
Hi,
Seeing as the version w_scan is not available to download, could someone recompile this with the latest version and create an APK?
Especially to run on a 5+ Android phone, with PIE.
Thanks,
E
I'm having the same problem. Except I can't use the phone at all. I took the SIM card out of the micro sd port where the phone has been working somehow. It was a qlink wireless phone. I put the SIM card in the appropriate spot and factory reset it and now it is saying Unfortunately the Process.com.android.phone Has Stopped. Non-stop. It sometimes stops most of the time it's on the screen 24/7. Idk what to do. I want to use this phone. Please help.
Same Thing (Sprint Prepaid)
I am having the same issue as well, my phone was running crappy so i had performed a factory reset, upon reboot i have been receiving the com.android.phone repeatedly, and its no longer registering with the Sprint prepaid service. From there i decided to enable USB debugging to see if i could get some kind of info with "adb logcat" and this is what i received:
I/ActivityManager( 803): Process com.android.phone (pid 8149) has died.
I/com.skyfire.browser.toolbar.ProcessObserverService( 1302): On process died 8149,1001
I/ActivityManager( 803): Start proc com.android.phone for restart com.android.phone: pid=8196 uid=1001 gids={41001, 3004, 3009, 3005, 1006, 3002, 3001, 3003, 1028, 1015}
V/PhoneApp( 8196): onCreate()...
D/ItsOnAPI( 8196): Unable to load ItsOnOemApi implementation: java.lang.ClassNotFoundException: Didn't find class "com.itsoninc.android.impl.ItsOnOem" on path: DexPathList[[],nativeLibraryDirectories=[/vendor/lib, /system/lib]]
I/ItsOnAPI( 8196): ItsOn is not enabled
I/RoamingUtils( 8196): loadOdmSettings loaded:0
I/RoamingUtils( 8196): load odm settings start:
I/RoamingUtils( 8196): load odm settings node:./Customization/RoamPreference/HomeOnly value:0
I/RoamingUtils( 8196): load odm settings node:./Customization/RoamPreference/MenuDisplay value:1
I/RoamingUtils( 8196): load odm settings node:./SPA/DomDataGuard/Enabled value:N
I/RoamingUtils( 8196): load odm settings node:./SPA/DomVoiceGuard/Enabled value:Y
I/RoamingUtils( 8196): load odm settings domVoRoam:null domDaRoam:null domVoRoamGd:Y domDaRoamGd:N homeOnly:0 showMemu:1
W/dalvikvm( 8196): threadid=1: thread exiting with uncaught exception (group=0x415cbd58)
E/AndroidRuntime( 8196): FATAL EXCEPTION: main
E/AndroidRuntime( 8196): Process: com.android.phone, PID: 8196
E/AndroidRuntime( 8196): java.lang.RuntimeException: Unable to create application com.android.phone.PhoneApp: java.lang.NumberFormatException: Invalid int: "Y"
E/AndroidRuntime( 8196): at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4439)
E/AndroidRuntime( 8196): at android.app.ActivityThread.access$1600(ActivityThread.java:145)
E/AndroidRuntime( 8196): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1288)
E/AndroidRuntime( 8196): at android.os.Handler.dispatchMessage(Handler.java:102)
E/AndroidRuntime( 8196): at android.os.Looper.loop(Looper.java:136)
E/AndroidRuntime( 8196): at android.app.ActivityThread.main(ActivityThread.java:5109)
E/AndroidRuntime( 8196): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 8196): at java.lang.reflect.Method.invoke(Method.java:515)
E/AndroidRuntime( 8196): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:800)
E/AndroidRuntime( 8196): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)
E/AndroidRuntime( 8196): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime( 8196): Caused by: java.lang.NumberFormatException: Invalid int: "Y"
E/AndroidRuntime( 8196): at java.lang.Integer.invalidInt(Integer.java:137)
E/AndroidRuntime( 8196): at java.lang.Integer.parse(Integer.java:374)
E/AndroidRuntime( 8196): at java.lang.Integer.parseInt(Integer.java:365)
E/AndroidRuntime( 8196): at java.lang.Integer.parseInt(Integer.java:331)
E/AndroidRuntime( 8196): at java.lang.Integer.valueOf(Integer.java:489)
E/AndroidRuntime( 8196): at com.android.internal.telephony.RoamingUtils.loadOdmSettings(RoamingUtils.java:315)
E/AndroidRuntime( 8196): at com.android.internal.telephony.cdma.CdmaServiceStateTracker.<init>(CdmaServiceStateTracker.java:277)
E/AndroidRuntime( 8196): at com.android.internal.telephony.cdma.CdmaLteServiceStateTracker.<init>(CdmaLteServiceStateTracker.java:90)
E/AndroidRuntime( 8196): at com.android.internal.telephony.cdma.CDMALTEPhone.initSstIcc(CDMALTEPhone.java:104)
E/AndroidRuntime( 8196): at com.android.internal.telephony.cdma.CDMAPhone.<init>(CDMAPhone.java:162)
E/AndroidRuntime( 8196): at com.android.internal.telephony.cdma.CDMALTEPhone.<init>(CDMALTEPhone.java:83)
E/AndroidRuntime( 8196): at com.android.internal.telephony.PhoneFactory.makeDefaultPhone(PhoneFactory.java:129)
E/AndroidRuntime( 8196): at com.android.internal.telephony.PhoneFactory.makeDefaultPhones(PhoneFactory.java:57)
E/AndroidRuntime( 8196): at com.android.phone.PhoneGlobals.onCreate(PhoneGlobals.java:549)
E/AndroidRuntime( 8196): at com.android.phone.PhoneApp.onCreate(PhoneApp.java:44)
E/AndroidRuntime( 8196): at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1007)
E/AndroidRuntime( 8196): at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4436)
E/AndroidRuntime( 8196): ... 10 more
W/ActivityManager( 803): Process com.android.phone has crashed too many times: killing!
E/RLOG ( 7954): command timed out pid:8062
It appears that it has something to do with an invalid variable "Y" not being an integer. I am not super familiar with the Android OS, and have only dabbled with it briefly, but i am assuming the problem has been caused by the stock Recovery not wiping the cache on factory reset. Also im assuming that without root access and fastboot working, clearing the cache via ADB isn't going to work either . But as it stands right now I have 2 bricked phones and I just started freelancing, so i am going to be forced into figuring this out, because i need a phone. That's all the insight i can provide as of now, hopefully somebody else around here has more experience in the matter and can give us a hand.
I also experienced the same thing
I need twrp backup for recovery
hi
Your baseband is unknown ?
hoost3in said:
I am having the same issue as well, my phone was running crappy so i had performed a factory reset, upon reboot i have been receiving the com.android.phone repeatedly, and its no longer registering with the Sprint prepaid service. From there i decided to enable USB debugging to see if i could get some kind of info with "adb logcat" and this is what i received:
I/ActivityManager( 803): Process com.android.phone (pid 8149) has died.
I/com.skyfire.browser.toolbar.ProcessObserverService( 1302): On process died 8149,1001
I/ActivityManager( 803): Start proc com.android.phone for restart com.android.phone: pid=8196 uid=1001 gids={41001, 3004, 3009, 3005, 1006, 3002, 3001, 3003, 1028, 1015}
V/PhoneApp( 8196): onCreate()...
D/ItsOnAPI( 8196): Unable to load ItsOnOemApi implementation: java.lang.ClassNotFoundException: Didn't find class "com.itsoninc.android.impl.ItsOnOem" on path: DexPathList[[],nativeLibraryDirectories=[/vendor/lib, /system/lib]]
I/ItsOnAPI( 8196): ItsOn is not enabled
I/RoamingUtils( 8196): loadOdmSettings loaded:0
I/RoamingUtils( 8196): load odm settings start:
I/RoamingUtils( 8196): load odm settings node:./Customization/RoamPreference/HomeOnly value:0
I/RoamingUtils( 8196): load odm settings node:./Customization/RoamPreference/MenuDisplay value:1
I/RoamingUtils( 8196): load odm settings node:./SPA/DomDataGuard/Enabled value:N
I/RoamingUtils( 8196): load odm settings node:./SPA/DomVoiceGuard/Enabled value:Y
I/RoamingUtils( 8196): load odm settings domVoRoam:null domDaRoam:null domVoRoamGd:Y domDaRoamGd:N homeOnly:0 showMemu:1
W/dalvikvm( 8196): threadid=1: thread exiting with uncaught exception (group=0x415cbd58)
E/AndroidRuntime( 8196): FATAL EXCEPTION: main
E/AndroidRuntime( 8196): Process: com.android.phone, PID: 8196
E/AndroidRuntime( 8196): java.lang.RuntimeException: Unable to create application com.android.phone.PhoneApp: java.lang.NumberFormatException: Invalid int: "Y"
E/AndroidRuntime( 8196): at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4439)
E/AndroidRuntime( 8196): at android.app.ActivityThread.access$1600(ActivityThread.java:145)
E/AndroidRuntime( 8196): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1288)
E/AndroidRuntime( 8196): at android.os.Handler.dispatchMessage(Handler.java:102)
E/AndroidRuntime( 8196): at android.os.Looper.loop(Looper.java:136)
E/AndroidRuntime( 8196): at android.app.ActivityThread.main(ActivityThread.java:5109)
E/AndroidRuntime( 8196): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 8196): at java.lang.reflect.Method.invoke(Method.java:515)
E/AndroidRuntime( 8196): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:800)
E/AndroidRuntime( 8196): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)
E/AndroidRuntime( 8196): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime( 8196): Caused by: java.lang.NumberFormatException: Invalid int: "Y"
E/AndroidRuntime( 8196): at java.lang.Integer.invalidInt(Integer.java:137)
E/AndroidRuntime( 8196): at java.lang.Integer.parse(Integer.java:374)
E/AndroidRuntime( 8196): at java.lang.Integer.parseInt(Integer.java:365)
E/AndroidRuntime( 8196): at java.lang.Integer.parseInt(Integer.java:331)
E/AndroidRuntime( 8196): at java.lang.Integer.valueOf(Integer.java:489)
E/AndroidRuntime( 8196): at com.android.internal.telephony.RoamingUtils.loadOdmSettings(RoamingUtils.java:315)
E/AndroidRuntime( 8196): at com.android.internal.telephony.cdma.CdmaServiceStateTracker.<init>(CdmaServiceStateTracker.java:277)
E/AndroidRuntime( 8196): at com.android.internal.telephony.cdma.CdmaLteServiceStateTracker.<init>(CdmaLteServiceStateTracker.java:90)
E/AndroidRuntime( 8196): at com.android.internal.telephony.cdma.CDMALTEPhone.initSstIcc(CDMALTEPhone.java:104)
E/AndroidRuntime( 8196): at com.android.internal.telephony.cdma.CDMAPhone.<init>(CDMAPhone.java:162)
E/AndroidRuntime( 8196): at com.android.internal.telephony.cdma.CDMALTEPhone.<init>(CDMALTEPhone.java:83)
E/AndroidRuntime( 8196): at com.android.internal.telephony.PhoneFactory.makeDefaultPhone(PhoneFactory.java:129)
E/AndroidRuntime( 8196): at com.android.internal.telephony.PhoneFactory.makeDefaultPhones(PhoneFactory.java:57)
E/AndroidRuntime( 8196): at com.android.phone.PhoneGlobals.onCreate(PhoneGlobals.java:549)
E/AndroidRuntime( 8196): at com.android.phone.PhoneApp.onCreate(PhoneApp.java:44)
E/AndroidRuntime( 8196): at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1007)
E/AndroidRuntime( 8196): at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4436)
E/AndroidRuntime( 8196): ... 10 more
W/ActivityManager( 803): Process com.android.phone has crashed too many times: killing!
E/RLOG ( 7954): command timed out pid:8062
It appears that it has something to do with an invalid variable "Y" not being an integer. I am not super familiar with the Android OS, and have only dabbled with it briefly, but i am assuming the problem has been caused by the stock Recovery not wiping the cache on factory reset. Also im assuming that without root access and fastboot working, clearing the cache via ADB isn't going to work either . But as it stands right now I have 2 bricked phones and I just started freelancing, so i am going to be forced into figuring this out, because i need a phone. That's all the insight i can provide as of now, hopefully somebody else around here has more experience in the matter and can give us a hand.
Click to expand...
Click to collapse
Ever make any progress on this? This is the second time this happened to me and I don't want to wait another week for sprint to replace it again! What kind of pos can't be factory reset without basically bricking the phone!
binthe920 said:
Ever make any progress on this? This is the second time this happened to me and I don't want to wait another week for sprint to replace it again! What kind of pos can't be factory reset without basically bricking the phone!
Click to expand...
Click to collapse
Wondering the same as well.
I have the same problem and I can't even go to Sprint, as I don't have service with them
Please help
Solved, sort of, restore a working backup.
The only solution I could get to work is to root using the new aio app method that also installs TWRP. Someone was kind enough to share a functional backup at that point which I restored to mine. Pretty sad that Sharp and Sprint released a phone that you can't factory reset. It's not my backup to share but if you do a search you should be able to find someone to share theirs with you.
binthe920 said:
The only solution I could get to work is to root using the new aio app method that also installs TWRP. Someone was kind enough to share a functional backup at that point which I restored to mine. Pretty sad that Sharp and Sprint released a phone that you can't factory reset. It's not my backup to share but if you do a search you should be able to find someone to share theirs with you.
Click to expand...
Click to collapse
Can you tell me exactly which tool you used to root and custom recovery?
Is it this one? http://androidforums.com/threads/tool-aio-root-unroot-and-recovery-installer-gui-edition.705515/
I know you won't share that other person's backup, but can you send me your own?