0.9.7 is out to fix the reboot on GPS lock if on the new screen. Thanks everyone for the quick testing and fix!
1 Like
I can confirm the fix did work for my TBEAM v1.1 m8n.
2 Likes
I tested the 1.0.0 app, connected to board, got a message to update firmware 
and did just that. Worked like a charm. However, when I connected to my second(and 3rd) board I did not get the option. I tried updating to the second latest firmware via esp(which worked fine) but still didnât get an option to update firmware when I connected the app. I even tried connecting directly via OTG (which also works like a charm) but no go. And I know the firmware was 0.9.7 on both boards.
I think I read somwhere that the update button gets hidden after update, but when you connect to an older firmware it doesnât reapper. Anyone else having this problem?
1 Like
This is the first 1.1.0 series release. If a couple of yaâll brave alpha-testers could report basic âthis seems to workâ that would be helpful.
Changes since 1.0.0:
- @a-f-G-U-C fixed a bug where bogus GPS positions could be reported while GPS was doing initial lock. #397
- @r51n added AU/NZ frequency ranges
- Limit transmit power to 13 dBm in Japan (regulatory) #346
- We were incorrectly setting transmit power too low on sx1262 based radios. The default is now 22 dBm.
- The max power users could selection for sx127x radios was too low. You can now set up to 23 dBm, the default is still 17 dBm.
- Added portunino support. Which currently enables development/debugging as a linux app (no need to run on ESP32/NRF52). Eventually will allow a much smaller/more portable version of the software on NRF52 devices and support for directly running meshtastic (with SPI radio chips) on Raspberry Piish boards. Alas, this feature is super alpha still and still not ready for âusersâ.
4 Likes
this seems to work:
- fast meshing
- fast setup overall
- fast GPS fix
- correct position on the map
After a fresh firmware flash on all devices, and after setting the name and channel on all devices I send a message from all devices to the mesh. Some names are correct on the other nodes, some are â???â or âunknownâ or sometimes ânon readable stuffâ.
To update the names on all devices I reboot every device, one after another and wait for about 20 seconds in between.
Tomorrow I will check the range with my two sx1262 and will report if it increased. I can send messages from my apartment to my parentâs house in the next village. Well not to my parentâs house directly, but to a âhillâ about 500m away. maybe the extra 5dB will do the trick. Would be really nice setting up a relay on my parentâs house to connect with old friends from my hometown 
2 Likes
âAdded [portunino] supportâ
Does that refer to in the future running Meshtastic from a PI with something like this?
Yep! It does, or running any arduino code on a pi with no source code changes needed.
(Also it will allow me to port Meshtastic to work with the built-in Lora radio on Pinetab)
2 Likes
Android 7.0 on Huawei MediaPad M3, six tbeams four 6n and two M8N EU865, app 0.9.90.
Noit so good for me. All meshed quickly and present in app but did not pair with app. Tried forgetting devices and restarted BT from meshtastic app. All gave error failed to pair in app. Went back to BT settings menu and all refused with error pairing failed - incorrect key or device not configured correctly. Reported bug.
1 Like
One single Tbeam hardware v1.0. Flashed to 1.1.0. The (re)setup felt much quicker and smooth. GPS works, lock after some 5m-10m multiple sats. Rejoined mesh ok. Sending messages to different firmware version Lora32 board ok. Android APP version 1.0 on both clients.
Ran range tests this week will try a few locations tomorrow and see if the extra mWâs/Dbmâs make a difference.
2 Likes
Hi I downloaded the apk for 1.0.00 and that has worked much better. All paired and meshed and I can text them too. Two things I find difficult to understand. I once named a device rather than use its default. That name still exists and makes that device show up twice. Does this make sense? Also the devices seen on the report bug page - they keep changing and I rarely see all of them together. Is that correct behaviour.
2 Likes
Today I did some range test on my usual route. Unfortunately I could not see any difference with the extra 5dB. 
I got connection on my general waypoints where I got connection before the update, but could not cover those 500m behind a small âhillâ.
This isnât really meaningful, because we still need line of sight for reliable resultsâŚ
1 Like
Line of sight or something that the signal can reflect against. I am in an urban area with lots of concrete and high buildingsâŚMany dead areaâs (shadows) with zero signal but the unblocked locations show surprisingly high signals (60-80% at 1km) while Iâm using an omnidirectional on the receiver. Got a directional antenna in the mail, waiting for customs to release it.
2 Likes
Hi On more checking the device does not appear twice - my error. But it has kept a name I called it from many versions ago of both the device and the app - how do I delete it? I thought installing a new version would overwrite everything.
In this case I would set the name to something random wait 20s and rename it to what it should be.
Send a message to the mesh and if the name is still not updated, then restart the device and it will anounce the new name to the mesh.
Hope that helps.
Name change announcements (node db updates) are only sent rarely. Iâll have to check but I think worst case time is 1hr.
Thanks for both your comments. Renaming the device works - a few minutes for the device new name as seen on the other devices. Over a longer time to change the name on the map. Strangely I can change the name but I cannot leave it blank - it justs adds the name back. So I cannot default to the device identity (as now seen on all the devices). Also in the top LH corner of message I now see a U when I send the message.
1 Like
1.1.0 of the android app is ready for alpha tester group members.
- @Bussemann added Norsk translation!
- @retrodime added Romanian translation!
- @isinglass Improved generation of short usernames
- @KenVanHoeylandt cleaned up some of the service code
- @comgram added Korean translation
- Fix a couple of rare autobugs.
I think my username patch should probably always include the first letter of the longname if it starts with a vowel. Iâll submit an updated patch soon when I have time.
When I tested my patch, I uninstalled the official beta meshtastic app to install my own build. The fact that one canât have the official app and a custom build side by side on the same device is â as was mentioned in another thread recently â is inconvenient. When I removed my custom build and re-installed the official build, I got the current release version. It still says âyouâre a beta tester for this app. future updates will include beta versionsâ, but it reports version 0.9.90 and doesnât behave like i would expect with respect to my patch.
I spent a little time trying to see if make android think my custom build was a different app, but it looks like android studio makes that hard to do. It looked like Iâd probably have to rename an entire directory structure, and probably also edit a bunch of project files. Anybody know a kludge to workaround this situation?
1 Like
Derp
I just realized this was regarding the Android app. I saw the v1.1.0 of the firmware and got them mixed up! Sorry about that
It would be great to have a list of all the things to confirm for this kind of validation, and Iâm probably too late to know what is going to be useful, but for what itâs worth!
- loaded onto a Heltec Lora v2 / ESP32 module (with the plastic case) - firmware is firmware-heltec-US-1.1.0.bin
- Some trouble with the phone app (why does it demand access to Location in the phone at all times, and you need Location turned on to see nodes and attach?). But got it working and connected just fine to this Heltec node by Bluetooth.
- GPS is working on v1.1.0! With a GT-U7 / GoouuuTech module [is that a u-blox knockoff?]
I was unable to get anything but âNo Satsâ on the display with v1.0.0 of the code
This GPS unit is nice since it has USB so I can troubleshoot easier, and if I power the GPS module by USB, it will power the Heltec module and I can read the GPS information on the computer at the same time.
[Where are instructions for hooking up GPS modules, anyway? fortunately I found geeksvilleâs mention of Pins 36 and 37 for the Heltec module, in a post about a different module] - One boot-up of this v1.1.0-loaded Heltec module did not seem to find my other v1.0.0 Heltec node. But, rebooted and it joined the mesh network just fine.
- Sent text message through the app and it went through the 2-node mesh after a few seconds (It felt longer than normal, but I donât know what is typical yet.). Second time I counted about 10 seconds to see the cloud-checkmark icon in the app.
Seems to be running well! Iâm just happy to get the GPS module working. I have a couple other GPS modules (one is BN-880), Iâll see if I can get to work.
-Edit: the BN-880 unit populated GPS coordinates too! And both work indoors so I can keep testing without too much trouble. Both seem to get around 10 satellites too.
1 Like
This is a requirement from Android. Android will not give apps access to bluetooth unless the app also has location permissions (because the ability to see blueooth devices can slightly/implicitly leak location data to apps if the app wanted to use those devices as markers).
re: instructions for hooking up GPS
Alas there are none because this project was mostly focused on using âoff the shelfâ modules. It would be super appreciated if you could send in a PR adding something like docs/hardware/gps-modules.md?