starred/sms-backup-plus-jberkel

Fork 0

mirror of https://github.com/jberkel/sms-backup-plus.git synced 2026-04-26 01:15:58 +03:00

[GH-ISSUE #127] add hint about browser problems in oauth dialog #108

New issue

Closed

opened 2026-02-26 00:36:16 +03:00 by kerem · 6 comments

kerem commented

2026-02-26 00:36:16 +03:00

Owner

Originally created by @jberkel on GitHub (Jan 29, 2011).
Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/127

possible to check for standard browser??

Originally created by @jberkel on GitHub (Jan 29, 2011). Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/127 possible to check for standard browser??

kerem closed this issue

2026-02-26 00:36:16 +03:00

kerem commented

2026-02-26 00:36:17 +03:00

Author

Owner

@dr-norton commented on GitHub (Sep 18, 2011):

i don't know whether it's related, sorry if it's not. i don't have stock/standart browser, and don't want to use it. i use opera mini but apparently it's impossible to grant/deny access with it. is there any way to cope with it?

@dr-norton commented on GitHub (Sep 18, 2011): i don't know whether it's related, sorry if it's not. i don't have stock/standart browser, and don't want to use it. i use opera mini but apparently it's impossible to grant/deny access with it. is there any way to cope with it?

kerem commented

2026-02-26 00:36:17 +03:00

Author

Owner

@jddcef commented on GitHub (Dec 18, 2011):

Did some research, yes it seems possible to force opening the default browser:

Using
intent.setComponent(new ComponentName("com.android.browser", "com.android.browser.BrowserActivity"));
http://stackoverflow.com/a/3494991/40961

Explicit Intents have specified a component (via setComponent(ComponentName) or setClass(Context, Class)), which provides the exact class to be run. Often these will not include any other information, simply being a way for an application to launch various internal activities it has as the user interacts with the application.

Also, related: you can initiate the Chooser dialog for the user to choose an associated handler for the intent....
startActivity(createChooser(new Intent(Intent.ACTION_VIEW, Uri.parse(...)), 'Pick a Browser'));
http://stackoverflow.com/a/6307390/40961

@jddcef commented on GitHub (Dec 18, 2011): Did some research, yes it seems possible to force opening the default browser: Using `intent.setComponent(new ComponentName("com.android.browser", "com.android.browser.BrowserActivity"));` http://stackoverflow.com/a/3494991/40961 > Explicit Intents have specified a component (via setComponent(ComponentName) or setClass(Context, Class)), which provides the exact class to be run. Often these will not include any other information, simply being a way for an application to launch various internal activities it has as the user interacts with the application. Also, related: you can initiate the Chooser dialog for the user to choose an associated handler for the intent.... `startActivity(createChooser(new Intent(Intent.ACTION_VIEW, Uri.parse(...)), 'Pick a Browser'));` http://stackoverflow.com/a/6307390/40961

kerem commented

2026-02-26 00:36:17 +03:00

Author

Owner

@jddcef commented on GitHub (Dec 18, 2011):

I tried it out on the 1.5 emulator and intent.setComponent(new ComponentName("com.android.browser", "com.android.browser.BrowserActivity")); seems to work.

@jddcef commented on GitHub (Dec 18, 2011): I tried it out on the 1.5 emulator and `intent.setComponent(new ComponentName("com.android.browser", "com.android.browser.BrowserActivity"));` seems to work.

kerem commented

2026-02-26 00:36:17 +03:00

Author

Owner

@jberkel commented on GitHub (Jan 3, 2012):

@jddcef: i think the problems is with devices which don't ship with the default browser - so this would fail there too.
however it could first try explicit intent, then default.

actually the best way to solve this problem is to use a webview, and not depend on any installed browser.

@jberkel commented on GitHub (Jan 3, 2012): @jddcef: i think the problems is with devices which don't ship with the default browser - so this would fail there too. however it could first try explicit intent, then default. actually the best way to solve this problem is to use a webview, and not depend on any installed browser.

kerem commented

2026-02-26 00:36:17 +03:00

Author

Owner

@jddcef commented on GitHub (Jan 4, 2012):

Good idea, any idea of the percentages that don't ship with the default browser? It must surely be less than 1.5 devices?

@jddcef commented on GitHub (Jan 4, 2012): Good idea, any idea of the percentages that don't ship with the default browser? It must surely be less than 1.5 devices?

kerem commented

2026-02-26 00:36:17 +03:00

Author

Owner

@jberkel commented on GitHub (Jan 4, 2012):

no idea - really depends on manufacturer.

@jberkel commented on GitHub (Jan 4, 2012): no idea - really depends on manufacturer.