Oneplus One GPS not reliable



  • I recently got a OnePlus One and flashed Ubuntu Touch onto it.

    Call/Messages work, that's 2/3 requirements I have, the third is GPS.

    When I try to use uNav, I had it work once, but now it cannot find the position. It gives me an error, "GPS Denied" Error reading the GPS status.

    I tried deleting the app and re-adding it. (From the OpenStore)

    I tried rebooting.

    I got some logs for you, it occurs near the bottom, but I'm not sure this is the right logfile.

    /var/log/syslog

    Nov 20 20:01:40 ubuntu-phablet repowerd[782]: UnityScreenService: dbus_clearSysState(:1.91,1978)
    Nov 20 20:01:40 ubuntu-phablet dbus[733]: [system] Activating service name='com.canonical.PropertyService' (using servicehelper)
    Nov 20 20:01:40 ubuntu-phablet dbus[733]: [system] Successfully activated service 'com.canonical.PropertyService'
    Nov 20 20:01:41 ubuntu-phablet repowerd[782]: UnityScreenService: dbus_clearSysState(:1.68,1979)
    Nov 20 20:01:41 ubuntu-phablet repowerd[782]: LibsuspendSuspendControl: allow_suspend(UnityScreenService)
    Nov 20 20:01:42 ubuntu-phablet repowerd[782]: DefaultStateMachine: handle_user_activity_extending_power_state
    Nov 20 20:01:42 ubuntu-phablet repowerd[782]: UnityScreenService: dbus_requestSysState(:1.91,active,1)
    Nov 20 20:01:42 ubuntu-phablet repowerd[782]: LibsuspendSuspendControl: disallow_suspend(UnityScreenService)
    Nov 20 20:01:42 ubuntu-phablet repowerd[782]: UnityScreenService: dbus_requestSysState(:1.91,active,1) => 1980
    Nov 20 20:01:45 ubuntu-phablet repowerd[782]: UnityScreenService: dbus_keepDisplayOn(:1.913)
    Nov 20 20:01:45 ubuntu-phablet repowerd[782]: UnityScreenService: dbus_keepDisplayOn(:1.913) => 278
    Nov 20 20:01:45 ubuntu-phablet repowerd[782]: DefaultStateMachine: handle_disable_inactivity_timeout
    Nov 20 20:01:46 ubuntu-phablet repowerd[782]: UPowerPowerSource: change_device(/org/freedesktop/UPower/devices/battery_battery), is_present=1, state=2, percentage=93.00, temperature=28.00
    Nov 20 20:01:52 ubuntu-phablet repowerd[782]: DefaultStateMachine: handle_user_activity_extending_power_state
    Nov 20 20:01:55 ubuntu-phablet dbus[2491]: apparmor="DENIED" operation="dbus_method_call"  bus="session" path="/com/canonical/usensord/haptic" interface="org.freedesktop.DBus.Introspectable" member="Introspect" mask="send" name="com.canonical.usensord" pid=9264 label="navigator.costales_navigator_0.73" peer_pid=2504 peer_label="unconfined"
    Nov 20 20:01:55 ubuntu-phablet repowerd[782]: message repeated 4 times: [ DefaultStateMachine: handle_user_activity_extending_power_state]
    Nov 20 20:01:55 ubuntu-phablet repowerd[782]: UnityScreenService: dbus_requestSysState(:1.68,usensord,1)
    Nov 20 20:01:55 ubuntu-phablet repowerd[782]: LibsuspendSuspendControl: disallow_suspend(UnityScreenService)
    Nov 20 20:01:55 ubuntu-phablet repowerd[782]: UnityScreenService: dbus_requestSysState(:1.68,usensord,1) => 1981
    Nov 20 20:01:57 ubuntu-phablet repowerd[782]: UnityScreenService: dbus_clearSysState(:1.68,1981)
    Nov 20 20:02:00 ubuntu-phablet kernel: [250843.029770] [rmnet0] error: rmnet_ioct called for unsupported cmd[35585]
    Nov 20 20:02:00 ubuntu-phablet kernel: [250859.706496] wlan: [1493:E :HDP] hdd_tx_rx_pkt_cnt_stat_timer_handler: Disable split scan
    Nov 20 20:02:26 ubuntu-phablet repowerd[782]: UPowerPowerSource: change_device(/org/freedesktop/UPower/devices/battery_battery), is_present=1, state=2, percentage=93.00, temperature=28.00
    Nov 20 20:02:31 ubuntu-phablet kernel: [250889.766533] wlan: [1493:E :HDP] hdd_tx_rx_pkt_cnt_stat_timer_handler: Disable split scan
    

    I currently have the flu, but once I'm healthy I need to go down to a client's place of business and I will need directions. Probably next week, it's a very nasty flu. Not to put undue pressure on you guys, but a phone without GPS is useless to me. If we can't get it to work I'll just flash Android onto it, and re-flash Ubuntu Touch once you guys have Mozilla Location Services available.

    Thank you in advance!



  • Hey guys, in case the time that I have posted this seems weird, I am in Fort Worth, Texas. Central Time Zone. Since uNav opens up to Europe on the first launch, I will assume you guys are mostly in Europe. I will respond when I can. My apologies in advance for any late replies.

    I was looking around at Ubuntu Touch GPS problems, nothing like mine that I can tell, but I did find the test_gps command which is awesome. Although... I don't understand it.

    Within three seconds test_gps returned a location of my house. Not bad. But uNav doesn't get a location, it just errors. How can I fix that?

    I removed the gps location near the end for my privacy. Actually pretty accurate, correct room in the house even. If I let it run a little longer the accuracy would increase, probably to the exact position I'm in right, but it's plenty of data to look through already.
    Output:

    phablet@ubuntu-phablet:~$ test_gps
    *** setup signal handler
    *** get gps interface
    *** device info
     id = gps
     name = loc_api GPS Module
     author = Qualcomm USA, Inc.
    *** init gps interface
    *** set capabilities
    capability is 00000007
     ** Creating thread: 'Loc_hal_worker' (start=0xb6b63135, arg=0xcc8a90)
     ** After thread_create: 'Loc_hal_worker', error=0 (start=0xb6b63135, arg=0xcc8a90)
    open **** Thread wrapper start (start=0xb6b63135, arg=0xcc8a90) ****
    : Unknown error -1226120188
    open: Unknown error -1226120188
     Diag_LSM_Init: Failed to open handle to diag driver, error = 13*** setting positioning mode
    *** start gps track
    *** gps tracking started
    *** tracking.... 
    *** status callback
    *** session begin
    *** status callback
    *** engine on
    *** status callback
    *** session begin
    *** nmea info
    timestamp:	-593224839
    nmea (29): 	$GPGSA,A,1,,,,,,,,,,,,,,,*1E
    *** nmea info
    timestamp:	-593224839
    nmea (24): 	$GPVTG,,T,,M,,N,,K,N*2C
    *** nmea info
    timestamp:	-593224838
    nmea (24): 	$GPRMC,,V,,,,,,,,,,N*53
    *** nmea info
    timestamp:	-593224838
    nmea (25): 	$GPGGA,,,,,,0,,,,,,,,*66
    *** sv status
    sv_size:	0
    num_svs:	22
    	 azimuth:	0.000000
    	 elevation:	0.000000
    	 prn:	51
    	 size:	0
    	 snr:	32.700001
    	 azimuth:	196.000000
    	 elevation:	9.000000
    	 prn:	3
    	 size:	660
    	 snr:	0.000000
    	 azimuth:	303.000000
    	 elevation:	34.000000
    	 prn:	7
    	 size:	660
    	 snr:	0.000000
    	 azimuth:	142.000000
    	 elevation:	45.000000
    	 prn:	8
    	 size:	660
    	 snr:	0.000000
    	 azimuth:	300.000000
    	 elevation:	64.000000
    	 prn:	9
    	 size:	660
    	 snr:	0.000000
    	 azimuth:	168.000000
    	 elevation:	2.000000
    	 prn:	11
    	 size:	660
    	 snr:	0.000000
    	 azimuth:	37.000000
    	 elevation:	37.000000
    	 prn:	16
    	 size:	660
    	 snr:	0.000000
    	 azimuth:	0.000000
    	 elevation:	0.000000
    	 prn:	22
    	 size:	660
    	 snr:	0.000000
    	 azimuth:	177.000000
    	 elevation:	73.000000
    	 prn:	23
    	 size:	660
    	 snr:	0.000000
    	 azimuth:	47.000000
    	 elevation:	9.000000
    	 prn:	26
    	 size:	660
    	 snr:	0.000000
    	 azimuth:	85.000000
    	 elevation:	45.000000
    	 prn:	27
    	 size:	660
    	 snr:	0.000000
    	 azimuth:	230.000000
    	 elevation:	3.000000
    	 prn:	28
    	 size:	660
    	 snr:	0.000000
    	 azimuth:	286.000000
    	 elevation:	9.000000
    	 prn:	30
    	 size:	660
    	 snr:	0.000000
    	 azimuth:	260.000000
    	 elevation:	53.000000
    	 prn:	66
    	 size:	0
    	 snr:	20.500000
    	 azimuth:	115.000000
    	 elevation:	26.000000
    	 prn:	86
    	 size:	0
    	 snr:	20.700001
    	 azimuth:	351.000000
    	 elevation:	49.000000
    	 prn:	76
    	 size:	0
    	 snr:	23.700001
    	 azimuth:	49.000000
    	 elevation:	24.000000
    	 prn:	75
    	 size:	0
    	 snr:	25.100000
    	 azimuth:	188.000000
    	 elevation:	22.000000
    	 prn:	65
    	 size:	0
    	 snr:	26.299999
    	 azimuth:	282.000000
    	 elevation:	21.000000
    	 prn:	77
    	 size:	0
    	 snr:	0.000000
    	 azimuth:	0.000000
    	 elevation:	0.000000
    	 prn:	87
    	 size:	0
    	 snr:	0.000000
    	 azimuth:	56.000000
    	 elevation:	22.000000
    	 prn:	85
    	 size:	0
    	 snr:	0.000000
    	 azimuth:	322.000000
    	 elevation:	23.000000
    	 prn:	67
    	 size:	0
    	 snr:	0.000000
    *** nmea info
    timestamp:	-593224809
    nmea (61): 	$GPGSV,3,1,12,03,09,196,,07,34,303,,08,45,142,,09,64,300,*7A
    *** nmea info
    timestamp:	-593224808
    nmea (61): 	$GPGSV,3,2,12,11,02,168,,16,37,037,,22,00,000,,23,73,177,*75
    *** nmea info
    timestamp:	-593224807
    nmea (61): 	$GPGSV,3,3,12,26,09,047,,27,45,085,,28,03,230,,30,09,286,*73
    *** nmea info
    timestamp:	-593224806
    nmea (69): 	$GLGSV,3,1,09,66,53,260,21,86,26,115,21,76,49,351,24,75,24,049,25*60
    *** nmea info
    timestamp:	-593224805
    nmea (63): 	$GLGSV,3,2,09,65,22,188,26,77,21,282,,87,00,000,,85,22,056,*61
    *** nmea info
    timestamp:	-593224804
    nmea (28): 	$GLGSV,3,3,09,67,23,322,*5F
    *** nmea info
    timestamp:	-593224803
    nmea (29): 	$GPGSA,A,1,,,,,,,,,,,,,,,*1E
    *** nmea info
    timestamp:	-593224802
    nmea (24): 	$GPVTG,,T,,M,,N,,K,N*2C
    *** nmea info
    timestamp:	-593224801
    nmea (24): 	$GPRMC,,V,,,,,,,,,,N*53
    *** nmea info
    timestamp:	-593224800
    nmea (25): 	$GPGGA,,,,,,0,,,,,,,,*66
    *** nmea info
    timestamp:	-593224799
    nmea (29): 	$GPGSA,A,1,,,,,,,,,,,,,,,*1E
    *** nmea info
    timestamp:	-593224798
    nmea (24): 	$GPVTG,,T,,M,,N,,K,N*2C
    *** nmea info
    timestamp:	-593224797
    nmea (24): 	$GPRMC,,V,,,,,,,,,,N*53
    *** nmea info
    timestamp:	-593224796
    nmea (25): 	$GPGGA,,,,,,0,,,,,,,,*66
    *** sv status
    sv_size:	0
    num_svs:	22
    	 azimuth:	303.000000
    	 elevation:	34.000000
    	 prn:	7
    	 size:	660
    	 snr:	32.500000
    	 azimuth:	300.000000
    	 elevation:	64.000000
    	 prn:	9
    	 size:	660
    	 snr:	29.700001
    	 azimuth:	177.000000
    	 elevation:	73.000000
    	 prn:	23
    	 size:	660
    	 snr:	22.200001
    	 azimuth:	0.000000
    	 elevation:	0.000000
    	 prn:	51
    	 size:	0
    	 snr:	33.299999
    	 azimuth:	196.000000
    	 elevation:	9.000000
    	 prn:	3
    	 size:	660
    	 snr:	0.000000
    	 azimuth:	142.000000
    	 elevation:	45.000000
    	 prn:	8
    	 size:	660
    	 snr:	0.000000
    	 azimuth:	168.000000
    	 elevation:	2.000000
    	 prn:	11
    	 size:	660
    	 snr:	0.000000
    	 azimuth:	37.000000
    	 elevation:	37.000000
    	 prn:	16
    	 size:	660
    	 snr:	0.000000
    	 azimuth:	0.000000
    	 elevation:	0.000000
    	 prn:	22
    	 size:	660
    	 snr:	0.000000
    	 azimuth:	47.000000
    	 elevation:	9.000000
    	 prn:	26
    	 size:	660
    	 snr:	0.000000
    	 azimuth:	85.000000
    	 elevation:	45.000000
    	 prn:	27
    	 size:	660
    	 snr:	0.000000
    	 azimuth:	230.000000
    	 elevation:	3.000000
    	 prn:	28
    	 size:	660
    	 snr:	0.000000
    	 azimuth:	286.000000
    	 elevation:	9.000000
    	 prn:	30
    	 size:	660
    	 snr:	0.000000
    	 azimuth:	188.000000
    	 elevation:	22.000000
    	 prn:	65
    	 size:	0
    	 snr:	26.900000
    	 azimuth:	260.000000
    	 elevation:	53.000000
    	 prn:	66
    	 size:	0
    	 snr:	0.000000
    	 azimuth:	115.000000
    	 elevation:	26.000000
    	 prn:	86
    	 size:	0
    	 snr:	0.000000
    	 azimuth:	282.000000
    	 elevation:	21.000000
    	 prn:	77
    	 size:	0
    	 snr:	0.000000
    	 azimuth:	351.000000
    	 elevation:	49.000000
    	 prn:	76
    	 size:	0
    	 snr:	0.000000
    	 azimuth:	49.000000
    	 elevation:	24.000000
    	 prn:	75
    	 size:	0
    	 snr:	0.000000
    	 azimuth:	0.000000
    	 elevation:	0.000000
    	 prn:	87
    	 size:	0
    	 snr:	0.000000
    	 azimuth:	56.000000
    	 elevation:	22.000000
    	 prn:	85
    	 size:	0
    	 snr:	0.000000
    	 azimuth:	322.000000
    	 elevation:	23.000000
    	 prn:	67
    	 size:	0
    	 snr:	0.000000
    *** nmea info
    timestamp:	-593224767
    nmea (67): 	$GPGSV,3,1,12,07,34,303,33,09,64,300,30,23,73,177,22,03,09,196,*73
    *** nmea info
    timestamp:	-593224766
    nmea (61): 	$GPGSV,3,2,12,08,45,142,,11,02,168,,16,37,037,,22,00,000,*7F
    *** nmea info
    timestamp:	-593224766
    nmea (61): 	$GPGSV,3,3,12,26,09,047,,27,45,085,,28,03,230,,30,09,286,*73
    *** nmea info
    timestamp:	-593224765
    nmea (63): 	$GLGSV,3,1,09,65,22,188,27,66,53,260,,86,26,115,,77,21,282,*6F
    *** nmea info
    timestamp:	-593224764
    nmea (61): 	$GLGSV,3,2,09,76,49,351,,75,24,049,,87,00,000,,85,22,056,*6E
    *** nmea info
    timestamp:	-593224764
    nmea (28): 	$GLGSV,3,3,09,67,23,322,*5F
    *** nmea info
    timestamp:	-593224763
    nmea (29): 	$GPGSA,A,1,,,,,,,,,,,,,,,*1E
    *** nmea info
    timestamp:	-593224762
    nmea (24): 	$GPVTG,,T,,M,,N,,K,N*2C
    *** nmea info
    timestamp:	-593224761
    nmea (24): 	$GPRMC,,V,,,,,,,,,,N*53
    *** nmea info
    timestamp:	-593224761
    nmea (25): 	$GPGGA,,,,,,0,,,,,,,,*66
    *** sv status
    sv_size:	0
    num_svs:	22
    	 azimuth:	196.000000
    	 elevation:	9.000000
    	 prn:	3
    	 size:	660
    	 snr:	23.299999
    	 azimuth:	303.000000
    	 elevation:	34.000000
    	 prn:	7
    	 size:	660
    	 snr:	32.099998
    	 azimuth:	300.000000
    	 elevation:	64.000000
    	 prn:	9
    	 size:	660
    	 snr:	28.500000
    	 azimuth:	37.000000
    	 elevation:	37.000000
    	 prn:	16
    	 size:	660
    	 snr:	18.799999
    	 azimuth:	177.000000
    	 elevation:	73.000000
    	 prn:	23
    	 size:	660
    	 snr:	22.200001
    	 azimuth:	85.000000
    	 elevation:	45.000000
    	 prn:	27
    	 size:	660
    	 snr:	23.000000
    	 azimuth:	0.000000
    	 elevation:	0.000000
    	 prn:	51
    	 size:	0
    	 snr:	33.700001
    	 azimuth:	142.000000
    	 elevation:	45.000000
    	 prn:	8
    	 size:	660
    	 snr:	0.000000
    	 azimuth:	168.000000
    	 elevation:	2.000000
    	 prn:	11
    	 size:	660
    	 snr:	0.000000
    	 azimuth:	0.000000
    	 elevation:	0.000000
    	 prn:	22
    	 size:	660
    	 snr:	0.000000
    	 azimuth:	47.000000
    	 elevation:	9.000000
    	 prn:	26
    	 size:	660
    	 snr:	0.000000
    	 azimuth:	230.000000
    	 elevation:	3.000000
    	 prn:	28
    	 size:	660
    	 snr:	0.000000
    	 azimuth:	286.000000
    	 elevation:	9.000000
    	 prn:	30
    	 size:	660
    	 snr:	0.000000
    	 azimuth:	115.000000
    	 elevation:	26.000000
    	 prn:	86
    	 size:	0
    	 snr:	18.700001
    	 azimuth:	49.000000
    	 elevation:	24.000000
    	 prn:	75
    	 size:	0
    	 snr:	26.600000
    	 azimuth:	188.000000
    	 elevation:	22.000000
    	 prn:	65
    	 size:	0
    	 snr:	24.200001
    	 azimuth:	260.000000
    	 elevation:	53.000000
    	 prn:	66
    	 size:	0
    	 snr:	0.000000
    	 azimuth:	282.000000
    	 elevation:	21.000000
    	 prn:	77
    	 size:	0
    	 snr:	0.000000
    	 azimuth:	351.000000
    	 elevation:	49.000000
    	 prn:	76
    	 size:	0
    	 snr:	0.000000
    	 azimuth:	0.000000
    	 elevation:	0.000000
    	 prn:	87
    	 size:	0
    	 snr:	0.000000
    	 azimuth:	56.000000
    	 elevation:	22.000000
    	 prn:	85
    	 size:	0
    	 snr:	0.000000
    	 azimuth:	322.000000
    	 elevation:	23.000000
    	 prn:	67
    	 size:	0
    	 snr:	0.000000
    *** nmea info
    timestamp:	-593224130
    nmea (69): 	$GPGSV,3,1,12,03,09,196,23,07,34,303,32,09,64,300,29,16,37,037,19*70
    *** nmea info
    timestamp:	-593224129
    nmea (65): 	$GPGSV,3,2,12,23,73,177,22,27,45,085,23,08,45,142,,11,02,168,*74
    *** nmea info
    timestamp:	-593224128
    nmea (61): 	$GPGSV,3,3,12,22,00,000,,26,09,047,,28,03,230,,30,09,286,*7A
    *** nmea info
    timestamp:	-593224128
    nmea (67): 	$GLGSV,3,1,09,86,26,115,19,75,24,049,27,65,22,188,24,66,53,260,*63
    *** nmea info
    timestamp:	-593224127
    nmea (61): 	$GLGSV,3,2,09,77,21,282,,76,49,351,,87,00,000,,85,22,056,*6C
    *** nmea info
    timestamp:	-593224126
    nmea (28): 	$GLGSV,3,3,09,67,23,322,*5F
    *** nmea info
    timestamp:	-593224125
    nmea (29): 	$GPGSA,A,1,,,,,,,,,,,,,,,*1E
    *** nmea info
    timestamp:	-593224125
    nmea (24): 	$GPVTG,,T,,M,,N,,K,N*2C
    *** nmea info
    timestamp:	-593224124
    nmea (24): 	$GPRMC,,V,,,,,,,,,,N*53
    *** nmea info
    timestamp:	-593224123
    nmea (25): 	$GPGGA,,,,,,0,,,,,,,,*66
    *** sv status
    sv_size:	0
    num_svs:	22
    	 azimuth:	196.000000
    	 elevation:	9.000000
    	 prn:	3
    	 size:	660
    	 snr:	22.299999
    	 azimuth:	303.000000
    	 elevation:	34.000000
    	 prn:	7
    	 size:	660
    	 snr:	32.099998
    	 azimuth:	300.000000
    	 elevation:	64.000000
    	 prn:	9
    	 size:	660
    	 snr:	28.799999
    	 azimuth:	168.000000
    	 elevation:	2.000000
    	 prn:	11
    	 size:	660
    	 snr:	17.500000
    	 azimuth:	37.000000
    	 elevation:	37.000000
    	 prn:	16
    	 size:	660
    	 snr:	18.600000
    	 azimuth:	177.000000
    	 elevation:	73.000000
    	 prn:	23
    	 size:	660
    	 snr:	16.100000
    	 azimuth:	85.000000
    	 elevation:	45.000000
    	 prn:	27
    	 size:	660
    	 snr:	23.500000
    	 azimuth:	0.000000
    	 elevation:	0.000000
    	 prn:	51
    	 size:	0
    	 snr:	33.400002
    	 azimuth:	142.000000
    	 elevation:	45.000000
    	 prn:	8
    	 size:	660
    	 snr:	0.000000
    	 azimuth:	0.000000
    	 elevation:	0.000000
    	 prn:	22
    	 size:	660
    	 snr:	0.000000
    	 azimuth:	47.000000
    	 elevation:	9.000000
    	 prn:	26
    	 size:	660
    	 snr:	0.000000
    	 azimuth:	230.000000
    	 elevation:	3.000000
    	 prn:	28
    	 size:	660
    	 snr:	0.000000
    	 azimuth:	286.000000
    	 elevation:	9.000000
    	 prn:	30
    	 size:	660
    	 snr:	0.000000
    	 azimuth:	115.000000
    	 elevation:	26.000000
    	 prn:	86
    	 size:	0
    	 snr:	18.700001
    	 azimuth:	351.000000
    	 elevation:	49.000000
    	 prn:	76
    	 size:	0
    	 snr:	24.000000
    	 azimuth:	49.000000
    	 elevation:	24.000000
    	 prn:	75
    	 size:	0
    	 snr:	22.299999
    	 azimuth:	188.000000
    	 elevation:	22.000000
    	 prn:	65
    	 size:	0
    	 snr:	25.200001
    	 azimuth:	260.000000
    	 elevation:	53.000000
    	 prn:	66
    	 size:	0
    	 snr:	0.000000
    	 azimuth:	282.000000
    	 elevation:	21.000000
    	 prn:	77
    	 size:	0
    	 snr:	0.000000
    	 azimuth:	0.000000
    	 elevation:	0.000000
    	 prn:	87
    	 size:	0
    	 snr:	0.000000
    	 azimuth:	56.000000
    	 elevation:	22.000000
    	 prn:	85
    	 size:	0
    	 snr:	0.000000
    	 azimuth:	322.000000
    	 elevation:	23.000000
    	 prn:	67
    	 size:	0
    	 snr:	0.000000
    *** nmea info
    timestamp:	-593223064
    nmea (69): 	$GPGSV,3,1,12,03,09,196,22,07,34,303,32,09,64,300,29,11,02,168,18*7A
    *** nmea info
    timestamp:	-593223063
    nmea (67): 	$GPGSV,3,2,12,16,37,037,19,23,73,177,16,27,45,085,24,08,45,142,*76
    *** nmea info
    timestamp:	-593223063
    nmea (61): 	$GPGSV,3,3,12,22,00,000,,26,09,047,,28,03,230,,30,09,286,*7A
    *** nmea info
    timestamp:	-593223062
    nmea (69): 	$GLGSV,3,1,09,86,26,115,19,76,49,351,24,75,24,049,22,65,22,188,25*68
    *** nmea info
    timestamp:	-593223061
    nmea (61): 	$GLGSV,3,2,09,66,53,260,,77,21,282,,87,00,000,,85,22,056,*65
    *** nmea info
    timestamp:	-593223061
    nmea (28): 	$GLGSV,3,3,09,67,23,322,*5F
    *** location callback
    flags:	55
    latitude: 	***REMOVED BY ME, LOCATION OF HOUSE***
    longtide: 	***REMOVED BY ME, LOCATION OF HOUSE***
    accuracy:	31.000000
    utc: 	-593223192
    *** nmea info
    timestamp:	-593223058
    nmea (52): 	$GPGSA,A,3,03,07,09,11,16,23,27,,,,,,3.9,3.7,1.0*33
    *** nmea info
    timestamp:	-593223058
    nmea (30): 	$GPVTG,,T,,M,0.0,N,0.0,K,A*23
    *** nmea info
    timestamp:	-593223057
    nmea (68): 	$GPRMC,033425,A,3250.565703,N,09712.806187,W,0.0,,211117,3.7,E,A*2E
    *** nmea info
    timestamp:	-593223057
    nmea (73): 	$GPGGA,033425,3250.565703,N,09712.806187,W,1,07,3.7,186.0,M,-24.0,M,,*7F
    ^C*** cleanup
    


  • Hmm... I rebooted again, and after this reboot uNav works almost instantaneously.

    Placed the GPS marker on the other side of the road, updated to more accurate position after a few minutes. Zooms in to a unavailable zoom level, have to zoom out to see anything. Hmm... Workable, but it needs to be reliable so I still got to figure out how to cause it to happen. It might've been the frantic uninstalling and installing of different Google Map apps (and uNav) from OpenStore and Ubuntu Store. lol

    I would've just stuck with uNav after installing it the first time if it could bring me to a house number instead of just that road. So if I use it to go to a client I have to go to Google Maps, put in the address, get the latitude and longitude, than go to that longitude and latitude. Not ideal but workable. Also hilarious use of Google Maps. Any chance someone has an app that will turn an address into a latitude and longitude, then provide a button that will open up uNav with those coordinates? That would be perfect.

    I tried texting the coordinates to myself using Riot on my computer and uMatrixs on the phone, but I cannot copy and paste out of uMatrix. I'd email to myself but I have separate problems with Dekko and Dekko 2. (Still not working after the reboot. I will post issues tomorrow, it's late and I just wanted GPS right now. I'll post issues for everything else later.) I guess I can just type it in before I leave. Workable but annoying.

    Also I noticed when I went to the location permissions in the settings there were two applications with no name or icon, after the reboot there are now four. I always have all of them on allow. Very odd.

    And to the creator of uNav,=: awesome app. I love that I can search restaurants and stuff using the categories, and those do go to exact coordinates instead of just the road. Not going to the house (building) number is annoying, but not work stopping. Thank you!

    Output where it works:

    Nov 20 22:05:52 ubuntu-phablet dbus[730]: [system] Activating service name='com.canonical.PropertyService' (using servicehelper)
    Nov 20 22:05:52 ubuntu-phablet dbus[730]: [system] Successfully activated service 'com.canonical.PropertyService'
    Nov 20 22:05:52 ubuntu-phablet repowerd[785]: DefaultStateMachine: handle_user_activity_extending_power_state
    Nov 20 22:05:54 ubuntu-phablet repowerd[785]: message repeated 2 times: [ DefaultStateMachine: handle_user_activity_extending_power_state]
    Nov 20 22:05:54 ubuntu-phablet repowerd[785]: UnityScreenService: dbus_requestSysState(:1.86,active,1)
    Nov 20 22:05:54 ubuntu-phablet repowerd[785]: LibsuspendSuspendControl: disallow_suspend(UnityScreenService)
    Nov 20 22:05:54 ubuntu-phablet repowerd[785]: UnityScreenService: dbus_requestSysState(:1.86,active,1) => 22
    Nov 20 22:05:56 ubuntu-phablet repowerd[785]: UnityScreenService: dbus_keepDisplayOn(:1.145)
    Nov 20 22:05:56 ubuntu-phablet repowerd[785]: UnityScreenService: dbus_keepDisplayOn(:1.145) => 4
    Nov 20 22:05:56 ubuntu-phablet repowerd[785]: DefaultStateMachine: handle_disable_inactivity_timeout
    Nov 20 22:06:03 ubuntu-phablet repowerd[785]: DefaultStateMachine: handle_user_activity_extending_power_state
    Nov 20 22:06:03 ubuntu-phablet dbus[2499]: apparmor="DENIED" operation="dbus_method_call"  bus="session" path="/com/canonical/usensord/haptic" interface="org.freedesktop.DBus.Introspectable" member="Introspect" mask="send" name="com.canonical.usensord" pid=6509 label="navigator.costales_navigator_0.73" peer_pid=2512 peer_label="unconfined"
    Nov 20 22:06:03 ubuntu-phablet repowerd[785]: UnityScreenService: dbus_requestSysState(:1.59,usensord,1)
    Nov 20 22:06:03 ubuntu-phablet repowerd[785]: LibsuspendSuspendControl: disallow_suspend(UnityScreenService)
    Nov 20 22:06:03 ubuntu-phablet repowerd[785]: UnityScreenService: dbus_requestSysState(:1.59,usensord,1) => 23
    Nov 20 22:06:03 ubuntu-phablet core::trust::Daemon::Skeleton[2842]: CachedAgent::authenticate_request_with_parameters: Application pid: 6509 Application uid: 32011 Application id:  navigator.costales_navigator Cached request:   Request(from: navigator.costales_navigator, feature: 0, when: 1510970889165293342, answer: granted)
    Nov 20 22:06:04 ubuntu-phablet repowerd[785]: UnityScreenService: dbus_clearSysState(:1.59,23)
    Nov 20 22:06:05 ubuntu-phablet kernel: [  548.517552] [rmnet0] error: rmnet_ioct called for unsupported cmd[35585]
    Nov 20 22:06:05 ubuntu-phablet kernel: [  558.078381] wlan: [1797:E :HDP] hdd_tx_rx_pkt_cnt_stat_timer_handler: Disable split scan
    Nov 20 22:06:10 ubuntu-phablet repowerd[785]: UPowerPowerSource: change_device(/org/freedesktop/UPower/devices/battery_battery), is_present=1, state=2, percentage=80.00, temperature=27.50
    


  • Okay, last night after I went to bed I noticed when I put my phone to the side the screen goes horizontal. Apparently the accelerometer is fixed as well. (I didn't realize I had one. In fact I deleted an app that required me to go horizontal and I couldn't, don't remember what it was.) When I went to the sensor app it was just dashes. But after the reboot it works now and the sensor app shows data. I have no data for any of the other sensors except GPS, I think it's just the accelerometer and GPS that I have on the hardware.

    Whatever this issue is, it affects all available sensors, not just GPS. I have logs, but I don't know how to get it to replicate. If it happens again, I will look at what I had done just before it broke and post here.

    Anyone else have this issue?

    Tonight (Central Time Zone) I will post some other less important issues. Is there a list of github projects for the different apps? I can post the issues directly there.

    Thank you!


  • Infrastructure

    @josephtocci Hi,

    for the apps: Please go to Github and search for "-app" in our organization: https://github.com/ubports?utf8=✓&q=-app&type=&language=

    uNav is not a core app however, its dann by our genious Marcos Costales and he could answer you most of your questions probably.

    Last idea: OPO can have boot issues, it sometimes turns off again for me after a boot, I have to cold-boot it again. So maybe it depends on some strange boot conditions if your sensors work or not ;)

    Try https://plus.google.com/+MarcosCostales

    BR Florian



  • Thank you!

    Next time I boot and the GPS does not work, I will post a full dmesg and syslog.

    It seems most of my other issues are already posted. If I catch something unreported I'll let you guys know.


Log in to reply
 

Looks like your connection to UBports Forum was lost, please wait while we try to reconnect.