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

Help dial pad issue

Johnnyshinta

Newbie
Dec 4, 2013
13
0
When I open my phone pad for the first time the dial pad doesn't load. Then I back out and try again and it works fine. If I open recent apps and clear it and go back in the problem comes back and the same thing is true. If I back out and try again it works.

Anyone else have this issue?
 
I'm pretty sure that's the intended behavior. When you open the dialer, it's showing your favorites and most recent call, and you can search contacts by tapping on the search field at the top and staring to type. If you close the app with the dial pad displayed, it will be displayed when you return - bringing you back to where you left off, just like with other apps.

I prefer the dial pad myself, since it's much easier to dial and search one handed using the dial pad.
 
Upvote 0
Dialer One
I started using it way back when, it was one of the few that had speed dial. It's just been my go-to dialer forever.

I'm not sure if it's KitKat or Dialer One but now when I make a call (most of the time, not always) it opens Chrome. I have to close that after the call. It may be because I use Google Voice Callback or it may be the new 'search around you' feature that isn't active yet in KitKat for the Moto X or Dialer One may need to be updated for KitKat. It's not a problem, just a slight annoyance. That aside, I really do prefer it over all the stock dialers I've had/tried.
 
Upvote 0
There is definitely some bug with the dialer. Not sure If I have the same one you guys are talking about. But sometimes when I open the dialer in Kit Kat, and click the button to open the number pad...it never comes up. I have to hit the back button, and then hit the number pad again for it to show. Its like a little glitch. Kinda annoying. But not a huge deal. Hope it gets fixed whenever I get a new update. Is this what you guys are getting as well?

The bug won't happen again, until I close the app from the active application menu.
 
Upvote 0
On my Nexus 5 I had this problem too where if I press the icon at the bottom to bring up the dialpad it would just give me a bit of white space, then I'd have to press back and then press it again to get it to appear.

I found another discussion about this here:
https://code.google.com/p/android/issues/detail?id=62394

It turns out I had "Animator duration scale" set to "Off" in the developer settings, and changing that to ".5x" fixed the problem for me.

Apparently the Nexus 4 had the same problem so maybe it's a similar thing happening with the Moto X.
 
Upvote 0
Yup the new dialer ......SUCKS!! I hate having to go get a dialer app. Seems so stupid. Just go back to Froyo dialer, please. Something that......WORKED!!!!

Just loaded ExDialer. Looks good so far. Figured it out in just a few seconds. Very intuitive design or it seems at first glance. And you can actually find your 'favorites'.
 
Upvote 0
I converted to it a month ago. Someone finally got it right.

The classic black theme on my phone allows me to actually read the numbers (but not the letters) on the dial pad in direct sunlight.

A friend wanted to send an announcement about a death in his family to 40 e-mail addresses. Not a problem here ... check make on each one and all addresses are included un the To:

... Thom
 
  • Like
Reactions: DonB
Upvote 0
Several people have described the same issue I have:

Each time you open dialer, the first time you hit the numpad icon, instead of numpad showing up, whitespace does (the numpad overlay/window appears, but the contents are not correctly painted and I wasn't adventurous enough to try randomly jabbing things, but I suspect the buttons may not work).

IF you backed out of this messed up display to regular dialer window, then hit the numpad icon again, number pad window shows up and works correctly.

Madriss solution (changing the Animation duration scale in the developer options under settings) does make this behaviour cease and numpad comes up correctly the first time. Thank you Madriss! :) :dancing2:

I experienced this issue all the way up to and including a current 4.4 release of Android for my Nexus 4. They have not fixed it.

The nature of the issue suggests some sort of timing/initialization issue the first time the numpad window is required after dialer start. The fact changing the animation duration slightly fixed it probably confirms that.

Now, it's ridiculous to have to change a developer setting to a non-default setting to get your MOST BASIC FUNCTION on a phone to not glitch.

Any answer that starts with 'The problem will go away if you factory reset your phone....' is also a big FAIL (someone else suggested this, Madriss answer does not require this). I probably have 100 apps installed and configured plus boat loads of data on my phone. Even if this could all be easily replaced, the time hit to do a full factory reset and then reload and reconfigure is on the order of 15+ hours I imagine. There's NO EXCUSE for this kind of solution to be required on what are CORE PHONE FUNCTIONS.

I can't believe the poor quality control that let this one ever get deployed to devices. Even the most basic dialer test would reveal this one and the dialer should have a high priority. I think Google frequently drops balls and this is one example (kind of like removing table of contents with page numbers from desktop Google Docs and never replacing it....WT#BBQ!!???). I've worked on a lot of large software projects and even the crappiest of companies would have thought twice about letting this one go out.

Tom

On my Nexus 5 I had this problem too where if I press the icon at the bottom to bring up the dialpad it would just give me a bit of white space, then I'd have to press back and then press it again to get it to appear.

I found another discussion about this here:
https://code.google.com/p/android/issues/detail?id=62394

It turns out I had "Animator duration scale" set to "Off" in the developer settings, and changing that to ".5x" fixed the problem for me.

Apparently the Nexus 4 had the same problem so maybe it's a similar thing happening with the Moto X.
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones