Question from a new user - can y'all help answer?

[jtbutcher]

@M1BDK

TBEAM0.7 EU. 0.9.1 I have 2 TTGO’s the message is hard to read as the it spans the yellow and blue part of the LCD screen.

This sounds like it might be an issue with the lcd,

@M1BDK

Also the GPS location is not working just a ? in the circle.

Even outside my devices can take a long time to get a fix, I don’t know if this is a hardware or software issue.

@M1BDK

The battery level is reporting 155% and above.

@geeksville has mentioned here "progress bar", no gps, etc - #21 by geeksville
“The tbeam0.7 doesn’t have a software accessible pmu”

@M1BDK

Pitty the Bluetooth pairing needs a code. As then the app could just connected to the nearest device if there was a mesh in that location. So anyone with the app might get to send a msg even when not local to their own Lora device. Or use wifi on the esp32’s with all SSD’s and passwords the same.
…
My ideal mesh would be phone would txt out over normal network if available and also via lora. An acknowledge received via either method. Also a mesh packet system that would attempt to relay messages via lora or 4g or wifi as available, I know that routing while using 4g or wifi however these is out of scope for this project. But as long as the msg contained the sender telephone number and the receiving number. This could be done via a third party website interface. Also if this was achievable, Then solar powered static wifi stations could be located on hill tops to gain txt service to none service areas. For users to see it’s Wifi and log into it’s landing page to fill in fields with sender number, msg and recipient no. Then relay that info to other static stations until it finds a phone device that is connected via lora to forward to the txt msg service online. Or via a static station that is connected via wifi to the internet.

I can see merit in these things under different circumstances, but there are so many different things that everytime I delve into it I come up with more things that are related.
I think unsecured bluetooth might be an issue, I don’t know if it can be secured from people modifying the configuration if they have bluetooth access.
I think if @geeksville gets MQTT support embedded Proposal for global messaging support then all these ideas could be built on top of meshtastic really easily, but I think you are probably right about them been out of scope for the base project.
The only concern I would have with opening it up so much to users just connecting adhoc is exceeding the duty cycle on the frequencies in use.