Hello
I am using the ROM tazet (CM7-111118-1809-nightly-Milestone2). I'm very happy, put this as the original ROM still has a problem locking the screen
when the phone receives a call and finds himself in the pocket ..
Anyone know how to solve?
Not sure how to just fix it as is, but you could try applying endless7's patch for tezet's cm7. It's amazingly fast so I think you would like the changes it makes
Sent from my A953 using xda premium
Related
I have a Wildfire that is still stock standard. 2.1 update 1. I am still reading up on how to root and will be doing that sort of thing soon. However this phone has a annoying intermittent problem. Sometimes when I get an incoming call and to answer one would swipe your finger downwards, nothing happens. So I miss the call. But this happens only sometimes, but enough to be an annoyance.
Anyone have a similar issue?
yes, it happens to me too...
And it happened to we with various wildpuzzle roms.
Dont know what to do...
me too, pls help
I have the same problem to ...
me too. having the same problem
My friend on 2.1 has the same issue. Fine on my one running froyo (stock)
Sent from my HTC Wildfire using XDA App
So everything works like a dream except for calls (and the battery but I've got that under control). I try to call someone, it shows that the call connects, but I can't hear anything and neither can the other party. The only way I hear anything is if i turn the speaker phone on using the LAB (left action button or menu button) in call.
Any one got a fix?
Thanks in advance and thanks to everyone who are putting work into this project.
Same here, tryed microfoon fix but did not help.
edit: rebooted a few times and used volume buttons when calling. works now
having similar issue tho i can hear them speaking to me, but the other side can't hear me... it's not a mic problem cos the "voice recorder" app works just fine... have you found any solutions so far, as i ask about the same issue 3 months later?
Try updating to 2.0 M5 (2.3.4)
Sorry to bump an old thread but I really want to get back onto swiftdroid.
Has the in call issue been fixed yet??
Sent from my GT540 using XDA App
niklfc83 said:
Sorry to bump an old thread but I really want to get back onto swiftdroid.
Has the in call issue been fixed yet??
Sent from my GT540 using XDA App
Click to expand...
Click to collapse
Yes, calling works fine now.
Thanks for letting me know, I'll flash rc1 tomorrow.
Sent from my GT540 using XDA App
niklfc83 said:
Sorry to bump an old thread but I really want to get back onto swiftdroid.
Has the in call issue been fixed yet??
Click to expand...
Click to collapse
Update to 2.0 RC1
As many others, my HD2 freezes after a call when using Android (with WM6.5 and WP/ the issue doesn't ocurr).
With ICS, though the screen goes black during a call and it's impossible to activate it, when the call ends all goes back to normal, without being necessary to pull out the battery.
Does the same happen with you?
No Try a different Rom
My HD2 does this all the time. If you fix, tell me plz. I use Screebl Lite and SpeakerShake(I think) to make it go on so I don't have to pull the battery out.
Sent from my LG-VM670 using Tapatalk
IM HAVING A HUGE PROBLEM
Ok well first my phone is currently off, I own a Tmobile G2 aka HTC Vision
When my phone is off i can still recieve calls but i cant make any outgoing calls (Tmobiles magic)
so when my phone is off i use google voice to text and keep up with friends but lately after installing this ROM 7.0.3 the majority of all my incoming calls I never recieve or im not notified about
Google voice alerts me that ive missed a call, But when people call my phone it does not ring at all or even notifies me that ive missed a call ((( someone please let me know what is going you would be a life saver!!
Is there a reason you flashed CM 7.0.3 and not 7.1 (the latest stable)?
I'd at least try 7.1 first before trying to hunt down the cause of the issue.
I had the same problem with 7.0.1 too that was the reason behind the downgrade
xstarr15 said:
I had the same problem with 7.0.1 too that was the reason behind the downgrade
Click to expand...
Click to collapse
Still wondering why you haven't tried 7.1.0??
7.0.3 is newer than 7.0.1 btw
Sent from my HTC Vision using xda premium
Weird problem.
Technically saying, when u shut the phone off, most component of the cell stop working, not possible to receive a call, but in yr case i believe there's something wrong during the shutdown process, try logcat while u turn off the phone.
A possible is that, something hangs the kernel during the shutdown process (this happens sometimes even on a desktop), while the radio component still working and communicating with the base, so yr phone "receives" calls, but the system is freezed, it can't switch to the ringing process.
Do a wipe. Flash latest nightly.263
Sent from my SGH-T989 using xda premium
Karakoram2 said:
Do a wipe. Flash latest nightly.263
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
That isn't latest nightly
Sent from my HTC Vision using xda premium
Im not sure what i can do. Is it the radio? or do i need to flash a new radio or something i need serious help my phone will not ring at all and google voice is the only thing that is keeping track of all my missed call.
This is really annoying as I have to turn volume up every time after it automatically goes to silent mode.
Does anybody else have the same problem? or any idea for solutions?
My phone is rooted, using stock rom android version 4.2.2 and stock kernel.
Thanks for reading.
Having the same issue
Didn't have this problem before.. It started happening after i installed some applications..
But i don't know which application is causing this.. If we can find out a way by which we
can find the common ones it would be easier.. Are you using any dialer application like dialer ex or fake caller application.. Or it might be true caller. If you have any of these please let me know..
If you can't fix it ... Try doing a factory reset but don't forget to back up your data :S
Best of luck
Sent from my GT-I9000 using Tapatalk 2
Found the culprit
Found out avg was the culprit.. Many who are having nexus4 running on 4.2.2 jb had the same issue.. Removed it and now it's fine..
Thanks for your help..
Glad you fixed it
Sent from my GT-I9000 using Tapatalk 2