Windows Phone Thoughts: Frustrations Of Setting Up A Device

Be sure to register in our forums! Share your opinions, help others, and enter our contests.


Digital Home Thoughts

Loading feed...

Laptop Thoughts

Loading feed...

Android Thoughts

Loading feed...



Friday, March 26, 2004

Frustrations Of Setting Up A Device

Posted by Ed Hansberry in "THOUGHT" @ 03:00 PM

I installed an update to an app this week that made a change to the UI that I really didn't like. In trying to revert to the old version I caught the bug that some of you have - failing alarms. :? Two days in a row they have failed. Now it is time for a hard reset. I figure now is as good of time as any to upgrade to the new iPAQ 2215 ROM 1.10, so off we go.

The upgrade ran smooth. Now for the hours and hours of putting apps back on through this weekend. There were several things I wanted done today though and one was to get my bluetooth partnership with my Nokia 3650 going. I am sure you can see where this is headed. I start the process on my 2215 and the Nokia keeps seeing "Pocket_PC" which is wrong. I've already named my device Hans2215. Buried deep within not the iPAQ Bluetooth Manager but the Bluetooth icon in the Connection tab I finally found out why. For some stupid reason it says "Pocket_PC" for the device name. Fine. Change that, ok, ok, ok, hit New Connection in the Bluetooth Manager again. Same thing. Reboot the iPAQ and Nokia. Same thing. Screw it. Connect as "Pocket_PC" then rename it on the Nokia side, because, yeah, I'm anal about that sort of thing. :grumble:



But do they connect? Noooo.... Now I try to establish a partnership from the Nokia to the iPAQ and that works. I have no clue why I have to do it both ways. Fine. Enter the impossibly long connection string to get T-Mobile working, connect, nothing. Sigh... The iPAQ and Nokia are talking, but the dialup isn't happening. For some reason I have to open the Bluetooth Manager and tap-hold on the phone icon, click connect then tell it to use my "TMobile" connection because for some reason, me telling the TMobile connectoid to use the Bluetooth Dialup Modem involved too much common sense. I am beginning to understand that bluetooth is like a black hole. It lives in the same Einsteinian universe I live in, but like black holes, it doesn't obey the same laws. So, as you get closer to the bluetooth event horizon, logic is crushed in on itself and a whole new set of rules kicks in. I am not well versed in quantum physics, or bluetooth apparently. :roll: After this step, the connection finally works. :werenotworthy:

Now to launch inbox and connect to my corporate email server. I know this works because I have already set up the VPN server with my Socket WiFi CF card. It blows sky high. Fine. Start|Settings|Connections. Where did all of my network connections go?!?!?! "My ISP" and "My Work Network" are gone and in their place is a single "Bluetooth Settings" configuration. Now, keep in mind I was in a foul mood before this because:

• Audible has changed their Pocket PC software in an apparent answer to my post here and my trick no longer works.
• Microsoft has changed the default black text in the Start Menu to White somewhere in the Theme logic and all of my favorite themes are rendered useless.

Dig around and find out that the HP Bluetooth Manager has added this new "network" for bluetooth settings and moved all of my ISP and VPN settings into it. Not copied. Moved! Fine. But HP, like the rest of us, doesn't fully grasp the finer nuances of Connection Manager because if they did, they WOULDN'T HAVE MOVED MY VPN SETTING FROM "MY WORK NETWORK" TO THEIR BOGUS "BLUETOOTH NETWORK INTERNET" SETTING! You can't do that. That is like setting everything to WORK WORK WORK in the Connection Manager then wondering why your VPN never fires. Trust me. It won't.

So I change everything back to the way it belongs with My ISP and My Work Network, make a new connection string, which I have to call TMobile2 because TMobile is used in the Bluetooth area :roll: and my VPN is called VPN2 for the same stupid reason. And yes, I did go and delete the ones in the Bluetooth network and rename mine because, yeah, I'm anal about that sort of thing.

Oh, one more thing. For the first time since moving to Windows Mobile 2003, I got the "Not enough memory" error when starting up the bluetooth stack. I am not impressed with ROM 1.10 at all. And I am not upgrading anything for quite some time. I am sick of loading apps and playing "Find the UI control we moved" and it has happened several times in the past 2 weeks with both Pocket PC and PC apps I got an urge to update.

One good thing did happen today though. My new CDs by Sugerplum Fairies arrived. Bliss...

Tags:

Reviews & Articles

Loading feed...

News

Loading feed...

Reviews & Articles

Loading feed...

News

Loading feed...

Reviews & Articles

Loading feed...

News

Loading feed...

Reviews & Articles

Loading feed...

News

Loading feed...

Reviews & Articles

Loading feed...

News

Loading feed...