Database Info

Annoying o2 logo/ XDaIIi

All
I have an XDaIIi on the o2 network uk. The o2 logo is permanently displayed in the WA area and I do find it irksome and annoying. On my previous phone I was able to remove this by removing the o2 UI active interface application. On this phone this doesn't seem to be possible as it keeps telling me the application is in use, read only etc...
I have gone to Windows folder and deleted associated files but I cant seem to get rid of;
Windows/fonts/xpdr_o2.ttf
Windows/Mobile Solutions/O2ActiveUI/Modules/Connections/connections.exe
Can anyone advise how to disable this at all please so that I can clearly see the icons in WA that I want to see.
I have tried telling WA to ignore o2UI but it doesn't seem to make any difference.
All help appreciated
NB the beta version of Wisbar Advance works fine with the XDaIIi, a must have for any user and well worth the minimum cost!

did you look if it's started in the
windows\startup
and if so tried to remove that shortcut

Doing as RudeGear WILL work because it's exactly what I myself did last week.
No more annoying logo!!

I just removed "connections.Ink" from the start up menu and yes it does appear to have worked.
Thanks both!
Probably silly of me to ask, but why do they put that bloody logo there after all the unit is stamped o2 on the case, so why????

It's not a logo thing, if you tapped it you get a connection dropdown list, for GPRS or USB connections etc.
It's just crap, s'all.
Ant

WM5.0 SMS Alert Fix v0.01

This Patch is compatible on the Blueangel and Himalaya
This will fix the tiny issue when receiving SMS while the Device is in the suspends or off MODE.
Problem occurs when the device is turned off and a sms arrives.
Following are the two cases than can occur when the Device is in the suspends MODE when the TEXT Message had arrive.
On most occasion, the device will vibrate but it will not turn the device on and it leaves them unaware of the new SMS especially for other who disable the vibrate for New Text Notification.
On worst cases, the SMS is not receive until the device is turned on.
This little program attempts to fix this two possible issue by turning the DEVICE ON when it receives a SMS.
And for the Second case, it happened when the tmail.exe(Inbox/Messaging) is close by other program that closes an Application when the "x" or "ok" button is tapped like SPB Pocket Plus, Magic Button, Vbar, Wisbar etc..
If you are using SPB Pocket Plus or Wisbar it is always recommended to include \Windows\tmail.exe in your Close Exception.
PS.. This is just an attempt and probably not the best solution. Use this tool on your own risk.
Written by Toenaild
Orginal link Here!

i've downloaded the files... now how do i use them?
thanks!

It just work by it self, after you install it )

it's working. great fix.

Sorry to ask the same question again, i've downloaded the files (4 files)
but my computer doesn't seem to recognize the files and can't be open or install.
Pls help!
TQ!!!
ramram said:
It just work by it self, after you install it )
Click to expand...
Click to collapse

I've successfully installed it, but the problem continues.

Same here..installed the cab...problem still there

Argggh!! I think I did something stupid.

I upgraded our first SPVM1000 (xda2 from orange) with WM5 and it all seemed to work fine.
I then up upgraded the second and it went fine. The second one is still workign completely fine with no problems. We noticed that the first one could not get reception. If you put its sim card in the other phone then it works. Now I tried with with Orange and Vodafone sims. They work in PDA 2 but in PDA 1 there is no reception (it was working yesterday).
Then it kept coming up with an error saying that it was sorry for the inconvenience but there was an error with cprog.exe.
After a reset (power button and soft reset button) that stopped happening but then I found that I could not active sync PDA1. It cant connect and so connects as "guest". After what used to be a hard reset, everything is still as though I just did a soft reset with WM5 - not sure why.
Then I tries to backdate it to the old rom. If I use OSImage tool it wants it to be active synced which doesn't work (v3.8 or v4.0). I also tried to reupgrade with WM5 again (a fresh installation) but althoght it will go into boot mode with Serial 1.03 and then USB 1.03 appearing on the screen, the upgrade fails. It says there is a communication error.
Everything is working with PDA 2 so it cant be a connection fault. I think I did something and now I got myself in quite a pickle.
Can anyone help please?
I'd be happy to reset / reboot right back to the beginning again though I'd like to keep WM5.
Thanks
Anthony

Solution (how to hard reset in wimdows mobile 5)
Hard resetting WM5 has fixed all of these problems including the phone reception. To hard reset (sometimes called clear reset in the forums) you have to press the tape and camera buttons and then the soft reset with the stylus. This is on an XDA2 (SPVM1000) and is different since upgrading to WM5 (prev power button and the soft reset did the trick). I found lots of websites giving different instructions on how to do this but for the XDA2 type this works.
Ant
)

Hi
I am having turabul whit my mda vario 2
3 months a go I got the phone from t mobile is been came whit the windows mobile5 and I install the windows mobile 6 but I am having turabul whit it and I when to go back to windows mobile5 now I call the T-Mobile customer service they cudont help me and refer me to manufacture to solve the problem.
I tray to install the window mobile5 but is giving me turabull code 224 devise is not responding I tray to dart resetting is well but instil is running on window mobile 6.
Can you pls help me to install the window mobile5, or have to delete the rom update.

Hey Bro, you're knocking on the wrong door, this is the "Himalaya" forum you need to check out the "Wizard" Forums next door

Reply Deleted

Voicemail Icon Issue Anyone???

HI there, I was using WM6 since we all got a chance to, and i did notice since very early stages, of WM6 developement, my Uni started having a REAPEARING VOICEMAIL ICON issue. Even after listening and deliting your voicemail (BTW i am on Orange) the icon stayes there. Which began to be really annoying recently, so i called orange thinking its their fault, as usual, but they could not do a thing (as usual).
I hard reset the device -- didnt help
I reflashed with all other possible options of WM6 -- didnt help
I tried different Sim -- didnt help Believe it or not.
Anyone has any idea how to get rid of it???
Thanks

Voicemail notification
I think you'll find that this an Orange issue. I had the same problem with WM5 & 6. Orange flush something out of the system from their end it clears the voicemail notification from your phone after a warm reboot. Just don't tell them your using WM6!

JUST CAN'T fix Q9h WM6.1 SMS timestamp error.

Hi everyone!
I've been going through this ENTIRE forum, and countless others on top of dozens upon dozens of google searches, and I still haven't found a solution to my SMS timestamp error.
All the solutions offered up by people seem seriously promising, because they seem to help a lot of people, and that is what's kept me hopeful: that someone out there/in here can help me fix this problem.
Basically, I have an unlocked Fido Motorola Q9h, that is being used on the Rogers network. Never delved into flashing my device, cuz I was happy with WM6. Not to mention I'd got it tweaked to a very lovely point
Then a week ago, my phone locked up after I'd put my phone into airplane mode (I'd done this countless times before with no issue), and just would not let me turn the antenna back on. Nothing I tried worked, so of course I eventually caved and did a hard reset. That was when I figured I would give WM6.1 a try, seeing as how my device was gonna be starting from scratch anyway.
I flashed to an unlocked AT&T WM6.1 ROM, and went ahead with all the registry tweaks to remove all the bloatware. Phone is pretty damn clean if I do say so myself. I've got PHM on there, GPSID, CHome COnfigurator, and that's really about it.
After all that was said and done, and I got my first SMS, I realized the message was timestamped 4 hours behind. Every single SMS from every single contact shows timestamped 4 hours earlier. In the threaded SMS stream, my messages are timestamped correctly, but the other peoples' aren't.
Example:
Me (7:37): Send me a text to see if this timestamp issue's been fixed.
Steph (3:37): Okay =)
The strange thing is that MMS messages come in with the correct timestamp, and that is something that seriously boggles my mind.
Please, please, PLEASE. If anyone out there has some kind of suggestion, I would absolutely love to hear it. Here are the remedies I've tried that have had no effect:
-Installed DST cab from Microsoft.
-"TrustTimeZoneField" w/DWORD value of "0" minus quotations of course
-"TrustTimeZoneField" wDWORD value of "1" to allow the device to trust the provider's time just in case my phone was screwing up.
-"RcvTimeStamp" w/DWORD value of "1"
-tweaked some "NetworkTimeSync" (or something along those lines) entry to a value of "1" instead of its current value of "0," but nothing.
I'm at the end of my rope here guys and girls, so please, anything you can suggest that I haven't already tried would be infinitely appreciated
Thanks in advance everybody

although i dont know the answer ive got a thing for you to try
in the setting section make sure you regional settings are set correctly

Thanks Pilot, will double check those settings. Well, as per your instructions, I've double-checked the settings, and they're correct. Have my locale set as English (Canada), and nothing. Even changed it to English (United States) just to see, but to no avail.
*sigh*
I am almost at my wits end...Is there no one out there with a Q9h running the unlocked AT&T WM6.1 ROM, that's having the same issue??? Or even better, someone out there who's SOLVED the issue?
I've even called Rogers and they suggested a new SIM card, seeing as how I have the original SIM from Rogers, and I'm waiting on it. I've even tried my sister's SIM which is a new one, but nothing. Figure it HAS to be the ROM

Found a solution to timestamp issue with q9 & wm6.1!!!
Hi everyone!!!
I can't believe I'm actually going to be the person posting the solution to this problem, but I guess it's true that perseverance pays off
This post is in regards to the sms timestamp issue that I've noticed several people are having with the moto q9 once they upgrade to wm6.1 and are on a Canadian service provider.
***This solution involves modifying your device's registry, so if you do not feel comfortable or are unfamiliar with the process, please do not proceed with the modification. I will not be held responsible for any bricked/malfunctioning devices as a result of this tweak***
Use a reg editor (I used the free PHM registry editor), and navigate to:
-HKLM (HKey Local Machine)
-Software
-Motorola
-RilDrv
Now that you're in the RilDrv Folder, there should be a few more folders in here...don't navigate to any specific one, just click the "values" softkey (whatever it may be for your devices), and somewhere in the values that become visible, you should see one that says "LocalizedTimeStamp." Open that value and modify it's value to "0" (without the " " of course)
Reboot your device, wait 10 seconds, cross your fingers and toes, and restart your device. Once your device is fully booted, and seems to be functioning normally, send yourself a text message, and check the received timestamp. It *should* be correct (ie. a minute or two or less in the future of your sent timestamp). To be sure it isn't just for your own texts, ask someone to text you anything, and hopefully the result it yields will be the same.
I have only tested this solution on an unlocked Motorola Q9h from Fido, running the unlocked AT&T WM6.1 ROM on Rogers.
I serached for close to a month with no real viable solution, so I just kept poking and prodding at my registry. Yeah, kinda dangerous I know, but I was at my wits end with this little bug. Finally though, the time and investigation paid off
Hope it goes well for all of you out there who are having the same problem!