Works only on browser? about mobile-packages HOT 6 CLOSED

I looked into this. In the Android emulator, it turns out you have to provide a GPS location.

Run this:
~/.meteor/android_bundle/android-sdk/platform-tools/adb emu geo fix -111.0250778 35.0275474

Note this is $longitude $latitude, whereas Google Maps gives you $latitude $longitude. If you forget to swap them the invalid location will likely be silently ignored.

Here's some background: http://stackoverflow.com/questions/2279647/how-to-emulate-gps-location-in-the-android-emulator

I don't know if we should be setting a location for you by default.

from mobile-packages.

Also, I tried it on my android device. It did start reporting my correct GPS location after a brief delay (for me, it was on the second poll).

On your device, double-check that GPS is enabled and give it time to lock-on?

from mobile-packages.

Okay it does work on emulator when I use geo fix indeed. On the other hand I could not find the emulator program on my computer so I used this method which worked like a charm.

Once I got it working on emulator I could easily debug the issues on my phone. Thanks for the info!

I don't think a default location should be set either. Maybe put a quick tip on the readme somewhere? Personally I really did not think the emulator was the issue, so I never stumbled on those kind of answers...

from mobile-packages.

Great news, and thanks for the feedback on default vs a warning.

So we can figure out what that warning should say, are you saying the command ~/.meteor/android_bundle/android-sdk/platform-tools/adb emu geo fix -111.0250778 35.0275474 didn't work for you? And the telnet approach did work? Are you using USE_GLOBAL_ADK?

from mobile-packages.

Yes, this command didn't work.

I wouldn't know... How do I check this?

from mobile-packages.

@justinsb any updates on this?

from mobile-packages.