Jump to content
|Topic||Stats||Last action by|
|ULA wants the public to name its next rocket||
|Quebec resident Alain Philippon to fight charge for not giving up phone password at airport||
|Printing via RDP with a none supported printer||
|Odd password field question||
Posted 09 January 2013 - 19:37
Posted 09 January 2013 - 22:39
Most useful, since indeed there's been quite literally a quadrupling of power (single core 1.5 GHz to quad core 1.5 GHz, 512 MB to 2GB of RAM) between my previous venture into Android and the phone I'm looking at
It almost entirely depends on how many and which apps you install. If you have 100 apps that all think they need a background process, then yes, you're going to see a slowdown. I generally run a handful (10-20) apps and some small games usually of the words with friends or scramble with friends variety, and I haven't had lag on the latest generation devices. I don't think I could make my One X lag if I tried. Older phones like my Captivate were definitely slower though, but again, the only relation to how long it had been since I'd factory reset would have been how many apps I had installed. Regardless, smooth then was nothing like smooth now. Project Butter really helps to smooth out the whole experience.
I know that the iPhone 4 (my current phone) lags like an asthmatic ant when I try to do fast browsing in Chrome Mobile, and I've figured out that mobile browsing with Chrome, Kindle and various social media clients are the primary usages of my smartphone. I don't mobile game - I always have something to read on the go, and so I need a phone that gives me the best mobile browsing experience with Chrome Mobile.
Put it this way, I've never found any of my Android devices to be any more or less laggy than iOS devices of the same time frame. The iOS fanboys just like to act like iOS never lags. I had a 3G a long time ago and it had horrible lag sometimes. I had an iPhone 4 and it was much better, but it too lagged now and then. I haven't had extensive experience with the iPhone 5, but I suspect, like Androids on current hardware, it would show very little to no lag. The reason it would have been more noticeable on an Android is because of the multitasking and allowing apps to freely run their own services. I think these features are major advantages of Android, but they aren't without some performance impact. That's why Apple is always able to include slower CPUs and less memory in the iPhone comparatively.
Thanks, very helpful post
I'd really say that smart phones have only just matured in the last year or so. Prior to that, new features were being rolled out as fast as performance was being improved, especially on a mobile OS like Android that has more extensive multitasking and such. Now that mobile CPUs have gotten so fast and large amounts of memory are being included, lag isn't really much of a factor on more new phones from any manufacturer or type.
Posted 10 January 2013 - 03:08
Posted 10 January 2013 - 03:52
I'm still running Android 2.3 on my old HTC and have never had a problem but a friend of mine has the exact same phone and has had nothing but problems with bogging down. Not sure exactly what it is.
Posted 10 January 2013 - 06:21
It's extremely easy to root an Android phone. I had my friend root her phone, and she drove through the whole process, while I watched. Hell there are even toolkits that pretty much do everything for you. There's a plethora of information/videos on the internet My Galaxy Nexus has been stable, and Jelly Bean made it so much smoother.
Yeah, and my Windows Phone started to bog down after a while. The main UI was still smooth, but once you open up too much apps, it was game over. Not to mention the 'mulitasking' on WP just blows compared to Android/iOS
Posted 10 January 2013 - 06:25
Posted 10 January 2013 - 17:54
There are multiple reasons why this happens.
It comes down to:
1. Apps you install. If an app you installed has memory leaks (aka not coded right or has a bug that causes that memory leak) only that one app can cause your phone to become unstable as it will eat your memory. Unlike iOS, the thing with Android is that it is a true multitasking OS. This means that your apps runs as a process in the background and can execute things. iOS kills apps completely after you switch away from it, so the app can't do anything when it's in that state. It's a bit more complex than that but that's basically the gist of it.
2. The ROM version or custom ROMs might also have memory leaks themselves. Especially in launchers they put on top and that could be the cause of instability. At first everything runs great, but after time your OS gets out of memory and it starts closing processes and just becoming unstable. That's when you get those WAIT or CLOSE PROCESSES dialog.
For those who have issues my advice is when your Android device starts lagging, go to Applications and you will see processes there and how much memory they consume. You can spot which apps have memory leaks and just kill those and don't run them or if you do, make sure you close their process after you are done with it.
Posted 10 January 2013 - 22:12
A developer of an Android app has to explicitly write code that runs in the background, otherwise the OS (as of v4) could kill the task to free up resources. And it does. It more-or-less works like iOS now for the vast majority of apps. Difference being, a developer can explicitly force background execution of code for whatever reason on Android and it will be approved for the app store. In iOS, only applications featuring VoIP or Navigation are allowed to execute whatever code they want in the background (as a matter of App Store policy).
Both operating systems have "true multitasking*" (with an Astrix).
Posted 10 January 2013 - 22:33
Your application on Android will run as a process in the back. Android doesn't kill them. You have to ask permission whether or not you want to run a long running processes in the background which is something else.
And no, Android and iOS are not the same. Android is a true multitasking OS and allows execution of background services and parallel tasking while iOS is a quasi multitasking OS which allows only 7 APIs to run in the background and it's not a matter of App store policy it's how iOS is engineered.
Posted 10 January 2013 - 23:02
...I didn't say they were the same I was saying as of v4 of Android that they are similar. But you know both of them inside and out so I digress.
The articles I've read on Android v4 multitasking state things differently but I guess they don't know as much on the subject than you do, Boz.
Posted 10 January 2013 - 23:14
Posted 11 January 2013 - 02:46
My wife used a Samsung with Android for two years and it slowly got slower to the point she could not stand using the phone anymore. She only had a few apps installed and rebooted often. It got worse with time. I almost seemed as if Google was purposefully slowing down the OS so that she would get a new phone. Well she did. She got a WP7 and loves it and will not be going back to Android. Several people I work with report the same with different Android phones.
Posted 11 January 2013 - 04:12
Posted 11 January 2013 - 04:34
Posted 11 January 2013 - 04:42
Every Android phone i had got slower over time, eventually to the point it rebooted itself, or just froze on a black screen. Always found this to be annoying.
Recently i got some cache clearing app which seems to help alot, but i still get the problems.
i had the original droid, and an x2. Thinking about getting a Galaxy s3, but i don't know. i think the problems will still be there.
Man i so wish iphones were itunesless.