I need to develop a chat application for Samsung watches running Tizen OS. How can I send messages between the watches?
I am assuming they are on the same Wifi, but we can't implement Wifi direct in Tizen wearables (it is only supported for mobile apps).
The last option would be to send SMS, but that would require them to be connected to mobile devices or have a separate SIM.
Thanks,
another option is using Bluetooth.
There is a sample app in Tizen IDE:
Go to Tizen IDE > File > Project > Tizen Native Project > Online Sample > Network > Bluetooth Chat
Related
I need to send some binary files via bluetooth from tizen g2 watch to android phone and then from phone to watch, as I've searched it I can't implement bluetooth in js files as said here so what is the most straightforward way to do it? can we use tizen wearable debug over bluetooth instead? is it applicable in this case?
I'm new to tizen so I feel confused and I really appreciate any advice about this problem.
You can develop companion app using Samsung Accessory Protocol(SAP) in this scenario. Please go through this link to know more. If you are trying to develop the tizen part in web, then have a look in the File Transfer sample of web section. There're separate applications for sending and receiving files from tizen to android and vice versa. You can combine those to implement the bidirectional communication.
I am planning to develop an iOS application where I need to use VOIP services. I found Liblinphone which is one such open source API for VOIP.
My requirements:
Making voice call & receiving
Making video calls & receiving
Making voice call conferences.
Are these all possible with Liblinphone? Are there any other opensource VOIP libraries for achieving this better than Liblinphone?
Any help and tutorial links are a big helpfor me.
You may take a look at siphon (http://code.google.com/p/siphon/).
From their homepage:
Home of the World's first free SIP/VoIP application for iPhone and iPod Touch 1 and 2.
Siphon SIP/VoIP project is the first in his category that works on iPhone and iPod Touch 2 with headset for all SIP providers. It is a native application approved running on 2.X using internal micro/speaker and headset.
The Application supports the SIP standard, preserving compatibility with hundreds of SIP providers and offers a GUI which preserves the apple design of native iPhone applications.
I'd like to examine the possibility of writing an unofficial Windows 8 (WinRT/Metro) sender API for Chromecast. The goal would be to allow Windows 8 Store apps roughly the same functionality of iOS / Android apps through the official sender API available for those platforms.
I've noticed that, although the inner workings of the API haven't really been exposed yet, some of the source code for the Chromecast device is available, and there's an unofficial emulator for the device out on Github (https://github.com/dz0ny/leapcast).
Is this possible, given how Chromecast devices seem to take commands directly from Google?
ChromeCast is using a proprietary protocol called RAMP (Remote Application Media Protocol) to do media control. Once you have setup your ChromeCast device for development, the device will open a port for remote Chrome debugging. Open Chrome at your ChromeCast device IP address port 9222: http://192.168.0.x:9222/
You should see a page with a link to the receiver page of the currently running ChromeCast app. Click the link and then use Chrome developer tools on that page. Take a look at the network and console tabs to see the RAMP commands.
I have open sourced an Android app that shows you how to discover ChromeCast devices and setup the Websocket connection to handle the RAMP commands: https://github.com/entertailion/DIAL
When I run my web application on the Tizen Web Simulator and the Tizen Emulator using the same resolution (HD 720x1280) and density (DPI), the display does not match. Which one is closer to the display on the actual Tizen device?
Tizen Emulator is closer to the actual device because does an actual emulation so it has an OS image build on it.
Web Simulator is simulating the API, the Web Runtime, and some of the connectivity using Chromium's Webkit engine. It is a simulated environment and there is support only fort the HTML5 applications and not for the native applications.
From my experience with the Tizen Web application API, Tizen Emulator was closer to the actual device compared with the simulator.
There is a scale menu for Tizen Emulator. You can find context menu when you click to right mouse button on the tizen emulator. 4 scales available.
1x
3/4x
1/2x
1/4x
'1x' is closer to actual Tizen device. Tizen simulator display is similar '1/2x' scale of tizen emulator for me.
The Emulator is indeed closer to the device display than the simulator.
However, if you want to see how your app would look on a device, why not flash the Tizen image on a device?
they can be found here, and i'm sure instructions are there also:
http://download.tizen.org/releases/2.1/tizen-2.1/
I was to develop a simple j2me application for microworks. The application is to send sms.
But I found that most of the mobile phone they carry are very simple and even some of them don't have Bluetooth, infrared, browser. How to make it work out?
We can assume configuration as nokia 2100, nokia 1616. How am I supposed to deploy my app on such handsets?
OTA is required to work on every MIDP mobile device, just navigate with the device browser to the jad URL and click it.