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 SMS/MMS notifications, unable to pull logs #14

Open
LarksTonguesInAspic opened this issue Jun 8, 2019 · 8 comments
Open

No SMS/MMS notifications, unable to pull logs #14

LarksTonguesInAspic opened this issue Jun 8, 2019 · 8 comments

Comments

@LarksTonguesInAspic
Copy link

I do not receive notifications for SMS & MMS messages on dory. My phone is an Android One moto x4 running Android 9.0 and AsteroidOSSync 0.13. I receive all other notifications.

On another note, I tried to ssh into the watch to pull some logs for this post (using ceres and root @ the default IP address), but my connection keeps timing out. I took a pcap of the connection and it was all TCP Retransmissions.

I want to work on this though because I otherwise love AsteroidOS so far. :) Thanks for making!

@FlorentRevest
Copy link
Member

Hey,
I suspect the problem is not on the watch but on the phone.
If you feel like debugging the problem yourself, I suggest putting debugging messages in this function: https://github.com/AsteroidOS/AsteroidOSSync/blob/master/app/src/main/java/org/asteroidos/sync/services/NLService.java#L146
And investigate what's happening in this class: https://github.com/AsteroidOS/AsteroidOSSync/blob/master/app/src/main/java/org/asteroidos/sync/utils/NotificationParser.java
This is starting to be a bit of a spaghetti code but this is necessary to handle all the weird cases like yours :)
If you find a solution, a PR is welcome!

@LarksTonguesInAspic
Copy link
Author

Thanks so much for the reply, Florent! 😃 My carrier is a VoIP MVNO, and I had wondered if their proprietary software might be causing the issue; your suspicion that the issue is phone-side suggests as much. I'll keep looking into what I can do to resolve or work around the issue; if I come up with anything good, I'll definitely post it here!

@jrtberlin
Copy link
Member

I had wondered if their proprietary software might be causing the issue

Do they have their own messaging app? if yes can you share details on the app e.g. package name, version,...?

@LarksTonguesInAspic
Copy link
Author

The carrier is Republic Wireless; they require a proprietary app (called just Republic) installed on stock Android for a device to work with their services (it will not work on LineageOS for some reason; I have tried). They also offer an optional texting app called Republic Anywhere, but the issue seems agnostic to apps anyway; I've tried Android Messages (my default), Anywhere, QKSMS, and even Facebook Messenger.

I brought this up to their support, and they do not think the issue has to do with any of their software, but I noted that they did not seem familiar with AsteroidOS, either. 😏

@jrtberlin
Copy link
Member

jrtberlin commented Jun 9, 2019

Maybe this issue is with parsing grouped notifications or updated notifications as they are usually used by messaging apps instead of a "normal" notifications per message. If you need help debugging please let me know!

Probably a duplicate of AsteroidOS/AsteroidOSSync#35

@LarksTonguesInAspic
Copy link
Author

That would be great, thank you!

My skills are in Linux and networking; I really don't know much coding at all. How should I get to work on debugging this?

@jrtberlin
Copy link
Member

Let us move to the issue on AsteroidOSSync and close down this one, to keep it organized. Are you in the IRC?

@LarksTonguesInAspic
Copy link
Author

I don't believe so!

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

3 participants