• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

May be leaving Android

Nope, but after having phones like the Hero, Evo 4G/3D, Sensation, Nexus S 4G and now the Galaxy S2, I can easily say the battery in the iPhone easily beats them all. I couldn't care less what size the battery is as long as I am not running to a charger or having to swap a fresh battery in every 8-10 hours like I had to with my Android phones.

I work side-by-side with an iP4s owner whose battery lasts a fraction of my 3vo - go figure. Too bad you didn't get the advice needed about not running task killers, but even if you had, phone use varies for everyone.

And it's pretty clear that you have multiple issues with Android beyond the battery - and no need for them to be re-hashed here. But no worries, there's no perfect phone, just the right phone for the individual at any given point in time.

Enjoy your new iDevices, hope they're everything you want and more. :)

Hope you find the right Apple forum to go with your iDevices, there are many good ones out there, but like ardchoille, you'll always be welcome here with positive insights.
 
  • Like
Reactions: B2L
Nope, but after having phones like the Hero, Evo 4G/3D, Sensation, Nexus S 4G and now the Galaxy S2, I can easily say the battery in the iPhone easily beats them all. I couldn't care less what size the battery is as long as I am not running to a charger or having to swap a fresh battery in every 8-10 hours like I had to with my Android phones.

We have to remember that the programming language used on the iPhone (C/C++) is faster and more efficient than that which is used in Android (Java). So, it only follows that the battery life will be better. Still not sure why Google chose Java. Maybe due to libs/dependencies?
 
...Finally, I may be leaving Android, but I'm not leaving my friends.. and my friends are here :) I'll be hanging around here for a while.

That's good to hear, and I'm glad we wont be losing you (entirely). :) I also think it speaks well to the kind of community we've all built here at AF. Kudos to you, the great staff here and all the members who make AF the place that it is.
 
I work side-by-side with an iP4s owner whose battery lasts a fraction of my 3vo - go figure. Too bad you didn't get the advice needed about not running task killers, but even if you had, phone use varies for everyone.

And it's pretty clear that you have multiple issues with Android beyond the battery - and no need for them to be re-hashed here. But no worries, there's no perfect phone, just the right phone for the individual at any given point in time.

Enjoy your new iDevices, hope they're everything you want and more. :)

Hope you find the right Apple forum to go with your iDevices, there are many good ones out there, but like ardchoille, you'll always be welcome here with positive insights.

I never used a task killer on any of my Android phones. When I say kill the app, I mean using the built in one on the S2, closing them out. If I would not do that and things like camera, gallery, quick view and all the other things I had opened during the day were all in there, it would really reduce battery life.
 
We have to remember that the programming language used on the iPhone (C/C++) is faster and more efficient than that which is used in Android (Java). So, it only follows that the battery life will be better. Still not sure why Google chose Java.

Actually, native programming is used in addition to Java for some apps.

Android apps are much more compact that iOS apps because of the difference in architectures between the two systems. iOS apps drag around their own baggage, with the advantage that when the app is running, it can hog processor resources a bit more, unlike Android. That's a large part of the perceived fluidity of iOS when running on slower processors.

Compact Android apps call on that equivalent baggage as built in Linux services, and all of those were written in C/C++, leading to less of a language difference than you're thinking.

Battery use for either platform is influenced by how you use it. I do not use social apps on my phone, battery goes on and on. My iPhone friends that launch up resource intensive apps and social stuff get poor battery life.

Every day, someone switches camps because they can show the new camp, Android or iPhone, has better battery life - neither is wrong. It comes down to matching the platform with your use for best results.

The only fact we know for certain is that all mobile devices need battery improvements.

I never used a task killer on any of my Android phones. When I say kill the app, I mean using the built in one on the S2, closing them out. If I would not do that and things like camera, gallery, quick view and all the other things I had opened during the day were all in there, it would really reduce battery life.

Apologies, I must have misread your post in another thread, as others did.

In any case, I've not owned that phone, we've both owned Evo 3D phones, so it's a simple case of your mileage may vary. :)
 
A lot of mobile device users tend to skip over one minor little detail in comparing Android to iOS. Apple makes software for one piece of equipment-"Apple". Android has to accommodate varying hardware platforms and OEMs. I love the diversity of Android. :-)
 
