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.
Related
On the whole I'm very pleased with my imate PDA2K, but I am wondering whether anyone else is experiencing the following problems
1) After the phone has been on for a few hours, sometimes you cannot send an SMS. Once you do a soft reset then text message sending is OK again.
2) I've had this twice now. I make a phone call and I get no dial tone. A soft-reset sorts this out again. This is after the phone has been on for a few hours again.
3) The machine seems generally sluggish in popping up the text box for text message received/message sent confirmations after the notification icon has appeared in the top line.
4) Wifi access can be flaky. My signal strength generally shows as poor and the range is a lot shorter than an IPAQ HX4700 I have also used. This connects everytime in every room of the house.
5) Does anyone find the yellow tinge to the screen annoying. The XDAII contrast is better although actual screen on PDA2K is better when you get the viewing angle spot-on.
I never saw these issues on my XDAII.
I'm using the latest ROM update (1.12.22), Radio (1.02.00) ExtROM (1.12.169).
I'm begginning to consider using a SPV C500 Bluetooh phone with an IPAQ HX4700 if I need GPRS internet - it has a beautiful screen - any comments.
I really want a "one-device fits all", but these little problems are making me re-consider.
Mike
i second everything you said
my PDa2K is the same
John
I don't have Pda2k but consider most of your problems related about first ROM and Radio Stack Version..All devices have some bugs
Then about the yellow screen,that is hardware related,I am sure it is made by another company then Xda2 screen.
Note: We all know XDA2 also had initially one type screen,then after some months they (HTC) have sell XDA2 with other type screen..
I find the tint of the yellow screen changes with screen angle and I find it quite annoying.
My bluetooth headset (jabra) that has worked fine on my XDAIII for the last year and my XDA1 (with dongle) before that keeps loosing it's connection with MDAIII - works fine for half an hour after a soft reset but then stops working again.
while i can live with most of the things you mentioned so far pretty well, i can't live with the fact, that mine turns on every time i receive a short message, or when someone calls me.. because turning on not only means showing me what's on the display (that'd be ideal) but it does also mean, releasing the key- and screenlock! so whenever i get a message from someone, i start tapping on my screen probably without knowing it (since it's in my pocket) and everything gets messed up, and if i'm unlucky i might even call someone or delete stuff...
is there any workorund for that? (i have postet this problem to the general discussion earlyer this day, but nobody seems to either care, share the problem or know a solution... )
other than that, i am rather happy with my investment ;-)
cheers
pascal
They used a yellowish screen for a reason, it is 'suppose' to be ALOT easier to view under direct sunlight compared to the Xda II which will be almost unviewable under sunlight. But i personally rather have the white bright screen of xda II, who looks at their pda under direct sunlight at it anyways u can just use ur head to block the sunlight.
I know this topic has be address many many times and there are still no soluation to the problem.
So.. I want to make a poll to see how many user is experiencing this problem.
I hope to grather enough data to see if it is a hardware problem or Firmware problem so that i can address to O2 regarding this issue.
I love my PDA/phone.. but... this issuse really bugs me cos i used the phone for business and it always happens when a important call arrived... :evil:
Pls, Lets Vote with your honest answer...
Derek
No problems here....
What i've experienced is that sometimes the ringing sound is very quite even though the volume is at maximum. I make a soft reset and everything's back to normal.
NO SOUND
I have also experienced the same. I normally have to do a soft reset to fix the problem. Seems its a firmware issue to me.
One more issue is that we need to disable the power off system setting after 3minutes.
If not, a phone call will be automatically ended after 3 minutes talking.
i have also experienced this problem. i had a important caller call me twice and i didnt hear my phone ring. it was also next to me. luckily, i had my backup phone with me when he tried that line.
agreed that we shouldnt have to soft reset to get back the ring tone functionality. i personally think its a caller id version problem, but thats my opinion cause its easier to fix. i just hope it isnt a firmware problem since i wont hold my breathe on O2 releasing a rom upgrade in my phone version.
im going to try some reg tweaks to see if it will help, once my main pc is up and running (currently moving). i just dont want to go back to an older rom because of a ringing problem. but it IS a big problem for most of us.
ps. sorry about the spelling mistakes and punctuations. im on my pda at a coffee shop.
Yup I have see the no sould on outgoing, no sound on incoming, reset does the trick for me. Also feel that the sound is low in general (even if set to max)
Ha.. i call XDA today in their headoffice in Singapore. The CS guy told me.. they know this issue and say there will be a new (Rom) or patch release very soon.
After seeing the vote result. I believe that the issue is do to software, not hardware.
I have a firend that design such product. he told me that it could be that DSP script is not written well. He said, the Echo Cancelling must be overflow causing the unit to manufunction. and after reset, the overflow will be clear out, so the unit function again.
I hope O2 is really releasing a new patch to fix this issue. If not, i think i am force to go back to my Sony Ericsson P910i or one PDA and one phone option.
i'm glad that O2 recognises the problem and not passing it on to other people. thanks for the information rcbear. glad you took the extra steps get them looking this way.
i hope "soon" means in a waek or two.
same problem
My ringer always works but sometimes, at least every other day. When someone calls me i can not hear them, they can sort of hear me, but the earpiece is dead. A soft reset fix's this problem. Is my issue related to the current issue dicussed in this thread? Thanks
Jeff
I have the problem
But I get it seldom and sporadically.
pda2k (out of the box)
ROM: 1.22.00 WWE
Radio: 1.06.00
Protocol: 1337.38
ExtROM: 1.22.162 WWE
AT&T/Cingular
Re: same problem
jeffro01 said:
My ringer always works but sometimes, at least every other day. When someone calls me i can not hear them, they can sort of hear me, but the earpiece is dead. A soft reset fix's this problem. Is my issue related to the current issue dicussed in this thread? Thanks
Jeff
Click to expand...
Click to collapse
Hi Jeffro01..
Welcome to the club.. :lol:
Derek
I don't seem to have the ring volume problem, but my phone will get into a state where it rings, I answer the phone, but there is no audio. In the six or so times it's happened, I haven't really determined if the caller can hear me. A reboot fixes it.
I can't pin down any one thing I do to cause it to get into this state, but it seems like a software/firmware issue.
I have this problem too.
I had to send my BT headset for repair for two weeks and noticed it did not happen during that time while it started again since I got my BT back.
When it happens (once to twice a week) I soft reset my SPVM2000 and it then is ok.
Also the BT Orange Switzerland patch makes the problem appear less often.
Phone ring problem got me twice today...
Both times, never heard three calls, but the phone still reports them as being missed.
Gotta be a solution for this or I'll be soft resetting every time I finish a call/use.
I had to send my BT headset for repair for two weeks and noticed it did not happen during that time while it started again since I got my BT back.
Click to expand...
Click to collapse
If so I have 2 questions for everyone who has this issue:
1, Do you use a bluetooth headset or any other bluetooth device (gps...)?
2, What is your current bluetooth version and build?
I have Bluetooth build 3900, and I'm using 1.33.
No probleme here
not using BT or WiFi.
Where can I find my BT version?
I don't also have the 3 minutes switch off pb, the PDA function switch off after 3 minutes but the phone remains operational. I often switch the PDA off myself whilst on the phone to save on batteries.
...Hi everyone! (1st post!)...
I get the dead-speaker in calls too...
I took delivery of my first SPV M2000 a couple of weeks ago; it had a few problems, one of which was that the speaker would be dead occassionally when making or answering calls requiring a soft-reset to resolve. I initially thought this might be caused by the device not correctly recognising external hardware had become disconnected - handsfree/BT/car-cradle etc. - but it did seem to be at random.
Orange replaced the device last week; and by day 3 without using any handsfree/cradles etc. and BT and WiFi not even enabled (much less paired/connected); the dead-speaker problem reappeared.
I'm not going to bother chasing Orange about this issue on its own (this device doesn't exhibit any of the other problems I had with my first); as it seems to be a pretty common problem that's going to require a software update to fix. Needless to say when I read that HTC have written a fix I will be on Orange's back to make a fix for their ROMs public. (dreaming?).
Just FYI, both the initial device I was supplied and the replacement have the same software versions (in my sig).
Regards,
Rob.
I circumvented (temporally fixed) the ringtone problem by setting the default ringtone to "None", and also set the phone to vibrate. Then Re-enabled MS Voice Command to announce all incoming calls. The only problem is, the voice isn't loud enough in noisy places, but it does the job in the office or semi noisy environment. I guess this will have to do until a verified fix comes along our way.
I'm having the same problem for a week now...
I was on the street with my BA making calls and all went ok. I use it for my work, so I do lots of calls a day. Suddenly, I realized, when I call, that the other can not hear me, nor can I hear them! The counter is running, the screen says "Connected". I haven't done anything to change the configuration, nor it have dropped it from my pocket.
I'¡m getting crazy. I don't know what I've done wrong.
Things tried unsuccessfully:
-Lots of device resets..... Between tryes and Updates.
- Reinstalled WM5 using a different ROM. Now I have TM 1.3. [http://forum.xda-developers.com/viewtopic.php?t=42632]
- Upgraded Radio to 1.15 (previously, I had 1.13)
- Used a Bluetooth headset. It worked, I could hear the sound from the phone, at least. Only thru the bluetooth headphone. Still, I could not hear any phone-sound from the loudspeaker when I turned off the headphone and the bluetooth headset were disabled, even with the Bluetooth signal ON, as suggested on other post. Each try with a new call.
- "Installed" the Unidirectional patch (copied the AudioGW.dll file over the old one successfully, reset, etc..)
- Turned off the device and leave it off for a while. Take off the SIM card, touch it (cosmic vibrations ) Sometimes, before, the SIM card went a little nuts if I resetted the device too much -maybe :?- or if I got the battery off...
Sorry if this has been posted before, but, at this point, when I've been tried almost (I think) everything, i couldn't find anything relevant using search.
Please, any help will be greatly appreciated!!! Maybe I can use at least a link to another thread..
Thanks
come on, people, a little bit of help here Still making calls with my old Nokia
Out of interest... do you have any wisbar apps installed?
No wisbar apps installed. Thanks
I'm having the same problem. Most of the time this occurs the first time I use it in the morning. The other side can hear me, but I can't hear them. I softreset and it works again.
Yes, I've checked and there's lots of posts about this problem. It differs from mine in the sense that the other CAN hear you. In my case, nor I or the other part can hear us....
As you can read, I've done lots of soft-resets, now I have also 3 hard-resets with everything "at 0" (clear Registry Hive and format Storage). But the problem remains. The only thing I see I can do now is downgrade to wm2003 and see.......
Thanks for your answer.
mutho said:
I'm having the same problem. Most of the time this occurs the first time I use it in the morning. The other side can hear me, but I can't hear them. I softreset and it works again.
Click to expand...
Click to collapse
I've moved to the "BA upgrade, etc" forum. Please, help me from there!! Still looking for an answer
http://forum.xda-developers.com/viewtopic.php?t=44440
there is an issue with BT and this behaviour. Either you need to always have BT activated or once you have deactivated BT you need to reboot your device. I have the same problem myself.
Regards,
Fredrik
I have a problem that more people seem to have, according to the search. I couldn’t find the “audio” tab in my Bluetooth-settings, so that didn’t help me.
The problem is as follows. After 1 day the sound on my compact III mutes, including vibration. Sometimes it's after 12 hours, sometimes after 2 days, there's no distinct pattern to be recognized. Also, it doesn't seem to matter if you use the phone or not, since it sometimes is alright at night and the sound is muted the next morning. This is for all sound-events (warnings, incoming call notifications, messages, mp3 etc), however, you can make a call without any problems and hear what the other person is saying. Once you’ve hard-reset the device everything is back to normal.
It does get annoying however, since I regularly miss calls due to this bug.
I had the same problem on my Vario in the past. So I’m guessing it’s somewhere in the software I use, but apart from Total Commander and TomTom6 I haven’t installed any third-party apps.
Yup i've been having a slight problem with the sound. I thought it was like the endless knackered M500's that orange used to send me which had speaker failure after about 10minuites! (Swear they kept sending me the same 2 faulty phones - I had 5 in 5 days once!) But a play in the bluetooth seems to get it working again.
The other annoying thing is that if you leave the power management at the default settings then occasionally the screen blanks without being able to get the backlight on again - so now I have to manually turn of the screen. Stil aint much of a problem - ive had a normal days use, 2 hours of radio play, bluetooth and wi-fi on all day and still have 35% battery - wehay!
Hopefully there'll be a patch soon to sort out he glitches.
I forgot to mention I had the exact same problem on my mda Vario also. I always thought it was a problem with that specific piece, but apparantly not.
Could it be the vibrate.cab that I'm using to produce vibrations when you use the phonepad? Or should I really do some further research in the bluetooth-department?
Same problem here.
Phone becomes completely silent after 9 hours in standby mode.
I need to reset it to get back sound
Does someone know what is going on here ?
Please advise. Thank you.
I seem to experience no problems the past couple of days (fingers crossed). I used the 'speed up your WM5' tweak where you set the Glyphcache to 32768. After I reduced it to 16something the problems seem to have disappeared.
I noticed that this problem happens when for example email is automatically checked during night. If email comes in (and is not read immediately) the phone will start notifying in background.
Notifications are kept and only a program like "check notifications" will delete them manually. But still if you delete them, the phone then needs a reset
to work properly again.
This is not a memory issue, it has to do with the notifications.
I do not know how to solve it.
I have had to send my Leo back for repair due to white patches developing on the screen. As I had given my last device (an iPhone) to the missus, I have gone back to using my O2 Orbit until my HD2 is returned but I have just remembered why I stopped using it.
I have this really annoying issue where, after a random amount of time (could be hours, could be days), it simply won't accept incoming calls or texts, despite it seeming to have a full network signal. Outgoing calls work as normal but if you call the phone, it goes straight to voicemail and if you send a text message, it won't be received. However, as soon as I perform a soft reset the phone goes back to normal and any texts which were sent while it wasn't working get arrive. Then it eventually happens again. It doesn't seem to be a rom issue as I have had this problem with at least 5 cooked roms and the original O2 one.
Anyone have the same issue or is it, as I suspect, simply a case of the phone being shagged? I would love to get this resolved as at the moment I'm having to call it once an hour to make sure it rings which is a bit annoying.
im having the same issue but a small difference, i get this prob so frequently around 5~8 times a day...........
im jus suspicious on the battery.......
could u jus look at ur battery voltage when 100% charged and reply plz????
ive jus asked this same issue here
http://forum.xda-developers.com/showthread.php?t=642435