I'm posting my question here because I can't find any suitable answer to it.
I have an Android device that acts as a 'Google TV Board/Box' (linked to TV, network connection, Android OS, ...)
And I have multiple Android devices (smartphones and tablets).
I would like to be able to use the Chromecast application to cast the screen of a tablet (for example) to the 'Google TV board/box'.
I don't want to use an external Chromecast device as I have all the power needed directly from the board/box.
I heard about the Cheapcast application which emulate a chromecast device but I tested it and since Google change its politics regarding security certificates, I'm not able to make it works.
So my question is :
Is there any way to emulate a chromecast on an Android device
OR
Is there any way to make this possible wihtout emulating on an Android OS ? Maybe some king of API ?
Thank you for your time!
As you noticed, the official Cast SDKs on the sender sides validate that the Cast device they are talking to is a genuine device, hence you cannot emulate a Cast device if your sender is an using official Cast SDK.
Related
I like to have single android app in our managed devices, we want only that app to be used on the device with necessary restriction, such that,
Single use - Device will have only one app, user can't use other apps, like browsing, youtube or anything,
the initial setting like notification sound, GPS always on, notification and ring sound maximum level can't be modified.
user can not power off the device.
this setting can only be changed by our servers.
i think i have 2 option,
1) Using samsung knox sdk on samsung devices,
Here's MDM proving feature of Samsung Knox Standard!
2) General Android way, Set up Single-Purpose Devices, COSU solution
Android Developer's site.
Wanted to know your's view on this, may be if you guys have done any of the two or any other ways, i could use some of the guidelines or a path.
Thanks for reading, and please comment if i was unable to articulate the subject or it needs editing.
You can use Google's new Android Management API, it seems to suit your needs.
It is a new cloud API that allows to manage Android devices from a server, without having to build an on-device agent (a device policy controller).
I have broad experience of using Samsung Kiosk Mode from Knox Standard SDK which is free and Pro-Kiosk mode from Knox Customization SDK (which has more functions but is not free).
So I can tell you for sure that all 4 points that you have mentioned can be achieved by using Knox Standard SDK.
Singe Purpose: https://seap.samsung.com/api-references/android-standard/reference/android/app/enterprise/kioskmode/KioskMode.html
LocationPolicy (you can turn on GPS and restrict changing): https://seap.samsung.com/api-references/android-standard/reference/android/app/enterprise/LocationPolicy.html
Yes. It is possible but I forgot the exact implementation.
Yes, as well.
Only downside of using this SDK is:
You are tied to Samsung (which I personally okay with, since Samsung has such market penetration and you could get service almost anywhere in the world and in enterprise world it is critical)
About Android native functionality: never tried it
Update March 7, 2019: Now I am playing around Device Owner, we use it for Kiosk mode, works well and works on android Device with Nougat and earlier.
I understand that to access SIM/eSE from an Android app we need to install Open Mobile API addon on Android Studio. However, is it true that it will not work on all NFC phones? For example, do some OEM limited access to SIM/eSE? Or are there phones where only custom firmware will work with Open Mobile API?
Also, is there a list of phones that support Open Mobile API by default?
That's correct. The phone needs to implement the Open Mobile API (by means of the smartcard system service) in order for your app to be able to use it. Not all devices implement this. It's mainly devices from Samsung, Sony, and HTC which support the Open Mobile API.
In addition to that restriction, you need the SE (UICC/eSE) set up to allow your application (this is handled by GlobalPlatform SE Access Control) to interact with the SE.
Finally, I'm not aware of any complete list (and ther probably is none). However, have a look at the question List of OMAPI supported devices to get some ideas on how to test devices and how to let Play Store generate a list for you.
You may also want to read our report Open Mobile API: Accessing the UICC on Android Devices to get some idea about how the Open Mobile API works.
I am planning a new application that I would like to put on the smartwatch. I would like to have it usable also when there is no phone nearby. The app needs no Internet connection to work, could synchronize data to the phone later and I do not need anything from the phone while the app is running. However I could use the phone no problem to install the app.
I have googled, there are some foggy talks on a web that this is not possible, Android watch must always be connected to the phone for apps to run. How much is it true?
With Android Wear 2.0 it is possible to now develop standalone applications and thus eliminates the need for a mobile 'companion' completely.
Please follow this link for more information: https://developer.android.com/wear/preview/index.html
As I am aware, the current Android Wear version always requires a companion app for installation purposes etc. But with 2.0 this is no longer necessary. It would probably make sense for you to start developing with 2.0 now. That being said, it is still in a development preview and can officially run on only two smart watches (Huawei Watch and LG Watch Urbane 2nd Edition)
Wearable apps are run directly on wearables and don't require presence of a phone except for installation or phone-provided features (voice recognition, SMS, internet connection etc.)
Note that some features are wearable-provided or phone-provided depending on the hardware configuration of the watch/wearable (eg. GPS).
Yes, it is most definitely possible. As long as the wearable app doesn't require any functionality from the phone then it can operate as a standalone device. It will require a companion app on the phone to install the app on the wear device.
There are several wear apps that work without the need to be tethered to the phone, including Google Play music. There is the possibility of designing wear apps for hardware on only a few wear devices - I know that Ghostracer has standalone functionality using GPS, but it requires the wear device to have a GPS chip (it is designed for the Sony SmartWatch 3).
I want to develop an app on android that uses screen mirroring with Samsung TV. I'm looking to use my android app screen as a remote(say a game controller) & TV screen to run the actual game. My initial approach was learning google cast but it needs a chromecast dongle which I don't want to use for this project. I want to use Samsung Smart TV's Screen Mirroring feature to do so. After some googling, I figured out that samsung uses Allshare Framework API for screen mirroring/cast but I'm not completely sure on this. I'm currently struggling to find a proper documentation for screen mirroring. If someone can point to the correct documentation link then that'd be awesome. Also, please correct me if I'm wrong with the assumption that this can be achieved using Allshare API only.
It seems Samsung have came out with this new SDK - Samsung Multiscreen SDK( or maybe I've found it now :)). This link should cover most of the questions I've asked above. Also, if you are Unity user, Samsung has their own version of Unity which comes intalled with Samsung Multiscreen Game SDK. But you need to send a partnership request to samsung in order to use this version of Unity. Apart from these two, you can also use Connect SDK which is independent of any technology, i.e. it covers almost every other technology used for Cast. For exmple, if you have a Samsung Smart TV at your home & a Roku connection. With Samsung SDK you can only discover Smart TV but not Roku stick. Whereas, with Connect SDK you can discover Samsung Tv as well as Roku & any other Cast device which is available in your network.
I'm looking for a way to have my android wear device locally communicate with my android tv. I was hoping that I could use the wearable Message API, which doesn't seem to work on android tv (probably because the android tv doesn't pair with android wear).
Ideally I was hoping if this would be possible without having to relay messages through the mobile phone app.
Any suggestions? Thanks
You can't connect to any other device directly, for example through Bluetooth or Wifi.
All connections need to go through Google Play Services using Data Layer API or Channel API.
For that, all devices need to be paired using a Android Wear app. Theoretically you could install Android Wear app on the TV but I don't think it will be usable with the controller.