Not sure if this is a bug or a feature: I have several T-Beams with 8M and just updated two of them to 1.2.64 - the rest remained in 1.2.55. I noticed that GPS is never turned off and it keeps running even when rest of the device is in light-sleep. Would not this shorten the battery time ?
This is true, it is a last legacy release to fix some gps issues with other hardware, 1.2.64 is probably not a good choice for a neo 6m tbeam
Let’s see, caveman99 is quite busy with GPS.cpp and I will wait now until it settles down. I might then do my own improvements and see if I can gain battery time.
actually you might try now, i think i have all kinked out …
https://github.com/meshtastic/artifacts/blob/device/pr/pr1455-firmware-1.2.64.179a262.zip?raw=true
If you can confirm general GPS operation i can put it back to sleep once in a while.
Sorry for the slight hijack - complete newbie here - and wondering if there a wider issue with the gps update in 1.2.64.
In contrast to OP’s devices always being powered on, I’ve got the no GPS module after updating a pair of v.1.1’s to 1.2.64.
When I first powered them up, they both got GPS lock and a few satellites. However, since the Meshtastic Android app updated the devices to 1.2.64 OTA and now I’ve had the the “No GPS Module” message for the last 6 hours.
I thought that following#327, all future updates would reset the GPS by default? Link to the post re #327: [FIXED] "No Sats"/No Red GPS LED - Aliexpress TBeam 1.1 NEO-6M - Fixed for me! - #2 by geeksville
Thoughts welcome!
please try the newer firmware from https://github.com/meshtastic/artifacts/blob/device/pr/pr1455-firmware-1.2.64.179a262.zip?raw=true
No Problem - your hijack just reminded me that I had the same issue as well, but I did not yet open issue/topic whatever… It seems that you have to leave the T-Beam completely powerless for a while and the GPS will work. I think this has also something to do with powering of the GPS-module. I will test that one as well with new version
What happens with the new firmware: if there is NO communication whatsoever with the GPS chip 60 seconds after poweron it will issue a factory reset to the chip next time the device is rebooted. Since this request for factory reset is issued after the device is opened and initialized for operation with meshtastic (for reasons we cannot change) you may have to reset the device one more time to get it to register the GPS Chip. This procedure will only fail if the chip somehow was set to a different baudrate. In this case please use the GPS Reset Sketch found here: GitHub - eriktheV-king/TTGO_T-beam_GPS-reset: Reset U-blox NEO GPS devices on TTGO T-beam T22- V1.0 and 1.1 back to factory settings
Thanks for letting me know rsainio. I left one with, and one without the battery overnight, no change this morning.
Thanks Caveman99.
Unfortunately I can’t be sure which version of the firmware is on the device other that to say it was flashed by the Android app yesterday, so presumably latest version (?). As of this morning, one has a blinking red LED but still saying no GPS module, the other is in the same state but no LED.
Another minor problem is that I can’t get the devices to communicate with my iMac at the moment most likely due to (1) the age of my imac although I have the latest versions of Python and PIP or (2) my microUSB cable is not transmitting the data (although the meshtastic web client is working fine). Sorry state of affairs really!
A useful feature in the mobile apps might be to offer the ability to roll back firmware versions over the air, which means I don’t have to buy a new computer!
Thanks, I tested it on one of my TBeams, however it does not switch off GPS. I consider GPS on when that LED blinks.
Here is an excerpt from my console log when it enter LS
12:47:28 21005 [PowerFSM] Done shutting down bluetooth
Shutdown BT: 204624 heap size
12:47:28 21005 [PowerFSM] GPS prepare sleep!
12:47:58 21035 [PowerFSM] GPS prepare sleep!
12:47:58 21035 [Power] Battery: usbPower=1, isCharging=0, batMv=0, batPct=0
12:47:58 21035 [PowerFSM] GPS prepare sleep!
12:48:28 21065 [PowerFSM] GPS prepare sleep!
12:48:28 21065 [Power] Battery: usbPower=1, isCharging=0, batMv=0, batPct=0
12:48:28 21066 [PowerFSM] GPS prepare sleep!
12:48:58 21096 [PowerFSM] GPS prepare sleep!
12:48:58 21096 [Power] Battery: usbPower=1, isCharging=0, batMv=0, batPct=0
12:48:58 21096 [PowerFSM] GPS prepare sleep!
12:49:28 21126 [PowerFSM] GPS prepare sleep!
12:49:28 21126 [Power] Battery: usbPower=1, isCharging=0, batMv=0, batPct=0
12:49:28 21126 [PowerFSM] GPS prepare sleep!
12:49:58 21156 [PowerFSM] GPS prepare sleep!
12:49:58 21156 [Power] Battery: usbPower=1, isCharging=0, batMv=0, batPct=0
12:49:58 21156 [PowerFSM] GPS prepare sleep!
12:50:28 21186 [PowerFSM] GPS prepare sleep!
12:50:28 21186 [Power] Battery: usbPower=1, isCharging=0, batMv=0, batPct=0
12:50:28 21186 [RadioIf] (bw=31, sf=9, cr=4/8) packet symLen=16 ms, payloadSize=40, time 2265 ms
12:50:28 21186 [RadioIf] Lora RX (id=0x06e2b886 Fr0x74 To0xff, WantAck0, HopLim3 Ch0x2 encrypted rxSNR=11.25)
12:50:28 21186 [RadioIf] AirTime - Packet received : 2265ms
12:50:28 21186 [Router] Add packet record (id=0x06e2b886 Fr0x74 To0xff, WantAck0, HopLim3 Ch0x2 encrypted rxSNR=11.25)
12:50:28 21186 [Router] Using channel 0 (hash 0x2)
12:50:28 21186 [Router] Installing AES256 key!
12:50:28 21186 [Router] decoded message (id=0x06e2b886 Fr0x74 To0xff, WantAck0, HopLim3 Ch0x0 Portnum=67 rxtime=1652964628 rxSNR=11.25)
12:50:28 21186 [Router] handleReceived(REMOTE) (id=0x06e2b886 Fr0x74 To0xff, WantAck0, HopLim3 Ch0x0 Portnum=67 rxtime=1652964628 rxSNR=11.25)
12:50:28 21186 [Router] Plugin ‘EnvironmentalMeasurement’ wantsPacket=1
12:50:28 21186 [Router] Received EnvironmentalMeasurement from=0xc460f074, id=0x6e2b886, portnum=67, payloadlen=20
12:50:28 21186 [Router] Plugin ‘EnvironmentalMeasurement’ considered
12:50:28 21186 [Router] Plugin ‘routing’ wantsPacket=1
12:50:28 21186 [Router] Received routing from=0xc460f074, id=0x6e2b886, portnum=67, payloadlen=20
12:50:28 21186 [Router] Routing sniffing (id=0x06e2b886 Fr0x74 To0xff, WantAck0, HopLim3 Ch0x0 Portnum=67 rxtime=1652964628 rxSNR=11.25)
12:50:28 21186 [Router] Rebroadcasting received floodmsg to neighbors (id=0x06e2b886 Fr0x74 To0xff, WantAck0, HopLim3 Ch0x0 Portnum=67 rxtime=1652964628 rxSNR=11.25)
12:50:28 21186 [Router] Should encrypt MQTT?: 1
12:50:28 21186 [Router] Installing AES256 key!
12:50:28 21186 [Router] enqueuing for send (id=0x06e2b886 Fr0x74 To0xff, WantAck0, HopLim2 Ch0x2 encrypted rxtime=1652964628 rxSNR=11.25)
12:50:28 21186 [Router] txGood=89,rxGood=46,rxBad=0
12:50:28 21186 [Router] FIXME-update-db Sniffing packet
12:50:28 21186 [Router] Delivering rx packet (id=0x06e2b886 Fr0x74 To0xff, WantAck0, HopLim3 Ch0x0 Portnum=67 rxtime=1652964628 rxSNR=11.25)
12:50:28 21186 [Router] Exit state: LS
12:50:28 21186 [Router] Allowing GPS lock
12:50:28 21186 [Router] Setting bluetooth enable=1
Pre BT: 203948 heap size
12:50:28 21186 [Router] Starting bluetooth
yes, that firmware is not to put back sleep mode, it is to bring back ‘no GPS’ devices to life. The sleeping is the next thing i am tackling, but i want to finish one thing first 
no GPS seems to be gone. I have tried it several times, however I get following when I boot
??:??:?? 0 Hoping that NMEA might work
??:??:?? 0 WANT GPS=1
??:??:?? 2 WARNING: Unable to set UART.
and then one second later GPS seems to work:
??:??:?? 3 [GPS] NMEA GPS time 2022-05-19 20:17:19
00:00:03 3 [GPS] Upgrading time to RTC 1652991439 secs (quality 3)
20:17:19 3 [GPS] Read RTC time as 1652991439 (cur millis 3630) quality=3
that warning is really only a warning. it’s part of the init code and may fail.
I think the red light blinks when the deevicee is acquiring satellites. Ive observeed my T (1.2.46) updating position and altitudee data with no reed light blinking on the GPS sideee of the board.
And yes my keyboard has a sticky e.lol
Iˋve confirmeed the correct operation through analyis of the packets, so thee system is updating my pposution, (from the TBeam ratheer than from the phone GPS)
While on thee subjeect of altitudee, Ive noticeeed that the NEO chip on my TBeam does not seem to compensate for the geoid. I.E I have useed the T at locations with known altitudes and I am obseving discrepances between it and deevicees operating geoid correction