Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Junk characters showing in AP name & HTML page #26

Open
bigbrodude6119 opened this issue Jul 13, 2023 · 3 comments · May be fixed by #53
Open

Junk characters showing in AP name & HTML page #26

bigbrodude6119 opened this issue Jul 13, 2023 · 3 comments · May be fixed by #53
Labels
bug Something isn't working help wanted Extra attention is needed

Comments

@bigbrodude6119
Copy link
Owner

Sometimes when the portal starts the UART connection sends "junk" characters that appear at the end of the AP name and/or in the HTML page. I found that this happens more often when starting the portal quickly after opening the app.

I'm not sure if its some sort of noise/interference happening during the communication between the flipper & esp32.

@bigbrodude6119 bigbrodude6119 added bug Something isn't working help wanted Extra attention is needed labels Jul 13, 2023
@leedave
Copy link

leedave commented Jul 24, 2023

Maybe too much RAM reserved and getting random characters written by other processes

@leedave
Copy link

leedave commented Jul 25, 2023

I would recommend switching to FlipperFormat for the AP name configuration. It would change the format of the file but reading out data is pretty easy after that, you always get a key -> value pair out of each line and no random characters.
Let me know if you need help with it.

@manu0466 manu0466 linked a pull request Jul 29, 2023 that will close this issue
@aaron-sc
Copy link

aaron-sc commented Dec 24, 2023

The issue is still happening!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working help wanted Extra attention is needed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants