What's new
DroidForums.net | Android Forum & News

This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

iPhone 4.0 vs Android 2.1

Oh really? Go ahead and open 20 browser windows and watch how fast your battery dies.

If you have several tasks and half of them are sleeping they have a flag that tells the scheduler to skip accessing anything related to the sleeping task and go to the next one. Having to kill the task and start it up again takes more battery power and cycles to perform than simply skipping the task.

As for memory, you have to keep it powered if you are using it or not. You cannot turn off the power to half your memory to save power.
 
Last edited:
I'm not even going to bother being polite about this because I'm getting tired of people chiming in when they don't know what they are talking about. So, point being, you don't know what you're talking about. Every task you add to memory exponentially increases the amount of electricity required by memory to keep it there. ANY task in memory is draining battery. It uses the same amount of battery from memory whether it's using CPU cycles or not. It's kind of ridiculous that people actually believe memory doesn't require electricity to function.

Polite or not, the marginal amount of electricity to maintain a few kilobytes of code in memory compared to running an app is infinitesimal. The electricity you're talking about is maintaining memory whether it is filled or not. The notion that "every task you add to memory exponentially increases the amount of electricity required" suggests you don't understand the word "exponentially."

Oh really? Go ahead and open 20 browser windows and watch how fast your battery dies.

OK I have on any given day anywhere between 10 - 15 browser windows open in the stock browser. I have my widgets running, with a battery miser that shuts off wifi, gps, APN after two minutes of sleep. I listen to Pandora/MP3s for approx 2 hours on the commute, browse for about 1 or 2, facebook, text and about 30 minutes of phone calls. I unplug at 100% at 7am and get home at 7:30 pm with 40%-50% every day. No task killers involved.
 
Polite or not, the marginal amount of electricity to maintain a few kilobytes of code in memory compared to running an app is infinitesimal. The electricity you're talking about is maintaining memory whether it is filled or not. The notion that "every task you add to memory exponentially increases the amount of electricity required" suggests you don't understand the word "exponentially."

Oh really? Go ahead and open 20 browser windows and watch how fast your battery dies.

OK I have on any given day anywhere between 10 - 15 browser windows open in the stock browser. I have my widgets running, with a battery miser that shuts off wifi, gps, APN after two minutes of sleep. I listen to Pandora/MP3s for approx 2 hours on the commute, browse for about 1 or 2, facebook, text and about 30 minutes of phone calls. I unplug at 100% at 7am and get home at 7:30 pm with 40%-50% every day. No task killers involved.

Obviously, that's impossible. And if you had a task killer you'd never use any battery power. :)
 
Oh really? Go ahead and open 20 browser windows and watch how fast your battery dies.
As for memory, you have to keep it powered if you are using it or not. You cannot turn off the power to half your memory to save power.

That's not true. Memory power consumption scales as needed.

OK I have on any given day anywhere between 10 - 15 browser windows open in the stock browser. I have my widgets running, with a battery miser that shuts off wifi, gps, APN after two minutes of sleep. I listen to Pandora/MP3s for approx 2 hours on the commute, browse for about 1 or 2, facebook, text and about 30 minutes of phone calls. I unplug at 100% at 7am and get home at 7:30 pm with 40%-50% every day. No task killers involved.

That's terrible battery life. You're using what? A total of 4 or 5 apps? If my Droid used that much battery in 24 hours I'd throw it in the river. Plus your short story is very conflicting with your own story. You're not a good story teller.
 
I am interested on more of the details on the multitasking engine.
1. Background audio
2. Voice over IP
3. Background location
4. Push notifications
5. Local notifications
6. Task completion
7. Fast app switching

These are the ones that are affected for multitasking as stock once the update gets pushed.
Now thoughts on that? Since we are just going all over the place about it..lets address it one at a time.
 
And i just posted this on the FLASH thread...since we are talking about all that affects IPHONE 4.0 vs the Future of Android and Flash.

Adobe says iPhone / iPad adoption and 'alternative technologies' (cough, HTML5) could harm its business -- Engadget
Adobe says iPhone / iPad adoption and 'alternative technologies' (cough, HTML5) could harm its business

By Nilay Patel posted Apr 9th 2010 11:50AM



