i'm developing an app that runs in some tablets. these tablets are rooted and the user that uses that can't go out the single app that tablet run. If i want to use an external app inside my app is possible? Like an emulator inside my app.. Thanks!
Technically to run android application inside android application you need and android emulator on your Android device, which needs lots of CPU, and is neither implemented now, nor a good solution for any problem that you may be facing. Theoretically it's possible but technically - very complicated and to my mind useless.
You should try to find a more elegant solution rather than this. The simplest thing you can do is to make incapsulated switching mechanism between your restricted apps or think about solution how this apps can be integrated.
Related
For a POS system is there a way or ways to make an application harder to close?
The desire is to have employees be able to use the device and the application, but not use other applications.
The implementation does not necessarily require a password. So far the answers I have seen on similar questions suggest this is not possible. Except in Lollipop per this question : How to make an app unclosable?
Are there any options for older APIs?
Or am I just out of luck?
That is not possible as a feature of the API since the Android system is in control of what is executed or stopped. And that could mean that your app gets stopped for a number of reasons.
To achieve what you are asking for you will need to create your own distribution of the system. I have no experience of doing that but it basically means creating a rom and distribute it.
That would of course be an option if the device running the POS app is only used for that particular task.
I need a device that runs only one custom application and does not allow the Users to access any other features. Building a complete device would involve a lot of time and money for sure(only if this can be done with android). This can usually done for each android device seperately. It could be better if there could be simply a piece of code that can be simply executed on the device that installs the application and at the same time restricts the device as per requirement.
Could someone advice me a way to implement in the Android devices. Is it something possible :(
Would also like to know if the same is possible with iOS..
Thanks..
If you want to be absolutely sure that users cannot do anything but accessing one specific app, the only way to do this is to create a custom ROM that allows to install your app only.
Currently I am developing an android application. This application should load when the device boot and it should restrict all the inbuilt & other applications. I have searched in forums as it can be possible by make our ROM customized. But this process can be do manually by ourselves. I want to make this by coding. Or is there any other way to make my application default?
If you want your app to be default - yes, you haven only way to build your own custom android.
Only what you can do on your default android system is to automatically load your app after OS have loaded.
You're not stating precisely what you intend to do. The words restrict and default can mean a lot of things.
Despite what dilix writes, one way you might succeed with what you want is if you make your app a launcher. A launcher plays an interesting role in the system.
However, you cannot force anyone to really use it. But that wouldn't be possible either way, right? Unless you talk to device manufacturers.
I have been messing around with android programming for the last couple of months,
now after developing a couple of apps I would like to extend exisiting android app so that I can change their menues add more features etc.
for that I have two questions:
1. Can i upload such a "driver" to the android market as an app? even after it gets installed all it do is add more features to the android OS?
2. where can I get more info about how and what should I read\learn for my purpose?
Tnx in advance.
if you want to make certain expansions to system apps, well... it's difficult. You will have to do that by editing the system app and adding new smali code for functionality. The problem is, that it will work only on your phone, on or phones with the exact system. For example, if you want to add new functionality to Phone.apk from a samsung phone, the resulting app will work only on samsung phones that have an identical Phone.apk. Besides, the phone must be rooted and the installation can't be done from Play... because it can't replace a system app.
One other thing to consider, for replacing functionality inside apps is Xposed Framework
You can read more about that, there.
In conclusion, it's not easy or pleasant to waste your time expanding system apps. You can try to develop new mods for CM for example.
I would like to start looking at development for Android applications (nothing huge, just for learning). Before I begin, I would like to find out whether or not development on the Android phone I use daily would be corrupted or changed in some way if I used it as a development device.
I probably won't put anything on the Market, but I would just like to test out how everything "works" with Android development.
Any help that will guide me is great.
Thanks.
It shouldn't cause any problems at all. The only problem I can imagine is that you have to enable installation of applications from unknown sources (i.e. not the marketplace). You just need to be sensible not to go installing applications from dodgy places.
No, not at all! Sorry for the shortness of the answer, but that's it.
The only problem I can think of is writing to internal memory more than usual, but if you install a lot of new apps, the effect will be the same, so it's nothing special. And as alextsc said, if you write something and it doesn't work, just remove it, and that's all.
Not at all. But even better, when you set everything up (Eclipse, the Android SDK and the ADT Eclipse plugin) you'll also get an Android emulator that you can test your development projects on virtually.
Still, it's just fine (and recommended) to do testing on an actual device, but if you're just playing around, you can likely just use the emulator and only deploy to your device if the end result is something you'd like to show off to your friends!
Best of luck!
Hey in addition to the above answers,
You should actually test on your device when you are making an app that uses one of the following :
GPS, or wi-fi to get user location
when you want to use any phone sensor in your app
when you are trying to integrate camera/ camcorder in your app
also you might need to actually test phone call/sms functionality integrated in an app
otherwise the emulator just works fine