I did. The last comment is mine. But the most recent update is from February and I thought it would be interesting to know if there is any progress.
On Thu, Apr 16, 2009 at 8:47 PM, dar <dher...@gmail.com> wrote: > > You probably want to star issue 1073 > http://code.google.com/p/android/issues/detail?id=1073 > then you will get updates if it is worked on. > > > On Apr 16, 5:09 am, Mariano Kamp <mariano.k...@gmail.com> wrote: > > Well, did Cupcake bring some functionality that lets non-Google apps > access > > the user's Google credentials or has there been any progress in that > > direction? > > Reading your question I assume the answer is no. But what would be good > way > > to get to know if there are any plans to provide the functionality > mentioned > > above? > > > > On Fri, Mar 20, 2009 at 10:50 PM, Dianne Hackborn <hack...@android.com > >wrote: > > > > > Sorry maybe someone else can help you but I can't; I work on the > Android > > > platform, I am not that familiar with what is going on with the Google > apps. > > > > > On Fri, Mar 20, 2009 at 1:01 PM, Mariano Kamp <mariano.k...@gmail.com > >wrote: > > > > >> On a related note, is there any API today or planned for tomorrow for > > >> accessing the user's Google credentials in a safe way to pass them > onto a > > >> Google service? > > >> The actual context is that I have users complaining that they don't > want > > >> to give my app their google userid/pw to access Google Reader via my > app. I > > >> hear "Gmail doesn't ask me for that" ... Of course, I am aware, that > my app > > >> will not be on equal footing with Gmail, but I am still wondering if > there > > >> is any way around getting to know the user's credentials today? Or in > > >> Cupcake? > > > > >> 2009/3/20 Dianne Hackborn <hack...@android.com> > > > > >>> This will be fixed in cupcake, where we have a secure settings area > that > > >>> nobody outside of the system can touch. > > > > >>> Also keep in mind that GoogleLoginServiceBlockingHelper is not public > > >>> API. In fact it is not an Android API at all, it is part of the > Google > > >>> application suite which will not be on all Android phones. > > > > >>> On Fri, Mar 20, 2009 at 10:47 AM, strazzere <str...@gmail.com> > wrote: > > > > >>>> The android_id *should* not change, but can currently be modified. > > > > >>>> It's stored in the database located at; > > >>>> /data/data/com.android.providers.settings/databases/settings.db > > > > >>>> Run the query; select * from system; > > >>>> You'll see plenty of information which can then be changed; > > >>>> update system set value='dead00beef' where name='android_id'; > > > > >>>> However, this only changes the android_id when you do a call to > > >>>> Settings.System.ANDROID_ID - not how google does it through the > > >>>> GoogleLoginServiceBlockingHelper. > > > > >>>> -Tim > > > > >>>> On Feb 28, 8:30 am, dar <dher...@gmail.com> wrote: > > >>>> > I have a related question - is android_id implemented on the > device > > >>>> > and thus will not change no matter which gmail account is used on > that > > >>>> > device? > > > > >>>> > I am hoping that if a user downloads my app and runs it on one > device > > >>>> > that they will get one android_id, and if they also use the same > gmail > > >>>> > account on a different device that this will result in a different > > >>>> > android_id. Is this true? > > > > >>>> > On Feb 26, 4:47 pm, Dan Bornstein <danf...@android.com> wrote: > > > > >>>> > > On Thu, Feb 26, 2009 at 12:15 PM, strazzere <str...@gmail.com> > > >>>> wrote: > > >>>> > > > Here is a small snippet; [...] > > > > >>>> > > I'm sorry to harp on this, but please provide a complete, > > >>>> *compilable* > > >>>> > > and *runnable* example, along with what you actually observed > when > > >>>> > > running it (e.g., log output) > > > > >>>> > > I don't doubt that you are seeing a problem, but I've been > burned > > >>>> way > > >>>> > > too many times by program fragments not actually triggering the > > >>>> > > alleged problem to be willing to spend any time (nor expect > anyone > > >>>> > > else to spend the time) to flesh out an incomplete fragment. > What > > >>>> > > you've provided thus far, I am afraid, isn't sufficient to > > >>>> demonstrate > > >>>> > > the problem. > > > > >>>> > > Thanks in advance for your continued efforts, > > > > >>>> > > -dan > > > > >>> -- > > >>> Dianne Hackborn > > >>> Android framework engineer > > >>> hack...@android.com > > > > >>> Note: please don't send private questions to me, as I don't have time > to > > >>> provide private support. All such questions should be posted on > public > > >>> forums, where I and others can see and answer them. > > > > > -- > > > Dianne Hackborn > > > Android framework engineer > > > hack...@android.com > > > > > Note: please don't send private questions to me, as I don't have time > to > > > provide private support. All such questions should be posted on public > > > forums, where I and others can see and answer them. > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
