Open GoogleCodeExporter opened 9 years ago
Original comment by mimm...@google.com
on 15 Aug 2013 at 8:39
Would be great to get the Google Play Services on board, to be able to use
LocationClient.
It's shares last location between apps so it's usually way faster at delivering
it back to the apps.
Instead of using LocationClient you can use the LocationManager class,
available since Android API 1:
http://developer.android.com/reference/android/location/LocationManager.html
Original comment by tomasz.z...@gmail.com
on 8 Oct 2013 at 11:20
Yes, It will be great to have this too. The getting locations from
LocationClient consumes less power, which is always a good thing to have for
wearables.
Original comment by Platinum...@gmail.com
on 31 Oct 2013 at 4:39
I'm trying to use the latest version of Google Play Services in a GDK Sneak
Peek project and this is still an issue. The message provided by the debugger
is the following:
11-25 15:14:18.513: W/GooglePlayServicesUtil(31699): Google Play Store is
missing.
11-25 15:14:18.513: E/GooglePlayServicesUtil(31699): GooglePlayServices not
available due to error 9
Error 9 is "The version of the Google Play services installed on this device is
not authentic."
In my case, I'm trying to use it for authentication purposes, not location.
Original comment by azugal...@gmail.com
on 25 Nov 2013 at 8:27
I just pulled down and installed the maps sample project from the glass library
and installed it. When it runs I get the following message:
Google Play Services, which some of your applications rely on, is not supported
by your device. Please contact the manufacturer for assistance.
When I press ok I get:
E/AndroidRuntime( 3570): FATAL EXCEPTION: main
E/AndroidRuntime( 3570): java.lang.NullPointerException
E/AndroidRuntime( 3570): at
android.app.Instrumentation.execStartActivity(Instrumentation.java:1378)
E/AndroidRuntime( 3570): at
android.app.Activity.startActivityForResult(Activity.java:3195)
E/AndroidRuntime( 3570): at
android.support.v4.app.FragmentActivity.startActivityForResult(FragmentActivity.
java:839)
E/AndroidRuntime( 3570): at
android.app.Activity.startActivity(Activity.java:3302)
E/AndroidRuntime( 3570): at com.google.android.gms.dynamic.a$5.onClick(Unknown
Source)
E/AndroidRuntime( 3570): at android.view.View.performClick(View.java:3511)
E/AndroidRuntime( 3570): at android.view.View.onKeyUp(View.java:6074)
E/AndroidRuntime( 3570): at android.widget.TextView.onKeyUp(TextView.java:5567)
E/AndroidRuntime( 3570): at android.view.KeyEvent.dispatch(KeyEvent.java:2575)
E/AndroidRuntime( 3570): at android.view.View.dispatchKeyEvent(View.java:5501)
E/AndroidRuntime( 3570): at
android.view.ViewGroup.dispatchKeyEvent(ViewGroup.java:1246)
E/AndroidRuntime( 3570): at
android.view.ViewGroup.dispatchKeyEvent(ViewGroup.java:1246)
E/AndroidRuntime( 3570): at
android.view.ViewGroup.dispatchKeyEvent(ViewGroup.java:1246)
E/AndroidRuntime( 3570): at
android.view.ViewGroup.dispatchKeyEvent(ViewGroup.java:1246)
E/AndroidRuntime( 3570): at
android.view.ViewGroup.dispatchKeyEvent(ViewGroup.java:1246)
E/AndroidRuntime( 3570): at
android.view.ViewGroup.dispatchKeyEvent(ViewGroup.java:1246)
E/AndroidRuntime( 3570): at
com.android.internal.policy.impl.PhoneWindow$DecorView.superDispatchKeyEvent(Pho
neWindow.java:1891)
E/AndroidRuntime( 3570): at
com.android.internal.policy.impl.PhoneWindow.superDispatchKeyEvent(PhoneWindow.j
ava:1365)
E/AndroidRuntime( 3570): at
android.app.Activity.dispatchKeyEvent(Activity.java:2329)
E/AndroidRuntime( 3570): at
com.android.internal.policy.impl.PhoneWindow$DecorView.dispatchKeyEvent(PhoneWin
dow.java:1818)
E/AndroidRuntime( 3570): at
android.view.ViewRootImpl.deliverKeyEventPostIme(ViewRootImpl.java:3337)
E/AndroidRuntime( 3570): at
android.view.ViewRootImpl.handleFinishedEvent(ViewRootImpl.java:3310)
E/AndroidRuntime( 3570): at
android.view.ViewRootImpl.handleMessage(ViewRootImpl.java:2469)
E/AndroidRuntime( 3570): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 3570): at android.os.Looper.loop(Looper.java:137)
E/AndroidRuntime( 3570): at
android.app.ActivityThread.main(ActivityThread.java:4424)
E/AndroidRuntime( 3570): at java.lang.reflect.Method.invokeNative(Native
Method)
E/AndroidRuntime( 3570): at java.lang.reflect.Method.invoke(Method.java:511)
E/AndroidRuntime( 3570): at
com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:784)
E/AndroidRuntime( 3570): at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:551)
E/AndroidRuntime( 3570): at dalvik.system.NativeStart.main(Native Method)
Original comment by waggo...@gxmconsulting.com
on 26 Nov 2013 at 8:17
I am hoping to leverage the PanoramaClient; the instructions on
https://developers.google.com/photo-sphere/android/ suggest that Google Play
Services is the way to go. I know Glass must be capable of displaying panorama
since (eg "Meet the team"), but it isn't clear how to do so without running
into the Play Services dependency.
Original comment by jason.l...@gmail.com
on 2 Dec 2013 at 6:56
Really need to get this in there...
Original comment by j...@rededge.com
on 10 Dec 2013 at 5:13
Issue 300 has been merged into this issue.
Original comment by ala...@google.com
on 13 Dec 2013 at 4:56
I'd also like to see this, as well. I really want to get access to frequent,
passive location data.
Original comment by e.john.f...@gmail.com
on 18 Dec 2013 at 6:15
So after digging into the code a bit I was able to build a location aware app
for glass using the LocationManager class. Here is the tutorial that got me on
the right path:
http://www.javacodegeeks.com/2011/01/android-proximity-alerts-tutorial.html
Original comment by j...@rededge.com
on 20 Dec 2013 at 4:23
RE: 10, That's fine for certain applications, but there lots of things that
Play Services provides, like passive location. For example, I'd like to have a
service running that kicks on whenever you start moving faster than ~8mph. I
don't need it to start that second, but within about a minute is probably fine.
In order to do that, without killing the battery, I need Play Services.
Original comment by e.john.f...@gmail.com
on 20 Dec 2013 at 4:44
RE #11: agreed. In the meantime you could set a proximity alert for a
reasonable distance from the users current location and upon exiting the
Proximity check Location.getSpeed() and create a new proximityAlert from the
new location...
http://developer.android.com/reference/android/location/Location.html#getSpeed()
I'm not sure how efficient that will be on the battery but it could work...
could be worth a try. Sorry if this is moving off topic... I'm on the Google+
Glass Developer community if you want to move this convo to a more appropriate
forum: https://plus.google.com/u/0/communities/105104639432156353586
Original comment by j...@rededge.com
on 20 Dec 2013 at 4:56
RE #12: My main concern is battery with this. If I can't use the GPS in a
really, really efficient way, then it defeats the purpose, and I'd rather kick
the process off manually until passive GPS is available.
That said, your suggestion is interesting. A better way though, would be to
simply request updates based on distance travelled. You could request a
location every 100m or something and then take a look (since you don't
necessarily know where the person is heading to and they may not reach your
POI).
Regardless, even if all of the passive Location stuff were doable in Glass,
there are other things that Play Services provides that would be really nice to
have. Auth, G+, Wallet, Maps, Leaderboards, etc.
https://developer.android.com/reference/gms-packages.html
Original comment by e.john.f...@gmail.com
on 20 Dec 2013 at 5:01
The majority of applications I am developing for Glass would be far more
impressive and useful is Google Play Services was available. Please provide us
with some details on this issue.
Original comment by Charlesp...@gmail.com
on 5 Jan 2014 at 12:30
My use case is for basic GCM, it seems like Glass Home uses it but also embeds
all of the Play Service functionality within itself, so not sure APKs that use
GDK can leverage that?
Original comment by roberto.andrade
on 19 Jan 2014 at 6:46
Original comment by ala...@google.com
on 3 Feb 2014 at 11:43
Thank you for accepting this issue and looking into the problem.
I'm working with a team of grad students on an application for Glass that turns
the device into a mini-map for indoor buildings using Android Google Maps V2.
The application works great on the phone but we can't test it on the Glass
because play services is not authentic.
We have been waiting to test this program on Glass for quite some time. Please
keep us updated!
Original comment by Charlesp...@gmail.com
on 4 Feb 2014 at 9:12
Another use case: I'd like to use Google Play Game Services Cloud Save
(https://developers.google.com/games/services/common/concepts/cloudsave) to be
able to easily save content (i.e., favorites) from a companion app
(Android/iOS/web) and load these favorites on Glass as the default content.
Original comment by sjbarb...@gmail.com
on 12 Mar 2014 at 4:59
Another use case - passing data from Glass to the paired device a la Android
Wear - see
http://developer.android.com/training/wearables/data-layer/index.html and issue
#395.
Original comment by outofcof...@gmail.com
on 15 Jul 2014 at 9:45
Trying to use Drive API to save files. Don't really need Filepicker ui, just
want to push and pull files.
Original comment by mrcook...@gmail.com
on 12 Jan 2015 at 10:48
Please update us.
Original comment by bran...@nobetw.com
on 23 Jan 2015 at 11:04
Ok I'm working on a project and I need to trace a route on a static MAP with a
Polyline. I tried to use a different way but it seems that the result we need
is necessary use the google api v2. Does It be reasonable waiting for this
issue?
Original comment by Alberto....@gmail.com
on 28 May 2015 at 7:20
Original issue reported on code.google.com by
egt...@gmail.com
on 15 Aug 2013 at 7:21