After adding a certain website to homescreen through Chrome for Android, I'm looking for a way to autorun that homescreen app as the device boots up. I found a few apps in the Google Play store that offer that behaviour but they don't list Chrome homescreen apps as possible to autorun on boot.
Any solution, anyone?
Unfortunately, there is no solution right now. Chrome homescreen apps work slightly differently from regular apps. Please read here for the full details: https://developer.chrome.com/multidevice/android/installtohomescreen
Specifically, Google developers have mentioned that Android can not detect Chrome homescreen apps as installed.
Do not prompt the user to add your app to the homescreen. There is no
way to detect if the app is running installed or not.
So by extension, you are not able to run them at startup.
Running homescreen apps on device boot up might be tricky since Android cannot detect them as installed, but here is a workaround you might be interested in:
Install AutoStart - No root on your Android device
In the app, Set "Auto startup" to ON
Add Chrome to the Applications list
In Chrome, add the page you wish to launch as the browser start page
Optional - Install a secondary browser and repeat the steps above in order to avoid interfering with the start screen of your regular browser
Optional - Install an app like Fulscrn Free or similar and add your browser to the list of apps that run in full screen mode.
This way, every time you boot up the device, a browser will launch with the page you designate, almost as if it is launching the homescreen app.
Here is what I did:
Installed Tasker and AutoInput . They are paid though.
In Tasker, add a profile for "On device boot" and an action from Plugins->AutoInput.
Follow the instructions in AutoInput to create an action that simulates a press on the web app's icon on the homescreen.
I placed my icon on the default home screen, otherwise you might need to add a swipe action first to get to the proper screen.
Related
We have a project we need to complete at work, however the coding is done and the app works.
What I need to know, how do I take an Android tablet and change the OS that when the device is turned on the device must open up with a logo when started up, to say (ABC with the logo) and then the application we have designed should automatically open up and start running the operation.
In the same sentence, all apps should be blocked out and only the one app should be opened and should work, with internet connectivity.
There are a few different options,
1) Google Dedicated Device
2) Fully Managed Device
3) mason
4) SureLock for Android
I have explored recently that Samsung devices if you integrate deep links in your app (i.e. coming from the web to in-app) the chooser dialogue open only one time after its install and after that whenever the web detects that URL deep link initialize whichever app user has chosen last time to browse that webpage. I thought before that the OS saves the user preference on that specific deep link url maybe so by deleting / re-installing app will re-initialize the 'open with' dialogue. but on some devices even after uninstalling and re-installing the app doesn't even work.
problem is sometimes it opens up the webpage without even asking for open with dialogue. I'm mostly sanity testing these deep links on Samsung devices but I think this problem could be on other devices as well. anyone else encountered this problem? is there any solution for testing purpose? Can anyone suggest something?
Ok so anyone having the same problem with Samsung specific devices is that Samsung devices select default apps automatically. you can change that in settings page then search for default apps and there is section Default app selction
it would be "set default apps automatically" change it to "ask before setting default apps. that would solve this issue
I know that android OS asks the user to define open the url just one time with the app or use it as a default application.
You can clear default application from setting and see the choose dialog again.
Remember if you use BROWSABLE in your manifest, it causes your app be recognized as web application that can open urls and show your app in the web application dialogs.
Android emulator is not asking for any permission while running an application which uses protective functions like dialing a number etc. Is the user consent asked only while running on a mobile and not on emulator?
permission is asked on install time, once the app is installed, it will use all the functionality of phone that was asked on install time.
So on Emulator, you just hit the run button and it installs automatically, that's why you are thinking it is not asking permission.
if you go into Settings->Applications->YourApp
you will see the details of the permission your app will use.
Update for newer emulator versions where the Settings app can't be found on the launch screen anymore: Open the notifications by swiping from the top of the screen to the bottom, do it again to enlarge the quickstarter for bluetooth, flashlight etc. On the bottom-right you will find a gearwheel to open the Android settings.
Just that, I like to know is always all the preinstalled apps are with the uninstall button disable in Android.
If I am reading your question correctly, some of the pre-installed apps can't be uninstalled without rooting your phone using cyanogenmod or rooting your phone.
Some pre-installed applications can be uninstalled. For example in Android 4 (ICS) you can go to Settings -> Apps and select the "All" tab. There you can uninstall some of the preinstalled software.
Root the phone, put the APK into the /system/app folder and then unroot the phone. This is possible on a Droid 4 at least in theory. Not sure about other hardware models. If you can root and unroot the phones it should work.
This depends on the Device manufacturer. They have the possibility to install the app in any way they like before they freeze the image and flash it to the hardware in the factory.
For example some of the Branded apps might be installed under system privileges, but some of the more "friendly recommendation" apps might be free to uninstall.
From what i understand in ics apps in usolder can be uninsfreeled, apps in system folder instead of uninstall the button reads disable. Except for only s slight few only, these apps are reQuired by the os for the user to be able to"enable" a disable App, so i think i the app needs to be signed by the room cooker our needs top have a intent in the manifest like a launcher or home app (since if you disable your home launcher you bricked your phone, so you can't disable it, but if you give your app a intent label of copied from the Android source launcher then the phone will think it's a launcher, and not let you disable it, you will prob have to set the home launcher back to be default or Android will ask you witch launcher too use Every time user hits the home button, i was looking for the same answer found this page
Android 4.0 Api to Disable Apk Witch gave me the idea, currently thus reply is closest I've come to impinging the idea, i well be trying it soon, if you beat me to it, let me know tour results, and i well do the same.
And to install a app in /system/app a uninstall.zip won't do it, you need too root the phone, install the app, xfer it to system (i use system/app mover available in the play store free, the too secure ot Unindtsll app mover, and unroot, any way good luck.
P.s. I'm Not a Dev, i just understand the format format of the app language, and can c effectivly search for info, so please no code questions. i can't answer them, but google can.
If you were to install a Home Screen application that does not give you access to the System Settings screen (to go to Manage Applications), and also does not let you launch Apps (such as the Market App or 3rd party install/unistallers), is there ANY way to uninstall such an application?
I know that Android requires your permission before letting a new App take over the home screen privilege. But say you're trying a newly published Launcher app that is buggy (or malicious). You are of course still going to tell Android it's ok to give this App the Home screen privilege. Now once it is installed, your phone is now effectively useless?
Is there a way for a typical end user (who doesn't have Eclipse/ADB) to get out of this situation? Other than doing a complete factory reset?
I realize there are ways to uninstall an App via ADB ("adb uninstall package.name")
But it seems like a typical end user is potentially screwed if they ever install such a malicious/buggy app. This seems like a gaping security hole in Android, no?
You are right, there is no nice way of uninstalling such an application from the Android device itself. The only solutions are the ones you are mentioning, factory reset (which is difficult for most users, if the settings menu is not accessible) or using adb.
I wouldn't call it a security issue, but it could certainly be a problem for users that are not careful about what they are installing.
One of the big selling points about Android, that really puts the system way ahead of the competition, is the possibility to replace any app you don't like with something you download and install yourself. ("All applications are created equal.")
The price to pay for this freedom is that there are rogue applications that will try to take over.
Someone on StackExchange posted a very helpful solution to this problem. It seems that in addition to a factory reset, most phones also support a Safe Mode that disables other Home/Launcher apps that have been installed (at least that's what it did on my Droid X). This allows you to then uninstall the offending application. Then simply reboot again back into normal mode to get your old phone back.
There's actually an easier solution these days, surely? Use the market.android.com website to install a new homescreen app remotely onto your device. Once you've done this, hitting the home button will once more bring up the list of homescreen apps to choose from, and you can select a non-malicious, non-buggy one, and then use that to uninstall the evil one.