cant get call notifications

hi
i cant get call notification since i bought watch .i tried several differnet settings but no luck.i hope i can fix this problem.thanks

Do you get any other notifications?

What kind of phone do you have? Android, or iOS?

i am getting all notiifcations but no phone call ones
i have android phone

If you force-stop Gadgetbridge and then restart it, are you sure that you've granted it every permission it requests when it starts?

i tried all this solutions.doesnt worked.

do i need install other app then gadgetbridgate on phone or android?or other maasage ui widget

No, if you have Gadgetbridge and you have installed Android Integration on Bangle.js you should be ok.

Make you sure you have installed Android Integration and not the deprecated Gadgetbridge app on your Bangle though.

Everything is set up correctly, but I still don't get phone notifications.

Please can you go into the Gadgetbridge app, tap top-left, then Debug, then tap incoming call.

This will 'fake' an incoming call from Gadgetbridge - I'd be interested to see if this works... If it does then the problem is on the phone, trying to get call info from Android, but if not it's on the watch

i tried this test many time since i bought watch but no call notification only sms massage works.and redmi is my second phone before i tried Samsung m21 ,with both i had same problem

The debug call notification triggers the watch response for me. Bangle.js Gadgetbridge nightly version 9b6fce566, espruino fw2v25.03, updated watch apps.

Edit: also works for me with latest Bangle.js Gadgetbridge nightly version cd7c7092b.

Edit2: I have a Sony Xperia xz2 compact running LineageOS 21

Yes, it also works great for me too.

So the fact it doesn't for you means that it'll be some configuration issue on your watch.

Please can you connect with the Web IDE on your PC, then on the left-hand side, paste in:

GB({"t":"call","cmd":"incoming","name":"Test","number":"01234567890"})

and then paste here what's written on the screen afterwards?

You could also enable logging in Gadgetbridge, click the incoming call button, and then paste up the part of the log from around the time that you pressed the button (make sure it doesn't contain any personal info) - but if we can track it down from what the Bangle says after manually pasting in the command, that would be easier

i have to connect watch to pc ?(pc has no bluetooth )

A chromium based browser, e.g. Brave browser, on your Android device should work as well. Make sure to disconnect the watch from the Gadgetbridge UI so it's available to the browser.

i wrote and phone call massage arrived to my watch ,massage on phone chrome browser is undefined
any app that i have to enable app to get notification for call on gadgetbrigde?

I'm not quite sure I understand. So just to be clear:

• Pasting GB({"t":"call","cmd":"incoming","name":"Test","number":"01234567890"}) via the Web IDE caused your watch to display an incoming call message?
  
• Tapping Debug then incoming call in Gadgetbridge did not display an incoming call message?
  
  

If that's the case, please can you enable logging in Gadgetbridge, click the incoming call button, and then paste up the part of the log from around the time that you pressed the button (make sure it doesn't contain any personal info)

'' Pasting GB({"t":"call","cmd":"incoming","name":"­Test","number":"01234567890"}) via the Web IDE caused your watch to display an incoming call message?
Tapping Debug then incoming call in Gadgetbridge did not display an incoming call message?''
yes
i hope i uploaded correct log

1 Attachment

• log bangle.txt

Thanks! Yes, that's perfect. So the issue is that instead of sending:

GB({"t":"call","cmd":"incoming","name":"­Test","number":"01234567890"})

Gadgetbridge is actually sending:

GB({"t":"call","cmd":"\u0131ncom\u0131ng","name":"Test","number":"Test"})

This is just all kinds of strange though - I just checked the Gadgetbridge source code and the code there looks ok. It gets the text incoming from an actual variable name in the CallSpec class, so it shouldn't be affected by translation. It's almost like your Gadgetbridge installation itself is corrupted.

Which version of Gadgetbridge are you using? Is it the one from the Play Store? Or F-Droid? Or did you build it yourself?

@Ganblejs have you seen anything like this before? I know we hit issues when using reflection with field names before (there was a step that removed them from the build) but I thought we fixed that.

Perhaps in the case of calls I just need to go back to hard-coding the names...

version is 0.80.0a.it is from playstore .

Don't think I have seen that really no. The closest that comes to mind is when umlauts and wrapString didn't play nice.

@user157973 are you from Turkey?
In Turkish the small i is missing the dot, if I remember correctly.
https://www.compart.com/unicode/U+0131

Could be a character set problem.

@BartS23 thanks for the heads-up! That could well be it.

@user157973 please can you confirm your phone's language? If I can change language on my phone here hopefully I can get a fix in to Gadgetbridge.

yes my problem fixed .my language on phone is turkish then changed to English it worked thanks alot .

Great! Did you restart your phone first, or you just changed the Language and that was it? What model is your phone?

I just changed my phone to Turkish and restarted Gadgetbridge and I can't get it to happen, but I'm pretty sure I know what the issue is now.

Turns out String.toUpper/Lowercase commands use the current locale by default, so for Turkish, "INCOMING" turns into "ıncomıng" (the 'i' is different!)

I've just pushed a change to Gadgetbridge, so the next 'Nightly' build should have it in. I'm not sure when I'll be able to push the next app store release as the Play Store is being really picky about this one, requiring me to record videos to explain why certain permissions are needed