I've been running hashcode's CM10 build for about a week (KEXEC-cm-10-20121103-UNOFFICIAL-solana) and everything has been pretty solid except each time I end a call with somebody, the phone.android service crashes. This isn't a huge deal because it happens at the end of every call, but nonetheless, I'd like to get all the crashes figured out. Anybody else running into this issue in any JellyBean roms on the D3?
DRELUXOID said:
I've been running hashcode's CM10 build for about a week (KEXEC-cm-10-20121103-UNOFFICIAL-solana) and everything has been pretty solid except each time I end a call with somebody, the phone.android service crashes. This isn't a huge deal because it happens at the end of every call, but nonetheless, I'd like to get all the crashes figured out. Anybody else running into this issue in any JellyBean roms on the D3?
Click to expand...
Click to collapse
Yeah - it happens to me about half the time. I'm trying to figure out if it makes a difference whither it's an outgoing or incomming call or who hangs up first, but can't see a pattern yet.
djbolden said:
Yeah - it happens to me about half the time. I'm trying to figure out if it makes a difference whither it's an outgoing or incomming call or who hangs up first, but can't see a pattern yet.
Click to expand...
Click to collapse
It's fixed in the 12-12 build. Sensor works during phone calls now too.
Related
Does anybody know why my hero might be a bit slow at dialing? When I touch a number in my contacts, it takes up to 30 seconds before it starts connecting the call. Sometimes its instant, sometimes its a long time. If I press it twice, it'll try to three way call the person later.
What causes this, and how do I fix it?
I have this problem too as does my hubby's phone.
We have tried damagecontrol and fresh roms and it happens on both of them.
We also get issues with the internet and gps not working on and off so we have to reboot. Not sure at all if this is any way related to the phone calls being so slow to take.
would LOVE an answer to how to fix this!
a dialer without haptic feedback usually solves this, here's one for damage/fresh/sprint based roms. Other wise, try zen's slide rom, dialer works GREAT, fastest yet for me even with haptic on!
gapoochi said:
We also get issues with the internet and gps not working on and off so we have to reboot. Not sure at all if this is any way related to the phone calls being so slow to take.
Click to expand...
Click to collapse
I get the same problem as well. Usually its fixed by turning wifi on then off, or turning gps off then on respectively.
danaff37 said:
a dialer without haptic feedback usually solves this, here's one for damage/fresh/sprint based roms. Other wise, try zen's slide rom, dialer works GREAT, fastest yet for me even with haptic on!
Click to expand...
Click to collapse
I get this problem without even using the dialer though. E.g. going into people, touching a contact, then touching the phone number to call it. The phone just does nothing for a little bit then suddenly it initiates the call. Would changing the dialer still fix this problem?
not entirely sure... possibly, I think it still has to load the dialer app when you do that. Best I could say is just try it. If it doesn't, and you want the old dialer, just pull it from the original zip you flashed and adb push to system/app to replace the one I posted. But that dialer works much better, in my opinion
Mine does this too and has on the stock ROM as well as every version of damagecontrol since 2.06. Sometimes it will dial right away and other times it will wait 10-20 seconds, then turn the screen off and immdiately back on and then dial and other times it just waits however long it wants to start dialing.
I know when I was still on stock and not rooted it would sometimes go into a state where it wouldn't respond to any commands that would make it dial but every other function seemed to be fine. I don't believe that's happened since I rooted and ROM'd it though.
I've used the stock dialer and well as SuperDial and Dialer One and all have had the problem. I've had this problem with haptic turned off/removed and still on. Sometimes waiting a few seconds after unlocking will help but not always.
So far for me, 100% fix has been the slide rom or darch droid (which finally booted for me today!). Both those, not one issue.
-------------------------------------
Sent via the XDA Tapatalk App
Hi all,
Friend and I both have the Incredible S, loving it! He has a slight issue and I can't for the life of me solve it. Everything was working fine but now when he has an incoming call and the screen is off the incoming call screen flashes up briefly then disappears and device shows normal 'desktop' - you can't answer the call!
If you call his phone and the screen is active, incoming call screen pops up as expected and you can answer call.
Any ideas peeps?
Thanks
Ant
Hmmm,
I'm having the exact same problem. Running Fresh Evo on HTC Evo. Would love to know why this is happening. Any ideas?
Sliphorn said:
Hmmm,
I'm having the exact same problem. Running Fresh Evo on HTC Evo. Would love to know why this is happening. Any ideas?
Click to expand...
Click to collapse
Never worked it out, friend did factory reset in the end to fix it.
Ant
Bummer. Here's some info:
Latest Fresh EVO
Rom Manager
Rom Manager Janitor
Juice Defender Ultimate Juice
Titanium Backup Pro
Cachemate for Root
ShootMe
Adfree Android
adbwireless
Call Control (problem before this, though)
Launcher Pro
Any hints?
Having the same exact issue. This sucks... This started today for me around noon ( no calls before then), and has persisted throughout the day. Yesterday was fine.
I use Google voice for all of my calls.
The only thing I've done today that I haven't done every other day was that I installed the Gtalk app this morning. In the past, I've used Gmail directly. However, my computer was off during at least one of the phone calls I received today, so I can't imagine this could be it...
Perhaps because I installed gAlwaysIdle (an addition to Gtalk that makes you never go idle or always be idle) as well?
Does this correspond with anyone else's experience?
I'll probably just reflash my phone
<Rooted Atrix 4g running GingerBlur>
hmm this sounds like a serious firmware problem tho..
all i could suggest is flash a firmware that the most of the ppl are using, and dont got probs with...
well doing a good reboot seems to help alot these days. So disable the fastboot option en turn it off, wait a while (10 secs should be enough) en start the device again.
Also had some of the trouble like crashing things and this solved it for me. Give it a try and hope it will fix it.
Otherwise there seems to be no other way than a factory reset (go htc!)
I upgraded my Captivate to gingerbread/talon/continuum yesterday.
That went fine and everything was hunky dory.
Phone was working fine the whole day today, incoming/outgoing calls, data.
I came home and installed Skype and thats when all hell broke loose.
Now the phone part is dead (kinda!). I can make calls fine but if I get a incoming call, the call gets disconnected after 1 ring and I get a msg popup (like some error) but I cant really see what the message is.
I also noticed that it disconnects me from ATT network when a call comes in and then after a little bit it reconnects.
I also verified this by going to the About->Status screen and then making a call.
It normally says ATT but for a couple of secs after call drop it says 'Unknown'.
What did I do to screw it up and how can I fix it?
Thanks
Glaring obvious first question -- did you try uninstalling Skype to see if that resolved anything?
mK
mommehK said:
Glaring obvious first question -- did you try uninstalling Skype to see if that resolved anything?
mK
Click to expand...
Click to collapse
Sorry, I should have added that to my first post.
Yes, I did uninstall Skype and reboot the phone, just incase, but no difference.
Still the same.
Update:
After playing around with various things for a couple of hrs, I finally gave up and reflashed Continuum.
Everything started working again.
Applied my Ti backed up config and loaded Netflix. Same problem. Dialer died with an incoming call.
I reflashed Continuum again and everything started working as expected.
I then applied my Ti backup, still everything working.
I am in the process of updating all my apps and then lets see if everything is still working.
The only thing that is missing for now is the Netflix app.
I will keep everyone updated if its the Netflix app causing the issue or its the Skype.
activemind: Keep us posted if you find a cause. I am on a Samsung Vibrant (3g) via TMOB but have been having the same issue today with a completely different rom (simply honey). This is actually about the 6th thread I've found in the past two days having this same issue on Galaxy S phones.
I have had this problem before and what caused it was restoring system data with titanium. Make sure you are only restoring apps.
Sent from my GT-I9000 using XDA Premium App
I just recently decided to root my phone shortly after changing providers from t-mobile to family mobile which is run through t-mobile but cheaper. I figured fresh start all around right?
Well I rooted it, put cm10-or-10.1 linaro on it (forgot which) did some v6 supercharging (had no idea what I was doing, probably shouldn't have bothered) and everything was fine except when I would receive or make a call the phone app would freeze up and at times I could hear the person calling inbound but they couldn't hear me. I could call them back okay though. I figured I'd try a different rom, it didn't help. Now when I make outbound calls the screen freezes in the transition from pressing call to the screen it displays during the call, then the screen shuts off which I assume is the proximity sensor kicking in and then I can either turn it back on and the screen displays correctly or the hardware key lights come on but the screen stays black. Upon hanging up it just sits on the during call screen with everything grayed out for about 10-20 seconds before it finally goes back to home.
So far I've been through: the stock rom, peach sunrise, cm10 linaro and cm10.1 linaro and none of them have been error free. Is this a hardware issue that can be addressed? I've searched around for a topic similar but with no real luck. This is the closest I could get http://forum.xda-developers.com/showthread.php?t=1293442 and they seemed to come to the conclusion that it was an internal memory error.
tigane1 said:
I just recently decided to root my phone shortly after changing providers from t-mobile to family mobile which is run through t-mobile but cheaper. I figured fresh start all around right?
Well I rooted it, put cm10-or-10.1 linaro on it (forgot which) did some v6 supercharging (had no idea what I was doing, probably shouldn't have bothered) and everything was fine except when I would receive or make a call the phone app would freeze up and at times I could hear the person calling inbound but they couldn't hear me. I could call them back okay though. I figured I'd try a different rom, it didn't help. Now when I make outbound calls the screen freezes in the transition from pressing call to the screen it displays during the call, then the screen shuts off which I assume is the proximity sensor kicking in and then I can either turn it back on and the screen displays correctly or the hardware key lights come on but the screen stays black. Upon hanging up it just sits on the during call screen with everything grayed out for about 10-20 seconds before it finally goes back to home.
So far I've been through: the stock rom, peach sunrise, cm10 linaro and cm10.1 linaro and none of them have been error free. Is this a hardware issue that can be addressed? I've searched around for a topic similar but with no real luck. This is the closest I could get http://forum.xda-developers.com/showthread.php?t=1293442 and they seemed to come to the conclusion that it was an internal memory error.
Click to expand...
Click to collapse
Try aoip its up to date and works good.
schuylkillparanormal said:
Try aoip its up to date and works good.
Click to expand...
Click to collapse
working on downloading it but the download keeps failing -_-
When switching Roms second, third and .... times, did you do a rom wipe?
Sent from my Nexus 7 using xda app-developers app
Mwas. said:
When switching Roms second, third and .... times, did you do a rom wipe?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yes rom and cache/dalvik. And if I forgot I went back and wiped and re-installed it.
tigane1 said:
Yes rom and cachredowvik. And if I forgot I went back and wiped and re-installed it.
Click to expand...
Click to collapse
There's nothing wrong with the link try redownloading the ROM something might of got corrupted.
I fixed it. Kind of
I did a bit more searching using some different terms and people were having trouble with the proximity sensor on their phones causing similar problems so I turned mine off and the problem corrected itself! So now I guess I just have to deal without having a functioning proximity sensor during calls, oh well, not a biggie. I appreciate the help though guys.
Folks;
not sure where to put this - apologies if this is the wrong forum: Using CM11 nightlies (downloaded via CyanDelta) on my p880, I update to the recent builds fairly often. With the last two or three nightlies, I experience repeated audio issues while doing outgoing or picking incoming calls: By then, it seems the phone audio is muted or not working, I am not able to hear anything, but obviously the "other end" does hear what I say. I don't get no dialtone then, either, even though the call obviously is being established. In some situations, trying this two or three times helps. Sometimes rebooting the device helps. It's not generally there but a bit annoying. Is this a known problem? Anything I can do about this? In cm-11-20140920-NIGHTLY-p880, this problem(?) is still there.
TIA and all the best,
Kristian
kr428 said:
Folks;
not sure where to put this - apologies if this is the wrong forum: Using CM11 nightlies (downloaded via CyanDelta) on my p880, I update to the recent builds fairly often. With the last two or three nightlies, I experience repeated audio issues while doing outgoing or picking incoming calls: By then, it seems the phone audio is muted or not working, I am not able to hear anything, but obviously the "other end" does hear what I say. I don't get no dialtone then, either, even though the call obviously is being established. In some situations, trying this two or three times helps. Sometimes rebooting the device helps. It's not generally there but a bit annoying. Is this a known problem? Anything I can do about this? In cm-11-20140920-NIGHTLY-p880, this problem(?) is still there.
TIA and all the best,
Kristian
Click to expand...
Click to collapse
if you check official cm11 thread, you will see that the issue is recognised and is being worked on.
other than that, you can install 23.9. nightly, or wait till it's fixed.
cheers.
Thanks a bunch for your reply!