hello! i've searched but didnt find any help with my problem. When my jasjar rings (incomming call) and after i press the answer button (the green one) i need to wait about 1 to 2 seconds before i can hear the person that is calling me...strange...did this ever happen to you? how can i solve this problem? Thanks in Advance
Yes, i have the same problem on my MDA Pro
After pressing the green button, i have to wait 3 secounds with speaking.
I had the same problem and now is solved.
In phone/options/band select WCDMA (not automatic)
i think that didnt solve the problem...sorry...thanks
I have the same probelm on the incoming call. However, i finally realized that it's the problem on the Pocket Plus V3.0.4 installed on the system.
It appear to be normal once i removed the program.
It's the case for me, and i hope it would help you as well
I too have this problem with my I-Mate Jasjar. I need to wait for a few seconds after hitting the answer button before I can hear the calling party. I did a hard reset and installed the latest wwe ROM available on clubimate site. The problem still persists even without any third party software installed. So I do not blame pocketplus for this problem. I think this is a software/hardware issue which should be addressed in a ROM upgrade.
I have the same problem with my JasJar. I have also updated to the lates ROM from clubImate by advice from clubImate support.
Sometimes the phone does not even answer the call at all when pressing the green button. This is becoming an even more expensive phone since I have to call back so many people on account of missed calls
Seriously, It cannot be right that a problem like this exists on a phone in this price range. ClubImate support even said they had never heard of this problem before.
i did a few hard resets and the problem persists without any extra software installed. "Very bad bug". i've already test a K-jam and it works beautifull...i'm sad
Got my XDA Exec today. It's pretty good but is not the same as my XDA2. Even less phone. More PDA...
If I turn my machine off in landscape mode and then close the lid with the screen out (like the XDA2) then when a call arrives it takes ages to answer because the screen has to rotate first to portrait mode.
If I turn off and close in laptop mode (landscape) then it rings immediately and I can answer it immediately using the hinge buttons.
Maybe it is the same for you?
i have noticed it seems to be quicker to goto portrait than to landscape in all respects of use
ok, lets try it...thanks
how i test it: jasjar "on" charging, open in portait mode. same delay.
L to P is roughly twice as long for me.
going to L i get twist and flip and the display is done ready and waiting
going to P i get twist and flip then get a 2s ish of L before it flips to P
this was battery power
*** its the same on mains and battery !
Carnivor said:
L to P is roughly twice as long for me.
going to L i get twist and flip and the display is done ready and waiting
going to P i get twist and flip then get a 2s ish of L before it flips to P
this was battery power
*** its the same on mains and battery !
Click to expand...
Click to collapse
When my Exec is on, the rotation is pretty much instant. I have no apps running. It's only when a phone call wakes it up that the rotation is slooooow.
My Qtek 9100 also take app. 5 sec before it rings, and the S100 I had before was the same. My dad has an XDA mini, same problem. It seems like pocket plus will increase the problem, but even without any extra software its not working perfect. Its strange after such long time, they havent been able to solve simple problems like theese.
I also get this, Its very annying. Maybe they incorperated it so you can answer the call asap and the before it acually picks up, you have a few seconds to turn the screen round and see whos calling ect?
I have an Exec and there is certainly a knack to answering a call on it, but i'm getting better!!!
Firstly the voicemail seems to kick in way too early, i only get 4 rings of the 'ring' ringtone max before the VM kicks in, sometimes i think it is less, but i may just be going deaf! does anyone else find this a problem?(not deafness)
As i usually have the exec closed in my pocket, this is how i answer a call.
1, Hear the first ring, if i don't it's too late already!
2, Drop everything, and remove phone(ha!) from case and open into laptop mode only. If i rotate all the way into PDA mode the screen takes too long to change and the call goes to VM before i can see who it is.
3, Answer call after seeing who it is
4, Rotate or close screen and put to my ear and wait 2 seconds to speak.
It's a real pain in the arse and very annoying.
Great forum btw, it's been very helpful, i knew bugger all about PDAs three weeks ago.
Ian
Which button(s) do you have success with?
The small green on the side,
the green above the other keys on the keyboard,
the soft key button,
or touching the screen?
ipanter said:
...
Firstly the voicemail seems to kick in way too early, i only get 4 rings of the 'ring' ringtone max before the VM kicks in, sometimes i think it is less, but i may just be going deaf! does anyone else find this a problem?(not deafness)
...Ian
Click to expand...
Click to collapse
If you're using the Exec on o2, you can adjust the cut-in delay at the o2 end. You do so by keying in/sending the following to o2:
**61*901*11*xx# [send]
(where xx is number of seconds, e.g. 30.)
Note: I think the maximum delay allowed is about 30-secs - at least I've never got it to extend longer than that!
I have found that o2 occasionally reset mine back to about 10-secs, so have it programmed into a contact number.
HTH
I've found something interesting.
I tried to swap two sim cards.
<boring>
The one originally in my phone was a sim card from Orange Denmark (where I live). Orange has since been bought by Telia, and this same sim card is now using Telias network. This is by design. It gives my the roaming symbol all the time since the buy-over.
To say the least, some things have been very ****ty in this process, so I thougt that I might try another sim card.
</boring>
I had another one from TDC (another danish operator), and bang! My Universal (Jasjar) answers instantly - every time - on all the buttons!
Could some of you who have this problem as well, please confirm this? Please tell what kind of sim card (and country) you are networking through, and try another one.
Okay so I think I know at least A solution but I'm hoping that someone here will be able to suggest something besides a hard reset.
I've got a Cingular 8125 a couple of weeks ago. Flashed it to the latest imate rom. I kept it from installing the custom imate stuff but did install some of the Cingular cabs.
Now I'm having a few problems with the phone. It's quite a list.
A) I can't enable wifi at all. At one point I could but the phone locked up on me while I was trying to resetup my connection. I had no choice but to soft reset it. Now I can't enable wifi at all. If I click on it in the comm manager to turn it on it will sit there with the spinning wheel like it's enabling then go back to the same icon with the x on it. I've tried turning flight mode on and off, etc but nothing seems to help it.
B) the phone HAS been locking up. It will just sort of freeze and stop responding. Sometimes I'm able to get to the memory settings in control panel and still have available memory (it's usually been around 16 MB of program memory when this has occured) but even so closing everything will often not help. Even if it unfreezes then it will usually do so not much later and often it just won't unfreeze.
C) sometimes I can't close out the phone application. This seems to happen when Magic Button is running. I click to close it and it goes from the phone to my call history. Closing that goes back to the phone again. I can't get to the Today screen. Pressing the red hangup button would sometimes fix it but usually not.
D) voice command is REALLY wonky using my BT headset (Scala 500). Okay, I know it doesn't officially work with BT headsets and I could live with that. But why does it have to be so damned random?
1) Sometimes pressing the button once will get me the chime. Usually it just gets me a lower pitched tone. If the first press doesn't get it then typically a second within a short time will. Sometimes it takes three though.
2) At one point the phone would usually play my selected ringtone and announce the incoming call over the headset. Other times I would only get the default incoming call sound on the headset and the phone and voice command announcement are over the phone speakers instead. In the last couple of days I've ONLY been getting them from the phone.
3) While typically when I'm using the headset with voice command the feedback DOES come over the headset, sometimes it gives me the confirmations from the phone instead
I think there were a few other flaky issues too but this is the majority of them. Also many of them were present before the rom upgrade so I don't think it's responsible for most of it.
edit: oh, one other thing is that after the ROM upgrade I can't get the default input to stay on anything but keyboard. Even if I change it, I turn around and it's back to keyboard again. I'm thinking, though, that there's a reghack for this?
*bump*
===A) I can't enable wifi at all. At one point I could but the phone locked up on me while I was trying to resetup my connection. I had no choice but to soft reset it. Now I can't enable wifi at all. If I click on it in the comm manager to turn it on it will sit there with the spinning wheel like it's enabling then go back to the same icon with the x on it. I've tried turning flight mode on and off, etc but nothing seems to help it.==
I have the same problem with you. Can anybody help?
any solutions i have the same problem
Try this: back up your PIM, then flash phone back to OEM ROM (cingular, t-mobile, whatever it is for your model). Then unlock it again (if needed), and flash the ROM again. If it's still garbage, try reading the thread for the ROM you loaded (chances are you're not the first to experience this problem, and the other testers of that ROM may offer solutions). If it's still garbage after all that, consider using a different ROM altogether. CRacing's CR86 Touch HD and SVI's ANGEL are both quite nice, and VERY reliable for functionality.
well it's been bugging me for a while, and lately it got me in a sticky situation.
basically if i'm on a call, and i wish to end it.. pressing the hardware hangup button doesn't really do anything if the display is off (i.e: the device switches to power saving while on a long call)
and the only ways to hangup is either to wait for the other party to hang up, or press the power button first, wait for the display to light up, then hang up..
i've always had this problem, even with the latest i-mate ROM available, and didn't think much of it, till today i finished a call, and somehow it skipped my mind that my phone acts stupid that way, and the person on the other end heard somethings they shouldn't have heard while i thought the line was already hung :S
anyway.. is there a known fix to this?
i'm thinking of upgrading to Jwrightmcps' AKU 3.2 Rom Update 1.90.94
any clues if that could help?
is it a problem in the radio ROM?
thanks in advance
Member
As u have tried two ROMs even the official one also So, I don't think so that this is something related to OS as Jwright's ROM is pretty much stable and fast indeed so u can give it a try and if it doesn't work for u then IMHO it's a hardware thing to be worried about .
you can set like this:
open start-settings-buttons-lock
then choose do not lock buttons.
but if you set like this,press any key(except tape screen)will wake it up.
Hi,
My T-Mobile MDA Vario (Wizard) is taking ages to boot. But as soon as it start the handset it is still on the blue Windows Mobile screen the GSM Radio start (green LED) and during this time if I get a call it rings but the handset does not display anything since it is still on bootup scrren nor does it log the missed call.
How can I delay the GSM Radio activation till the handset has fully booted to avoid this problem.
Due to this problem I dont know who called and the caller thinks I have received a missed call so I will call back which cannot happen as the call has not been logged.
Tweak to a Registry entry or modification to bootup sequence... just some guess but need help to do this.
Thanx.
Rohin.
hi, couldn't find anything similar via search and it seems that I'm the only one having such problem.
so, I've tried numerous roms by Quarx, few slimkats and my phone regularly unlocks (i assume) while talking, and hangs up, or even worse, tries to call someone else. i was ready to call it a proximity sensor malfunction, but if i try to cover it while holding phone in hand it works perfectly every time, and I'm using stock ROM for a few weeks now - no hang ups at all. only solution is to push phone firmly into my face or keep it away from it..
so, any suggestions ? even an app which wouldn't unlock the phone in call unless unlock button is pressed or call just ended would be very nice.
thanks.