Quake3World

Eraser wrote:But it's Android and Android still suffers from wakelocks and battery murder even in 2017

Eraser wrote:More anecdotal evidence.

Look, I'm not arguing Android is better or worse than iOS, but the endless stream of bullshit (anecdotal) arguments from either side of the discussion are just really tiring and dumb.

Eraser wrote:More anecdotal evidence.

Look, I'm not arguing Android is better or worse than iOS, but the endless stream of bullshit (anecdotal) arguments from either side of the discussion are just really tiring and dumb.

Don Carlos wrote:lol What a pathetic thread

SOAPboy wrote:

Eraser wrote:More anecdotal evidence.

Look, I'm not arguing Android is better or worse than iOS, but the endless stream of bullshit (anecdotal) arguments from either side of the discussion are just really tiring and dumb.

Look man, I'm not gonna argue either way, a quick google can prove im right. This isnt some anti android thing, its purely facts. Look it up.

losCHUNK wrote:

Eraser wrote:More anecdotal evidence.

Look, I'm not arguing Android is better or worse than iOS, but the endless stream of bullshit (anecdotal) arguments from either side of the discussion are just really tiring and dumb.

https://developer.android.com/topic/per ... elock.html

https://www.xda-developers.com/stop-wak ... hout-root/

I have no brand loyalty which is why I'll be going back to Apple after a good few years and I'm not here to argue what's better or not but I'm just talking about known issues and my experiences.

losCHUNK wrote:That's why said it varies from app to app but it can also be an Android update too which is what hit one of my phones, where Android itself would hoard resources in the background. The main problem is trying to track the problem down cos of Android kernel, the problem app won't show itself because it's hidden somewhere in the memory. Android been trying to fix it for years, the problem is allowing bad practice in the 1st place, it's more like getting a nasty virus rather than a bad program.

So when your phone updates and you got a wakelock problem, wtf do you do ?

Eraser wrote: Sounds like implementation errors in individual apps, not something that's wrong with the OS.
If I write a Windows application that peaks your CPU to 100% by simply entering an infinite while loop, look at what that'll be doing on your laptop's power consumption. You can hardly blame Windows for this.

Κracus wrote: Ummm no. My work has me directly supporting these devices and battery issues are no more a problem with samsung than they are with iphones or blackberry's. All of which I support from a technical point of view. Funnily enough, we actually try to dissuade people from using apple devices as much as possible due to their technical limitations which cause us problems and the only reason we allow them at all is because people in charge who don't know anything about technology refuse to not use them because of marketing. The only benefit I can see to owning an apple device is the apps that are only available for apple devices and I personally do not see them as being that important. I work with these devices daily so I see them a lot. I have two samsung devices and to give you an idea of how good the battery is on them, my Samsug S3 is still used daily and the battery will last a full 24 hours with heavy use. My A5 which is newer will last 48 hours with heavy use. This is consistent with apple devices too. If anything, blackberry's put both to shame in terms of battery life as I've seen the older devices last up to 6 days on a charge with normal use and I've had blackberry's sitting on my shelf for months before they finally beep to let me know it's low on battery.

Eraser wrote:You ok, soapboy?