FORUMS
Remove All Ads from XDA

[MOD][PORT] Samsung Gear 360 Manager for all devices [Updated: 20/May/18, v1.2.00.8]

7,446 posts
Thanks Meter: 6,040
 
Post Reply Email Thread


Samsung Gear 360 Manager ported for use on (almost) all devices

LAST UPDATED: 20th May 2018, Version 1.2.00.8

Requirements:
- A Gear 360 2016 or 2017 (BOTH work with the same app)
- Android 5.0 or above
- A decently powerful phone. The Live View will not work on any phones with the equivalent or lower power than a Galaxy S5, but try it anyway

Latest Version Download:
Download

Screenshots:
Click a screenshot to enlarge it

Main Menu

Live View (camera is covered)

Gallery View

Image View

360 Image viewer

360 Video viewer (there's steam in this shot, that's not the camera quality!)

Settings

Mod Settings



Known Issues:
- Live View does not work on slow/older devices. This is unlikely to be fixed, but I am looking at implementing the "no live view" mod (which still works on 2016 cameras) as an option

- App is slow, downloads take ages. Probably down to the proprietary/disabled code from Samsung in the app for checking CPU speed. May be fixed soon

- Live Broadcast doesn't work on 2016 camera or when using Soft AP. Latter cannot be fixed, former may be able to be ported with enough time (not sure)

- WiFi Direct is buggy. Probably down to the app's mode being made for Samsung's modified WiFi direct, unlikely to be fixed

- WiFi doesn't automatically connect/gets disconnected. This is down to Android's smart detection of networks, it connects to a network with a known good internet connection instead. You can disable this with ADB/Root, see here

FAQ:

Q: What's the difference between WiFi direct/non WiFi Direct (Soft AP) mode?
A: WiFi Direct uses an experimental modification for enabling the Samsung WiFi Direct mode for all devices. It's quite buggy right now, but in theory allows you to update the camera's firmware (known to be dangerous, be careful). It also means you don't disconnect from the internet when using the app

Q: It's stuck on "Installing Samsung accessory service"
A: Install it manually

Q: I'm trying to use Live View/Gallery but the app gets stuck on loading
A: (If in Soft AP/WiFi Mode): Open Settings > WiFi and connect to the Gear 360 network. Disable your mobile data and any VPNs you may be using, and disconnect from any Bluetooth headphones or speakers (turn them off). Return to the app
A: (If in WiFi Direct Mode): Open Settings > WiFi > Advanced > WiFi Direct, and remove any old remembered groups. Wait for the Gear 360 to appear and tap it to connect. If it returns to available, tap it, delete it and repeat until connected. Then press back until you return to the app

Q: I have a 2017 camera and don't know the password for its WiFi!
A: Switch your camera to iOS mode (on the camera itself, using the menu). It will display a password, write that down. Switch back to the normal mode and continue as normal, entering the WiFi password you wrote down when prompted

Q: Does Live Broadcast work?
A: On the 2017 camera, when in WiFi direct mode apparently so. I've not tested it, and it doesn't work on any other configuration however

Q: What do the mod settings do?
A: See the "Mod Settings" section below

Q: There's a new version of the app on the Play Store, when will you update?
A: Check the last few pages of the thread. If the original APK has been posted already, the mod will be updated soon™. If it hasn't been, and you have a Samsung device compatible with the original app, please grab the APK and post it (the original APK is hard to get hold of)

Q: I found a crash!
A: Please post it in the thread, WITH A LOGCAT (don't know how to logcat? See here)

Mod Settings:
Since version 1.0.00.18, the mod has built in settings to allow a single unified APK. They can be found in the app's settings, under Mod Settings

WiFi Direct
Enable WiFi direct mode. Disabled by default as it's fairly buggy

Override Camera Recognition
Force your camera to appear to the app as a certain model. This isn't actually that useful, as it just causes crashes because of incompatible settings (default: don't override)

Always Show Live Broadcast
This is NOT aimed at allowing broadcast on 2016 cameras (they can't do it), but at countries where Live Broadcast is hidden. Enable this to always show it (disabled by default)

Automatically Open Settings
Automatically open the WiFi Settings/WiFi Direct settings when connecting to save you time (enabled by default)

Porting Guide:
I don't plan to stop updating the mod any time soon, but if you want to port it yourself I have a rough guide available Here

Old Versions:
You probably shouldn't use these, they have bugs

1.1.00.5
1.0.00.18
"Test" build 190617
1.0.00-2: WiFi Direct, Soft AP
Even older, pre-2017 camera app:
1.0.18-39
1.0.18-34: 4K, 2K


Thanks to:
- Bin4ry for the original port

Tools used:
- Apktool
- V10 Studio/Notepad++ for smali editing
- JEB for viewing Java code in APK

Disclaimer: You are responsible for your Gear 360 when using this app. Updating the firmware, whilst possible in WiFi Direct mode, may brick your device. It's recommended you find a compatible Samsung device and use that to update
The Following 65 Users Say Thank You to Quinny899 For This Useful Post: [ View ]
 
 
17th June 2016, 10:52 PM |#2  
Quinny899's Avatar
OP Recognized Developer / Recognized Contributor
Flag Ormskirk, Lancashire, UK
Thanks Meter: 6,040
 
Donate to Me
More
Thanks to @Bin4ry for the original port, this is his OP from before work was transferred to me:

Deprecated archived post:


Hi all,

in the last days i was working on a port of the Gear 360 Manager app.
You should be able to use the app now even with non-Galaxy devices, or older Galaxy devices which are not officially supported by Samsung. I myself use it with a Sony Xperia Z5 without problems now

Mods:
1.) Removed device lock
2.) Forced 4K Video support, this way the app does NOT downgrade videos to 2k for other devices than Galaxy S7!
3.) Several Mods needed to get the app running on non-galaxy devices!

Requirements:
1.) You need to be on Android 5.0 or higher (App depends on API Level 21!)
2.) You need to install Samsung Accessory Service from playstore Link (they come preinstalled on many Samsung phones and the playstore may tell you incompatible )


Download the modified version (currently based on original Samsung Gear360 Manager version 1.0.4) here:

Update:
Version 1.0.10:

Force 2k Version : http://ul.to/5zsfz9mr
Force 4k Version: http://ul.to/kysjk5c8

IF YOU ARE RUNNING NOUGAT see this post of User Quinny899, he modded the new Nougat app:
https://forum.xda-developers.com/sho...&postcount=418

Known problem for this verison 1.0.10:
Make sure you allow the permissions (on my devices the permission are not requested automatically). To do that go to:
Settings -> Apps -> Gear 360 Manager -> Permissions -> Allow everything there.



Old Verson 1.0.4:

Update 20.06.2016: Even longer videos can now be stiched in 4k [tested on Xperia Z5] and some more bugfixes!
Force 4k Version : http://ul.to/i8ieooet
Force 2k Version: http://ul.to/uznv4asf



Make sure to download the file correctly, if you have any issues while installing make sure you are on Android 5 or higher!

Known issues:
1.) When switching to LiveView and Device browsing sometimes the app shows only "loading..." without doing something!
--> Please check if you phone is connected to the Cameras Wifi (normally Called "AP_GEAR360..."). If you are still connected to you homenetwork etc. please just manually connect to the gear's wifi and switch back to the gear manager app
2.) Sometimes the Samsung Accessory Service force closes while using the app!
--> If that happens go to Android Settings -> Apps -> choose the Samsung Accessory Service and click "Stop now", also go to the Gear 360 Manager and click "Stop now" here too! After that just open the Gear 360 manager again and continue working.
3.) Overlayicons in the Liveview are low-res and look crappy, i will try to fix that in a future release.
4.) On some phones the stiching of videos > 10 seconds will take very long time. In this case please use the Force 2k Version, 4k maybe too much for your phone to handle!
5.) Problably more, i don't use share to social media or stuff like that, so these points are still untested.

X.) If your phone seem not to support Live view you can try this mod by RostoVisualFX http://forum.xda-developers.com/show....php?t=3471526

That's it for now. If you have any issue please make sure to include a logcat output for me. Without an log i cannot help you.



Disclaimer: I am not responsible for anything that happens to your hardware.


Best Regards
17th June 2016, 10:52 PM |#3  
Junior Member
Thanks Meter: 1
 
More
My Note 4 completely died today. No power, not even with USB cable connected. Not sure if the installation of the app has caused this but I thought I'd mention it. I haven't had any issues with the phone before. Could be a total coincidence, of course. Will have to send the phone in for repair
18th June 2016, 01:55 AM |#4  
Junior Member
Thanks Meter: 2
 
More
I have attempted to use this software with the Note 3, but I am running into some issues.


Whenever I click on live view it seems to freeze up and I keep viewing a black screen with the camera options. After about 10 seconds, the screen turns black and then returns to the app after 10 more seconds. I am unsure if I am connecting through wifi direct.

When I try to share a gear 360 pic or video from my phone, it takes me to the flipboard share screen.

I can't view images or videos from the camera. Whenever I click on the media it attempts to stitch the images together, but only gets about 60% done.

I am able to view images and videos which have already been stitched and transferred from the computer, but it is pretty glitchy and doesn't always work.


Thanks for your work thus far, Bin4ry. This will be amazing if it works on many different phones.
18th June 2016, 09:14 AM |#5  
Bin4ry's Avatar
Recognized Developer
Flag Schwelm (NRW)
Thanks Meter: 5,933
 
Donate to Me
More
Quote:
Originally Posted by efassbender

My Note 4 completely died today. No power, not even with USB cable connected. Not sure if the installation of the app has caused this but I thought I'd mention it. I haven't had any issues with the phone before. Could be a total coincidence, of course. Will have to send the phone in for repair

Hey,
that sounds very strange. But i cannot imagine how the app can cause such problems, because this is a normal userspace app and it does not have any access to relevant system files, bootloader or such. I can only think of a strange coincidence. Hope you will get your phone repaired soon. Maybe you some things, this guy tells a few tricks about the issue:
http://thedroidguy.com/2015/07/how-t...g-guide-108854

Quote:
Originally Posted by billford22

I have attempted to use this software with the Note 3, but I am running into some issues.


Whenever I click on live view it seems to freeze up and I keep viewing a black screen with the camera options. After about 10 seconds, the screen turns black and then returns to the app after 10 more seconds. I am unsure if I am connecting through wifi direct.

When I try to share a gear 360 pic or video from my phone, it takes me to the flipboard share screen.

I can't view images or videos from the camera. Whenever I click on the media it attempts to stitch the images together, but only gets about 60% done.

I am able to view images and videos which have already been stitched and transferred from the computer, but it is pretty glitchy and doesn't always work.


Thanks for your work thus far, Bin4ry. This will be amazing if it works on many different phones.

Hey, thanks for the feedback. Can you please provide me a logcat of the problems, like mentioned in the first post i really need such thing to be able to help.

Best Regards
The Following User Says Thank You to Bin4ry For This Useful Post: [ View ]
18th June 2016, 11:41 AM |#6  
Junior Member
Thanks Meter: 0
 
More
I just tested on a nexus 4, it connect ok, but I can't see 360 folders or anything, I'll try to upload the log later.
18th June 2016, 02:33 PM |#7  
Junior Member
Thanks Meter: 3
 
More
Bluetooth settings crash
After installing the modded app everything worked fine. But now everytime i try to access the android bluetooth settings it crashes. Has anyone experienced the same problem?
The Following 2 Users Say Thank You to Hasmax78 For This Useful Post: [ View ] Gift Hasmax78 Ad-Free
18th June 2016, 02:56 PM |#8  
Bin4ry's Avatar
Recognized Developer
Flag Schwelm (NRW)
Thanks Meter: 5,933
 
Donate to Me
More
Quote:
Originally Posted by blacksrv

I just tested on a nexus 4, it connect ok, but I can't see 360 folders or anything, I'll try to upload the log later.

Please provide the log ☺
18th June 2016, 02:57 PM |#9  
Bin4ry's Avatar
Recognized Developer
Flag Schwelm (NRW)
Thanks Meter: 5,933
 
Donate to Me
More
Quote:
Originally Posted by Hasmax78

After installing the modded app everything worked fine. But now everytime i try to access the android bluetooth settings it crashes. Has anyone experienced the same problem?

Strange thing. Try to uninstall the app and Samsung accessory service. This should not really happen!
19th June 2016, 09:39 AM |#10  
Member
Flag Genoa, Italy & Augsburg, Germany
Thanks Meter: 4
 
