I was wondering if anyone had a relatively simple solution for us.
We created an app to be used by our clients on android devices that we give them.
We would like the client to only be able to use our app and have limited access to everything else (i.e. settings, email etc.) What is the best way to achieve this without using 3rd party apps.
Thank you in advance!
This may not help but the L preview has a task locking feature included that may be of some insight, I'm not aware of how it functions as yet
Task locking
The L Developer Preview introduces a new task locking API that lets you temporarily restrict users from leaving your app or being interrupted by notifications. This could be used, for example, if you are developing an education app to support high stakes assessment requirements on Android. Once your app activates this mode, users will not be able to see notifications, access other apps, or return to the Home screen, until your app exits the mode.
http://developer.android.com/preview/api-overview.html
Hope this helped
Suppress the Title Bar & Make Your App a Launcher
Root Your Tablet
Modify System Files and Settings to hide the soft keys
On the next link you can find the complete solution for the Nexus 7 (2012)
http://thebitplague.wordpress.com/2013/04/05/kiosk-mode-on-the-nexus-7/
simple Answer is:
Lock Install button with modify system settings.
Create your own customized-ROM and apply your requirement to that ROM.
more info, visit XDADavelopers
Related
I am stuck with one of my client requirement , it seems not be feasible to me as i am not able to find anything related to this particular requirement.I am goggling but does not came up with proper clue.I though studied the below mentioned link which states that it is not supportive . Here is the link :-
How to force a widget to appear on lock screen programmatically (Android)
i just want to confirm that is it feasible ? Or this can be achieved by making custom lock screen for application.
Here is what my client requirement is :-
I need your suggestion here , please let me know .
Thanks
i just want to confirm that is it feasible ?
As I wrote in the answer to the question that you linked to, the standard Android lockscreen framework only supports app widgets from Android 4.1 through 4.4, which is a steadily shrinking portion of the Android device ecosystem.
Or this can be achieved by making custom lock screen for application.
Android does not support the creation of custom lockscreens, other than by building your own modified version of Android, poured into your own custom ROM, installed onto whatever hardware your custom ROM supports.
There are plenty of developers who claim to create custom lockscreens. Those actually require you to disable the device lockscreen, then their apps attempt to interpose themselves between the user and ordinary apps. At the best of times, this offers weaker security.
I am relatively new to android and want to create an application that permanently overrides androids basic softkey behaviour and view (for devices with soft keys).
Some functionalities I want to implement are changing the size of the softkeys window at the bottom, change its images, and possibly change its functionality.
For example, the user can set the size to of the softkey to be "large", "medium" or "small". And I can change the functionality of the back button to open say a particular application instead of going "back".
I'm basically looking for a high level answer as to how to do this, a basic direction of what I should read/study in order to be able to accomplish this. I realise this may require root access.
Please note that I want this behaviour to change not only in my application but I want the effect to exist on all applications. If this requires the application to be running atleast at the backend, that is fine.
After doing some decent amount of search, it seems I will have to make changes in the systemUI.apk, or possibly get its source code and modify it. Is this correct?
Thanks in advance.
I don't think even root is going to be enough for the type of changes you are describing. You're going to need to edit the Android source code and build your own system image.
Well you can't override system resources because they are part of the system image.
What you are looking for is called Home Application which can be developed like any other android app no need for root , you can find an example for it in your sdk samples.
Home Sample Application.
your app would be responsible to have UI components to send the user to all of the phone functionalities which includes:
Place for wegits
Place for apps listing (menue)
Access telephony functionality (call, phone history ...)
Access settings.
I have a requirement for trying to develop an alternative to the current pin password security system on the android operating system. The main goal will be to try and replace the current password system with an alternative that uses one of the hardware features on the device. Is this possible as a third party? Or, would you need to go to the specific head set manufacturer to get the ability to circumvent or change the current security system?
I believe there is no API which is specifically designed to replace/be a pluging to a lock screen on Android.
However, people found several clever way of implementing it:
Replace home screen
Showing activity on top of lock screen
Take a look at these questions:
Where can I find examples or tutorials about creating a custom android lockscreen?
Customizing Android Lock Screen functionality?
how to make application lock for android mobile.how to lock the application. I have done locking the home screen i.e the entire mobile, but im not sure how to lock particular application.
For this situation you need to catch the listener event to lock the installed apps..
I have to say that I don't quite get what you're trying to di.
If you're trying to prevent people from using an app after it's downloaded the only way I can think of is having an HTTP(S) request done to a server with an identifier that is set the first time the app is run and check a DB to see if it can run (set a boolean flag shouldRun or something like it).
If you wat to prevent it from being copied from one phone to another, you can use the Google Play built in option to prevent it.
if this is what you're trying to achieve, you should probably obfuscate your code as well
obfuscating code on android
There is currently no support in the Android SDK to reliably do this. The application locking apps that are currently on the market aren't reliable in that they exploit a security loophole and put themselves in the foreground when you try to run a given application. This can be bypassed without much difficulty if you know how, and the security flaws they exploit will hopefully be closed. Sorry.
Does anyone know that is it possible to have a multiple user profiles in an Android device. If it is possible then will it be possible also to separate the search history or search settings for different user profiles? We are working on a custom Android device and trying to have different user profiles there. Although my job is not to find how to create multiple users but I got the task to find out how to differ the search settings for different users on the same device. I have checked almost everything in Android developer guide for searches and cant find anything like that. Any answers or clues or suggestions will be highly appreciated.
You cannot have multiple profiles on standard Android devices. You will have to create a highly customized ROM for this. I wish you fellows luck.
I guess since you are saying that you are building a custom android device you are building the
source from Android Open Source Project(AOSP). Since you have access to the entire source code, you
could set the system property 'fw.max_users=4' or any number you want greater than 1 to enable
multiple user profiles on the device. You could set this value in your device's system.prop file.
This feature probably started out in Android 4.2
But I don't there is currently any way to separate search history and search settings.
I see that this question was asked a long time ago, but it may help any new users who have the same
question.