Power on / power off using TAPI : odd errors occurring - Windows Mobile Development and Hacking General

I'm using the standard TAPI commands for powering the device on and off (lineSetEquipmentState()). This works fine most of the time. However, it can often get into a state where neither functions work with the function reporting the 'operation failed' TAPI code. The only way of fixing this is to warm start the device.
The problem seems to stem from a timing issue as if I turn the module on then off quickly using the line function I will often receive these errors. Once I receive one failure it is almost impossible to recover. Unfortunately this problem is quite unpredictable.
Secondly, some SIMs have given us problems on power up. The only way I found to get round this is to call lineGetEquipmentState() directly after the lineSetEquipmentState() function. While this (hack) works I have no idea why.
This problem is affecting both XDA and XDAII, but is more pronounced on the XDAII. It would be nice to know what is causing the problem and what can be done to counter-act it. Anyone have any ideas?

Related

Phone application (radio?) not responding!

Hi,
On my XDAII (1.72) I sometimes experience a not responding phone/SMS application or radio stack.
People trying to call me are instantly redirected to the voicemail, and if I try to make eiter a call or send a text message, respectively the phone application is stalling or the SMS 'Send' button stays in the 'pressed' state.
Soft-resetting the phone or toggling the 'turn off radio' function re-establishes the radio.
Does anyone knows of a solution?
Any help would be GREATLY appreciated and possibly rewarded with a 6-pack Heineken beer
weird, mines just done the same thing. I sent an sms and nothing. I was then taken to the phone screen and it said something like invalid sim something.
I'm wondering if the sim card is not locked in place. I was fiddling around with mine yesterday and maybe forgot to lock the sim card in place.
Just a thought but maybe worth checking :wink:
what radio version do you have ? I recently have the problem that when people call me, the ringtone goes for about 2 seconds, then restarts, etc.
Meanwhile I can do nothing ( green button don't work) . When the caller hangs up my phone returns to the normal state.
I use radio 1.18. Thinking of downgrading to 1.17 which people say is more stable.
pleun said:
what radio version do you have ? I recently have the problem that when people call me, the ringtone goes for about 2 seconds, then restarts, etc.
Meanwhile I can do nothing ( green button don't work) . When the caller hangs up my phone returns to the normal state.
I use radio 1.18. Thinking of downgrading to 1.17 which people say is more stable.
Click to expand...
Click to collapse
I'm using Radio version 1.17, ROM version 1.72.00WWE
The SIM is firmly locked into place
ah..... :shock:
Hello folks,
I have the same problem now for a week... It's driving me crazy... At
some point in time during the night or the day my Qtek2020 gets weird.
The result is that people trying to call me can't connect but to viocemail,
and I can't receive SMS. The only way I can see that I am having this
problem is that whenever I try to send a SMS I get a message "your SMS
cannot be sent", and if I try to make a call, the phone seems to dial out
normally the first second, but then the DIAL-button (which is color-less)
becomes green again...
Please, if someone knows what's wrong or if someone had the same
problem and solved without having to default the whole thing, please
let me know what is the solution.. It is really annoying, so I now have
to randomly reset my phone throughout the day.
PS: my battery is now on 4% so I have to look for my charger, and
after that I can supply with info about radio-version etc. I am running
WM2003 by the way, and I've had no problems like this before, this
unit has been working fine until now. I guess it's a sw-bug? And I
am also wondering if this problem occurs whenever I pass a place
with low signal.. hmm, it's so annoying..
Thanks for any help!
Fred
I've been having problems similar to the OP for 2-3 weeks now (found this thread in a search before posting). It's damned annoying, as it means you can't really trust your phone - am I meant to reset every morning, or more frequently? It seems an intermittent problem, in so far as I've been receiving and making calls as normal, and then you someone asks 'did you get my text?'. Gritting teeth, you call the phone from a landline to find that calls are going straight to voicemail. After a soft reset all missing texts are received immediately, and calls can again be received.
When in this state other PDA functions seem to work as normal. However, I suspect that the power display is "suspended" too. On performing a soft reset after experiencing this problem today, I immediately got "your battery is extremely low", whereas before the reset I recall it was around 50% (vBar image). As others have stated, one clue that not all is well is that sent texts do not get a "Message sent" confirmation.
I've been racking my brains as to what's changed recently on my PDA. For family reasons I've been making a lot more calls than usual, but I also added TomTom Navigator 5 a couple of months ago, and so have started intermittently using BT. But I don't use Sat Nav that frequently, and this problem seems more prevalent.
I'm conscious that I don't have latest and greatest ROM, etc, but am vary about attempting upgrades without strong reasons.
Has anyone seen and solved this issue?
Have you tried cleaning the contacts on the sim card? After a while dust and general wear and tear can mess them up. Also as it's obviously(?) a phone problem it might be beneficial to call your service provider for a new sim card.
That's what I had to do last week. Wish you the best anyway.
It can't have anything to with the sim card as I'm having this problem with a brand new sim card.

Warning: Hacks for DLL on SD may cause 10sec powerup delay

Guys,
This foxed me for a few days and is worth keeping an eye out for.
Following I'll explain the issue, then show you how to test if you have this 'bug'. It's worth checking if you're an avid tweaker!
Explanation
There are several hacks/tweaks that move DLL's to the SD to give u some ROM space. The Opera cache hack is the one that floored me. They typically involve editing the registry so that the EXE and DLL search path is appended to include the SD card (usually \storage card\DLLs).
The issue
With these hacks, you may (ie I definitely did, and I definitely solved it by correcting this) find a 5 to 10 second delay 10% of the time that you turn on your device. This manifests as a real issue in several ways:
When you turn on, screen stays blank so you press power key again and screen flashes on then off, so you press again and finally you're in. Particuarly evident if you run WisBarAdvanced2 which is clearly looking around for DLLs
When you call up the dial pad, your keypresses take several seconds to respond
When receiving a call there is a long delay before your phone starts to ring. Even tho you answer ont he first ring calling party says "where you on the jazz or something?"
When making a call you get "dialing..." and the other party is actually connected and listening to you swearing about what a piece of sh1t your JasJar is cos it won't connect (actually, this may be a problem over and above the issue covered here - anyone else experienced this?)
Testing whether you have this issue
Go to phone app
Turn off JJ for 1 full second
Turn on and immediately press a number key
Did it take 10 seconds to respond?
Repeat 10 times, problem will hit me at least 8x within 10
If you find a delay, repeat whole test without SD card. Here I find that I get the problem once, but not thereafter. It's like the JJ needs to find out that the SD card is not there, and then it doesn't do this 10sec checking delay again.
The phone pad is simply a test that can work on all setups, and seems to have an over 50% success (failure?) rate.
Let me know if this helped you. Perhaps I had a unique situaiton such as the Opera cache hack combines with WA2?
Edit: Since fixing this, and one other issue, my JJ performs awesomely! The second issue is trning off UMTS until I need it. HATE that cos in ZA we have awesome 3G coverage, and I don't mind the cost. However, issue is that where there is a weak UMTS signal, JJ latches on and then becomes very unreliable in making/receiving calls (much like the old days of poor GSM coverage). Remember these devices nee to be in UMTS OR GSM mode - they do not run both at the same time.

Phone freezing

Hi,
I have a big problem with my Tytn (sorry if this is already been posted). Quite often the phone freezes, making it impossible to turn on again. The only thing that works is a soft-reset. What is worse, is that when the phone is in this state, although the green light is regularly flashing, it is unable to get phone calls even if the caller gets the normal ringing signal. No trace is left of the call, neither in calls list! This is a really serious issue: please, let me know if you have an idea of how to solve the problem.
Thanks!
I am having the same issue. I haven't been able to isolate it. I was havign to0 restart 1-2 times a day. Same systems press the power button nothing. Lights blinking everything looks ok. but nothing on the screen. and i miss calls. really pain in the ass. I loaded mobile secretary and it hasn;t locked in a day or two which is odd.
I also sometimes have to rpess the power button two times for it to wake
me too
It's happening to me too. I will lose service and the phone doesn't go out and poll automatically when service should be good. It may show 1, 2, 3 bars then when I try to make a call it hangs, and then get an x and a Y!, then searches for service. I have the GSM only hack installed and the activesync workaround and it still does this. It is not useable as a phone.
do a search in this forum.
one relevant thread here:
http://forum.xda-developers.com/showthread.php?t=285974
With all due respect, there is no solution where the link leads to.
I am having the GSM problem also. Just from time to time I am noticing an exclamation mark near the 'antennae' icon in the top bar. When I tap it, I read 'Service unavailable' in the balloon. From that point I may either soft-reset, or switch GSM flight mode on and off, which brings the PIN code keyboard and the phone works again.
I really don't think it is related to power saving, as it happened a few times in the car with TyTN on external power.
mnez said:
With all due respect, there is no solution where the link leads to.
I am having the GSM problem also. Just from time to time I am noticing an exclamation mark near the 'antennae' icon in the top bar. When I tap it, I read 'Service unavailable' in the balloon. From that point I may either soft-reset, or switch GSM flight mode on and off, which brings the PIN code keyboard and the phone works again.
I really don't think it is related to power saving, as it happened a few times in the car with TyTN on external power.
Click to expand...
Click to collapse
I think warmkiwi's link may be relevant to jimwormold's original post, which may not be related to your and angled1's problem of failing to poll correctly after dropping it's signal.
Mike
yes, it was. sorry, i should have quoted the original author (jimwormold)
well, sorry for being so picky on you :|
Now when we have defragmented the conversation I wonder if the GSM problem is reported more widely? and what is supposed to do in order to isolate the problem and fix it...?
jimwormold said:
Quite often the phone freezes, making it impossible to turn on again. The only thing that works is a soft-reset. What is worse, is that when the phone is in this state, although the green light is regularly flashing, it is unable to get phone calls
Click to expand...
Click to collapse
Sorry to do a "me too" posting, but I experience the exact same symptoms. There is no obvious pattern to when this happens, but it is a major problem, as there is no way (other than trying to switch it on) to distinguish whether the phone is working or not at any given moment.
I am running the latest (South African) ROM on my Vario II.
Philip said:
Sorry to do a "me too" posting, but I experience the exact same symptoms. There is no obvious pattern to when this happens, but it is a major problem, as there is no way (other than trying to switch it on) to distinguish whether the phone is working or not at any given moment.
I am running the latest (South African) ROM on my Vario II.
Click to expand...
Click to collapse
Given this thread now appears to have two distinct issues running together I better be clear that I am referring to the lock-up/freezing issue not the dropped GSM signal issue!!
To be honest there are quite a few possible causes for the freezing issue(s). I would suggest searches and the wiki on such things as (and you may or may not have tried some already):
1. Use of a Task Manager to properly shut running programmes otherwise they contiue to run in the background
2. Proper shutting down of Active Sync in addition to any task manager you may have, as it can re-start itself automatically (particularly overnight. Look for the "Fake Server Trick")
3. Always shut down Wifi when not in use (vital particularly overnight but also good practice to avoid lock ups)
4 For overnight and possibly other quiet times you can consider having your device automatically perform a soft reset to clear any running programmes that may block alarms/receipt of mail etc. Look for such things as xbar or SK schema
Mike
mikechannon said:
Given this thread now appears to have two distinct issues running together I better be clear that I am referring to the lock-up/freezing issue not the dropped GSM signal issue!!
1. Use of a Task Manager to properly shut running programmes otherwise they contiue to run in the background
2. Proper shutting down of Active Sync in addition to any task manager you may have, as it can re-start itself automatically (particularly overnight. Look for the "Fake Server Trick")
Click to expand...
Click to collapse
Yes indeed, although I think that both: a Phone App problem, and a GSM signal problem, are indeed the same, maybe only differently percepted and described by users affected.
I need ActiveSync to be running in order for DirectPush to work. If it conflicts with the phone, it makes the device unusable concerning push email functionality.
mnez said:
Yes indeed, although I think that both: a Phone App problem, and a GSM signal problem, are indeed the same, maybe only differently percepted and described by users affected.
I need ActiveSync to be running in order to DirectPush work. If it conflicts with the phone, it makes the device unusable concerning push email functionality.
Click to expand...
Click to collapse
I agree they may be cause and effect for some folks. Although I don't believe we can say that all the freezing and lock-ups are due to dropped GSM signal and freezing when failing to re-establish it. The items I list either taken together or individually have been found by others to work in some cases.
I appreciate that if you require Active Sync running then this is not a solution for you. I think the issue of crashing on loss of signal requires more analysis and I'm not aware of much discussion of it - though I could be wrong!!
Mike
I was fiddling with the phone yesterday and today, and I have a hypothesis that my problem is related to PIN entry screen that won't pop up but is silently awaiting a PIN underneath.
I was trying to ucheck the "Require PIN when phone is used" box in Settings but with no luck, my PIN is then refused with "Unknown SIM Error" message. Maybe it wants a PUK but I don't have it on hand to try.
My plan now is to:
- uninstall all Phone-related applications (PhonePlus, Dark_Blue Buttons, EZDial),
- request PUK from my office and try to uncheck the box,
- try prepaid SIM card which has no PIN
To observe symptoms I need two-three days, so I will rather not be posting until solid data is collected.
ps Mike, it is a pleasure to be on a board with people like you.
mnez said:
I was fiddling with the phone yesterday and today, and I have a hypothesis that my problem is related to PIN entry screen that won't pop up but is silently awaiting a PIN underneath.
I was trying to ucheck the "Require PIN when phone is used" box in Settings but with no luck, my PIN is then refused with "Unknown SIM Error" message. Maybe it wants a PUK but I don't have it on hand to try.
My plan now is to:
- uninstall all Phone-related applications (PhonePlus, Dark_Blue Buttons, EZDial),
- request PUK from my office and try to uncheck the box,
- try prepaid SIM card which has no PIN
To observe symptoms I need two-three days, so I will rather not be posting until solid data is collected.
ps Mike, it is a pleasure to be on a board with people like you.
Click to expand...
Click to collapse
Very kind of you to say so
Look forward to seeing your findings.
Mike
new phone
I'm on day 2 of my replacement phone from Cingular and the problem with losing gsm signal is non existent. The problem was hardware and fixed by calling and getting a warranty replacement phone. I'll let you know if the problem returns. Oh, and I have not been using the gsm only hack. I'm trying to see if the phone will work as designed first.
angled1 said:
I'm on day 2 of my replacement phone from Cingular and the problem with losing gsm signal is non existent. The problem was hardware and fixed by calling and getting a warranty replacement phone. I'll let you know if the problem returns. Oh, and I have not been using the gsm only hack. I'm trying to see if the phone will work as designed first.
Click to expand...
Click to collapse
Good news - hope it continues to work well.
Mike
I am reporting from the test field that my problem persists, despite uninstalling all phone-related extenders.
I have noticed that freezing is paired with disabling Bluetooth. So after switching the phone off (flight mode on) and back on (flight mode off), I also have to turn on Bluetooth.
EDIT: I was grounded for last few days at home and freezing problem was not occuring. I am now thinking that it may be related to switching band between GPRS and UMTS. My next step will be disabling UMTS for good. It saves a whole lotta battery, by the way. I am for the third day mostly on standby, with a few calls made, and I am still on 70%! (no 3G in the area)
I have contacted my vendor and asked about replacement policy, they are "checking this with the importer". It's a beauty of living in not-so-western country. Poland is the name.
mnez said:
EDIT: I was grounded for last few days at home and freezing problem was not occuring. I am now thinking that it may be related to switching band between GPRS and UMTS. My next step will be disabling UMTS for good. It saves a whole lotta battery, by the way. I am for the third day mostly on standby, with a few calls made, and I am still on 70%! (no 3G in the area)
Click to expand...
Click to collapse
I'm having exactly the same problem, very annoying because the staus LEDs keep blinking as normal. I too think the problem is UMST-GPRS switching related, as I also have problems when phoning while I drive with my car from a UMTS enabled into a GPRS only zone. The voice call is interupted and I get a loud noise, sounding like a scrambled voice, on both sides of the connection. At home my UMTS signal is very weak, so I think it happens when I move around the house to a place where the TyTN switches to GPRS.
I've put my TyTN to "GSM network" only now to see if this helps, but I use UMTS frequently so this is no long term solution for me.
pbw
same problem here, only gsm wil not help, new sim cards wont help either even other provider wont help
check: http://forum.xda-developers.com/showthread.php?t=287669
treid several different roms nothing will help
good luck
Hi,
mine was siffering of freezing issue, I sent a mail to HTC support, they don't know about it but the guy said me that I must to hard reset my device. Then no more freezes, I will keep testing it.
Regards,
Taguapire.
BTW: I changed my old and almost destroyed SIM card by a new one.

Instant Dropped calls on Cingular?

I keep getting calls that drop the second I hit the answer key. I'm using the latest Cingular based firmware for my 8525. Is anyone else experiencing this? I'm trying to determine if it is one of my installed apps or a problem with the phone itself. Thing is I have no apps that are meant to handle calls or VM so if other users are experiencing this please post.
I am not having this problem, 1st I've heard of anyone dropping calls instantly.
Were you located, I'm in chicago and know 4 other with the 8525 without any dropped calls.
NJ. I've been on the Cingular network for a few years now. I had an MPX220 before this.
In my opinion it may come from the magnet of the default case; give some try without it.
yeah, I've had it happen to me too. Interesdtingly, it didn't seem limited to my TyTN either. I had it on my 8125. Seems to happen most often when I answer using the softkeys instead of just pressing the green phone icon.
hmm. im not really sure which i answer the phone, both if im not wrong. I'll have to keep my eye out for that.
I was having a similar problem that turned out to be my case hitting the buttons as I pulled the phone out. I switched to a seidio clip case and it hasn't happened since.
there was a slight delay, so it actually disconnected about the time I hit the button. sometimes the call would answer instead of dropping, depending on which button was hit.
Same Problem on Vodafone
I bought 2 V1605s (tytn) 2 months ago for my business. I seem to have the exact same problem on both phones - about 20-30% of calls have this issue. Scenario is as follows:
Phone rings, after any amount of time Answer with either the green button or the soft keys and the call dies. The other party is routed to Voicemail at that time. While this problem is present I sometimes get a problem where I can't initiate a call - get an error that Cannont make an outgoing call due to lack of signal.
I have seen some suggestions that this (or similar problems) can happen when you are going into and out of coverage blackspots. My work and home areas both have blackspots, so it seems to fit with this.
Only solution I have found is a soft reset. I have tried the following:
- Set band selection to Manual - didn't work
- Set UMTS/GSM to GSM only - didn't work
- Do a hard reset (wiping data and other installed programs) - didn't work
- Make sure that all other applications are closed properly through task Manager (especially data-using ones) - Trying now - no results.
I'd appreciate any suggestions as I need this sorted - no matter how good this phone is as a PDA, I can't tolerate losing 30% of my incoming calls!
I've had similar issues. Last couple of days have been worse than others.
I am beginning to consider an alternate carrier -- the big V is better in and around NYC from what I understand

hermes giving problems

when i check my balance it shows failed and sometimes when a message comes the screen turns on and then after 2-3mins the message is recieved
any ideas if this is a radio problem because on other cell phones this works fine
By other phones do you mean non windows mobile phones.
I ask because they work in a different way when it comes towaking up the phone software for incoming calls and messages.
In simple terms a non wm phone is always on but the screen is off (so it reacts almost instantly). A wm phone cannot run all the time in the background or else the battery would be flat in no time - what with it's larger operating system and running applications. (It therefore has to truly wake up and start all those processes going - this takes time. It also accounts for the screen coming on and then a delay before it starts up the messaging/phone applications before either the phone call or text message can come through.
This delay is a price you pay for a more sophisticated phone wih more processes to run. There is however talk of the WM system being changed to run continuously like a regular phone - because in practice it takes a lot of power to start and stop the process when we put the wm phone in standby. So the benefit of stopping and starting processes may not be as great in saving power as first thought.
Regarding your other issue with the short codes for getting your balance for example. In my case with O2 *#10# should get my balance. I have never got this to work on my unlocked phone - it always fails. Whether this is true of a phone tied to a particular network I'm not sure. Perhaps someone else has an answer.
Mike
yes i was meaning a non wm phone.this doesnt bugs alot but the balance check always annoys me.
before hermes i got a htc touch(elf),it was also unlocked but didnot showed this error so what can i do about this problem?
i think this is concerned with radio version
sometimes calls from same network shows same name although the calling number is different
any ideas how can this be fixed

Categories

Resources