[PATCH] Support for launching Chrome browser(if present) from HS20 client
som6000 at gmail.com
Tue Nov 3 02:54:03 PST 2015
The code already uses /system/bin/am start -a
android.intent.action.VIEW [...] .. as suggested by you. Not
specifying the -n argument will give the option to the user to select
the browser. But it pops out a dialog for the user to select the
browser, which is an extra step and might irritate the user also.
On Tue, Nov 3, 2015 at 4:20 PM, Somdas Bandyopadhyay <som6000 at gmail.com> wrote:
> Yes, that is also an option (to do that we have to remove the -n
> argument in the am command). But that will pop out a dialog for the
> user to select the preferred browser. From an UX perspective that
> might not be good, as all of a sudden the user will get an pop up to
> select a browser. Currently the code always launches the Android
> Native browser. I added the support to launch chrome browser if it is
> present. Else it continues with the normal flow of launching native
> browser. I feel that's a better option.
> On Tue, Nov 3, 2015 at 4:04 PM, Johannes Berg <johannes at sipsolutions.net> wrote:
>> On Tue, 2015-11-03 at 15:49 +0530, Somdas Bandyopadhyay wrote:
>>> PFA the patch file.
>>> If Chrome browser is present in the device then launch Chrome
>>> Else launch the normal native browser (original flow). PFA the patch
>> That seems really odd - wouldn't you use the intents framework to
>> launch the user's default browser?
> Thanks and regards,
Thanks and regards,
More information about the Hostap