so first, the GPS download warning is indeed just a warning; the GPS
provider currently only works standalone, there's a bug preventing it to
work with the HERE location provider ("Espoo").The issue you now have is that the default location service config points to the HERE location provider which you seem not to have. It's in the custom tarballs for krillin and mako on utopic and rtm and the wrappers are in the ubuntu-location-provider-here package. Cheers, -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1367835 Title: Error downloading GPS Xtra data: [...] Timeout was reached: No space left on device Status in “location-service” package in Ubuntu: Confirmed Bug description: Hi, To test location-service with latest utopic-proposed image on mako, I had to make some adjustments: 1) change: export HERE_IMEI_FRAGMENT=$Serial to: export HERE_IMEI_FRAGMENT=35513605 in /etc/init/ubuntu-location-provider-here-posclientd.conf to help the service come up on boot (see bug #1367244), not sure it helps though. 2) change exec /usr/bin/ubuntu-location-serviced --bus system --provider $provider $poptions to: exec /usr/bin/ubuntu-location-serviced --bus system --provider $provider $poptions --provider remote::Provider --remote::Provider::name="com.ubuntu.espoo.Service.Provider" --remote::Provider::path="/com/ubuntu/espoo/Service/Provider" in /etc/init/ubuntu-location-service.override. I saw this in location-service log: E0910 16:42:09.632657 4078 android_hardware_abstraction_layer.cpp:157] Error downloading GPS Xtra data: /build/buildd/net-cpp-1.1.0+14.10.20140804/src/core/net/http/impl/curl/request.h@157 - execute: Timeout was reached: No space left on device $ system-image-cli -i current build number: 235 device name: mako channel: ubuntu-touch/utopic-proposed last update: 2014-09-10 15:19:31 version version: 235 version ubuntu: 20140910 version device: 20140903.1 version custom: mako-0.3a Seems this is due to GPS data file being saved to the wrong place: $ df -hl Filesystem Size Used Avail Use% Mounted on /dev/loop0 2,0G 1,5G 423M 78% / udev 916M 4,0K 916M 1% /dev tmpfs 184M 728K 183M 1% /run /dev/mmcblk0p23 13G 1,7G 11G 14% /home /dev/loop1 107M 105M 1,5M 99% /lib/modules none 4,0K 0 4,0K 0% /android tmpfs 918M 4,0K 918M 1% /etc/fstab /dev/disk/by-partlabel/cache 552M 55M 498M 10% /android/cache /dev/disk/by-partlabel/persist 16M 4,2M 12M 27% /android/persist /dev/disk/by-partlabel/modem 64M 54M 11M 83% /android/firmware none 4,0K 0 4,0K 0% /sys/fs/cgroup tmpfs 918M 32K 918M 1% /tmp none 5,0M 0 5,0M 0% /run/lock none 918M 96K 918M 1% /run/shm none 100M 24K 100M 1% /run/user tmpfs 918M 0 918M 0% /media tmpfs 918M 8,0K 918M 1% /var/lib/sudo Cheers, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1367835/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
