I like how they're still pushing web "apps" in 2013.
[QUOTE=zugu;39702353]I like how they're still pushing web "apps" in 2013.[/QUOTE]
They are the future. Write once run everywhere. Phones just aren't fast enough to cope with the overhead yet and all the implementations suck.
looks incredibly ugly IMO
The only thing I like about this is that it's a tiny phone with Smartphone capabilities like 4g. But if someone made an Android phone with an identical size for an identical price, it'd sell insanely better than this just because Android's already so established.
[QUOTE=Amiga OS;39704599]Android is just a horrifically bad idea on a budget phone, you need a 1.5Ghz quad core CPU and 2GB of RAM to get the piece of shit to even approach a constant 60FPS and not close background apps randomly.[/QUOTE]
No, not at all. Android can run very quickly on most devices. The issue is many hardware manufacturers don't take the time to properly optimize Android for their device. You'd have that issue with [i]any[/i] operating system that spans many constantly changing hardware platforms (such as the many versions of ARM). Take the Kindle Fire for example - Since it was Amazon's only Android device, they had plenty of time to optimize it. With a 1Ghz Dual Core and 512MB of RAM it runs Android Gingerbread very well. And, there are third party ROMs for it such as CM10 that, because they are properly optimized, run even better than the stock OS.
In short, the problem with "budget" Android devices isn't Android, it's that the company that made it didn't spend the proper amount of time optimizing Android for the device. This would happen with any operating system said company decided to put on their device. A phone with a 1Ghz single core processor and 512MB of RAM is perfectly sufficient for running the latest version of Android and playing most Android games if properly optimized.
[QUOTE=Amiga OS;39704599]Android is just a horrifically bad idea on a budget phone, you need a 1.5Ghz quad core CPU and 2GB of RAM to get the piece of shit to even approach a constant 60FPS and not close background apps randomly.[/QUOTE]
ok whatever you say lol
android runs fine on low end devices, the only time low end budget devices turn to shit is when they're loaded with manufacturer bloatware. not to mention it all depends on your definition of a budget device. any modern smartphone OS will run like shit on a hyper-cheap device, its not like iOS is powering $100 phones from Taiwan without problem
[editline]24th February 2013[/editline]
1.5ghz quad and 2gb ram my ass lmao you're just making shit up
my first android phone was an htc aria, it was 600mhz and 384mb ram, AND it was loaded with the god awfully sluggish HTC Sense, still ran beautifully, STILL DOES after like 2-3 years, never force closes my apps, never has any issues with lag or sluggishness
[QUOTE=Kopimi;39704765]my first android phone was an htc aria, it was 600mhz and 384mb ram, AND it was loaded with the god awfully sluggish HTC Sense, still ran beautifully, STILL DOES after like 2-3 years, never force closes my apps, never has any issues with lag or sluggishness[/QUOTE]
I've got an old Huwaei Ascend laying around (710Mhz OC, 256MB RAM) running CM7 on it. It can emulate NES and SNES and use things like YouTube just fine :v:
Not to mention the [url=http://en.wikipedia.org/wiki/HTC_Dream#Hardware]very first Android phone ever made[/url] (528Mhz, 192MB RAM) was capable of playing [url=https://code.google.com/p/prboom4android/]a full port of Doom.[/url]
[QUOTE=Amiga OS;39705252]Nexus S 1Ghz ARMv7, 512MB of RAM, both with CM10.1 and Stock AOSP, runs like fucking shit.
ZTE Blade 600Mhz ARMv6 512MB of RAM, stock 2.2 ROM and CM7, runs like shit.
Sony Xperia Tipo 800Mhz ARMv6, 512MB of RAM, Android 4.0, runs like shit.
iPhone 1 412Mhz ARM11 chip, 128MB of RAM, runs rings around nearly every low-mid range Android phone.[/QUOTE]
Except you pulled all of that out of your ass.
[url]https://www.youtube.com/watch?v=aOCletx2OJU[/url]
[url]https://www.youtube.com/watch?v=-zmXXGIFSHc[/url]
[url]http://www.youtube.com/watch?v=lVbwFkIPJ5M[/url]
All three of those phones are capable of fluently running 3D applications. It is true that iOS gets better performance for the specs than some of these phones, but that goes back to what I said before about companies not properly optimizing Android for their devices. When Android [i]is[/i] properly optimized for the device, it runs just as well as, if not better than, iOS does on the iPhone.
[QUOTE=Amiga OS;39705252]It can manage all of that and yet not a responsive and fluid interface?
Laughable.[/QUOTE]
It does, actually. Thanks for asking before you assumed.
If you had actually read what I posted before, you'd understand that my point is if Firefox OS did somehow take off and end up on a large amount of devices, you would start seeing poorly optimized phones for that platform as well. Again, the problem comes when the developer doesn't optimize the operating system for their device; it doesn't matter what operating system they pick. It could be Android, Chrome OS, WebOS, Firefox OS, their own OS, anything.
[QUOTE=Amiga OS;39705252]
It can manage all of that and yet not a responsive and fluid interface?
Laughable.[/QUOTE]
My old HTC Droid Eris (528 MHz ARM 11) was very smooth. Sure it took a few tweaks and removal of HTCs bloatware, but it was a pretty great phone for its time.
In terms out out of the box performance, yeah your right iPhone dominated. The operating system wasn't to blame though, it was usually the Manufacturer and/or the carriers.
[QUOTE=Amiga OS;39705252]Nexus S 1Ghz ARMv7, 512MB of RAM, both with CM10.1 and Stock AOSP, runs like fucking shit.
ZTE Blade 600Mhz ARMv6 512MB of RAM, stock 2.2 ROM and CM7, runs like shit.
Sony Xperia Tipo 800Mhz ARMv6, 512MB of RAM, Android 4.0, runs like shit.
iPhone 1 412Mhz ARM11 chip, 128MB of RAM, runs rings around nearly every low-mid range Android phone.
[editline]25th February 2013[/editline]
It can manage all of that and yet not a responsive and fluid interface?
Laughable.[/QUOTE]
Don't understand at all why you are getting boxes for this. I hate Apple devices with a passion and would never consider buying one, but it's obvious that they have their priorities straight - native code and fast, responsive interfaces.
It is a fact that only high end devices released in the last year (or devices which have been blasted within an inch of their lives with custom roms, something no consumer should have to do) or so are capable of running Android in the same way that any iPhone can run its release version of ios.
[QUOTE=Dr. Evilcop;39705538]Except you pulled all of that out of your ass.
[url]https://www.youtube.com/watch?v=aOCletx2OJU[/url]
[url]https://www.youtube.com/watch?v=-zmXXGIFSHc[/url]
[url]http://www.youtube.com/watch?v=lVbwFkIPJ5M[/url]
All three of those phones are capable of fluently running 3D applications. It is true that iOS gets better performance for the specs than some of these phones, but that goes back to what I said before about companies not properly optimizing Android for their devices. When Android [i]is[/i] properly optimized for the device, it runs just as well as, if not better than, iOS does on the iPhone.[/QUOTE]
There's no question that Android when fully optimised for a device (even phones such as my 'ancient' galaxy s) can run at 60fps. And there's also no question that any Android device with adequate CPU/GPU power can run a 3D game smoothly, mostly regardless of the state of the underlying OS.
The problem lies in starting applications, and enjoying a wonderful black screen for several seconds despite a smooth 60fps animation leading into said black screen. Or switching between two applications and literally praying that the other has not been terminated due to RAM constraints while backgrounded, forcing you to re-find your place.
And google just ignore the main problem and instead focus on smoothness - often at the expense of touch responsiveness or correctness. The amount of times I've mistapped due to what I would imagine is a massive CPU spike is crazy. Similarly when performing a background task such as music playback or polling for emails, things will very often go batshit insane and start clicking all over the place, or just freeze for several seconds.
It's taken until now for anyone to even bother trying to fix these problems: [url]https://play.google.com/store/apps/details?id=com.lcis.seeder&hl=en[/url] - And it doesn't even make much difference.
[QUOTE=Darkimmortal;39710443]The problem lies in starting applications, and enjoying a wonderful black screen for several seconds despite a smooth 60fps animation leading into said black screen.[/QUOTE]
I've never had an issue with that, and honestly it sounds like a minor inconvenience.
[QUOTE=Darkimmortal;39710443]Or switching between two applications and literally praying that the other has not been terminated due to RAM constraints while backgrounded, forcing you to re-find your place.[/QUOTE]
That's completely intentional and necessary for a limited-RAM device like a phone to support multi-tasking. Android, unlike iOS, lets you keep these apps open in the background - that's a double edge sword in that although you don't have to restart these apps each time, the open apps take up RAM that could be used elsewhere. To circumvent this, Android will eliminate the oldest/least used process from RAM if it's needed elsewhere. If it didn't, you would be constantly running out of memory and having to manually clear apps from the recent apps list (something many users don't think to do). It's better that it's done automatically, and since it eliminates the oldest app, many users don't even notice.
If you don't like that, Android also supports not keeping recent apps. Or, manually clear apps from the recent apps lists if you don't want to lose your place in other apps.
[QUOTE=Darkimmortal;39710443]And google just ignore the main problem and instead focus on smoothness - often at the expense of touch responsiveness or correctness. The amount of times I've mistapped due to what I would imagine is a massive CPU spike is crazy. Similarly when performing a background task such as music playback or polling for emails, things will very often go batshit insane and start clicking all over the place, or just freeze for several seconds.[/QUOTE]
I've never had a problem with this on any of the devices I've used. What phone are you using with what version of Android?
Sorry, you need to Log In to post a reply to this thread.