PostFrontal Forum
PostFrontal Forum
LK8000_Support_Forum | Profile | Register | Active Topics | Members | Search | FAQ
Username:
Password:
Save Password
Forgot your Password?

 All Forums
 LK8000 International Support
 BUG reporting and solved list
 6.1r Xiaomi Mi5X GPS No Valid Fix (NOBUG)
 New Topic  Reply to Topic
Next Page
Author Previous Topic Topic Next Topic
Page: of 2

Alebu
Falchetto

Italy
105 Posts

Posted - 26/04/2018 :  21:58:37  Show Profile  Reply with Quote
Hi, just installed LK8000 on the brand new Android smartphone Xiaomi Mi5X original ROM MIUI 9.5.3.0 (Chinese). Everything seems to work fine exluded the fact that very often ( almost each 5 seconds) the message "GPS: No Valid Fix" appears. Runtime file is also available but I don't know how to attach it here.

Best regards,


Alebu

Edited by - AlphaLima on 14/05/2018 11:33:30

AlphaLima
Moderator

Germany
1978 Posts

Posted - 26/04/2018 :  22:02:13  Show Profile  Visit AlphaLima's Homepage  Reply with Quote
"No Valid Fix" means the GPS does not receive GPS Statelite data.
Have you tested it inside a building? go outside and try again.
Go to Top of Page

Alebu
Falchetto

Italy
105 Posts

Posted - 26/04/2018 :  22:09:59  Show Profile  Reply with Quote
Good point, but unfortunately I was under a clear sky.
Go to Top of Page

AlphaLima
Moderator

Germany
1978 Posts

Posted - 26/04/2018 :  22:26:43  Show Profile  Visit AlphaLima's Homepage  Reply with Quote
Hmm, can you make an NMEA log and post it here or send it to AlphaLima (at) lk8000.it
Go to Top of Page

Marco from Hangar 5
Pterodattilo

Netherlands
886 Posts

Posted - 27/04/2018 :  18:28:36  Show Profile  Reply with Quote
My two cents..

If the gps was located in China first and turned off there before you turned it on in Italy, it may take some time for the GPS to find out where it actually is.. This can take 30 minutes or even more in some cases.

Turn on the GPS (run LK8000) and leave it outside with as much as possible open sky above, and do not move the phone untill you do not get that "NO VALID GPS FIX" message anymore. This may take quite some time, so be patient!

Of course, if the GPS works fine in other applications (try Google maps or Waze) above is not applicable and the problem is related to something else

Marco
BU (PH-588)
Mini Nimbus HS7, s/n 039
http://www.zweef.nl/
Zweefvliegcentrum Noordkop, NETHERLANDS
Go to Top of Page

Alebu
Falchetto

Italy
105 Posts

Posted - 27/04/2018 :  21:35:25  Show Profile  Reply with Quote
Thanks Marco,
I did as suggested by you but nothing changed. Please notice that the device makes the fix correctly. As I told, LK8000 works fine, the only problem is the message that comes out continuously. While doing your tentative I did notice another detail. The message (GPS: No valid fix) comes out also when I zoom in and out. Not always but the 95% of the times. When the message comes out by it selves LK does also the "bing" sound. When it pops up while zooming there is the zoom "click" only.

Regards.
Go to Top of Page

MrGoMario
Pulcino

South Africa
11 Posts

Posted - 01/05/2018 :  16:01:43  Show Profile  Reply with Quote
How interesting. I have the Xiaomi Mi5s Plus. I had the exact same issue but after recently updating the ROM to 9.5.2.0 Global Stable, the issue disappeared totally. My device is also rooted but that should not be an issue. Keep in mind, Xiaomi is actively developing the OS and they do it quite a lot. Mistakes can and will happen. Just try some other ROM. I know a few things about Android and Xiaomi. Let me know if you don't come right.
Go to Top of Page

MrGoMario
Pulcino

South Africa
11 Posts

Posted - 10/05/2018 :  13:33:51  Show Profile  Reply with Quote
UPDATE: I managed to emulate the issue you are having (or at least I think so). Indeed, there seems to be a issue with LK8000 too. Without going into detail, here is a potential solution. Before starting the LK8000 program do the following:
1. Make sure the GPS has a good location fix.
2. Switch OFF and back ON the GPS on your Xiaomi.
3. Immediately thereafter START the LK8000 program.
If it finds the GPS I think I know where to look for a LK8000 fix. Let me know please.
Go to Top of Page

Alebu
Falchetto

Italy
105 Posts

Posted - 10/05/2018 :  22:53:04  Show Profile  Reply with Quote
Dear MrGoMario,
I really appreciate your effort but having sent back the Mi5X I'm no more in condition to follow the procedure you suggest.
I'm sure it will be very useful to other people.
Thanks a lot.
Go to Top of Page

danielvelez
Falchetto

Colombia
145 Posts

Posted - 17/07/2018 :  01:14:57  Show Profile  Visit danielvelez's Homepage  Click to see danielvelez's MSN Messenger address  Reply with Quote
Hello MrGoMario. I´m reopening the issue.
I bought another Chinese android phone called Hisense A2 Pro. Beautiful.

I´m having the "GPS: No valid fix" bug every 5 secs or so, while I´m perfectly connected to sats, and recording a IGC log using GPSDUMP on background. 11-14 sats on visual. Good strenght. It seems like there´s a tiny break on coms with the gps and so the LK8000 gives you the audio alarm and the text, even when it seems like you are showing great on the nav map, and everything else seems working fine.
Go to Top of Page

danielvelez
Falchetto

Colombia
145 Posts

Posted - 17/07/2018 :  15:38:41  Show Profile  Visit danielvelez's Homepage  Click to see danielvelez's MSN Messenger address  Reply with Quote
quote:
Originally posted by AlphaLima

Hmm, can you make an NMEA log and post it here or send it to AlphaLima (at) lk8000.it



Hello AlphaLima. I'm having this strange behaviour too on another chinese android phone. I'm currently using a cheap lg phone that works perfect with lk but the chinese has "e-ink" on one of the sides so it's more readable on sunlight, so I was hopping on making it work.

(Hisense A2 Pro, with android 7.1).

Is there a way of connecting to the internal android gps using a "pass through" app that can be detected as an external device by lk8000? Just to see if a "filtered nmea" sentence can fix the issue...

I'm gonna try to record an NMEA sentence today, and maybe the runtime.log, and send it to you to see if you can give me a hand.

Go to Top of Page

danielvelez
Falchetto

Colombia
145 Posts

Posted - 17/07/2018 :  21:37:13  Show Profile  Visit danielvelez's Homepage  Click to see danielvelez's MSN Messenger address  Reply with Quote
So far what I´m guessing is that the GPS frecuency on the Qualcomm board on this phones is not refreshing as required or verified by lk8000. Maybe there´s a way of changing the tolerance on LK8000 without compromising it´s behaviour, and that allows for the NMEA sentences of this phones to be fully accepted and "valid 3d FIX".

I´m hard reseting the phone because made some mess playing with configuration codes... So I will re-install lk8000 and try to record a Runtime.log , an nmea log and a IGC log file if you guys could take a look.
Go to Top of Page

danielvelez
Falchetto

Colombia
145 Posts

Posted - 17/07/2018 :  22:28:36  Show Profile  Visit danielvelez's Homepage  Click to see danielvelez's MSN Messenger address  Reply with Quote
Ok. NMEA log did not record anything. Probably because it only records external devices?

Runtime log:

[001312033] ------------------------------------------------------------
[001312034] . Starting LK8000 v6.1r Feb 26 2018 LINUX
[001312035] . System Name: Linux localhost
[001312036] . Kernel Version: 3.18.31-perf-g502f558-01290-gd6f4726
[001312036] . Kernel Build: #1 SMP PREEMPT Tue Apr 10 23:24:38 CST 2018
[001312036] . Machine Arch: aarch64
[001312038] . Free ram=173804 K storage=4294967295 K
[001312039] . Host and Cpu informations not available
[001312650] .... LoadProfile </storage/emulated/0/LK8000/_Configuration/DEFAULT_AIRCRAFT.acf> open failed
[001312651] .... LoadProfile </storage/emulated/0/LK8000/_Configuration/DEFAULT_PILOT.plt> open failed
[001312653] .... LoadProfile </storage/emulated/0/LK8000/_Configuration/DEFAULT_DEVICE.dvc> open failed
[001312658] . InitLKScreen: AUTORES 1080x1920
[001314597] . LKInstall created </storage/emulated/0/LK8000/_Configuration/LASTINFO.TXT>
[001316416] .... LoadProfile </storage/emulated/0/LK8000/_Configuration/DEFAULT_PILOT.plt> open failed
[001316417] .... LoadProfile </storage/emulated/0/LK8000/_Configuration/DEFAULT_DEVICE.dvc> open failed
[001316419] .... LoadProfile </storage/emulated/0/LK8000/_Configuration/DEFAULT_AIRCRAFT.acf> open failed
[001316941] . Loading polar file </data/app/org.lk8000.beta-1/base.apk/assets/polars/Default.plr>
[001316956] . Terrain Open RasterMapRaw </storage/emulated/0/LK8000/_Maps/DEMO.DEM>
[001316958] ... Terrain size is 2073600
[001316959] ... Available memory is 141740kB
[001316960] ... Terrain : use heap memory
[001316971] . Waypoint file 1 format: SeeYou
[001316973] . LOADED 58 WAYPOINTS + 19 virtuals
[001316974] ... Cannot load recent wp history
[001316980] . open AirfieldFile <WAYNOTES.txt>
[001316981] ...... No HomeWaypoint, default position set to terrain center
[001316997] . Reading OpenAir airspace file
[001317000] . Now we have 15 airspaces
[001317001] ... No airspace file 2
[001317093] . LKMAPS Advanced Topology file found
[001317101] . FLARMNET database, found 0 IDs
[001317109] . ComCheck Init
[001317109] . Device A is <Internal> Port=internal
[001317123] . Device B is DISABLED.
[001317124] . Device C is DISABLED.
[001317124] . Device D is DISABLED.
[001317124] . Device E is DISABLED.
[001317124] . Device F is DISABLED.
[001317287] . GCE_STARTUP_REAL
[001317288] . ProgramStarted=NormalOp h19:50:41 (NO FIX)
[001317288] . Free ram=165752 K storage=4294967295 K
[001317335] . LoadTask : </storage/emulated/0/LK8000/_Tasks/Default.lkt>
[001318326] . LK Battery Manager V1 started, current charge=57%
[001333525] . First GPS DATE: 2018-7-17 h19:51:00 (NO FIX)
[001350307] . Logger Started h19:51:16 (UTC 19:51) File </storage/emulated/0/LK8000/_Logger/2018-07-17-XLK-WOC-01.IGC>
[001415813] . Logger OK, IGC signed with G-Record
[001415815] . Logger: File saved h19:52:22 (UTC 19:52)
[001429608] . Entering shutdown h19:52:36 (UTC 19:52)
[001430356] . Save history to </storage/emulated/0/LK8000/_Configuration/History.txt>
[001430357] . SaveRecentList: saved 0 recent waypoints
[001430376] . SaveTask : saving </storage/emulated/0/LK8000/_Tasks/Default.lkt>
[001430415] . Stop COM devices
[001430421] . Settings for 15 airspaces saved to file </storage/emulated/0/LK8000/_Airspaces/AspConfig.LK>
[001430423] . CloseLKAirspace
[001430424] . ComPort 0: status=1 Rx=0 Tx=0 ErrRx=0 ErrTx=0
[001430424] . ComPort 1: status=1 Rx=0 Tx=0 ErrRx=0 ErrTx=0
[001430425] . ComPort 2: status=1 Rx=0 Tx=0 ErrRx=0 ErrTx=0
[001430426] . ComPort 3: status=1 Rx=0 Tx=0 ErrRx=0 ErrTx=0
[001430426] . ComPort 4: status=1 Rx=0 Tx=0 ErrRx=0 ErrTx=0
[001430427] . ComPort 5: status=1 Rx=0 Tx=0 ErrRx=0 ErrTx=0
[001430428] . Finished shutdown h19:52:36 (UTC 19:52)
[001430429] . WndMain::OnDestroy


And IGC log at the same time:

AXLKWOC
HFDTE170718
HFPLTPILOT:WOLF.HIRTH
HFGTYGLIDERTYPE:CIRRUS-STD
HFGIDGLIDERID:D-1900
HFCCLCOMPETITIONCLASS:CLUB
HFCIDCOMPETITIONID:WH
HFFTYFRTYPE:LK8000 LINUX
HFRFWFIRMWAREVERSION:6.1r
HFDTM100GPSDATUM:WGS-84
C170718195100000000000002
C0610747N07534912WTAKEOFF
C4546556N00935603EUBIONE
C4549500N00906917EBRUNATE
C4605643N00924846ELEGNONE
C4546556N00935603EUBIONE
C0610747N07534912WTAKEOFF
B1951000610741N07534901WA0000001589
B1951010610738N07534903WA0000001584
B1951020610743N07534905WA0000001585
B1951030610745N07534908WA0000001587
B1951040610744N07534907WA0000001586
B1951050610745N07534907WA0000001583
B1951060610745N07534909WA0000001578
B1951070610746N07534909WA0000001577
B1951080610746N07534910WA0000001574
B1951090610746N07534910WA0000001572
B1951100610747N07534911WA0000001572
B1951110610747N07534912WA0000001569
B1951120610747N07534911WA0000001571
B1951130610747N07534911WA0000001569
B1951140610747N07534911WA0000001568
B1951150610747N07534912WA0000001567
B1951160610747N07534912WA0000001566
B1951180610747N07534913WA0000001564
B1951200610747N07534913WA0000001564
B1951210610747N07534913WA0000001564
B1951220610747N07534913WA0000001564
B1951230610747N07534913WA0000001563
B1951240610747N07534914WA0000001563
B1951250610747N07534913WA0000001563
B1951260610747N07534914WA0000001563
B1951270610747N07534913WA0000001563
B1951280610747N07534913WA0000001563
B1951290610747N07534913WA0000001562
B1951300610747N07534913WA0000001562
B1951320610747N07534913WA0000001562
B1951330610747N07534913WA0000001562
B1951340610747N07534913WA0000001562
B1951350610747N07534913WA0000001562
B1951360610747N07534913WA0000001562
B1951370610747N07534913WA0000001562
B1951380610747N07534913WA0000001568
B1951390610747N07534913WA0000001568
B1951400610747N07534913WA0000001567
B1951410610747N07534913WA0000001566
B1951420610747N07534913WA0000001565
B1951430610747N07534913WA0000001565
B1951440610747N07534913WA0000001564
B1951450610747N07534913WA0000001564
B1951460610747N07534913WA0000001564
B1951470610747N07534913WA0000001564
B1951480610747N07534913WA0000001564
B1951490610747N07534913WA0000001564
B1951500610747N07534913WA0000001563
B1951510610747N07534913WA0000001563
B1951520610747N07534913WA0000001563
B1951530610747N07534913WA0000001563
B1951540610747N07534913WA0000001563
B1951550610747N07534913WA0000001563
B1951560610747N07534913WA0000001563
B1951570610747N07534913WA0000001563
B1951580610747N07534913WA0000001563
B1951590610747N07534913WA0000001563
B1952000610747N07534913WA0000001563
B1952010610747N07534913WA0000001562
B1952020610747N07534913WA0000001562
B1952030610747N07534913WA0000001568
B1952040610747N07534913WA0000001567
B1952050610747N07534913WA0000001566
B1952060610747N07534913WA0000001565
B1952070610747N07534913WA0000001564
B1952080610747N07534913WA0000001564
B1952090610747N07534913WA0000001564
B1952100610747N07534913WA0000001563
B1952110610747N07534913WA0000001563
B1952120610747N07534913WA0000001563
B1952130610747N07534913WA0000001563
B1952140610747N07534913WA0000001563
B1952150610747N07534913WA0000001564
B1952170610747N07534913WA0000001564
B1952180610747N07534913WA0000001564
B1952190610747N07534913WA0000001564
B1952200610747N07534913WA0000001564
B1952210610747N07534913WA0000001564
B1952220610747N07534913WA0000001564
Gccff886cf8cf9ff9
Gdd00413e91fbedf1
G06b2f6f4450331ab
Gb51f53408920ce9f
G6a25e41f7ccf5e30
Gd7e38bc40e19405e
G7b30468be2fd893c
G0695a2fd918a0cf9


As you see, the logger seems to be recording all the gps positions just fine, but the "Invalid Fix" is showing almost all the time, and only briefly the 3D Fix comes out on the status window.

Go to Top of Page

brunotl
Pterodattilo

France
1090 Posts

Posted - 18/07/2018 :  13:24:24  Show Profile  Reply with Quote
can you check Gps Accuracy with apps like "Status GPS"
Go to Top of Page

danielvelez
Falchetto

Colombia
145 Posts

Posted - 18/07/2018 :  19:50:25  Show Profile  Visit danielvelez's Homepage  Click to see danielvelez's MSN Messenger address  Reply with Quote
quote:
Originally posted by brunotl

can you check Gps Accuracy with apps like "Status GPS"



Yes. Indee. I have prepared some files.

I did a Moto ride to office this morning. Running gpsdump on background and nmea tools, and Lk8000 on front. The log files, the runtime log, the nmea log, the tracks on igc and kml as recorded by lk and gpsdump are here...

https://www.dropbox.com/s/8ndpjw5t4f0zfu4/Logs.zip?dl=0

Also i made a youtube video of the screen on LK showing the missbehaviour.

Here

https://youtu.be/fEkT633k5C8


Go to Top of Page

danielvelez
Falchetto

Colombia
145 Posts

Posted - 18/07/2018 :  21:40:55  Show Profile  Visit danielvelez's Homepage  Click to see danielvelez's MSN Messenger address  Reply with Quote
Ok. I think i found a difference on the way the Hisense A2Pro (A2P) phone sends GPS sentences and the way that a samsung s7 (SS7) does:

A2P: $GPGGA,035424.00,0610.749545,N,07534.912703,W,2,10,0.7,1576.0,M,13.0,M,,*4A
SS7: $GPGGA,035424.56,0610.742627,N,07534.906191,W,1,09,3.2,1561.3,M,2.0,M,,*75

Main difference (regardless the Samsung is sending positions at intervals different than the exact seccond, don´t know why...)
After the position record, there´s the "valid/invalid" number as per this deffinition of the sentences:

Where:
GGA Global Positioning System Fix Data
123519 Fix taken at 12:35:19 UTC
4807.038,N Latitude 48 deg 07.038' N
01131.000,E Longitude 11 deg 31.000' E
1 Fix quality: 0 = invalid
1 = GPS fix (SPS)
2 = DGPS fix
3 = PPS fix
4 = Real Time Kinematic
5 = Float RTK
6 = estimated (dead reckoning) (2.3 feature)
7 = Manual input mode
8 = Simulation mode
08 Number of satellites being tracked
0.9 Horizontal dilution of position
545.4,M Altitude, Meters, above mean sea level
46.9,M Height of geoid (mean sea level) above WGS84
ellipsoid
(empty field) time in seconds since last DGPS update
(empty field) DGPS station ID number
*47 the checksum data, always begins with *

So the A2P is sending "2" that means DGPS Fix. Probably LK only checks for this field to be =1, and everything else is "Invalid"?
Go to Top of Page
Page: of 2 Previous Topic Topic Next Topic  
Next Page
 New Topic  Reply to Topic
Jump To:
PostFrontal Forum © PostFrontal - La community del Volo a Vela Go To Top Of Page
This page was generated in 0.14 seconds. Snitz Forums 2000

Since 2006, owned and maintained by PostFrontal S.A.S. di Giuliano Golfieri & c. - VAT ID: IT05264240960
THIS WEBSITE ONLY USES FUNCTIONAL COOKIES
Privacy & Cookie Policy