More
The 2K versions opens on a Motorola X (2014), it connects to the Gear 360. Clicking on live view begins to load the gui with all the buttons and then the screen goes black.
The log is from the app aLogcat, hope it helps:
Code:
--------- beginning of main
W/InputEventReceiver(26907): Attempted to finish an input event but the input event receiver has already been disposed.
I/WebViewFactory(26907): Loading com.google.android.webview version 51.0.2704.81 (code 270408100)
I/cr_LibraryLoader(26907): Time to load native libraries: 15 ms (timestamps 5548-5563)
I/cr_LibraryLoader(26907): Expected native library version number "51.0.2704.81", actual native library version number "51.0.2704.81"
V/WebViewChromiumFactoryProvider(26907): Binding Chromium to main looper Looper (main, tid 1) {3448aa18}
I/cr_LibraryLoader(26907): Expected native library version number "51.0.2704.81", actual native library version number "51.0.2704.81"
I/chromium(26907): [INFO:library_loader_hooks.cc(143)] Chromium logging enabled: level = 0, default verbosity = 0
I/cr_BrowserStartup(26907): Initializing chromium process, singleProcess=true
E/ApkAssets(26907): Error while loading asset assets/natives_blob_64.bin: java.io.FileNotFoundException: assets/natives_blob_64.bin
E/ApkAssets(26907): Error while loading asset assets/snapshot_blob_64.bin: java.io.FileNotFoundException: assets/snapshot_blob_64.bin
I/Adreno-EGL(26907): <qeglDrvAPI_eglInitialize:410>: EGL 1.4 QUALCOMM build: AU_LINUX_ANDROID_LA.AF.1.1_RB1.05.00.02.006.020_msm8960_LA.AF.1.1_RB1__release_AU ()
I/Adreno-EGL(26907): OpenGL ES Shader Compiler Version: E031.25.03.06
I/Adreno-EGL(26907): Build Date: 03/30/15 Mon
I/Adreno-EGL(26907): Local Branch: mybranch8688311
I/Adreno-EGL(26907): Remote Branch: quic/LA.AF.1.1_rb1.16
I/Adreno-EGL(26907): Local Patches: NONE
I/Adreno-EGL(26907): Reconstruct Branch: AU_LINUX_ANDROID_LA.AF.1.1_RB1.05.00.02.006.020 + 9b2699f + 2215637 + 60aa592 + f2362e6 + 5c64f59 + 82411a1 + 1f36e07 +  NOTHING
W/cr_media(26907): Requires BLUETOOTH permission
19th June 2016, 11:02 AM |#11  
Bin4ry's Avatar
Recognized Developer
Flag Schwelm (NRW)
Thanks Meter: 5,933
 
Donate to Me
More
Quote:
Originally Posted by ThomasKru

The 2K versions opens on a Motorola X (2014), it connects to the Gear 360. Clicking on live view begins to load the gui with all the buttons and then the screen goes black.
The log is from the app aLogcat, hope it helps:

Code:
--------- beginning of main
W/InputEventReceiver(26907): Attempted to finish an input event but the input event receiver has already been disposed.
I/WebViewFactory(26907): Loading com.google.android.webview version 51.0.2704.81 (code 270408100)
I/cr_LibraryLoader(26907): Time to load native libraries: 15 ms (timestamps 5548-5563)
I/cr_LibraryLoader(26907): Expected native library version number "51.0.2704.81", actual native library version number "51.0.2704.81"
V/WebViewChromiumFactoryProvider(26907): Binding Chromium to main looper Looper (main, tid 1) {3448aa18}
I/cr_LibraryLoader(26907): Expected native library version number "51.0.2704.81", actual native library version number "51.0.2704.81"
I/chromium(26907): [INFO:library_loader_hooks.cc(143)] Chromium logging enabled: level = 0, default verbosity = 0
I/cr_BrowserStartup(26907): Initializing chromium process, singleProcess=true
E/ApkAssets(26907): Error while loading asset assets/natives_blob_64.bin: java.io.FileNotFoundException: assets/natives_blob_64.bin
E/ApkAssets(26907): Error while loading asset assets/snapshot_blob_64.bin: java.io.FileNotFoundException: assets/snapshot_blob_64.bin
I/Adreno-EGL(26907): <qeglDrvAPI_eglInitialize:410>: EGL 1.4 QUALCOMM build: AU_LINUX_ANDROID_LA.AF.1.1_RB1.05.00.02.006.020_msm8960_LA.AF.1.1_RB1__release_AU ()
I/Adreno-EGL(26907): OpenGL ES Shader Compiler Version: E031.25.03.06
I/Adreno-EGL(26907): Build Date: 03/30/15 Mon
I/Adreno-EGL(26907): Local Branch: mybranch8688311
I/Adreno-EGL(26907): Remote Branch: quic/LA.AF.1.1_rb1.16
I/Adreno-EGL(26907): Local Patches: NONE
I/Adreno-EGL(26907): Reconstruct Branch: AU_LINUX_ANDROID_LA.AF.1.1_RB1.05.00.02.006.020 + 9b2699f + 2215637 + 60aa592 + f2362e6 + 5c64f59 + 82411a1 + 1f36e07 +  NOTHING
W/cr_media(26907): Requires BLUETOOTH permission

Thanks. But the logcat is not complete it is cut after the first startup lines. I need a full one where the error of the gear360 manager is shown.
If alogcat don't give you a full one please use adb logcat and reroute output to a file.

Adb logcat > mylog.txt

This creates the log file in your current directory.

Thanks and best regards
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread