Hallo,
I want to pay a big compliment to all who try to bring android to the HTC devices and hope you can help me, to complie the Kernel on my on.
Following the instructions on http://wiki.xda-developers.com/index.php?pagename=BuildTheKaiserKernel I get an error when compiling. The output is:
<stdin>:1097:2: warning: #warning syscall fadvise64 not implemented
<stdin>:1265:2: warning: #warning syscall migrate_pages not implemented
<stdin>:1321:2: warning: #warning syscall pselect6 not implemented
<stdin>:1325:2: warning: #warning syscall ppoll not implemented
<stdin>:1365:2: warning: #warning syscall epoll_pwait not implemented
<stdin>:1377:2: warning: #warning syscall timerfd_create not implemented
<stdin>:1389:2: warning: #warning syscall timerfd_settime not implemented
<stdin>:1393:2: warning: #warning syscall timerfd_gettime not implemented
scripts/genksyms/lex.c: In Funktion »yylex1«:
scripts/genksyms/lex.l:95: Warnung: Der Rückgabewert von »fwrite«, der mit dem Attribut warn_unused_result deklariert wurde, wird ignoriert
scripts/genksyms/lex.l: Auf höchster Ebene:
scripts/genksyms/lex.c:1487: Warnung: »input« definiert, aber nicht verwendet
scripts/mod/modpost.c: In Funktion »get_markers«:
scripts/mod/modpost.c:1527: Warnung: Der Rückgabewert von »asprintf«, der mit dem Attribut warn_unused_result deklariert wurde, wird ignoriert
scripts/mod/modpost.c: In Funktion »add_marker«:
scripts/mod/modpost.c:1935: Warnung: Der Rückgabewert von »asprintf«, der mit dem Attribut warn_unused_result deklariert wurde, wird ignoriert
scripts/kallsyms.c: In Funktion »read_symbol«:
scripts/kallsyms.c:80: Warnung: Der Rückgabewert von »fgets«, der mit dem Attribut warn_unused_result deklariert wurde, wird ignoriert
init/calibrate.c: In function 'calibrate_delay':
init/calibrate.c:172: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:https://support.codesourcery.com/GNUToolchain/> for instructions.
make[1]: *** [init/calibrate.o] Fehler 1
make: *** [init] Fehler 2
My configuration is Kubuntu 8.10 running on a Pentium M.
No need to open a new thread.
Polaris Android Linux Kernel Development Project
To answer your question:
I think the htc-vogue branch is broken at the moment - because we're running into the same error.
Thanks for the reply. I already found this answer http://forum.xda-developers.com/showpost.php?p=3331331&postcount=3290, however it didn't work for me. I already tried to compile one week ago and it didn't work. I can't imagine that the branch is broken such a long time. Anyway, I hope we can make it run
I opened a new thread, because "Polaris Android Linux Kernel Development Project" seems quite messed up as any information related to this project is posted there and I find difficult/impossible to read the whole thread. Maybe, an own category should be created, where all the "Project-" related issues can be posted in own threads...
Found the solution to this problem: Use arm-2008q3 instead of 2008q1.
Please post your changes to the other thread.
Worked well!! Thanks.
So what are you working on?
If I read the code right - I think wlan stuff is atm only available for Kaiser (progress being made but not fully functional) - it shouldn't be a huge problem to port it to Polaris (different gpio's?).
The bluetooth stuff should also be fairly easy (at least afair) - but thats only built-in for Nike atm (and also not working).
Wired Headset also "only" needs to be ported from Vogue.
Battery and Leds are also working on Kaiser but not Polaris.
Same goes for powering down the different screens and touchscreen improvements.
If you're interested in working on any of these issues - I can probably assist you in getting it done (best contact me throug PC or IM).
Update 12.10.2017
MehStrongBadMeh said:
Maik268 said:
UPDATE
There is a new Gear S Plugin update available in PlayStore. They fixed the crashes, everything is working now.
Looks like even the modded gear app is not needed anymore. But I will check this later.
Sent from my HTC 10 using XDA Labs
Click to expand...
Click to collapse
Can confirm, updated to the latest Gear S Plugin and latest unmodded Gear App and everything is working properly on my HTC 10.
Gear App 2.2.17022862
Gear S Plugin 2.2.03.17101142N
Click to expand...
Click to collapse
In our Viper10 Thread we had multiple reports, that the Samsung Gear app force closes when trying to connect their device.
Seemed not just the HTC10 is affected though. From my google research I found also some logcats from other roms and devices posted with the same issue.
@Toni10 linked me to that thread today, opened by @kajos in the Samsung Gear S3 Forum..so it seems it's really a general issue.
Okay, so what is the issue:
Code:
-27 21:10:15.357 E/AndroidRuntime(6044): FATAL EXCEPTION: main
11-27 21:10:15.357 E/AndroidRuntime(6044): Process: com.samsung.android.app.watchmanager, PID: 6044
11-27 21:10:15.357 E/AndroidRuntime(6044): java.lang.NoClassDefFoundError: Failed resolution of: Lcom/samsung/android/feature/FloatingFeature;
11-27 21:10:15.357 E/AndroidRuntime(6044): at com.samsung.android.app.watchmanager.sdllibrary.FloatingFeature.getEnableStatus(FloatingFeature.java:11)
11-27 21:10:15.357 E/AndroidRuntime(6044): at com.samsung.android.app.twatchmanager.log.LoggerUtil$Builder.<clinit>(LoggerUtil.java:95)
11-27 21:10:15.357 E/AndroidRuntime(6044): at com.samsung.android.app.twatchmanager.util.HostManagerUtils.startPluginActivity(HostManagerUtils.java:551)
11-27 21:10:15.357 E/AndroidRuntime(6044): at com.samsung.android.app.watchmanager.setupwizard.HMConnectFragment.callPluginActivity(HMConnectFragment.java:377)
11-27 21:10:15.357 E/AndroidRuntime(6044): at com.samsung.android.app.watchmanager.setupwizard.HMConnectFragment.callPluginActivityWithDelay(HMConnectFragment.java:365)
11-27 21:10:15.357 E/AndroidRuntime(6044): at com.samsung.android.app.watchmanager.setupwizard.HMConnectFragment.access$200(HMConnectFragment.java:67)
11-27 21:10:15.357 E/AndroidRuntime(6044): at com.samsung.android.app.watchmanager.setupwizard.HMConnectFragment$1.handleMessage(HMConnectFragment.java:315)
11-27 21:10:15.357 E/AndroidRuntime(6044): at android.os.Handler.dispatchMessage(Handler.java)
11-27 21:10:15.357 E/AndroidRuntime(6044): at android.os.Looper.loop(Looper.java)
11-27 21:10:15.357 E/AndroidRuntime(6044): at android.app.ActivityThread.main(ActivityThread.java)
11-27 21:10:15.357 E/AndroidRuntime(6044): at java.lang.reflect.Method.invoke(Native Method)
11-27 21:10:15.357 E/AndroidRuntime(6044): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java)
11-27 21:10:15.357 E/AndroidRuntime(6044): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java)
11-27 21:10:15.357 E/AndroidRuntime(6044): Caused by: java.lang.ClassNotFoundException: Didn't find class "com.samsung.android.feature.FloatingFeature" on path: DexPathList[[zip file "/data/app/com.samsung.android.app.watchmanager-1/base.apk"],nativeLibraryDirectories=[/data/app/com.samsung.android.app.watchmanager-1/lib/arm64, /system/fake-libs64, /data/app/com.samsung.android.app.watchmanager-1/base.apk!/lib/arm64-v8a, /system/lib64, /vendor/lib64]]
11-27 21:10:15.357 E/AndroidRuntime(6044): at dalvik.system.BaseDexClassLoader.findClass(BaseDexClassLoader.java:56)
11-27 21:10:15.357 E/AndroidRuntime(6044): at java.lang.ClassLoader.loadClass(ClassLoader.java:380)
11-27 21:10:15.357 E/AndroidRuntime(6044): at java.lang.ClassLoader.loadClass(ClassLoader.java:312)
11-27 21:10:15.357 E/AndroidRuntime(6044): ... 13 more
Bad coding, or intended, no idea.
A framework class com.samsung.android.feature.FloatingFeature is not found on none samsung devices.
I took the effort to decompile the sams h i t app and digged in the code and backtraced the issue.
The source of the bug (or intended behavior) is the samsung device detection:
Code:
.method public static isSamsungDevice()Z
.locals 1
invoke-static {}, Lcom/samsung/android/app/twatchmanager/TWatchManagerApplication;->getAppContext()Landroid/content/Context;
move-result-object v0
invoke-static {v0}, Lcom/samsung/android/app/twatchmanager/util/InstallationUtils;->hasInstallPermission(Landroid/content/Context;)Z
move-result v0
return v0
.end method
It also returns true even on none samsung devices.
Not sure why that fails. it checks if it can get android.permission.INSTALL_PACKAGES...that perm can be just granted to apps in /system.
So moving the app to /system should work too, to fix the issue for rooted users...still it should return falls and not true on none samsung devices that dont't have it on /system
The result of it is that causes the app to crash in LoggerUtil$Builder:
Code:
.method static constructor <clinit>()V
.locals 2
invoke-static {}, Lcom/samsung/android/app/twatchmanager/util/HostManagerUtils;->isSamsungDevice()Z
move-result v0
if-eqz v0, :cond_0
invoke-static {}, Lcom/samsung/android/app/twatchmanager/util/FloatingFeatureFactory;->get()Lcom/samsung/android/app/watchmanager/libinterface/FloatingFeatureInterface;
move-result-object v0
const-string v1, "SEC_FLOATING_FEATURE_CONTEXTSERVICE_ENABLE_SURVEY_MODE"
[COLOR="red"]invoke-interface {v0, v1}, Lcom/samsung/android/app/watchmanager/libinterface/FloatingFeatureInterface;->getEnableStatus(Ljava/lang/String;)Z[/COLOR]
move-result v0
if-eqz v0, :cond_0
const/4 v0, 0x1
:goto_0
sput-boolean v0, Lcom/samsung/android/app/twatchmanager/log/LoggerUtil$Builder;->SUPPORT_LOGGING:Z
return-void
:cond_0
const/4 v0, 0x0
goto :goto_0
.end method
that tries to access an method in a class just available on a samsung device and its framework:
Code:
.method public getEnableStatus(Ljava/lang/String;)Z
.locals 1
invoke-static {}, Lcom/samsung/android/feature/FloatingFeature;->getInstance()Lcom/samsung/android/feature/FloatingFeature;
move-result-object v0
[COLOR="red"]invoke-virtual {v0, p1}, Lcom/samsung/android/feature/FloatingFeature;->getEnableStatus(Ljava/lang/String;)Z[/COLOR]
move-result v0
return v0
.end method
It's the only location where a call requires the samsung framework.
So how to fix it:
We just modify the device detection method to return always false:
Code:
.method public static isSamsungDevice()Z
.locals 1
const/4 v0, 0x0
return v0
.end method
...recompile, resign and it's done.
So far I got 4 reports that it indeed works...so it should also for others.
Since I had to resign the app, ensure you uninstall the original one before installing the fixed version.
When an update in playstore drops for the gear app, and it still force closes, uninstall it and install my fixed version again.
Since I won't monitor that thread...someone should shoot me a PM, so I can merge my fix to the new version from playstore.
Code:
[B]Update 06.09.17[/B]
Samsung Gear to fix custom binary message on samsung devices
Gear S Plugin 2.2.03.17061361
Samsung Health 5.12.0.025
[B]Update 30.06.17[/B]
Accessory Service 3.1.51.70612
Gear S Plugin 2.2.03.17041441N
Samsung Health 5.9.1.003
[B]Update 02.04.17[/B]
Accessory Service 3.1.39_170322
[B]Update 01.04.17[/B]
Samsung Gear 2.2.17022862
Gear S Plugin v2.2.03.17032442N
[B]Update 08.02.17[/B]
Added modifications to new [URL="http://www.tizenexperts.com/2017/01/samsung-gear-manager-application-gear-smartwatches-updated-2-2-16121661/?utm_content=buffer51605&utm_medium=social&utm_source=twitter.com&utm_campaign=buffer"]Gear App 2.2.16121661[/URL]
[B]Update 03.02.17[/B]
The installation issue some people were having seems to got resolved by signing the Gear S Plugin and Samsung Accessory Service with the same signature as the resigned Gear App.
All three files are uploaded on Google Drive now (xda does not allow zips > 20mb, and no single apks > 8MB)
Downloads:
Samsung Gear Apps
Great I was looking for this gear thing since a long time
Thanks buddy
Thank you so much man , was waiting for this
Thank you so much !!!, I was waiting for months this solution !!
66 downloads, seems a a few waited for that fix
wow! well done!
Looks like a similar method used to fix an almost identical crash with the Gear 360/Gear VR apps: https://forum.xda-developers.com/android/software/mod-samsung-gear-360-manager-device-t3400383
Quinny899 said:
Looks like a similar method used to fix an almost identical crash with the Gear 360/Gear VR apps: https://forum.xda-developers.com/android/software/mod-samsung-gear-360-manager-device-t3400383
Click to expand...
Click to collapse
Do you think will this method also fix the FC in the Galaxy S7 ported camera app on non-samsund ROMs/devices?
Thank you very much for your work on this, I was looking for this for almost a month.
I can confirm its working on Xiamoi MI 4S with xiaomi.eu ROM (8.1.3)
Kikill3r said:
Do you think will this method also fix the FC in the Galaxy S7 ported camera app on non-samsund ROMs/devices?
Click to expand...
Click to collapse
Depends what the force close is, do you have a logcat?
Quinny899 said:
Depends what the force close is, do you have a logcat?
Click to expand...
Click to collapse
I can make one
I'll flash the app and report back
If you manage to do this, the entire AOSP community will love you, I guarantee it. I have a Galaxy S7 on AOSP and the camera quality in the stock AOSP camera app is horrible. I've been looking everywhere for a S7 TouchWiz camera app port that works on AOSP, but none of them work
Oh yes I forgot to say, the app is a flashable zip that also contains frameworks and libraries and so on. Will this be a problem?
Here you go, I got the logcat and the flashable zip for you. I hope you can do anything with it... :/
Link for zip: https://mega.nz/#!jE9TzTYQ!BzlWWYYIeNAYkpdlCAi853PWvlVGdIwEQhlMepNUqSo
Kikill3r said:
Here you go, I got the logcat and the flashable zip for you. I hope you can do anything with it... :/
Link for zip: https://mega.nz/#!jE9TzTYQ!BzlWWYYIeNAYkpdlCAi853PWvlVGdIwEQhlMepNUqSo
Click to expand...
Click to collapse
can take a look when my son is in bed.
Kikill3r said:
Here you go, I got the logcat and the flashable zip for you. I hope you can do anything with it... :/
Link for zip: https://mega.nz/#!jE9TzTYQ!BzlWWYYIeNAYkpdlCAi853PWvlVGdIwEQhlMepNUqSo
Click to expand...
Click to collapse
...was a different issue. It expects some logging methods in the framework that does not exist in yours.
I removed all the calls...but it might crash elsewhere
push the file to /system/app/SamsungCamera5
...no idea how your manufacturer handles sigantures or if your rom got signature checks removed.
it if does not work, try to install the signed apk manually
@j to the 4n
I have not bought the the Gear S3 again yet, but tried to install the modified apk on my phone to test
This works, but now I can't install the associated apps Gear S Plugin and Samsung Accessory Service
The apps are downloaded and will install, but then an error message appears (s. screenshot in the attachment)
When reinstalling the original app, the installation of the additional apps will work again
I do not think this can work like this with the watch
Are you able to fix that?
My phone is the Huawei MediaPad X2, stock rom 5.0
https://forum.xda-developers.com/gear-s3/themes/how-to-gear-s3-unsupporteted-android-t3521532
----------------------------------------------------------------------
In Deinen Daten sehe ich, dass Du aus Deutschland kommst.
Da mein English nicht (mehr) so gut ist, hier nochmal das selbe Thema auf Deutsch (etwas ausführlicher):
Erst einmal herzlich Dank für Deine Bemühungen, den Absturzproblemen der GearApp auf den Grund zu gehen.
Ich bin bereits einige Zeit dabei, für die Suche nach einer Lösung zu werben.
Wegen der drehbaren Lünette hatte ich die Gear S3 bei Amazon bereits vorbestellt gehabt, weil ich mit der Bedienung von Android-Wear nicht so zufrieden bin, trotzdem die HuaweiWatch grundsäztlich einwandfrei funktioniert.
Leider zeigte sich dann, dass die GearApp für mein Phone nicht einmal im Playstore angeboten wird, also habe ich die apk über meinen Bluestacks Player auf dem PC gezogen, denn dieser erlaubt verrückterweise den Download, vermutlich weil er sich als Samsung-Device ausgibt.
So hat die Installation dann auch problemlos funktioniert
In den beiden Zusatzapps ist interessanterweise keine derartige Restriktion eingebaut, sodass diese geradeaus über den PlayStore, auch für das X2 aufrufbar sind.
Leider stürzte die GearApp dann zum Start der Installation der S3 ab, (die Bluetooth-Erkennung funktioniert noch) genau dann, wenn auf den Playstore zur Install der 'Gear S Plugin App' verwiesen wird, sollte diese noch nicht auf dem Phone sein, wohl genauso, wie bei vielen Custom-Roms.
Deshalb hatte ich die Uhr erst einmal wieder zurückgegeben.
Mit der von dIr kreierten, modifzierten App habe ich nun eine neue, bis dahin unbekannte Erscheinung (s. Screenshot):
Mit der Installation lassen sich die beiden Zusatzapps nicht mehr aufspielen, weil deren Install. mit einer Fehlermeldung abgebrochen wird.
Nach dem Deinstall. und Install. der originalen, funktioniert das mit den Zusatzapps wieder störungsfrei
Ich habe übrigens auch mit einer Integration der GearApp in das System experimentiert, weil sich so u.A. das bisw. "etwas zickige" Huawei Berechtigungsystem umgehen läßt, aber selbst das bringt leider keine Änderung...
(mein X2 ist also rooted, die Software aber ansonsten komplett Serie (Andriod-Version 5.0))
Es wäre schön, wenn sich auch hier eine Lösung finden würde.
Denn sollte das Update auf AndroidWear2.0, welches für den 9.Februar angesagt ist, keine entscheidenden Verbesserungen in der Bedienung bringen, würde ich es mit der Gear S3 gern nochmals versuchen.
kajos said:
@j to the 4n
I have not bought the the Gear S3 again yet, but tried to install the modified apk on my phone to test
This works, but now I can't install the associated apps Gear S Plugin and Samsung Accessory Service
The apps are downloaded and will install, but then an error message appears (s. screenshot in the attachment)
When reinstalling the original app, the installation of the additional apps will work again
I do not think this can work like this with the watch
Are you able to fix that?
My phone is the Huawei MediaPad X2, stock rom 5.0
https://forum.xda-developers.com/gear-s3/themes/how-to-gear-s3-unsupporteted-android-t3521532
----------------------------------------------------------------------
In Deinen Daten sehe ich, dass Du aus Deutschland kommst.
Da mein English nicht (mehr) so gut ist, hier nochmal das selbe Thema auf Deutsch (etwas ausführlicher):
Erst einmal herzlich Dank für Deine Bemühungen, den Absturzproblemen der GearApp auf den Grund zu gehen.
Ich bin bereits einige Zeit dabei, für die Suche nach einer Lösung zu werben.
Wegen der drehbaren Lünette hatte ich die Gear S3 bei Amazon bereits vorbestellt gehabt, weil ich mit der Bedienung von Android-Wear nicht so zufrieden bin, trotzdem die HuaweiWatch grundsäztlich einwandfrei funktioniert.
Leider zeigte sich dann, dass die GearApp für mein Phone nicht einmal im Playstore angeboten wird, also habe ich die apk über meinen Bluestacks Player auf dem PC gezogen, denn dieser erlaubt verrückterweise den Download, vermutlich weil er sich als Samsung-Device ausgibt.
So hat die Installation dann auch problemlos funktioniert
In den beiden Zusatzapps ist interessanterweise keine derartige Restriktion eingebaut, sodass diese geradeaus über den PlayStore, auch für das X2 aufrufbar sind.
Leider stürzte die GearApp dann zum Start der Installation der S3 ab, (die Bluetooth-Erkennung funktioniert noch) genau dann, wenn auch der Playstore zur Install der 'Gear S Plugin App' verweist, sollte diese noch nicht auf dem Phone sein, wohl genauso, wie bei vielen Custom-Roms.
Deshalb hatte ich die Uhr erst einmal wieder zurückgegeben.
Mit der von dIr kreierten, modifzierten App habe ich nun eine neue, bis dahin unbekannte Erscheinung (s. Screenshot):
Mit der Installation lassen sich die beiden Zusatzapps nicht mehr aufspielen, weil deren Install. mit einer Fehlermeldung abgebrochen wird.
Nach dem Deinstall. und Install. der originalen, funktioniert das mit den Zusatzapps wieder störungsfrei
Ich habe übrigens auch mit einer Integration der GearApp in das System experimentiert, weil sich so u.A. das bisw. "etwas zickige" Huawei Berechtigungsystem umgehen läßt, aber selbst das bringt leider keine Änderung...
(mein X2 ist also rooted, die Software aber ansonsten komplett Serie (Andriod-Version 5.0))
Es wäre schön, wenn sich auch hier ein Lösung finden würde.
Denn sollte das Update auf AndroidWear2.0, welches für den 9.Februar angesagt ist, keine entscheidenden Verbesserungen in der Bedienung bringen, würde ich es mit der Gear S3 gern nochmals versuchen.
Click to expand...
Click to collapse
Never saw such behavior, that playstore denies installations of dependent apps. If you have no gear app installed at all, you can't install the apps?
..well you could always install the original gear, then the other apps. Uninstall the gear app, then install mine?
..also the apps are available on apkmirror, you can download and install them from there.
Not sure sure why it seem to work for all others...
Want to make one thing clear here though: I don't own gear myself and never will..I'm just a good guy that wanted to help out some of gear users on our rom (HTC 10).
Means i can't do any deeper debugging, besides reading logs people provide me.
I'm also very confused why no other dev (that owns a gear, and is familar with it and Samsung) looked into it, because it was an really easy fix.
j to the 4n said:
..well you could always install the original gear, then the other apps. Uninstall the gear app, then install mine?
.
Click to expand...
Click to collapse
- original + GearSPlugin + SamsungAcessoryService works
- delete original + install mod not working : error message
- delete all 3 apps + install mod working + GearSPlugin + SamsungAcessoryService not working : error message
Wait a minute....so you're saying I can FINALLY use my Samsung Gear S with a non-samsung phone?!?! I've been waiting soo, soooo long for this. Can't wait to give it a shot.
Thank you very much for your work!
kajos said:
- original + GearSPlugin + SamsungAcessoryService works
- delete original + install mod not working : error message
- delete all 3 apps + install mod working + GearSPlugin + SamsungAcessoryService not working : error message
Click to expand...
Click to collapse
What error message you get when you have the other apps installed and then install my modded version?
j to the 4n said:
What error message you get when you have the other apps installed and then install my modded version?
Click to expand...
Click to collapse
I tried it again now!
- all Samsung Apps are deinstalled on my Phone
then
- Gear S Plugin + Samsung Accessoire Service install
then
- your mod
see attachment
(I'm able to install your mod without them, but no way along with)
Enclosed the Komoot apps for the mobile and gear.
1) Rename SAPServiceConsumer.zip to SAPServiceConsumer.wgt and install via sdb on your gear (https://forum.xda-developers.com/showpost.php?p=75687360&postcount=9)
2) Install the apk on your mobile and ignore the error message that it was not correctly installed (do not confirm de-installation)
Not working on my gear s3.
I can install the apk on my mate 10 pro and i can install the wgt on my gear s3 ( both without error message).
The apk even says connected to gear but my gear only shows a green flashing point.
And my mobile data on my mate 10 cuts off... strange
would be awesome if we can fix that mate
I got a HTC 10 and Gear Sport and it seems to work. :good:
When I connect, I do see the flashing point first. Then I start navigation or tracking in Komoot on my phone and the watch shows information about the route.
The only thing that did not work: When you are on a track and do not get any navigation-messages, the watch is in foreground until there's a new navigation message. Then Komoot gets in foreground again. This might also be an issue of the original app, I don't know.
That's unfortunately normal behaviour...
Error message during installation
For me it's not working. Got an error message during the installation of the *.wgt file. Seems to be something with the write protection but you are not able to type a confirmation. From my understanding it's asking about the deleting of the write protected file. Any ideas? Appreciate your help in this case. Tanks in advance.
C:\tools>sdb install SAPServiceConsumer.wgt
pulled SAPServiceConsumer.wgt 100% 1MB
1 file(s) pulled. 0 file(s) skipped.
SAPServiceConsumer.wgt 954 KB/s (1386575 bytes in 1.418s)
path is /opt/usr/home/owner/apps_rw/tmp/SAPServiceConsumer.wgt
__return_cb req_id[1] pkg_type[wgt] pkgid[deKomoot14] key[start] val[install]
__return_cb req_id[1] pkg_type[wgt] pkgid[deKomoot14] key[install_percent] val[8]
__return_cb req_id[1] pkg_type[wgt] pkgid[deKomoot14] key[install_percent] val[11]
__return_cb req_id[1] pkg_type[wgt] pkgid[deKomoot14] key[install_percent] val[14]
__return_cb req_id[1] pkg_type[wgt] pkgid[deKomoot14] key[install_percent] val[17]
__return_cb req_id[1] pkg_type[wgt] pkgid[deKomoot14] key[install_percent] val[20]
__return_cb req_id[1] pkg_type[wgt] pkgid[deKomoot14] key[error] val[-27] error message: :Side loading error
__return_cb req_id[1] pkg_type[wgt] pkgid[deKomoot14] key[end] val[fail]
processing result : Undefined Error [-27] failed
spend time for pkgcmd is [2978]ms
rm: remove write-protected regular file `/opt/usr/home/owner/apps_rw/tmp/SAPServiceConsumer.wgt'?
Chrispy19 said:
For me it's not working. Got an error message during the installation of the *.wgt file. Seems to be something with the write protection but you are not able to type a confirmation. From my understanding it's asking about the deleting of the write protected file. Any ideas? Appreciate your help in this case. Tanks in advance.
C:\tools>sdb install SAPServiceConsumer.wgt
pulled SAPServiceConsumer.wgt 100% 1MB
1 file(s) pulled. 0 file(s) skipped.
SAPServiceConsumer.wgt 954 KB/s (1386575 bytes in 1.418s)
path is /opt/usr/home/owner/apps_rw/tmp/SAPServiceConsumer.wgt
__return_cb req_id[1] pkg_type[wgt] pkgid[deKomoot14] key[start] val[install]
__return_cb req_id[1] pkg_type[wgt] pkgid[deKomoot14] key[install_percent] val[8]
__return_cb req_id[1] pkg_type[wgt] pkgid[deKomoot14] key[install_percent] val[11]
__return_cb req_id[1] pkg_type[wgt] pkgid[deKomoot14] key[install_percent] val[14]
__return_cb req_id[1] pkg_type[wgt] pkgid[deKomoot14] key[install_percent] val[17]
__return_cb req_id[1] pkg_type[wgt] pkgid[deKomoot14] key[install_percent] val[20]
__return_cb req_id[1] pkg_type[wgt] pkgid[deKomoot14] key[error] val[-27] error message: :Side loading error
__return_cb req_id[1] pkg_type[wgt] pkgid[deKomoot14] key[end] val[fail]
processing result : Undefined Error [-27] failed
spend time for pkgcmd is [2978]ms
rm: remove write-protected regular file `/opt/usr/home/owner/apps_rw/tmp/SAPServiceConsumer.wgt'?
Click to expand...
Click to collapse
I have exactly the same problem. Anyone had a way to fix that? I want to use komoot on my gear s3 with a Huawei p20 pro.
Thank you.
Marcel Nick said:
I have exactly the same problem. Anyone had a way to fix that? I want to use komoot on my gear s3 with a Huawei p20 pro.
Thank you.
Click to expand...
Click to collapse
Look here: https://forum.xda-developers.com/gear-s3/help/gear-s3-wgt-sideload-error-t3795561
And try this: https://forum.xda-developers.com/gear-fit/general/howto-sign-sideload-tizen-applications-t3639793
I had to do the same after I changed my phone and reassigned the smartwach. Now it works again.
Hi,
Tell me if i'm wrong but..
If someone can extract original S3 frontier app (need to be root on S3 i think)
You copy the app (with S3 file manager - no needed to be root) on your S3 and install it and it's done ?!! no ??
the people who don't have a samsung phone can't see the S3 Komoot on the store but if you inject directly, you have the source and it's must be working.
The difficulty is to be root on S3 and have a Samsung in first to install Komoot application, after it's must be simple to extract the Komoot app from S3 and give it to us ^^
godsavenger said:
Hi,
Tell me if i'm wrong but..
If someone can extract original S3 frontier app (need to be root on S3 i think)
You copy the app (with S3 file manager - no needed to be root) on your S3 and install it and it's done ?!! no ??
the people who don't have a samsung phone can't see the S3 Komoot on the store but if you inject directly, you have the source and it's must be working.
The difficulty is to be root on S3 and have a Samsung in first to install Komoot application, after it's must be simple to extract the Komoot app from S3 and give it to us ^^
Click to expand...
Click to collapse
hmm, extactly that is what I did and you find the Gear app in the first post of this thread
Anyone know if this is still working?
After install on both phone and watch, can you get regular app updates from Tizen store and Play store? Or are updates blocked due to phone not being a Samsung phone?
Komoot auf Gear s3 Frontier
Hallo ich bin neu hier und hatte mich hier mal durch gelesen vieleicht kann mir einer weiter helfen. ich hab alles wie in der Anleitung gemacht und hab glaube ich ne Fehler Meldung. bin in Englisch nicht gerade der beste so das ich einiges nicht ganz verstehe. kann mir einer weiter helfen. grüsse aus Deutschland
daromani said:
Anyone know if this is still working?
After install on both phone and watch, can you get regular app updates from Tizen store and Play store? Or are updates blocked due to phone not being a Samsung phone?
Click to expand...
Click to collapse
also ich habs auspropiert und komme nicht weiter immer wieder fehlermeldung
Can anybody write an actual status about this topic?
Is the komoot gear app working with non Samsung devices, or still just errors during installation? Thanks
Nein hab auch leider noch nichts neues gehört. Hatte es auch mit der Anleitung versucht und bekomme immer ne Fehlermeldung auf dem PC
Just for some info on the topic, i just used this to install the komoot app on my galaxy watch sport. Worked as explained
Can anyone confirm that this is still working? I'm using an Active 2 with an OnePlus 6.
for the ones having the error... did you check signing the application newly as this package here was signed for tizen 2.x if I remember right. How to do that was already mentioned on page 1.
pls see again:
https://forum.xda-developers.com/smartwatch/gear-fit/howto-sign-sideload-tizen-applications-t3639793
Maybe someone having a Samsung phone could provide us an updated komoot wgt file extracted from the phone.
Arno_Nymus said:
Can anyone confirm that this is still working? I'm using an Active 2 with an OnePlus 6.
Click to expand...
Click to collapse
English:
Can confirm this still works. I'm using a Pixel3 Smartphone with a Samsung Gear Sport. The only thing missing in the documentation is, that I had to restart my watch after activating debug mode in order to accept connections via sdb. Works like a charm, kudos to the guy who documented this in the first place!
German:
Ich kann bestätigen, dass es noch immer funktioniert. Ich nutze ein Pixel3 Smartphone in Verbindung mit der Samsung Gear Sport. Es fehlte nur ein Punkt in der Doku: Ich musste meine Uhr neu starten nachdem ich den Debug Mode aktiviert hatte, damit sie die Verbindung via sdb akzeptiert. Hab die App gerade kurz getestet, funktioniert super. Vielen Dank an denjenigen, der sich die mühe gemacht hat, diese Anleitung zu verfassen.