Call only rings 1.5 times, then it goes to VM

Ah ok. I have a Pebble 2 SE and was thinking that maybe that was involved with the issue…but the issue still happens for me when i have it turned off.

Was just curious of that could be a common factor…but it appears not, since you do not have a smart watch…must be something else. Maybe with Android 9 somehow.

I am having this issue happen now on my new Pixel 3.
Same contact most frequent.
I had thought before it may have my Pebble watch and its software…but I no longer use that but instead a Samsung Galaxy Watch which is much more up to date.

It seem to be happening when the phone is on wifi. (I am not away from Wifi that often or long enough to test if this happens when only on cell.)

Contact called me, I saw it notify my watch but was only for a second, then gone, just like before when i first posted about this. I “woke” the phone, pulled up an app or 2. Then locked the screen. within a min or so, he called back, and it did the same thing. So it does not appear to be a Doze or Deep sleep issue. I had previously tried the MacroDroid thing that is for the Doze issue, and it had no effect.

Perhaps the next logical step would be for a RW network engineer to look into the call server for my line at the incoming calls this is happing to and maybe gain some insight? A assume i need to create a ticket for that to happen.

Edit: I am going to block the UDP Call Setup port via my Routers Firewall, which then forces Calls to be Cell only. Will try this for a week or 2. See if the issue persists.

So. It seems that this issue IS related to wifi calling setup.
I have 7 days of no issues by blocking the UDP port in my router.
I enabled it again yesterday, and 2x now, this issue has happened.

Yup. Seems I have to choose between not having wifi calling while at home, and actually getting my calls to fully ring 100% of the time… or…have wifi calling, that has better audio quality, but have to call people back after they try calling me and it only rings for me 1.5 or 2x and I can’t answer it fast enough.

Edit: Note to Republic staff - you do not have the Pixel 3 added to the list of phones in the Ticket creation pages under “Select your phone”. Only the 1st and 2nd gen models are there.


I opened a ticket, giving them a list of the calls and times when this issue happend to me. Hoping they could look into the servers and see. I was told that they can only look at the last 72hr history though. I was told they found nothing out of the ordinary, and they sent me a new SIM card to see if that fixed the issue.

It at first seems to have fixed it, but the contact had only called me 1 or 2 times since I installed the new SIM Card. We both got got sick, then were very busy afterward with work related tasks, and did not talk to each other at all. But just now, he called me and the issue happened. I go to update my ticket, last I left it I told them I need a week or 2 before I would know and would get back to them, but ticket is now closed out and my reply will not go through.

O well. I guess it is just a Pixel thing…or something with him being on Cspire?

Just to update…this still happens.
It happens sometimes, but then not at all for weeks.

I just happened a couple times over the last few days.

I have been stuck home for a while, with phone in Airplane mode, wifi on.
So that force the call to be wifi only.
It still did it when certain person called me.

This topic came up in another thread where I mentioned some other things, link here:

So, it is happening again, alot with the 2 contacts that call me frequently.
The main contact, his work schedule had changed, so I am probably not gonna hear from him as much now moving forward.

Seems that being on wifi only(no cell), no mater the wifi network, 2.4g or 5g, has no effect on this issue.

The only thing i don’t think i have tried, is to stay on cell only, no wifi…which i could try for a bit i suppose, just have to remember to not do anything data intensive.

@southpaw could DM me info on that ADB hack thing your team has come up with that u mentioned at some point. I would like to see what that is about and the pros/cons of trying that. ( i have seen ADB hacks cause serious issues before). I may consider giving it a try.

i could try the MacroDroid Doze mode thing again, but the only one i see in there states its for Android 9.0 and lower…i have 10.

The reason I state “Doze Detect 9.0 and below - ver 0.9.6” is that I have only a Moto X4 to test on, if you would download it, determine the condition when it fails and provide screenshots of the logs, I would be glad to work with you to see if it something that I am able to fix.

1 Like

There’s no hack that “our team” has come up with. Let’s not take that route since you’re concerned about serious issues.

If you’ll continue to add to the symptom list, I’ll be compiling a list to present to the developers after I’ve had some time to replicate the issues myself.

That gave me the impression that you guy had come up with something?
I guess i interpreted that wrong.

Logs? i was not aware or know of logs saved by macrodroid.
Where/how does one view the logs of the macro?
Last i tried it, it just did nothing noticeable.
I see the code has mention of an RW notification…does this mean that the persistent RW app notification needs to be enabled?

Again, i do not think this has to do with doze mode, as the issue has happend when the phone is active, in use, even. But i can still give it a try anyway.

There exists on the internet a method using ADB to disable two doze mode functions. I’ve tried it personally and found that my phone does not move from a solid arc to an empty arc after an hour of not being used.

This has nothing to do with anything any Republic Wireless team is working on toward engineering a supported solution. I’m curious to know if the calls going to voicemail issue is also improved in this state. (I don’t get enough calls to notice and don’t have time at the moment to dedicate to testing it.) I thought it might be something you’d be interested to try, but I do not want to encourage such a trial given your predetermination that it is risky, because then, should anything at all happen to your phone, you may blame me.

Logs are available as ‘User Log’, in the Doze App :menu: but if the problem you are having occurs even when active (in a call, or screen displayed), then AFIK it is not a Doze problem

Ah. I see. Thanks for that clarification.

What is Doze app?

When a user has installed MacroDroid and is using the Doze Detect 9.0 and below - ver 0.9.6 that I have published (found in the Template section of the MD app by searching) you can then access the :menu: and select User Log … sorry if my short response caused additional confusion

i do not have a 3 line button like that.
There is one with dots infront of it, but that is to select macro category.
There is 3 dot menu, but I do not see a option to see log.

From your 1st screenshot, hit the top left back arrow 2 times, this will take you to where you should see the hamburger menu

O. It is on the main app screen, not in the macro it self screen.

Is there nothing supposed to be there, even if u run Test actions with the Macro?

edit: when i enable the RW persistent notification, then i do see entries in log…
so this is dependent on the RW notification.
But it just keeps just locking my screen.
Might be causing a System UI crash and recover.

The Macrodorid System log is saying Error: Notification content info was null.

Ok. so the macro and RW notification is enabled.
My mother just rang me. Phone has been sitting for a bit, i look over to it, it shows the incoming call screen, ring 1.5 times, then says called ended. and goes back to lock screen.

The RW notification is saying on cell, no acces to messages or voice mail…
However the phone is on wifi and gets VM and messages fines.
I unlock the phone and the RW notice goes back to connected.

This is getting annoying. I even have MacroDrod set to email me for missed calls, but since this issue does not trigger a missed call, it does not send an email. And there does not seem to be anyway to make a Google Home mini announce or ring at same time as phone…

Any suggestions?

I think my next test will to be just not use wifi and see if it happens on cell only.

I have set my router to block UDP port 5090.
That results in all calls being on cell, but i can still remain on my home wifi.
I am gonna see if this stops the issue at all.