Open GoogleCodeExporter opened 9 years ago
I think this does not work in aosp either, so its an enhancement.
This certainly is some encoding issue, so someone with some background may look
into that. Most certainly there is a mismatch about the scanned name and how it
is saved into /data/misc/wifi/wpa_supplicant.conf by the framework.
If someone wants to do that, post on the mailinglist so we can provide further
help.
Original comment by polyth...@gmail.com
on 18 Sep 2010 at 2:40
Is this working in 6.3-rc2?
Original comment by trmfrei...@gmail.com
on 7 Feb 2011 at 3:36
This is not working on 6.3-rc5.
Initial name: çlústers
What appeared: [some foreign char, perhaps chinese]sters
Will try to check what wpa_supplicant saved later.
Original comment by trmfrei...@gmail.com
on 10 Feb 2011 at 10:36
This is what is present in wpa_supplicant:
ssid="笺sters"
Original comment by trmfrei...@gmail.com
on 12 Feb 2011 at 12:32
It was the same that appeared on the screen.
Original comment by trmfrei...@gmail.com
on 12 Feb 2011 at 1:33
wpa_supplicant doesn't seem to be able to parse non-ascii characters.
But from what I get in several forums thruought the web the problem concernes
the wpa_supplicant, not android itself.
Quoting:
"
# ssid: SSID (mandatory); either as an ASCII string with double quotation or
# as hex string; network name
"
from:
http://user.uni-frankfurt.de/~testrad/wpa_supplicant/wpa_supplicant.conf.example
s
Original comment by migaxmoi...@gmail.com
on 12 Feb 2011 at 2:01
Ok, I guess you can put the hex string...
So all you need is a converter. Maybe the input box for the ssid could see if
there were some non ascii chars and convert them right away?
Original comment by migaxmoi...@gmail.com
on 12 Feb 2011 at 2:04
Original issue reported on code.google.com by
garth...@gmail.com
on 8 Sep 2010 at 5:06