Skip to main content

This Phone Will Self-Destruct . . .

Yesterday, I activated a Samsung Windows Mobile Phone. It has been years since I last touched a WinMo phone. The last time was my old T-Mobile Dash, which I shoehorned WinMo6 into towards the end of its run. It was a good phone. So, I was doing an activation for a friend on her new phone. I find myself perplexed that Microsoft would design such a finicky product, and that Samsung would agree to manufacture it.

The interface is really nice, don't get me wrong. There is a lot of ooh and aah designed into the OS. However, activating the phone requires that you install a memory card... no, hold that. The phone requires you to install a Certified Windows 7 Compatible memory card.

You could try a non-certified card; but, the system will rip it to shreds and make it unusable, even unformattable. I can see maybe if you want the phone to use a Class 10 card, you would discourage the use of a Class 4 memory card. However, this is the opposite. The cards that are known to work are Class 2, 4, and 6.

Not knowing this, I popped in a spare card to get my friend up and running. She messaged me today that the card (and phone for that matter) crapped out today.

I can't, for the life of me, figure out what the thinking was in creating this monster that eats memory cards. The operating system becomes one with the memory card of your choice. If you take out the card to upgrade to a better one (assuming you got it to work), you can't do it without reinstalling the entire system.

For somebody like me who is used to messing around with tech, this is a little speed bump. But, to the average consumer, this can be a major sore spot. Especially if it craps out after one day of use.

If we can get it running reliably, the phone could be great. But, between now and then, it's a disappointment.

Comments

Popular posts from this blog

Before Getting Out of the Gate

Tonight, I was working on a new blog project. Google and Blogger have been good platforms for me in the past. I was able to get the domain pointed and was working on the layout and template. Suddenly, the website was blocked. I had searched for ways to publish that were not subject to censorhsip. I wound up on the Hive blockchain. It's great for censorship resistance, but it's not without its problems. In any case, I was thinking that maybe I was being too paranoid. Now, before getting out of the gate, I have a blog censored. I'm trying to think of what I could have posted, reposted, or even been associated with that could have caused the blog to be blocked. I can't think of anything. If this doesn't pan out after review, I may need to look for an alternative hosting option. I was already looking at Publii as an option. It only requieres simple FTP updates. I prefer not to use Wordpress as experience has taught me that you an customize a theme and add plugins ...

Blogger blocks excessive posting

A while ago, I tried uploading a blog post via Android App. The upload kept failing. Not to be deterred, I deleted the app and reinstalled, to find no better success. I thought that perhaps I could email the post to Blogger. That did not work either. The email bounced back with the following: Technical details of permanent failure: You have exceeded the the allowable number of posts without solving a captcha. This happened because I imported quite a few blog posts from another blog I discontinued just yesterday. It has been less than 24 hours since the import. It makes sense. I'm rather certain the captcha speedbump is also why the mobile app refused to publish my posts. The problem can be circumvented if you post directly on the Blogger site and solve the captcha. This problem will likely resolve in the next few hours and all will be right with the universe once more.