Is anyone using their Gear S3 with a phone running the Android P dev preview? Been trying to connect mine and it constantly force closes. Just want to see if it's just me or if it is a problem with the app not working with P.
** --------- beginning of crash
03-28 19:53:29.528 3377-3377/? E/AndroidRuntime: FATAL EXCEPTION: main
*** Process: com.samsung.android.app.watchmanager, PID: 3377
*** java.lang.NoClassDefFoundError: Failed resolution of: Landroid/content/pm/IPackageInstallObserver$Stub;
******* at com.samsung.android.app.twatchmanager.packagecontroller.PackageControllerFactory.makeInstance(Unknown Source:6)
******* at com.samsung.android.app.twatchmanager.packagecontroller.PackageControllerFactory.getInstaller(Unknown Source:4)
******* at com.samsung.android.app.twatchmanager.util.CleanupAsyncTask.onPreExecute(Unknown Source:40)
******* at android.os.AsyncTask.executeOnExecutor(AsyncTask.java:648)
******* at android.os.AsyncTask.execute(AsyncTask.java:595)
******* at com.samsung.android.app.watchmanager.setupwizard.HMConnectFragment.startCleanupTask(Unknown Source:28)
******* at com.samsung.android.app.watchmanager.setupwizard.HMConnectFragment.access$3100(Unknown Source:0)
******* at com.samsung.android.app.watchmanager.setupwizard.HMConnectFragment$13.handleMessage(Unknown Source:121)
******* at android.os.Handler.dispatchMessage(Handler.java:106)
******* at android.os.Looper.loop(Looper.java:164)
******* at android.app.ActivityThread.main(ActivityThread.java:6656)
******* at java.lang.reflect.Method.invoke(Native Method)
******* at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:438)
******* at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:823)
**** Caused by: java.lang.ClassNotFoundException: Didn't find class "android.content.pm.IPackageInstallObserver$Stub" on path: DexPathList[[zip file "/data/app/com.samsung.android.app.watchmanager-ExhBUk2ofzT0Hwta2wDw9w==/base.apk"],nativeLibraryDirectories=[/data/app/com.samsung.android.app.watchmanager-ExhBUk2ofzT0Hwta2wDw9w==/lib/arm64, /system/fake-libs64, /data/app/com.samsung.android.app.watchmanager-ExhBUk2ofzT0Hwta2wDw9w==/base.apk!/lib/arm64-v8a, /system/lib64]]
******* at dalvik.system.BaseDexClassLoader.findClass(BaseDexClassLoader.java:125)
******* at java.lang.ClassLoader.loadClass(ClassLoader.java:379)
******* at java.lang.ClassLoader.loadClass(ClassLoader.java:312)
******* at com.samsung.android.app.twatchmanager.packagecontroller.PackageControllerFactory.makeInstance(Unknown Source:6)*
******* at com.samsung.android.app.twatchmanager.packagecontroller.PackageControllerFactory.getInstaller(Unknown Source:4)*
******* at com.samsung.android.app.twatchmanager.util.CleanupAsyncTask.onPreExecute(Unknown Source:40)*
******* at android.os.AsyncTask.executeOnExecutor(AsyncTask.java:648)*
******* at android.os.AsyncTask.execute(AsyncTask.java:595)*
******* at com.samsung.android.app.watchmanager.setupwizard.HMConnectFragment.startCleanupTask(Unknown Source:28)*
******* at com.samsung.android.app.watchmanager.setupwizard.HMConnectFragment.access$3100(Unknown Source:0)*
******* at com.samsung.android.app.watchmanager.setupwizard.HMConnectFragment$13.handleMessage(Unknown Source:121)*
******* at android.os.Handler.dispatchMessage(Handler.java:106)*
******* at android.os.Looper.loop(Looper.java:164)*
******* at android.app.ActivityThread.main(ActivityThread.java:6656)*
******* at java.lang.reflect.Method.invoke(Native Method)*
******* at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:438)*
******* at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:823)*
****
****
*** --------- beginning of system (end of crash)
I kept having this issue and finally realized the issue. Android deprecated the hidden API Samsung references (IPackageObserver). This hidden API only works if the app is a system app, so it is weird that Samsung has this. Maybe it makes the experience a little nicer on Samsung devices since everything can be done in the background, but when it causes crashes it is not ideal. All you need to do to resolve this issue is edit the smali file for com.samsung.android.app.twatchmanager.packagecontroller.PackageControllerFactory.
The method makeInstance() needs changed to false (So it doesn't try hidden API). After that you will have to re-sign Samsung Gear, Accessory, and Plugin APK's because they use a shared user ID. One issue I noticed is due to having to re-sign the APK Samsung Pay was giving me issues. Hopefully Samsung resolves this issue soon.
Please do post it. I'm tempted to roll back if I can't get my watch working.
Just grab the Oreo image from Google and use fastboot to flash it. You might can even get by without having to factory reset the phone doing it that way if you just remove the "-w" from the fastboot command.
DO NOT INSTALL ANDROID P IF YOU HAVE THE SAMSUNG GEAR APP ON YOUR PHONE.
Sorry didn't mean to yell but it will render your gears s3 a paper weight...and Samsung could care less
---------- Post added at 01:18 PM ---------- Previous post was at 01:14 PM ----------
I have been trying to opt out of android P for 18 hours now...and got nothing. Getting ready to just do a warranty exchange.
---------- Post added at 01:27 PM ---------- Previous post was at 01:18 PM ----------
don't do it...your gear smart watch or fitness device will become useless. Requested a rollback from Google back to android O 19 hours ago and haven't gotten it yet. Cant even sideload the previous android O.....
Why would Samsung support software that is not meant for general use and aimed at developers? Google even warns you it is not to be used as a daily driver and all your software may not work. Stop being so entitled. Support for P will come in due time, probably during one of the later builds that finalize the APIs if the O preview was anything to go by.Not working on Android p beta 2. Samsung does not give a f*** about their users.
My Tmo Gear s3 is working perfectly fine on my p2xl on android P, I had it setup before taking the P Beta OTA.
My Tmo Gear s3 is working perfectly fine on my p2xl on android P, I had it setup before taking the P Beta OTA.
Has anybody gotten the new Gear S plugin update on android O and then upgraded to android P? If so did the gear app update fix the FC issue???