Related
I have a SPV m2000 with the latest rom from orange, the first problem i had was when you go to reply to a text you sometimes could only send 70 char. before you had a 2nd text, but that was sorted by this site by turning the use assci code off, the onlt other problem is this -
Sometimes when i go to make a phone call, i dont hear a dialing tone, but after a few seconds it starts counting up like in connected to the call. The person im ringing says that they got the call and they could hear me but i didn't reply. This has happened many times now, it seems to be after its been a long time since i restarted the phone, e.g in the morning etc
I was just wondering if anyone else had ths problem?
Silent Calls
I had this problem from day 1 with my M2000, and I had to soft reset to clear it. Recently updated Radio to 1.13 and Bluetooth to 3900 and problem hasn't re-occured. Of course this may be a coincidence... :roll:
Turn on BT and leave it on, even if you don't use it. This worked for me.
Sometimes when i go to make a phone call, i dont hear a dialing tone, but after a few seconds it starts counting up like in connected to the call. The person im ringing says that they got the call and they could hear me but i didn't reply.
Click to expand...
Click to collapse
There is a huge thread on this somewhere with a poll (survey) in it. Last time I checked around 76% of owners of this handset have the 'no sound in call problem' to some degree.
My old BA did it 2-3 times a day. My new one with 1.13 radio ROM does it less often, but the problem still remains.
If you are really unhappy, and need a reliable phone you obviously wont want the BlueAngel again! Take it back to where you bought it. They will try to deny it is a known problem and at best give you a new Blue Angel. My advice is to find the thread on here, print all 10 pages of it and take it to where you bought the phone. They won't be able to deny it with the evidence right in front of them. Make sure you show it where the public can see/hear so they have to try and talk their way out of it in fornt of an audience
I did this to prove that the whistling screen was a known common problem, not something caused through my neglect and so I was entitled to a new handset under my warranty, not just a new screen (Everyone said the problem came back despite a new screen as the problem is with the circuit board)
As I remember, about 1 in 6 Blue Angel users will end up with a whistling screen after owning the device for a month so you probably have that to look forward to aswell.
My 1.40 iMate ROM may have helped too.
Read the wiki and upgrade to wm5. Problem has not happened for me in months.
The other day I took my phone out of my pocket and set it down. I watched as it unlocked itself, opened a new text message, and began typing gibberish. I could see the letters on the keyboard popping up and then moving around before settling on a letter. It got through about three gibberish words before a phone call came through and the phone began ringing.
I have had this happen before (gibberish texts sent to people) but have never caught it in the act. It seems to happen when an event is happening on the phone - either an incoming call or an alarm going off. It's like some instructions are being sent in the phone internally but are being manifested through input on the touch screen or into the Google Voice SMS app.
Anyone else see anything similar or know what might be going on?
I'm running unrooted with the latest OTA updates.
gthing said:
The other day I took my phone out of my pocket and set it down. I watched as it unlocked itself, opened a new text message, and began typing gibberish. I could see the letters on the keyboard popping up and then moving around before settling on a letter. It got through about three gibberish words before a phone call came through and the phone began ringing.
I have had this happen before (gibberish texts sent to people) but have never caught it in the act. It seems to happen when an event is happening on the phone - either an incoming call or an alarm going off. It's like some instructions are being sent in the phone internally but are being manifested through input on the touch screen or into the Google Voice SMS app.
Anyone else see anything similar or know what might be going on?
I'm running unrooted with the latest OTA updates.
Click to expand...
Click to collapse
That is the most intense thing I have ever heard ever.
I'd root that baby. Maybe an Android "virus"?
jigglywiggly said:
That is the most intense thing I have ever heard ever.
I'd root that baby. Maybe an Android "virus"?
Click to expand...
Click to collapse
i dont believe android phone has viruses....maybe just program errors.
Its a ghost.
campchi said:
i dont believe android phone has viruses....maybe just program errors.
Click to expand...
Click to collapse
no viruses, YET!
gthing said:
The other day I took my phone out of my pocket and set it down. I watched as it unlocked itself, opened a new text message, and began typing gibberish. I could see the letters on the keyboard popping up and then moving around before settling on a letter. It got through about three gibberish words before a phone call came through and the phone began ringing.
I have had this happen before (gibberish texts sent to people) but have never caught it in the act. It seems to happen when an event is happening on the phone - either an incoming call or an alarm going off. It's like some instructions are being sent in the phone internally but are being manifested through input on the touch screen or into the Google Voice SMS app.
Anyone else see anything similar or know what might be going on?
I'm running unrooted with the latest OTA updates.
Click to expand...
Click to collapse
ok, first off...
secondly, your thread title alone is tempting enough for me to post a reaction.
thirdly, maybe there's a delay in your screen touch input? or maybe someone has remote access into your evo? (this is going to make me sound dumb and ignorant, but please bear with me).. i know there are ways to get access into iphones to control them via commands through text messages. maybe that's happening with your evo?? again, i'm almost embarrassed to even be entertaining this idea since android is quite locked down in its nature, but it's the closest thing i could think of as a possible cause besides paranormal activity.
...which, in and of itself, sounds so awesome and creepy.
I had similiar things happen when using any custom rom based off the new ota..
Its something with the screen sensitivity they changed for the ppl who were having grounding issues..its the only thing I can think of..
I think I also have a paranormal situation of my own! Well maybe, but its very curious... A certain phone number/friend of mine has told me that my phone is calling him while my phone is completely idle. This has happened twice in the last 10 days or so. The first day he missed the call, the second time he was able to answer it and it was dead air. My phone was never touched; it was home alone the first time and it was streaming bluetooth music the second time. I know this sounds absurd, but unless it starts happening more frequently I guess I'll just deal with the mysteriousness of it all.
oOflyeyesOo said:
Its a ghost.
Click to expand...
Click to collapse
the ghost would have to use a hot dog for the screen to recognize him/her LOL..
i myself dont believe in ghost but thats trippy.
lol a floating hot dog typing things by its self. WTH I just laughed out loud and nearly woke my wife up. That was funny if you picture it in your head lol.
When i got my first Vogue, it would do that. Randomly resend text, send garbled text, and call people. Without any interaction whatsoever.
Sent from my Evo using XDA App
That is hilarious. I would have freaked out seriously. Is your phone rooted?
My phone is not rooted and was running stock with the latest OTA. I am leaning towards the theory that it is something to do with the latest OTA which addressed the grounding issue.
I enabled a password on my phone. Last night I kept hearing these little noises, like a bug beating its wings in really quick, short durations. I was looking all over before I realized it was coming from my phone. Face down, on my nightstand, it was randomly pressing buttons on the password screen and I was hearing the short vibrations of the tactile feedback. It had done it enough that I was locked out and had to wait 30 seconds.
Something's not right in Evo land.
You definitely need an exorcists.
Since you live in UT, I am sure there lots of Mormon High Priest that can help you out.
Good luck.
gthing said:
My phone is not rooted and was running stock with the latest OTA. I am leaning towards the theory that it is something to do with the latest OTA which addressed the grounding issue.
I enabled a password on my phone. Last night I kept hearing these little noises, like a bug beating its wings in really quick, short durations. I was looking all over before I realized it was coming from my phone. Face down, on my nightstand, it was randomly pressing buttons on the password screen and I was hearing the short vibrations of the tactile feedback. It had done it enough that I was locked out and had to wait 30 seconds.
Something's not right in Evo land.
Click to expand...
Click to collapse
i've tried searching this forum with no luck for results, so maybe someone can point me in the right direction...
just wondering if there is a fix for this issue, that apparently is a bug:
when receiving an incoming call, and while the phone ringer is turned on, it will ring for a split second then it will stop ringing. the call will still be coming through and i can answer it and talk just fine, it's just the ringer that is the problem. this happens randomly, and i've found numerous posts on other forums by searching google, but haven't been able to find anything here.
can't post a url so here's some quotes:
My Dinc sometimes stops ringing after half a second with incoming calls. I'd hear a very short ring and then it just stops ringing or vibrating. I just noticed this today after missing several calls with my phone today.
This problems comes on randomly and goes away in a similar fashion. This seems to happen only when the phone is lying screen down on a flat surface. I called HTC and they said it might be due to the sensor in the front and advised me to not put phone face down and always carry it in a pouch. This is not an acceptable solution. I carry my phone in my pocket and it can very well be face down in there.
Has anyone noticed this problem? If not, I invite you to reproduce this problem. Put your phone screen down on a perfectly flat surface and try to call your cell. I'm wondering whether my phone is defective or it's a much wider issue.
Thanks.
Update: Apparently there is a feature on HTC devices when if you're holding the phone and if it rings, it will mute if you put it on a surface face down. While this is fine, the problem with my device is that if I leave it on a flat surface, it will do that for all subsequent calls too (ring for half a second and then mute). Maybe my phone has a bug in implementation of this 'feature'?
Click to expand...
Click to collapse
It's a well known issue that HTC has not fixed and will most likely never fix. I've been through 3 Dincs because of this problem and they all do the same thing. Quite irritating! Nice phone except for this BIG bug.
Click to expand...
Click to collapse
is there any fix for this bug? and does anyone know if this bug is software or hardware related. currently, i'm running stock 2.2 rooted with city id deleted. thinking about flashing CM7 or another custom rom, and just curious if it will do this with those roms as well.
thanks for any help
Must be an issue with the stock rom. I've never had a problem. But I've also never ran the stock 2.2 rom. I ran stock 2.1 until root was achieved. Custom Rom's from there on out.
Sent from my ADR6300
Also on my HTC Wildfire
This happens also on my htc wildfire android v2.2.1 (latest official rom), i think it is caused by the mute-on-pickup feature that is bugged in some way, even if i have turned it off.
Hello everybody,
Everything is fine with my Arc, except for the huge problem that sometimes I simply can't answer an incoming call! It happens like this: When a call is incoming, the phone starts ringing and vibrating as it usually does. However, the screen that is supposed to come up which shows you who is calling and where you can select to accept or reject the call is simply not showing up.
Has anybody experienced this before?
All I can do is slide to unlock the screen and then I'm looking at my home screen with the phone still ringing but no chance to get the call. There is nothing in the notification area or anywhere else where I could answer the call. All I can do is to wait until the ringing stops!! Really really bad behavior.
Furthermore, once the ringing has stopped, there is no information about the missed call in the call log. So I can't even call back the person who called me!
First time this happened I had "Plants vs Zombies" running so I figured the phone wasn't fast enough to switch to the incoming call. But it also happens when the phone is idling.
There seems to be no scheme behind all of this. Sometimes it happens twice in a row, sometimes only once a week.
I got my unbranded simlock free Arc in mid April with 2.3.2 and .181 firmware and applied Gingerbreak for root access. Later I upgraded via PC Companion to 2.3.3. and .145 firmware. But I lost root which I didn't like. So I downloaded the Generic World Firmware .181 and flashed it on the phone. Then used Gingerbreak again and made an OTA update to 2.3.3. and .145 firmware. Now I have root and the latest firmware.
All the while I used Titanium Backup to restore all my data, settings and apps as I don't want to reinstall all from scratch because it would take forever.
With this latest firmware, everything is fine, except for the call problem!
Please help me, what can I do?? I don't want to reflash and upgrade or whatever or lose all my data. I just want my phone to be able to handle calls as it should be!!
P.S.: I used Antek App Manager and frooze (not deleted!) some apps which where uncessesary and running in the background or at startup which speed up my startup time and free ram quite a bit. But I didn't frooze any crucial apps, at least I hope. Only stuff like Chinese keyboard and Let's Golf etc.
Also, if I would have frozen the call handling app or something, I wouldn't be able to accept calls in most cases, wouldn't I?
P.S.: I used Antek App Manager and frooze (not deleted!) some apps which where uncessesary and running in the background or at startup
Click to expand...
Click to collapse
Think you may have answered your own question here...
could be, but on the other hand I only frooze really stupid apps which should not affect any important functions of the phone. Also, if I frooze something important related to calls, why is it working most of the time? This is what I don't get.
Here is what I frooze (most of them just took up space in the app drawer and I don't use them), maybe it helps:
- stock browser (I use Opera)
- chinese keyboard (I'm german and don't need it)
- "Downloads"
- retaildemo
- live ware manager
- fb mediadiscovery
- dlna server
- news and weather
- postcard
- SE setup wizard
- sim toolkit
- sony ericsson sync service
- playnow
- sony ericsson support
- track id
- twitter
- let's golf
- google talk
- sony ericsson sync client wizard
so is your problem solved?
Anything related to google should be left alone news and weather should be fine to freeze or delete but would leave Talk alone, and depending what data from which FW was backed up, might also be an issue.
so I defrosted Google Talk. Anything else I should defrost?
Under "Settings" and then "Running services" I sometimes stop "Timescape Legacy Plugin" or whatever it's called because it takes up RAM. Could this also be a cause but I believe it's only for the Timescape app which I seldom use.
drsoran2 said:
Hello everybody,
Everything is fine with my Arc, except for the huge problem that sometimes I simply can't answer an incoming call! It happens like this: When a call is incoming, the phone starts ringing and vibrating as it usually does. However, the screen that is supposed to come up which shows you who is calling and where you can select to accept or reject the call is simply not showing up.
Has anybody experienced this before?
Click to expand...
Click to collapse
I have the exact same problem.
It doesn't happen often but it's really annoying either way.
I barely installed anything off the market and I don't use any sort of app killers/managers.
that's strange because I thought it could be my own fault because I played around and frooze same apps. But it's "good" to know that I'm not the only one.
Do you have any hints about when it happens or when not? Can you exclude anything?
Today, I re-enabled all the froozen apps and then frooze some of them again, according to the thread here on xda. But only apps about which I was really sure.
Don't know how I could test if the error is gone. I mean, have people calling me 100 times and hope it occurs or not doesn't really sound great.
may be there is some problem in your firmware,try some other firmware of other region.................
drsoran2 said:
that's strange because I thought it could be my own fault because I played around and frooze same apps. But it's "good" to know that I'm not the only one.
Do you have any hints about when it happens or when not? Can you exclude anything?
Click to expand...
Click to collapse
That's the weirdest part, the only thing I used that day was Whatsapp.
The incident happened about 5 hours later, I was in a car when my phone started ringing.
I tried picking it up but.. I guess you know the rest..
I was about to buy this phone but now I'm having second thoughts.
@flamez
yesterday it happened to me again. The weird thing is, that my girlfriend said she called me three times but I heard it ringing four times! She claims she didn't call me between her second and her third call! But it definetly rang but I couldn't answer it. Also my other friends say that they didn't call me at this time. Could be someone calling who I don't know at the exact time but the chance is slim I guess.
Also whenever there is such a phantom call, there's not even a hint of it inside the missing calls log. And when this happens, nobody ever leaves a message on my mailbox. Is this the same for you? Could be the person is just lazy but I don't know.
Furthermore, it happened several times to me already and never once a person asked me later why I didn't get their call. Strange, isn't it. It almost seems like that there was no one calling at all!
Now, could it be for some unknown reason that our phones just start ringing as if there is a call but in fact there isn't one at all?! You know, the phone just running crazy and triggering the ringtone? That could be the reason why the "accept call screen" doesn't show up and there's no call log because there is now call!
I know, sounds very weird. But think about it. They could be really "ghost calls".
briggs007 said:
I was about to buy this phone but now I'm having second thoughts.
Click to expand...
Click to collapse
Well, I can tell you that this a great phone and it seems me and drsoran2 are the only ones with this problem..
Guess we just had some bad luck..
drsoran2 said:
@flamez
yesterday it happened to me again. The weird thing is, that my girlfriend said she called me three times but I heard it ringing four times! She claims she didn't call me between her second and her third call! But it definetly rang but I couldn't answer it. Also my other friends say that they didn't call me at this time. Could be someone calling who I don't know at the exact time but the chance is slim I guess.
Also whenever there is such a phantom call, there's not even a hint of it inside the missing calls log. And when this happens, nobody ever leaves a message on my mailbox. Is this the same for you? Could be the person is just lazy but I don't know.
Furthermore, it happened several times to me already and never once a person asked me later why I didn't get their call. Strange, isn't it. It almost seems like that there was no one calling at all!
Now, could it be for some unknown reason that our phones just start ringing as if there is a call but in fact there isn't one at all?! You know, the phone just running crazy and triggering the ringtone? That could be the reason why the "accept call screen" doesn't show up and there's no call log because there is now call!
I know, sounds very weird. But think about it. They could be really "ghost calls".
Click to expand...
Click to collapse
No, I don't think that's it..
It's happened only twice to me over a 2-3 month period and my friends have always called me back asking why I never pick up the phone.
It really just happens about once a month to me, and I can answer the second time they call me right away without any problem.
Are you guys running task killers?
{EDIT - I remember OP saying that he'd frozen a load of stuff.. Suggest that if you're getting this a lot that you un freeze all of it and see how it goes, maybe just freeze the end user apps - like Lets Golf HD at first then build up the frozen apps slowly until you get the problem..}
im_iceman said:
Are you guys running task killers?
{EDIT - I remember OP saying that he'd frozen a load of stuff.. Suggest that if you're getting this a lot that you un freeze all of it and see how it goes, maybe just freeze the end user apps - like Lets Golf HD at first then build up the frozen apps slowly until you get the problem..}
Click to expand...
Click to collapse
No, as I said before, I'm not using any sort of task killers/app managers.
Today first time i encountered same problem. I have WhatsApp running in background. No task killer, nothing else.
Though i donno how to solve this problem. But i can surely tell how to pick up call in this case.
Just press the power key, this will take phone in locked state, but the call wont be rejected.
now click the home key and you will see the answer key, now slide it, it will slide without problem
it's good news that you found a workaround! I'll try to remember it the next time it happens.
Today, I had the problem again but this time it was different. The slider or the contact picture of the person calling didn't appear, but I could see the number of the person who is calling in the notification bar (not the name, just the number although this number and contact is stored in my contacts).
This happened the first time, all the other times the phone just rang without any hint of who is calling.
It would be nice if we were able to pinpoint a certain event which causes this odd behavior but so far I had no luck. What I'm doing differently since the last time it happened is, that I don't use task killers anymore. But still, it happened again today.
It's difficult to find out what it is when you don't know what causes it and when it will happen. For example, it happened to me today once for the first time in about a week.
in recent days, "it" happened very often to me!
Sometimes, the phone manages to at least show the number of the person calling so that I can call back. But usually it doesn't! The call just disappears into nirvana.
Do you guys remember if the error is associated with a certain amount of RAM left available? In other words, if the available RAM at the time of the incoming call is below a certain limit (which I don't know) the phone can't display the call. When it happened to me today, I had only 90MB RAM left. Maybe the phone can't free up enough RAM fast enough?!
Also the trick, which somebody mentioned a few posts above me, that when it happens you press the power button and then home and then you can slide and accept the call very rarely works!
I'm desperate and don't know what to do about it. I have just finished adjusting my phone to my needs. I linked apps with Link2SD and now have over 100 apps installed and still 215MB left on the internal memory, I have root and the .145 firmware. Everything is fine, except for this error!! It would take ages to restore it to the point where it is now, if it is complety possible at all.
I mean, if a phone can't handle calls, what good is it for?
I had a NEC e616 years ago which frooze while sending SMS or crashed after connecting a call or during a call and other "funny" things, but this was well known for this model.
But we don't have 2004 anymore and I except the Arc to work.
I could send it in on warranty, possibly. But then everything would be erased and it would take forever to get it repaired.
And I'm afraid they are going to tell me that they couldn't reproduce the error (because it happens so randomly)!
Such a nice and beautiful phone if not for this stupid error!
I'm already tempted to get rid of the phone and look for something else. But who's going to buy a phone with a bug which can't display phone calls?!!
I mean, I could reset it and flash the fimware and stuff and then hope. Maybe the error is gone. Maybe it persists and then all my data is gone and I have to start from scratch.
Or it is gone and then I have to start from scratch also!
If I should be forced to do it all over again and have all the work, then I could do it on another phone as well.
The Samsung Galaxy SII is quite ugly, to wide and big but I hope it can at least handle a call?!
Thank you for any help!!
Hmm..
If it happens rarely.. Why don't you sell it off on ebay
If asked about other mobile. I prefer sensation to sgs2. Much better phone function. In fact IMO htc is better than all other androids when it comes to phone functions.
Sent from my LT15i using XDA Premium App
This has been annoying since I got the phone 7 months ago.
It doesn't turn off the screen when I take/make a call. I'm constantly putting my caller on hold or even hanging up with my ear or cheek. I've Googled the crap out of this and I've found MANY different settings to check/change - NONE of which exist on this phone.
So does anyone know? Is this simply not a feature of this phone?
Thank you.
bcsteeve said:
This has been annoying since I got the phone 7 months ago.
It doesn't turn off the screen when I take/make a call. I'm constantly putting my caller on hold or even hanging up with my ear or cheek. I've Googled the crap out of this and I've found MANY different settings to check/change - NONE of which exist on this phone.
Click to expand...
Click to collapse
I thought it was just me! I haven't looked for a solution as yet, but if you find one please post back here and share.
Actually I did resolve it finally! I installed a different dialer app and it worked with it. I hated the app though, so I uninstalled it. Before I had a chance to find a different app, a call came in (using the default app again) and it worked as it should. I can't explain why, but for me... installing a different app and then removing it got the default dialer to behave correctly.
Now that it works "correctly", I have noticed a quirk with it. I have to wait for an outgoing call to actually be ringing (which can take some time with some calls) before I put it up to my ear or the screen won't shut off until I bring the phone down and then back up. Now, it is *possible* that this was always the issue and I just never figured it out. So maybe the whole app install/uninstall thing is unnecessary. Not sure.
bcsteeve said:
Actually I did resolve it finally! I installed a different dialer app and it worked with it. I hated the app though, so I uninstalled it. Before I had a chance to find a different app, a call came in (using the default app again) and it worked as it should. I can't explain why, but for me... installing a different app and then removing it got the default dialer to behave correctly.
Now that it works "correctly", I have noticed a quirk with it. I have to wait for an outgoing call to actually be ringing (which can take some time with some calls) before I put it up to my ear or the screen won't shut off until I bring the phone down and then back up. Now, it is *possible* that this was always the issue and I just never figured it out. So maybe the whole app install/uninstall thing is unnecessary. Not sure.
Click to expand...
Click to collapse
I had a same problem too, but did resolved after factory reset. But I don't know where is the problem located, maybe the proximity sensor is very sensitive even with dust.
Sorry, bad English.
Your English is fine
I think you might be right, because my problem now seems to come and go. The screen definitely shuts off, but there's some times when my face will put the call on mute or other strangeness. I've even accidentally sent an email to my Mom, all with my cheek while on the phone with someone else! I had to click the back button 6 or 7 times to get back to the phone screen.
This phone was good value, but I do regret the purchase.
The proximity sensor is very sensitive, even with a very small string. I just test this when I call my second phone. And moving around my finger, and boom! My screen is turned off, but did turned on again after I moving away my finger. This is surprising me when I call my mom, and I force to turn off my device, and it's rebooted. After my device is successfully booted, I tried to call my Dad, and surprisingly the screen is not turned off. So I'll try to find the problem, and I founded them:
The proximity sensor is very sensitive, so be sure to wipe the proximity sensor until it gets clean completely.
That's it, so no matter if you use a different dialer or default dialer for your device, just keep in mind that I mentioned there.
Thank you. As always, sorry for my bad English.?