It is a hard choice.
For different AP has different encoding charset.
For Android device, some product use UTF-8, some product use GBK, and etc. The most unbelievable thing occur to me is that one android phone support both UTF-8 and GBK when scan AP's SSID.
For IOS, the iphone use UTF-8 charset.
So we use UTF-8 as the default charset.
If it lead to configure fail all the time, please try another charset.
I think that we could hint the user: "We only support SSID is ASCII" if the configured AP's SSID isn't ASCII.
It is hard to decide, so I let ESPTOUCH v0.2.1 could be set the encoding charset.
For Android:
In ByteUtil.java: public static final String ESPTOUCH_ENCODING_CHARSET = "UTF-8";
For IOS:
In ESP_ByteUtil.h: #define ESPTOUCH_NSStringEncoding NSUTF8StringEncoding
I don't think it is a wise solution to let the user choose the encoding charset. What's your opinion?
Please write down your view, and let us make ESPTOUCH better for both of developers and users.
ESPTOUCH Discussion: SSID encoding related
Who is online
Users browsing this forum: No registered users and 2 guests
Login
Newbies Start Here
Are you new to ESP8266?
Unsure what to do?
Dunno where to start?
Start right here!
Latest SDK
Documentation
Complete listing of the official ESP8266 related documentation release by ESPRESSIF!
Must read here!
- All times are UTC+08:00
- Top
- Delete all board cookies
About Us
Espressif Systems is a fabless semiconductor company providing cutting-edge low power WiFi SoCs and wireless solutions for wireless communications and Internet of Things applications. We are the manufacturer of ESP8266EX.