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.
Related
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
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.
Not sure how to describe this other than sometimes the phone just doesn't turn on.
It's very odd, and I can't always recreate it, but sometimes I can.
Occasionally, if I get a notification and the screen comes on then after 10 seconds it will time out and turn off automatically (this is normal). At this point, if I press the power button to turn the screen back on within 5 minutes of it turning off then it doesn't come back on. The back and menu buttons light up, and the volume works, I can even answer a call with the home key and the phone works. The screen just doesn't come on.
If I press the button 4 or 5 times in a row, it eventually wakes up. Sometimes, I have to hold the power button to cause the power menu to come up, that will sometimes wake up the screen. This makes me think there is some system process hanging causing the screen not to display until it unfreezes, but I can't tell what that is.
This happens to me at least once a day and I can't figure it out.
I'm on android 4.4.2 with SHOstock-i v5.0 with MDL baseband.
I did some research, there are threads where other people were talking about almost the exact same issue, but a different rom and a different phone. Does this mean it's a hardware failure issue or some specific setting/app causing it? This is driving me crazy.
What I have tried:
Reflashing the ROM
Flashing ROM with full wipe
Throttling CPU (since disabled)
Alternative Kernel (although no one else is complaining of this issue)
Uninstalling random apps to see if it goes away (hard for me to run without any apps)
Have you tried the new 6.1? I'm running it and it is very smooth. I had similar issues on the att version of Shostock. I can't say whether the full wipe or the new rom fixed my issue, but it is running smoothly now.
You could also try running Greenify.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
XGhozt said:
Not sure how to describe this other than sometimes the phone just doesn't turn on.
It's very odd, and I can't always recreate it, but sometimes I can.
Occasionally, if I get a notification and the screen comes on then after 10 seconds it will time out and turn off automatically (this is normal). At this point, if I press the power button to turn the screen back on within 5 minutes of it turning off then it doesn't come back on. The back and menu buttons light up, and the volume works, I can even answer a call with the home key and the phone works. The screen just doesn't come on.
If I press the button 4 or 5 times in a row, it eventually wakes up. Sometimes, I have to hold the power button to cause the power menu to come up, that will sometimes wake up the screen. This makes me think there is some system process hanging causing the screen not to display until it unfreezes, but I can't tell what that is.
This happens to me at least once a day and I can't figure it out.
I'm on android 4.4.2 with SHOstock-i v5.0 with MDL baseband.
I did some research, there are threads where other people were talking about almost the exact same issue, but a different rom and a different phone. Does this mean it's a hardware failure issue or some specific setting/app causing it? This is driving me crazy.
What I have tried:
Reflashing the ROM
Flashing ROM with full wipe
Throttling CPU (since disabled)
Alternative Kernel (although no one else is complaining of this issue)
Uninstalling random apps to see if it goes away (hard for me to run without any apps)
Click to expand...
Click to collapse
Not familiar with your rom but I know any rom I have tried where idle speed is set to 182 I find the occasional freeze then pushing too many buttons causes a reboot. The rom I am using now has the min set to 384 MHz and that seems to work very well, not one wake up issue or reboot. Depends if your kernel has a tweaker tool or not. Currently using googy-max kernel which comes with a tweaker.... you would need to research if it is compatible with your rom though..... this kernel set on battery profile gives me currently 1 day 20 hrs.... screen on time 2 hrs... battery left... 44% pretty good I'd say....
Gage_Hero said:
Not familiar with your rom but I know any rom I have tried where idle speed is set to 182 I find the occasional freeze then pushing too many buttons causes a reboot. The rom I am using now has the min set to 384 MHz and that seems to work very well, not one wake up issue or reboot. Depends if your kernel has a tweaker tool or not. Currently using googy-max kernel which comes with a tweaker.... you would need to research if it is compatible with your rom though..... this kernel set on battery profile gives me currently 1 day 20 hrs.... screen on time 2 hrs... battery left... 44% pretty good I'd say....
Click to expand...
Click to collapse
I don't think I can change the clock speed with my kernel. I will try that but I'm not sure that's the issue since the phone appears to be functioning even when the screen is stuck off. You might be on the something, if I press too many buttons that's usually how I can cause it to reboot/crash.
Try using cpu spy to see what the minimum clock setting is. Shostock 6.1 appears to be 384
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Red_81 said:
Try using cpu spy to see what the minimum clock setting is. Shostock 6.1 appears to be 384
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
Yes, I am on v5.0 and it's set to 384. The issue might not be the clock speed.
This ROM doesn't have support for manually changing the clockspeed anyway.
Any other ideas?
I noticed we both had 32gb. Maybe the tolerances on the chip are not quite as good as the 16gb. I did play with cpu settings because waze would cause my phone to really heat up.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
I have since changed to a different kernel and I have not had the issue yet (~13 hours running).
I can only assume this is a bug with the kernel until I have the issue again. My attempts to recreate it on the new kernel have failed.
XGhozt said:
Not sure how to describe this other than sometimes the phone just doesn't turn on.
It's very odd, and I can't always recreate it, but sometimes I can.
Occasionally, if I get a notification and the screen comes on then after 10 seconds it will time out and turn off automatically (this is normal). At this point, if I press the power button to turn the screen back on within 5 minutes of it turning off then it doesn't come back on. The back and menu buttons light up, and the volume works, I can even answer a call with the home key and the phone works. The screen just doesn't come on.
If I press the button 4 or 5 times in a row, it eventually wakes up. Sometimes, I have to hold the power button to cause the power menu to come up, that will sometimes wake up the screen. This makes me think there is some system process hanging causing the screen not to display until it unfreezes, but I can't tell what that is.
This happens to me at least once a day and I can't figure it out.
I'm on android 4.4.2 with SHOstock-i v5.0 with MDL baseband.
I did some research, there are threads where other people were talking about almost the exact same issue, but a different rom and a different phone. Does this mean it's a hardware failure issue or some specific setting/app causing it? This is driving me crazy.
What I have tried:
Reflashing the ROM
Flashing ROM with full wipe
Throttling CPU (since disabled)
Alternative Kernel (although no one else is complaining of this issue)
Uninstalling random apps to see if it goes away (hard for me to run without any apps)
Click to expand...
Click to collapse
I haven't experienced this with my GS4. But with my GS2 I had this problem and it seemed to happen with custom Kernels and with the min set to 182. I seen someone else mention this too .. The fact I haven't seen this yet is probably because I cant underclock being my bootloader is locked and I cant flash a custom kernel..Have you tried a different scheduler . It seemed to be worse on my gs2 when I had it set to NOOP. Hope you get this figured out because I know how frustrating it is to have as a problem..My Gs2 almost turned into a 70 mph fastball into a brick wall numerous times EDIT .. My fault I didn't see your post about it being set to 384 already
spirodave said:
I haven't experienced this with my GS4. But with my GS2 I had this problem and it seemed to happen with custom Kernels and with the min set to 182. I seen someone else mention this too .. The fact I haven't seen this yet is probably because I cant underclock being my bootloader is locked and I cant flash a custom kernel..Have you tried a different scheduler . It seemed to be worse on my gs2 when I had it set to NOOP. Hope you get this figured out because I know how frustrating it is to have as a problem..My Gs2 almost turned into a 70 mph fastball into a brick wall numerous times EDIT .. My fault I didn't see your post about it being set to 384 already
Click to expand...
Click to collapse
This might be related, but I'm not sure. The new kernel I'm on is actually set to 189Mhz - 1998Mhz and I have yet to have the issue happen again.
XGhozt said:
This might be related, but I'm not sure. The new kernel I'm on is actually set to 189Mhz - 1998Mhz and I have yet to have the issue happen again.
Click to expand...
Click to collapse
Right on .. Sounds like a kernel issue to me also ..I ran into the problem more often when I was playing music with the screen off .. Mind you that was on my tmobile gs2..It seemed to me that when any button was pressed to turn the screen on It was like it wasn't scaling through freqs enough to power on.. Hopefully your issue is resolved ... Now I know if I run into this issue in the future ill know its kernel related
I just wanted to follow up here. I noticed the issue happen again but this time it was right after I made a change. I'm using GO TaskManager EX and there is a setting in here to "Clear when turn on screen" and "Clear when turn off screen". When either of these are enabled then it causes the device to take an extra 15 seconds to wake and/or it doesn't wake at all.
Still not 100% sure if this was the original issue, but I thought I would post it in case anyone else is using this as well. Especially since it caused a similar behavior.
Major face-palm moment.
Hi guys
I recently bought an OnePlus 2. With the original firmware, I experienced a very strange and very annoying issue: My screen randomly turned off (e.g. during a chat in WhatsApp). The screen turns off and I have to turn it on again by pressing the power button. Then I enter my PIN to access my phone again and it locks AGAIN. This happens like 10 times in a row, then I have to reboot the phone and it was OK again. I seriously don't know what triggered this issue.
However, recently I got pissed of because I tried to call one of my customers and as soon as I entered my PIN and tried to open the phone app, the screen locked again and I almost threw away my phone. Damned troll.
So I decided to try another ROM as I thought it was an OS-related issue. Now I'm running Exodus Android 6.0.1. I did a clean install and guess what: The issue came back on this ROM...
In my opinion there's only something both installations (my previous 5.1.1 stock ROM and my current 6.0.1 ROM) have in common: I've been using XPosed with Amplify, Greenify and XPrivacy. Other than that, I have no idea what it might be.
Have you encountered the same or a similar issue? If so, were you able to solve it? How did you solve it?
I just uninstalled Amplify, as I think it stops somehow the Gyroscope service, that's why it locks randomly. I'll check if the issue appears again...
I think I have good news for you guys: I guess I was able to locate the issue.
I noticed it always happened when I was holding the phone in the hand I had a ring on my finger. Then I found out the phone has magnetic sensors (for flip covers).
I downloaded the Xposed module "Magnet Sensor Control", the bug hasn't appeared so far!
I hope I was able to help you guys with my findings. This thread may be closed now.
So, I have a very curious problem with my phone. Sometimes, randomly, usually when playing video, my navbar and statusbar disappear completely, and then everything just goes to black, my wallpaper comes up, and then my lockscreen. The phone just locks itself. I use fingerprint, but I need to enter the code to "enable fingerprint". I'm guessing System UI is crashing, but why?
I used to be on stock ROM (Marshmallow), stock kernel, rooted, and had Xposed installed. I had a ton of Xposed modules installed and frankly, I thought one of the modules was the problem. My phone would, as I described lock itself while doing somthing. It seemed to be random, but happened the most while watching videos on YouTube. Sometimes this would happen 4-5 times, and I'd find my wallpaper replaced with the factory default one.
I recently flashed Lineage OS 14.1 and ElementalX kernel, re-installed Xposed (though an incomplete version, the one made by the PurifyOS team) and enabled only 1 very minor module (Android Phone Vibrator). I was very unpleasantly surprised to see the same thing happening, yet again. Not necessarily after enabling the Xposed module . It only happened twice so far, (while using WhatsApp) but the symptoms are the same. My navbar and statusbar disappear, although this time the screen freezes, instead of turning off completely. I can still turn off the screen and open the power menu using the power button.
I can provide logs, or any other info necesarry really, but it's really hard for me to catch logs, because I can't reproduce the error. It's really driving me insane. Please, help me..
MMMedic said:
So, I have a very curious problem with my phone. Sometimes, randomly, usually when playing video, my navbar and statusbar disappear completely, and then everything just goes to black, my wallpaper comes up, and then my lockscreen. The phone just locks itself. I use fingerprint, but I need to enter the code to "enable fingerprint". I'm guessing System UI is crashing, but why?
I used to be on stock ROM (Marshmallow), stock kernel, rooted, and had Xposed installed. I had a ton of Xposed modules installed and frankly, I thought one of the modules was the problem. My phone would, as I described lock itself while doing somthing. It seemed to be random, but happened the most while watching videos on YouTube. Sometimes this would happen 4-5 times, and I'd find my wallpaper replaced with the factory default one.
I recently flashed Lineage OS 14.1 and ElementalX kernel, re-installed Xposed (though an incomplete version, the one made by the PurifyOS team) and enabled only 1 very minor module (Android Phone Vibrator). I was very unpleasantly surprised to see the same thing happening, yet again. Not necessarily after enabling the Xposed module . It only happened twice so far, (while using WhatsApp) but the symptoms are the same. My navbar and statusbar disappear, although this time the screen freezes, instead of turning off completely. I can still turn off the screen and open the power menu using the power button.
I can provide logs, or any other info necesarry really, but it's really hard for me to catch logs, because I can't reproduce the error. It's really driving me insane. Please, help me..
Click to expand...
Click to collapse
Tried in safe mode?
anhoxhrs said:
Tried in safe mode?
Click to expand...
Click to collapse
Well, that's pretty hard to do, since these "lockups" happen with long intervals not really consistently, so it'd be really hard to disable everything I installed and use my phone for a few weeks in that state.
@MMMedic Did you resolve your problem?
My Moto G4 Plus has started doing the same thing as you described, even down to changing the wallpaper.
My phone isn't rooted and I'm just using the stock Android.
I'm not sure what to do to fix it.
I think resetting your phone and start a fresh without restoring a backup and install only the apps you need would fix your issues..