Welcome to the Geek Choice Blog

So many friends and I are always going back and forth about what phone is better the iPhone or the Android. The debate usually starts up when one of our phones has a major glitch or issue. Well today I get to put another small on the iPhone. Did anyone who had an iPhone have to get up for work on Sunday and happen to use the iPhone as your alarm clock? Well if you did you might have been extremely late to work. You may ask why if you don’t answer yes to that question. Well a glitch in the iPhone caused many of the phones to spring back instead of spring ahead. So if you were looking to get up for let’s say 8AM you got up at 10AM. Oh the wonders of the iPhone! I personally have a Droid X and I woke up and checked my phone and then checked my PC and cable box and wouldn’t you know it, all of the times were correct. Now this was said to happen in US iPhones and isn’t the first time this issues has come up. Also it didn’t matter which carrier you used for the iPhone both AT&T and Verizon had this issue, so if it is not the carrier then it is the phone. This being a known glitch it has happened before outside of the US. In England this happened back in November 2010 the alarms failed to switch from British Summer Time to Greenwich Mean Time and this also happened in Australia during their daylights savings time. So the question begs to be asked, will Apple fix this glitch before the next daylight savings time??? A+ Apple…. A+!

As I keep hearing more and more commercials for the new Windows phones. That have a pretty screen, a new lovely interface that includes such things as Xbox Live support and being able to stream Netflix which in my opinion is nice, Windows still has its issue.

None more disturbing than an update error that has been problematic for Samsung users who want to get the phone’s March update. This is the first Windows Phone 7 update and I am really not shocked that this update is not going through properly. Windows in my opinions has never been very good at implementing updates for the most part especially if they are critical. Such as the XP and Vista service pack update debacles.

Right now there is no fix for this error and it shows up as the code “error code 800705B4.” Sometimes you can reboot, remove apps, free up space on the mobile device may help alleviate this error but apparently not for everyone. Microsoft is telling people now to hold off on downloading the update. So if you are one of the lucky few who read my blog and have a Windows Phone and haven’t updated it yet, well you’re safe and with any new Windows product that has an update I usually hold off for a few until I have heard the update doesn’t crash your system. A hard lesson learned back in the XP service pack update days.

We have all seen them when a page fails to load on the internet, and people often do no understand why they happen.

The error messages are the end result of a problem that happens all the time in the internet. Whether you are visiting a site that you are not allowed to visit, or you are just trying to check email, these messages tell you that access is denied. The problem is that the messages do not really tell you anything, about how to solve the problem or direction towards making sure this does not happen again.

HTML runs on these codes,  they determined whether this page loaded correctly or something is off. There are actually codes being sent in your computer right now.

From the numbers 100 to 300, each beginning digit corresponds to a specific function. If it is a 201 or 202 then the code is received as a success. If it is a 401, or a 404 which seems to be the most common type of error message, something is wrong.

• 400 (Bad Request). The server did not understand the request. This is usually cured by resending the request.
• 401 (Unauthorized). The request requires some form of authentication (e.g., userid and/or password) but did not contain it. Usually, this code results in a box popping up in your browser asking you for the required information. Once you supply it the request is sent again.
• 402 (Payment Required). Reserved for future use. [Who says the web is not moving toward being a commercial medium!]
• 403 (Forbidden). This is a sort of catch-all refusal. If the server understood the request but, for whatever reason, refuses to fill it, a code 403 will often be returned. The server may or may not explain why it is sending a 403 response and there is not much you can do about it.
• 404 (Not Found). If you happen to mistype a URL or enter an old one that no longer exists this is the error you will likely see. The condition may be temporary or permanent but this information is rarely provided. Sometimes code 403 is sent in place of 404.
• 405 (Method Not Allowed). Your browser has requested a resource using a procedure not allowed to obtain that resource. The response should contain allowed procedures.
• 415 (Unsupported Media Type). If your browser makes a request using the wrong format, this code may result.

When you see these error messages, there is always a solution to the problem. If you feel that you have run out of ideas, and have no where to turn for help, look for the Geek Choice guys. They will assist you in completing the task and getting you up and running again.