XDA Recap: This Week In Android (May 17 – 23)

Another week, another recap. The Sunday tradition marches on this week with a fresh … more

Huawei To Sell Honor Smartphones Via Indian Retail Outlets

World’s fourth largest smartphone maker Huawei plans to now sell its … more

Sunday Debate: Are Smaller Bezels Better or Worth It?

Bezels have been getting smaller and smaller as the years go by, and while devices … more

LG G4 First Impressions and Unboxing – XDA TV

The latest in LG’s signature line of “G phones” has been released. … more
Post Reply Subscribe to Thread Email Thread

Big problem with google account authentication

22nd June 2011, 08:30 PM |#31  
Flag Reigate
Thanks Meter: 1
Is it going to turn out to be some really daft and simple issue? I mean, if it works when you change the Language to US (it did for me on Google Goggles), perhaps it is something like the date format in a text string being sent during authentication? i.e. changing language updates the regional settings.
22nd June 2011, 09:51 PM |#32  
(.)'s Avatar
Senior Member
Thanks Meter: 100
try to use wlan instead of 3g, this maybe helps..

I know that it is not a connection problem.. google just makes you think it is, when in fact its about to register your data.
28th June 2011, 12:25 PM |#33  
Junior Member
Thanks Meter: 1
I'm the developer of Andlytics and found a solution for my app. (Andlytics user Paulo told me about this)

I think the problem is related to the translation strings which Samsung changed from the default ones on the SGS2.

The original String which pops up on authentication requests is:

<string name="permission_request_notification_with_subtitle">Permission Requested\nfor account %s</string>
Samsung changed it to something without the '\n', that's why a IndexOutOfBounds error occurs (

final String titleAndSubtitle = mContext.getString(R.string.permission_request_notification_with_subtitle,;
final int index = titleAndSubtitle.indexOf('\n');
final String title = titleAndSubtitle.substring(0, index); <--IndexOutOfBounds
final String subtitle = titleAndSubtitle.substring(index + 1);
The solution for me was to use a different method on authentication requests:

public AccountManagerFuture<Bundle> getAuthToken (Account account, String authTokenType, Bundle options, Activity activity, AccountManagerCallback<Bundle> callback, Handler handler)
instead of what I was using before:

public AccountManagerFuture<Bundle> getAuthToken (Account account, String authTokenType, boolean notifyAuthFailure, AccountManagerCallback<Bundle> callback, Handler handler)
Last edited by andlytics; 28th June 2011 at 12:44 PM.
The Following User Says Thank You to andlytics For This Useful Post: [ View ]
21st September 2011, 06:18 PM |#34  
drmacinyasha's Avatar
Senior Member
Flag Sacramento
Thanks Meter: 279
Just for the hell of it: This bug is present on the Epic 4G Touch. GG Samsung.
8th November 2011, 12:31 AM |#35  
Junior Member
Thanks Meter: 0
Originally Posted by drmacinyasha

Just for the hell of it: This bug is present on the Epic 4G Touch. GG Samsung.

After reading about various I9100 users solving this by switching to English (US) I figured I'd try something similar. Since the only other language available on a Sprint Epic Touch 4G is Spanish I switched to Spanish, went back to Goggles and tried to save --> SUCCESS!

Now switch back to English and proceed to take stupid pictures to see just how much Google can recognize.
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes