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

Help Notification LED?

Not a completely fair comparison, as the iPad has a 9.7" screen, and first and foremost, has very tight OS and hardware integration that allows for such stellar battery life that still trumps any of the Honeycomb tablets. Same can be said for Blackberry devices as well. Give credit where credit is due and try to learn from it. This is probably why preliminary reports have pegged some great battery life on the SGS2. They are working hard on a lower level to fully optimize Exynos, something they can't do with Tegra, and all the prototypes with different performances gives reason to believe they are not fooling around on the driver and software front, and taking their time, unlike quicker to market early adopters Atrix and Optimus 2x.
 
hmmm i don't know what i did, but my battery seems to last a lot longer now.
Could be due to losing it for a few days. i8910 on silent with vibrate off (not the best idea) fell under the seat in my mate's car. Missing for 3 days bout a month ago, so the battery would have had a lot of time to discharge very slowly from not being used a lot.

I used to charge it overnight, but since i got it back, i only charge it every 2 or 3 days when it's on it's last legs. Right now, the battery meter says 5 bars out of 7, and i charged it 2 nights ago.. wtf??
Not like i haven't been using it, i make video calls, use wifi...
 
Not a completely fair comparison, as the iPad has a 9.7" screen, and first and foremost, has very tight OS and hardware integration that allows for such stellar battery life that still trumps any of the Honeycomb tablets. Same can be said for Blackberry devices as well. Give credit where credit is due and try to learn from it. This is probably why preliminary reports have pegged some great battery life on the SGS2. They are working hard on a lower level to fully optimize Exynos, something they can't do with Tegra, and all the prototypes with different performances gives reason to believe they are not fooling around on the driver and software front, and taking their time, unlike quicker to market early adopters Atrix and Optimus 2x.

iOS has the luxury of not truly multi-tasking which means unless your chugging on an application that uses data or consumes the gpu, you're not hitting the battery so hard. Suspending processes that reside in the background does wonders for battery life. I'm sure there's some degree of optimization so, yes, some credit is due there, but a lot of the efficiency and buttery smoothness of iOS resides in the pseudo-single-tasking approach. Apple isn't dumb. They knew what needed to be done to maintain a high quality user experience, and the average consumer doesn't care about what they're missing. My bet is that most of the folks here do (hence why they're here).
 
iOS has the luxury of not truly multi-tasking which means unless your chugging on an application that uses data or consumes the gpu, you're not hitting the battery so hard. Suspending processes that reside in the background does wonders for battery life. I'm sure there's some degree of optimization so, yes, some credit is due there, but a lot of the efficiency and buttery smoothness of iOS resides in the pseudo-single-tasking approach. Apple isn't dumb. They knew what needed to be done to maintain a high quality user experience, and the average consumer doesn't care about what they're missing. My bet is that most of the folks here do (hence why they're here).

I'm not too familiar with how multi-tasking works between iOS and Android, but I'm pretty sure Android can suspend and terminate applications as well, why task killers aren't necessary, and iOS can do facebook/email/notification background updates which fall under the data category, although they are more stringent about who and what can work in the background. Why the GPU is running something in the background when nothing is displayed, sucking up more power than it needs to, I'm not sure if that's really what happens, beyond maybe caching textures for a game, which is another guess.

The iOS program launch speed is also snappy, so I really don't know what constitutes as multi-tasking. Same thing for multi-threading, when a single core processor does it fast enough, and you can only run one window at a time, the perceived difference between single-core and multi-core processors is minimal on a phone. It's different with desktops, because you can run two or more windowed programs at full speed. I also think pegging the type of people in this forum into one hardcore category is silly. There are many greenstick posts, and simple or superficial stuff. I'm pretty sure the staff wants to attract more casual folk from their forum rules. Otherwise, I'd be screaming "google it!" all day. :p JK.

My main gripes that I would consider multi-tasking on the iPad right now is, why doesn't my search results stick in the app store when it boots me to the homescreen during installation? And where's the frickin' back button???
 
hmmm i don't know what i did, but my battery seems to last a lot longer now.
Could be due to losing it for a few days. i8910 on silent with vibrate off (not the best idea) fell under the seat in my mate's car. Missing for 3 days bout a month ago, so the battery would have had a lot of time to discharge very slowly from not being used a lot.

I used to charge it overnight, but since i got it back, i only charge it every 2 or 3 days when it's on it's last legs. Right now, the battery meter says 5 bars out of 7, and i charged it 2 nights ago.. wtf??
Not like i haven't been using it, i make video calls, use wifi...

You might be on to something there ;)
 
hmmm i don't know what i did, but my battery seems to last a lot longer now.
Could be due to losing it for a few days. i8910 on silent with vibrate off (not the best idea) fell under the seat in my mate's car. Missing for 3 days bout a month ago, so the battery would have had a lot of time to discharge very slowly from not being used a lot.

I used to charge it overnight, but since i got it back, i only charge it every 2 or 3 days when it's on it's last legs. Right now, the battery meter says 5 bars out of 7, and i charged it 2 nights ago.. wtf??
Not like i haven't been using it, i make video calls, use wifi...
It is quite possible the phone would have run down to completely no energy cells and then being left for a further period then killed off any residual memory.
 
I'm not too familiar with how multi-tasking works between iOS and Android, but I'm pretty sure Android can suspend and terminate applications as well, why task killers aren't necessary, and iOS can do facebook/email/notification background updates which fall under the data category, although they are more stringent about who and what can work in the background. Why the GPU is running something in the background when nothing is displayed, sucking up more power than it needs to, I'm not sure if that's really what happens, beyond maybe caching textures for a game, which is another guess.

The iOS program launch speed is also snappy, so I really don't know what constitutes as multi-tasking. Same thing for multi-threading, when a single core processor does it fast enough, and you can only run one window at a time, the perceived difference between single-core and multi-core processors is minimal on a phone. It's different with desktops, because you can run two or more windowed programs at full speed.

I may not have this spot on, but task killers aren't necessary with 2.2 because Android dynamically manages the memory and in some cases processes you kill may just re-start automatically depending on their settings. There is some limit, and yes Android will kill off or suspend the oldest processes (since last use) such that there's a limit to how many processes run in the background at any given time. So I suppose it's not true multi-tasking, but much closer than iOS which really just limits key functions in the background like the updates you mentioned. The difference, for example, is exiting an app in Android doesn't close the process (unless you choose that path) whereas in iOS it does close the process and you have no choice in that matter. True multi-tasking capabilities are inclusive, and Android treats it that way with a management scheme to work within the confines of the mobile arhcitecture. Prior to (I think) version 4, iOS was pretty much single tasking, but now it practices (very) exclusive multi-tasking. Again, it just comes down to Apple slightly loosening the reigns for a little extra additional functionality all while trying to keep tight control of the UX.

...I also think pegging the type of people in this forum into one hardcore category is silly. There are many greenstick posts, and simple or superficial stuff. I'm pretty sure the staff wants to attract more casual folk from their forum rules. Otherwise, I'd be screaming "google it!" all day. :p JK.
I think you misunderstood my assertion. I'm not suggesting many here are hardcore phone enthusiasts, but they probably want what iOS is lacking. Multi-tasking is at the heart of some of Android's superficial features that differentiate it from iOS. That's what I'm suggesting people are here for. What iOS can't do.
 
It's probably just the car seat gnomes, they often swap batteries. Nothing to be surprised about.

Android has always handled processes like you describe kyler, although since 2.2 it has been stricter about when an app gets killed.

I think if the SGS2 had a qHD Super AMOLED Plus display, I'd wet myself. Oh well, I guess they have to keep something for the SGS3. 720 Super AMOLED Plus? :)
 
I may not have this spot on, but task killers aren't necessary with 2.2 because Android dynamically manages the memory and in some cases processes you kill may just re-start automatically depending on their settings. There is some limit, and yes Android will kill off or suspend the oldest processes (since last use) such that there's a limit to how many processes run in the background at any given time. So I suppose it's not true multi-tasking, but much closer than iOS which really just limits key functions in the background like the updates you mentioned. The difference, for example, is exiting an app in Android doesn't close the process (unless you choose that path) whereas in iOS it does close the process and you have no choice in that matter. True multi-tasking capabilities are inclusive, and Android treats it that way with a management scheme to work within the confines of the mobile arhcitecture. Prior to (I think) version 4, iOS was pretty much single tasking, but now it practices (very) exclusive multi-tasking. Again, it just comes down to Apple slightly loosening the reigns for a little extra additional functionality all while trying to keep tight control of the UX.

I think you misunderstood my assertion. I'm not suggesting many here are hardcore phone enthusiasts, but they probably want what iOS is lacking. Multi-tasking is at the heart of some of Android's superficial features that differentiate it from iOS. That's what I'm suggesting people are here for. What iOS can't do.

Oky doky. I was grasping a little anyway, cuz I assumed you were another anti-apple troll. :p Okay, maybe just a wee bit biased.

I am still under the impression though, that most casual users will go straight to iPhone (in the US anyway) just by sheer popularity. No thinking involved, or know how. Android ends up being more of a concession, for people who can't get an iPhone for various reasons, mostly carrier-based, and maybe price.They'll have so many choices now, and specs to look at, it's disconcerting. And then there are people who hate what is "popular", want to be non-conformist, etc. The number of times people ask if so and so phone is an iPhone in public kind of speaks for itself.
 
I almost hate to use language like "real" in the context of this discussion. At the end of the day is the multitasking _effective_ regardless of how it's implemented.

When an app is in the background, it doesn't need to suck up any cycles unless it's handling required data anyway. For non-Windowed type OS, I'd say that's preferable.

Anyway, one of the main differences between aOS (Android) and iOS is where the multitasking is handled. Under iOS, the developer has to proactively make very specific API calls so the app can do things like continue to stream music (the iPod app, Pandora, etc.). In aOS, unless the developer specifically suspends the app when it swaps out, the OS itself continues to spend cycles, more like a traditional OS model.

The models are kind of funny since they're kind of a programming metaphor of how Apple operates vs. Google/partners/etc.


My main gripes that I would consider multi-tasking on the iPad right now is, why doesn't my search results stick in the app store when it boots me to the homescreen during installation? And where's the frickin' back button???

If you JB your iPad there's an app called "Stay in Store" (er, something like that). When you install, it doesn't flee back to the home pages. I think it has a couple of other tweaks to the whole download/install process too.

I was JB'ed with 4.3.1, but just not enough to incent me to stay (even with iFile and better notifications). Keeping up with the OEM updates (that require either waiting and/or re-JB'ing each time), plus a little runtime wonkiness made up my mind for me to go OEM only (just did last night with the 4.3.2 update).
 
