OK, I've had the Moto X Force (Droid 2 Turbo) for a couple of months now, and some odd issues have arisen.
Logged with Motorola, to no effect/feedback.
Stock ROM, Marshmallow 6.0
System: 24.11.8.kinzie_reteu.reteu.en.EU.retgb
Launcher: Hola v 2.2.3
1. Intermittently calls ring, but no pop up to answer.
There's no way to answer the call!
I have to wait, then look at Call Log t see who's called!
Next call might come through normally.
Some calls, same caller, work, some don't.
No whitelists/blacklists etc. enacted on any app.
2. Some SMS's not arriving (daily 8am text from bank)
Again sometimes OK, sometimes nothing.
I'm sure this is a clashing App, not H/w - any ideas?
Nothing obvious, and the intermittent nature of the fault is REALLY annoying!
Trying to avoid a full reset.
Also, waiting for Marshmallow 6.01 as my Mi Band won't act as a Bluetooth Device for Screen lock purposes (Pairs invisibly) - and 6.01 is supposed to fix this.
Any ideas when this might be released by Motorola?
Cheers
En_croute
Related
Hi!
My first post here....
I rooted my MT3G and installed CyanogenMod latest version. It was working fine for a week or so (except for "Force Close" issues, but I took care of that by removing task bar), and now since last Friday I'm not receiving most of my incoming phonecalls. My friends tell me they're trying to call me, but get disconnected right away. Phone doesn't ring, I get no missed calls, and it won't even go to voicemail. Occasionally though some calls will go through.... Outgoing calls and everything else seems to work fine. Also, when in the car and connected to bluetooth system and someone would call my phone, the bluetooth recognizes incoming phonecall, says "call from...", and doesn't even proceed with the number, just says "call ended".
I tried to reinstall CyanogenMod; called my phones several times from different phones, worked fine, but later in the day started getting messages from people saying that they can't reach me.... calls are dropping again.
Please advise if you have any ideas to solve this.
Or if someone can tell me how to reverse the upgrade I did, I would like to give it a try and see of it fixes my phone.
Thanks!
My phone works just fine with CM, maybe it's a hardware problem, if you don't get it fixed by next week I suggest unrooting it and seeing if the problem still persists. If it does, maybe take it back to your carrier and get a replacement.
Thanks, Anartic!
Yes was considering unrooting it. Could you tell me please how to do it? Or give me a link to that info?
Thanks!
First off, I didn't find this anywhere on the forum, so I hope it's not a dupe - but it's a very annoying problem. I have a Galaxy S5 on KitKat. Here's the issues (pretty much all related):
Often times, I'll answer an incoming call successfully but the person on the other line simply hears a continuous ring cycle.
(Same as #1), but instead of hearing ring cycles - they get voicemail.
On other occasions my phone will be face up on a counter, I'll get a phone call, and when I walk over to the device it will "automatically answer" but the person never connects on the other line.
For all of these occasions, this seems to happen more frequently the first time someone tries to call me. Sometimes additional incoming calls from that number will go through with more success, but not all the time. Restarting the phone and pulling out the SIM card and battery not only do not fix the issue, but seem to consistently re-create the problem.
I should also note that I had Google voice as my provider for voicemail, but I have temporarily disabled that and set up my voicemail through Verizon - still doesn't help. Also 3rd party dialer apps like Dialer One do not make a difference.
Here are my settings:
Android Version 4.4.4 - Kitkat, no updates available (non rooted)
Blocking mode disabled
Motions and Gestures disabled
S-Voice disabled
Preferred network mode: LTE / CDMA **This seemed to solve the problem at first, but it came back immediately. (It was set to 'Global')
I've spent hours trying to fix this and contemplated rooting my device to try to get it to work, but to be honest I'd rather just exchange the phone for a new one before I did something like that. I also have not restored to Factory Default... but again that is preferably a last resort.
Any thoughts? I need a 100% working phone for my job and missing phone calls and having to call people back just isn't cutting it.
rmarq423 said:
First off, I didn't find this anywhere on the forum, so I hope it's not a dupe - but it's a very annoying problem. I have a Galaxy S5 on KitKat. Here's the issues (pretty much all related):
Often times, I'll answer an incoming call successfully but the person on the other line simply hears a continuous ring cycle.
(Same as #1), but instead of hearing ring cycles - they get voicemail.
On other occasions my phone will be face up on a counter, I'll get a phone call, and when I walk over to the device it will "automatically answer" but the person never connects on the other line.
For all of these occasions, this seems to happen more frequently the first time someone tries to call me. Sometimes additional incoming calls from that number will go through with more success, but not all the time. Restarting the phone and pulling out the SIM card and battery not only do not fix the issue, but seem to consistently re-create the problem.
I should also note that I had Google voice as my provider for voicemail, but I have temporarily disabled that and set up my voicemail through Verizon - still doesn't help. Also 3rd party dialer apps like Dialer One do not make a difference.
Here are my settings:
Android Version 4.4.4 - Kitkat, no updates available (non rooted)
Blocking mode disabled
Motions and Gestures disabled
S-Voice disabled
Preferred network mode: LTE / CDMA **This seemed to solve the problem at first, but it came back immediately. (It was set to 'Global')
I've spent hours trying to fix this and contemplated rooting my device to try to get it to work, but to be honest I'd rather just exchange the phone for a new one before I did something like that. I also have not restored to Factory Default... but again that is preferably a last resort.
Any thoughts? I need a 100% working phone for my job and missing phone calls and having to call people back just isn't cutting it.
Click to expand...
Click to collapse
First try a data factory reset, if that doesn`t help refash the stock rom with odin 3.09 and after that factory reset/wipe cache in recovery.
rmarq423 said:
First off, I didn't find this anywhere on the forum, so I hope it's not a dupe - but it's a very annoying problem. I have a Galaxy S5 on KitKat. Here's the issues (pretty much all related):
Often times, I'll answer an incoming call successfully but the person on the other line simply hears a continuous ring cycle.
(Same as #1), but instead of hearing ring cycles - they get voicemail.
On other occasions my phone will be face up on a counter, I'll get a phone call, and when I walk over to the device it will "automatically answer" but the person never connects on the other line.
For all of these occasions, this seems to happen more frequently the first time someone tries to call me. Sometimes additional incoming calls from that number will go through with more success, but not all the time. Restarting the phone and pulling out the SIM card and battery not only do not fix the issue, but seem to consistently re-create the problem.
I should also note that I had Google voice as my provider for voicemail, but I have temporarily disabled that and set up my voicemail through Verizon - still doesn't help. Also 3rd party dialer apps like Dialer One do not make a difference.
Here are my settings:
Android Version 4.4.4 - Kitkat, no updates available (non rooted)
Blocking mode disabled
Motions and Gestures disabled
S-Voice disabled
Preferred network mode: LTE / CDMA **This seemed to solve the problem at first, but it came back immediately. (It was set to 'Global')
I've spent hours trying to fix this and contemplated rooting my device to try to get it to work, but to be honest I'd rather just exchange the phone for a new one before I did something like that. I also have not restored to Factory Default... but again that is preferably a last resort.
Any thoughts? I need a 100% working phone for my job and missing phone calls and having to call people back just isn't cutting it.
Click to expand...
Click to collapse
Im having the same issue, i cleared the cache, did a factory reset and made sure s voice was turned off, it cleared the issue up for about a month. Recently i have been having this issue happen more and more. Im starting to think it may have something to do with the Bluetooth or the visual Voice mail / voice mail. Anyone else have any ideas on what else to try or do ? The only problem is recreating the environment to cause it to happen. Right now its completely random.
Ok ive been pulling my hair out for a while with this problem so im really hoping you guys can give me some answers or suggestions to help me fix it My Girlfriend has the Galaxy S5 SM-G900V. Baseband version G900VVRU2BOG5 So rooting or custom ROMS is out of the question so that leaves me with trying to diagnose and eliminate this problem without a easy way out.
Ok the problem is once she updated the phone to lollipop she had all the common problems that come with it over time i have slowly eliminated them with factory resets and cache cleaning and such although i have one problem that not even verizon can figure out. The phone itself with occassionally and randomly just refuse to make or receive calls its a very odd problem because the phone will send and receive sms and mms just fine when this happens but when we try to dial out it just sits at dialing and never connects, when calls are dialed into the phone it will ring 5 times or so then go to voice mail or just go straight to voicemail altogether without ever ringing the s5 shows no sign of anyone ever trying to call at all no ringing no records nothing. Once in a blue moon it will ring 4 times on the dial in and then the s5 will start ringing around the 5th ring which is extremely long time IMO. This happens very randomly and in all different locations i have disabled call blocking and auto reject i have tried safe mode to only experience the same problems, i have factory reset several times. Verizon opened a ticket with there tier 2 techs and network development team to check out the issue they tell us everything is completely fine and theres nothing they can see wrong. But they do not deny the problem is there they just cant explain it. Now get this, This is the second phone that has done this to her Ther first one had the same problem and was warranty claimed this is the second phone and same exact issues. Im not sure what else i can do i am a very tech savy person and this one has got me stumped the only thing i can see thats odd for me is the phone has 3 Phone services running in the background But I believe this may have something to do with the Touchwiz Easy Or Regular Home UI althought im not sure why it would use seperate apps. Anyway any input would be helpful Thanks
Hi, I recently (yesterday actually) had to factory reset my S7edge. I'm running the latest beta Nougat version still but I noticed that I wasn't receiving any notification pop ups on my home screen for my text messages and incoming phone calls I use both stock apps and I've never had this happen before without being able to troubleshoot it myself. I think I've done everything possible, but if someone could help me out, I'd really be grateful. Thank you... Keith G
It started suddenly after a week on the January update, but I downgraded to Dec update and still have the same issues, meaning it's a hardware defect. Already reported this to google. Anyone else?
Had similar issue
I had a similar issue since yesterday. Tried booting into the safe mode to check if any third party app is doing it( If you wanna try that hold the power button then touch and hold the power icon on the screen). If it still stays it is a hardware issue you need to get it repaired. I just gave my phone to Ubreakfixit
Yes it is a hardware issue. Safe mode, factory reset, downgrading the software did not work.
This just happened to me this morning.
what is going on? this literally just happened to me too this morning. I can make calls via whatsapp/facebook etc, but if I try to call anyone it just says "calling" but there's no sound, eventually it cuts off. If someone tries to call me, the phone doesn't ring and I just get the sms saying there's a message in my voicemail. It says I'm on the 4g network, I can send sms messages and wifi works fine. If I have to ship the phone anywhere I'm ****ed, I'll have to buy another phone as a spare :crying:
SmokewiseGanja said:
what is going on? this literally just happened to me too this morning. I can make calls via whatsapp/facebook etc, but if I try to call anyone it just says "calling" but there's no sound, eventually it cuts off. If someone tries to call me, the phone doesn't ring and I just get the sms saying there's a message in my voicemail. It says I'm on the 4g network, I can send sms messages and wifi works fine. If I have to ship the phone anywhere I'm ****ed, I'll have to buy another phone as a spare :crying:
Click to expand...
Click to collapse
It appears the bottom speaker just burnt out. Hundreds of other people have the same issue across all pixel models.
backslashV said:
It appears the bottom speaker just burnt out. Hundreds of other people have the same issue across all pixel models.
Click to expand...
Click to collapse
Looks like I'm one of the lucky ones. I had to go out and soon as I got to the next town a call came in, so I tested making more calls and it worked fine there. Upon returning home the issue returned. I figured it's gotta mean something is up with my provider or the nearby antenna so asked a few friends who live near me and a neighbour. Turns out they all have the same issue. I'll have to wait it out now and see if they fix it. The wierd part is 4g data and sms work fine and I've still got full signal strength or I'd have assumed that right away.
SmokewiseGanja said:
Looks like I'm one of the lucky ones. I had to go out and soon as I got to the next town a call came in, so I tested making more calls and it worked fine there. Upon returning home the issue returned. I figured it's gotta mean something is up with my provider or the nearby antenna so asked a few friends who live near me and a neighbour. Turns out they all have the same issue. I'll have to wait it out now and see if they fix it. The wierd part is 4g data and sms work fine and I've still got full signal strength or I'd have assumed that right away.
Click to expand...
Click to collapse
That sounds more plausible than hundreds of Pixels bottom speaker burning out all of a sudden. When the call supposedly comes in does it show on the screen or just go directly to voicemail? That would be the initial test of the speaker. Does it play music, can you hear notifications? Every once in a while that happens to me and then I just try again a mile or so down the road and it connects fine. If you have wifi calling you can try that too.
bobby janow said:
That sounds more plausible than hundreds of Pixels bottom speaker burning out all of a sudden. When the call supposedly comes in does it show on the screen or just go directly to voicemail? That would be the initial test of the speaker. Does it play music, can you hear notifications? Every once in a while that happens to me and then I just try again a mile or so down the road and it connects fine. If you have wifi calling you can try that too.
Click to expand...
Click to collapse
No, it was the service provider in the end. My whole town had the issue for a couple days. The company (movistar) have fixed it now so I can make calls and recieve them no problem. To say I was relieved is an understatement.
Bottom speaker broke out of nothing
I guess I'm really unlucky, me and my girlfriend got two pixel 4 in black Friday and both of the phones had the same issue, it started having a crackling sound for a few seconds and then the bottom speaker completely died while in a speakerphone call tried a factory reset with no luck, no sounds comes out, my girlfriend had the phone only for a few weeks when that happened, and in my phone happened last week, now we have to figure how to ship the phone back to the US and try to get a refund, since if it breaks again it would be close to impossible for us to ship it back again
backslashV said:
It started suddenly after a week on the January update, but I downgraded to Dec update and still have the same issues, meaning it's a hardware defect. Already reported this to google. Anyone else?
Click to expand...
Click to collapse
Hello everyone
I own a pixel 4 and it has a constant problem.
after operating normally, suddenly for no apparent reason it loses all sounds and vibrations.
also it is not possible to make calls and freezes in various system applications.
sometimes this is solved with a simple restart of the phone, other times a factory reset is necessary and lately it is required to unlock the boot loader to reinstall the factory image and test with which security patch recovers all its functions and returns to function normally.
It started suddenly after a week on the January update
What would be the cause of this failure in the phone?
At first I reported the problem to google and they indicated the same to most of you; restarting the phone or factory reset and how the method worked no longer insisted.
after the February update its operation was normalized, but with the arrival of the May update the same problem returned.
I had to downgrade to the April update, then to the March update and after several attempts it worked again, but a few days later the problem returns and I have to repeat the process.
What arguments should i use to convince google to change the phone or return my money?
I never rooted
Buy the unlocked phone at BHphoto on Black Friday
model G020I
I live in Peru
NOTE: I do not speak English and use the translator.
sorry
I'm on latest Android 11 DP and I noticed that this release removed a lot of bass from the speaker. I think to prevent the clipping and damage of the speaker.
SmokewiseGanja said:
what is going on? this literally just happened to me too this morning. I can make calls via whatsapp/facebook etc, but if I try to call anyone it just says "calling" but there's no sound, eventually it cuts off. If someone tries to call me, the phone doesn't ring and I just get the sms saying there's a message in my voicemail. It says I'm on the 4g network, I can send sms messages and wifi works fine. If I have to ship the phone anywhere I'm ****ed, I'll have to buy another phone as a spare :crying:
Click to expand...
Click to collapse
Is your "Do not disturb" mode turned on by chance.
Sorry if this is a stupid suggestion.