Hi to everyone.
Recently I started having a problem with my Moto G 2015. Each time i make or receive a call, my Moto G reboots with apparently no reason.
I searched in XDA and in other webs, and i didn't found a solution.
Then, i decided to experiment with the system. I made everything with no results.
One day, doing some research, i found the default apps option and i saw that i have other app in the calls option. I changed the option to "Dialer", tested the phone, and it works!!!
The steps to repair are:
Go to Settings>>Applications>>click on the Cogwheel>>Default Applications>>Telephone Application>> Select the app "Dialer"
And that's all!!
I hope this works to all.
Related
I have a Droid Pro, Android 2.3.3, build 4.5.1-110-VNS-11, sim unlocked, using it in Europe.
I've recently changed my provider, and the new one needs to use the data roaming option all the time. Problem is, I turn it on, but as soon as you loose signal, the option turns itself off and you have to manually turn it on. Doing this many times a day becomes a big PITA ...
After some research it seems to be a known Moto software issue, found several threads in the Droid 3 part of the forum, but haven't identified a fix for the Droid Pro.
Does anyone know of any system update that i can install, or some app or custom whatever ?
Thanks for any pointer in the right direction ...
I have Lenovo A6000 plus with Android Lollipop 5.0.2 in it. Since few days, whenever I dial a number and press call button or tap on the number (which redirects to call), it's not dialling the call, I have to press 4-5 times then it dials. It happens in both Truecaller (which comes default in A600 plus) and Default Dialer. I cleared all data, caches of both the apps; restarted my phone but problem still continues!
Please HELP!!!
If you are using a true caller app. uninstall app and reboot phone. call now. Problem won't repeat again.
Sent from my Lenovo A6000 using XDA Free mobile app
try uninstall the true caller app first.
hope it's worked
HarshMehta813 said:
I have Lenovo A6000 plus with Android Lollipop 5.0.2 in it. Since few days, whenever I dial a number and press call button or tap on the number (which redirects to call), it's not dialling the call, I have to press 4-5 times then it dials. It happens in both Truecaller (which comes default in A600 plus) and Default Dialer. I cleared all data, caches of both the apps; restarted my phone but problem still continues!
Please HELP!!!
Click to expand...
Click to collapse
Mine was facing same problem. Couldn't fixed it so moved to custom ROMs.
Please reply if you've sorted it
Im having same issue with my a6000 5.1.1 here
Sent from my iPhone using Tapatalk
I' m also facing the same problem.. It feels irritating that the basic job of phone that is calling doesn't work.
HarshMehta813 said:
I have Lenovo A6000 plus with Android Lollipop 5.0.2 in it. Since few days, whenever I dial a number and press call button or tap on the number (which redirects to call), it's not dialling the call, I have to press 4-5 times then it dials. It happens in both Truecaller (which comes default in A600 plus) and Default Dialer. I cleared all data, caches of both the apps; restarted my phone but problem still continues!
Please HELP!!!
Click to expand...
Click to collapse
Update your phone to latest build no. S034
Is this problem is in 3g and 2g network
I believe that In lenovo a6k in 4g can't place call due to absence of volte
I am also facing the same problem... unable to fix it... plz help...
I am sorry to say, but you can't
I think you can't fix it. If anyone suggest a fix, Lenovo release an update to make your fix not work. Why?
All the android mobile manufacturers, come to mutual understanding. Once you use the phone for 1 year, you will start facing one or the other issues (which are introduced by them) So that you would soon consider buying a new Phone.
This is how you are able to get smart phones at cheaper rate. They know that your phone is not permanent. It's like a life time membership, instead of paying them 100 in one go, you pay 20 every year.
You thought, you got your smart phone at a steal deal? Not really. And this strategy is even encouraged by Google as their success if reliant of the success of these companies.
Hard fact. But it's true. No matter what phone you take, we are victims. Period.
The best thing you can do is to not buy phone from the same manufacturer and also spread negative publicity about that brand. There by, sometime later, they realize that their trick is not working.
Hello,
If an iphone user from T-mobile sends my Moto G4 Play (also on T-mobile) an SMS that is longer than the 160 character limit then I may or may not receive the text on my moto g4 play (Amazon edition). I have done experiments. If they send me 5, then I will likely only receive 3 of them. I have done this experiment multiple times and have never received all 5. I have had a friend on AT&T repeat this experiment and I received all 5. I did this experiment to my son's moto E 2nd generation and I think he receives all 5. So, it doesn't appear to be an issue with T-mobile iphones to androids, in general.
I have switched out SIM cards and my phone still has the same issue.
(if my wife puts a subject field in it and turns it into a MMS, I will always receive the message).
I am trying to figure out if the problem is with my particular phone or with the model phone.
So, could a US T-mobile owner of a moto G4 Play who has someone with a T-mobile iphone please have that person send them 5 long SMS messages and see how many come through. That would be helpful for me. I would like confirmation that this problem is with my particular phone.
If you have any other suggestions, I am open to them. My next steps would be a factory reset. If that doesn't fix it I guess I can call Amazon and see if I can get a replacement.
I didn't see anything exactly like this on the forums. Thank you for any help you can provide!!
I recently moved to a Wear24 from a ZenWatch 3 (sadly a MASSIVE improvement in every way besides appearance), but suddenly all my incoming call notifications on the watch display as Private Number. They show up fine on the phone, and I feel confident that when I initially setup the watch they were showing up properly, but now I just get no way to identify the caller on the watch.
Any tips on something obvious I might be missing besides a full reset?
Specifics, if needed:
1. Wear24, unrooted stock, fully up to date on 2.0.
2. Pixel 2 XL running Android P Beta 2/DP3
I am seeing this as well with asus zenwatch 2. I went so far as to reset the watch and set it back up with the same result. I wonder if it has to do with permissions. i have checked to make sure the wear app has all the proper permissions but still "Private Number" shows
Same thing *just* started happening on my Huawei Watch Gen. 1. Haven't tried a factory reset, but it's interesting that this issue is popping up for us all of the sudden at the same time.
Same issue here. Pixel XL 2/Huawei Gen 1
moto360 2015 too
I've got a ART5005 and this is doing my head in. I was using a SW3 with no issues and still no issues. Are people on the Android P beta? Might sync it with another phone to see if I get the same results.
same issue with pixel 2 xl and ticwatch e. phone app on watch will display 'name of contact' missed call but private call whilst ringing.
Same here Pixel 2 XL with Huawei 1st gen. Running P DP3
Have a feeling it's Android P DP3, that's when it started happening for me too
Pixel 2XL - LG Urbane
FYI, yesterday after a reboot of my phone my watch suddenly wanted to pair again and failed. The reconnect function in the Wear OS app wouldn't work. I eventually restarted both devices, opened Wear OS again, hit reconnect, repaired successfully, and then the Wear OS app asked me if I wanted to allow the watch to make and manage calls. I answered yes, and my Caller ID on the watch has worked perfectly since.
Well looking at your comment, i went and opened Watch OS app and i had the same prompt about allow the watch to answer/reject calls. I hit allow and now it's working
What is "Watch OS app" . Did you mean "Wear OS app"?
Hello all,
I've been using my Axon 7 since 2016, and I'm still hapy with it. Recently, a weird bug has cropped up which I can't figure out. When I call some phone numbers, the phone doesn't ring at all. It goes straight to 'Call ended'. I've tried my SIM in another phone and it works just fine. So it seems to be the phone, not the provider. It happens to a select few phone numbers. The vast majority of phones I call are completely fine. LTE + data is completely untouched too.
About two years ago, I moved from stock to LOS 15. Today, I updated to crDroid 9 (from this forum). That did not solve the issue. I then updated the modem with the one from @raystef66 (v1.30B01), which didn't fix the issue either.
It's worth noting that these phone numbers still worked when I first moved to LOS. Only this year, a few months ago, problems started to arise.
Some info about my phone:
ZTE AXON 7 A2017G
Android 9/crDroid 5.12 w/ sec patch feb 2021, vendor sec patch july 2018
Baseband .2.0.1.c8-00024-....
Kernel 3.18.140-Baddar-RC1.2
How would I go about solving this issue?
Cheers,
Qopzeep
I found the solution. For other people in the future also struggling with this, this is how I solved it:
Go to Settings
Tap Network & Internet
Tap Mobile network
Toggle 'Enhanced 4G LTE Mode' off
After toggling it off, all numbers are reachable again. What a strange bug. Is this Android/crDroid or my provider?
Anyway, I hope this helps someone else.
Cheers,
Qopzeep