gear360reveng
gear360reveng copied to clipboard
Hacking BT remote mode
Hi,
first of all thanks for the work! I am trying to make timelapse photo mode for Gear 360 (gen.1) which only has video timelapse mode (half reso of photo mode and output format is video). Obviously custom firmware is out of question, since nobody decrypted it yet (all we know it's linux based).
Other option if to use generic bt dongle to emulate official bt remote (which connects to cam in remote mode). Have you tried to hack it maybe? I do not have official bt remote (comes in expensive samsung value bundle), but i got mac address from it. From the log seems it connects, but then camera asks for some unkown service which other side (Kali Linux with bt dongle) doesn't have and disconnects. Could that service be in Samsung Accessory service for android?
any help would be great!
Hi,
Sorry, can't help much here.
On one hand I wouldn't suspect them to use anything non-standard, I don't have enough Bluetooth knowledge to judge that.
If you put the camera in Streetview mode you can take pictures at an interval using the Google streetview app (even on iOS). Apparently in Streetview mode the camera supports the Open Spherical Camera API (or parts of it)
Well, as i thought. Samsung is using Samsung Accessory Framework (custom GATT service) even for a plain thing as bt remote shutter :/ Check this pdf:
developer.samsung.com/html/techdoc/ProgrammingGuide_Accessory.pdf
@neuhaus when using OSC API, camera itself stitches photos (it takes 10-15sec), which is kinda messy since stitching ain't that great (and it's cropped!) and I need shots to be taken faster (every 3-5s). Tho it's really easy to use OSC API and battery drain is, unexpectedly since it's wifi+stitching, almost same as with br remote.
That's some interesting news, thanks for the update. That would explain why I couldn't connect using normal Bluetooth Serial connection.
Hello, I'd like to join the conversation as am also trying to hack in this camera..
I need to have this camera connect to an existing wifi network, from which I would be able to use the OSC api from my server (i.e. to capture pictures and upload through wifi).
I was hoping the 2017 version had the OSC 2.1 version API that has the switchWifi command, unfortunately it still implement the version 1.0. Which means that there is no method out of the box to have the camera connect to another network.
I started to dig around and find out through this or other sites that I could telnet to it , so I though that once inside a telnet session I could start looking on how to change the wlan interface from AP mode to Station mode so it would connect to my desired network instead (the script would go in the SDCard as mod just like the telnet mod).
My problem is that since I am not an experienced linux/unix gui, and since it's a one shot try as swapping the wifi config would kick me out of the telnet session and in the case I messed up I am afraid I would not be able to connect to the camera anymore through the access point.
What do you think, is there a risk to brick the camera this way? Would any change to the filesystem files be permanent or by removing the sdcard with the mods I can go back to its original state? Is it possible to reflash/reset the firmware?
Have you already looked into this kind of problem and how connect to the camera osc api remotely?
Any help would be appreciated and thanks a lot for sharing already all this stuff, it really helped a lot so far.
I'd say the risk is low as long as you do not interfere with the boot scripts (I'm guessing here a bit).
As for the persistence of the filesystem - might be tricky as the camera uses hibernation (dump memory to disk, enter low-power mode). What I would do - write things to internal flash, then do commands sync
and reboot
.
As to safely do experiments with network - I'd do some kind of "reset" mechanism (either a timeout or attach yourself to the button) that resets the WiFi to safe defaults.
Recently I didn't do much with the camera, so can't help you any more than this.
I have the bluetooth remote for the Samsung Gear 360 (2016), if you want I can test something (capture bluetooth data etc). Just tell me what to do.
Hi. Thanks for the offer; I'll pass for the moment. On top of that it might be not that easy to setup bluetooth packet capturing.
Found an interesting related github project: https://github.com/jdeats76/OSCIntervalometer-
Another project using OSC api, i test with 2016 camera and work, conected via wifi as Google Street View mode . The stitching was done inside the camera.
https://github.com/baardove/osc