Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Android Lag - Nonsense or Fact?
- Thread starter mib1800
- Start date
- Sort by reaction score
have you used an iphone 5 and loaded up 50+ apps and try to make it lag? I did that with a jailbroken iphone 5 with tons of tweaks and live wallpaper running. I can open safari and browse the web with no lag. I can even open up Engadget app and scroll with no lag. I did see lag when I opened the multitask window that uses the Auxo icons and scrolled and that was the only lag I experienced, but that can be blamed on the developer because once you scroll through all the icons it's smooth as butter; which tells me it needs optimization. I did that on a iphone 4 which is old and got major lag, but iphone 5 just the auxo multitask icons lag. Take my android device and open up the Comcast app and start scrolling all I see is lag with not even a app running in the background. While on my iphone or ipad it's butter smooth even with 50+ apps opened. People shouldn't talk about lag on a ios device unless you ran one that has 1GB of Ram.
Last edited:
50+ apps open at the same time?
News flash .... They weren't still opened.
point is they were clicked on and took up Ram...so my phone should lag like others have suggested.
I guarantee you some of those 50+ apps you speak of would have reloaded/refreshed.
50+ apps open at the same time?
News flash .... They weren't still opened.
Android doesn't keep an infinite number of applications running either. All systems start killing off applications when they hog too many resources.
Is that a good thing? Senior Android developers at I/O just said that the newer applications optimized for 4.0 and higher are causing lag:
"The lagging effects that some users may experience has more to do with each of the individual applications than the system itself, and those applications are sometimes optimized to work only with newer hardware."
Well if you wanna live in a completely worry free app world then, no. You'll be better off with the iPhone and the App store.
Consider most posts I see on lag is more about the OS, default launcher, or default apps. So maybe most of the cases are from bloat and not really any apps downloaded. 4.2.2 was known to have lag even on the N4.
Yes it still had a little lag. Especially trying to access the dialer, contacts, texts, or photo area quickly.
True, but browsing Safari on iOS on my iPhone 5 is tons smoother than using Chrome on my Nexus 4 or GS3. Granted their are other browsers are smoother than Chrome, such as Opera. But none of them are near as fluid as iOS. It isn't terrible on Android, it's just smoother on iOS.
I agree, the windowed mode is pretty sick.
That's Chrome, it's really bad on mobile (since it takes huge amounts of resources and mobiles don't have them).
+1
I've been using Dolphin HD for a long time. I've tried others but keep going back to Dolphin HD. It's a solid mobile browser.
Too lazy to go through 6 pages of this, but Galaxy S4 user here - NO LAG. Smooth as butter. And I'm coming from an iPhone 5.
(I'll gladly make a video)
(I'll gladly make a video)
Not all opened apps in Android consume CPU cycles in the background. In reality most apps (other than service apps) when they go into the background they are suspended like in iOS. The only difference is that these suspended apps can still receive intents/events and when they do, they will wake up and run.
You don't actually need to worry about "closing" of app in Android either. Apps are divided into 2 broad categories - normal and service app. Normal app will get suspended when it goes to the background (like iOS) and when RAM is needed they are unloaded. Service apps are kept alive in RAM monitored by the OS. If any service app that continues to hog the cpu for a certain amount time the "force close/wait" dialog will popup. And you cannot kill service app (it will be restarted).
The problem arises when you have you have many rouge (or poorly programmed) service apps that keep waking up in short regular intervals to do processing and thus consuming battery. But most mainstream apps that are service apps like skype. whatsapp, g+, tw etc dont really consume much battery.
Last edited:
Another take:
- Having the buttons on top is sensible as that's where usually any branding etc is as well. The placement doesn't become an issue until phone sizes get bigger than the iPhone 5.
- The inconsistent back functionality in Android is ********. When I press back, I want the last step to be whatever is the top level of the current app. It should not change apps or go to the home screen, that's why there's a separate home button or gesture. Applications aren't a stack.
- Agreed about settings, but I still think it's better to have settings in one place vs scattered inside each app with a different UI etc.
- Long pressing for a menu is no more logical. It's just a different action you have to learn. Personally I really like how quick the "swipe and click delete" functionality is to use while also being pretty foolproof so you don't accidentally remove stuff.
- Agree about quick toggles though that is available as a jailbreak feature.
- With the screen sizes the iPhones have, having a small notifications display isn't that useful.
Oh and iOS 6 does lag sometimes, on both my iPhone 4 and iPad 3. Even stock Android lags occasionally on the devices I've used. I think it will still take a while before we don't see this on mobile devices and it is further aggravated by the more immediate response we expect when using devices with our fingers.
Lag is expected with iPhone 4, considering it's (now) outdated and weak internals. Although iPad 3 is just over a year old it uses the same CPU from the iPad 2, and it's GPU (although 2x as powerful as the A5) has to push 4x the number of pixels.
The fairest thing to do is to compare the newest generation of devices (iPhone 5 (A6) and iPad 4 (A6X)). I have an iPhone 5 and it never lags. The only way you can make it stutter is to restart it and then the moment it turns on swipe to the spotlight screen. That's the only time I experienced lag with the iPhone 5. After doing this you can swipe to spotlight a hundred times and do whatever you want and as fast as you want and the phone won't lag. It is the smoothest phone there is.
I see what you mean about scrolling in iOS. I visited my grandparents yesterday. At Christmas I bought them an iPad 4 to replace their dying laptop, my grandad asked me where he could get a HDMI adaptor for the ipad. I went on apples site to look at accessories, scrolling took forever. I swear its like it only let me scroll a few inches with each flick. I don't remember it being that slow.
I guess I've been spoiled by android scrolling, where I have 100 comments per page in these forums enabled, I can scroll to about comment number 30 in a single flick.
I guess I've been spoiled by android scrolling, where I have 100 comments per page in these forums enabled, I can scroll to about comment number 30 in a single flick.
The thing is that iOS way of scrolling is not laggy. It is intentionally made that way (it offers the most control). In the music app for example scrolling is faster (it doesn't mean it is better). I prefer the iOS way and you are free to prefer Android, but to say iOS scrolling is laggy is simply not true.
Then you never had apps downloading and installing in the background. If anything, that makes iOS stutter and lag far more than doing the same on Android.
I can even tell when an app being downloaded has gone from downloading to installing--as that is when things are the most jerky.
It is very real.
Michael
----------
I never bother closing apps and my Note 2 does not lag. I still own it. No "justification memories" going on here.
Michael
Dude, I've used Apple hardware since a still warm out of the box Apple //. Don't ****ing tell me what I've never done and ****. Trust me when I ****ing say stuff. It means I know what the **** I'm talking about.
It's done intentionally. I don't want a flick to take me all the way to the bottom of a page. A flick is just that, a way to scroll a bit further down. I feel it's more precise that way, instead a flick throwing me all the way to the bottom of the page.
And speaking of flicking. On Android tablets, Chrome's flick scrolling is completely broken. Sometimes the page won't even move at all. I've tried this on my Nexus 7 and my older Asus Memo tablet and it's the same behavior.
Is Google ever going to release an update to fix this? It's just painful.
Then the intention is wrong. On Android depending on the length or intensity of the flick the scrolling speed varies according. one flick can take you a long or short distance. On iphone the max speed/distance is always the same no matter how fast or long you flick.
The implementation of iphone general UI and browser scrolling is subpar compared to android. Since we use scrolling all the time I feel the lag in iphone is worse. I use the s3 and note2 most of the time and I can immediately feel the irritating ip5 scrolling lag when I use it.