Post your smartphone screenshot.

[SaltwaterServr]

I wouldn't necessarily say that. I had no clue how to sbf my phone when I rooted my D1 and messed up quite a few times while following directions and it never hurt my phone.

Obviously, once you root, the warranty is violated.

I've got a live wallpaper running on mine, matrix style
No theme on mine right now because I just switched ROMs (From Simply Stunning to Bugless Beast) a few days ago and haven't got around to installing one.
http://i58.***BLOCKED***/albums/g273/air0208/CAP201012201004.jpg

I found a youtube shot of the live wallpaper. That's pretty dang cool. I tried finding it for my desktop, but no luck.

 

[kapolani]

Fixed. How did that work out?

Proprietary solutions always get marginalized in the market. iPhone will stay around as a boutique solution, but is about to get pummeled. Not as bad as Blackberry though...

We'll see.

People ***** and moan about Apple's 'walled garden.'

But, this way they can make sure carriers don't try add bloatware that can ruin the experience.

Sure, you can root your Droid to get rid of some of that crap, but out of the box your normal everyday person won't want to do that.

Some new devices running Android have builds that came out iterations ago. So, you get a new device that's loaded down with crapware with an old OS.

 

[kapolani]

The Samsung Captivate craps all over the Iphone.

The Craptivate!?!?

That's a good one.

 

[kapolani]

Another thing to think about.

Apple would sell much, much more iPhones if they ran the types of deals that other vendors do.

You ever see a 'buy one iPhone and get the second free?'

Never. And they still sell a boat load of phones.

Once it is sold through other carriers I see another iPhone explosion.

I think Apple has it right. They are tying all the IOS devices together i.e. Apple TV and iPad.

 

[kapolani]

Very good point in reference to the PC. My Polymers professor had his phone go off in the middle of class one day and apologized because he and his wife had just switched from iPhone's to Evo's. His biggest complaint was that the new iPhone couldn't get reception worth a crap inside the chemistry building.

That has nothing to do with the phone and all to do with the carrier.

 

[SaltwaterServr]

That has nothing to do with the phone and all to do with the carrier.

Nope. He said he had the older iPhone, then upgraded to the new one before going to the Evo. One of the grad students said he was glad he stayed with the 3G or whatever. Doc mentioned that he would have reactivated his old set if he hadn't donated them.

So I guess it was all AT&T's fault.

iPhones were the first of that breed, and are now losing out to better systems. Split out the market share of iOS's between the major competitors and focus on the iPhone (Apple really likes to lump the iPod Touch in with the iPad as well) and you'll see Apple's phone OS losing to Android.

This is actually the first time I've seen an complaint about bloatware that was imbedded to the extent you had to root it out. Got an example?

I've always said the only way I'd ever touch an iToy is when it went to Verizon. If there's a better system out there, and the indication is that the newest incarnation of the Android phones are, then I'll go with whomever is the best out there at the time.

I'll be perfectly candid, the last **** Apple pulled on their customers with the "phantom bars" and short circuiting antenna really put me off the approach to their customers. Had that been a RIM product, Apple customers would have laughed their rear ends off at the crappy customer service and flaunted it for quite some time. Of that I have little doubt.

 

[kapolani]

Nope. He said he had the older iPhone, then upgraded to the new one before going to the Evo. One of the grad students said he was glad he stayed with the 3G or whatever. Doc mentioned that he would have reactivated his old set if he hadn't donated them.

When the iPhone 4 first came out ATT had a massive failure. When they were trying to bring their HPSA+ capabilities online many areas all over the country had a horrible signal. When I first got mine it was irritating because 3G was almost non existent.

So I guess it was all AT&T's fault.

Yep. Just said that.

iPhones were the first of that breed, and are now losing out to better systems. Split out the market share of iOS's between the major competitors and focus on the iPhone (Apple really likes to lump the iPod Touch in with the iPad as well) and you'll see Apple's phone OS losing to Android.

Well, it's who you believe. Data has shown that it has leveled off. Plus, with the inclusion of the Chinese market and the Koreans it has exploded once again. Wait until Verizon or TMobile gets it.

Also, as more and more Android phones come out it further causes fragmentation. Have to code for different screen sizes. Have to code so things play nicely with the vendors added API's.

This is actually the first time I've seen an complaint about bloatware that was imbedded to the extent you had to root it out. Got an example?

Are you serious?

HTC sense, Motorola Blur etc. Hell, to get the Blockbuster app off of the new Droid you have to root it. How about VCast?

I'll be perfectly candid, the last **** Apple pulled on their customers with the "phantom bars" and short circuiting antenna really put me off the approach to their customers. Had that been a RIM product, Apple customers would have laughed their rear ends off at the crappy customer service and flaunted it for quite some time. Of that I have little doubt.

I'll give you that.

But, I haven't lost any bars. I don't have to the 'death grip' problem. I got the iPhone 4 the day it came out. So, I would really like to see how many people were really affected by it.

 

[BrAinPaiNt]

As noted I am getting the Iphone 4 soon. Maybe by christmas maybe a few days after.

I originally thought about the EVO but the wife is getting a good deal on the phone and since she is already on a family plan adding me to the service will be cheap where as I would probably have to get a different service plan all together with the evo.

I have watched a few videos on youtube where some tech sites did a comparison or competition of sorts between the iphone and evo. In some categories the Iphone did better and in others the evo did better but most of the time the evo would win by a slight margin overall due to the 4G service with the carrier and also the atenna issue with the iphone. However in the categories that best suited what I was interested in the Iphone won out except for screen size. However I am ok with a slight difference in size as long as it is clear and the iphone screen with the retina display is very clear.

 

[kapolani]

As noted I am getting the Iphone 4 soon. Maybe by christmas maybe a few days after.

I originally thought about the EVO but the wife is getting a good deal on the phone and since she is already on a family plan adding me to the service will be cheap where as I would probably have to get a different service plan all together with the evo.

I have watched a few videos on youtube where some tech sites did a comparison or competition of sorts between the iphone and evo. In some categories the Iphone did better and in others the evo did better but most of the time the evo would win by a slight margin overall due to the 4G service with the carrier and also the atenna issue with the iphone. However in the categories that best suited what I was interested in the Iphone won out except for screen size. However I am ok with a slight difference in size as long as it is clear and the iphone screen with the retina display is very clear.

Sweet. The Retina display is amazing.

I do wish, however, that the screen was just a tad bit bigger. It would have made it perfect in my opinion.

Although I come off as an Apple fanboy, make no mistake, if something better came out by another company (at least better for me) then I would jump ship. I just feel the iPhone has a better all around user experience. It also helps that there is massive support for it.

If you're a gadget guy and not afraid of tinkering you can Jailbreak your phone. It's painless to do.

Once you get it PM me if you want some tips.

 

[SaltwaterServr]

Vcast? Delete it and move on.

From the conversation I was privy to, the older iPhones didn't have the same issue in reception that the i4 did. Hence the professor asking the grad student if his phone had any signal issues because his i4 never had worked in the class whereas his older one had.

You're really playing the fragmentation thing up, and I find that kind of laughable considering I'm sitting behind a Windows OS. Coding for different screen sizes? Oh no, what ever will the tech engineers do? Lawd help 'em if they ever have to code for differing screen sizes and maybe even resolution too. You know, the same exact things that PC's have had to do for around 20 years now?

 

[kapolani]

Vcast? Delete it and move on.

From the conversation I was privy to, the older iPhones didn't have the same issue in reception that the i4 did. Hence the professor asking the grad student if his phone had any signal issues because his i4 never had worked in the class whereas his older one had.

Are you not reading what I'm typing?

The new iPhone 4 uses HPSA+. The older iPhones didn't. When I first got my phone and the problem arose I was getting degraded signal in places where my 3G didn't.

You're really playing the fragmentation thing up, and I find that kind of laughable considering I'm sitting behind a Windows OS. Coding for different screen sizes? Oh no, what ever will the tech engineers do? Lawd help 'em if they ever have to code for differing screen sizes and maybe even resolution too. You know, the same exact things that PC's have had to do for around 20 years now?

It's laugable because you have no idea what you're talking about. Apples to Oranges.

Coding for a box running Windows95 is a different experience than coding for a box running the latest and greatest.

For example function calls become deprecated. What one had to code for then is not the same now.

How do you target many different devices running different builds of an OS? What version build one Droid phone may be running could be a few iterations back. What has changed between iterations? This is what programmers have to deal with. I deal with it on a daily basis. Some of our customers are running several versions back. So, when I make a change to a XML DTD for instance I have to make sure I handle each specific change - especially if a value is required.

Coding for an app to play nicely with HTC Sense could be an entirely different method than coding for Motorola Blur.

 

[kapolani]

Furthermore...

Why do you think that Google can't just press a button and update EVERY Android device to the latest and greatest build?

 

[SaltwaterServr]

Are you not reading what I'm typing?

The new iPhone 4 uses HPSA+. The older iPhones didn't. When I first got my phone and the problem arose I was getting degraded signal in places where my 3G didn't.

That was confusing because you didn't specify 3G service in the post above so it looked like you were referencing the iPhone 3G. Probably my reading error. Odd though that they'd roll out a new product line like that. I understood that every single new i4 had the short circuiting problem.

It's laugable because you have no idea what you're talking about. Apples to Oranges.

Coding for a box running Windows95 is a different experience than coding for a box running the latest and greatest.

For example function calls become deprecated. What one had to code for then is not the same now.

How do you target many different devices running different builds of an OS? What version build one Droid phone may be running could be a few iterations back. What has changed between iterations? This is what programmers have to deal with. I deal with it on a daily basis. Some of our customers are running several versions back. So, when I make a change to a XML DTD for instance I have to make sure I handle each specific change - especially if a value is required.

Coding for an app to play nicely with HTC Sense could be an entirely different method than coding for Motorola Blur.

So it's a problem that the app providers need to worry about here, sort of like a manufacturer creating drivers for any number of peripherals to play with any number of operating systems it might get plugged into?

If I'm clear on things, Apple can't push a button and upgrade EVERY iPhone to the latest and greatest build either. That choice still resides with the end user, or am I to understand your product is at the whim of Apple's updating discretion?

 

[kapolani]

That was confusing because you didn't specify 3G service in the post above so it looked like you were referencing the iPhone 3G.

My fault. Thought we were on the same page.

So it's a problem that the app providers need to worry about here, sort of like a manufacturer creating drivers for any number of peripherals to play with any number of operating systems it might get plugged into?

You're getting closer. But, the example you provided is similar.

The difference here is: with regards to a WinOS box it's a closed environment. The developers know the platform. They know the changes etc. They can write code that's backwards compatible.

But, the problem with the Android platform is when the vendors start adding their stuff to it. They have to make sure it plays nicely with all the different devices out there running the vendors additions. That's why some Droid apps look horrible on some phones while looking/working great on other phones.

So, the developer has the difficult task of figuring out what devices to support.

If I'm clear on things, Apple can't push a button and upgrade EVERY iPhone to the latest and greatest build either. That choice still resides with the end user, or am I to understand your product is at the whim of Apple's updating discretion?

Correct. The user can upgrade only when a new build comes out.

The difference is: when Apple comes out with an update the end user can upgrade immediately. The user doesn't have to wait for their vendor to massage the code so that it works nicely with their environment. The builds are released to the developers early so that they can modify their code to work with the latest build.

That's why you see new Android devices coming out with old builds. The enduser is at the mercy of the vendor.

 

[YosemiteSam]

How do you target many different devices running different builds of an OS? What version build one Droid phone may be running could be a few iterations back. What has changed between iterations? This is what programmers have to deal with. I deal with it on a daily basis. Some of our customers are running several versions back. So, when I make a change to a XML DTD for instance I have to make sure I handle each specific change - especially if a value is required.

Coding for an app to play nicely with HTC Sense could be an entirely different method than coding for Motorola Blur.

Coding for the different builds of Android isn't as big of a deal as many people make it out to be. Most Android devices upgrade to the newer versions of Android anyhow. The fact that phones have about a two year life makes the issues even less of one since most phones today are Android 2.1 or 2.2. It's just like there are iPhones G3s and G4s.

Now coding for the different devices can be a different story. You have some phones that have x & y, while others can have x, y & z. It can still be done, but it truly isn't the extremely problem most people make it out to be. (hell, many apps don't even used the specific hardware like front facing cameras) Right now the two biggest issues from developers who have worked on both platforms isn't this "fragmentation", it's been the fact that Android's documentation isn't quite what iOS is and B, Google is limiting app size to something like 50MB. I'm sure at some point that will change. Not that getting it from a different location than Google's app store gets around that problem anyhow.

 

[Vtwin]

The Craptivate!?!?

That's a good one.

You should have been on the boat with my nephew and his Iphone and me and my Captivate Sunday. I've got a Froyo rom running and am rooted with all bloatware removed.

He is asking for a Captivate for Christmas now. LOL

I suppose if you need to be able to just charge the phone and go the Iphone may be for you but it you are willing to spend a half hour doing some very easy tweaks the Iphone just can't keep up. My friend had a Droid X that I would buy before I got an Iphone.

Any personal experience with the Captivate or are you just running your mouth cause you're an Apple fanboy?

 

[kapolani]

You should have been on the boat with my nephew and his Iphone and me and my Captivate Sunday. I've got a Froyo rom running and am rooted with all bloatware removed.

Is your nephew Jailbroken?

What iPhone does he have?

I suppose if you need to be able to just charge the phone and go the Iphone may be for you but it you are willing to spend a half hour doing some very easy tweaks the Iphone just can't keep up. My friend had a Droid X that I would buy before I got an Iphone.

I 'tweaked' my phone in 5 minutes. I'm Jailbroken on IOS 4.1. Haven't upgraded to 4.2 yet.

Any personal experience with the Captivate or are you just running your mouth cause you're an Apple fanboy?

I'm running my mouth because I played with the Captivate and it's nothing special. I can do everything you can do on your phone AND have greater support and breadth of apps.

 

[kapolani]

Coding for the different builds of Android isn't as big of a deal as many people make it out to be. Most Android devices upgrade to the newer versions of Android anyhow. The fact that phones have about a two year life makes the issues even less of one since most phones today are Android 2.1 or 2.2. It's just like there are iPhones G3s and G4s.

Really? Is this through experience? So, you code apps for the Android platform?

2 years is a lifetime for a moble device.

Now coding for the different devices can be a different story. You have some phones that have x & y, while others can have x, y & z. It can still be done, but it truly isn't the extremely problem most people make it out to be.

It's not a problem until you have to code for it.

Is this through experience?

 

[YosemiteSam]

I really don't write in Java much, though I've thought about making a CZ app to simplify accessing CZ on my phone. Reality doesn't want to capitulate with my request for some type of thread feed, so I never started working on it. Though I'm fairly sure it will be a write once, run on any device app since it's make-up is a pretty basic network and render app. Though I suspect you know this already, but prefer to argue the Apple / Android point. Besides, over 83% of the Android market is Android 2.1 or 2.2. The biggest difference in Android versions exist between 1.x and 2.x. As we discussed the 2 year lifespan of the devices. Most Android devices that have 1.x are reaching that lifespan now.

Now, while have not written an app for Android, I know quite a few people who do. They all have the same complaint and most of the time it isn't fragmentation. (unless they are trying to write a graphics intensive game and actually want it to run on Android 1.5/6.) When they do, I ask why they want to do that since it's a small and dying percentage of the Android market. Chances are, that small percentage of Android 1.x users will be Android 2.x users within the next three months. Basically, it's like writing an app today for the iPhone 4 and back porting it to iPhone 3 when iPhone 5 comes out next month. There is no point in doing so for such a small and dying market.

The only people I know that persist with the fragmentation argument are Apple fanboys. Most of them are techies, but don't even write software in any language. (the non-techie Apple guys don't even know what fragmentation means when it comes to these devices) Most of the software I've written was in C/C++ back in the day, but now it's mostly Python for infrastructure management or my own personal projects.

 

[kapolani]

Though I'm fairly sure it will be a write once, run on any device app since it's make-up is a pretty basic network and render app. Though I suspect you know this already, but prefer to argue the Apple / Android point.

It's a trivial thing to do if you're writing a simple app. No bells and whistles doesn't require you to work too hard.

Now, while have not written an app for Android, I know quite a few people who do. They all have the same complaint and most of the time it isn't fragmentation. (unless they are trying to write a graphics intensive game and actually want it to run on Android 1.5/6.) When they do, I ask why they want to do that since it's a small and dying percentage of the Android market. Chances are, that small percentage of Android 1.x users will be Android 2.x users within the next three months. Basically, it's like writing an app today for the iPhone 4 and back porting it to iPhone 3 when iPhone 5 comes out next month. There is no point in doing so for such a small and dying market.

I guess you don't understand what I'm saying.

Coding for the Android platform isn't difficult at all. Heck, any platform shouldn't be difficult to a programmer who is decent. That's not the problem.

Having to code for different vendors because they added another layer to the onion is the problem. Actually, I shouldn't downplay the difficulty that could arise for coding from build to build, but it shouldn't be too difficult.

The only people I know that persist with the fragmentation argument are Apple fanboys. Most of them are techies, but don't even write software in any language.

Like I stated earlier, I deal with 'fragmentation' on a daily basis. One application that I work on requires the ability to import data from xml files. If any changes are made to the DTD file from build to build you HAVE to account for it when parsing in the data. Of course it's dependent upon whether or not the element can be null (a perfect example of 'fragmentation').

Most of the software I've written was in C/C++ back in the day, but now it's mostly Python for infrastructure management or my own personal projects.

Most of my experience is writing embedded software in a Unix/Linux environment. I've worked with 1553 stuff writing bus controllers and monitors for subsystems that run on platforms on many of our military aircraft. Currently writing stuff in Java and C/C++. Any programmer worth his salt can look at a new language and begin programming immediately. Coding isn't hard. Anyone can do it. Writing efficient code is what separates the good from decent.