Related
Hey guys!
So here's the problem.
I used framework-res,framework.jar, and android.policy.jar from the hdpi version of UHD by Jader.
I faced some fcs:-
1) Brightness fcs when i access it from settings->display. (Toggle in statusbar works well)
2) APN settings fc.
3) In QuickPic, when i try to change alignment of arrangement of photos, it fcs.
Please help!
Here are the logcats:-
https://db.tt/KTgYTd0b
Thank you!
Sent from my WT19i using XDA Premium 4 mobile app
Anyone? I really need help
Bump.
Someone help please?
coolancool said:
Hey guys!
So here's the problem.
I used framework-res,framework.jar, and android.policy.jar from the hdpi version of UHD by Jader.
I faced some fcs:-
1) Brightness fcs when i access it from settings->display. (Toggle in statusbar works well)
2) APN settings fc.
3) In QuickPic, when i try to change alignment of arrangement of photos, it fcs.
Please help!
Here are the logcats:-
https://db.tt/KTgYTd0b
Thank you!
Sent from my WT19i using XDA Premium 4 mobile app
Click to expand...
Click to collapse
come on gtalk >> [email protected] after 7 pm indian time
edit : use orignal UHD framework on mdpi as there is nothing needed to be changed in framework
Wish someone could help me out with this one.
It's making me crazy.
coolancool said:
Wish someone could help me out with this one.
It's making me crazy.
Click to expand...
Click to collapse
Hmmm...i believe you need to use the original system UI too cause those FC comes out because the system UI that you are using right now is not properly compile to work on original framework...
iPusak Gaoq™ said:
Hmmm...i believe you need to use the original system UI too cause those FC comes out because the system UI that you are using right now is not properly compile to work on original framework...
Click to expand...
Click to collapse
Is that what the logcat says?
Sent from my WT19i using XDA Premium 4 mobile app
Ignore this post
I am just using this post as a check point so I dont have to re-read the logs every time
Code:
11-03 23:46:47.524 4309 4309 E AndroidRuntime: FATAL EXCEPTION: main
11-03 23:46:47.524 4309 4309 E AndroidRuntime: android.view.InflateException: Binary XML file line #15: Error inflating class android.widget.RadioButton
11-03 23:46:47.524 4309 4309 E AndroidRuntime: at android.view.LayoutInflater.createView(LayoutInflater.java:606)
11-03 23:46:47.524 4309 4309 E AndroidRuntime: Caused by: android.content.res.Resources$NotFoundException: File res/drawable/btn_radio_label_background.xml from drawable resource ID #0x1080187
11-03 23:46:49.364 634 730 E InputDispatcher: channel '41036438 com.android.settings/com.android.settings.Settings (server)' ~ Channel is unrecoverably broken and will be disposed!
Hello there! I'm new to these parts because I recently acquired a Gear Fit.
TL;DR: I took aooga's stuff (thanks!) and made it work on my CM 12 (5.0.2) phone. I hope it works for you. Get it here.
Anyway, I'm using a Galaxy Nexus running a cm 12 build from Ziyan, and I quickly realized that I needed to do some extra work. Unfortunately, zwegnet's patched Gear Fit Manager didn't work for me, and neither did aooga's very comprehensive guide, so I figured I'd try doing it myself. I see that some of you are interested in how this works, so I'm documenting my process for everyone's benefit (let's collaborate!).
You will learn the basics of:
how to debug using adb logcat
how to disassemble an app (specifically, a dex file) into smali
how to navigate and modify smali code
how to reassemble smali to dex and rebuild the app
how to sign an app for deployment
You will need:
adb
java runtime environment
smali/baksmali
signapk with test keys
I've collected some of the tools for you here; just add adb and java.
1. Debugging
So, we've got Gear Fit Manager and Gear Fitness installed... but Gear Fit Manager crashes! Darn it. How are we gonna connect a Gear Fit? Let's see.
First, let's pop open your favorite terminal (yes, we will be using the command line) and start streaming some logs:
Code:
adb logcat
There should be a bunch of text scrolling through the terminal. While that's going on, try to launch the offending app, and wait until it crashes. As soon as it crashes, hit Ctrl+C in the terminal to stop logging. Look, a fatal exception:
Code:
E/AndroidRuntime(32368): FATAL EXCEPTION: main
E/AndroidRuntime(32368): Process: com.samsung.android.wms, PID: 32368
E/AndroidRuntime(32368): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.samsung.android.wms/com.samsung.android.wms.app.base.ContentsActivity}: android.content.res.Resources$NotFoundException: Resource ID #0x0
E/AndroidRuntime(32368): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2298)
E/AndroidRuntime(32368): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2360)
E/AndroidRuntime(32368): at android.app.ActivityThread.access$800(ActivityThread.java:144)
E/AndroidRuntime(32368): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1278)
E/AndroidRuntime(32368): at android.os.Handler.dispatchMessage(Handler.java:102)
E/AndroidRuntime(32368): at android.os.Looper.loop(Looper.java:135)
E/AndroidRuntime(32368): at android.app.ActivityThread.main(ActivityThread.java:5223)
E/AndroidRuntime(32368): at java.lang.reflect.Method.invoke(Native Method)
E/AndroidRuntime(32368): at java.lang.reflect.Method.invoke(Method.java:372)
E/AndroidRuntime(32368): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:898)
E/AndroidRuntime(32368): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:693)
E/AndroidRuntime(32368): Caused by: android.content.res.Resources$NotFoundException: Resource ID #0x0
E/AndroidRuntime(32368): at android.content.res.Resources.getValue(Resources.java:1233)
E/AndroidRuntime(32368): at android.content.res.Resources.getDrawable(Resources.java:756)
E/AndroidRuntime(32368): at android.content.res.Resources.getDrawable(Resources.java:724)
E/AndroidRuntime(32368): at com.samsung.android.wms.app.base.WingtipBaseActivity.brandGlowEffect(WingtipBaseActivity.java:136)
E/AndroidRuntime(32368): at com.samsung.android.wms.app.base.WingtipBaseActivity.onCreate(WingtipBaseActivity.java:94)
E/AndroidRuntime(32368): at com.samsung.android.wms.app.base.ContentsActivity.onCreate(ContentsActivity.java:139)
E/AndroidRuntime(32368): at android.app.Activity.performCreate(Activity.java:5933)
E/AndroidRuntime(32368): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1105)
E/AndroidRuntime(32368): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2251)
E/AndroidRuntime(32368): ... 10 more
When you've been bug-hunting for a while, you start to notice these stack traces quite readily, even in a sea of irrelevant output. This one tells us that:
the offending app is named com.samsung.android.wms
a Resources$NotFoundException occurred, likely because the app requested a resource that did not exist
... and so on
Note that the stack trace appears in reverse-chronological order; that is, what happens later appears first. I often like to read these things backwards. Now, have a look at these lines:
Code:
E/AndroidRuntime(32368): at android.content.res.Resources.getDrawable(Resources.java:724)
E/AndroidRuntime(32368): at com.samsung.android.wms.app.base.WingtipBaseActivity.brandGlowEffect(WingtipBaseActivity.java:136)
E/AndroidRuntime(32368): at com.samsung.android.wms.app.base.WingtipBaseActivity.onCreate(WingtipBaseActivity.java:94)
What happened?
a WingtipBaseActivity is created to display the app, and is being initialized in its onCreate method
... which calls brandGlowEffect
... which calls into the Android system
... which eventually leads to the crash
With the entire chain of events exposed to us, we could now look for the culprit! Why don't we examine WingtipBaseActivity.brandGlowEffect? It's the last thing the app does before passing control over to Android, and we're assuming that the app (not Android) is faulty.
2. Disassembly
To do this, we need to take a peek under Gear Fit Manager's hood. An apk file is just a zip file, so we already know how to unpack it. We're interested in the classes.dex within, which contains the executable code. dex is not a very human-readable format, so we need to disassemble it using baksmali.
Firstly, let's extract the classes.dex from the archive. Then, we could disassemble it by running:
Code:
java -jar baksmali.jar -o dexout classes.dex
3. Modification
This generates a folder full of disassembled code. Because we're interested in com.samsung.android.wms.app.base.WingtipBaseActivity, we'll look inside the file dexout/com/samsung/android/wms/app/base/WingtipBaseActivity.smali
There, on line 693, we see the method WingtipBaseActivity.brandGlowEffect getting called from WingtipBaseActivity.onCreate. This looks like some cosmetic fluff that we could dispense with, so let's just delete the line altogether and save the file. Sorry, Samsung, your brand's not gonna glow this time.
4. Reassembly
Now we could re-generate the classes.dex:
Code:
java -jar smali.jar -o classes.dex dexout
... and we'll drop the new classes.dex inside the apk.
5. Signing
But wait! We couldn't install this new apk yet — it needs to be signed. This is easy enough with signapk:
Code:
java -jar signapk.jar testkey.x509.pem testkey.pk8 GearFitManager.apk GearFitManager_signed.apk
6. Deploying
We need to uninstall the original app before we could install the new one, because they were signed using different keys (the original was signed using Samsung's keys). After that, we just need to install and test!
We've barely scratched the surface. I hope this helps someone, and I certainly hope we could team up to make something awesome. I've had a look at the more recent versions of Gear Fit Manager, and I have a feeling a lot more work would be required...
Just when I was about to give up , I found this thread . Thank you so much .
The app finally doesn't crash . But it doesn't seem to be connecting with the Fitness app .
Running Nexus 4 with CyanogenMod 12 , v5.0.2 .
[DIY][CM 12][Android 5.0] Gear Fit on Non-Samsung Devices with Lollipop
Hello there! I'm new to these parts because I recently acquired a Gear Fit.
TL;DR: I took aooga's stuff (thanks!) and made it work on my CM 12 (5.0.2) phone. I hope it works for you. Get it here.
Anyway, I'm using a Galaxy Nexus running a cm 12 build from Ziyan, and I quickly realized that I needed to do some extra work. Unfortunately, zwegnet's patched Gear Fit Manager didn't work for me, and neither did aooga's very comprehensive guide, so I figured I'd try doing it myself. I see that some of you are interested in how this works, so I'm documenting my process for everyone's benefit (let's collaborate!).
You will learn the basics of:
1.how to debug using adb logcat
2.how to disassemble an app (specifically, a dex file) into smali
3.how to navigate and modify smali code
4.how to reassemble smali to dex and rebuild the app
5.how to sign an app for deployment
You will need:
•adb
•java runtime environment
•smali/baksmali
•signapk with test keys
I've collected some of the tools for you here; just add adb and java.
1. Debugging
So, we've got Gear Fit Manager and Gear Fitness installed... but Gear Fit Manager crashes! Darn it. How are we gonna connect a Gear Fit? Let's see.
First, let's pop open your favorite terminal (yes, we will be using the command line) and start streaming some logs:
Code:
adb logcat
There should be a bunch of text scrolling through the terminal. While that's going on, try to launch the offending app, and wait until it crashes. As soon as it crashes, hit Ctrl+C in the terminal to stop logging. Look, a fatal exception:
Code:
E/AndroidRuntime(32368): FATAL EXCEPTION: main
E/AndroidRuntime(32368): Process: com.samsung.android.wms, PID: 32368
E/AndroidRuntime(32368): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.samsung.android.wms/com.samsung.android.wms.app.base.ContentsActivity}: android.content.res.Resources$NotFoundException: Resource ID #0x0
E/AndroidRuntime(32368): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2298)
E/AndroidRuntime(32368): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2360)
E/AndroidRuntime(32368): at android.app.ActivityThread.access$800(ActivityThread.java:144)
E/AndroidRuntime(32368): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1278)
E/AndroidRuntime(32368): at android.os.Handler.dispatchMessage(Handler.java:102)
E/AndroidRuntime(32368): at android.os.Looper.loop(Looper.java:135)
E/AndroidRuntime(32368): at android.app.ActivityThread.main(ActivityThread.java:5223)
E/AndroidRuntime(32368): at java.lang.reflect.Method.invoke(Native Method)
E/AndroidRuntime(32368): at java.lang.reflect.Method.invoke(Method.java:372)
E/AndroidRuntime(32368): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:898)
E/AndroidRuntime(32368): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:693)
E/AndroidRuntime(32368): Caused by: android.content.res.Resources$NotFoundException: Resource ID #0x0
E/AndroidRuntime(32368): at android.content.res.Resources.getValue(Resources.java:1233)
E/AndroidRuntime(32368): at android.content.res.Resources.getDrawable(Resources.java:756)
E/AndroidRuntime(32368): at android.content.res.Resources.getDrawable(Resources.java:724)
E/AndroidRuntime(32368): at com.samsung.android.wms.app.base.WingtipBaseActivity.brandGlowEffect(WingtipBaseActivity.java:136)
E/AndroidRuntime(32368): at com.samsung.android.wms.app.base.WingtipBaseActivity.onCreate(WingtipBaseActivity.java:94)
E/AndroidRuntime(32368): at com.samsung.android.wms.app.base.ContentsActivity.onCreate(ContentsActivity.java:139)
E/AndroidRuntime(32368): at android.app.Activity.performCreate(Activity.java:5933)
E/AndroidRuntime(32368): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1105)
E/AndroidRuntime(32368): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2251)
E/AndroidRuntime(32368): ... 10 more
When you've been bug-hunting for a while, you start to notice these stack traces quite readily, even in a sea of irrelevant output. This one tells us that:
•the offending app is named com.samsung.android.wms
•a Resources$NotFoundException occurred, likely because the app requested a resource that did not exist
•... and so on
Note that the stack trace appears in reverse-chronological order; that is, what happens later appears first. I often like to read these things backwards. Now, have a look at these lines:
Code:
E/AndroidRuntime(32368): at android.content.res.Resources.getDrawable(Resources.java:724)
E/AndroidRuntime(32368): at com.samsung.android.wms.app.base.WingtipBaseActivity.brandGlowEffect(WingtipBaseActivity.java:136)
E/AndroidRuntime(32368): at com.samsung.android.wms.app.base.WingtipBaseActivity.onCreate(WingtipBaseActivity.java:94)
What happened?
1.a WingtipBaseActivity is created to display the app, and is being initialized in its onCreate method
2.... which calls brandGlowEffect
3.... which calls into the Android system
4.... which eventually leads to the crash
With the entire chain of events exposed to us, we could now look for the culprit! Why don't we examine WingtipBaseActivity.brandGlowEffect? It's the last thing the app does before passing control over to Android, and we're assuming that the app (not Android) is faulty.
2. Disassembly
To do this, we need to take a peek under Gear Fit Manager's hood. An apk file is just a zip file, so we already know how to unpack it. We're interested in the classes.dex within, which contains the executable code. dex is not a very human-readable format, so we need to disassemble it using baksmali.
Firstly, let's extract the classes.dex from the archive. Then, we could disassemble it by running:
Code:
java -jar baksmali.jar -o dexout classes.dex
3. Modification
This generates a folder full of disassembled code. Because we're interested in com.samsung.android.wms.app.base.WingtipBaseActivi ty, we'll look inside the file dexout/com/samsung/android/wms/app/base/WingtipBaseActivity.smali
There, on line 693, we see the method WingtipBaseActivity.brandGlowEffect getting called from WingtipBaseActivity.onCreate. This looks like some cosmetic fluff that we could dispense with, so let's just delete the line altogether and save the file. Sorry, Samsung, your brand's not gonna glow this time.
4. Reassembly
Now we could re-generate the classes.dex:
Code:
java -jar smali.jar -o classes.dex dexout
... and we'll drop the new classes.dex inside the apk.
5. Signing
But wait! We couldn't install this new apk yet — it needs to be signed. This is easy enough with signapk:
Code:
java -jar signapk.jar testkey.x509.pem testkey.pk8 GearFitManager.apk GearFitManager_signed.apk
6. Deploying
We need to uninstall the original app before we could install the new one, because they were signed using different keys (the original was signed using Samsung's keys). After that, we just need to install and test!
We've barely scratched the surface. I hope this helps someone, and I certainly hope we could team up to make something awesome. I've had a look at the more recent versions of Gear Fit Manager, and I have a feeling a lot more work would be required...
Click to expand...
Click to collapse
Very good explanation.
Thanks to you I was able to path version 1.98 and it works the media control, I can upload new watches styles using Watch Styler for Fit.
What doesn't work is the App connect. All applications say that I have to install Gear Manager Fit first.
It's working on my Nexus 4 with 5.0.1. I also updated the gear fit to the last firmware and it connects perfectly.
I attach it.
Help
bronxgsi said:
Very good explanation.
Thanks to you I was able to path version 1.98 and it works the media control, I can upload new watches styles using Watch Styler for Fit.
What doesn't work is the App connect. All applications say that I have to install Gear Manager Fit first.
It's working on my Nexus 4 with 5.0.1. I also updated the gear fit to the last firmware and it connects perfectly.
I attach it.
Click to expand...
Click to collapse
I installed the zip by renaming it as an apk but when I try to pair it give the same confirmation but doesn't finish pairing please help... I have Nexus 5 it has stock 5.0.1 rooted as well.
I haven't been able to sync the Fitness with Gear app either, even with Samsung Account installed per Virnik0's recommendation.
I believe this stack trace is relevant:
Code:
D/SessionInputStream(29439): move remain data to first index / mTotalDataLength : 83 mTotalReceivedLength : 88
W/SessionManager(29439): notifyDataReceived port : 2
I/SessionManager(29439): mBinderMap.get action:com.samsung.android.wms.communication.session_manager_for_interanalbinder:115174198
I/SessionManager(29439): listener.onDataReceived is called
V/DataExchangeManager(29439): SessionManagerEventListener onDataReceived
W/DataExchangeManager(29439): From : HEALTH, Attempt to invoke interface method 'void com.samsung.android.wms.service.communication.DataExchangeManager$OnDataReceivedListener.onDataReceived(com.samsung.android.wms.service.communication.WingtipApp, byte[])' on a null object reference
W/DataExchangeManager(29439): java.lang.NullPointerException: Attempt to invoke interface method 'void com.samsung.android.wms.service.communication.DataExchangeManager$OnDataReceivedListener.onDataReceived(com.samsung.android.wms.service.communication.WingtipApp, byte[])' on a null object reference
W/DataExchangeManager(29439): at com.samsung.android.wms.service.communication.DataExchangeManager$InternalHandler.handleMessage(DataExchangeManager.java:126)
W/DataExchangeManager(29439): at android.os.Handler.dispatchMessage(Handler.java:102)
W/DataExchangeManager(29439): at android.os.Looper.loop(Looper.java:135)
W/DataExchangeManager(29439): at android.app.ActivityThread.main(ActivityThread.java:5223)
W/DataExchangeManager(29439): at java.lang.reflect.Method.invoke(Native Method)
W/DataExchangeManager(29439): at java.lang.reflect.Method.invoke(Method.java:372)
W/DataExchangeManager(29439): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:898)
W/DataExchangeManager(29439): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:693)
It seems that it actually connected to Samsung's servers, but had some trouble handling the response. I'll investigate this sometime...
will1549 said:
I installed the zip by renaming it as an apk but when I try to pair it give the same confirmation but doesn't finish pairing please help... I have Nexus 5 it has stock 5.0.1 rooted as well.
Click to expand...
Click to collapse
Same here -- I'd blame the differences among ROMS
I actually haven't been able to get any recent versions working, myself...
inportb said:
I haven't been able to sync the Fitness with Gear app either, even with Samsung Account installed per Virnik0's recommendation.
I believe this stack trace is relevant:
Code:
D/SessionInputStream(29439): move remain data to first index / mTotalDataLength : 83 mTotalReceivedLength : 88
W/SessionManager(29439): notifyDataReceived port : 2
I/SessionManager(29439): mBinderMap.get action:com.samsung.android.wms.communication.session_manager_for_interanalbinder:115174198
I/SessionManager(29439): listener.onDataReceived is called
V/DataExchangeManager(29439): SessionManagerEventListener onDataReceived
W/DataExchangeManager(29439): From : HEALTH, Attempt to invoke interface method 'void com.samsung.android.wms.service.communication.DataExchangeManager$OnDataReceivedListener.onDataReceived(com.samsung.android.wms.service.communication.WingtipApp, byte[])' on a null object reference
W/DataExchangeManager(29439): java.lang.NullPointerException: Attempt to invoke interface method 'void com.samsung.android.wms.service.communication.DataExchangeManager$OnDataReceivedListener.onDataReceived(com.samsung.android.wms.service.communication.WingtipApp, byte[])' on a null object reference
W/DataExchangeManager(29439): at com.samsung.android.wms.service.communication.DataExchangeManager$InternalHandler.handleMessage(DataExchangeManager.java:126)
W/DataExchangeManager(29439): at android.os.Handler.dispatchMessage(Handler.java:102)
W/DataExchangeManager(29439): at android.os.Looper.loop(Looper.java:135)
W/DataExchangeManager(29439): at android.app.ActivityThread.main(ActivityThread.java:5223)
W/DataExchangeManager(29439): at java.lang.reflect.Method.invoke(Native Method)
W/DataExchangeManager(29439): at java.lang.reflect.Method.invoke(Method.java:372)
W/DataExchangeManager(29439): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:898)
W/DataExchangeManager(29439): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:693)
It seems that it actually connected to Samsung's servers, but had some trouble handling the response. I'll investigate this sometime...
Same here -- I'd blame the differences among ROMS
I actually haven't been able to get any recent versions working, myself...
Click to expand...
Click to collapse
My problem getting the Bluetooth pair to GFM. On version 1.49 for lollipop it was but not this zip
will1549 said:
My problem getting the Bluetooth pair to GFM. On version 1.49 for lollipop it was but not this zip
Click to expand...
Click to collapse
It works. Sort of. Basically it asks for update every time I connect to my Fit. That update then fail due to different signing keys, but then it works.
I have used the version from OP
Virnik0 said:
It works. Sort of. Basically it asks for update every time I connect to my Fit. That update then fail due to different signing keys, but then it works.
I have used the version from OP
Click to expand...
Click to collapse
My problem is it only pair Bluetooth but never connect gear fit manager to the gear fit it keeps send verification codes.
bronxgsi said:
Very good explanation.
Thanks to you I was able to path version 1.98 and it works the media control, I can upload new watches styles using Watch Styler for Fit.
What doesn't work is the App connect. All applications say that I have to install Gear Manager Fit first.
It's working on my Nexus 4 with 5.0.1. I also updated the gear fit to the last firmware and it connects perfectly.
I attach it.
Click to expand...
Click to collapse
This one works fine! Thanks for sharing!
---------- Post added at 10:43 PM ---------- Previous post was at 10:25 PM ----------
Virnik0 said:
This one works fine! Thanks for sharing!
Click to expand...
Click to collapse
BTW, we'll need version 1.102, and original genuine keys. so, once you'll compile/smali odex, just add it to original APK, that shall do it, otherwise we won't be able to use any gear app plugin
I don't know why it doesn't pair... Sorry I'm not an expert in this issue.
Virnik0 said:
This one works fine! Thanks for sharing!
---------- Post added at 10:43 PM ---------- Previous post was at 10:25 PM ----------
BTW, we'll need version 1.102, and original genuine keys. so, once you'll compile/smali odex, just add it to original APK, that shall do it, otherwise we won't be able to use any gear app plugin
Click to expand...
Click to collapse
I tried to patch the last versión (GearFitManager_NL1_1.111.1216_USER.apk) but it doesn't pair. The original one, in a G2 with KitKat doesn't pair neither.
I was able to use all the plugins from App connect patching the "dexout\com\samsung\android\sdk\cup\Scup.smali" file to not to check the keys. Just changing:
if-eq v1, v6, :cond_e2
to
if-ne v1, v6, :cond_e2
The problema is that I had to patch every App I want to use and it is a little tedious. Maybe we can make an script or a program to automatically doing it...
Dunno what will be best way to do this now. I have a very little time to do any coding nowadays. But at least version 1.98 works fine. Running RR 5.2.9 (CM12 - Android 5.0.2) on GT9300. Pairing works correctly
A script would be wonderful
pcp12 said:
A script would be wonderful
Click to expand...
Click to collapse
Of course!!!
Works on my Nexus 5 (the APK in the first post)
I'll try to patch the last release
Does this versions just work on cm12? I have GPE lollipop on my s4 and when I connect my phone to the gear fit, the gear fit manager crashes immediately.
poaudet said:
Of course!!!
Works on my Nexus 5 (the APK in the first post)
I'll try to patch the last release
Click to expand...
Click to collapse
Because you have to modify ro.product.manufacturer=samsung to something else (like ro.product.manufacturer=GPE) in /system/build.prop
Reboot after modification is done and you should be OK.
BTW, SGS5 does have LP available for download for more then month, but GFM is the same. Works there fine, because all classes are provided from TW framework.
Virnik0 said:
Because you have to modify ro.product.manufacturer=samsung to something else (like ro.product.manufacturer=GPE) in /system/build.prop
Reboot after modification is done and you should be OK.
BTW, SGS5 does have LP available for download for more then month, but GFM is the same. Works there fine, because all classes are provided from TW framework.
Click to expand...
Click to collapse
Thanks, got it working. Really nice work! [emoji1]
poaudet said:
Of course!!!
Works on my Nexus 5 (the APK in the first post)
I'll try to patch the last release
Click to expand...
Click to collapse
Poaudet do you have a stock rom or another rom? I have a stock nexus 5 with kitkat and i am not about to upgrade to lollipop until my gear fit doesnt have the functionalities that are now working with 4.4.4. Anyone is using a stock nexus 5 with lollipop?
alexxio said:
Poaudet do you have a stock rom or another rom? I have a stock nexus 5 with kitkat and i am not about to upgrade to lollipop until my gear fit doesnt have the functionalities that are now working with 4.4.4. Anyone is using a stock nexus 5 with lollipop?
Click to expand...
Click to collapse
Im using google play edition on my s4. Its like the lollipop on nexus 5 and everything for me is working.
alexxio said:
Poaudet do you have a stock rom or another rom? I have a stock nexus 5 with kitkat and i am not about to upgrade to lollipop until my gear fit doesnt have the functionalities that are now working with 4.4.4. Anyone is using a stock nexus 5 with lollipop?
Click to expand...
Click to collapse
I've stock lollipop rom.
Things that didn't work:
-music control
-everything that need Samsung Account
-Endomondo
-GPS (Gear Navigation, Weather, ...)
Everything else seems to work, with some edit it the apk of Connected App, see the other post in this thread.
I've attached those i've already edit.
Noob question: I flew over the tutorial and didn't really noticed any variable data. Is there something preventing someone from generating and sharing a patched apk of GFM that would work with basically any non-Samsung Lollipop phone ?
I was encouraged by some of you to try new marshmallow and lollipop ROMs but after using a titanium backup and during restore app, phone give me some fcs after both of ROMs. Anyway It is doesn't matter cause is too slowly for me.
So I came back to CM11 with stagefright fix by Lanchon. Everything goes perfect but the cLock weather is not working at all. I know that I need resize widget and set up everything in lock screen setting but it makes only calendar work.
Thank you for a tip!
One think I changed in a flash I download a micro opengaps to install google launcher by default.
I'm getting the same problem on Slimsaber 4.4.4 rom (by Greekdragon)
Here is the log:
Code:
E/dashclock_WeatherExten(12106): Showing a weather extension error
E/dashclock_WeatherExten(12106): com.google.android.apps.dashclock.weather.CantGetWeatherException: Error parsing weather feed XML.
E/dashclock_WeatherExten(12106): at com.google.android.apps.dashclock.weather.YahooWeatherApiClient.getWeatherForWoeid(YahooWeatherApiClient.java:168)
E/dashclock_WeatherExten(12106): at com.google.android.apps.dashclock.weather.YahooWeatherApiClient.getWeatherForLocationInfo(YahooWeatherApiClient.java:75)
E/dashclock_WeatherExten(12106): at com.google.android.apps.dashclock.weather.WeatherExtension.tryPublishWeatherUpdateFromLocationInfo(WeatherExtension.java:264)
E/dashclock_WeatherExten(12106): at com.google.android.apps.dashclock.weather.WeatherExtension.onUpdateData(WeatherExtension.java:172)
E/dashclock_WeatherExten(12106): at com.google.android.apps.dashclock.api.DashClockExtension$1$1.run(DashClockExtension.java:312)
E/dashclock_WeatherExten(12106): at android.os.Handler.handleCallback(Handler.java:733)
E/dashclock_WeatherExten(12106): at android.os.Handler.dispatchMessage(Handler.java:95)
E/dashclock_WeatherExten(12106): at android.os.Looper.loop(Looper.java:136)
E/dashclock_WeatherExten(12106): at android.os.HandlerThread.run(HandlerThread.java:61)
E/dashclock_WeatherExten(12106): Caused by: java.io.FileNotFoundException: http://weather.yahooapis.com/forecastrss?w=1103816&u=c
E/dashclock_WeatherExten(12106): at com.android.okhttp.internal.http.HttpURLConnectionImpl.getInputStream(HttpURLConnectionImpl.java:186)
E/dashclock_WeatherExten(12106): at com.google.android.apps.dashclock.weather.YahooWeatherApiClient.getWeatherForWoeid(YahooWeatherApiClient.java:94)
Seems like the weather feed XML is down, meaning that it will affect all users of this dashclock extension (please confirm)
gsstudios
KPPD Control
Hey everyone! I know many of you are a big fan of @savoca 's KCal daemon KPPD. It is KCal for select chip sets on rooted phones that do not have KCal built into the kernel, or for phones that the KCal only partly supports.
KCal is a tool for adjusting the color, saturation, contrast, etc., of your screen, post processed. That means it happens after the image is drawn, and only affects what you visually see, so a screenshot is not affected by this. this helps you make your display show true black, and all sorts of cool color effects!
You can read more about KCal here:
https://forum.xda-developers.com/showthread.php?t=3165247
And a couple of quotes from savoca:
Hello all! If you're familiar with*KCAL*and suffer from symptoms such as a locked bootloader or non-loadable kernel modules then you may be interested in KCAL Post-Processing Daemon, or KPPD - the all-in-one display tuning tool that you can use to customize your color calibration on the fly!
This does NOT require an unlocked bootloader, custom kernel, or even a kernel that supports module loading, just run the daemon and you're good to go!
A once *very* device dependent feature now made available for the following chipsets:
Quote:
8x10
8974 v1.0
8x26 v1.0
8x26 v2.0, 8926 v1.0
8926 v2.0
8974 v2.0
8974 v3.0 (Pro)
8084 v1.0
8084 v1.1
8994 v1.0
8916 v1.0
8939 v1.0
8092 v1.0
Click to expand...
Click to collapse
However, the LG G4 has an 8992 chip, and it works too. So you could always try it if you have a Qualcomm chip. Be sure to let us know the results!
All the credit for KPPD goes to savoca. Using his tools used to require installation at the terminal or with ADB. Then, to make changes required hand editing a text file. But praise God, not anymore! now you can just use this app to handle everything from installation to making adjustments!
Feel free to give it a try! I made this app under the Apache 2.0 license, so fell free to borrow anything you need!
After install, you must give the app permission to read/write to the phone.
Go to:
Settings --> apps --> kppd --> permissions
And turn on storage.
Note: If you turned on storage permissions, but it still says "error, check permissions" then go to your sdcard, and create a folder called "documents" (if it doesn't exist) and in that folder, create an empty file called "kppd.conf". Then try the app again. This happens on some ROMs, and I'm not sure why.
Google Play Store:
https://play.google.com/store/apps/details?id=com.alaskalinuxuser.kppdcontrol
GitHub: (The app folder has a copy of the apk as well, if you don't use the play store.)
https://github.com/alaskalinuxuser/app_kppdcontrol
I have only tested this on a T-Mobile LG G4, but it should work on any KPPD/KCal compatible (mdp5) device.
Enjoy! And feel free to comment!
{
"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"
}
Sent from my LG-H811 using XDA-Developers Legacy app
AlaskaLinuxUser said:
KPPD Control
Hey everyone! I know many of you are a big fan of @savoca 's KCal daemon KPPD. It is KCal for select chip sets on rooted phones that do not have KCal built into the kernel, or for phones that the KCal only partly supports.
KCal is a tool for adjusting the color, saturation, contrast, etc., of your screen, post processed. That means it happens after the image is drawn, and only affects what you visually see, so a screenshot is not affected by this. this helps you make your display show true black, and all sorts of cool color effects!
You can read more about KCal here:
https://forum.xda-developers.com/showthread.php?t=3165247
All the credit for KPPD goes to savoca. Using his tools used to require installation at the terminal or with ADB. Then, to make changes required hand editing a text file. But praise God, not anymore! now you can just use this app to handle everything from installation to making adjustments!
Feel free to give it a try! I made this app under the Apache 2.0 license, so fell free to borrow anything you need!
Google Play Store:
https://play.google.com/store/apps/details?id=com.alaskalinuxuser.kppdcontrol
GitHub: (The app folder has a copy of the apk as well, if you don't use the play store.)
https://github.com/alaskalinuxuser/app_kppdcontrol
I have only tested this on a T-Mobile LG G4, but it should work on any KPPD/KCal compatible (mdp5) device.
Enjoy! And feel free to comment!
Click to expand...
Click to collapse
Thanks sir
This is what i wanted
To change values everytime editing the file was very messy
Thanks sir
And also to savoca
addy692 said:
Thanks sir
This is what i wanted
To change values everytime editing the file was very messy
Thanks sir
And also to savoca
Click to expand...
Click to collapse
Thank you, I'm glad you like the app!
Sent from my LG-H811 using XDA-Developers Legacy app
@AlaskaLinuxUser thank you so much for this.
i used to use kcal on my sony xperia z2 on stock marshmallow rom with compiled kcal module but now i am on resurrection remix android 7.1.2 (aosp base), i installed the app but i can only adjust RGB same like the built in feature live display but i can't adjust anything else like contrast saturation,values...etc, from what i readed i should be able to adjust everything same like kcal even without custom kernel ! or should the kernel supports kcal to be able to adjust everything ?
thanks again for the app .
rocker00 said:
@AlaskaLinuxUser thank you so much for this.
i used to use kcal on my sony xperia z2 on stock marshmallow rom with compiled kcal module but now i am on resurrection remix android 7.1.2 (aosp base), i installed the app but i can only adjust RGB same like the built in feature live display but i can't adjust anything else like contrast saturation,values...etc, from what i readed i should be able to adjust everything same like kcal even without custom kernel ! or should the kernel supports kcal to be able to adjust everything ?
thanks again for the app .
Click to expand...
Click to collapse
rocker00,
Thanks for the kind words.
Two thoughts:
#1. Could you open the /sdcard/documents/kppd.conf file, and manually edit it to pa version 1 instead of 2? Then try editing (manually) the file values and press save. Does that work? Be sure before hand to open the app and enable once to get the kppd running. This will see if you have pa version 1 or 2. My app is only set up for version 2, but I may need to make a settings page for version 1 or 2.
#2. If you manually install per savoca's kppd thread (link in op) does it work? If not, then it is a problem with the kppd, not my app.
I am not trying to duck the problem. Just trying to isolate if it is my app or kppd itself. I didn't make kppd, and kppd may need to be specifically edited and compiled for your phone, I'm not sure. Was there ever a working kppd (not KCal, which is in the kernel) for your phone?
Also, for grins, can you send me a log cat when it fails to work?
Thanks!
Sent from my LG-H811 using XDA-Developers Legacy app
AlaskaLinuxUser said:
rocker00,
Thanks for the kind words.
Two thoughts:
#1. Could you open the /sdcard/documents/kppd.conf file, and manually edit it to pa version 1 instead of 2? Then try editing (manually) the file values and press save. Does that work? Be sure before hand to open the app and enable once to get the kppd running. This will see if you have pa version 1 or 2. My app is only set up for version 2, but I may need to make a settings page for version 1 or 2.
#2. If you manually install per savoca's kppd thread (link in op) does it work? If not, then it is a problem with the kppd, not my app.
Edit: @AlaskaLinuxUser tried to install manually without you app, same result ! can't adjust anything except RGB ! also tried your idea to change pa from 2 to 1 but also the same result ! so the problem is not the app, the problem is kppd itself or something in the rom ! thank you so much for the app and for trying to help and also lets wait for feedback for other users.
best regards
I am not trying to duck the problem. Just trying to isolate if it is my app or kppd itself. I didn't make kppd, and kppd may need to be specifically edited and compiled for your phone, I'm not sure. Was there ever a working kppd (not KCal, which is in the kernel) for your phone?
Also, for grins, can you send me a log cat when it fails to work?
Thanks!
Sent from my LG-H811 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Thanks for trying to help and yeah sure i understand you are just trying to figure out where is the problem !
i will do what you said and i will let you know the result.
Thanks.
Edit: @AlaskaLinuxUser tried both ideas, changing pa form 2 to 1 & installing manually without your app but still the same result ! only able to adjust RGB ! so, obviously the problem is not the app itself but in kppd or something in the rom !
anyway thank you so much for the app and for trying to help and also lets wait for feedback from the other users !
best regards .
rocker00 said:
Thanks for trying to help and yeah sure i understand you are just trying to figure out where is the problem !
i will do what you said and i will let you know the result.
Thanks.
Edit: @AlaskaLinuxUser tried both ideas, changing pa form 2 to 1 & installing manually without your app but still the same result ! only able to adjust RGB ! so, obviously the problem is not the app itself but in kppd or something in the rom !
anyway thank you so much for the app and for trying to help and also lets wait for feedback from the other users !
best regards .
Click to expand...
Click to collapse
Do you have a link to the threads with the compiled kcal module? savoca made kppd open source, so if the thread has any clue to the girth commits to make it work on your phone, perhaps there is something we can do. Perhaps, no promises, and it's a long shot....
Sent from my LG-H811 using XDA-Developers Legacy app
AlaskaLinuxUser said:
Do you have a link to the threads with the compiled kcal module? savoca made kppd open source, so if the thread has any clue to the girth commits to make it work on your phone, perhaps there is something we can do. Perhaps, no promises, and it's a long shot....
Sent from my LG-H811 using XDA-Developers Legacy app
Click to expand...
Click to collapse
here is the thread for the module https://forum.xda-developers.com/crossdevice-dev/sony/5-x-kcal-module-flashable-t3159869 , the rom which i am using right now supposed to use 3.10 kernel but it uses 3.4 kernel to have a fully working camera due to the lack of camera blobs source from sony, since i am not linux user unfortunately i don't know anything about compiling but i also feel that it's a little bit complicated in this case !
Thank you so much
I'm assuming that because this deals with modifying the kernel that you have to have an unlocked boot loader. Which means this won't work for a Verizon LG G4?
Spookymyo said:
I'm assuming that because this deals with modifying the kernel that you have to have an unlocked boot loader. Which means this won't work for a Verizon LG G4?
Click to expand...
Click to collapse
This actually does not require an unlocked boot loader. The KPPD daemon runs in user space, but root is required. I have only tested on the T-Mobile G4, but it should work on any rooted G4.
I would appreciate hearing your results if you have time to test it.
Sent from my LG-H811 using XDA-Developers Legacy app
Does not work on LG G5
obol2 said:
Does not work on LG G5
Click to expand...
Click to collapse
Thanks for testing it!
Question: did it not work at all? Did the r g b multipliers work, or just not at all?
Sorry, just read up on the LG G5, it has an 8996 chip, which savoca did not list as applicable. Then again, neither is the G4's chip, the 8992, but it works on the G4 anyways. Sorry that it does not work on the G5.
Also, if you have time did savoca's original kppd work? Sorry for all all the questions. Thanks for taking the time to test it!
Forgive my ignorance, too, but is the G5 chose on the list of chips in the OP (just updated, was not there before now)?
If so, which version? Notice in the text file there is a "pa" version. You may need to change to 1, 2, or 3 depending on your version. If that is the case (and them editing the text file works) I could add a settings for version number also.
Sent from my LG-H811 using XDA-Developers Legacy app
Hi there!
Would this tool work on a Nexus 6P running Pure Nexus with ElementalX kernel? I had been using savoca's Color Control app but it doesn't work anymore on Nougat.
Thanks!
Sent from my Nexus 6P
Works on msm8953 chip?
Ghisy said:
Hi there!
Would this tool work on a Nexus 6P running Pure Nexus with ElementalX kernel? I had been using savoca's Color Control app but it doesn't work anymore on Nougat.
Thanks!
Sent from my Nexus 6P
Click to expand...
Click to collapse
Great question!
Yes, it should work.
On the original kppd thread (link in OP) a 6P was using it. They did mention a specific 6P glitch, though, that if you had the screen off when kppd applied, the colors would look funny. So give it a try, but keep that glitch in mind, you may not want the set on boot.
Sent from my LG-H811 using XDA-Developers Legacy app
suvam69 said:
Works on msm8953 chip?
Click to expand...
Click to collapse
I don't see that on savoca's list of approved chips, but neither was the G4's 8992, so feel free to give it a shot. I'd like to hear how it turns out. If it works, we can add it to the list.
Sent from my LG-H811 using XDA-Developers Legacy app
Thanks for the awesome job! This app makes KPPD so much easier to use
Btw, does anybody have a display-calibrating tool to find the right values to have the G4 calibrated to sRGB colorspace?
I'm asking because most of the internet content is sRGB so it would be amazing to achieve a better calibration on our G4 (which has horrible factory calibration).
Thanks in advance
Hello!
Im using a RN4x with snapdragon 625. I can't get that app to be working :/ i gave it already root permissions and to memory, but it still says "Error: Please check permissions". What's wrong?
ReDuXX528 said:
Hello!
Im using a RN4x with snapdragon 625. I can't get that app to be working :/ i gave it already root permissions and to memory, but it still says "Error: Please check permissions". What's wrong?
Click to expand...
Click to collapse
Cheers,
reporting the same issue on latest Xiaomi.eu Beta-7.7.20 and working Magisk 13.3 on a Xiaomi Redmi Note 4 Global Edition.
Logcat reports the following for the application using
Code:
adb logcat *:W
Code:
07-27 16:48:37.904 9538 9538 W System.err: java.io.FileNotFoundException: /storage/emulated/0/kppd (Permission denied)
07-27 16:48:37.905 9538 9538 W System.err: at java.io.FileOutputStream.open(Native Method)
07-27 16:48:37.905 9538 9538 W System.err: at java.io.FileOutputStream.<init>(FileOutputStream.java:221)
07-27 16:48:37.905 9538 9538 W System.err: at java.io.FileOutputStream.<init>(FileOutputStream.java:108)
07-27 16:48:37.905 9538 9538 W System.err: at com.alaskalinuxuser.kppdcontrol.InstallActivity.installKPPD(InstallActivity.java:84)
07-27 16:48:37.905 9538 9538 W System.err: at java.lang.reflect.Method.invoke(Native Method)
07-27 16:48:37.905 9538 9538 W System.err: at android.support.v7.app.AppCompatViewInflater$DeclaredOnClickListener.onClick(AppCompatViewInflater.java:288)
07-27 16:48:37.905 9538 9538 W System.err: at android.view.View.performClick(View.java)
07-27 16:48:37.905 9538 9538 W System.err: at android.view.View$PerformClick.run(View.java)
07-27 16:48:37.905 9538 9538 W System.err: at android.os.Handler.handleCallback(Handler.java)
07-27 16:48:37.905 9538 9538 W System.err: at android.os.Handler.dispatchMessage(Handler.java)
07-27 16:48:37.905 9538 9538 W System.err: at android.os.Looper.loop(Looper.java)
07-27 16:48:37.905 9538 9538 W System.err: at android.app.ActivityThread.main(ActivityThread.java)
07-27 16:48:37.905 9538 9538 W System.err: at java.lang.reflect.Method.invoke(Native Method)
07-27 16:48:37.905 9538 9538 W System.err: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java)
07-27 16:48:37.905 9538 9538 W System.err: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java)
This is the output when not searching for warnings and above:
Code:
07-27 16:50:57.920 9538 9538 W System.err: java.io.FileNotFoundException: /storage/emulated/0/kppd (Permission denied)
07-27 16:50:57.920 9538 9538 W System.err: at java.io.FileOutputStream.open(Native Method)
07-27 16:50:57.920 9538 9538 W System.err: at java.io.FileOutputStream.<init>(FileOutputStream.java:221)
07-27 16:50:57.920 9538 9538 W System.err: at java.io.FileOutputStream.<init>(FileOutputStream.java:108)
07-27 16:50:57.920 9538 9538 W System.err: at com.alaskalinuxuser.kppdcontrol.InstallActivity.installKPPD(InstallActivity.java:84)
07-27 16:50:57.920 9538 9538 W System.err: at java.lang.reflect.Method.invoke(Native Method)
07-27 16:50:57.920 9538 9538 W System.err: at android.support.v7.app.AppCompatViewInflater$DeclaredOnClickListener.onClick(AppCompatViewInflater.java:288)
07-27 16:50:57.921 9538 9538 W System.err: at android.view.View.performClick(View.java)
07-27 16:50:57.921 9538 9538 W System.err: at android.view.View$PerformClick.run(View.java)
07-27 16:50:57.921 9538 9538 W System.err: at android.os.Handler.handleCallback(Handler.java)
07-27 16:50:57.921 9538 9538 W System.err: at android.os.Handler.dispatchMessage(Handler.java)
07-27 16:50:57.921 9538 9538 W System.err: at android.os.Looper.loop(Looper.java)
07-27 16:50:57.921 9538 9538 W System.err: at android.app.ActivityThread.main(ActivityThread.java)
07-27 16:50:57.921 9538 9538 W System.err: at java.lang.reflect.Method.invoke(Native Method)
07-27 16:50:57.921 9538 9538 W System.err: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java)
07-27 16:50:57.921 9538 9538 W System.err: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java)
AlaskaLinuxUser said:
This actually does not require an unlocked boot loader. The KPPD daemon runs in user space, but root is required. I have only tested on the T-Mobile G4, but it should work on any rooted G4.
I would appreciate hearing your results if you have time to test it.
Click to expand...
Click to collapse
I gave it a try. No luck. Doesn't work for rooted Verizon LG G4. When I open the app it prompts me for root which I grant. Then I click the install button and the phone restarts. I open the app again and there is no control panel it only shows the install button again. Tried it a few times with the same results.
Work in progress to make it work on a samsung tablet running android 7.1.1
Can get the watch to be seen by gear manager but it fails during set up.
This is a list of trial and errors at the moment - please add any ideas you have.
Install magisk /root
Install Magiskhide props config
Install terminal emulator
install busybox via magisk downloads
terminal emulator -> props
Add new custom value
ro.product.model
Was SM-T395
Set to GT-N7105 (note 2)
1. default (current)
y
Boots OK
Safetynet pass
download wear
download amaze file manager
navigate to /data/data/com.samsung.android.app.watchmanager/files/rules.xml
edit to allow tablets=true
set it read only(!)
restart
Safetynet pass
run gear wearables & connect
--------------Beyond this it's a bit of a guess. Trying gearmanagerstub.apk but no luck yet.
--------------Currently fails after 5-10 seconds of 'connecting to gear', which displays on phone and watch.
Sees watch and connects also shows connecting on the watch but then the app bombs back to a list of devices. So it passes the initial device checks at least, but gear2splugin is failing somehow
Maybe I need gearmanagerstub Will try downloading Note 8 7.1.1 firmware see if there is a gearmanagerstub. Yes it has one.
& use magisk app systemiser module....
terminal -> systemize
option 3
enter path of gearmanagerstub.apk e.g. /sdcard/GearManagerStub.apk (where I put mine)
where to install? 1. /system/app
Nothing shows in /system/app... watchmanager bombs again
try restart
Interesting it keep updating rules.xml now.... it is back to supports tablet=false. Both after restart, and then after starting watchmanager. (I edited it after boot then checked again)
fix is set rules.xml to read only.
So perhaps an older version of gearmanagerstub would do the trick.. (I'm using the oldest note 8 one)
run terminal ->systemize
revert app - select 1- (null??)
install note 3 5.0 gearmanagerstub.apk same process
After another failure to connect it got further to ELUA screen before bombing.
I see it thinks my watch is installed now...
It connects for maybe 10 seconds hits "back up and restore" and immediately bombs. The app acts like it is working but the gear says it's not "failed to connect"
Suddenly pops up "error your gear is disconnected" on the restore page.
Now it's back to failing after 5 seconds / 10 spins.
tried copying gearmanagerstub to /system/app and reinstalling all, no difference
This did not trigger safetynet.
Try setting to SM-950F... no change.
Try setting fingerprint to note 8 (SM-950F) (8.0 although I am running 7.1.1)
try ro.build.characteristics=phone,emulator (currently tablet,emulator)
This gives a different list of devices (watches not just earphones) when I reinstalled gear manager.
Still bombs, also the icon is still a tablet when connecting, not a phone.
If anyone has figured this out already I'm all ears
could try non samsung next
https://forum.xda-developers.com/showpost.php?p=79230009
or other ideas
https://www.youtube.com/watch?v=nKH1ykQR4iQ
Update- bluetooth crash in logcat
Looking at logcat and the apks it appears that watchmanager only checks to see if the watch is 'non samsung'. How it decides that an GT-N7105 magically makes it a samsung product but a T395 is not, I can't figure it out.
Interestingly modifying rules.xml and simply adding supportsnonsamsung = true seems to work.
In any case logcat shows a bluetooth error/crash. Why it crashes I don't know.
It looks like the trigger is
11-14 13:35:56.237 4853 4853 E SACalendarProvider::Service: CALENDAR_HOSTMANAGER_CONNECT
Shortly after this a lot of data seems to be sent over bluetooth. A few seconds later the data stops, and 200ms later an error:
11-14 13:35:59.786 3525 3609 E bt_hci : command_timed_out [BT_CORE] hci layer timeout waiting for response to a command. opcode: 0xffff
Nothing interesting happens in logcat in the 2 seconds of data transfer.
A while later the app detects that the watch is disconnected
and eventually bombs. A few seconds after that the watch reports setup fail.
Here is a list of interesting error codes
11-12 12:18:58.417 31815 31832 E BluetoothDataManager: getUartErrorInfo 000 000 000 000
11-12 12:18:58.417 31815 31832 E BluetoothDataManager: "LO_MFN":"29","LO_LMP":"8","LO_SUB":"602","LO_FWV":"BTFM.TF.1.3-00036-QCATFSWPZ-1","ERROR_REASON":"225","UART":"000 000 000 000"
11-12 12:18:58.599 22777 31958 E SABtServerListener: SA_ERROR: IOexception in UUID xxx-xxx-xxx-xxx-xxx ::Exiting Now
11-12 12:18:58.601 3600 4901 I ActivityManager: Process com.android.bluetooth (pid 31815) has died(68,798)
Here is a list of things that crashed
11-12 12:18:58.611 3600 4901 W ActivityManager: Scheduling restart of crashed service com.android.bluetooth/.btservice.AdapterService in 1000ms
11-12 12:18:58.612 3600 4901 W ActivityManager: Scheduling restart of crashed service com.android.bluetooth/.hdp.HealthService in 11000ms
11-12 12:18:58.614 3600 4901 W ActivityManager: Scheduling restart of crashed service com.android.bluetooth/.hid.HidService in 10997ms
11-12 12:18:58.617 3600 4901 W ActivityManager: Scheduling restart of crashed service com.android.bluetooth/.map.BluetoothMapService in 10994ms
11-12 12:18:58.618 3600 4901 W ActivityManager: Scheduling restart of crashed service com.android.bluetooth/.a2dp.A2dpService in 10993ms
11-12 12:18:58.619 3600 4901 W ActivityManager: Scheduling restart of crashed service com.android.bluetooth/.gatt.GattService in 10992ms
11-12 12:18:58.619 22777 22808 D SADiscoveryCore: handling msg: DEVICE_ACCESSORY_LOST...
11-12 12:18:58.619 3600 4901 W ActivityManager: Scheduling restart of crashed service com.android.bluetooth/com.samsung.ble.BleAutoConnectService in 20992ms
11-12 12:18:58.619 3600 4901 W ActivityManager: Scheduling restart of crashed service com.android.bluetooth/.hid.HidDevService in 30992ms
11-12 12:18:58.620 3600 4901 W ActivityManager: Scheduling restart of crashed service com.android.bluetooth/.opp.BluetoothOppService in 30991ms
11-12 12:18:58.620 3600 4901 W ActivityManager: Scheduling restart of crashed service com.android.bluetooth/.sap.SapService in 30991ms
I am not sure what causes this error.
I tried many versions of gear2plugin which contains the apks such as SAproviders / SAcalendarprovider code..
It seems that the bluetooth process under hostmanager-connectionmanager-databuilder works for "single chunk" but with fragmented data it receives 12 chunks of 61k (or so) before dying.
any ideas?
Just FYI
The same T395 tab-phone works pairing a Gear S3 which uses a different plugin 'gearoplugin', with rules.xml edited to say support tablet = true and set to read only. No other tricks are needed I think as supportnonsamsung is already true, all connected to the internet etc. Obviously you need root to edit rules.xml.
= Gear S plugin V2.2.03.19032541N
= Galaxy Wearable V2.2.27.19083061
The gear s uses gear2smodule. I tried the latest version I could find 2118120361, which didn't work.
aka GearModule Version 2.2.02.18120361
Does anyone have a later version?