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.
Anyone having issues with the desire delay of about a second after you press the answer icon. I press it once, nothing happens, so I think I havent pressed it so I hit it again just as the button changes to "End call" cutting off the person calling you.
I`ve done it two days running now anyone else having this issue.
When I answer, I just pause before putting it to my ear.
There may be a small pause but I dont have any issues. Has this happened from day 1 or is it getting worse?
Maybe if its getting worse some apps are causing the Desire to lag, try turning the handset off and on, dont open any apps, wait 1 minute and get someone to call you to see if it makes a difference.
Happened since day one I think. have tried killing all non-critical apps and tried calling from my home phone and no difference , always some lag. But I also noticed its random. Tried about 10 times , sometimes its a 1 second delay, another was 2+secs.
Think this is why sometimes I`m pressing twice and cancelling the call.
happens to me also. had an interesting thing happening to me yesterday: after answering the call vibrate function still carried out through the call and it did not stop even after ending the call. i had to restart the device.
I have noticed since upgrading to Froyo that my caller ID is broken if I'm already on another call. It's very strange because it only shows the phone number, but after I complete both the calls and go into my call log, the phone is able to resolve the number to the contact.
I've been reading around the net and there's spotty coverage of other people having this issue but no resolution.
Is anyone else having this problem? Anyone else figure out a solution?
No problem with it here, mine has been working fine.
mine does it intermittently
Just as importantly, there seems to be no way to hang up on one call while keeping the other. You can flash between the two, and even merge them, but switching to one and then hitting end hangs up on both. As it stands, I have to let the one call sit until I decide to hang up both.my old g1 had a "switch and hang up" button that you could use to select the caller you wanted to disconnect.
pinetreehater said:
Just as importantly, there seems to be no way to hang up on one call while keeping the other. You can flash between the two, and even merge them, but switching to one and then hitting end hangs up on both. As it stands, I have to let the one call sit until I decide to hang up both.my old g1 had a "switch and hang up" button that you could use to select the caller you wanted to disconnect.
Click to expand...
Click to collapse
I haven't figured this one out either
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
I personally have the very annoying issue with my L900 where the buttons sometimes "push themselves" then become unresponsive. Does anybody else have this issue? Can it be fixed?
I've never had them push themselves, but they are definitely less responsive than my HD7... At least that's what it seems like until I actually see precisely where my finger/thumb is pressing.. If it's not dead on the center of the "button" then it won't recognize it as a press.. So I don't think it's that they're unresponsive, I just think that on the Lumia 900 they made the area around the buttons less sensitive to prevent accidental key pressing that tons of WP7 users have complained about. Accidentally hitting search when handing your phone to somebody to look at a picture or whatever...
But like I said, mine don't press themselves --- I'd arrange to have your phone serviced...
Have you tried going into Diagnostics and testing your buttons functionality repeatedly to test responsiveness and see where they like to be pressed.
Sent from my Lumia 900 using Board Express Pro
I frequently have the problem where the buttons become unresponsive. Then when you press the back button, it 'sticks' and brings up the multitask screen. I've seen this reported elsewhere on the forum.
I was also having trouble with this. After searching the WPCentral and Nokia Support forums I found that it has to do with the speaker. I didn't believe it at first but you can replicate the problems 90% of the time.
Do this:
Play a game on max volume for about 5 minutes.
Try exiting using the back button or the Windows button. 90% of the time it will "stick."
Now play a game again on max volume, but with headphones.
When you try and exit, it will work 100% of the time.
Also if the buttons are sticking you can plug something (anything) into the headphone jack and they will work again. The rumor is that the speaker interferes with the buttons. Sometimes I have them activate all by themselves, which can be annoying when streaming video. Some people have reported the only option is to take your phone back to the store and get a new one. But the odds of getting a good one are slim.
I almost never play games, and don't listen to music often. And my Back button does occasionally bring up the multi-task view. Probably about 1 in 10 presses. Rather than sticking I attribute it to a timing issue, where the device has a problem discerning between a long/short press. Might have to do with how much work the processor is doing at the time or how much memory is being accessed. Not sure.
Sent from my Lumia 900 using Board Express Pro
Actually, a lot of people have this problem with unresponsive buttons. Nokia is ignoring everyone with this issue.
http://discussions.nokia.com/t5/Nok...mia-900-touch-capacitive-buttons/td-p/1375977
Never had this, even though I play games (but with sound turned off) and listen to music a lot...
nraudigy2 said:
Actually, a lot of people have this problem with unresponsive buttons. Nokia is ignoring everyone with this issue.
http://discussions.nokia.com/t5/Nok...mia-900-touch-capacitive-buttons/td-p/1375977
Click to expand...
Click to collapse
Actually, I don't think Nokia is ignoring anything. They can't afford to. What I do think is this is an intermittent problem, possibly associated with certain 3rd party apps or settings. Once they can pinpoint the issue it will be corrected.
I lived through a disappearing keyboard that Microsoft took more than 3 months to correct and AT&T still has not had the decency to push out the appropriate update (I did a forced update on my Surround in March). That issue drove me nuts, and kept me from typing replies like this one. On a bug scale of 1-10, that was an 8. The occasional Back button glitch, is more like a 2-3. I can live with it till Nokia pins it down.
Sent from my Lumia 900 using Board Express Pro
jimski said:
Actually, I don't think Nokia is ignoring anything. They can't afford to. What I do think is this is an intermittent problem, possibly associated with certain 3rd party apps or settings. Once they can pinpoint the issue it will be corrected.
I lived through a disappearing keyboard that Microsoft took more than 3 months to correct and AT&T still has not had the decency to push out the appropriate update (I did a forced update on my Surround in March). That issue drove me nuts, and kept me from typing replies like this one. On a bug scale of 1-10, that was an 8. The occasional Back button glitch, is more like a 2-3. I can live with it till Nokia pins it down.
Sent from my Lumia 900 using Board Express Pro
Click to expand...
Click to collapse
The Back button "sticking" happens to me every time I send a text message. So for me that is about 15-20 times a day. I don't play many games anymore because the buttons activate themselves too often to enjoy it.
I think Nokia is trying to ignore this problem. If you look on their forums you'll see someone was told, "Our engineers can't replicate the problem." It's something that I can replicate 99% of the time. You hear a lot about the Blue screen at low light but I haven't read one news story about this. Maybe it's time we put pressure on Nokia.
The_Vermonster said:
The Back button "sticking" happens to me every time I send a text message. So for me that is about 15-20 times a day. I don't play many games anymore because the buttons activate themselves too often to enjoy it.
I think Nokia is trying to ignore this problem. If you look on their forums you'll see someone was told, "Our engineers can't replicate the problem." It's something that I can replicate 99% of the time. You hear a lot about the Blue screen at low light but I haven't read one news story about this. Maybe it's time we put pressure on Nokia.
Click to expand...
Click to collapse
It's probably a hardware issue and they don't want to replace those with new phones. Not good for Nokia.
nraudigy2 said:
It's probably a hardware issue and they don't want to replace those with new phones. Not good for Nokia.
Click to expand...
Click to collapse
If you go into the Diagnostics menu, you can test those capacitive buttons 100 times, like I did, and they will perform perfectly. Got the same results when I tested the camera button (yes, another 100 times). Despite that, the capacitive buttons do occasionally register a long press. That's a software glitch.
Sent from my Lumia 900 using Board Express Pro
The_Vermonster said:
The Back button "sticking" happens to me every time I send a text message. So for me that is about 15-20 times a day. I don't play many games anymore because the buttons activate themselves too often to enjoy it.
I think Nokia is trying to ignore this problem. If you look on their forums you'll see someone was told, "Our engineers can't replicate the problem." It's something that I can replicate 99% of the time. You hear a lot about the Blue screen at low light but I haven't read one news story about this. Maybe it's time we put pressure on Nokia.
Click to expand...
Click to collapse
Ok, whatever. So I guess it's a Nokia conspiracy to cover up a bug so they don't have to send out another $100 to everyone. Btw, I do write 10-12 texts per day and have a terrible (WindowsMobile) habit of always backing out of everything, even though in testing I found it has zero effect on battery life. I do not recall ever having the multi-view screen popup or the Back button being unresponsive when exiting the Messaging app. So maybe its a software glitch (capacitive button are software controlled-hence capacitive) on your phone. Have you tried a hard reset? It can work wonders.
Sent from my Lumia 900 using Board Express Pro
same issue here. But it feels like a software issue. i did some experiment and come into conclusion that this wont happen when you playing video on 3rd party apps e.g., Metrotube, Netflix.
Did anyone try this way?
hopfully, Nokia can address the issue soon.
Sent from my Sony Tablet S using xda app-developers app
I went to AT&T to get a replacement because the capacitive buttons don't respond that good during an audio playing through the speaker. I showed the AT&T rep the issue and he called to get me a replacement device. He was using a black Lumia 900. The brand new phone came in. The capacitive buttons always work now. Definitely a hardware issue. Volume buttons work when locked. Camera button works 50% of the time. The Tango update should fix the camera button as it is confirmed by couple people.
What do you mean by "camera button works 50% of the time"? Works where? Do you mean launching the camera when the phone is locked by a long press on the camera button?
efektos said:
What do you mean by "camera button works 50% of the time"? Works where? Do you mean launching the camera when the phone is locked by a long press on the camera button?
Click to expand...
Click to collapse
I have that problem too, but it will only work if I have no apps running and I have the pin disabled.
As far as the "sticking" buttons, I can't say that 3rd party apps are any better. IE and Surfcube 3d were both having the same problem watching videos. Youtube videos seem to play fine but Nokia Trailers never work. All games fail miserably, even simple ones like Minesweeper.
nraudigy2 said:
I went to AT&T to get a replacement because the capacitive buttons don't respond that good during an audio playing through the speaker. I showed the AT&T rep the issue and he called to get me a replacement device. He was using a black Lumia 900. The brand new phone came in. The capacitive buttons always work now. Definitely a hardware issue. Volume buttons work when locked. Camera button works 50% of the time. The Tango update should fix the camera button as it is confirmed by couple people.
Click to expand...
Click to collapse
Ok, so is the new phone running the exact same firmware as the old phone? Did you ever try a hard reset on the old phone, and then not load any apps during the test period?
And the Tango update won't fix anything. The Nokia firmware update, that is supposed to to be attached to the AT&T Mango update, with though.
Sent from my Lumia 900 using Board Express Pro
jimski said:
Ok, so is the new phone running the exact same firmware as the old phone? Did you ever try a hard reset on the old phone, and then not load any apps during the test period?
And the Tango update won't fix anything. The Nokia firmware update, that is supposed to to be attached to the AT&T Mango update, with though.
Sent from my Lumia 900 using Board Express Pro
Click to expand...
Click to collapse
_______________________________________
I meant the Tango update that comes with the firmware update if you flash it using Nokia Care suite. New phone is running the latest firmware from Zune with Mango. Not the latest Tango update yet. I don't really want to wipe my device again. Nokia is ignoring this issue maybe because there is no fix for it.
nraudigy2 said:
_______________________________________
I meant the Tango update that comes with the firmware update if you flash it using Nokia Care suite. New phone is running the latest firmware from Zune with Mango. Not the latest Tango update yet. I don't really want to wipe my device again. Nokia is ignoring this issue maybe because there is no fix for it.
Click to expand...
Click to collapse
Sorry if I wasn't clear.
Is your new phone running the same firmware as your old phone, or a newer version?
Did you ever try a hard reset on your "old phone", without loading any third party apps during a 24-48hour test period to see if the capacitive button issue went away?
I am always puzzled by users who are reluctant to hard reset their phones, but have no problems exchanging their phone, which is in effect a hard reset. If it's not, it should be a requirement 24 hours prior to any exchange.
Sent from my Lumia 900 using Board Express Pro