Is there any way to either turn off the recent apps button in android 3.0 (I have a xoom) or clear the list? I have not found one so far.
It breaks my app protector program and allows people to circumvent the app password if its in the list. (like my gmail)
If not, does someone have a confirmed app protector program that accounts for this and works in android 3.0?
Why not add android:noHistory="true" to your manifest for the activity?
Related
Sorry for the ambiguous title but I couldn't think of anything better than this.
I am trying to make a quiz app, in which:
when student starts test, he/she might not be able to do anything( back, go to home, recent, see notifications, open another app) until he/she finishes the test.
I had seen such a kiosk-like thing on the web.
There was a kiosk mode mentioned on the android developers documentation but I want to do it without rooting. It must start only when certain activity is started and must stop when some other activity closes.
Pretty sure that's not possible for a normal app running on a non-rooted device.
I'd be surprised (and a bit concerned) if it were, since it would allow malicious app developers to lock users out of their devices.
Google provides Android platform to developers to develop app which tune with google intention. Thats why google have Playstore to make Apps trustworthy between developer and users.
Rather than violating Android rules, Why not you try something which will respect Android flow.
Like:
1.Do your implementation based on Activity/Fragment Life-cycle method(OnCreate,OnStart,OnPause,etc).
2.Write algorithm(Business logic) such that users can not go out of your current screen otherwise they will loos session, etc.
Lets #BuildForBillions.
The app I'm working on is an aggregator of sorts. The company coordinates with other app developers, gets their permission to market and push freemium versions of their apps within our app.
Basically, if you sign up with our app and pay $x, you get monthly access to a bunch of other apps that would've been more expensive if subscribed to directly.
This works but our app ends up needing to side-load the apps and it shows up in the app list and on the Home screen.
But, since we receive an authentic version of the apps from the developers themselves, is it possible for us to install the app on the user's phone without it showing up on the user's Home screen?
The idea is to ensure it doesn't look like we just helped them install an app on their phone.
We want those apps to be exclusively accessible via our app. It shouldn't be accessible via the phone's home screen or app list screen.
I imagine it could be possible since I've seen launchers do it. Some launchers come with smaller apps installed within them that's accessible only via their launcher platform. I'm not too sure how that's achieved though.
Thanks
You should ask your other apps developer to ship their app without the launcher category in the manifest file.
<category android:name="android.intent.category.LAUNCHER" />
Remove the above line from the launcher activity of other applications to prevent it from showing in launcher screen.
It shouldn't be accessible via the phone's home screen or app list screen.
While you can ask the developers to take steps to prevent their app from showing up in the launcher, you cannot prevent the installed app from showing up in the list of installed apps.
The idea is to ensure it doesn't look like we just helped them install an app on their phone.
Then do not install an app on their phone.
Some launchers come with smaller apps installed within them that's accessible only via their launcher platform.
If they do not show up as apps in the list of installed apps, then those are not apps, from an Android standpoint.
Is it possible to add an android app shortcut in home screen launcher without asking permission popup.
I tried but couldn't find any information/documentation.
Even tried with reflection but it is not working :(
Since Android asking for permissions to do certain stuff, such as changing home screen and accessing contacts is a safety feature of Android, I am almost certain that it is impossible for an app to avoid this.
The only exception I can think of is Google Play Store, which is built into Android so it makes sense that it is an exception.
I am trying to create a kiosk type app so when you press the recent apps button I dont want the user to be able to go to a different app. I have been googling around but cannot find anything on this matter. There is this solution in this
thread Recent apps button in android
However this does not seem to work for me on Android 6.0
Can someone please point me to the right direction on how to do this?
Thanks
In the link you provided yourself can find the answer:
Is that possible to override recent apps button in android? Not from
an ordinary SDK app.
You are welcome to build your own custom ROM that modifies the
overview screen, then convince people to install your custom ROM on
their devices.
So your answer is no in the app written by Google provided SDKs.
It is not possible. You can not control recent app AND home button in Android. You can't allow user to not leave the app. It is user's choice.
Edit: The only way you will be able to control those buttons is if you have system level permissions. To have system level permission for the device, you have to have system certificates and you won't have that unless you created the Android ROM on the device.
there's a app called "All in one Gestures" that can make the physical recent apps button without blocking some alternate way to trigger recent apps (like assistant menu in accessibility settings), i'm not the developer of that app but using APK editor, i see that the app are using accessibility service
Is possible to any harmful software to be installed on Android, without the user's permission and hide that software in the App List?
Spyware, virus, etc.
Thanks.
It is possible to have an app with no launcher icon, but every app will show up in the Settings's Application list.
Additionally, starting with Android 3.1, applications aren't allowed to do anything at all until they have been started by the user at least once, which requires them to be present in the launcher.