Talk-android: No visual or audio clues for incoming call

Created on 25 Jun 2018  Â·  28Comments  Â·  Source: nextcloud/talk-android

I may misunderstand the way things should work, but I call one of my contacts who has nextcloud talk app and they get no indication of any kind that a call is requested. I have set us both up with ring & message sounds. Also, text messages arrive but no sound plays.

If we both call each other then the call is connected and we can speak.

A visual and audio signal would be great.

Most helpful comment

@mario (Honest question) Are you saying that Nextcloud Talk can't provide native notifications without going through Google-controlled servers? If so: Is that just how Android is?

All 28 comments

What version od the app, what version od Talk app on the server, do you
have Notifications app installer on the server, Google Play on the phone?

On Mon, 25 Jun 2018 at 06:00, Grunthos notifications@github.com wrote:

I may misunderstand the way things should work, but I call one of my
contacts who has nextcloud talk app and they get no indication of any kind
that a call is requested. I have set us both up with ring & message sounds.
Also, text messages arrive but no sound plays.

If we both call each other then the call is connected and we can speak.

A visual and audio signal would be great.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/nextcloud/talk-android/issues/209, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAWsiE5n17O1GW_PLfdzytf_QzUgOvWks5uAGBKgaJpZM4U1epV
.

Sorry, I should have posted these!

App: 2.1.0beta 2 (and was at most recent non-beta before that)
NC: 13.0.4
Notifications App: 2.1.2 (enabled)
Google Play: Installed. Not sure version, app does not seem to ask for upgrade .

Edit: found play services version: 12.6.85

Google play services?

Also what phone & android version?

On Mon, 25 Jun 2018 at 09:07, Grunthos notifications@github.com wrote:

Sorry, I should have posted these!

App: 2.1.0beta 2 (and was at most recent non-beta before that)
NC: 13.0.4
Notifications App: 2.1.2 (enabled)

—
You are receiving this because you commented.

Reply to this email directly, view it on GitHub
https://github.com/nextcloud/talk-android/issues/209#issuecomment-399853443,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAWsvJsd6Q_v4sL4LJaWa4twv2ze0ulks5uAIw5gaJpZM4U1epV
.

Play services 12.6.85 on both.

Phone 1: Android 5.0 (Zenfone 5)
Phone 2: Android: 7.0 (Galaxy S7)

Sounds strange. I have S7 and it works perfectly.

Hm hm. Enabled notifications for Talk and disabled battery optimisations,
just in case?

On Mon, 25 Jun 2018 at 09:19, Grunthos notifications@github.com wrote:

Play services 12.6.85 on both.

Phone 1: Android 5.0 (Zenfone 5)
Phone 2: Android: 7.0 (Galaxy S7)

—
You are receiving this because you commented.

Reply to this email directly, view it on GitHub
https://github.com/nextcloud/talk-android/issues/209#issuecomment-399855996,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAWstq1DbNrZmipXQbiQYbh7Hzak0lkks5uAI7_gaJpZM4U1epV
.

Yes, on Asus, can't find on the Samsung. Still no joy.

Send me two test accounts on [email protected] and I can test later today.

On Mon, 25 Jun 2018 at 09:32, Grunthos notifications@github.com wrote:

Yes, on Asus, can't find on the Samsung. Still no joy.

—
You are receiving this because you commented.

Reply to this email directly, view it on GitHub
https://github.com/nextcloud/talk-android/issues/209#issuecomment-399859079,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAWstvXXrN09CAIb-yoVZjP4jKbJpvGks5uAJH5gaJpZM4U1epV
.

OK...is there a recommended means of sending accounts to external users?

NVM, I think I found it

Youshould receive emails. Let me know.

Ahhh...could be firewall? What ports are used? (anything more than 80/443?)

Firewall on mobile phones?

On Mon, 25 Jun 2018 at 11:21, Grunthos notifications@github.com wrote:

Ahhh...could be firewall? What ports are used?

—
You are receiving this because you commented.