I almost hate to use language like "real" in the context of this discussion. At the end of the day is the multitasking _effective_ regardless of how it's implemented.

When an app is in the background, it doesn't need to suck up any cycles unless it's handling required data anyway. For non-Windowed type OS, I'd say that's preferable.

Anyway, one of the main differences between aOS (Android) and iOS is where the multitasking is handled. Under iOS, the developer has to proactively make very specific API calls so the app can do things like continue to stream music (the iPod app, Pandora, etc.). In aOS, unless the developer specifically suspends the app when it swaps out, the OS itself continues to spend cycles, more like a traditional OS model.

The models are kind of funny since they're kind of a programming metaphor of how Apple operates vs. Google/partners/etc.

You can't really say what's preferrable simply from a basic operation standpoint without considering the higher level purpose. The Android method is the foundation for widgets, active monitoring, custom UI overlays, etc. It's essential to what makes Android customizable. Correct me if I'm wrong, but aren't the iOS background API's severely limited by Apple to a handful of operations such as music streaming or message notifications?
 
android Operating System? aOS :rolleyes:

I got that, sophisticated as it is, but it is called Android. iOS is called iOS, not because it is the iPhone/iPod Touch/iPad OS but because Apple decided to call it iOS. The OS might come from "Operating System", but that doesn't mean operating systems randomly change their name. Do you call Windows wOS?
 
I got that, sophisticated as it is, but it is called Android. iOS is called iOS, not because it is the iPhone/iPod Touch/iPad OS but because Apple decided to call it iOS. The OS might come from "Operating System", but that doesn't mean operating systems randomly change their name. Do you call Windows wOS?

People can call android and iOS whatever they like.
Personal preference I guess...
The OS comes from Operating System, there's no doubt about that.
And I call windows crap :p Mac ftw :D
 
People can call android and iOS whatever they like.
Personal preference I guess...
The OS comes from Operating System, there's no doubt about that.
And I call windows crap :p Mac ftw :D

:confused:

No you can't. The name is an identifier, the point is to specify what you are referring to. That only works if people use the same name. What mobile operating system am I referring to here?
"The new version of Wibble looks impressive."

Any idea? I am of course talking about Bada. Or Meego, I forget which. If only I'D NOT MADE STUFF UP.

If I'd seen aOS without the explanation, I'd see the iOS format, assume the 'a' was for Apple and conclude that it was referring to their desktop operating system, OSX.
 
Shhhh. It's not a big deal. I call Windows by WinOS too. :p That's been around way before the iPhone and iOS. aOS is fine within the context of the post. Might even be less confusing than Android for general use. Such a common generic word. But aOS has the OS of iOS, like iDock or iLuv has the i of the iPhone, so people can get hostile about it sometimes.


You know I sometimes stumble upon articles or news segments on TV talking about how multitasking is a myth and you really aren't doing more at the same time, you are doing less overall, just jumping between multiple things and getting a bit confused in the process. People with 5 monitors and split windows on each and such. Apple released their App Store for Mac and all their programs go fullscreen. This will be their design philosophy for upcoming OS changes to Macs in general. Even before then, back when OSX was released and people didn't start randomly hating Apple because it was still the underdog, nerdy tech writers always praised OSX for its simplicity and stability, even though it technically couldn't do as much as a Windows machine, and was a closed system, like now. It could do 95% of the stuff well enough, just not that 5% fringe stuff that Windows could. They would recommend it to grandmas and schoolchildren and non-techies and such. There were less menus and more icons and generally less clutter and stuff. I don't think the average person can multi-task that well. I have a hard enough time focusing as it is. :p
 