Adobe might continue to crow about Flash and its importance on both the desktop and mobile devices, but there's no lying to investors, and the company is pretty blunt about the threat of the iPhone and iPad in the end-of-quarter Form 10-Q it just filed with the Securities and Exchange Commission: it flatly says that "to the extent new releases of operating systems or other third-party products, platforms or devices, such as the Apple iPhone or iPad, make it more difficult for our products to perform, and our customers are persuaded to use alternative technologies, our business could be harmed."

Now, Adobe has to make doom-and-gloom statements in its SEC filings -- it also says that slowing PC sales or a failure to keep up with desktop OS development could harm its business -- but the timing is crazy here, since just yesterday Apple changed the iPhone OS 4 SDK agreement to block devs from using the upcoming Flash CS5 iPhone cross-compiler to build iPhone apps. What's more, Apple's also using HTML5 for its new iAd platform, which could potentially undo Flash's stranglehold on online advertising as well. Yeah, we'd say all that plus the recent push for HTML5 video across the web -- and from Microsoft -- could harm Adobe's business just a little. Better hope that final version of Flash Player 10.1 is everything we'd hoped and dreamed of, because Adobe's going to have to make a real stand here.
 
Oh really? Go ahead and open 20 browser windows and watch how fast your battery dies.
As for memory, you have to keep it powered if you are using it or not. You cannot turn off the power to half your memory to save power.

That's not true. Memory power consumption scales as needed.
Ive never heard of being able to turn on part of flash memory to save power. It is all or nothing.
 
Here in NY there was an interview on Fox Morning with a guy from PC Mag about the soon to be released iphone os4..well this guy was an obvious shill for Apple! He stated that now iphone will be able to multitask and that once iphone develops something it puts a "stamp on it" which encourages others in the industry to follow. WHAAAT?! Even the interviewer mentioned that the Droid already multitasks and he went back to the iphone"stamp" claim. What bs, trying to take credit for that is pure puffery! Google should sue!
 
Well, some people don't think Android has to worry...

Apple's iPhone OS 4.0 No Threat to Android - PCWorld

Good article. But I think what the author misses is that all Apple has to do to "win" is to "catch up." As long as there aren't obvious deficiencies compared to the Android platform most consumers will opt for platform with the huge set of available apps. That doesn't make the iPhone OS a "threat" to the Android. But it does suggest that Apple's moves will prevent major bleeding.

And since the limitations the author cites (limited multitasking, proprietary control of apps) don't bother most consumers and the Apple design will almost undoubtedly limit the unpredictability of response on the phone, I suspect that Apple will benefit.
 
Here in NY there was an interview on Fox Morning with a guy from PC Mag about the soon to be released iphone os4..well this guy was an obvious shill for Apple! He stated that now iphone will be able to multitask and that once iphone develops something it puts a "stamp on it" which encourages others in the industry to follow. WHAAAT?! Even the interviewer mentioned that the Droid already multitasks and he went back to the iphone"stamp" claim. What bs, trying to take credit for that is pure puffery! Google should sue!

Sue? Hardly. AT&T learned that lesson when they tried to sue Verizon over its advertising claims.
 
As for memory, you have to keep it powered if you are using it or not. You cannot turn off the power to half your memory to save power.

That's not true. Memory power consumption scales as needed.
Ive never heard of being able to turn on part of flash memory to save power. It is all or nothing.

It's all "on". But as it's utilized more power consumption increases. Same as a PC.
 
I am interested on more of the details on the multitasking engine.
1. Background audio
2. Voice over IP
3. Background location
4. Push notifications
5. Local notifications
6. Task completion
7. Fast app switching

These are the ones that are affected for multitasking as stock once the update gets pushed.
Now thoughts on that? Since we are just going all over the place about it..lets address it one at a time.

Good suggestion. Here's another. Try to come up with a realistic scenario in which this "limited multitasking" would not meet almost all users' needs. Clearly that's what drove Apple's design.
 
That's not true. Memory power consumption scales as needed.
Ive never heard of being able to turn on part of flash memory to save power. It is all or nothing.

It's all "on". But as it's utilized more power consumption increases. Same as a PC.

If your contention is that "running" apps deplete the battery, you're not going to find anyone to disagree with you. The question is how much power is required to have an app sitting quietly in memory versus having that memory address "empty."
 
Back
Top