I am trying to develop a Mobile Device Management Application. I have so far implemented native or basic restrictions (policies) based on http://developer.android.com/guide/topics/admin/device-admin.html
Now I want more access to the device to put more restrictions, I searched and found a page which is almost exactly same for what I want to implement. Below is the page:
http://www.manageengine.com/products/desktop-central/help/mobile_device_management/mdm_android_restrictions.html
I understand that almost all of these require the device to be SAFE. Once I have the SAFE device then where can I find any documentation or source code or samples where I can see how these restrictions are getting implemented in code. I am unable to find any such thing so far. There must be some API or tutorials etc to guide on implementing these.
Please guide me on how to implement these on SAFE device.
You need to register to Samsung Safe program. As soon as you will be member you will have access to
Documentation
Examples
Special API token which will allow you to call these API's
Related
I am trying to implement Microsoft Azure Cognitive Service Face Api for face recognition. Followed by https://go.microsoft.com/fwlink/?linkid=2184104 i created .NET Core console application and everything works fine. Now i would like to use this code in android app, but i am pretty stuck. Should i create rest api from existing C# code? Or there is android library that allows me to use face api directly like in console app?
Since Cognitive Services are already APIs, you could talk to the API directly and process the response right inside your Android code.
Please keep in mind that this does leave a potential security issue if the application is meant to go into the store / public. Users could look at the traffic or decompile your app, find your access keys and use your Cognitive Service for their own applications. In that case it could be interesting to wrap it in your own API and have some security checks in place there like rate limiting or call quota. Of course you need to make sure to use your access key inside of your own API to hide it from being seen externally.
Still, this leaves room for abuse. You now implemented a public API that, again, anybody could talk to. There are quite a few interesting discussions found on this, like this question right here on Stack Overflow: Restrict API requests to only my own mobile app.
Can I write a custom Phone app (dialer/in-call screen, etc.) with all the functionality of a native Android phone app? I've read that certain functions, like conference calling, may be off-limits to third party developers, but I haven't yet found anything official regarding what may or may not be allowed.
Here is the telephony API summary.
Also here you can find a mini tutorial on how you can do it.
I am trying to achieve a use case where on installing an app, all print services barring one would get disabled on the Android device.
To achieve this, I looked into Android's Device Administration API capabilities but that doesn't fulfill the use case. I also looked into Google's Android for Work framework and arrived at the following observations / possible solutions -
By setting up managed profiles (work profile): This was introduced from Android 5.0 but can only manage the listed/enterprise controlled and has no control over other apps as mentioned in the below links -
https://developers.google.com/android/work/build-dpc
https://developer.android.com/work/managed-profiles.html
By writing a Device Policy Controller (DPC) app: To achieve the specific use-case the DPC would have to run as the device owner in which case the provisioning needs to be done via NFC and is not straightforward. Also, this scenario is generally meant for corporate owned, single use (COSU) devices.
So my questions/doubts here are -
Is there any straightforward way in which this use case can be achieved?
Is this even achievable as it violates the Android Security model?
You should write your custom DPC. Right now you can do provisioning using several methods. If you have devices which use Android 7 and above you can use QR code provisioning which is quite convenient. For this purpose you can upload your dpc apk to a remote server and write information about the server, application DeviceAdminReceiver and apk checksum to QR code (you can take this QR code as example).
You can check to google awesome project TestDPC which will give your deep understanding of what is DPC and how can you use it.
You can read more about provisioning methods in android documentation. Also if you can contact the manufacturer of devices you can ask him to preinstall your custom dpc.
It is achievable and doesn't violate Android Security model because during provisioning your dpc app it get Device Owner (root). So you can do anything without any restrictions. Here you can check device owner API and possibilities. Also take a look at TestDPC source code and you will understand that nothing is impossible with Device owner mode :)
I'm trying to create a new user in IAM using Amazon web-service SDK for Android.
But after searching a lot I couldn't find any sample codes or documentation clearly stating the above functionality. I saw this and also this.
The first link only works for Java SDK only.
So my question is does AWS SDK for Android support a way to create a new IAM user programatically?
I also faced the same problem.I mailed AWS technical support team for solution.They clearly stated that android sdk for aws does not supports the new user creation for IAM.
Actually I am not sure about IAM implementation for Android, as a Web Service you can use them in a deeper level anyway, but I don't think this is your needs.
I suggest you read IAM Limits, which shows some limitation on users number, which may be a problem for future growth.
In your scenario I would suggest this article which will require another layer to control user authentications with token control, it will solve user limitations, will give you a lot more security and control over your system.
After all, you can still using IAM for user's power level control, as another security layer.
I'm looking to get access to get low level network information on an android device that isn't available through the api. Is there a way to talk to the RIL to get more information?
Yes. I'm actually messing around that same thing. My hardware uses GSM radio and everything turns around the android internal API. (do a stackoverflow search with "[android] internal API" and you will get tons of info on how to access it). In my case, I'm interested in the data link over the GSM. So, it's in android source code in frameworks/base/telephony/java/com/android/internal/telephony/DataConnectionTracker.java. If you are interested in other features like SMS, SIM cards, voice call or anything that is not available on the standard "public" API, look in the folders frameworks/base/telephony/java/com/android/internal/telephony and the names are pretty relevant to what it does. As for a clear documentation, I did not find it. I think it's not publish since it is not recommended to use the internal APIs because it could change without notice and there is no guaranty an internal API will not change in the next Android version.