Reply to this email directly, view it on GitHub
https://github.com/nextcloud/talk-android/issues/209#issuecomment-399887853,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAWsv3g4kip0DMmp68BoXxxaHzAPqChks5uAKuVgaJpZM4U1epV
.

NC server, since I assume phones speak via server

Notifications are related to Google servers. Anyway I will test if it works
once near a computer

On Mon, 25 Jun 2018 at 12:15, Grunthos notifications@github.com wrote:

NC server, since I assume phones speak via server

—
You are receiving this because you commented.

Reply to this email directly, view it on GitHub
https://github.com/nextcloud/talk-android/issues/209#issuecomment-399902660,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAWshzLpA1IT1Tf2_b13KeEzXBx_Lj_ks5uALg9gaJpZM4U1epV
.

I have no problem with call notification, but text msg's are not notified.

NC 13.04, Notifications 2.1.2, Coturn, Play Services 12.6.85, Android 5.1 (2 devices)

Tested phone to phone, phone to website
Voicecall: Working, including notifications
Textchat: Working, but without notifications
Videochat: App on both phones crash immediatly

Older versions 1.x work well. (Voice/Video-calls)

Text chat has notifications only if you're mentioned. Say "@jookk" or "@ArtJames". cc @ArtJames and @jookk

So, no notification on receiving new msg?

@Grunthos so I had a quick look. It seems like app tokens that are created as part of the login flow are not stored properly/at all and that is why push registration fails. Feel free to delete my accounts now.

(cc @rullzer anyone else complained about this?)

This is possibly a setup or a server (https://github.com/nextcloud/server) bug so you might look into that direction.

@mario Thanks for investigating. There was nothing in the logs from nextcloud that indicated an issue, and nothing in the app that indicated that regisdtration failed. So what I did was kill the app on my phone to (I assume) force it to register again. What I see is this:

<MY-ADDR> - <USER> [26/Jun/2018:10:10:32 +1000] "POST /ocs/v2.php/apps/notifications/api/v2/push?proxyServer=https://push-notifications.nextcloud.com&devicePublicKey=-----BEGIN<STUFF>END%20PUBLIC%20KEY-----%0A&pushTokenHash=<LONG HASH>&format=json HTTP/1.1" 400 112

The 400 response is probably the root of the problem. Also, using https://push-notifications.nextcloud.com (presumably a next cloud server) might be an issue since I assume I am not registered there.

Any suggestions?

I answered via email @Grunthos since you mailed me.

But to write it again here: The reason why you get 400 is what I mentioned earlier: your Nc server doesn't store app tokens for some reason.

@mario (Honest question) Are you saying that Nextcloud Talk can't provide native notifications without going through Google-controlled servers? If so: Is that just how Android is?

@mario you asked how @Grunthos installed it and he said Google Play store. I got it from F-Droid, so I assume and hope there are no Google services integrated in this version?

Notifications don't work there too, which is why I'm here. How does it work for those setups? And what about iOS or other platforms?

@mario Having the same problem. Using FDROID to install apps on my phone and neither google play nor google play services installed due to privacy concerns.

Is there really no google-free solution for getting notifications? There are apps out there being able to give notifications, e.g. Conversations.

Please stop spamming the issue :-/ There will be a partial solution for fdroid installs soon.

@makuser spamming it is because this issue has NOTHING to do with F-Droid and it was closed as a setup issue.

If you want F-Droid related thing, please take a look into https://github.com/nextcloud/talk-android/issues/257. Also, look at the latest reply there where I said exactly what you wanted to hear.

In the mean time, please take a look at Code of Conduct or I will be forced to take further actions since your wording is not adequate.

Edit: this was an answer to a comment that seems to have been removed (by Github itself?) in the mean time.

(for reference, here's the deleted comment: https://gist.github.com/Pistos/2420c65117ed9edc56df8c2ba3c53026 )

Personally, I think the aggression on both sides was unwarranted.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

jookk picture jookk  Â·  6Comments

mario picture mario  Â·  6Comments

mahibi picture mahibi  Â·  7Comments

nickvergessen picture nickvergessen  Â·  4Comments

neerro picture neerro  Â·  3Comments