I'm developing now for Android 2.0 and the Browser Bookmarks and
history are working again
(in the Emulator and on my Droid).

I'm using the following permissions:
        <uses-permission
android:name="com.android.browser.permission.READ_HISTORY_BOOKMARKS" /
>
        <uses-permission
android:name="com.android.browser.permission.WRITE_HISTORY_BOOKMARKS" /
>
To get the Browser bookmarks I used:
       // Get all the bookmark url's using the direct call (gives URL
but no longer the title)
        mCursor = Browser.getAllBookmarks(getContentResolver());

To get the History (all visited URLs):
        // Use the standard Android call to get the visited URLs
(includes Bookmarks)
        mCursor = Browser.getAllVisitedUrls(getContentResolver());

Note: the history includes the Bookmarks.

jh

jh

On Oct 25, 9:38 am, Vamsee <vkanak...@gmail.com> wrote:
> On Oct 9, 9:37 pm, "John B. Hansen" <jnahan...@gmail.com> wrote:
>
>
>
> > I've been using the following permissions since SDK 1.1:
>
> > <uses-permission
> > android:name="com.android.browser.permission.READ_HISTORY_BOOKMARKS" /
>
> > <uses-permission
> > android:name="com.android.browser.permission.WRITE_HISTORY_BOOKMARKS" /
>
> > Now, while migrating to 1.6 I'm seeing two things that are surprising:
>
> > 1. The 1.6 release notes are saying those permissions are new (have
> > been added)
>
> >http://developer.android.com/sdk/android-1.6.html#api-changes
>
> > 2. I'm getting the following warnings in Logcat and my activities that
> > use them are crashing:
>
> My app is using the same persmissions too, and I'm having a similar
> problem - the weird thing is, the app works fine in a 1.6-based avd.
> But it won't work on the actual device (ADP1 running 1.6 images from
> HTC) - gives security exceptions saying that the app needs
> READ_HISTORY_BOOKMARKS permissions, though they were (both read/write
> permssions) already present in the manifest file. I can confirm this
> is happening for others too, as people are complaining that it's been
> force closing on them ever since the 1.6 OTA update happend. Did you
> happen to find a fix for this, by any chance?
>
> TIA,
> Vamsee.

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Reply via email to