• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help Droid Turbo not ringing when someone calls....help!

NikkiBett said:
Has anyone had the issue of your phone not doing anything when someone calls?? I've seen it with my own eyes: someone calling and my phone doing nothing. My phone is usually on vibrate because I have a 3 month old. Today is the second time it's happened, the first time was the first of the year. I just thought it was a bug with the new year. Any help would be greatly appreciated! This mommy is kinda freaking out
Click to expand...
 
Have you downloaded the new UPDATE to your phone.?It just came out a little while ago.I am hoping this is the fix for this problem. With tech support you'll get all kinds of answers. None work. Shut off the phone and turn it back on works most of the time. Last week mine would last a few hours and start missing calls. Power off/on and it worked for a few days. i downloaded the new patch and it seems to be working. good luck.
 
We have the same problem with the Droid Turbo not ringing and also not alerting you of a call. Any time we try a fix it only last for a few days.
 
Holding my breath. Haven't had an issue with calls going directly to voicemail since the update. Anyone else having good luck.??
 
well since the update I haven't had any missed calls .But Iam not sure about that. Seems that
I was surfing the net and maybe a call didn't come thru. Not sure,but it didn't show up in voice mail. Just cleared cache. Let's see what happens. But all in all ,so far so good. Anyone else missing calls since the update?
 
Great! I just got a Droid Turbo less than 3 weeks ago and just found I am having the same issue - just outside of the exchange period of 2 weeks.

How can this still be a problem?

1. I usually keep the ringer off, but missed calls should show up in the call log! They do not..
2. I do get a notification that VZW wants me to set up video voicemail. NO! I do not want that. I want to know WHO called before even checking voice mail.
3. I miss my Droid (yes, the original). If there was voice mail, the little green light blinked and the missed calls ALWAYS showed up in the call log. I RARELY had to reboot it.
4. As for the suggestion that I reboot the phone to "fix" this? I had inadvertently done that just a few hours before I noticed this problem.
5. Having to BUY a new phone (despite VZW telling me I have a free upgrade available) sucks when you're not planning on it and haven't had time to research new phones. (the Droid broke suddenly and unexpectedly).

SUGGESTION FOR VZW (I will pass this on to them as well): They said if I exchanged my new Turbo (within the 2 week period) I would be charged an additional $35 "because they can't sell it as new". Take some of those exchanged phones and let people try them out to see if they like them. If they do, bill them. If they don't, let them try another phone. Reading reviews is all well and good but until you actually experience the phone yourself, you cannot know what shortcomings will really affect you or if you'll like it.

Now I'm stuck with a 2-year contract (that I didn't have before 3 weeks ago) and a phone that won't even acknowledge missed calls.
 
I have this issue as well. I thought perhaps it was because my Bluetooth was connected, but in my pocket, that I was not hearing my phone ring. So I tested that theory.
I called the phone from my land line with the Bluetooth on and it did not ring but the Bluetooth was telling me I had an incoming call. Then I turned off the Bluetooth and called and the phone displayed incoming, but did not ring nor vibrate although it is set to do both. So while the call was being displayed I hit the vol up to ensure it was turned up, the volume indicated full up, and the phone began ringing and vibrating.
I then reconnected my Bluetooth, dialed in again and lo and behold, the phone rings aloud, vibrates, and the Bluetooth tells me I have a call incoming.
So now what remains to be seen is how long this will stick.

Verizon asked me to clear my cache partition, and I think I did so, prior to conducting this test.
I followed the prescribed steps but they don't quite jive.
I selected the recovery mode per the steps to scroll using vol down, and then it says to select recovery mode using vol up, but vol up simply scrolls in the other direction from vol down, and changes the mode.
So I had to punch the power button to select. From there it indicates "no command" so I have no idea what's happening. Then after waiting a while the phone powered up.
Did it clear the cache partition? Who knows?
But "whatever"!
for the moment incoming calls ring, vibrate, and tell me over Bluetooth.

As I said "we'll see how long this sticks".
Sounds superstitious, as opposed to a fix, but the outcome is thus far undeniable.
 
To Wipe Cache Partition on the Droid Turbo ...

My updated instructions using the Motorola website instructions ...

This will remove any temporary files that may be causing the problem, but will not delete your files or settings.
1. With the phone powered off, press the VOL DOWN KEY for 2-3 seconds then POWER key then release.
2. The device will display different BOOT OPTIONS
3. Use the VOL UP and DOWN Keys to SCROLL to Recovery mode and POWER Key to select
Tip: If the device reboots, you may have waited to long to make a selection, you will need to begin the process again.
4. The device will display the Motorola logo and then the Android in distress ( logo with Exclamation mark)
5. Press and hold the VOL UP key for 10-15 seconds. While still holding the VOL UP key tap and release the POWER key
Tip: You can try this step, holding the phone in landscape. If you are stuck on step 6, try a force reboot by pressing the Power key and Vol Down key, and start the process again.
6. The device will display additional menu options (Text will appear in BLUE)
7. Use the VOL DOWN Key to scroll to wipe cache partition and the POWER Key to select this option
8. The device will then perform the partition wipe (It will run for over 5 min and you need to just let it run to completion.)
9. The device will reboot and start the normal power up sequence

... Thom
 
Allan Cruet said:
I have this issue as well. I thought perhaps it was because my Bluetooth was connected, but in my pocket, that I was not hearing my phone ring. So I tested that theory.
I called the phone from my land line with the Bluetooth on and it did not ring but the Bluetooth was telling me I had an incoming call. Then I turned off the Bluetooth and called and the phone displayed incoming, but did not ring nor vibrate although it is set to do both. So while the call was being displayed I hit the vol up to ensure it was turned up, the volume indicated full up, and the phone began ringing and vibrating.
I then reconnected my Bluetooth, dialed in again and lo and behold, the phone rings aloud, vibrates, and the Bluetooth tells me I have a call incoming.
So now what remains to be seen is how long this will stick.

Verizon asked me to clear my cache partition, and I think I did so, prior to conducting this test.
I followed the prescribed steps but they don't quite jive.
I selected the recovery mode per the steps to scroll using vol down, and then it says to select recovery mode using vol up, but vol up simply scrolls in the other direction from vol down, and changes the mode.
So I had to punch the power button to select. From there it indicates "no command" so I have no idea what's happening. Then after waiting a while the phone powered up.
Did it clear the cache partition? Who knows?
But "whatever"!
for the moment incoming calls ring, vibrate, and tell me over Bluetooth.

As I said "we'll see how long this sticks".
Sounds superstitious, as opposed to a fix, but the outcome is thus far undeniable.
Click to expand...

WOW! I called Motorola to find out if the wrong Clear Cache Partition instructions were known to them.
"some Turbos clear cache differently from the posted instructions" was their response.
at the step that shows the icon with "no command" I had to proceed to press the volume up button for 12 seconds, then add a click of the power button (simultaneous with vol up) to result in another menu.
The font for that menu is nearly microscopic.
the last item on that menu is "Wipe Cache Partition"
I performed that, and it took minutes to complete (seemingly forever) the tech says that supports that the cache was possibly over-loaded.
He believes this will eliminate the weird behavior of the phone not ringing, or the phone power resetting itself once a day lately.
I have had the phone since November and could have accumulated so much stuff in the cache that the phone could not handle it.
We'll see, because if I can go a day or two without resetting mysteriously, and if it rings, then I am fixed.
 
Ever since KitKat 4.4.4, Motorola phones have been taking anywhere from 5 to 20 minutes to wipe the cache partition. It doesn't much matter how much it is "overloaded".
 
I Wipe Cache Partition every Saturday (my maintenance day). Not doing it results in it becoming contaminated over time and performance really suffers.

I've noticed that the time to wipe is about 6-7 minutes on both the Turbo and the Maxx. No one has yet explained why it takes so long.

... Thom
 
Thom said:
I Wipe Cache Partition every Saturday (my maintenance day). Not doing it results in it becoming contaminated over time and performance really suffers.

I've noticed that the time to wipe is about 6-7 minutes on both the Turbo and the Maxx. No one has yet explained why it takes so long.

... Thom
Click to expand...
I have never previously wiped cache. The phone never did anything weird until these recent episodes.
After wiping cache with per Verizon's suggestion, I was hoping it would cease cycling power on its own.
But later in the afternoon yesterday, it once again cycled its power.

recap of symptoms:
The phone began power cycling no more than once a day as of last week.
I have had this phone since November and it never did this before.
It is running 4.4.4, and was last updated in February.
I have made no changes to my phone recently.
And my previous Turbo did the same thing after owning it for a while.
For that phone they had me do several things that did not work.
replace the SIM card, factory reset, gradually reinstall apps to see if one had anything to do with it.
Then when all else failed, replace the unit (last November)

And now working with VZ, when it power cycles itself I dial 1111 to pin point the time of day so they can see if anything relates. We will gather more facts about "when".
 
The cache partition is a fixed size.

If a phone's recovery clears it with a format command, it's really fast.

If it uses a verified remove of each item instead, it's going to take longer and scale up in time for more items.

In a perfect world, both produce identical results.

