I was getting frustrated with the problems I was facing with GPRS in i-mate's new rom. Some people couldn't connect and disconnect properly, I personally was suffering from having my Red Phone button disconnect GPRS when I merely pressed it, not held it, every time.
I got pissed off with it last night, and decided to find the problem once and for all.
First, I cleared my extended rom, and did a hard-reset. I then noted that the red phone button sound reverted to normal, and that the GPRS didn't disconnect unless I held the red phone button. In other words, I discovered my problem lied within the extended rom.
So, then I went through cab by cab and tried to find out exactly which one caused the problem. All the obvious choices did not. I then stumbled upon the problem cab; the I-Mate customization cab (Default_ImateV112.002.cab). This little 74kb cab was causing my GPRS to disconnect whenever I pressed the Red Phone button. So, I recooked my extended rom without that cab, then hard reset. Voila, GPRS was working properly.
My comparison of the new I-mate customization cab with the older one, brought up one small difference in CM_Entries.xml, and it was exactly this small change that resulting in GPRS disconnecting when the Red phone button is pressed instead of held.
The lines that cause the problem are:
<characteristic type="Registry">
<characteristic type="HKLM\ControlPanel\Phone">
<parm name="Flags2" value="8" datatype="integer" />
</characteristic>
</characteristic>
The section of code that I identified to be causing the problem creates a key named "Flag2" within HKLM\ControlPanel\Phone. What this does is actually creates the Disconnect button we now see in the Connectivity bubble. It seems that enabling this button is the root of my (and perhaps other people's) GPRS problems.
Here is the information on this code:
To get just the disconnect/time online in your bubble, Tweak the following key:
[HKEY_LOCAL_MACHINE\ControlPanel\Phone]
"Flags2"=dword:00000000 = no button disconect in buble con.
"Flags2"=dword:00000008 = button disconect on buble con.
"Flags2"=dword:00000010 = button disconect and time con. on buble conection (hex)
Removing the key "Flags2" solves the problem, but removes the disconnect button (I assume this is the same as setting it to 0). The new default 8 setting is the problem. Setting it to 16, which adds the button and a connection length timer seems to be problem free from my testing, so if you like the disconnect button, I recommend setting it the key to 16 (DECIMAL, 00000010 HEX) and giving that a try, and if you aren't satisfied then remove the key altogether. Reset after any changes to the registry to see the results.
THE CABS BELOW ARE NOT PATCHES. THE SHORT TERM SOLUTION IS TO CHANGE THE REGISTRY KEY. THESE CABS ARE MEANT TO BE REPLACEMENTS FOR THE ORIGINAL PROBLEM CAB IN YOUR EXTENDED ROM, NOT TO BE RUN SEPERATELY
I have also made 2 cabs meant to replace the old Default_ImateV112.002.cab within your extended rom for a more perminent solution.
http://qlink.queensu.ca/~3bsg/16Flags2/Default_ImateV112.002.cab : Sets the key Flags2 to 16, keeping the disconnect button and adding a timer
http://qlink.queensu.ca/~3bsg/RemovedFlags2/Default_ImateV112.002.cab : Stops the key Flags2 from ever being created, removed the disconnect button[/b]
Sweet, (still looking for the coffee hack), thanks
Re: Solution to i-mate 1.40 GPRS woes
TheLastOne said:
The lines that cause the problem are:
<characteristic type="Registry">
<characteristic type="HKLM\ControlPanel\Phone">
<parm name="Flags2" value="8" datatype="integer" />
</characteristic>
</characteristic>
Click to expand...
Click to collapse
Maybe imate fixed this already???
I did fresh install from imate website and after reading your post, I checked my Registry and it is already "16"
Let me verify this.
Edit:
I went through a lot of trouble to disprove this.
I just went to clubimate.com, downloaded a fresh rom, reinstalled the extended rom, and can disprove this. Nothing has changes. Flags2 is still set to 8 by default. Problems still occur with GPRS.
Great solution! Applied this to my pda2k and JAM and could not be happier. Make sure you upload it to the FTP.
Better why not use Phone Alarm 1.13.2 latest version.It does the same as explained and I am using it.....
Re: Solution to i-mate 1.40 GPRS woes
Your registry hack works very nicely...thanks.
My problem is more than not after a phone call the GPRS will not connect again until I either do a reset of the ppc or go into flight mode and come back out.
Any ideas on a fix for that?
tekhound, you have changed your registry and then reset your device to apply the changes? Go into your registry and change the Flags2 key in question to 16, then reset your device (or run the Flags2 = 16 cab I included in the first post). If that doesn't fix your problem, then your problem is different than those faced by others.
TLO...
I actually had your cab file already installed. I went ahead and deleted the reg key all together. Hopefully that will work, since I use the GPRS for my push email more than I use the phone.
Thanks for all of your hard work. I find it amazing that groups like this and people like you seem to know more about this stuff than the people who make or support them.
Update....
I was still having problems even after i made the changes and uploaded the cab TLO made. No luck on keeping the the GPRS not only connected, but be able to connect it again with out having to reset.
I decided to copy all of the extended rom files out completey and do a hard reset. Everything has been working fine so far without any disconnect or reconnect problems I experienced before. I have since gone back in and added the battery patch and a few other files I wanted.
I will add a cab at a time and hopefully see when the cab causing the problem is installed.
I have a sneaky feeling that one of those cabs does something that makes the BA not talk to the US T-Mobile network correctly. I have seen a few post on different boards from people that use the US T-Mobile network have similar problems when they updated their imate PDA2K device to the new version.
I will post with any updates.
Thanks again for everyones support!
i would like to know what you find, i had a similar problem before the Imate rom was released; gprs would not reconnect after the first connection without a soft reset. What worked for me was not installing the AKU26_RC20 Caller id cab. I was already using GBSOFT Tweak to enable the disconnect and time display in the gprs bubble. But other people reported no problem using that cab so may just be coincedence.
My experience is (unfortunately) consistent with tekhound's, even after installing the TLO's cab. Although TLO's cab is still an improvement with the Disconnect button and counter. I am also with T-Mobile in the US.
Odd. Then perhaps the different GPRS problems to not share the same cause.
I must say, I am not facing the same problem as you guys are. After changing the key to 16 and reset, GPRS has worked flawlessly.
However, I think it is important to note that everyone who is still facing GPRS problems is in the United States (I would assume using T-Mobile). Are all your devices SX66's as well?
I'm having problem using my i-mate JAM.
i-mate's forum led me here via howardforums....i-mate recently released their JAM ROM upgrade and that looks to be where the GPRS connection problems have surfaced. They are not being reported as specific to T-Mobile or even the US. Users with different carriers and/or the ROM for another country (at least saw UK referenced) are finding the bug.
From a quick scan of i-mate's forum for the PDA2K, similar symptoms are being reported after the ROM upgrade for that device.
I used the new hacked .cab for a few days and had no problems whatsoever when I installed it from a hard reset WHEN NOT INSTALLING THE EXTROM. The GPRS ran great and no longer disconncted with the touch of the red phone button.
Unfortunately, I had problems with "Phone Pad" among others which I thought could be solved by installing the full 1.11 EXTROM. After installing the extrom and the .cab fix, my phone pad was working fine, but now the damn "Unknown reason" Error message is back again which leads me to belive that there is something in the extrom that is messing stuff up.
I'm afraid that I'm going to have to head back to 1.06WWE now for the 5th time. It's pain in the ass as I have to set up my exchange server settings all over again. I'm getting really tired of Imate's piss poor programming. Do they not test their own software? I noticed problems minutes into the new ROM. It's unacceptable.
Well, that's my ranting raving for the evening. I'm sure that after I spend my Saturday reinstalling everything back to 1.06 that I-Mate will release a file to fix everything. :-(
Maybe it's me....but I thought that this was the B/A forum.....
:?
mbc said:
I'm having problem using my i-mate JAM.
i-mate's forum led me here via howardforums....i-mate recently released their JAM ROM upgrade and that looks to be where the GPRS connection problems have surfaced. They are not being reported as specific to T-Mobile or even the US. Users with different carriers and/or the ROM for another country (at least saw UK referenced) are finding the bug.
From a quick scan of i-mate's forum for the PDA2K, similar symptoms are being reported after the ROM upgrade for that device.
Click to expand...
Click to collapse
I also have the same problem with the new rom in HK. So, I can confirm that this is not operator related. It also happened to magician as well.
I installed again a previous version of wireless manager from other rom and will report later. Not the 'Remove wifi logo' one but 'Default_OEM_BA_09080401.CAB'.
thanks, TLO! I appreciate all of your hard work! This added the timer for me and doesn't seem to kill my GPRS connection when I hit the hang up button more than once, as it was before.
Now if I can just get the darn device to actually consistently MAKE a connection without requiring a soft reset...
The 'Default_OEM_BA_09080401.CAB' is no good.
It also had the same effect.
I hard reset my device and change the autoconfig file to NOT to install any patch. I then check the connections by turning on and off again and it's working so far. Will report again tomorrow.
Cheers,
Related
Hi
I have been playing with this for a day now, and it has introduced more bugs in the wifi functionality. If you want to use WiFi from your IIs then I would avoid this 'update' like the plauge.
What you get:
- ROM: 1.31.00 WWE (13th Dec 04) so this is 2.5 months old
- Radio 1.06.00 (1.06.02 is latest)
- ExtRom: 1.31.139 WWE (no real updates to existing progs)
Whats Better
---------------
- The camera performs better in low light conditions (I used to get vertical lines on the screen
- Bluetooth stack build 3500. A vast improvement, but the latest is now build 3900 which some say solves the 'scratching noise' that is heard in some headsets
Whats Worse/Not Fixed
---------------------------
- O2 Active V3.5. Its bloody awful - spends its life redrawing the screen, its very sluggish, and adds nothing to the today screen. I never used to use the old version, but having the O2 icon was handy for its ability to list the active connections and terminate them. Much is made of the ability to change the position of the icon (which I never found to be a problem in the first place. Tapping the new icon starts O2 Active rather than listing the active connections. To list active connections, you need to tap and hold for 5 seconds. I find that after tapping and holding, I get the menu, but that the menu then fails to respond to my 'close connection' taps. I reverted back to the old O2 active program.
- WiFi. They have completely buggered it up. It was unreliable at best beforehand. I have a network at home, which I finally pursuaded the device to connect to after multiple resets. I headed into work this morning (2 AP's) switched it on, and it just sat there searching for the network. I went into Tools-->Network cards, and see the work network listed as 'connected' (it was not connected, I had not given it the PSK yet). I soft reset the device, and it finally saw the network and prompted with the usual 'Internet/Work' dialogue. I was then asked for the pass key. At this point I noticed that there is no longer a possibility to activate the soft keyboard in order to enter the pass key (A right pain in the arse when the passkey is just a random multicase/numeric key, and all you get are ** on the dialogue). Anyway, I entered the key, and the device refused to get a valid IP address. Doing IPconfig showed that the wireless card was trying to use an old GPRS IP!!! I tried a renew (3rd party ipconfig tool). I tried stopping and starting wifi. Eventually, I soft reset (still the same), so I stopped wifi, soft reset, started wifi - and *finally* it decided to go and get itsself an IP address. (this is a bug I saw in the old firmware, but its worse than it used to be).
- WiFi still marks the wrong networks as 'available', i.e at work, 10 miles from home, my home network is marked as 'available' and my work network is marked as 'unavailable' !!! (this is an old bug)
- In Network adapters, the dialogue, 'My Work Network Connects To:' is blank, and there is no longer a possibility to select work/internet (options are blank). This is new to v1.31.139 (anyone else also missing this)
- If you select a wifi connection and change it from being a 'work' connection to an 'internet' connection then the change does not stick. This is new to v1.31.139
- In the MMS applet, it is no longer possible to select a 'modem' directly. I used to be able to select 'O2 Active'. You now have to select a profile that includes an appropriate modem. This is new to v1.31.139
- When editing a network profile in 'network management' eg: My ISP. the device still forgets to display existing modem/vpn connections. (same as old version).
Out Of Date Software / missing software
-----------------------------------------------
- Photo Contacts (CallerId cab) is still version 1.17 (latest is 1.20)
- Missing O2 plus - other o2 devices include this
- Missing Intelipad
- Missing Smartdialer
- Old build of Java Midlet software
- Old build of MMS composer software
Other Thoughts
------------------
For my money, the device feels more sluggish than it did before. Though its difficult to prove this!
O2 has spent far too much time on that O2 Active rubbish - does *anyone* actually use this [email protected]?? - and not enough time integrating/testing the latest versions of CE, drivers, and third party apps.
I'll add more to this as I find new bugs, and send it all off to O2 in a couple of weeks.
What I am now using
------------------------
I am now using v1.31.139 + Bluetooth build 3900 + PhotoContacts 1.20 + Java build 1004.
----------------------------
Additions: 1/3/05
- SMS notify no longer seems to work. Anyone else suffer from this? MMS notify works fine and SMS notify is switched on. Perhaps the notify event is missing, but I have no idea how to sort this.
- VPN over wireless lan is still not possible - it tries and fails to connect. VPN over GPRS still works OK.
Additions 02/03/05
- SMS Notify problem is *not* to do with the rom update. I removed the registry key: HKLM\software\microsoft\inbox\svc\outlook since I had no need for the outlook folder in inbox. Removing this also kills off SMS notify!! I backed up, hard reset, preventing the stuff in the extended rom from installing. Installed PHM regedit, exported the outlook key, restored my backup and imported the reg key!!
- Internet/Work settings missing from Wlan setup. After restoring the backup, these had returned. Pretty strange, perhaps they were linked to the same registry key. No additional software bar the contents of the extended rom had been installed. If anyone else gets this, I suggest back, hard reset, restore might fix it.
Regards
Nigel
I have the same version with the latest radio build and cannot got the device to connect to my home Wifi what so ever.
Not exactly much use. It detects the network but refuses to connect. Either it says its connected but does not get an IP or it continously prompts for the network key.
I have also upgraded and am finding that the device often freezes when I try and switch it off, this happens about once or twice a day needing a soft reset.
I dont use the active stuff (which I never use) and am dissapointed that the O2 icon now starts O2 active rather than list the state of connections and allow you to trun them off i.e GPRS.
I agree the device does seem to be slower, I think I will be going back to the original code base and applying the BT patches, anyone know where there is a CAB installer for 3900?
check the ftp server
ftp://ftp.xda-developers.com/BlueAngel/CAB_Files/Bluetooth Upgrades/
username xda
password xda
its the file that ends in 3900.
I installed 3900 over the recent O2 update (3500) and all went fine. Just do a soft reset before playing with bluetooth or it will moan about an expired stack.
Nigel
SMS Notify
Hi
Anyone else found that the SMS notify stops working once the latest O2 update is installed. MMS notify works, but SMS does not - its damned anoying!
UPDATE: Found the reason for this see end of original post
Nigel
Thanks for the comments on the update. I think I will stay with the original 1.12 ROM! Where can you get the other updates for the Camera and Java and Bluetooth etc? I'm currently running Bluetooth 3500.
Cheers
This is why you should sell you XDA IIs on ebay and buy a XDA IIi :lol:
Well that IS a concept! Thanks made me grin!
Hi since I installed the new Rom, my clock keep on freezing. The phone goes on standby > then it freeze. If I wake up the phone , it will still be frozen.
I have to click on start > Today in order to refresh it. :evil:
Any ideas ? It's still happening with no other today pluggin. :x
Would you recommend we dont bother upgrading the ROM atm then?
I upgraded also - the process was simple and took around 10 mins. This made my Bluetooth much more reliable and over a greater distance. I also find the 2s locks up frequently and requires soft resets.
Does anybody know how to remove the entire o2 software - I dont know anybody that uses it and Im sure it would speed up the whole device.
Remove entire O2 software:
You mean everything in the extended rom or just o2 active?
Hard reset, and when the message pops up about installing blah in 3 seconds (after you have done the touchscreen config) then soft reset. This gets you a plain vanilla HTC Blue Angel before the operator has installed its sh1te on it.
You can then selectively install just the bits you want, download the extended rom from the ftp site here, or unlock yr extended rom, copy out the cabs to main memory/SD etc, and then tap just the ones you want to install them.
If you just want rid of o2 active, then hard reset, and wait until the corporate/personal? message appears and then soft reset. O2 active is the last thing to be installed.
Nigel
mhanbury:
Hunt them down on the FTP site. Compare the version/build numbers with those in the new O2 extended rom.
Nigel
eskimofisherman said:
I upgraded also - the process was simple and took around 10 mins. This made my Bluetooth much more reliable and over a greater distance. I also find the 2s locks up frequently and requires soft resets.
Does anybody know how to remove the entire o2 software - I dont know anybody that uses it and Im sure it would speed up the whole device.
Click to expand...
Click to collapse
Hard-reset your xda.
When the Personal/Corporate screen comes up, select corporate and enter 0506 - zero five zero six
This won't install active.
I'm getting a new XDAIIs (my 3rd one) , I will stay away from the new update and just put the bluetooth/ radio and contact manager manually.
That new update is just a piece of [email protected] :evil:
jeux_1 said:
I'm getting a new XDAIIs (my 3rd one) , I will stay away from the new update and just put the bluetooth/ radio and contact manager manually.
That new update is just a piece of [email protected] :evil:
Click to expand...
Click to collapse
If you buy a new XDAIIs in the UK now you will get it with :
ROM Version: 1.31.00 WWE
ROM date: 12/13/04
Radio Version: 1.06.00
Protocol Version: 1337.38
ExtROM Version: 1.31.139 WWE
Ive had mine for 2 days now and ive had to soft reset about 6 times! and Hard reset once!
and this is annoying the hell out of me! can anyone tell me what im doing wrong. Why is it that whenever I do a hard reset I have to change the name of my activesync folder? If I try to keep them the same, it says I cant because there is already a device with that name!?!? :twisted: Or am I just being a noob?
irelmo said:
jeux_1 said:
I'm getting a new XDAIIs (my 3rd one) , I will stay away from the new update and just put the bluetooth/ radio and contact manager manually.
That new update is just a piece of [email protected] :evil:
Click to expand...
Click to collapse
and this is annoying the hell out of me! can anyone tell me what im doing wrong. Why is it that whenever I do a hard reset I have to change the name of my activesync folder? If I try to keep them the same, it says I cant because there is already a device with that name!?!? :twisted: Or am I just being a noob?
Click to expand...
Click to collapse
This is really wierd. My IIs works fine - doesn't lock up, doesn't need hard resets or anything so drastic. I don't have any other apps on the device though, just the standard one's O2 supplies (GPRS Monitor etc).
What other apps are people running? I'm guessing Today screen plugins are causing grief (Pocket+ etc)
yeah I did tried my phone with no today plug in but it is still crap, was working just fine with the previous rom......... what have I done :x
At least it keeps me busy....
The problem is you should have bought a XDA IIi not a XDA IIs.
Mike
Hi,
I just upgraded to 1.40 rom and noticed that once I turn off wireless from the wireless manager, i can;t turn wireless back on until I reset the device. Is anyone else having this issue?
Thanks,
Skumky
Yes and no.
I've experienced the same problem, but I've also had it with 1.12, 1.22, 1.31 and 1.33 too so I'd comfortably say it's not specifically related to 1.40.
I've also had this problem with the following radios: 1.02, 1.06.02, 1.08, 1.10 and 1.12. (I like to upgrade hehe)
Sorry that wasn't much help, but really just trying to say I think it's more a bug with the operating system itself and not a specific version. Perhaps combination of software affects it and thus you've never had it before. I don't know :-(
I have also upgraded to 1.40 and the wi-fo worls perfectly. I dont face your issue.
I have also upgraded to 1.40 and the wi-fo worls perfectly. I dont face your issue.
I've experienced this with the 1.40 and 1.12 radio.
No problems to report here about the WiFi-module. Works fine. Is it related to the security-level that you run on your WiFi-network? I use an 64-bit WEP-encrypted protocol, and leech on open networks , so more then 64-bit it won't get. Maybe an increased security-protocol causes the system to hang?
No problems here. I did have that problem in an earlier rom combination however.
1.40 WIFI
I had the same problem, so I ran the WLANPatch.CAB from the Cingular update. This cured the problem, so I put it in my extended ROM and did hard reset but the problem came back. As a temporary solution I just rerun WLANPatch.CAB after Hard Reset and no problems so far..
I have that problem all the time. When my wireless manager reads "not connected to network" before I turn it on, it usually works, but after I've turned it on and off again it says "wireless off" instead, and then there's often no way to get it to work again.
I have a feeling this is caused by Omega One Battery Pack's custom "ok" button - I guess it closes the app in an incorrect way. What I usually do is tapping Start->Today instead of "ok" to exit the wireless manager after I've turned wireless on or off. This seems to solve the problem most of the time.
same problem here as well. Was trying for the last hour to turn wifi on, no go. Did a soft reset and wifi was already enabled when it startled back up. This has happened to me with previous roms as well. Guess its a "feature" of the phone.
SBP Pocket Plus will cause this also (customized close)
Has anyone tried my suggestion? Make a habit of just tapping "start :arrow: today" instead of "ok" each time you use the wireless manager and the problem should occur a lot less. If it does occur, the only way out seems to be a soft reset.
Also, does anyone know of a more structural way of actually solving the problem instead of working around it like I do?
Yeah. Don't turn it off!
Don't Turn it Off..
The only problem with that is that when you drive down the road, it tries to connect to everyone's wireless network and keeps popping up those ' Do you want to connect to John's' network' boxes...
Exactly! That's the fun part! And around 70 % of those networks, at least here in Norway, are totally unprotected! :twisted:
Ah!... so now I understand what "free internet" means in those Norweigen commercials :wink:
Hello,
My T-Mobile MDA Vario spoke Dutch which was very unformortable so I unlocked it and installed the Qtek ROM. Installation was fine.
However, it kept on being confused about the state of the "flight mode"; either I could make phone calls even though the icon said it was not connected to the network (aerial with X) or it did not want to connect to GPRS even though it was on the T-Mobile network
Otherwise it all worked fine.
In an attempt to get rid of this annoying behaviour I installed the K-Jam ROM found on the FTP server of this website. Installation was fine again, however now the device soft resets itself all the time and does not always want to turn on when I push the button on top. The soft reset frequency is very unpredictable, and turning phone on or off does not really make a difference.
Any clue?
Many thanks in advance
Manhattan.
It looks like the reset problem is solved after installing an updated i-mate ROM that resides in the upload section of this site's FTP. It seems to me it has only an updated extended rom part, perhaps someone has figured out what's the difference?
thanks
manhattan
what's the filename? i couldn't find it...
K-JAM_WWE_1010903_106_10110_ship.exe
i new to this whole pocket pc thing, and i found this site and started upgrading my t-mobile mda. first i upgraded the rom to the k-jam upgrade and everything worked fine. then i started messing with the registry with registry wizard. that was fine also. but as soon as i hit the edge icon tweak, i can no longer connect to gprs. i get a msg saying
"Cannot connect. make sure your phone is turned on, or tap settings to check your connection settings. "
can anyone help me. i didnt alter the settings from when it was working so im unsure of what the problem is. any help is greatly appreciated
sounds like ou ahve been doing a fair amount of tweaking. Even in the registry. Are you sure it was the Edge icon tweak that did it as my Cingular 8125 is running 2.16.9.1WWE and I have made that change and mine works fine. My wonder is if one of the previous changes didn't take affect until a reload or a new program load, and that is what actually caused the problem. I loaded some cingular cabs yesterday and it broke activesync.
ethorn said:
sounds like ou ahve been doing a fair amount of tweaking. Even in the registry. Are you sure it was the Edge icon tweak that did it as my Cingular 8125 is running 2.16.9.1WWE and I have made that change and mine works fine. My wonder is if one of the previous changes didn't take affect until a reload or a new program load, and that is what actually caused the problem. I loaded some cingular cabs yesterday and it broke activesync.
Click to expand...
Click to collapse
yah i know. but even after i restored my original registry settings i still cannot connect. when i try to connect, the window that shows gprs is trying to connect flashes 2x then it reads the msg i posted. any ideas
none here... I hope someone else can help, or you can hard reset and try to do the changes slowly soft reset a couple of times after each change until you figure out which one cased it. Each change including installed programs.
Sorry
mine does the same thing and I have been able to get it to connect without reset. Tap your signal bar on screen and turn on flight mode than turn off it will reset connections. It happens after every sync or charge for me and once we are able to unlock the cid and install the cing ext rom it might go away.
i actually just got rid of the program and it works now
Greetings fellow tweakers,
I am having a problem with my newly acquired US-version T-Mobile MDA Vario (aka HTC Wizard).
For some reason, I can't get ANY 3rd party SIPs (software input panels) to work with this damned thing. NONE. I have tried at least half a dozen (Calligrapher, InterKey, etc.), and the result is always the same. The SIP installs, and when I click on the SIP icon, the option shows on the popup menu (although that menu takes FOREVER to display). Then, when I try to select it, the device reverts to the default keyboard SIP and the one I installed never works.
I once had this problem on my older Wallaby device, and it mysteriously went away. Is it possible that I have a corrupted DLL or registry setting somewhere?
Is anybody else seeing this kind of problem?
Thanks, and happy hacking.
- Justin
This is a know problem with the WM5 devices. I had the same problem.
Luckily Fitaly made a version 4 which doesn't have this problem.
All the other alternetive input methods suffer from this problem.
A small workaround: Soft reset and then choose the SIP of choice before opening any other programs. Works most of the time. Sometimes Todayplugins can interfere.
Wouter
I've tested a bunch of SIPs, and there's several where after the install, you need to soft reset first. Some of them actually do this for you (TopKey was one of them, I think).
I know this topic is months old, but I have recently run into this issue. I'm using Molski's WM5 v3.3 and am getting the EXACT issue as the 1st post recounts.
I install calligrapher, soft reset, run anything, click the keyboard icon (in order to change input methods), the PDA pauses for 7-12 seconds, menu pops up, I click on calligrapher, the keyboard icon remains and the input method doesn't change.
I absolutely LOVE calligrapher, and this is really worrying me on this AKU version.
Is there a fix for this or another AKU3.3 ROM that allows calligrapher to work?
Lowkee