News Forum Phone database

> New Topic
> Reply
< Esato Forum Index > General discussions > General > Do we really need Quad core phones? Bookmark topic

Currently... We need more efficient coding more than we need 4 cores. We need better battery tech more than we need 4 cores.
--
Posted: 2012-01-21 06:54:32
Edit : Quote


Yeah I was always thinking that too. Battery life is still a major hurdle.
--
Posted: 2012-01-21 12:15:00
Edit : Quote




interesting comment about more efficient coding, and as a developer myself I'm curious if you have access to android/iOS/Windows mobile sources that brings you to this conclusion?

I'm not familar with android SDK but the iOS SDK makes coding VERY efficient unless you are a stupidly bad programmer that goes out of their way to write bad code.

In regards to batteries, thats always the case but in my experience, multiple cores generally bring better battery life.
--
Posted: 2012-01-21 12:28:03
Edit : Quote


Well an example of bad programming was actually a case in the Nokia Lumia recently but has been resolved. The battery life was quite poor due to apps were not getting the full capacity from the battery. Nokia released the update the other day and now battery life is a million times better. Its excellent now.
--
Posted: 2012-01-21 14:44:00
Edit : Quote


ah, so this was meant at operating system level rather than app level.

There is certainly more opportunity for bugs at that level, and indeed many iOS upgrades include fixes to the API's and lower levels, I'll grant you that.

I'm a firm believer in Moore's law and believe we'll need quad core, and more, as our device needs and speed requirements increase. eventually we won't be counting cores as I believe its largely a marketing thing. we'll have some other standard by which to compare processors.
--
Posted: 2012-01-21 14:59:06
Edit : Quote




Masseur, it's mostly behavioral differences between iOS and Android. There was an article written by one of the early Android devs that states that the Touchscreen UI of Android was an after thought. Which is why Android (even Gingerbread) will still lag (or even hang) compared to iOS. I never became a programmer after my programming classes in college, but I can understand the complexity of having to redo the GUI had it not been planned from day 1.

iOS makes interface and animation a priority. Most techies will see this as just "cosmetic" but this also improves consumer experience without having to resort to battery sucking quad cores. That "superficial" approach makes even 1st gen iPhones "seem" more responsive than most current Androids.

**in regards to your observation on multi-cores... yes it's supposed to be more efficient, unless an app wasn't written properly and doesn't shut down in the background...**

--
Posted: 2012-01-21 15:01:02
Edit : Quote




You mean the article Andrew Munn wrote ie. "Android Graphics true facts" - Google+ link here : http://plus.google.com/100838276097451809262/posts/VDkV9XaJRGS

This was corrected by Dianne Hackborn in a post that Andrew acknowledged as being more factually correct than his own :

Dianne's post here : http://plus.google.com/u/1/10[....]738280261832/posts/XAZ4CeVP6DC

She writes:

"One issue that has been raised is that Android doesn’t use thread priorities to reduce how much background work interrupts the user interface. This is outright wrong. It actually uses a number of priorities, which you can even find defined right here http://developer.android.com/[....]ess.html#THREAD_PRIORITY_AUDIO in the SDK.

The most important of these are the background and default priorities. User interface threads normally run at the default priority; background threads run in the background priority. Application processes that are in the background have all of their threads forced to the background priority."

*and*

"I have also seen a number of claims that the basic Android design is fundamentally flawed and archaic because it doesn’t use a rendering thread like iOS. There are certainly some advantages to how iOS work, but this view is too focused on one specific detail to be useful, and glosses over actual similarities in how they behave.

Android had a number of very different original design goals than iOS did. A key goal of Android was to provide an open application platform, using application sandboxes to create a much more secure environment that doesn’t rely on a central authority to verify that applications do what they claim. To achieve this, it uses Linux process isolation and user IDs to prevent each application from being able to access the system or other application in ways that are not controlled and secure.

This is very different from iOS’s original design constraints, which remember didn’t allow any third party applications at all."


Dianne's role in the Google Android team seems to be the final authority in how the Android framework evolves or works -I'd take her word over Andrew's.

ps. between quadcore & longer battery life , I'll take better battery life every time

--
Posted: 2012-01-21 17:07:17
Edit : Quote


Well if it reaches 1080p screens on mobile devices that's gonna not just need processing power but a bloody fat battery. Call me biased with my Nokia Lumia but it seems to me Android needs these Quad core & Dual Core's inside them. I see my Windows does everything Android or iOS can do(apart from a a few restrictions) at decent speeds & more fluid than Android. And I feel it does not need quad core & WP does not seem to have a thousand standard apps running in the background hogging everything. It's much improved from the old Windows. Android seems to suffer from lag more than any other imo
--
Posted: 2012-01-21 17:26:08
Edit : Quote


Android doesnt need dual or quad core,it needs the manufacturers to learn to optimize their SW to work well with the HW, SAMSUNG have done an excellent job of this on the GS2 and even better on the GNote, they had VERY NEARLY done that with the original GS but made a poor choice in FS and mem chip which let it down. SE also show this with the Xperia Arc S but again, poor choice in memory. I have absolutely no lag in my GS2 it runs just as fast as a 4S.
Im not suprised WP is fast, it doesnt realy multitask, and is still missing many things that Android has.
If you put a full house Range Rover against a Mini Cooper S the Mini will be faster and more nimble to drive thanks to the fact that its super lite and doesnt have as much to deal with as the Range, although its capable of higher speeds.

Most dual-core Androids are on 2.3.3, Android doesnt take advantage of the 2nd core in versions before 2.3.4 and even in 2.3.4 the 2nd core doesnt do much, ICS4.0 is where both cores are fully utilized as well as the GPU, lets see how ICS does in these skinned droids.
--
Posted: 2012-01-21 18:31:31
Edit : Quote




The human eye can't tell the difference between a 720p and 1080p on a smartphone screen!
That's the idea behind the Retina display.. Up from a certain ppi (around the 320ppi I guess) it becomes pointless to higher the screen resolution!


--
Posted: 2012-01-21 21:06:36
Edit : Quote

---

New Topic   Reply

Forum Index