Log in or register to post comments

"Service Unavailable" on some Android devices

May 23, 2013 - 9:58am #1

Cloud Recognition (including the sample project) fails with the "Service Unavailable" message (TargetFinder.UpdateState.UPDATE_ERROR_SERVICE_NOT_AVAILABLE) on some Android devices.  We have encountered the problem on:

  • HTC Nexus One running Android 2.3.6
  • Samsung Galaxy Proclaim S720C running Android 2.3.6

However, the scan line and interest points are visible.

Has anyone else had similar problems?  Any known solutions?

"Service Unavailable" on some Android devices

April 4, 2017 - 12:56pm #18

I am facing the same problem still. I have just bought a new phone "Vivo Y53" and am trying to replicate the demo application just as shown in the following video:

https://www.youtube.com/watch?v=ebPJjdkRW8g

It works fine in play mode on my laptop but is throwing "Service Unavailable" exception when deploying on the device.

The device has Android 6.0 installed with correct timezone and time setting.

Please help!!!

 

"Service Unavailable" on some Android devices

July 23, 2013 - 8:14am #17

Thanks again, that's very helpful.

"Service Unavailable" on some Android devices

July 23, 2013 - 7:16am #16

Here are two other accounts of time zone issues (though not necessarily the same cause as our issue):

Moreover, there are some apps dedicated to fixing time zone errors on rooted devices.  For example:

From the reviews of that app, you can see that many users did have time zone errors.  For example, one reviewer says, "Now the timezone in Australia is GMT+10 instead of GMT-00. Thanks for the fix!"

I would infer that many Android users have an incorrect GMT offset, whether or not the clock is on automatic.

"Service Unavailable" on some Android devices

July 22, 2013 - 1:07pm #15

Thanks. Have you found any other accounts of the Time Zone issue online? The only related issue that I've been able to find is..

http://code.google.com/p/android/issues/detail?id=26667

"Service Unavailable" on some Android devices

July 22, 2013 - 11:33am #14

The seasonal offset is wrong for both automatic and manual.

"Service Unavailable" on some Android devices

July 22, 2013 - 11:17am #13

Does setting the time zone configuration back to automatic resolve the problem? - or is the seasonal offset incorrect regardless of whether it is configured automatically or manually.

"Service Unavailable" on some Android devices

July 22, 2013 - 7:07am #12

Okay, the underlying issue seems to be a time zone bug in Android 2.3 (or maybe specifically 2.3.6).  The OS is incorrectly reporting Americas/Halifax as GMT -4 all year round.  The correct value is GMT -3 during "summer" time (Mar. 10 to Nov. 3), and GMT -4 otherwise.  The issue affects most but not all of our Android 2.3.6 test devices.

I haven't determined whether other time zones are buggy too.

As a workaround, we can warn Android 2.3 users about this issue and encourage them to install a third-party app such as ClockSync to correct the time zone.  This solution is a bit ugly, though.

It would be nice if Cloud Recognition were robust to errors in the user's clock.  A lot of devices, especially running Android 2.3, do not keep accurate time.  For another example, see these bug reports:

Does anyone have other suggested workarounds, or any information about plans to make Cloud Recognition robust to clock errors?  Thanks.

"Service Unavailable" on some Android devices

July 22, 2013 - 6:08am #11

magnetica, which OS versions are you using on those two phones?

"Service Unavailable" on some Android devices

June 6, 2013 - 7:48am #10

same error here with 2 device..

HTC nexus one and samsung gt 7500

"Service Unavailable" on some Android devices

May 23, 2013 - 5:31pm #9

"Automatic" is off and the date, time zone, and time are correctly set.

Our time zone is AST (GMT -4), if that makes any difference.

"Service Unavailable" on some Android devices

May 23, 2013 - 1:56pm #8

One more confirmation request - Please check your timezone setting, we've encountered similar issues when devices were set to an 'automatic' time zone detection setting that turned out not to be setting the correct timezone. So while the time appeared correct it was not producing the correct time stamp.

"Service Unavailable" on some Android devices

May 23, 2013 - 12:38pm #7

That's interesting - Please see my PM

 

"Service Unavailable" on some Android devices

May 23, 2013 - 11:22am #6

The date and time are correctly set but the error persists.

We've found another affected device: Samsung Galaxy S, running Android 2.3.6.  All affected devices so far are running 2.3.6.

"Service Unavailable" on some Android devices

May 23, 2013 - 11:17am #5

Check that the time is set correctly as well. That error occurs when the request timestamp is too far from the expected time for the request interval - e.g. indicating a significant delay.

"Service Unavailable" on some Android devices

May 23, 2013 - 11:11am #4

It turns out that the dates were set incorrectly on the affected devices.  However, after correcting the dates, the error changes to "Clock Sync Error" (UPDATE_ERROR_TIMESTAMP_OUT_OF_RANGE).  What might cause this?

"Service Unavailable" on some Android devices

May 23, 2013 - 10:54am #3

The error does occur consistently on those devices, and they do have a network connection.

We have never had Cloud Recognition working on these devices.  We have one example of each device.

"Service Unavailable" on some Android devices

May 23, 2013 - 10:08am #2

This is occurring consistently on those devices? - have they ever worked properly? - have you confirmed that they have a network connection?

Also have you observed this issue on multiple devices of the same model, or only with those two examples?

Log in or register to post comments