Related
Hi.
Summary: the AndroidRuntime process fails when starting the Connectivity Service, causing my phone into a boot loop.
Sorry for the very verbose post.
Background: I've spent quite a bit of time trying to resolve a problem that causes my Sony Ericsson Xperia X10 Mini (from O2) to go into a boot loop. I've rooted the phone some time ago using this process: (sorry the forum prevents me from posting link, please copy and paste this: android.doshaska.net/x10miniroot).
I then proceeded to remove some of the redundant programs from /system/app.
Everything worked fine for several weeks until the phone started complaining about the storage being filled up. I could see that /data was getting full and I suspected that the K9 email client I had installed was using lots f space to keep the IMAP folders synced.
I can't remember if the phone rebooted itself or if I did it manually, but it never managed to boot up again, and is ever since stuck at the Sony Ericsson logo.
adb logcat tells me that the AndroidRuntime process fails when starting the Connectivity Service. It's stuck in this loop, but I've isolated one single loop in the attachment logcat.txt. The crash file references has been attached as 1279210811.txt.
The final fatal crash is:
I/SystemServer( 1297): Starting Connectivity Service.
W/dalvikvm( 1297): threadid=51: thread exiting with uncaught exception (group=0x2aac9a28)
E/AndroidRuntime( 1297): Uncaught handler: thread ConnectivityThread exiting due to uncaught exception
E/AndroidRuntime( 1297): *** EXCEPTION IN SYSTEM PROCESS. System will crash.
E/AndroidRuntime( 1297): java.lang.NullPointerException
E/AndroidRuntime( 1297): at android.app.ActivityThread.getProvider(ActivityThread.java:3938)
E/AndroidRuntime( 1297): at android.app.ActivityThread.acquireProvider(ActivityThread.java:3967)
E/AndroidRuntime( 1297): at android.app.ApplicationContext$ApplicationContentResolver.acquireProvider(ApplicationContext.java:1527)
E/AndroidRuntime( 1297): at android.content.ContentResolver.acquireProvider(ContentResolver.java:579)
E/AndroidRuntime( 1297): at android.content.ContentResolver.query(ContentResolver.java:147)
E/AndroidRuntime( 1297): at android.provider.Settings$NameValueCache.getString(Settings.java:476)
E/AndroidRuntime( 1297): at android.provider.Settings$Secure.getString(Settings.java:1701)
E/AndroidRuntime( 1297): at android.provider.Settings$Secure.getInt(Settings.java:1741)
E/AndroidRuntime( 1297): at com.android.server.ConnectivityService.getPersistedNetworkPreference(ConnectivityService.java:182)
E/AndroidRuntime( 1297): at com.android.server.ConnectivityService.<init>(ConnectivityService.java:123)
E/AndroidRuntime( 1297): at com.android.server.ConnectivityService.<init>(ConnectivityService.java:47)
E/AndroidRuntime( 1297): at com.android.server.ConnectivityService$ConnectivityThread.run(ConnectivityService.java:87)
I've had a look at the JavDoc for android.app.ActivityThread.getProvider, but I've not been able to find any useful information. I have to guess that the start-up process fails to read the provider (network) specific settings for some reason. I don't have a clue whether the source is a file, database or something else.
A wild guess is that something got corrupted when the data partition filled up. There are some upset earlier in the log (line 180) when the PackageManager is reading an XML file that relates to the PackageManager settings that seems to have been corrupted:
E/PackageManager( 1297): Error reading package manager settings E/PackageManager( 1297): org.xmlpull.v1.XmlPullParserException:
Premature end of document. (position:line -1, column -1) caused by:
org.apache.harmony.xml.ExpatParser$ParseException: At line 1, column 0: no element found
I've seen a few similar posts, but nothing exactly like this nor anything that I could use to resolve it.
Stupid section
I've got myself into this through a combination of stupidity and bad luck. I've backed up all .APK that I've removed and created a log of what I removed (that I'm still looking for). I thought this was all that I needed and I don't have a full backup.
Unfortunately, the root access now gives me a segmentation fault and the root process requires the GUI to work, so I can't repeat the process. I don't want to try another root process before I've tried what I can to get the phone back in a reasonable state.
Fortunately, I still have full adb access, so I have visibility and some control over the phone.
Any help on this would be much appreciated. At least I've saved you the time pointing out that I'm an idiot not doing a full backup
Regards,
Dan
I am very happy to propose you my first custom rom for the HTC JetStream! This rom is based on the released rom from AT&T 1.30.502.1 and should work for both American and Canadian tabs. The system has been made as light as possible and all "unnecessary" application has been removed.READ CAREFULLY:
This rom does NOT include any kernel but works exclusively with DoomLord Kernel v1
Installing this rom will WIPE your device but can be done if this feature is needed
You need [URL="http://forum.xda-developers.com/showthread.php?t=1418084"]ClockWorkMOD [/URL]to install this ROM
You are doing this at your own risks
Rom Description:
This rom is my daily driver, I like my tablet, clean without any bloatware or unneccessary app or widgets from AT&T or HTC
Zipaligned / Deodexed
Rooted - latest version
Removed all unnecessary applications - see second post
Latest version 2.03.10:
Careful, this version will WIPE your device, make a backup!
Careful, the new version will WIPE your phone, make a backup!
I am not asking for donation but press the thanks button and please Vote for this thread tooCredits:
DooMLoRD for the kernel and CWM
mendozinas, for his online kitchen
dsixda, for his kitchen
Before asking a question, use this button
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and watch this , thanks:
v2.03.10
New Boot animation
Roboto fonts included
Battery in %
Ad-Away an No-Frill included
All bloatware removed
Phone functions enabled
Tethering activated
Rooted
Latest Market
Busybox installed
Zipaligned
Fully de-odexed
Frequently Asked Questions:
Will this rom work with the default kernel?
Most probably yes but...
Wi-Fi will be broken
Can I revert to the default kernel on this rom?
Yes now you can! but follow the steps and I won't babysit
Download the file from my site called: Jetstream_OsiMood_DefaultKernelFiles.rar
Inside you will find 2 files JetStream_OsiMood_DefaultKernel_WiFi_Module.zip and defaultBoot.img
Once those two files unzipped in a folder
Move the zip file to your SD-Card
Once done, reboot in bootloader: adb reboot bootloader
Now time to flash the default kernel: fastboot flash boot defaultBoot.img
Now go in recovery and install the attached zip, the patch will install the correct WiFi module and wipe your cache
Reboot, you have now the default kernel running and WiFi working
Try to reboot in recovery if it does not work just re-install the DooMLoRD recovery
Nice work - looking forward to flashing this tonight!
FYI - Link currently broken on DL page.
tyrannos said:
Nice work - looking forward to flashing this tonight!
FYI - Link currently broken on DL page.
Click to expand...
Click to collapse
I know for the link, working on it... will let you know when back up
it's great to see some movement here. one question - why must it work with doomlords kernel? that thing is quite unstable..
guru_shastri said:
it's great to see some movement here. one question - why must it work with doomlords kernel? that thing is quite unstable..
Click to expand...
Click to collapse
Simply because it is working smoothly for me @1.8ghz and that is more than enough
The link is up
Downloading now, looking forward to trying this one!
Wait, so this will still work with the stock kernel, right?
guru_shastri said:
it's great to see some movement here. one question - why must it work with doomlords kernel? that thing is quite unstable..
Click to expand...
Click to collapse
Gotta agree here, its great to see a custom rom for this device but after spending an hour reverting and wiping back to stock kernel just yesterday because of 2 weeks of rebooting and freezes with the custom kernal, I'd be really hesitant to go back to it.
I would absolutely love to see an option to stick with stock kernel if possible. Thanks for the work on this rom, its great to finally see some movement on this forum!
Sent from my HTC PG09410 using XDA
dcd17 said:
Gotta agree here, its great to see a custom rom for this device but after spending an hour reverting and wiping back to stock kernel just yesterday because of 2 weeks of rebooting and freezes with the custom kernal, I'd be really hesitant to go back to it.
I would absolutely love to see an option to stick with stock kernel if possible. Thanks for the work on this rom, its great to finally see some movement on this forum!
Sent from my HTC PG09410 using XDA
Click to expand...
Click to collapse
I am going to see what I can do for that as it seems I am also facing some random reboots
Market
Hello. Thanks, finally somebody have action, good to see people taking time to work with this great device.
I just download your rom and installed and runs very smooth and clean. One issue tho, the Market aka Google Play is giving me an error FC
D/AndroidRuntime( 3044): Shutting down VM
W/dalvikvm( 3044): threadid=1: thread exiting with uncaught exception (group=0x4001c798)
E/AndroidRuntime( 3044): FATAL EXCEPTION: main
E/AndroidRuntime( 3044): java.lang.NullPointerException
E/AndroidRuntime( 3044): at com.google.android.finsky.utils.Sha1Util.secureHash(Sha1Util.java:46)
E/AndroidRuntime( 3044): at com.google.android.finsky.utils.FinskyLog.scrubPii(FinskyLog.java:57)
E/AndroidRuntime( 3044): at com.google.android.finsky.services.Reconstructor.recordPackageInstalled(Reconstructor.java:139)
E/AndroidRuntime( 3044): at com.google.android.finsky.services.Reconstructor.reconstruct(Reconstructor.java:109)
E/AndroidRuntime( 3044): at com.google.android.finsky.services.ReconstructDatabaseService.updateFromReconstruct(ReconstructDatabaseService.java:135)
E/AndroidRuntime( 3044): at com.google.android.finsky.services.ReconstructDatabaseService.access$000(ReconstructDatabaseService.java:26)
E/AndroidRuntime( 3044): at com.google.android.finsky.services.ReconstructDatabaseService$1.onResponse(ReconstructDatabaseService.java:68)
E/AndroidRuntime( 3044): at com.google.android.finsky.services.ReconstructDatabaseService$1.onResponse(ReconstructDatabaseService.java:49)
E/AndroidRuntime( 3044): at com.google.android.vending.remoting.api.VendingRequest.deliverResponse(VendingRequest.java:141)
E/AndroidRuntime( 3044): at com.google.android.vending.remoting.api.VendingRequest.deliverResponse(VendingRequest.java:40)
E/AndroidRuntime( 3044): at com.android.volley.ExecutorDelivery$ResponseDeliveryRunnable.run(ExecutorDelivery.java:113)
E/AndroidRuntime( 3044): at android.os.Handler.handleCallback(Handler.java:587)
E/AndroidRuntime( 3044): at android.os.Handler.dispatchMessage(Handler.java:92)
E/AndroidRuntime( 3044): at android.os.Looper.loop(Looper.java:152)
E/AndroidRuntime( 3044): at android.app.ActivityThread.main(ActivityThread.java:4606)
E/AndroidRuntime( 3044): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 3044): at java.lang.reflect.Method.invoke(Method.java:491)
E/AndroidRuntime( 3044): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:841)
E/AndroidRuntime( 3044): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:599)
E/AndroidRuntime( 3044): at dalvik.system.NativeStart.main(Native Method)
W/ActivityManager( 300): Force finishing activity com.android.vending/com.google.android.finsky.activities.TosActivity
W/ActivityManager( 300): Force finishing activity com.android.vending/.AssetBrowserActivity
D/ActivityManager( 300): isSketcherDisabledInCurrentTask():false, ActivityRecord{40a49db8 com.android.vending/com.google.android.finsky.activities.TosActivity}
D/ViewRoot( 300): ## mIsSketcherDisabledInCurrentTask is false
D/WindowManager( 300): call linkToDeath, this=Window{4114a998 Sorry! paused=false}
dcd17 said:
Gotta agree here, its great to see a custom rom for this device but after spending an hour reverting and wiping back to stock kernel just yesterday because of 2 weeks of rebooting and freezes with the custom kernal, I'd be really hesitant to go back to it.
I would absolutely love to see an option to stick with stock kernel if possible. Thanks for the work on this rom, its great to finally see some movement on this forum!
Click to expand...
Click to collapse
You can now roll back to the default kernel
juannicolas said:
Hello. Thanks, finally somebody have action, good to see people taking time to work with this great device.
I just download your rom and installed and runs very smooth and clean. One issue tho, the Market aka Google Play is giving me an error FC
Code:
D/AndroidRuntime( 3044): Shutting down VM
W/dalvikvm( 3044): threadid=1: thread exiting with uncaught exception (group=0x4001c798)
E/AndroidRuntime( 3044): FATAL EXCEPTION: main
E/AndroidRuntime( 3044): java.lang.NullPointerException
E/AndroidRuntime( 3044): at com.google.android.finsky.utils.Sha1Util.secureHash(Sha1Util.java:46)
E/AndroidRuntime( 3044): at com.google.android.finsky.utils.FinskyLog.scrubPii(FinskyLog.java:57)
E/AndroidRuntime( 3044): at com.google.android.finsky.services.Reconstructor.recordPackageInstalled(Reconstructor.java:139)
E/AndroidRuntime( 3044): at com.google.android.finsky.services.Reconstructor.reconstruct(Reconstructor.java:109)
E/AndroidRuntime( 3044): at com.google.android.finsky.services.ReconstructDatabaseService.updateFromReconstruct(ReconstructDatabaseService.java:135)
E/AndroidRuntime( 3044): at com.google.android.finsky.services.ReconstructDatabaseService.access$000(ReconstructDatabaseService.java:26)
E/AndroidRuntime( 3044): at com.google.android.finsky.services.ReconstructDatabaseService$1.onResponse(ReconstructDatabaseService.java:68)
E/AndroidRuntime( 3044): at com.google.android.finsky.services.ReconstructDatabaseService$1.onResponse(ReconstructDatabaseService.java:49)
E/AndroidRuntime( 3044): at com.google.android.vending.remoting.api.VendingRequest.deliverResponse(VendingRequest.java:141)
E/AndroidRuntime( 3044): at com.google.android.vending.remoting.api.VendingRequest.deliverResponse(VendingRequest.java:40)
E/AndroidRuntime( 3044): at com.android.volley.ExecutorDelivery$ResponseDeliveryRunnable.run(ExecutorDelivery.java:113)
E/AndroidRuntime( 3044): at android.os.Handler.handleCallback(Handler.java:587)
E/AndroidRuntime( 3044): at android.os.Handler.dispatchMessage(Handler.java:92)
E/AndroidRuntime( 3044): at android.os.Looper.loop(Looper.java:152)
E/AndroidRuntime( 3044): at android.app.ActivityThread.main(ActivityThread.java:4606)
E/AndroidRuntime( 3044): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 3044): at java.lang.reflect.Method.invoke(Method.java:491)
E/AndroidRuntime( 3044): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:841)
E/AndroidRuntime( 3044): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:599)
E/AndroidRuntime( 3044): at dalvik.system.NativeStart.main(Native Method)
W/ActivityManager( 300): Force finishing activity com.android.vending/com.google.android.finsky.activities.TosActivity
W/ActivityManager( 300): Force finishing activity com.android.vending/.AssetBrowserActivity
D/ActivityManager( 300): isSketcherDisabledInCurrentTask():false, ActivityRecord{40a49db8 com.android.vending/com.google.android.finsky.activities.TosActivity}
D/ViewRoot( 300): ## mIsSketcherDisabledInCurrentTask is false
D/WindowManager( 300): call linkToDeath, this=Window{4114a998 Sorry! paused=false}
Click to expand...
Click to collapse
No clue why, empty the cache of the app and try again
This is going to sound stupid but how do you boot the device in recovery? I've loaded CWM through adb but any button combo won't work. I would really like to test out this ROM, thanks for any help!
for CWM - reset the device - and after the screen goes black press and hold vol. down.
so to install this rom we need to install the doomlord kernel and then go back to stock? or we can just install it over the stock?
can anyone actually work with the doomlord kernel to improve it? i think it was great at its base..perhapes just removing the voltage control..i think that's the problem it had.
CarpeNoctem said:
You can now roll back to the default kernel
No clue why, empty the cache of the app and try again
Click to expand...
Click to collapse
Tried that but since the app have never being opened there is no clean/clear cache option active for it.
NJFM said:
This is going to sound stupid but how do you boot the device in recovery? I've loaded CWM through adb but any button combo won't work. I would really like to test out this ROM, thanks for any help!
Click to expand...
Click to collapse
the simplest way, install this: https://play.google.com/store/apps/details?id=com.siriusapplications.quickboot&hl=en
CarpeNoctem said:
I am going to see what I can do for that as it seems I am also facing some random reboots
Click to expand...
Click to collapse
I really don't think the level is the issue. my Jetstream ran the MOST STABLE with Doomlords kernel. I had more random reboots before I ever rooted it or anything. I think Honeycomb just sux or maybe the version of Sense we have over Honeycomb sux and is waaaaay underdeveloped from factory. just my 2 cents....
Sent from my HTC Rezound™ using xda premium
k2trill said:
I really don't think the level is the issue. my Jetstream ran the MOST STABLE with Doomlords kernel. I had more random reboots before I ever rooted it or anything. I think Honeycomb just sux or maybe the version of Sense we have over Honeycomb sux and is waaaaay underdeveloped from factory. just my 2 cents....
Click to expand...
Click to collapse
Now you have the choice at least you, stock or DooMLoRD
its a fact that some devices sufford random reboots only when using the kernel. i think the kernel has a great base, and my device never ran faster - but it still crashed him.
i think it's got something to do with the Voltage control, but i can't really be sure.
Hey,
Ive got a Galaxy Tab 10.1 running stock 3.2. I encountered a strange problem with my tab today.
An app froze(google maps) - I could click the clock and the menu would roll up, it had a black screen and did nothing, so I reset the tab by long pressing power.
After this the tab got stuck at the SAMSUNG logo for a long time, so I tried another reset and then another after cleaning the connectors - the slot wasnt dirty but just in case. After I gave up and left the tab with the SAMSUNG logo for about 10 minutes it finally booted. But the weird part is that it booted like I have just performed a factory reset, but all my data is still there, all apps, heck even my background is the same.
Only thing is, that any app that has some connection to any account stored in on the tab is force closing. Its as if the accounts got corrupted.
Now this happened twice, first time I factory reset the tab and it was then ok, but a second time? I dont want to lose saved games, and stuff...
My question is, has this ever happened to anybody else? Can it be solved without data loss?
radqooo said:
Hey,
Ive got a Galaxy Tab 10.1 running stock 3.2. I encountered a strange problem with my tab today.
An app froze(google maps) - I could click the clock and the menu would roll up, it had a black screen and did nothing, so I reset the tab by long pressing power.
After this the tab got stuck at the SAMSUNG logo for a long time, so I tried another reset and then another after cleaning the connectors - the slot wasnt dirty but just in case. After I gave up and left the tab with the SAMSUNG logo for about 10 minutes it finally booted. But the weird part is that it booted like I have just performed a factory reset, but all my data is still there, all apps, heck even my background is the same.
Only thing is, that any app that has some connection to any account stored in on the tab is force closing. Its as if the accounts got corrupted.
Now this happened twice, first time I factory reset the tab and it was then ok, but a second time? I dont want to lose saved games, and stuff...
My question is, has this ever happened to anybody else? Can it be solved without data loss?
Click to expand...
Click to collapse
It happened to me 3 weeks ago, and all the applications were force closing. I had to uninstall them all, and then reinstall. I did not lose any document though.
Now, I feel that the default browser seems corrupted; Everytime I log in to Facebook, it asks me to to identify the current device.
ace81 said:
It happened to me 3 weeks ago, and all the applications were force closing. I had to uninstall them all, and then reinstall. I did not lose any document though.
Now, I feel that the default browser seems corrupted; Everytime I log in to Facebook, it asks me to to identify the current device.
Click to expand...
Click to collapse
That would make sense, the first time it happened I had the browser opened. I opened logcat to see what are the reasons of force closing, and its talking something about a corrupted database.
Here is an extract what happens when I want to run dropbox.
E/AndroidRuntime( 3182): FATAL EXCEPTION: main
E/AndroidRuntime( 3182): java.lang.RuntimeException: Unable to create application com.dropbox.android.DropboxApplication: android.database.sqlite.SQLiteCantOpenDatabaseException: unable to open database file
E/AndroidRuntime( 3182): at android.app.ActivityThread.handleBindApplication(ActivityThread.java:3702)
E/AndroidRuntime( 3182): at android.app.ActivityThread.access$1200(ActivityThread.java:122)
E/AndroidRuntime( 3182): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1065)
E/AndroidRuntime( 3182): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 3182): at android.os.Looper.loop(Looper.java:132)
E/AndroidRuntime( 3182): at android.app.ActivityThread.main(ActivityThread.java:4126)
E/AndroidRuntime( 3182): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 3182): at java.lang.reflect.Method.invoke(Method.java:491)
E/AndroidRuntime( 3182): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:844)
E/AndroidRuntime( 3182): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:602)
E/AndroidRuntime( 3182): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime( 3182): Caused by: android.database.sqlite.SQLiteCantOpenDatabaseException: unable to open database file
E/AndroidRuntime( 3182): at android.database.sqlite.SQLiteDatabase.dbopen(Native Method)
E/AndroidRuntime( 3182): at android.database.sqlite.SQLiteDatabase.openDatabase(SQLiteDatabase.java:983)
E/AndroidRuntime( 3182): at android.database.sqlite.SQLiteDatabase.openDatabase(SQLiteDatabase.java:956)
E/AndroidRuntime( 3182): at android.database.sqlite.SQLiteDatabase.openOrCreateDatabase(SQLiteDatabase.java:1021)
E/AndroidRuntime( 3182): at android.app.ContextImpl.openOrCreateDatabase(ContextImpl.java:772)
E/AndroidRuntime( 3182): at android.content.ContextWrapper.openOrCreateDatabase(ContextWrapper.java:221)
E/AndroidRuntime( 3182): at android.database.sqlite.SQLiteOpenHelper.getWritableDatabase(SQLiteOpenHelper.java:149)
E/AndroidRuntime( 3182): at com.dropbox.android.provider.g.b(panda.py:185)
E/AndroidRuntime( 3182): at com.dropbox.android.DropboxApplication.onCreate(panda.py:59)
E/AndroidRuntime( 3182): at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:968)
E/AndroidRuntime( 3182): at android.app.Ac...
Questions go in the Q&A section
I tried to compile CWM to my Trend 2 SM-G313HN and after flashing the recovery image and booting to recovery mode, a red exclamation mark appeared to the top left corner of the boot screen and the boot process stopped there. At first I thought that the compilation failed, but then I tried to unpack the original recovery.img, edit the default.prop (changed ro.secure to 0) and it happened again. Any changes to the recovery ot boot image seemed to trigger that error. There is a picture in the attachments, sorry about the quality, took it with my old Galaxy Gio.
Atleast I managed to root the phone by manually adding superuser to the system.img and flashing it via Odin, but a recovery would be nice.
EDIT: I discovered that there is a small bootloader hidden in the stock boot/recovery images. Got CWM to boot. (but no graphics yet, but I can connect via ADB) I am working on to get the recovery working.
Can you tell me what procedure you do to compile CWM ?
Link to source code, specific device *.ini or *.xml, linux/gnu x64 system...etc.? I would also like to compile it for Galaxy Trend 2, since there are no any other rooting option for sm-g313hn without octopus box.
adeii said:
Can you tell me what procedure you do to compile CWM ?
Link to source code, specific device *.ini or *.xml, linux/gnu x64 system...etc.? I would also like to compile it for Galaxy Trend 2, since there are no any other rooting option for sm-g313hn without octopus box.
Click to expand...
Click to collapse
https://github.com/TheNikiz/android_device_samsung_vivaltonfc3g
Here is the device configuration. It seems like the bootloader checks if the boot/recovery image is unmodified before continuing, if not, it will show the red "!" in the top left corner of the screen. :/
Nikiz said:
https://github.com/TheNikiz/android_device_samsung_vivaltonfc3g
Here is the device configuration. It seems like the bootloader checks if the boot/recovery image is unmodified before continuing, if not, it will show the red "!" in the top left corner of the screen. :/
Click to expand...
Click to collapse
Thanks a lot, Nikiz. I'll try it.
Do you had use Odin 3.0x and device in download mode to flash it?
Had you tried to compile TWRP: Team-Win-Recovery-Project-Samsung ?
Use Dees_Troy's injecttwrp program to inject the recovery-ramdisk.img into the boot.img
Click to expand...
Click to collapse
adeii said:
Thanks a lot, Nikiz. I'll try it.
Do you had use Odin 3.0x and device in download mode to flash it?
Had you tried to compile TWRP: Team-Win-Recovery-Project-Samsung ?
Click to expand...
Click to collapse
Yes, I flashed it with Odin 3.10. I have not tried TWRP yet. But it seems that anythin other than the stock boot.img/recovery.img does not work. It seems like the bootloader checks if the image is stock Samsung before booting. I tried to edit the stock recovery a little, not changing the functionality any way, but it triggers the error.
EDIT: Well, I have the Cyanogenmod 11 source code downloaded and the system.img is not protected, I started to work on porting CM11 to this phone. Few hours (and beers) later, it booted! But it is not usable yet, it throws a "unfortunately android.phone has stopped working" error repeately and I cannot continue to test it further. There might be a library missing or something.
Nice! Keep the good work!
Flashed it again and this time I opened logcat and see what caused the phone app to crash. Made some changes to the source code, recompiling..
Code:
W/dalvikvm( 4576): Unable to resolve superclass of Lcom/android/phone/MSimIccProvider; (730)
W/dalvikvm( 4576): Link of class 'Lcom/android/phone/MSimIccProvider;' failed
D/AndroidRuntime( 4576): Shutting down VM
W/dalvikvm( 4576): threadid=1: thread exiting with uncaught exception (group=0x415a1ce0)
E/AndroidRuntime( 4576): FATAL EXCEPTION: main
E/AndroidRuntime( 4576): Process: com.android.phone, PID: 4576
E/AndroidRuntime( 4576): java.lang.RuntimeException: Unable to get provider com.android.phone.MSimIccProvider: java.lang.ClassNotFoundException: Didn't find class "com.android.phone.MSimIccProvider" on path: DexPathList[[zip file "/system/priv-app/TeleService.apk"],nativeLibraryDirectories=[/vendor/lib, /system/lib]]
E/AndroidRuntime( 4576): at android.app.ActivityThread.installProvider(ActivityThread.java:4922)
E/AndroidRuntime( 4576): at android.app.ActivityThread.installContentProviders(ActivityThread.java:4514)
E/AndroidRuntime( 4576): at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4454)
E/AndroidRuntime( 4576): at android.app.ActivityThread.access$1500(ActivityThread.java:144)
E/AndroidRuntime( 4576): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1265)
E/AndroidRuntime( 4576): at android.os.Handler.dispatchMessage(Handler.java:102)
E/AndroidRuntime( 4576): at android.os.Looper.loop(Looper.java:136)
E/AndroidRuntime( 4576): at android.app.ActivityThread.main(ActivityThread.java:5146)
E/AndroidRuntime( 4576): at java.lang.reflect.Method.invokeNative(NativeMethod)
E/AndroidRuntime( 4576): at java.lang.reflect.Method.invoke(Method.java:515)
E/AndroidRuntime( 4576): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:732)
E/AndroidRuntime( 4576): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:566)
E/AndroidRuntime( 4576): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime( 4576): Caused by: java.lang.ClassNotFoundException: Didn't find class "com.android.phone.MSimIccProvider" on path: DexPathList[[zip file "/system/priv-app/TeleService.apk"],nativeLibraryDirectories=[/vendor/lib, /system/lib]]
E/AndroidRuntime( 4576): at dalvik.system.BaseDexClassLoader.findClass(BaseDexClassLoader.java:56)
E/AndroidRuntime( 4576): at java.lang.ClassLoader.loadClass(ClassLoader.java:497)
E/AndroidRuntime( 4576): at java.lang.ClassLoader.loadClass(ClassLoader.java:457)
E/AndroidRuntime( 4576): at android.app.ActivityThread.installProvider(ActivityThread.java:4907)
E/AndroidRuntime( 4576): ... 12 more
W/ActivityManager( 2003): Process com.android.phone has crashed too many times:killing!
I found out something! There is a small secondary bootloader hidden inside the recovery image. I noticed it when I compared the stock recovery to a repacked one. The repacked image did not have it. I tried manyally add it to the CWM build and.. The red exclamation point appeared.. But the screen went blank after that, so it did something! I will experiement with this a bit.
EDIT: Yup, fired up ADB while the screen was blank and got a shell. Now I need to get some graphics out of it.
Nikiz said:
I found out something! There is a small secondary bootloader hidden inside the recovery image. I noticed it when I compared the stock recovery to a repacked one. The repacked image did not have it. I tried manyally add it to the CWM build and.. The red exclamation point appeared.. But the screen went blank after that, so it did something! I will experiement with this a bit.
EDIT: Yup, fired up ADB while the screen was blank and got a shell. Now I need to get some graphics out of it.
Click to expand...
Click to collapse
I found these files in official firmware update here. And you are right, recovery.img have hidden stuff.
Got the recovery working! Well, sort of. I have to fix the mounts so it can be used.
EDIT: We now have a working recovery! Link: [RECOVERY][SM-G313HN] CWM-Based Recovery 6.0.5.1 for Trend 2
Congrats, Nikiz!
can you share root files with us, or procedure
Very good,thank you for your work.Successfully rooted with UPDATE-SuperSU-v2.40.zip after flashing your recovery.
Nikiz said:
I found out something! There is a small secondary bootloader hidden inside the recovery image. I noticed it when I compared the stock recovery to a repacked one. The repacked image did not have it. I tried manyally add it to the CWM build and.. The red exclamation point appeared.. But the screen went blank after that, so it did something! I will experiement with this a bit.
EDIT: Yup, fired up ADB while the screen was blank and got a shell. Now I need to get some graphics out of it.
Click to expand...
Click to collapse
Hello ! I'm also making a recovery for another samsung phone, and i noticed like you that little red exclamation. Could you explain what did you do to get it working please ? Thanks in advance !
Well,IMHO, this is only sign that phone detected that recovery (or just bootloader) is not original/stock and nothing more. On SM-G313HN, it appears only in recovery mode and everything works great.
About how to compile new recovery, I would also want to know all steps from Nikiz.
adeii said:
Well,IMHO, this is only sign that phone detected that recovery (or just bootloader) is not original/stock and nothing more. On SM-G313HN, it appears only in recovery mode and everything works great.
About how to compile new recovery, I would also want to know all steps from Nikiz.
Click to expand...
Click to collapse
I think you can follow this guide Porting ClockworkMod Recovery to a New Device. I've build cwm and twrp for my samsung device using this guide.
cleverior.ipul said:
I think you can follow this guide Porting ClockworkMod Recovery to a New Device. I've build cwm and twrp for my samsung device using this guide.
Click to expand...
Click to collapse
Thank you very much for guide.
Nikiz said:
I tried to compile CWM to my Trend 2 SM-G313HN and after flashing the recovery image and booting to recovery mode, a red exclamation mark appeared to the top left corner of the boot screen and the boot process stopped there. At first I thought that the compilation failed, but then I tried to unpack the original recovery.img, edit the default.prop (changed ro.secure to 0) and it happened again. Any changes to the recovery ot boot image seemed to trigger that error. There is a picture in the attachments, sorry about the quality, took it with my old Galaxy Gio.
Atleast I managed to root the phone by manually adding superuser to the system.img and flashing it via Odin, but a recovery would be nice.
EDIT: I discovered that there is a small bootloader hidden in the stock boot/recovery images. Got CWM to boot. (but no graphics yet, but I can connect via ADB) I am working on to get the recovery working.
Click to expand...
Click to collapse
How your fixed this? i have same problem with Gt-s5312c. help me
Onko sulla ideoita miten sais helpoiten tän samsung galaxy trend 2 sm-g313hn puhelimen rootattua ja asennettuu cm11
jonne1 said:
Onko sulla ideoita miten sais helpoiten tän samsung galaxy trend 2 sm-g313hn puhelimen rootattua ja asennettuu cm11
Click to expand...
Click to collapse
Sori näin myöhäinen vastaus. En tätä ketjua seuraile muutenkuin satunnaisesti.
Helpoin tapa rootata on asentaa custom recovery ja flashata sen kautta SuperUser-paketti.. En oo löytänyt mitään "parin klikkauksen" tapaa, mikä tällä puhelimella toimisi. Kannattaa kuitenkin ottaa huomioon, että menetät takuun roottauksen jälkeen.
Custom recoveryn asennus:
Lataa jostain Odin-ohjelma. Versio 3.10 ainakin toimii. Googlaa Odin 3.10 ja valitse ensimmäinen linkki.
Lataa täältä tuo Odin-paketti: (Odin-package) http://forum.xda-developers.com/ace-4/development/recovery-cwm-based-recovery-6-0-5-1-t2987827
Sammuta puhelin ja käynnistä uudelleen painamalla alas-, koti- ja virtanäppäintä yhtäaikaa. Siihen pitäisi ilmestyä varmistusruutu. Yhdistä USB-kaapeli tietokoneeseen ja paina ylä-näppäintä.
Avaa Odin tietokoneella, valitse tuo .tar.md5-tiedosto minkä latasit PDA/AP-kohtaan. Varmista, että "Option"-kohdassa on pelkästään "Auto reboot" ja "F. Reset Time" valittuna.
Sitten painat vain "Start"-nappia ja se asentaa tuon custom recoveryn. Puhelimen pitäisi käynnistyä uudelleen recovery-tilaan, kun se on valmis.
Roottaus:
Lataa tämä puhelimen muistikortille: https://download.chainfire.eu/345/SuperSU/UPDATE-SuperSU-v1.51.zip?retrieve_file=1
Käynnistä puhelin uudelleen recovery-tilaan painamalla ylös-, koti ja virtanäppäintä yhtäaikaa.
Recovery-tilassa voi liikkua painalamma äänenvoimakkuus-näppäimiä ja valita painamalla virtanäppäintä. Takaisin pääsee normaalisti painamalla takaisin-näppäintä.
Valitse "Install zip", "Install from /storage/extSdCard" (Jos latasit irroitettavalle kortille) ja valitset ladatun .zip-tiedoston. Se kysyy varmistusta ja valitset "Yes".
Sitten kun se on valmis, painat vain takaisin-näppäintä valitset "Reboot system now", niin puhelin käynnistyy uudelleen.
Tuo CyanogenMod 11 on vielä hieman keskeneräinen. Esimerkiksi Facebookissa ja joissain muissakin ohjelmissa ei toimi videot (Youtube tosin toimii), etukameran videokuvaus ei toimi ja muita "pikkuvikoja".
Löydät sen täältä: http://forum.xda-developers.com/ace-4/development/rom-cyanogenmod-11-galaxy-trend-2-t3189325
Lataukset löytyy "Latest builds can be downloaded here"-linkistä ja valitsemalla uusimman version.
Sen asennus tapahtuu samalla periaatteella kuin roottaus, mutta puhelimen tiedot pitää tyhjentää ennen sitä.. Kannattaa varmuuskopioida alkuperäinen Android valitsemalla "backup and restore", "backup to /storage/extSdCard". Tässä menee muutama minuutti. Jos haluaa vaihtaa takaisin alkuperäiseen Androidiin, valitse "backup and restore", "restore from /storage/extSdCard" ja valitse varmuuskopio.
Tietojen tyhjäys tapahtuu "wipe data/factory reset"-kohdasta.
CyanogenModia ei tarvitse rootata, sen saa käyttöön Asetukset -> Superuser-kohdasta. En muista pitikö kehittäjävaihtoehot olla käytössä, mutta ne saa käyttöön Asetukset -> Tietoja puhelimesta ja napauttamalla muutaman kerran "Ohjelmistoversion numero"-kohtaa.
Play-kauppaa tuossa ei ole valmiina mukana, niin se pitää ladata täältä: http://opengapps.org/
Valitset vain ARM ja 4.4. Kannattaa valita Micro-paketti ja asentaa muut ohjelmat Play-kaupasta. (Youtube, Google Maps, yms.) Nuo isommat ei yleensä mahdu muistiin kun päivittää CyanogenModia, niin ne joutuu asentamaan uudelleen.
Tuon OpenGapps-paketin asentaminen tapahtuu myös samalla periaatteella kuin roottaus.
Eiköhän näillä pääse alkuun.. Pitäisi tehdä selkeämmät ohjeet kuvilla, jos vain joskus jaksaisi.
Android Wear allows pairing to a new/second phone only after you perform factory reset of Android Wear: "You can switch which phone or tablet your watch is paired with, but you need to reset your watch to factory settings first. Then you can pair your watch to the new phone or tablet." Google Support
It's ok for most people but some just have more devices and want to switch them from time to time. Performing factory reset means compiling apps to aot, retransferring all apps the need to reconfigure all apps (Wear Mini Launcher, anyone?).
There used to be an app BeeLink but it stopped working and was removed.
There's actually way faster way how to set up connection with a new phone - in a minute. Just delete application data of "Google Play Services Wearable" app and reboot. All the 3rd party apps with their configurations, all watch faces with configurations, Google Fit data, and basically everything else will be kept.
Step by step
Wear is connected with phone A so turn off Bluetooth on this phone.
Execute following command on Wear (with ADB enabled - doesn't require root) or run attached app (root on watch required).
Code:
adb shell "pm clear com.google.android.gms && reboot"
Power on Bluetooth on phone B.
Depending whatever devices were paired previously, confirm pairing code or initiate new pairing using following command (thanks @matejdro) or also use the wear app for that
Code:
adb shell "am start -a android.bluetooth.adapter.action.REQUEST_DISCOVERABLE"
Finish setup, let it work for some time and restart both phone B and your watch to properly apply all changes. Done.
Attached apk is for installation on mobile phone (it contains and installs the actual Wear app). It's not on Play Store yet. Let's try it and get some feedback first.
Hi,
Thanks for making this for those of us who know nothing about adb. Unfortunately, I could not get this to work, but I'm certain the error is at my end. I downloaded and installed your apk, but I can't get it to open or find it in the app drawer. Excuse my ignorance. Could you please inform me as to how I can run the apk after installation? I downloaded it on to phone B, which does not have android wear installed, as per your instructions. However, I never got passed step 2 of your guide for the above mentioned reason.
Thank you kindly
moneytoo said:
Android Wear allows pairing to a new/second phone only after you perform factory reset of Android Wear: "You can switch which phone or tablet your watch is paired with, but you need to reset your watch to factory settings first. Then you can pair your watch to the new phone or tablet." Google Support
It's ok for most people but some just have more devices and want to switch them from time to time. Performing factory reset means compiling apps to aot, retransferring all apps the need to reconfigure all apps (Wear Mini Launcher, anyone?).
There used to be an app BeeLink but it stopped working and was removed.
There's actually way faster way how to set up connection with a new phone - in a minute. Just delete application data of "Google Play Services Wearable" app and reboot. All the 3rd party apps with their configurations, all watch faces with configurations, Google Fit data, and basically everything else will be kept.
Run the following command on your pc (with Wear connected and ADB enabled - this doesn't require root) or use my app for switching on-the-go (it requires root on Wear).
Code:
adb shell "pm clear com.google.android.gms && reboot"
Step by step
Wear is connected with phone A so turn off Bluetooth on this phone.
Execute above command or run attached app (root required).
Power on Bluetooth on phone B.
Depending whatever devices were paired previously, confirm pairing code or initiate new pairing.
Done.
Attached apk is for installation on mobile phone (it contains and installs the actual Wear app). It's not on Play Store yet. Let's try it and get some feedback first.
Click to expand...
Click to collapse
rekil goth said:
Hi,
Thanks for making this for those of us who know nothing about adb. Unfortunately, I could not get this to work, but I'm certain the error is at my end. I downloaded and installed your apk, but I can't get it to open or find it in the app drawer. Excuse my ignorance. Could you please inform me as to how I can run the apk after installation? I downloaded it on to phone B, which does not have android wear installed, as per your instructions. However, I never got passed step 2 of your guide for the above mentioned reason.
Thank you kindly
Click to expand...
Click to collapse
this App needs to be Sync'd to the watch so download it to Phone A, which is already paired.
wait until it syncs or manually sync Apps in Wear App on phone A.
when it's availalbe on your watch, then start this procedure.
hmm, just tried this (both ADB command and App installed on watch) with a new phone and I couldn't get it to pair. had to do the watch reset
Not working for me either. Will try the adb route when I can and report back
Finally a solution to my problem.
When i flash a new ROM i have to pair my moto 360 again... And to do this i allways do a reset on my watch...
Next time i will try it and give a feedback.
Not working on moto 360 5.0.2, rooted?
I was trying to figure out this one, but could not found proper app to clear. I cleared GMS, Wear launcher, settings etc. and nothing helped. In the end I found this solution which is even better IMO:
Code:
adb shell am start -a android.bluetooth.adapter.action.REQUEST_DISCOVERABLE
After executing above code via ADB, dialog will pop up on wear asking if you want to make watch discoverable. Then you can find and pair it to any phone.
matejdro said:
I was trying to figure out this one, but could not found proper app to clear. I cleared GMS, Wear launcher, settings etc. and nothing helped. In the end I found this solution which is even better IMO:
Code:
adb shell am start -a android.bluetooth.adapter.action.REQUEST_DISCOVERABLE
After executing above code via ADB, dialog will pop up on wear asking if you want to make watch discoverable. Then you can find and pair it to any phone.
Click to expand...
Click to collapse
Hi, my SW3 was connected to my Mi 4, setup done and working fine. I used Titanium Backup to backup Android Wear and all the watch faces apps.
After I flashed a new custom ROM, used Titanium Backup to restore Android Wear and watch face apps, and also Bluetooth connections on my Mi 4. When SW 3 is connected to my computer, in Adb, it says unauthorised.
Since it is unauthorized, I can't run the ADB command.
Any suggestions?
I don't think there is anything you can do at this point. You should have authorized your PC when you still had working watch connection.
any plans to update it
matejdro said:
I was trying to figure out this one, but could not found proper app to clear. I cleared GMS, Wear launcher, settings etc. and nothing helped. In the end I found this solution which is even better IMO:
Code:
adb shell am start -a android.bluetooth.adapter.action.REQUEST_DISCOVERABLE
After executing above code via ADB, dialog will pop up on wear asking if you want to make watch discoverable. Then you can find and pair it to any phone.
Click to expand...
Click to collapse
Using Minimal ADB, I had to run as admin to make this work, but then it worked perfectly. Thanks very much!
nothing. doesn't work with 5.1.1 g watch rooted, the app gives me black screen (dismissable with swipe)
Just using app from OP is apparently not enough anymore on 5.1.1.
I just made tutorial on reddit on how to reset 5.1.1 watch: https://www.reddit.com/r/AndroidWear/comments/3c4qf8/tip_how_to_switch_phones_without_hard_reset/
I updated the Wear app (v0.2) with support for requesting Bluetooth discoverable mode as well.
Did you guys see this: https://developer.android.com/training/wearables/apps/bt-debugging.html
Yes! I'm so glad something like this has been developed! Worst part about switching ROMs is resetting android wear now. Thanks so much!
Performed the clean in the watch.
It works, and is possible to link the watch with another phone without perform a data wipe.
Then only problem that I've encontered is that the installed watchfaces aren't visible in the Android wear app (in the phone), and I can't set from the phone or hide some.
Thanks
EDIT: Sometimes, due to the watchfaces issue, Android wear app UI generates a FC
Code:
E/AndroidRuntime( 6255): FATAL EXCEPTION: main
E/AndroidRuntime( 6255): Process: com.google.android.wearable.app, PID: 6255
E/AndroidRuntime( 6255): java.lang.NullPointerException: Attempt to invoke virtual method 'boolean android.content.ComponentName.equals(java.lang.Object)' on a null object reference
E/AndroidRuntime( 6255): at com.google.android.clockwork.companion.WatchFacePreviewFragment.loadWatchFaces(WatchFacePreviewFragment.java:261)
E/AndroidRuntime( 6255): at com.google.android.clockwork.companion.WatchFacePreviewFragment.onWatchFacesLoaded(WatchFacePreviewFragment.java:209)
E/AndroidRuntime( 6255): at com.google.android.clockwork.companion.watchfaces.WatchFaceLoadTask.onPostExecute(WatchFaceLoadTask.java:198)
E/AndroidRuntime( 6255): at com.google.android.clockwork.companion.watchfaces.WatchFaceLoadTask.onPostExecute(WatchFaceLoadTask.java:33)
E/AndroidRuntime( 6255): at android.os.AsyncTask.finish(AsyncTask.java:636)
E/AndroidRuntime( 6255): at android.os.AsyncTask.access$500(AsyncTask.java:177)
E/AndroidRuntime( 6255): at android.os.AsyncTask$InternalHandler.handleMessage(AsyncTask.java:653)
E/AndroidRuntime( 6255): at android.os.Handler.dispatchMessage(Handler.java:102)
E/AndroidRuntime( 6255): at android.os.Looper.loop(Looper.java:135)
E/AndroidRuntime( 6255): at android.app.ActivityThread.main(ActivityThread.java:5293)
E/AndroidRuntime( 6255): at java.lang.reflect.Method.invoke(Native Method)
E/AndroidRuntime( 6255): at java.lang.reflect.Method.invoke(Method.java:372)
E/AndroidRuntime( 6255): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:904)
E/AndroidRuntime( 6255): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:699)
W/ActivityManager( 829): Force finishing activity 1 com.google.android.wearable.app/com.google.android.clockwork.companion.StatusActivity
bartito said:
Performed the clean in the watch.
It works, and is possible to link the watch with another phone without perform a data wipe.
Then only problem that I've encontered is that the installed watchfaces aren't visible in the Android wear app (in the phone), and I can't set from the phone or hide some.
Thanks
EDIT: Sometimes, due to the watchfaces issue, Android wear app UI generates a FC
Code:
E/AndroidRuntime( 6255): FATAL EXCEPTION: main
E/AndroidRuntime( 6255): Process: com.google.android.wearable.app, PID: 6255
E/AndroidRuntime( 6255): java.lang.NullPointerException: Attempt to invoke virtual method 'boolean android.content.ComponentName.equals(java.lang.Object)' on a null object reference
E/AndroidRuntime( 6255): at com.google.android.clockwork.companion.WatchFacePreviewFragment.loadWatchFaces(WatchFacePreviewFragment.java:261)
E/AndroidRuntime( 6255): at com.google.android.clockwork.companion.WatchFacePreviewFragment.onWatchFacesLoaded(WatchFacePreviewFragment.java:209)
E/AndroidRuntime( 6255): at com.google.android.clockwork.companion.watchfaces.WatchFaceLoadTask.onPostExecute(WatchFaceLoadTask.java:198)
E/AndroidRuntime( 6255): at com.google.android.clockwork.companion.watchfaces.WatchFaceLoadTask.onPostExecute(WatchFaceLoadTask.java:33)
E/AndroidRuntime( 6255): at android.os.AsyncTask.finish(AsyncTask.java:636)
E/AndroidRuntime( 6255): at android.os.AsyncTask.access$500(AsyncTask.java:177)
E/AndroidRuntime( 6255): at android.os.AsyncTask$InternalHandler.handleMessage(AsyncTask.java:653)
E/AndroidRuntime( 6255): at android.os.Handler.dispatchMessage(Handler.java:102)
E/AndroidRuntime( 6255): at android.os.Looper.loop(Looper.java:135)
E/AndroidRuntime( 6255): at android.app.ActivityThread.main(ActivityThread.java:5293)
E/AndroidRuntime( 6255): at java.lang.reflect.Method.invoke(Native Method)
E/AndroidRuntime( 6255): at java.lang.reflect.Method.invoke(Method.java:372)
E/AndroidRuntime( 6255): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:904)
E/AndroidRuntime( 6255): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:699)
W/ActivityManager( 829): Force finishing activity 1 com.google.android.wearable.app/com.google.android.clockwork.companion.StatusActivity
Click to expand...
Click to collapse
Did you also try reseting app data of both Android Wear and Google Play on the phone (& restart)?
moneytoo said:
Did you also try reseting app data of both Android Wear and Google Play on the phone (& restart)?
Click to expand...
Click to collapse
yes, performed a reboot in the wear and also a wipe in the phone