Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No visual or audio clues for incoming call #209

Closed
Grunthos opened this issue Jun 25, 2018 · 28 comments
Closed

No visual or audio clues for incoming call #209

Grunthos opened this issue Jun 25, 2018 · 28 comments

Comments

@Grunthos
Copy link

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.

@mario
Copy link
Contributor

mario commented Jun 25, 2018 via email

@Grunthos
Copy link
Author

Grunthos commented Jun 25, 2018

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

@mario
Copy link
Contributor

mario commented Jun 25, 2018 via email

@Grunthos
Copy link
Author

Play services 12.6.85 on both.

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

@mario
Copy link
Contributor

mario commented Jun 25, 2018 via email

@Grunthos
Copy link
Author

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

@mario
Copy link
Contributor

mario commented Jun 25, 2018 via email

@Grunthos
Copy link
Author

Grunthos commented Jun 25, 2018

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

NVM, I think I found it

@Grunthos
Copy link
Author

Youshould receive emails. Let me know.

@Grunthos
Copy link
Author

Grunthos commented Jun 25, 2018

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

@mario
Copy link
Contributor

mario commented Jun 25, 2018 via email

@Grunthos
Copy link
Author

NC server, since I assume phones speak via server

@mario
Copy link
Contributor

mario commented Jun 25, 2018 via email

@jookk
Copy link

jookk commented Jun 25, 2018

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

@ArtJames
Copy link

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)

@mario
Copy link
Contributor

mario commented Jun 25, 2018

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

@jookk
Copy link

jookk commented Jun 25, 2018

So, no notification on receiving new msg?

@mario
Copy link
Contributor

mario commented Jun 25, 2018

No @jook. See: nextcloud/spreed#875

@mario
Copy link
Contributor

mario commented Jun 25, 2018

@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 mario closed this as completed Jun 25, 2018
@Grunthos
Copy link
Author

@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?

@mario
Copy link
Contributor

mario commented Jun 26, 2018

I answered via email @Grunthos since you mailed me.

@mario
Copy link
Contributor

mario commented Jun 26, 2018

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.

@Pistos
Copy link

Pistos commented Aug 5, 2018

@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?

@makuser
Copy link

makuser commented Sep 4, 2018

@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?

@n-e-y-s
Copy link

n-e-y-s commented Apr 5, 2019

@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.

@mario
Copy link
Contributor

mario commented Apr 5, 2019

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

@mario
Copy link
Contributor

mario commented Apr 5, 2019

@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 #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.

@Pistos
Copy link

Pistos commented Apr 11, 2019

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

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants