Recently I started getting this annoying freezing on my dialer. I'll go to enter a number or call a contact and I get this pop-up stating 'Activity Dialer (in process com.android.phone) is not responding.' and get the options to fc or wait. (tried to screenshot but I can't) If it takes to long and I fc, my signal get's an x then goes to the home screen. I've searched and didn't really find any help.
My question is, 1. is this common? and 2. how can I fix this? Any help would be greatly appreciated.
Device info is r800x vzw stock 2.3.4. thanks in advance.
1) Check if you have recently installed some new apps with bad compatibility.
A stock ROM should be functioning well all the time.
2) If you often gets an "x" which means poor phone signal; you may as well try a new Rom; or simply flashing a newer baseband.
3) I came across this "active dialer non responding" once too; when I used SetCpu to lock the lowest cpu clock at 138Mhz? or so; and it's proved that high-priority low CPU clock setting can generate this "active dialer non responding", as the cpu do not have enough power to respond at that low clock.:silly:
Thanks for the reply. The 'x' that I get is after I click to force close. Only for a quick second, then it gets signal again.
And I was using setcpu but I changed to antutu cpu master. Do you think if I upped the minimum settings that it might help it? Or do you have any other suggestions?
Use a new dialer?
Sent from my R800x using xda premium
How so? I use Go Dialer EX but it's the actual stock 2.3.4 r800x phone. I've actually tried using the Xperia S and another dialer but no other dialers actually worked...
Anyone else have any help?
Related
k i read about an app called spare parts on here so i figured hey i'll try it out. i did saw what extra setting were there and decided i wasn't gonna use it didn't even change any settings.
after opening the app and then pressing home something wierd happened i saw a white screen with HTC in green in the center for about 3-5 seconds my backround with a loading pop-up and nothing else for about another 3-5 seconds. this is happening every time i press the home button or exit out of an app. it's getting infuriating, i'm also getting wicked bad lagg in sense and lot's of hang up's and force closes. also wicked bad battery life. i don't know what to do to fix it.
i have the OTA and rooted last night with unrevoked method, this morning is when i tried the app around 10 or 11 not sure last couple days is a blur.
can anyone help, how can i restore what i had previously, do i have to do a full wipe.
nobody...... anyone plz, it is cripling my evo
thorpe24 said:
k i read about an app called spare parts on here so i figured hey i'll try it out. i did saw what extra setting were there and decided i wasn't gonna use it didn't even change any settings.
after opening the app and then pressing home something wierd happened i saw a white screen with HTC in green in the center for about 3-5 seconds my backround with a loading pop-up and nothing else for about another 3-5 seconds. this is happening every time i press the home button or exit out of an app. it's getting infuriating, i'm also getting wicked bad lagg in sense and lot's of hang up's and force closes. also wicked bad battery life. i don't know what to do to fix it.
i have the OTA and rooted last night with unrevoked method, this morning is when i tried the app around 10 or 11 not sure last couple days is a blur.
can anyone help, how can i restore what i had previously, do i have to do a full wipe.
Click to expand...
Click to collapse
get used to it if you intend to use sense, the screen you speak of is sort of like the htc sense/rosie intro. If you dont like it you can go vanilla and use another launcher, like adw froyo,launcherpro, or even the extra launcher thats included....
Sounds like you enabled aggressive handling of apps. Can you get in there to turn it off?
jmxp69 said:
Sounds like you enabled aggressive handling of apps. Can you get in there to turn it off?
Click to expand...
Click to collapse
Or just do a factory reset.
also, you are experiencing some isolated problems which leads me to beleive the issue is software related rather than hardware.I have experienced NOT ONE of the issues you speak of. Make sure you update prl. I can vouch for that one. My data was 90% broken till i did. Also try and wipe data, that would prolly fix everything as well.....FYI, i cannot gurantee the problem lies with your hardware OR software. Thats just my diagnosis. Good luck
Thats what it was the agressive handling of processes thanks alot guys feel like a fool.....
Sent from my PC36100 using Tapatalk
thorpe24 said:
Thats what it was the agressive handling of processes thanks alot guys feel like a fool.....
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Heh...I did that once on my hero. I know the feeling.
some versions of spare parts come with a launcher. the problem is that when you press the home button now, it's trying to goof with /system, which is forcing the reboot. even though you may be rooted, you don't have rw privileges in /system while messing with android.
you may be able to get away with accessing /system and erasing your goofy installed spare parts app. you'll have to do that through adb shell, and the custom recovery. do a search for 'remove apps', you should find it easily enough. i think the thread was moved from dev to general, or q and a.
anything that will call a write to /system (i.e. a rooted app that needs access to it to work right) has the potential to cause the phone to reboot. when i installed adfree, it had the same effect. trying to install hosts (which write to /system/etc) caused a reboot. i had to install hosts through recovery with a push after remount.
hope that helps
Hmm I installed autokiller and it appears to work doesn't mess with anything that is
I really dunno a way of testing that its actually working though if you where looking for a way to manage memory
I was using a task killer but read up on stuff and turned it off just keeping it in case I need it for something that wont close and the phone is running great and battery life keeps getting better and better.
Sent from my PC36100 using Tapatalk
autokiller
People you need to be careful with autokillers!
Make sure that you are not closing down sense items.
Put anything that says htc or sense on ignore.
If not you are shutting down parts of sense. Then sense has to reboot. Witch is why you see the white screen with the htc logo in the middle.
Hi guys, I have some problems with default dialer basically it takes about 20-30 seconds to load but after it loads itself then I can send it to background and and open it again with call button and it appears immediately. Unfortunately after some time system closes it again(?) and again it takes a while to open it. My question is can I setup my system in the way that it will not close dialer? I want to keep it running in the memory after the first load. Can it be done?
renice is 'supposed' to help this.
but I would also like to have the phone pinned-on.
I often will open the dialer before setting the phone to sleep.
it will wake up for calls much quicker this way.
but if you are using any other apps the dialer will close.
I am sure this will be fixed. it seems to be a popular issue.
mnjm9b said:
renice is 'supposed' to help this.
but I would also like to have the phone pinned-on.
I often will open the dialer before setting the phone to sleep.
it will wake up for calls much quicker this way.
but if you are using any other apps the dialer will close.
I am sure this will be fixed. it seems to be a popular issue.
Click to expand...
Click to collapse
There is a difference between the dialer and the phone. The dialer is actually Contacts.apk. The phone app which is called by the Dialer is Phone.apk.
The renice thing that people experiement with is about giving Phone.apk, or actually the process com.android.phone higher priority to speed up incoming calls. Usually that also means giving mediaserver higher priority also as it is responsible for playing the ring signal.
Contacts on the other hand is loaded fast if it's still in memory, sleeping, but if you have run other apps there is a good chance that it has been closed down. This is when it will take a long delay to start the Dialer (or Contacts as it's the same app). Renice:ing it will propably not make much difference.
Perhaps there are ways keep in the memory but I do not know how. What I do know is that increasing the memory can help keeping it there a little longer and that can be done with compcache. Compcache is compressed swap that in RAM. It's also possible to make more complicated setups with compcache that works togheter with a swap area on the SD-card.
In VaniljEclair Compcache can be enabled from within Spare Parts (in settings) and it uses 25% of the RAM for swap and while it doesn't make a huge difference it at least helps.
Personally I use Dialer One (free app from Market) instead of the stock Contacts/Dialer and I think it actually may be a bit quicker when loading.
Thanks guys for your input it helped a lot. Unfortunately one dialer doesnt work too well on my kaiser Imust admit that it loads much fasterthan the default one but isnt very responsive after the initial load so i think i will stay with the default dialer for now.
-------------------------------------
Sent via the XDA Tapatalk App
-Arturo- said:
Thanks guys for your input it helped a lot. Unfortunately one dialer doesnt work too well on my kaiser Imust admit that it loads much fasterthan the default one but isnt very responsive after the initial load so i think i will stay with the default dialer for now.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
With dialer one I turn off the "contact pictures" options and also vibration. works very well for me.
kallt_kaffe said:
With dialer one I turn off the "contact pictures" options and also vibration. works very well for me.
Click to expand...
Click to collapse
Thanks, Kalt I tried it again and it's working fine now maybe because i finally created 2 ext partitions and both data and system were placed on them.
Also I have another issue Suddenly my power button stopped turning the screen off i can only invoke a menu with " reboot, turn off,etc." options. What could have go wrong?
-Arturo- said:
Thanks, Kalt I tried it again and it's working fine now maybe because i finally created 2 ext partitions and both data and system were placed on them.
Also I have another issue Suddenly my power button stopped turning the screen off i can only invoke a menu with " reboot, turn off,etc." options. What could have go wrong?
Click to expand...
Click to collapse
check the panel and pm.sleep variables in your default.txt/startup.txt
Perhaps you've changed one of them by mistake?
Thanks Kalt actually I have managed to sort it out by assigning "sleep"action to the end call(red) button under spare parts which automatically fixed my power button.
Sent from my HTC Kaiser using XDA App
every other time my phone rings I cant answer it. The accept button just wont move?? is it just me or have anyone else had this error I have a dezire z
Do you have set CPU set to 245MHz @ screen off?
no i dont, why?
Well that could be one cause, maybe it's a bad app causing your phone to temporarily freeze? Can you slide it the other way and ignore the call?
Did you try flashing a different kernel?
Sent from my CyanogenMod powered G2.
Utorrent76 said:
Did you try flashing a different kernel?
Sent from my CyanogenMod powered G2.
Click to expand...
Click to collapse
why do you suggest this? how do you know hes using kernels? im just trying to see what your connection to the solution is -its quite a specific answer to a problem that hasnt really been examined. what rom is he on, etc before you can start talking about kernels -- so can you clarify?
accept button - do you mean the slider? if you have cmod - just activate settings to disable lock menu/trackball/ whatever --also you could try the no-lock unless you have security issues.
if no cmod -- theres apps to reduce the lockage -- that may help you get your phone calls but still doesnt fix the problem? you could try enomther's and his awesome extra ssettings app has all those options
Thanks for your help, well it is my wifes phone and it is fresh from the store, just a bunch of apps installed.
I will try some things and see if i can figure it out. And yes it is the slide button, can that be switched for a push button, Is it theme based or in the dialer?? hope you understand what i say.
jaypeg123 said:
Thanks for your help, well it is my wifes phone and it is fresh from the store, just a bunch of apps installed.
I will try some things and see if i can figure it out. And yes it is the slide button, can that be switched for a push button, Is it theme based or in the dialer?? hope you understand what i say.
Click to expand...
Click to collapse
If its a stock DESIRE Z and not a G2 then I think it's safe to assume its got sense on it and not AOSP. Did you try hard resetting it? (power down and pulling the battery for at least 30 sec) other than that id check for any OTA updates in the settings menu. OR if you're willing/know how, you can root it and run CM or virtuous. Both ROMs are excellent. If you do that and the problem persists, it could very well be a faulty unit. You have a lot of options!
I found I had problems answering calls when I had a specific make of screen protector on the phone. As soon as I took that off and went back to a previous one I'd used then it was fine again ! It's a long shot, but I thought I'd throw it in there.
Problem solved, An update did the trick, thanks for helping out my friends,
same problem , cannot answer with swipe keys
I have the same problem, which update did you use
same problem , cannot answer with swipe keys
I have the same problem, which update did you use
Sometimes when my phone rings I can't get it out of lock to answer the phone. When the caller hangs up only then I can answer. This is intermitant. I don't know what to do.
Running the stock ROM, and rooted with unrevoked.
michelbites said:
Sometimes when my phone rings I can't get it out of lock to answer the phone. When the caller hangs up only then I can answer. This is intermitant. I don't know what to do.
Click to expand...
Click to collapse
What ROM are you running? Rooted or not rooted? These are things you should remember to post when you're having issues. Makes diagnostics much easier
All I have done was root it. I didn't install any rom or anything. I only rooted it to get the wifi tethering.
So screen turns on, but you are not able to press "answer" when a call is incoming?
Its telling you to hang up on stock rom and go custom. Plus you have better support specially being in this community.
Just saying
Sent from my ADR6300 using XDA App
nikon_rh50 said:
Its telling you to hang up on stock rom and go custom. Plus you have better support specially being in this community.
Just saying
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
I'm inclined to agree. Custom ROMs definitely go waaaaay above and beyond the stock one. I use a combination of MyBackup Root and Titanium Backup free for contacts/messages and apps, respectively. Once you go custom, you never go back
What I was trying to say is that the screen is locked when the phone rings and then when I go to answer the phone it will not unlock until the phone stops ringing. But like I said in the first post this doesn't happen all the time. I would say about 25% of the time it does this. Sooo... Thats what I was trying to say.
Are you using Google Voice?
Are you using Google Voice to direct your calls? I have 3 phones that GV directs my calls to, and I've noticed that sometimes that causes one or the other of the phones to ring "late". Sometimes the Inc, sometimes not. I don't notice an issue when someone calls my direct line to any of the phones.
I am wondering what you would get if you use an app like No Lock that disables the lock screen.
I started using it when I had a roms lock screen fighting with a launcher's lock screen. I would get stacked lock screens, but only sometimes.
Running without a lock screen is not for everyone, so think about how you use your phone before disabling this great security feature. For me, my phone never leaves my side, and I mean NEVER. And if a "friend" starts poking at my phone I start poking in their face or purse... They learn after awhile.
reisa said:
Are you using Google Voice to direct your calls? I have 3 phones that GV directs my calls to, and I've noticed that sometimes that causes one or the other of the phones to ring "late". Sometimes the Inc, sometimes not. I don't notice an issue when someone calls my direct line to any of the phones.
Click to expand...
Click to collapse
I thought it was GV also but its not I uninstalled it and it would still do it.
Manitook said:
I am wondering what you would get if you use an app like No Lock that disables the lock screen.
I started using it when I had a roms lock screen fighting with a launcher's lock screen. I would get stacked lock screens, but only sometimes.
Running without a lock screen is not for everyone, so think about how you use your phone before disabling this great security feature. For me, my phone never leaves my side, and I mean NEVER. And if a "friend" starts poking at my phone I start poking in their face or purse... They learn after awhile.
Click to expand...
Click to collapse
I'm not sure if I would like the no lock because I tend to put my phone in my pocket all the time and it would just turn on and pocket dial people. LoL
Manitook said:
Running without a lock screen is not for everyone, so think about how you use your phone before disabling this great security feature. For me, my phone never leaves my side, and I mean NEVER. And if a "friend" starts poking at my phone I start poking in their face or purse... They learn after awhile.
Click to expand...
Click to collapse
App protector sounds like a good app for you.
Sent from my ADR6300
SetCPU?
Assuming screen is off when it cannot be unlocked - but...
Are you running SetCPU w/ a low screen off profile?
If not, maybe install SetCPU, and set a higher frequency in the screen off profile settings.
SetCPU is available in the market; it's also available as a free d/l for XDA members here on XDA.
smtom said:
Assuming screen is off when it cannot be unlocked - but...
Are you running SetCPU w/ a low screen off profile?
If not, maybe install SetCPU, and set a higher frequency in the screen off profile settings.
SetCPU is available in the market; it's also available as a free d/l for XDA members here on XDA.
Click to expand...
Click to collapse
Good call, I do remember when I was revving CPU way down with screen off. When it had been off for ~1-2 hours it'd be sluggish and take a bit for the CPU to rev back up. Never used it that long though because the Kernel I'm using now does this and using setCPU just chews up battery.
POQbum said:
Good call, I do remember when I was revving CPU way down with screen off. When it had been off for ~1-2 hours it'd be sluggish and take a bit for the CPU to rev back up. Never used it that long though because the Kernel I'm using now does this and using setCPU just chews up battery.
Click to expand...
Click to collapse
Well, there's something to try then - if the kernel is making the device slow to wake, use SetCPU to bump up the screen off profile and see if the issue persists.
Couple folk note just this issue in the kernel threads.
This is a known problem I struggle with myself. You may find that you can stroke up to deny the call but not unlock. It seems that this is some kind of grounding problem. Hearing that I tried setting the phone down and swiping while I wasn't touching it otherwise with some success. I've heard a quick cycle of the power button followed by an immediate swipe down can work. Some report pressing the screen firmly before swiping works. I usually just swipe up, call back and say "sorry about that, what's up?" After all, most people are used to drops and stuff because of Iphones.
I periodically goog "incredible can't answer" looking for the golden bullet.
Hi,
Sometimes when i click Home button Middle-Bottom of the screen.
physical buttons's Backlight turning on but screen doesn't come up.
I have to try at least 5-6 more times for screen to show up.
What is wrong with my phone ?
It's just sometimes really annoying..
Thank you for reading.
Best Regards.
UP
Using the latest FW ?
From my sexy LT15i
Do you use any custom Rom/kernel?
Sent from my Xperia Arc using XDA
Seems like extreme lag to me. The next time it happens check with a program (like OS monitor) the cpu usage. The situation that you described happened to me once, the MtpApp process was using 100% cpu and i couldn't use my phone properly until i rebooted it.
I faced a similar issue on a Xperia Ray
Its hardware i guess, flashing stock didnt work for me
What i say is you should flash stock FW
Thank you for all those answers !
I'm using DoomKernel 2.32.9 ( I Guess it's 19v )
2.3.7 Modded GB Deluxe Edition ( http://forum.xda-developers.com/showthread.php?t=1533332 )
It was happening more before i started using Modded GB Deluxe Edition.
But it is still happening, and still a lot annoying..
Thank you for reading.
Best Regards.
If your using a program like SetCPU or no-frills cpu control make sure that the minimum clock frequency is not set to 122MHz. Try set it to atleast 245MHz. I tried setting the "screen off" CPU to the minimum on SetCPU before in the hope to get more battery life, but whenever I wanted to wake the phone there would be a 2-3 second lag before the screen showed up. I hope this helps.
I guess this will work.
remove your SD card, connect it to a PC & format it, Insert it back.
@adielee
I wasn't using anything like SetCPU back than. So it can't be the problem.
Thank you for your answer.
@Kajendran
Okay, will try it. Sounds like a good idea.
But why is this hapening ?
oojjii said:
@adielee
I wasn't using anything like SetCPU back than. So it can't be the problem.
Thank you for your answer.
@Kajendran
Okay, will try it. Sounds like a good idea.
But why is this hapening ?
Click to expand...
Click to collapse
Maybe you can try flashing the stock kernel to test? i tried flashing a non-stock kernel a few times before and results were mixed and never perfect for me (don't really know why). Sometimes it would randomly glitch and the screen would turn black for about 1/2 a second or something. Wifi would sometimes be intermittent despite flashing the modules for some as well.
I'm not experienced enough to fully understand but I'm thinking that it could be a regional thing? I mean, how signals differ between regions?
So.......
Did it work........