Andriod is a geek brand OS, thereby Android is the correct name for the OS
IMHO.
I bet many Iphone users out there dont even know+\care the OS they use is iOS. I would even go further on that bet, and say that way more %`s in the Andriod comunity know what the name of the OS is, lets hope to keep it this way.

Btw Win os could be Win 3.11, win 95 , Server 2000 , WinNt, Windows Mobile, Windows phone 7, Win Vista , Win 7 ++++++ its the same as saying Microsoft os, Its a big NOGO ,atleast in geek termonology .. IMHO

Annyways if where to call it aOS, sJOBS would probably sue us for using the "feel and branding of apple"

(sJOBS is ofc Steve Jobs(see what i did there?)) :)
 
Shhhh. It's not a big deal.

Hahaha, no kidding!

I think it's hysterical people got all worked up over that. I believe I used it before when I was specifically talking about the OS specifically vs. the collective of Android devices, or something to that effect, but was setting it up [in that post] to use more than once to abbreviate things a bit (even though I didn't use it again).

Funny enough, I posted that in between writing some technical specifications for a revision to one of our major Federal products (in the forensics sector), which coincidently discusses a potential Android component (which I recently prototyped). For the record, I did _not_ use aOS in the specifications :D



You can't really say what's preferrable simply from a basic operation standpoint without considering the higher level purpose. The Android method is the foundation for widgets, active monitoring, custom UI overlays, etc. It's essential to what makes Android customizable. Correct me if I'm wrong, but aren't the iOS background API's severely limited by Apple to a handful of operations such as music streaming or message notifications?

Yeah, iOS supports audio, location, plus push/location notification, but also task completion. It's interesting, because I'd say a large number of the widgets I've seen/used could be constructed from that's available in the iOS API, but there is of course not the front facing UI that Android has (in terms of how the data is delivered).

If you sort of abstract a widget and even an app into it's basic functions, those really do match up well with the multitasking API in iOS.

I'm actually trying to think of a case where something beyond that would be needed? I guess maybe an RTS type game?

Most background tasks do fall into push (email, FB updates, weather), simple local notifications (timers, calendars), "data services" like voice/GPS, or extended, but finite tasks like uploading an image to photobucket.

***

I wanted to add something more on topic :D

When I got my Atrix, I was kind of stoked since it had an LED notification, and even supported several colors (I used one of those testing/management apps).

I considered it to be a nice perk over the Captivate.

Well, come to find out, I rarely, if ever used it. If I'm out and about I'll just occasionally check the phone by waking it up, and while I'm here at the World HQ, I use growl to receive broadcast notifications to my PC (plus things like voicemail are routed to my GMail where I'm notified).

For *me* at least, it's not a big deal that the SGS II doesn't have a notification LED. :)
 
Andriod is a geek brand OS, thereby Android is the correct name for the OS
IMHO.
I bet many Iphone users out there dont even know+\care the OS they use is iOS. I would even go further on that bet, and say that way more %`s in the Andriod comunity know what the name of the OS is, lets hope to keep it this way.

True, but the simple hardware selection helps. If you're using iOS, you're using Apple and you using an iDevice. Android comes in all sorts of shapes and sizes, so there is a need for a way to identify all hardware that uses a common OS. If I had an iPhone and wanted to upgrade and keep my purchased apps, I get another iDevice. Simple. I have an HTC phone but if I wanted to upgrade, I can't just buy another HTC phone or I might get stuck with WP7. I can, however, buy (some) Samsung phones, Motorola phones etc. This is where the little green robot comes in.

Also, yes, Android users are generally more clueful. Not all Android users of course, which is important to the on-going adoption of the platform.
 
Do the amount of LEDs cover the same area as in the ad or are they conning people and you only get to use the small area shown at the end of the vid?
 
Well, if you wired up a 9000mAh battery to an SGSII, restricted it to wi-fi, and ran iOS on it, you'd probably get the same results.

Seriously, the cure to my battery issues came in the form of having a second battery on hand and a battery charger. What would be great is if the manufacturers took on the challenge of allowing these phones to run off external power so you could hot swap the battery. Powering down for the change out is a little cumbersome.

Which phone are you using? If I plug my captivate in it will stay powered on even if i take out the battery. It's actually really annoying when trying to quickly reset it for recovery mode and what not because I forget it stays on when plugged in.

First time it happened it was really badly frozen and I took the batter out. It stayed on and i freaked out, "wtf!? how can a phone be so stuck it's stuck ON!?" heh

anyway, this could be only when plugged into a computer though, but I never mounted it so it just thought it was charging. I'll look into this more.
 
Back
Top Bottom