phone dialer crash - Galaxy S I9000 General

Hey Peoples
Ive got android 2.2 (updated from telco) and i've noticed occasionaly the phone dialer will crash.
Someones it will not answer a call when I try slide my finger over answer (or hangup if i want to not answer).
Also after a call it doesnt always want to hang up when i press the hang up button, and the call stays connected.
The above problems are quite random but somewhat anoying. Just wondering if anyone else has the same problems ? And does anyone know of any other dialer software I should try using ?
Thanks heaps
Justin

I am having the same random problem. Randomly sms apps (the built in one and, i.e., handcent, stop working. Any suggestion or tip?

Factory reset would be my first step .
jje

Uf! I do not have such severe problems as justin911 (OP).
But I do get dialer crashes and after that the Dialer app is draining my battery thru partial wake.
Once it crashed when I was in contacts and searching for somebody, other times I got called by someone and after 2-3 sec of talk time my phone automatically hung up the call (I called him back 5 times, same thing happened, then I just rebooted the phone and it worked).
For me to get the dialer back and working normally I have to reboot the phone.
This problem occurs randomly and it started doing this in v2.2.1 (Doc's XWJS3+speedmod kernel), but thankfully up until now it only occured 3 times.

Hi!
I finally found a solution to phone dialer crashes (I did not have a dialer crash for over a week now).
According to marcedli and his post the solution is the "Memo.apk" file that needs to be in "/system/app" (everyone should have it, because it is Samsungs own app).
I did not have it because I flashed my own rom from Doc's Kitchen and I do not use it, but apperantly it is needed by the phone app.
I copied "Memo.apk" into "/system/app" folder, rebooted my phone and everything works now and I never had a dialer crash that it would then force my phone to stay awake.
If anyone uses the XWJS5 FW, here is the link to CWM updatable version for "Memo.apk" (or just extract the file and copy it using Root Explorer):
http://www.megaupload.com/?d=0A36K4P3
@justin911 (OP):
It is also possible that in your telco's ROM, "Memo.apk" file (it is "Memo" app in the app drawer) is not included, if it is included it is also possible that some other file was not included into the ROM that is needed by the dialer app or some telco's app is messing with the dialer app, not sure.
The solution would be that you flash Darky's ROM or use Doc's ROM Kitchen.
I hope I helped you or at least guided you on a right track!

After two weeks I got the partial wake of Dialer again.
It woke up my phone for 3h and drained my battery.
There is obviously something else going on for these Dialer crashes.

i have the same prob.
i just do a factory reset and dialer crash prob disappear.

I'm having similar problems.
Sometimes, my phone just won't call anyone. When I call a number, there's just a long almost silent noise - and then it just hangs up without any error message. Almost seems like it doesn't get a "line free" signal.
Reboot fixes it, but it annoys the hell out of me.
Flashed to JPY via spoofed Kies...
Anyone got an idea what this could be? :/

It's me again!
And this time I'm for 100% sure how to fix the partial wake usage on "Dialer"!
"Phone/Dialer" drains your battery when you're making a phone call thru the dialer/call log/favorites and then when you finish your call you just push the "power" button to end the call and/or lock & turn off display (and you do NOT wait for the phone app to go back to home screen or you do NOT press the "back" button). The phone app is now still working in the background thinking you're still on the phone and it's waking your phone up.
To "fix" this when ending a call thru Phone/Dialer always press the "back" button or make sure that you're in your "home screen" and not in the phone app (dialer/call log/favorites).
And I don't know if the Phone/Dialer is still running if you press the "home" button instead of the "back" button.
And I don't know if "Memo.apk" fix helped.
And I'm sorry, but I don't know any other solutions for your Phone/Dialer problems.

i had this problems on 2.2 which made me go for a change....now i just flashed 2.3.3 ill test it out for the week hoping to get rid of that problem

Related

Phone goes to sleep and won't wake up.

It all started when I upgraded to a new rom. So the first thing I did was ditch the rom and install a new rom. I was running Black 3.0.1 and now updated to Black Satin.
The time it takes to lock up seems to very. I have had times where I could leave it for 4hrs and then hit the power button and it comes to life, other times I can have it sit for 30mins and hit the power button only to find it won't wake up. When it is in its locked up state, it won't even receive calls. It just sits there with the top right led blinking green. Its really getting frustrating.
In order to get it to come back I have to push the reset button on the bottom of the phone with my stylus.
I have been reading as many "lock up" threads as I can on the forum and so far it seems that most are to do with Push Mail. Which I don't use.
Any suggestions will be much appreciated.
I dont know if its a ROM issue as my does this sometimes (dont know about incoming calls as i dont get that many anyway) I am on the stock T-Mobile rom
I dont use push mail either
doesn't happen much to me (now i said i bet it does it all the time )
I think it seems to do it when i havnt soft restarted it for a while, so it could be that the lock up is due to memory or something and it just needs a soft reset to clear it down
I also have this problem, only a soft reset makes the phone respond. This happens sometimes when the phone has only been reset an hour previously.
It also happened once during the night and caused my alarm to not go off, so I only made it to the office for 10:30!!
Did you guys find a solution or did the problem just go away?
bump
got the same problem.
For me the problem went away only after I installed a new radio and new rom. I honestly don't know what was causing the problem. But it went away and I am happy. There might have been an issue with an installed app, but I never did find any app that directly caused the issue.

Force close, Force close, Force close

so i'm having this issue which is horrribly irritating, everytime i go onto my browser, use music, and recently whenever i get a call some application always has to foreclose. Its usually google apps, phone, or browser, but its been many other things as well (i.e. cnn widget, bbc widget, gps widget, etc.) this has been preventing me from answering my calls or basically using my phone in gerneral. Also before the phone call app or watever you call it started foreclosing and my phone was asleep, it usually took such a long time for the phone to wake up that i would miss the call, the phone wouldnt even let me click the green answer button to answer the call. Now i thought the problem was with my rom, which at the time was JF 1.51 Tmobile version so i changed my rom to Haykuro. The problem still existed so i changed to cyanogen 3.6.8.1 at first the problem was no longer existent, but a few days back it started again. I have no idea how to fix this or how to cope with it but any help would be great. Thanks.
LOL I think you need to change the title... Foreclose is different than a Force Close LOL
It could be compcache or a background task that's using a lot of memory/cpu that's causing the force closes.

Dialer lag

Does anyone got noticeable delay in start of the call when tap contact from the call history list?
I suspect it started after latest (1.31.405.4) ROM installation and happens periodically - you just tap the contact and nothing happens (sometimes at all but sometimes it reacts after minute or so and suddenly starts to call).
There could be at least two causes:
1. No reaction on actual "tap" (hard to explain why it finally calls sometimes but I noticed that Call button could give different reactions comparing to clicks on actual contact)
2. Process that executes call is doing something in the background (freeing up memory? restarting? doing some sync?)
After it "breaks through" it works for some time seamlessly - you just touch the contact and it calls immediately but after some time (even after phone reboot) the glitch is back
NB. I uninstalled almost all apps (including beautiful Timeriffic) I've got from Android Market and prey it's not related to the Exchange Sync and apps around it... Let's see if I still have problem tomorrow.
same problem i got. any solution pls tell.
kvasnevsky said:
Does anyone got noticeable delay in start of the call when tap contact from the call history list?
I suspect it started after latest (1.31.405.4) ROM installation and happens periodically - you just tap the contact and nothing happens (sometimes at all but sometimes it reacts after minute or so and suddenly starts to call).
There could be at least two causes:
1. No reaction on actual "tap" (hard to explain why it finally calls sometimes but I noticed that Call button could give different reactions comparing to clicks on actual contact)
2. Process that executes call is doing something in the background (freeing up memory? restarting? doing some sync?)
After it "breaks through" it works for some time seamlessly - you just touch the contact and it calls immediately but after some time (even after phone reboot) the glitch is back
NB. I uninstalled almost all apps (including beautiful Timeriffic) I've got from Android Market and prey it's not related to the Exchange Sync and apps around it... Let's see if I still have problem tomorrow.
Click to expand...
Click to collapse
Same problem
it could be a memory leak or something who knows,
the phone hasnt been out for long and there may be more updates comming.
plus if its a performance problem then when android 2.2 comes out with the JIT compiler it should be faster
lifeis, do you have any applications (in addition to pre-installed) on your device?
Version 1
The more I observe situations when dialer "hangs" the more I suspect that it happens due to some synchronization. Already several times I noticed such behavior starts when "data" icon indicates some outgoing traffic but nothing comes back (no active incoming arrow). Could it be that it tries to sync contact (with Exchange? Twitter? Facebook? Gmail?) and at the OS level it sees that network is "available" (somebody here already complained about similar issues) so needs to time-out instead of skip that attempt and proceed with requested operation immediately?
mee too
Today i notice that when i press the contact and after i pres power button screen goes and comes and phone starts dialing. I think sync cause this. May be latest update they can solve this. I had a hero and hero did n't have problem like that.
Dialer lag present on my device aswell. its not often and oddly happens when no apps are running in background. I think it conflicts with whatever sync services may be syncing at the time one tries to make a call
Sent from my HTC Legend using the XDA mobile application powered by Tapatalk
Same with mine. There is also a lag when I press the "Sync All' immediately after a WiFi connection is established.
Hope they fix this as it is quite annoying. And also make Maps 4 "officially" available to Legend.
Same problem
I started after updating the legend software!
Anyone have a solution?
Is it possible to go back to earlier software?
HTC answer
Somewhat expected suggestion:
Thank you for contacting us. About the problem that you have mentioned t us, I can gladly help you wit that: Note: Please ensure to backup any important data first. Method 1: 1. From the home screen, press Menu 2. Select Settings 3. Select Privacy 4. Select Factory Data Reset 5. If prompted, enter the unlock pattern. 6. Tap Reset Phone 7. Tap Erase Everything 8. The phone will reboot to factory settings Method 2: 1. Power device off (Open battery cover on bottom of the handset the close it again) 2. Press and hold the Volume Down button 3. Briefly press the Power button. 4. Continue pressing the Volume Down button until you see a white screen with three skateboarding androids at the bottom. 5. Release the Volume button 6. Press Volume Down to highlight CLEAR STORAGE 7. Press Power button 8. Press Volume Up to confirm 9. Once the Factory Reset has completed the phone will reboot automatically I trust that this resolve's your query, please do not hesitate to contact us again if required. Thank you for contacting HTC.
Does anyone willing to try? Not sure that I'm ready to spend another half a day restoring all settings and configurations after factory reset (also suspect that chances to succeed are not too high)...
Ah c'mon! that's like "hey do you have a problem with one application in windows? Ok that's the solution: go to ms dos and then type "format c:\"....
Ridiculus. HTC should just understand what's going on and release an update!
The reset actually works. I have not re-installed all of the applications i had before and did not use the backup file to restore the phone in its previous state so the dissappearence of the lag might be due to some setting being restored to default, but whatever the reason, the legend is now much faster.
Factory reset
Have you also installed latest ROM after factory reset?
kvasnevsky said:
Have you also installed latest ROM after factory reset?
Click to expand...
Click to collapse
Actually the update was still there after the reset - I didn't have to update again.
More observations
Interesting observations:
You try to call - dialer hangs
If you return to home screen you see that widget time is correct while status string on the top shows "outdated" time
If you try to browse some web page it connects and you see the content - I got feeling that this is some kind of "break thorough" since after that -->
Time at the status string gets updated
Almost immediately after that phone starts calling
Reset
Gave up and did factory reset - took couple of hours to restore it to the wanted state. Let's see if that solves the problem or I get issue back after returning configuration to the desired state.
Last observation I did before reset: problem disappears (or minimizes?) if I keep WiFi off - especially if Legend sees some network around but isn't connected. The same applies if it unsuccessfully tries to connect to some faulty router - most probably dialer lag starts after that...
Hi everybody,
Factory reset helped here. I didn't make lots of tests but after 3 days of using I didn't notice the lag.
Regards,
Michal
-------------------------------------
Sent via the XDA Tapatalk App
Hi everyone,
I had the same problem and the factory reset helped me,too.
I believe that either the rom update or one of the applications I have installed was causing the problem.
Now I will begin re-installing all the applications I had before and see if the problem will reappear again.
kvasnevsky said:
Last observation I did before reset: problem disappears (or minimizes?) if I keep WiFi off - especially if Legend sees some network around but isn't connected. The same applies if it unsuccessfully tries to connect to some faulty router - most probably dialer lag starts after that...
Click to expand...
Click to collapse
It appears that storing (remembering) wifi networks slows down connecting to any of them when present. When I only have one network remembered connecting to it is almost instant, while as soon as I remember other network setting, connecting to same network is much slower, even if is the only one present.

[Q] Lockscreen Wake Up Freeze and Reboot

Hi,
I've had my phone about a month now. I rooted it the day I got it. It seems like whenever I wake it up from long sleep or get a text message sometimes and try to wake it up, it freezes during the swipe and then randomly reboots. Sometimes it'll just make it to the att symbol and lock up again making me hold power down and then turn it back on. Then it works fine for a good period of time before the issue happens again.
tried- returning phone to stock. Didn't fix. Tried uninstalling att bloatware, not as frequent now but still happens. I have tried underclocking using rom manager. Didn't change anything. Next step maybe to try a custom rom and see if maybe there's a problem with my factory rom? Right now im in safe mode to see if its a third party app.
Is anyone else having this problem or should I consider warranty issue?
Not a third party app
It just did this in safe mode, so it must not be a third party app issue. I'm thinking about trying to install wicked rom following directions on galaxys4root.com. If it still freezes I think it may be a hardware issue.. Anyone have any thoughts?
alt keyboard?
My phone was/is doing the same thing. It seems to me like the phone is working now and I haven't had it freeze up since last night. Every time I install Swiftkey it starts freezing up and I have to pull the battery to reboot.

Dialer freezes

Has anyone come across this issue which I have lately with any of the custom roms that I try?
description:
the dialer freezes either when you try to answer an incoming call or even when you try to initiate a call. Dialer freezes completely, you can't kill it and no button is responsive, it doesn't crash though. Pressing the home button may take you to desktop but if you pull the notification list, you can still see the icons that show that the phone is still in dialing mode. During that time, if anyone calls you the phone is unresponsive so it is directed to voicemail. When this happens, restarting and trying within short interval will reproduce the problem. I noticed that it usually happens with low battery level.
I have tried to uninstall callrecorder (which I was suspecting was relevant), uninstall xposed in order to disable all exposed modules (in case any of those was interfering). It also used to happen on other ROM so it must not be something specific to any ROM, maybe the base though because I only experienced this on XXUGNG8 base.
My latest idea was to put back my oem Samsung battery as I was using a Mugen battery but again the same never happened with any of the older roms
Any feedback is welcome.
Sent from my GT-I9505 using Tapatalk
I would try the standard things.
Your old battery.
Different base rom or even try an aosp rom.
Maybe a full wipe.

Categories

Resources