A lot of mobile device users tend to skip over one minor little detail in comparing Android to iOS. Apple makes software for one piece of equipment-"Apple". Android has to accommodate varying hardware platforms and OEMs. I love the diversity of Android. :-)

What you see as diversity and a good thing, many others see as a headache. All of those different hardware platforms and OEM's are the exact reason it takes 6 months or longer for your carrier to update your phone to the next OS. Meanwhile, Google has already built 2 more of them with great new features and optimizations you won't see for a year...Its also the reason many users can't download certain apps and get frustrated because other Android phones can. Its a mess to be quite honest.
 
Again - Google does make phones save for specifying the Nexus, which is built by others.

And those come out once per year.

As has been mentioned repeatedly to you by many others.

And app updates and OS updates just are what they are - usually incremental, and major changes about once a year, coinciding with the Nexii.

Let's go back to giving hearty thanks to those of you moving on to iDevices for your positive contributions here and not hijack this thread with a re-hash of the Neverending Android vs. Apple Story.
 
After a few months of Android, I'm about ready to try an iPhone -- or return to Blackberry.
My biggest gripe with Android is how intrusive, bloated and inefficient it is.
I want a lean device that lets me read & reply to email, make the occasional phone call, and browse the 'net a bit.
The Android OS seems hell-bent on either selling me stuff or loading (and keeping loaded) stuff that I never (or rarely) use.
For example, Task Killer tells me that I currently have loaded Weather, My Account, Play Store, Appstore, Maps, Music & Dragon Dictation.
WHY!?!
If I need to know the weather, there's wunderground. I don't look up my bill with my handheld. Purchased apps shouldn't need to validate via a separate high overhead third-party app (e.g.Tapatalk). I usually use my mp3 player for tunes, but do play music OCCASIONALLY. And if I need to talk to my computer or need a map, then let ME invoke that functionality. Too often, simple operations are sluggish because there's only ~50k of free RAM. AND I'M NOT USING ANYTHING. There are simply too many undesired, unneeded apps loaded.
But I don't want to delete them, because I occasionally want them. But only occasionaly.
(And yes, I DID root and removed what I believe I safely could.)
Thoughts?
<stepping off of soapbox, breathing heavily & sweating profusely>
 
What you see as diversity and a good thing, many others see as a headache. All of those different hardware platforms and OEM's are the exact reason it takes 6 months or longer for your carrier to update your phone to the next OS. Meanwhile, Google has already built 2 more of them with great new features and optimizations you won't see for a year...Its also the reason many users can't download certain apps and get frustrated because other Android phones can. Its a mess to be quite honest.

This is one of the reasons I stopped developing for Android. I'd write an app that worked on my phone. A friend wanted a copy but it wouldn't work on her phone so I had to go and make changes in the code. I finally got tired and quit.

Here's what I'd like to see:
* Google tells carriers, no more pre installed apps, you will use Android as is
* Google redesigns Android so that every aspect is themeable - from buttons to notification bars - via .png files without needing root
* Google bans manufacturer skins
* Updates come directly from Google
* Google sets strict standards for hardware

I feel that would alleviate a lot of the fragmentation and frustration. It would also take a ton of work off the manufacturers.
 
After a few months of Android, I'm about ready to try an iPhone -- or return to Blackberry.
My biggest gripe with Android is how intrusive, bloated and inefficient it is.
I want a lean device that lets me read & reply to email, make the occasional phone call, and browse the 'net a bit.
The Android OS seems hell-bent on either selling me stuff or loading (and keeping loaded) stuff that I never (or rarely) use.
For example, Task Killer tells me that I currently have loaded Weather, My Account, Play Store, Appstore, Maps, Music & Dragon Dictation.
WHY!?!
If I need to know the weather, there's wunderground. I don't look up my bill with my handheld. Purchased apps shouldn't need to validate via a separate high overhead third-party app (e.g.Tapatalk). I usually use my mp3 player for tunes, but do play music OCCASIONALLY. And if I need to talk to my computer or need a map, then let ME invoke that functionality. Too often, simple operations are sluggish because there's only ~50k of free RAM. AND I'M NOT USING ANYTHING. There are simply too many undesired, unneeded apps loaded.
But I don't want to delete them, because I occasionally want them. But only occasionaly.
(And yes, I DID root and removed what I believe I safely could.)
Thoughts?
<stepping off of soapbox, breathing heavily & sweating profusely>

Some of us like the always-on mini-laptop in a pocket that is today's superphone - while just as many, like you, completely hate that.

What phone are you using? I'd be glad to check and see if there might an alternative rom that's more to your liking - many exist that are really pared down.

My son's tastes are exactly like yours, for example. He put Bloodawn's CTMod rom on his Samsung Prevail and it totally rocks. It's so minimal it's almost glacial in its beauty. And yet, does 100% of what he needs when he wants to, never otherwise.

Themed with an absolutely minimal single homescreen in use, zero clutter, and a clean notifications bar.

I have to admit, every time I look at his phone, I wonder if I'm not doing it all completely wrong! :) :p

OBTW - one thing about Android - it does automatic app management. Many of the things you see as "loaded" aren't running at all. A simple construct, think of it as a bookmark for an app, is left in memory allowing a quick re-start of things recently used.

There's likely to be things running that you don't need so much - but perhaps fewer than the Applications Manager is suggesting to you.

~~~~~~~~~~~

PS to ardchoille - I think we need to remember what sparked the Nexus before tossing Google under the "they don't set standards" bus.

Roll back a few years ago, handsets were all over the map, updates weren't happening, makers were blaming Google that it was too hard to build good handsets.

So, Google contracts with HTC to make a developer phone - the Nexus - to show that it can be done, and basically how.

Next, we saw all of the makers step up their game.

After, Google backed down from the Nexus being a one-time-only thing and has repeated it.

And Google - like Microsoft - does set minimum standards, the ones don't meet it don't get things like the Play Store, for example.

And just like with Windows, Google can no more enforce platform standards than Microsoft can with laptop vendors. And not all Windows programs properly on all Windows PCs.

That's a fact of hardware diversity.

The place where the Microsoft analogy ends is that when OS updates do come for Android - they're free.

I feel that would alleviate a lot of the fragmentation and frustration. It would also take a ton of work off the manufacturers.

And you'd have handset makers and carriers rushing back to their own private operating systems in droves.

You just gave the formula to turn Android into iOS, my friend.

The solution to that problem is simple, you've taken it - switch to iOS if you want that (along with day 1 updates).

No offense, but it is what it is. :)
 
PS to ardchoille - I think we need to remember what sparked the Nexus before tossing Google under the "they don't set standards" bus.

Roll back a few years ago, handsets were all over the map, updates weren't happening, makers were blaming Google that it was too hard to build good handsets.

So, Google contracts with HTC to make a developer phone - the Nexus - to show that it can be done, and basically how.

Next, we saw all of the makers step up their game.

After, Google backed down from the Nexus being a one-time-only thing and has repeated it.

And Google - like Microsoft - does set minimum standards, the ones don't meet it don't get things like the Play Store, for example.

And just like with Windows, Google can no more enforce platform standards than Microsoft can with laptop vendors. And not all Windows programs properly on all Windows PCs.

That's a fact of hardware diversity.

The place where the Microsoft analogy ends is that when OS updates do come for Android - they're free.



And you'd have handset makers and carriers rushing back to their own private operating systems in droves.

You just gave the formula to turn Android into iOS, my friend.

The solution to that problem is simple, you've taken it - switch to iOS if you want that (along with day 1 updates).

No offense, but it is what it is. :)

Good points. I had a developer phone and that's what I used when I got into Android development. That's fine if you want to develop for that particular phone, but some of the apps I developed didn't work on other Android devices. I feel Google needs to tell manufacturers &#8221;you will comply with our hardware standards or you won't use Android at all&#8221;, but that would require Google to expend resources policing things and possibly drive up the cost, and price, of Android. All of this may seem cut and dry to you and I, but when the unsuspecting consumer can't install an app on his new tablet that his buddy has installed on his gnex, it gives all of Android a bad name - word of mouth and all.
I don't know, something needs to change.. I'm not the only Android developer who has given up.
 
Having Google build, test and distribute OS updates to all devices that they don't make will drive their costs through the roof.

And then limit handset choices. And then make this a more exclusionary market offering.

See where I'm going with this? :)
 
Having Google build, test and distribute OS updates to all devices that they don't make will drive their costs through the roof.

And then limit handset choices. And then make this a more exclusionary market offering.

See where I'm going with this? :)

Yep. I'll just switch to something that works for me, one person isn't going to change the world. HTC recently stated that they're going to overhaul Sense because they've seen how bad it has become, maybe Google will do the same for Android (fingers crossed).
 
If something is already good why is it necessary to totally replace it with something new which is worse? I think Google should switch to a new way of design and forget this ice cream sandwich like ui..
 
HTC Sense 4.0 will be toned-down and mature:
HTC Sense 4.0 will be toned-down and mature, with heavy Dropbox integration | MobileSyrup.com

True wisdom lies in knowing we know nothing ;)

True, true. :)

I was hoping that you'd find the quote from HTC that I couldn't. That article doesn&#8217;t contain any HTC direct quotes.

I predicted that they would have to slim down Sense months ago because the data-use centric approach in ICS duplicates much of that found in Sense. High time Android took that approach.

I believe, if either of us can find the quote, that HTC said that their Sense slimming was a vindication of the data centric approach.

One thing that they did backtrack on was their locked theme approach in Sense.

Google has levied a Holo theme requirement for all ICS phones that access the Market, to set look and feel requirements.

Holo Everywhere | Android Developers Blog

So, we actually have Google to thank for that improvement, stemming from an increase in standards enforcement.

HTC did say that they screwed up with having too many model variations and that had to stop.

All of this came in the flurry of statements surrounding the HTC One, and many blogs managed to cross-wire some of what they said.

So the rotf wasn't personal, you know me. ;) :)

I do think that the makers would do well to pay attention to our feedback. We're on the same side in that.

We only differ in which entities to hold responsible.

Android makers save a bundle not having to do heavy lifting on a whole operating system. They can afford to step up a little closer to the plate.

So. Phone. Have you decided to go iPhone and if so, which model?
 
If something is already good why is it necessary to totally replace it with something new which is worse? I think Google should switch to a new way of design and forget this ice cream sandwich like ui..

If I'm not mistaken, up until now only Sense and the newer TouchWiz have had hardware acceleration.

Google started to set the UI update expectations right after the Froyo release nearly two years ago. They promised it for Gingerbread. Of course, back then, Google publicly predicted that Gingerbread would be their last significant update. Since then tablets and multi-core processors have occurred.

So, the new ICS UI finally gives hardware acceleration across the board, standardization between tablets and phones, and constrains what makers can do regarding themes and app look and feel (see link in my previous post).

So, it actually _may_ address some of the issues that ardchoille elaborated, for example.

Plus, it's Android. You can skip the update if you like, or customize the parts you won't like. :)
 
As similar as the fragmentation issues are in Androids and Windows, there seems to more clarity on the Windows side. Developers are obligated to have their releases work in a stated Windows OS revision. Seems like Android app _and_ OS developers are not kept in line that way, that&#8217;s it&#8217;s almost anarchy... just idle observation.
 

Fabulous! :)

That's the one I was looking for! Thank you :D

Me, too! I stand proudly corrected, you were right! :) :)

As similar as the fragmentation issues are in Androids and Windows, there seems to more clarity on the Windows side. Developers are obligated to have their releases work in a stated Windows OS revision. Seems like Android app _and_ OS developers are not kept in line that way, that&#8217;s it&#8217;s almost anarchy... just idle observation.

I think you're on to something.

If we go to the store, we see minimum Android version required and permissions.

We don't see storage required, ram required, cpu or gpu expectations or known devices that the app has been tested on, except for the most conscientious developer statements.

Some of it, I can blame the programming experience of the devs. Some of it, I can blame Google for being too loose.

But most of it, I blame on undefined or unclear development processes.


Look at complexities involved here, and don't take the story at face value, follow the links on both sides of the debate -

Developers Are Shooting Down the Myth that "Android Can Never Be as Smooth as iOS"

If you listen to talking heads (like me) Google clarifies it all in their SDK (software development kit) instructions. But to know where we are, good idea to look where we started -

Did Android Really Look Like BlackBerry Before the iPhone?

It's not easy being a dev for either platform.

Android has its own challenges and pitfalls.

Personally, I salute all Android devs that have given us so much!

We can talk OS philosophies until the cows come home, but at the end of the day, all we users really experience firsthand are the apps. ;)
 
Back
Top Bottom