Gadgetbridge: Messages are displayed in Chinese

Created on 30 Mar 2017 · 68Comments · Source: Freeyourgadget/Gadgetbridge

Before opening an issue please confirm the following:

[X] I have read the wiki, and I didn't find a solution to my problem / an answer to my question.
[X] I have searched the issues, and I didn't find a solution to my problem / an answer to my question.

Your issue is:

I configured the device with the application, but all messages are displayed in Chinese.

Your wearable device is:

Makibes Aerobic A1

Motorola X 2nd generation Android 6.0

Your Gadgetbridge version is:

0.18.3

New issues about already solved/documented topics could be closed without further comments. Same for too generic or incomplete reports.

device hplus potentially fixed / needs confirmation

Source

jmlopezo

All 68 comments

Can you provide a log file including the display of a message?
What is the language setting of your phone?
Can you attach a photo of the Makibes with a message in Chinese, and also provide us the message should be be presented?

jpbarraca on 31 Mar 2017

Can you tell me where I'm looking for the log file?

The mobile is setting in Spanish.

photo_2017-03-31_08-38-11

Thanks.

jmlopezo on 31 Mar 2017

In the configurations menu, the last item. Enable it, reconnect the device to gadgetbridge and trigger some messages.

Use messages with and without accented characters.

Btw.. Which android application do you use to communicate with the gadget?

jpbarraca on 31 Mar 2017

Enable debug mode ... but where is the log record?

I just connect with gadgetbridge

jmlopezo on 31 Mar 2017

Same happens with Zeblaze Plus - Both caller ID and SMS are displayed only in Chinese.
This doesn't happen with Hplus Watch app (which by the way I don't use)

kowalski215 on 31 Mar 2017

Please see this: https://github.com/Freeyourgadget/Gadgetbridge/wiki/Log-Files

jpbarraca on 31 Mar 2017

I attached the log, sorry for the delay, can not before.
[gadgetbridge-2017-03-31.1.log.zip]
redacted

[gadgetbridge.zip]
redacted

jmlopezo on 31 Mar 2017

Can you try this branch: https://github.com/jpbarraca/Gadgetbridge/tree/fix-630

If you wish, the corresponding APK is attached. If you are using GB from F-Droid or other market, when you install apk you will probably loose your data.

gb-debug-630.apk.zip

jpbarraca on 1 Apr 2017

Now it does not come out in Chinese, but it is only possible to see the sender, there are many spaces between characters.

jmlopezo on 3 Apr 2017

Can you provide an BT logfile of the original app?

jpbarraca on 4 Apr 2017

Of course, where is the log file?

jmlopezo on 4 Apr 2017

Go to the developer options in the Android Settings app, and enable the HCI log.
The file will be in the root of the sdcard.
If possible, try to present some known text as a notification. In the GB debug menu you can trigger notifications.

This may help you:
https://play.google.com/store/apps/details?id=com.android_rsap.logger
http://www.fte.com/webhelp/sodera/Content/Documentation/WhitePapers/BPA600/Encryption/GettingAndroidLinkKey/RetrievingHCIlog.htm

jpbarraca on 4 Apr 2017

This is?

btsnoop_hci.zip

jmlopezo on 4 Apr 2017

Didn't have a look at the dump yet, but this looks a bit like utf-16 encoded characters. FWIW, UTF-16 is Java's internal String encoding.

cpfeiffer on 5 Apr 2017

My problem with these devices is that the result in a Zeband is totally different. Only the first char of the message is presented.

@jmlopezo The log was created with the original application?

jpbarraca on 5 Apr 2017

There was a commit that potentially fixed this issue. Can you test the latest version from the GB master repository?

jpbarraca on 18 Apr 2017

Thanks for your help, but I gifted the smartwatch to an iphone user ... there it works without problems.

Greetings.

jmlopezo on 18 Apr 2017

log_bt.zip
in this log you have test notification from hplus watch app and gadgetbridge
check this attach

dawiddudek on 20 Apr 2017

👍1

I will analyse the log and see if there is something new. Thanks.
I made a commit that should have fixed this but it was made after 0.8.5. Please wait a few days for the next version.

jpbarraca on 21 Apr 2017

Thanks for reply and I wait for New version

21.04.2017 19:01 "João Paulo Barraca" notifications@github.com napisał(a):

I will analyse the log and see if there is something new. Thanks.
I made a commit that should have fixed this but it was made after 0.8.5.
Please wait a few days for the next version.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Freeyourgadget/Gadgetbridge/issues/630#issuecomment-296246913,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AahFj1UCzlNm_SVS7jn14KJTTaXeJ_knks5ryODLgaJpZM4MudMZ
.

dawiddudek on 23 Apr 2017

Zeband I still receive notification in Chinese with version 1.85

Logh0nox on 28 Apr 2017

btsnoop_hci_20170428141717.zip

Logh0nox on 28 Apr 2017

@1140921 Can you provide a log using the official app?

jpbarraca on 28 Apr 2017

@jpbarraca you mean hplus watch?
can you tell me how to get log file plase?

Logh0nox on 28 Apr 2017

@1140921
That is because the fix is Gadgetbridge 0.19.1 and not in your imaginary 1.85 version.
Please read the Changelog before posting

ashimokawa on 28 Apr 2017

Where I can find 0.19.1? In f-droid i have 0.18.5

28.04.2017 19:42 "Andreas Shimokawa" notifications@github.com napisał(a):

@1140921 https://github.com/1140921
That is because the fix is Gadgetbridge 0.19.1 and not in your imaginary
1.85 version.
Please read the Changelog before posting

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Freeyourgadget/Gadgetbridge/issues/630#issuecomment-298062027,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AahFj-KkXqTIdyeD4zNLVyhqKnnowr3vks5r0iUbgaJpZM4MudMZ
.

dawiddudek on 28 Apr 2017

@dawiddudek version 0.19.1 was tagged yesterday and will be released by fdroid hopefully soon. (we have no influence on fdroid release process)

danielegobbetti on 28 Apr 2017

@ashimokawa ok my bad I'm sorry
So I build my self the apk from version 1.9.1 and stil get Chinese messages when using debug and message to my self

Logh0nox on 28 Apr 2017

@Logh0nox
@dawiddudek
0.19.1 is now in f-droid, please test and report

ashimokawa on 1 May 2017

@ashimokawa I downloaded from f-droid using the debug to send message I still receive characters in Chinese

Logh0nox on 1 May 2017

EDIT:
hci_log.zip

I tested, i have that same problem. And i can't send debug notification to
oryginal aplication. When I go back to home download hci log and attach.

01.05.2017 15:53 "Andreas Shimokawa" notifications@github.com napisał(a):

@Logh0nox https://github.com/Logh0nox
@dawiddudek https://github.com/dawiddudek
0.19.1 is now in f-droid, please test and report

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Freeyourgadget/Gadgetbridge/issues/630#issuecomment-298336895,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AahFjzuwv3fKSlAEj2YTO_HjuTt_MWNlks5r1ePIgaJpZM4MudMZ
.

dawiddudek on 1 May 2017

@dawiddudek
The string "Test powiadomienT wiadomienie z Gad" appears in Chinese characters?
When you get home, please provide the dump of the original HPLUS app.
Is the device a Zeband or Zeband Plus?

jpbarraca on 2 May 2017

hci_log.zip
I have a problem with debug in GB. When i connect with orginal app I can't send any notification. When i push "create new notification" in orginal app doesn't reackt.
When i connect to GB and send new notification zeband show this info in chainise.

I have a ZeBand Plus. in zip file You have hci log and GB log. (first row in log has a orginal app, second is GB and send sms from other phone to my number)

dawiddudek on 2 May 2017

Thanks. I see that the Zeband Plus is sending a few different messages.
I will need some time to fully analyse the logs.

jpbarraca on 4 May 2017

👍1

Easy, i Will wait for solution a problem :-)

04.05.2017 14:35 "João Paulo Barraca" notifications@github.com napisał(a):

Thanks. I see that the Zeband Plus is sending a few different messages.
I will need some time to fully analyse the logs.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Freeyourgadget/Gadgetbridge/issues/630#issuecomment-299172418,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AahFjzj58E2NrVTDd9ZkBTHzJOejOSpmks5r2cYvgaJpZM4MudMZ
.

dawiddudek on 4 May 2017

AFAIU this should be fixed in 0.19.2 (available in f-droid) -- can check if this works for you now?

cpfeiffer on 15 May 2017

Hi.
Same issue with the Zeband Plus. Chinese characters are displayed on the watch. Running apk 0.19.2

FerryDaBoss on 22 May 2017

all characters as displayed in Chinese? Can you provide a log?

jpbarraca on 22 May 2017

gadgetbridge-2017-05-22.1.log.zip

Please find attached the log file. It`s not that straight forward. If I send the text: "apple" from the debugger, I get only Chinese characters, but if I send: "Apple" (with upper case A) I get the first letter A on the watch, and after that only chinese.

FerryDaBoss on 22 May 2017

Update:

I`ve sent from the debugger: "qwertyuiopasdfghjklzxcvbnm" and received:

img_20170522_222234

Then I`ve sent the same but all with upper case: "QWERTYUIOPASDFGHJKLZXCVBNM" and got:

img_20170522_222407

FerryDaBoss on 22 May 2017

There was a bug when storing the type of encoding required for the Zeband Plus (and others). Can you try this apk built from the current master?

app-debug.apk.zip

jpbarraca on 23 May 2017

Great! It's working with this version. All the characters are displayed correctly. Minor visual notice: too big spacing between the characters.
img_20170523_085936

FerryDaBoss on 23 May 2017

That is actually a bug... I will look at it later today. Can you provide the log file?

jpbarraca on 23 May 2017

Here you go:

gadgetbridge.zip

FerryDaBoss on 23 May 2017

That is actually a bug... I will look at it later today. Can you provide the log file with gb and the original app?

jpbarraca on 23 May 2017

Ive sent you the log from the gb, but for the life of me, I cant get to generate a log from the official app.

FerryDaBoss on 24 May 2017

Gadgetbridge 0.19.3 is out - but due to a bug in the f-droid android app it can't be updated.
The apk is here:

https://f-droid.org/repo/nodomain.freeyourgadget.gadgetbridge_96.apk

ashimokawa on 16 Jul 2017

@ashimokawa the "bug" being the index not updated for ~3 days again.

IzzySoft on 18 Jul 2017

No the bug is that the index is broken for many apps now, not even old versions can be installed.
New f-droid users have no way of downloading Gadgetbridge through the f-droid app at all!

ashimokawa on 18 Jul 2017

@ashimokawa have you tried with one of the "new-design-betas"? I've got an idea which bug might be behind that if it works with those (which is one of the reasons my repo doesn't run on the latest version of fdroidserver ← pointer/reminder for you-know-what-I-mean :wink:).

IzzySoft on 18 Jul 2017

@IzzySoft
Hmm. I just tried an old version of f-droid (the one that downloads from their site) and Gadgetbridge actually showed up, latest and previous versions.
Then I upgraded again and it broke again.

ashimokawa on 18 Jul 2017

@ashimokawa Believe it or not, that makes sense. I had the other bug in mind (lastest fdroidserver allows for multiple copies of the same version of an app to co-exist under certain circumstances – which breaks the index for older versions of the client) – but thinking closer, can't be that, which you proved. The other one are some "instabilities" with the latest clients – which seems to be what hits here. Now guess why their homepage doesn't link to one of those "latest versions", but to an older (stable) client version instead.

Not sure what exactly is wrong with the latest client (I'm not involved with that), and I like the old look-and-feel better anyway. So advice would be to stick with the stables – and you will see the new GB and can update it :stuck_out_tongue_winking_eye:

IzzySoft on 18 Jul 2017

Did you search their issue tracker?
https://gitlab.com/fdroid/fdroiddata/issues/

ildar on 18 Jul 2017

Emm
https://gitlab.com/fdroid/fdroidclient/issues

ildar on 18 Jul 2017

@ildar I found no related bug, but know from several sources that the latest versions (those with the new design) are still a bit flaky. I won't file a bug as I'm not affected; I rather stay with the "old-style version" as long as possible – unless some new version offers back that style. I'm not a fan of that "fancy tile stuff".

IzzySoft on 18 Jul 2017

@Izzy , could you please check with 1.0-alpha client and then I'll start
bugging f-droid guys?
I see the 0.19.3 in F-Droid newer client.

ildar on 19 Jul 2017

Using the new version (0.19.3) Chinese characters are still showing up when message contains umlauts (äöü). Message is in English up to the first umlaut than switches back to Chinese characters

TT1972 on 19 Jul 2017

@ildar No, I won't install the alpha (I strongly dislike the new layout, and much prefer the older). Today it turned up in the older client as well – so if you say it is available with the newer, that part of the issue is gone :wink:

IzzySoft on 19 Jul 2017

@TT1972
Ow, it seems it interprets the utf8 byte sequence as GB encoding. And I think umlauts are not supported by the font. You can enable transliteration as a work around for now. It will use ae oe and ue in your case.

@IzzySoft
I have the latest alpha, and it seems to me that the problem might simply be that I run by own debug build of Gadgetbridge, maybe that triggers a bug and makes all versions disappear. Previous f-droid versions always showed "from unknown source".
I will check on someone else's phone later - with no Gadgetbridge installed at all.

ashimokawa on 19 Jul 2017

👍1

Some characters are not supported by the font. We work around some known cases and transliteration will also help.

jpbarraca on 19 Jul 2017

@jpbarraca
If I understand @TT1972 correctly the first umlaut causes all following characters to be chinese

ashimokawa on 19 Jul 2017

With the latest version, äöü are displayed correctly in a Zeband. Don't know about a Zeband Plus as I do not own the hardware.

However, there is a transliteration map that is always applied to circumvent characters that are not at standard positions (those are included). Maybe that map is causing problems for Unicode enabled devices as it was designed for GB2312 devices.

Can you please try this version, which only applies the map to GB2312 devices?
app-debug.apk.zip

jpbarraca on 19 Jul 2017

@jpbarraca
Offtopic, I think we need a wiki page of the various HPlus devices, if I wanted one for testing, I wouldn't know what to buy..

ashimokawa on 19 Jul 2017

They are mostly the same, with a different ~~~shell~~~ enclosure and display and minor protocol variations. There are basically two families of devices: the ones supporting Unicode characters, and the ones only supporting GB2312.

I will add this information to the Wiki

jpbarraca on 19 Jul 2017

@IzzySoft
@ildar
still offtopic but I confirm that even in latest fdroid 1.0-alpha Gadgetbridge including icon and all versions is properly displayed if there is no self-compiled Gadgetbridge installed. If it is, then there is no icon and no versions displayed

ashimokawa on 19 Jul 2017

@ashimokawa Educated guess: signature check ("I cannot install this anyway, so no reason to show it and wake expectations"). You could see whether there's some related setting (like "ignore signature check", or "show X even if Y").

IzzySoft on 19 Jul 2017

@jpbarraca
With this version the umlauts are diplayed
img_20170720_113143