I'm on official July security update for Sprint. No root or anything. Using stock dialer app. Everytime I call a company or business that requires you to press something from a menu my phone doesn't register anything. They just keep repeating the menus over and over. Is anyone else having issue with this. The phone makes the sound when I hit a number and it shows on the dialer but the automated menus don't pick anything up
Does this happen with every automated dialler menu or just one number?
iceepyon said:
Does this happen with every automated dialler menu or just one number?
Click to expand...
Click to collapse
All of them. Called a store and my cable customer service. Still not working
Try booting your device into Recovery Mode and Wiping the Cache Partition. If that doesn't work try wiping the cache data in the dialler app. If after all that and your dialler is still doing the same thing. Then I recommend backing up all your data and performing a hard factory reset.
Related
My sprint Marquee started to develop an annoying problem: reset during call. I cannot post link yet, but there are several other Marquee users reported same problem in androidcentral forum.
It's not a complete reset, but the screen will turn blank and not responsive, only the four button will flash the led. After 1 minute it will come back.
I knew I can try to restore to factory default, but after a little search, I saw many android phone user met this problem, and many of them were using factory default settings. So I decided to uninstall apps and install an error log app for next reset.
Yesterday there was another reset, and I saved the error log immediately after the reset. But I'm not sure if the error caused the reset can be recorded.
Hear are the error log, anybody can have a look at it and get some ideas about the problem?
For the apps I installed in my Sprint marquee:
It was rooted. No task killer. Used to freeze sprint bloatware with Ti backup but I uninstalled Ti backup earlier.
Was using Go launcher, then zeam launcher.
Was using dialer one, then back to stock dialer. the call log was limited to 7 days. -- I was guessing it could be the call log too long.
For the error log files:
alogcat.2012-01-26-18-06-31-error.txt
this one was generated right after the reset, but I didn't know how to turn on time display at that time.
The reset occurred on about 18:06.
alogcat.2012-01-27-00-00-52-warning.txt
this one was generated later at night with time displayed. It's a log on warning level.
alogcat.2012-01-27-00-03-07-info.txt
this one was generated later at night with time displayed. It's a log on info level.
My wife's bionic updated to ICS yesterday. no problems that we know of yesterday. Her phone is calling "i assume the last person called" on its own while on a phone call with that person. This happened 3 times in about 2 minutes.
Today, mid conversation, she is talking to me then I hear the call coming in from other line. I look, its her. It happened near immediately. Idk if you can 3-way call the same person, but her talking to me to her calling me was near instant. She is disconnected from the previous call and when I answer the new call, she's back.
Her phone is calling "i assume the last person called" on its own while on a phone call with that person. This happened 3 times in about 2 minutes.
Stock OTA unrooted. No apps installed after OTA.
Any suggestions? Can you clean dalvik cache on unrooted bionic?
kegman913 said:
Can you clean dalvik cache on unrooted bionic?
Click to expand...
Click to collapse
I might be incorrect on this, but the OTA, having moved from GB to ICS should have triggered a dalvik wipe on its own. It could have been a flaky upgrade process, or if you told Google to save/restore phone settings during setup, could have caused issues. FWIW, this has caused me quite a few problems in the past with employee phones after major OS upgrades.
Since she doesn't have apps installed, I would try a full data wipe, and when you set the phone back up, do NOT allow Google to restore your phone settings. She'll get her contacts and calendar back when she logs into her Google account, just leave the phone settings out of it. Of course, she'll then have to set her wallpaper and icons back up, etc.
I'll wait to see if it keeps happening. thanks
Well heres the details
HTC One AT&T (Unlocked) Used on TMobile
Phone is bootloader unlocked and rooted
Was running a custom 4.4 ROM not sure which one. That one was having issues so my friend who owns the phone tried to fix it himself in TWRP.
He ended up formatting and deleting everything so the phone was stuck in boot loop with no OS.
So I side loaded cygen 4.4.2 and got it back up and running.
Issues began. When you open the Google Dialer it brings up all the contacts as it should but if you receive or dial a number the active call screen starts to load to a black screen then kicks you back to the contacts. The phone call will continue though and cannot be ended. Only way I have gotten it to end calls is by enabling lock to end call.
So I tried updating just Google Dialer which caused a force close issue even after clearing all data for GD and Phone in the apps section.
So I installed the newest google apps 4.4.x but the no active call screen remains
Next I installed the Beanstalk 4.4.2 (have it on my s3 and like it) everything runs great other than the Dialer again. It again is not working and still fails to load the active call screen both send or receive.
Ive done Cache/Delvik whipe. Ive done permission resets. Ive even tried Swipe Dialer from the app store with the same issue.
Open to suggestions to fix this. Im stumped. I have a feeling it has something to do with the Phone.apk and Phone_contacts.apk in the App section of the phone since Ive change the Google dialer apk 4 times and nothing has changed.
Added info
Blown240sx said:
Well heres the details
HTC One AT&T (Unlocked) Used on TMobile
Phone is bootloader unlocked and rooted
Was running a custom 4.4 ROM not sure which one. That one was having issues so my friend who owns the phone tried to fix it himself in TWRP.
He ended up formatting and deleting everything so the phone was stuck in boot loop with no OS.
So I side loaded cygen 4.4.2 and got it back up and running.
Issues began. When you open the Google Dialer it brings up all the contacts as it should but if you receive or dial a number the active call screen starts to load to a black screen then kicks you back to the contacts. The phone call will continue though and cannot be ended. Only way I have gotten it to end calls is by enabling lock to end call.
So I tried updating just Google Dialer which caused a force close issue even after clearing all data for GD and Phone in the apps section.
So I installed the newest google apps 4.4.x but the no active call screen remains
Next I installed the Beanstalk 4.4.2 (have it on my s3 and like it) everything runs great other than the Dialer again. It again is not working and still fails to load the active call screen both send or receive.
Ive done Cache/Delvik whipe. Ive done permission resets. Ive even tried Swipe Dialer from the app store with the same issue.
Open to suggestions to fix this. Im stumped. I have a feeling it has something to do with the Phone.apk and Phone_contacts.apk in the App section of the phone since Ive change the Google dialer apk 4 times and nothing has changed.
Click to expand...
Click to collapse
I forgot to add
The phone dialing abilities worked perfectly fine before even with the new google apps installed and on 4.4 KitKat. This problem only came after my friend soft bricked the phone by erasing the old roms.
try disabling "non-intrusive call" in Phone settings
Sent from my One using Tapatalk
Same problem GS4 Sprint
Blown240sx said:
Well heres the details
HTC One AT&T (Unlocked) Used on TMobile
Phone is bootloader unlocked and rooted
Was running a custom 4.4 ROM not sure which one. That one was having issues so my friend who owns the phone tried to fix it himself in TWRP.
He ended up formatting and deleting everything so the phone was stuck in boot loop with no OS.
So I side loaded cygen 4.4.2 and got it back up and running.
Issues began. When you open the Google Dialer it brings up all the contacts as it should but if you receive or dial a number the active call screen starts to load to a black screen then kicks you back to the contacts. The phone call will continue though and cannot be ended. Only way I have gotten it to end calls is by enabling lock to end call.
So I tried updating just Google Dialer which caused a force close issue even after clearing all data for GD and Phone in the apps section.
So I installed the newest google apps 4.4.x but the no active call screen remains
Next I installed the Beanstalk 4.4.2 (have it on my s3 and like it) everything runs great other than the Dialer again. It again is not working and still fails to load the active call screen both send or receive.
Ive done Cache/Delvik whipe. Ive done permission resets. Ive even tried Swipe Dialer from the app store with the same issue.
Open to suggestions to fix this. Im stumped. I have a feeling it has something to do with the Phone.apk and Phone_contacts.apk in the App section of the phone since Ive change the Google dialer apk 4 times and nothing has changed.
Click to expand...
Click to collapse
I have the same problem, but I'm not able to finish the call even enabling the "end call with power button". I have to activate airplane mode.
I'm on a Galaxy S4 Sprint. If you found a solution I'll appreciate if you share it.
I still havnt found a solution. Im currently downloading a stock rom hoping that it might have some system file I may be missing.
The Intrusive calling feature isn't on the HTC One
Anyone with programming or some knowledge on whats going on can you please help. Im stumped
Blown240sx said:
Anyone with programming or some knowledge on whats going on can you please help. Im stumped
Click to expand...
Click to collapse
So this is a really old thread, but I'm betting the IMEI got wiped. Phone can't call without an identity.
I'm not a noob by any means. I've done all the normal troubleshooting. I've looked for other similar topics and none exist for this phone. I've tried everything that I can think. Having said that, please excuse me if i missed anything.
Basically, my issue is that I can't accept 95% of my incoming calls. I try to.... And the call hangs up when I press answer. I have the regular stock google dialer. I'm stock but rooted and unencrypted. I realize this may have to do with LTE still being on and not H+ but it's really annoying. It does switch to H+ but still hangs up.
I tried a few custom ROMs and the issue still exists. I've ensured that notifications are checked in the dialer app.
Someone please help me. Maybe I'm missing something simple. It's really annoying not being able to accept a call and having to call people back for every call received.
Please and thanks
And now I've officially tried EVERY ROM for this phone and still.... Can't answer incoming calls. Ugh. Someone please help
Have you tried updating your radio? Have you tried setting your phone in non-LTE so at most it only utilizes H+/H/3G?
Have you cleared cache and tried it in safe mode?
@zephiK thank you for the ideas. Flashed the new radio from your thread... Issue still persists. I haven't gone to just 3g yet because I use my phone a lot for work (law enforcement) and need the LTE speed when identifying people
Edit: tried using 3g and 2g anyways.... Still hangs up whenever I answer incoming calls. Ugh
PDP///M said:
Have you cleared cache and tried it in safe mode?
Click to expand...
Click to collapse
I have cleared both cache and dalvik cache. I can't get safe mode to work..... I'm using liquid smooth at the moment and when holding power off it doesn't show the option for safe mode
Well I figured out holding reboot gives the safe boot option. My phone bootlooped. I'm going to have to totally undo everything on my phone. Lock and unroot my phone. Then I'll start over using only stock without unlocking or rooting first then continue this trouble shoot.
If anyone can think of anything else please let me know thank you and merry Christmas
I had the same issue with mine. I thought I was going crazy. Hope you get it worked out. I sent mine back to Motorola yesterday for a refund.
Sent from my iPhone 6 Plus using Tapatalk
Update : Solved....
I wiped everything and started over. I flashed stock and went into safe mode. Calls worked. So it was easy to figure out... It was a downloaded app. A call blocker that was blocking everything instead of just the calls it was supposed to.
Thank you to those who offered opinions, suggestions, and comments
I had the same issue with the N5 on att. Was rooted and used a tool that opened a Sprint "only" service menu. Played with a setting and boom, i had voice. Data worked no problem throughout this ordeal.
Have the same problem with a Nexus 6, suddenly the phone did not show up any incoming call screen/window or way to slide out to answer an incoming call. It rings but there is not way to answer the call, even trying to go to the task bar and see if there is a window up there to answer it, no notification or window to press and answer.
This phone is not rooted nor have an application to block calls. it is with lollipop 5.01.
Any ways to solve this horrible bug? This bug is driving me nuts.
I didn't make any significant modifications in the time frame this happened so i am at a loss for HOW it happened BUT, my phone is not recieving calls properly. whenever i get a phone call my home back and app buttons disappear and the accept or decline call screen doesn't show up. additionally i can't pull down the quick setting menu. once the caller hangs up i can call them back with the usual call back button as the normal missed call screen appears. i can also make calls normally.
I tried clearing cache, hard and soft reboot, restoring to an older known working date with titanium backup, re-downloading avg antivirus and scanning.
the only thing i have done to my z3c in the past couple days is download play legacy to try and update some apps i got from amazon for free from the play store automatically (tuneinradio pro and friday night at freddy's) i really don't like the amazon market place ... after this happened i uninstalled play legacy and it still didn't help. has anyone gone through something similar or can maybe help me as i really don't want to start fresh i have my system exactly as i want it and would like to avoid restarting from scratch.
thank you
bump
Restore your nandroid backup or reflash the rom.