In the real world, manufacturers choose whichever method is more reliable given their recovery software stack and their storage control hardware.

Cache can't get too big, it's already given a tested, preset limit.

It can get entries tangled up or stale elements that don't refresh properly.

Almost a guarantee that will happen with an OTA update - running new software easily loses alignment with the old cache.

Hope this helps, if not here and now, then next time.
 
Allan Cruet said:
I have never previously wiped cache. The phone never did anything weird until these recent episodes.
After wiping cache with per Verizon's suggestion, I was hoping it would cease cycling power on its own.
But later in the afternoon yesterday, it once again cycled its power.

recap of symptoms:
The phone began power cycling no more than once a day as of last week.
I have had this phone since November and it never did this before.
It is running 4.4.4, and was last updated in February.
I have made no changes to my phone recently.
And my previous Turbo did the same thing after owning it for a while.
For that phone they had me do several things that did not work.
replace the SIM card, factory reset, gradually reinstall apps to see if one had anything to do with it.
Then when all else failed, replace the unit (last November)

And now working with VZ, when it power cycles itself I dial 1111 to pin point the time of day so they can see if anything relates. We will gather more facts about "when".
Click to expand...
Have you tried running in safe mode?

I've had a bad browser update - complete with a runaway condition we call a memory leak - produce nearly identical results on another phone model fwiw.

"Gradually reinstalling apps" sounds good on paper but is really worthless if the last one or near to it is an offender. Iow - can work, often works, can't be guaranteed to work.
 
EarlyMon said:
Have you tried running in safe mode?

I've had a bad browser update - complete with a runaway condition we call a memory leak - produce nearly identical results on another phone model fwiw.

"Gradually reinstalling apps" sounds good on paper but is really worthless if the last one or near to it is an offender. Iow - can work, often works, can't be guaranteed to work.
Click to expand...

Tell me more about safe mode.
I know how to use it on a PC but not on my phone.
two questions:
How do I get into it?
What functionality will I be reduced to, while running in safe mode?

Given that it takes a day, at an unpredictable time of day, how practical would it be to run in safe mode for a day or so?
To prove what?
That an app is responsible due to a memory leak?
Then would I have to begin a binary process of elimination to find the app?

This is one of the best forums I have ever been involved with.
I thank you for the information you are providing.
It rings true!
 
http://www.verizonwireless.com/support/knowledge-base-118294/

Safe mode limits you to your pre-installed apps with the default settings.

You will lose access to your installed apps and any updates to your pre-installed apps.

Much more freedom than a pc in safe mode but every bit as secure for your purposes.

If the phone runs successfully that way, then we'll know it's an app for sure and can attempt various probes and measurements to see if we can't get out of the misery caused by an incremental installation do-over.

If the problem persists even in safe mode we'll start looking for bad media files causing your phone to go nuts trying to index the impossible.

If you're suffering from reception problems - constant signal loss and re-acquistion or constant 3G/4G toggling - that could also make your phone nuts.

If either of the above two conditions are involved then you'll be already noticing rapid battery drain compared to before.

If you're using any of the silly addon helpers for automation in: task management, ram cleaners, cache cleaners, battery boosters, signal boosters - please stop and say.

They're almost all - we're talking 99% here - complete snake oil and do far more harm than you might guess with zero offsetting gain. Iow - pure snake oil.

Good to start?
 
For an un-root-ed phone the usual approach ...

Wipe Cache Partition (rules our fragmented/contaminated temporary storage)
If problem is still there
Run in Safe Mode (rules out bad app that you added)
If problem is still there
Factory Data Reset (rules out any change you made and some firmware bugs)
If problem is still there
Replace phone

(I had one where the buttons at the bottom of my Turbo stopped working. I followed the process in preparation to an exchange. After the Factory Data Reset it started working again.)

... Thom
 
Once again excellent input thanks.

Thanks for the link on getting into safe mode.
it's very simple...figures :)

I am not prone to using those snake oil add-ons.
I'm using the same apps I have been using since November.
But I accept that one of them could have an update that contributes to the memory leak theory.

A default phone will be minimally useful to me, and I need select a time I can do without the useful apps I rely on, and use safe mode for that period of time.

The weekend is coming and I can do without those apps then.
I expect to run all day Saturday and Sunday in safe mode.

Then after using safe mode I will offer update results.
 
EarlyMon said:
If a phone's recovery clears it with a format command, it's really fast. If it uses a verified remove of each item instead, it's going to take longer and scale up in time for more items.
Click to expand...

20 sec vs. 7 min?

Is it possible that the longer version is caused by re-writing the area multiple times to make it more secure?

... Thom
 
You must log in or register to reply here.
Back
Top Bottom