What will happen to the Dream/G1 in the future? - G1 General

Honestly if i get flamed its bs but what ever.
My question is will the Dream just be ignore in the future for the basic fact that we can't update our hardware, while Google pushes out UI's like Rosie and more sophisticated one's in future. We've already noticed how much it lags with Rosie whats going to happen in 8-12 months when phones like the I7500 come to play with better hard ware and they make updates to those. Will the G1 suffer and thus be stuck on roms like CupeCake? I mean we are already seeing the limits that it can handle without to much lag.

Like any piece of hardware, it gets outdated. However as long as dev are kind enough to work on new ROMs for us, most likely there will be new additions, widgets, applications etc for us to use in the future.
I'm quite excited by the multi-core ARM-X processors coming out for mobile devices, plus more powerful GPUs (the iPhoneG S has a scaled down version of what's to come next year!) and hopefully Android can support such processors too.
For us G1 owners at the moment though you might as well enjoy it. I mean I don't believe I've owned a mobile previously where we had so much choice between ROMs and how fast development is... (*looks at Sony Ericsson with their slow P900 firmware upgrades, Nokia N95 Symbian upgrades etc*).

I think you're going to see the "base" Android experience (the Launcher, the bundled platform apps, etc) will require more or less the same level of computing power in the future as it consumes today. It's good practice to keep a consistent, maintainable standard and then build from there. So that's what you're seeing with Rosie, where 3rd parties like HTC add on these gaudy and poorly programmed interfaces. By producing these inefficient and cpu-intensive apps and interfaces, HTC can essentially nudge you to hardware upgrades.
But the core of Android, the stuff that comes out of 1600 Ampitheatre Parkway, should remain runnable on Dream for atleast a while. Google is aiming to have Android be a general purpose embedded systems operating system. In order to be flexible to all the types of devices Android can potentially run on, it has to have a relatively low baseline.

What you said. I think we'll see a longer life of the G1 than we've seen with past phones because of the degree of flexibility we have with it. Of course there are going to be things designed for better hardware that we won't be able to use, but Jashu's right. Not all hardware that comes out running android is automatically going to be better than the G1. As long as there's devs that have a G1, you'll continue to see development for it.
jashsu said:
I think you're going to see the "base" Android experience (the Launcher, the bundled platform apps, etc) will require more or less the same level of computing power in the future as it consumes today. It's good practice to keep a consistent, maintainable standard and then build from there. So that's what you're seeing with Rosie, where 3rd parties like HTC add on these gaudy and poorly programmed interfaces. By producing these inefficient and cpu-intensive apps and interfaces, HTC can essentially nudge you to hardware upgrades.
But the core of Android, the stuff that comes out of 1600 Ampitheatre Parkway, should remain runnable on Dream for atleast a while. Google is aiming to have Android be a general purpose embedded systems operating system. In order to be flexible to all the types of devices Android can potentially run on, it has to have a relatively low baseline.
Click to expand...
Click to collapse

imbonez9 said:
Honestly if i get flamed its bs but what ever.
My question is will the Dream just be ignore in the future for the basic fact that we can't update our hardware, while Google pushes out UI's like Rosie and more sophisticated one's in future. We've already noticed how much it lags with Rosie whats going to happen in 8-12 months when phones like the I7500 come to play with better hard ware and they make updates to those. Will the G1 suffer and thus be stuck on roms like CupeCake? I mean we are already seeing the limits that it can handle without to much lag.
Click to expand...
Click to collapse
Funny you should mention the i7500... it is essentially the same as the *lower spec* htc magic, i.e. the same chipset, cpu. Actually, it has *less* RAM than htc dream (128 vs 192) -- magic comes with 192 or.. 288 (depending on what the provider ordered). The main advantages are that its got more flash onboard (though it is yet to be seen if the whole flash is usable for app installation or if it is restricted to some small amount), slightly better camera with flash, and OLED capacitive touchscreen (vs TFT/LCD capacitive). In all, the lower RAM will make it perform WORSE than any of the current HTC-android devices, including the Dream.
Have a look, its not that impressive: http://www.gsmarena.com/samsung_i7500-2791.php

Related

How to improve Android GUI experience

I hope this isn't perceived as spamming or fishing for votes. I think most of us would like to see a smoother Android GUI instead of that choppyness on our 1GHz phones. I and many people believe that Google can do something about this but are not prioritizing this as they should. I think we can change this by visiting and voting here, clicking on the star under the headline, if we want to see a change: http://code.google.com/p/android/issues/detail?id=6914
Who knows, if we start voting now, maybe they will implement this feature in the next Android version.
P.S. You need a Google account to be able to vote.
EDIT: Maybe this is why we haven't seen it yet?
From what I've heard, the fault lies mostly with HTC, encouraged by wholesale indifference by the carriers. Here's the story I was told:
* Qualcomm makes the core chipset used by most HTC phones, and most Android phones were built by HTC until VERY recently. Thus, the things that got the most attention during Android's first year and a half of commercial availability were things directly supported by HTC phones.
* The price charged by Qualcomm for its chipset varies, depending upon what features the handset manufacturer chooses to license from them. Put another way, every Qualcomm chip in a given family has the silicon resources to do everything... but manufacturers are only allowed to use the features they pay Qualcomm for the right to use.
* Because the carriers don't care, and the carriers are HTC's real customers, HTC didn't care about GPU support, either. It saved a few cents per phone, and washed its hands of GPU support to boot.
* Making matters worse, Qualcomm only makes its chipset documentation available under NDA (at least, the parts dealing with "premium" capabilities), and only made it available to licensees (of which there were very, very few). Ergo, the documentation has been VERY hard to come by, and less likely to be leaked by a public-minded HTC employee for the good of humanity.
Put another way, there probably isn't a thing Qualcomm can do to stop the folks at xda-developers.com from releasing guerrilla video drivers for HTC Android phones that take advantage of acceleration if they can figure out how it works, but you'll never see a phone come out of the box new with GPU acceleration unless HTC officially licenses the capability from Qualcomm. Nor will you see Google making it easy to do an end-run around the official release to graft it on, because then Qualcomm would sue THEM.
Click to expand...
Click to collapse
- This is from: http://androidforums.com/android-news-talk/29584-why-doesnt-androids-gui-use-gpu-acceleration.html
I starred it.
Definitely is bizarre that GPU integration isn't enabled in Android 2.1+
This hardware-can-do-qualcom-wont-allow-it is old...
It happens with a LOT of devices...
Sent from my HTC Desire using XDA App
I'm glad to see that we are climbing on the chart of issues.
I have come to notice that the issue of the choppy Android experience is not only a problem because of the lack of GPU acceleration. Android phones tend to respond to our gestures way too exactly. This results in uneven transitions, one half of the animation is fast and the other half is slower. This unevenness being a result of us not making, or following through, with perfectly even movements in terms of speed. I believe this is something Apple has addressed and they did it very nicely because even though you are moving your fingers unevenly and slowly, the UI transitions follows your finger in an even and smooth fashion but in a speed that matches your finger. This looks phenomenal. Same goes for faster input gestures, the Ios (iOS) responds in an even and smooth fashion but the transition is faster.
It was the same with my old HD1, the xda gpu-drivers helped alot. Looks like we'll have to take the matter into our own hands again.
Wasn't HTC mass-sued for this a while back?
Syc said:
It was the same with my old HD1, the xda gpu-drivers helped alot. Looks like we'll have to take the matter into our own hands again.
Wasn't HTC mass-sued for this a while back?
Click to expand...
Click to collapse
Nope. There was a whole load of talk of it over the TyTn II debacle, but the only thing to ever come of that was the rather excellent XDA GPU drivers.
I hate to admit this, but if Google, or whoever it is responsible, doesn't do something about this, I'll have to look elsewhere (Iphone). It might sound crazy but it's that important to me. I mean, it's so basic. Why add mega-ultra-fiction features and all other sh*t, when you don't know how to make a smooth transition. The basic element of the GUI.
Don't get me wrong, I don't like Apple, their policy or their attitude towards the rest. However, I'm being honest about this: they care. I haven't seen one Android phone capable of delivering smooth transitions although they are more powerful than the Iphones. On the one hand you have a team utilizing the entire potential of their sh**ty phones, and on the other hand you have a team doesn't give a rats a*s about the hardware in them.
I don't know if Google is to blame or the phone manufacturers. I just don't like the idea of owning a 1 GHz CPU and an awesome GPU (Samsung Galaxy S) and not being able to use it.
Sorry to bump an old thread.
Has there been any progress on this issue?
Using spare parts and setting all the window animations and transitions to very slow has made everything "smoother" to me for all purposes of discussion. during the slow but smooth transition, my phone has time to fully load the next screen or popup menu, therefore it all appears to happen seamlessly.
android is very smooth on my Hd2 ... Did you try a cyanogen mod build ?
Sorry, i was referring more towards the GPU being actively used by the UI front end.
Im using a Legend with Azure's cyanogen mod (froyo) things are pretty slick but I can tell when there are slowdowns, but the worst offender is definately the web browser.
The best example I can find is going to the html5 test website, I get a score of around 180 and the iphone about 140, but the legend browser (built in and Dolphin) really struggles to scroll that page, whereas on the Iphone its extremely smooth. Its these kind of inconsistencies which are annoying.
Another gripe is the whole portrait-landscape switch, its not gpu based in the least and its a rather half assed solution at the minute (visually). But I understand that no app could ever interfere with how this works as its so deep in the os? Such a shame.
I work in animation which is why im overly critical

[DEBATE] Android optimisation problem

I am not Apple fanboy, but i think that Anddroid OS has a big optimisation problem.
For example the iphone 4S had a CPU 800 Mz and it seem to be real fast. But the latest Androphone plan to use Dual CPU. Is Android OS needed more ressources than iOS?
Before make effort to get more material ressources, is n't time for google to optimise his OS ?
Symbian was an OS whitch was too optimsed and i would like to have an Android OS like that.
Someones wouldnt like what i said but it is my deep think.
+1 BRO !!!!
I really dont know why the **** iOS is that smooth, never noticed any lag on an Iphone. But you should think about that : Every Phone needs his own setup, caused of CPU, GPU and other things like ram and so on....
every iPhone got the same setup, optimized for iPhone 4 , iPhone 3GS and so one. They all got the same CPU and GPU, so they really can tweak every singe hardware.
Google just give us a source code, which every Company, Like Samsung or HTC have to port on their new device...
By the way, HTC got much better optimized Original Roms than Samsung. ( I have seen some OFW running on HTC Desire, and they are very smooth... )
lascoul said:
....
Before make effort to get more material ressources, is n't time for google to optimise his OS ?
.....
Click to expand...
Click to collapse
It is same way as MS passed: one simple question to you: how would you like to optimize the OS against HUNDREDS of available hardware combinations?
Of course, the Apple choice is easy and smooth: ONE hardware set, ONE OS.
similar was already done by Ford with model T: everyone could have it with favourite colour, as long as it was black. and now the ford position on global market is...
it's easy to optimize a software for 1 device but for 10000+ devices it's not that easy
dadyal said:
it's easy to optimize a software for 1 device but for 10000+ devices it's not that easy
Click to expand...
Click to collapse
If google doesn't optimise the OS. He may do it for his phones. take a look at the future Nexus prime it will get a dual core CPU. But don't think that is necessary if the OS is much optimise. The ipohne 4S had only a CPU at 800MHZ
spamtrash said:
It is same way as MS passed: one simple question to you: how would you like to optimize the OS against HUNDREDS of available hardware combinations?
Of course, the Apple choice is easy and smooth: ONE hardware set, ONE OS.
similar was already done by Ford with model T: everyone could have it with favourite colour, as long as it was black. and now the ford position on global market is...
Click to expand...
Click to collapse
But a think that the OS is not optimise for googles phones. Otherwise why will they use a dual core CPU in Nexus Prime?
I thought the difference in speed was because of the way they handled multitasking. It was only recently that iOS even had multitasking. But this is probably just a part of the reason why iOS is faster.
lascoul said:
If google doesn't optimise the OS. He may do it for his phones. take a look at the future Nexus prime it will get a dual core CPU. But don't think that is necessary if the OS is much optimise. The ipohne 4S had only a CPU at 800MHZ
Click to expand...
Click to collapse
iPhone 4S: 1 GHz dual-core ARM Cortex-A9 processor
They both have dual-cores.
Yea ios is optimized better. But it also doesn't have many basic features like android. Like a proper customizable homescreen with the ability to chose your launcher (no, lockscreen and an app tray are NOT an homescreen like apple has been trying to sell it), widgets, proper multitask, proper application integration, live wallpapers, lack of an external SD, etc. That makes for a lightweight system. You gain speed but lose features.
That said, granted, android needs to be generic. But as soon as a big company like samsung picks up android and starts developing to one device of their own making, this "1 OS for all devices" gap ceases to exist. Its 1 OS being optimized to a single piece hardware, and they have all they need for proper optimization.
This isn't the same as windows -> 1000 kinds of hardware. Windows comes prepared from Microsoft to run everywhere so that applies. Android doesn't come prepared to run everywhere from google. You can't simply just download and put it on your phone regardless of brand. Has an extra step of preparation from hardware developing companies like HTC or Samsung.
What i'm trying to say is, there is room for optimization. But companies don't care much because they are on a tight schedule on market competition to put out the next big thing, have hardware specs to compensate for poorly optimized coding and in the end stuff works just the same, since most people, sadly, won't notice or care that much for those extra delays/lags.
Can't speak for other brands, but Samsung proved with SGS they don't care much for good coding. The community has been, since its release, improving this phone leaps and bounds and continue to do so even though a successor has shown up.
At the end, companies don't care enough, imo.
kaynpayn said:
What i'm trying to say is, there is room for optimization. But companies don't care much because they are on a tight schedule on market competition to put out the next big thing, have hardware specs to compensate for poorly optimized coding and in the end stuff works just the same, since most people, sadly, won't notice or care that much for those extra delays/lags.
Can't speak for other brands, but Samsung proved with SGS they don't care much for good coding. The community has been, since its release, improving this phone leaps and bounds and continue to do so even though a successor has shown up.
At the end, companies don't care enough, imo.
Click to expand...
Click to collapse
i am aggre with u. The compagny must provide us much optimise Room before growing the specs of the phones.
lascoul said:
I am not Apple fanboy, but i think that Anddroid OS has a big optimisation problem.
For example the iphone 4S had a CPU 800 Mz and it seem to be real fast. But the latest Androphone plan to use Dual CPU. Is Android OS needed more ressources than iOS?
Before make effort to get more material ressources, is n't time for google to optimise his OS ?
Symbian was an OS whitch was too optimsed and i would like to have an Android OS like that.
Someones wouldnt like what i said but it is my deep think.
Click to expand...
Click to collapse
Iphones are smooth because iOS was designed to work on one device (technically, 9 devices if you count all the variants of iphones, ipads and ipods) only whereas Android has to work on hundreds of devices with different processors and hardware.
Also, iOS removes so many functionalities from the user, hence has more free ram.
disclaimernotice said:
Iphones are smooth because iOS was designed to work on one device (technically, 9 devices if you count all the variants of iphones, ipads and ipods) only whereas Android has to work on hundreds of devices with different processors and hardware.
Also, iOS removes so many functionalities from the user, hence has more free ram.
Click to expand...
Click to collapse
The job of compagnies like SAMSUNG, HTC ... isn't to optimise the OS for they devices? To say that there are more devices is not an apologizes
First step then should be: CLOSE the system. Lock it all, and after that, you can optimize system individually for each phone, completely separately. Another option is to push Samsung, HTC, LG, SE or whoever else to have SAME hardware configuration.
Then: you will loose:
- all custom ROMs, bootloaders, CWM, root, kernels;
- all customized versions of stock apk's, like phone, start screens, themes, Market etc.
- ANY ROM update will be available only after OFFICIAL release, through Kies.
Well, xda does pretty good work with optimization, while Android is kept OPEN, not locked, like iOS.
I personally prefer that it will continue this way.
---------- Post added at 06:40 PM ---------- Previous post was at 06:37 PM ----------
lascoul said:
The job of compagnies like SAMSUNG, HTC ... isn't to optimise the OS for they devices? To say that there are more devices is not an apologizes
Click to expand...
Click to collapse
??? Why are you stating that they are not doing this? But, one thing: DO NOT flash everything available here, but just stay with OFFICIALLY released ROM's, via Kies (in case of SGS).
For example: JVR, JVS, JVT ROM's are not officially released, and then any claim that the sys is not optimized is pointless.
Whilst the first post is correct regarding speed and optimisations they fail to realise that Apple have only their own hardware to work on, so they can really work it until its perfectly optimised.
Google have one device to work on, but multiple manufactures use their open source platform using different hardware, so its up to them to optimise the software for their hardware, not google.
You also failed to quote correct hardware specs for the iphone, which has dual core and I believe as much memory as the galaxy s2... So it does sound like your trying to bash android with incorrectly informed arguments.
Just to close the item, and to proof how optimised the IOS is, the recent update, iOS 5, caused vanishing of the music, files, messages, contacts, customised folders and applications for not very small group of users:
Brilliant iOS5 update, example 1
Error 3200 and 3004
3002, 3200, 3194
So, I think that the conclusion may be:
Apple has much more simple way to optimise their sys, because they have much less kind of hardware than Google.
But, Apple is not able to manage even so small amount of the hardware variations, and iPhone CAN go smoothly on its 2 cores CPU (yes, dear OP, read the specs more closely) if Apple will not mess the sys or its update... what just happened.
It's only multitasking problem.suspend and resume of iOS paid off better although you miss some features because of that but on all basic features it way better.
I always wonder why dialer and messaging apps sent out of memory,they should have been kept in memory like browser.
We shouldn't be nagging much about it as things can be done by Android are much more.
Sent from my GT-I9000 using Tapatalk
I can't predict the future of course, but it is not unlikely we will see some performance increase with ICS.
I would deem it likely that ICS will use HC's memory manager which is definitely faster than GBs, especially when used with programs that are massive memory hogs. HC's still constantly frees memory it doesn't need to free though ( == waste of cycles), so there is still room for improvement there, let's hope ICS brings it.
Likewise, UI hardware acceleration is already better in HC than it was in GB, and it is rumored to be further improved in ICS. If that is true, ICS devices will likely seem much more fluent. It doesn't actually make them faster, but it will look that way.
In the end, iOS is much more optimized than Android, but ICS should be a good step in the right direction. It will probably not bring the optimization to an iOS level, though.
kaynpayn said:
Yea ios is optimized better. But it also doesn't have many basic features like android. Like a proper customizable homescreen with the ability to chose your launcher (no, lockscreen and an app tray are NOT an homescreen like apple has been trying to sell it), widgets, proper multitask, proper application integration, live wallpapers, lack of an external SD, etc. That makes for a lightweight system. You gain speed but lose features.
That said, granted, android needs to be generic. But as soon as a big company like samsung picks up android and starts developing to one device of their own making, this "1 OS for all devices" gap ceases to exist. Its 1 OS being optimized to a single piece hardware, and they have all they need for proper optimization.
This isn't the same as windows -> 1000 kinds of hardware. Windows comes prepared from Microsoft to run everywhere so that applies. Android doesn't come prepared to run everywhere from google. You can't simply just download and put it on your phone regardless of brand. Has an extra step of preparation from hardware developing companies like HTC or Samsung.
What i'm trying to say is, there is room for optimization. But companies don't care much because they are on a tight schedule on market competition to put out the next big thing, have hardware specs to compensate for poorly optimized coding and in the end stuff works just the same, since most people, sadly, won't notice or care that much for those extra delays/lags.
Can't speak for other brands, but Samsung proved with SGS they don't care much for good coding. The community has been, since its release, improving this phone leaps and bounds and continue to do so even though a successor has shown up.
At the end, companies don't care enough, imo.
Click to expand...
Click to collapse
Disable to slight extent. I felt that Samsung have done something to the ROMs they provide for SGS. Example the old RFS filesystem, lags like hell in the past but feels good now. Im using RFS instead of EXT4. Still, I have to agree, they don't care much on good coding, new phones are coming up, why bother? The community makes it happen
Apple hires a ton of CPU architects solely for this purpose. Apple prioritizes fluency and optimization above features and openness.
Just a different strategy, no better, no worse.
Sent from my GT-I9000 using xda premium
My mate has the latest iPhone his wife had the SGSII, I had the chance to compare them both side by side last night. What can I say except the SGS is larger, faster, smoother, has more apps, more customisable, the difference is amazing. The iPhone is like
a kiddies toy compared to the SGS.
Remember that the iPhone has been going a lot longer than Android, yet Android had had voice recognition for over a year. Enough said
Sent using TCP/IP

Interesting re: "full hardware accel" in ICS

Just a blog re: ICS enabling full hardware acceleration of the GUI. We've all figured it would make our tablets sprint but this is putting things in a new light so I figured I'd post it here.
Linky
I'm sure the programmers and people on top of Android out there knew this. It sort of worries me though. Keeping in mind, Apple is running a totally different system - it sort of makes me respect iOS more so, to know that such a smooth system exists within the limits of 256MB of Memory when we're going upwards of 512MB and still having 'issues'. Don't jump down my throat, I don't want iOS (or an idevice), I'm just sayin'.
Jesus. I've known for a long time that there is something wrong with the way Android accelerates stuff and the whole UI design paradigm, but that's just boneheaded o_o That begs the question though: who made the decision to implement acceleration in such a horrible way and why wasn't it designed properly from the get-go? Anyone who has the slightest experience in OpenGL programming would've been able to tell them they're doing it wrong.
What a stunningly stupid way to implement things.
Just goes to show how much difference it really makes when it comes to having experience in OS development...
I like Android, but this design choice was just... dumb.
FloatingFatMan said:
What a stunningly stupid way to implement things.
Just goes to show how much difference it really makes when it comes to having experience in development...
I like Android, but this design choice was just... dumb.
Click to expand...
Click to collapse
Well, there are several shortcomings to Android exactly because of these kinds of brainfarts, like e.g. the permissions system is terribly sketchy and should've received a lot more Q/A. But now that it's released there's little Google can do about it without breaking compatibility as they didn't even plan for it to be extendable.
I do quite like Android, but it's too uneven to really feel professional or trustworthy. I just recently pondered about what I'd want from a future mobile tablet on my Google+ page and while I didn't mention it there, I feel like Win8 would've been in a terrific position for the OS on such a device if they didn't decide to remove traditional desktop from the ARM-version. I know Windows and Microsoft aren't popular here, but they've got a lot more experience with OS-development than Google and are a lot better at power-management design and acceleration of UI and its drivers, plus they've really put some real effort into security lately. Alas, with them scrapping traditional desktop from ARM-version Win8 won't cut it, either.
You guys should read Google's blog post. That article misses one huge point: the trade off. This was far from a bad implementation, it was just a very different one. If you read the article you would know that ios freezes if you hold your finger on screen while loading a large list, Android does not. Android balances the CPU threads for ui display and data processing somewhat equally, while ios grants utter priority to their ui display thread . Basically, if the ui display thread is busy, data processing stops. Android is the winner, it is ios that will now be limited in speed with this configuration until it is optimized for new hardware much like how Android currently works!
autom8r said:
You guys should read Google's blog post. That article misses one huge point: the trade off. This was far from a bad implementation, it was just a very different one. If you read the article you would know that ios freezes if you hold your finger on screen while loading a large list, Android does not. Android balances the CPU threads for ui display and data processing somewhat equally, while ios grants utter priority to their ui display thread . Basically, if the ui display thread is busy, data processing stops. Android is the winner, it is ios that will now be limited in speed with this configuration until it is optimized for new hardware much like how Android currently works!
Click to expand...
Click to collapse
Uh, it is a bad implementation. You can have both a good implementation AND still balance priority of both the rendering queue and application threads, they are not mutually exclusive.
WereCatf said:
Well, there are several shortcomings to Android exactly because of these kinds of brainfarts, like e.g. the permissions system is terribly sketchy and should've received a lot more Q/A. But now that it's released there's little Google can do about it without breaking compatibility as they didn't even plan for it to be extendable.
I do quite like Android, but it's too uneven to really feel professional or trustworthy. I just recently pondered about what I'd want from a future mobile tablet on my Google+ page and while I didn't mention it there, I feel like Win8 would've been in a terrific position for the OS on such a device if they didn't decide to remove traditional desktop from the ARM-version. I know Windows and Microsoft aren't popular here, but they've got a lot more experience with OS-development than Google and are a lot better at power-management design and acceleration of UI and its drivers, plus they've really put some real effort into security lately. Alas, with them scrapping traditional desktop from ARM-version Win8 won't cut it, either.
Click to expand...
Click to collapse
If Microsoft is dumb enough to kill desktop mode on ARM, that really destroys the Win8 tablet market outside of running on Intel chips, which puts them at sub-par graphics. I suppose the only hope then is if AMD steps in and I'm not all that much a fan of AMD, though they have tried to make good efforts in the mobile arena with their A-series chips and having decent GPUs.
I suppose I'll keep an eye on this and see what Microsoft does. Given their lack of intelligent decision making of late (ie. far dumber than their normal stupidity), I don't hold out much hope. Pity, Win8 tablets were looking strong, too.
Gnoop said:
If Microsoft is dumb enough to kill desktop mode on ARM, that really destroys the Win8 tablet market outside of running on Intel chips, which puts them at sub-par graphics. I suppose the only hope then is if AMD steps in and I'm not all that much a fan of AMD, though they have tried to make good efforts in the mobile arena with their A-series chips and having decent GPUs.
I suppose I'll keep an eye on this and see what Microsoft does. Given their lack of intelligent decision making of late (ie. far dumber than their normal stupidity), I don't hold out much hope. Pity, Win8 tablets were looking strong, too.
Click to expand...
Click to collapse
The Metro-interface is aimed for touch-based devices, including tablets. Desktop-mode doesn't work too well on such. The problem is that Win8 tablet could serve as BOTH a mobile device AND a desktop computer if Microsoft played its cards right and thus reserve a very nice spot for itself.
WereCatf said:
The Metro-interface is aimed for touch-based devices, including tablets. Desktop-mode doesn't work too well on such. The problem is that Win8 tablet could serve as BOTH a mobile device AND a desktop computer if Microsoft played its cards right and thus reserve a very nice spot for itself.
Click to expand...
Click to collapse
Indeed. Being able to handle both of those would hook me in pretty easily.

Reactivity : Galaxy Note -VS- iPhone 4

View the thread : http://forum.xda-developers.com/showthread.php?t=1400110
edit : link removed
Not true and ive posten respons in the original thread.
Yes, is TRUE
So says you.
that's what I say, but it is mostly what you hear with your ears and see with your eyes : http://forum.xda-developers.com/showthread.php?t=1400110
It's an issue with Android's sound system. More info here: code.google.com/p/android/issues/detail?id=3434
From the video, it appears that this relates to a particular app (mini piano), so in that case, I'm not sure why it's Google's responsibility to improve the responsiveness of a third party piece of software.
That said, there are some very basic reasons for why iOS will invariably be smoother and more responsive than Android almost 100% of the time.
Put simply, iOS and Android both began their respective development at totally different times. Android started development during a time when the market was saturated with keyboard-centric devices like Blackberry's and such. There wasn't a whole lot of touch-screen proliferation, and even then, those devices with touch screens were still very proprietary and basically none of them offered multi-touch. As such, Android was never originally designed for multi-touch screens; that kind of functionality is more of an evolutionary adaptation than anything else really. Android's core design principles focus on multi-tasking and cloud service connectivity in order to maximize productivity. That's why Android has always more effortlessly been good at both of those things.
iOS on the other hand was designed from ground up to be used on a multi-touch user interface. As such, iOS products have been more focused on being UI-centric, while other functions take a lower priority. Basically, when the user interacts with the screen of an iOS device, the system will drop everything it's doing (if need be) just to make sure that the UI runs smoothly. For example, say you try to interact with a webpage as it's loading on an iOS device. The device will actually stop loading the page, as long as you are touching the device to interact with it. As soon as you're no longer touching it, the page will continue to load. This is also why multi-tasking was more of an afterthought than a core principle with iOS. Apple could have easily implemented some form of multi-tasking right with their first iPhone, but considering the resource limitations at the time, that would have come at the cost of an interface that wouldn't have been as smooth or responsive.
So, to sum up:
Generally speaking, iOS will almost ALWAYS have a smoother and more responsive touch interface than Android has (unless Google basically rebuilds Android for touch screens from ground up).
That said, Android will almost ALWAYS be a better at multi-tasking and integrating cloud services than iOS (unless Apple decides to basically rebuild iOS from ground up with a bigger focus on those services).
Which is better than the other? Well, that's up to you really; it's totally subjective. If you want a simple to use UI which is smooth and responsive, then maybe iOS is better suited for you. If a more diverse ecosystem with endless customization options and very powerful multi-tasking beasts are important enough that you can accept a reasonable cost in the UI smoothness, then Android is your best bet.
Jade Eyed Wolf said:
From the video, it appears that this relates to a particular app (mini piano), so in that case, I'm not sure why it's Google's responsibility to improve the responsiveness of a third party piece of software.
That said, there are some very basic reasons for why iOS will invariably be smoother and more responsive than Android almost 100% of the time.
Put simply, iOS and Android both began their respective development at totally different times. Android started development during a time when the market was saturated with keyboard-centric devices like Blackberry's and such. There wasn't a whole lot of touch-screen proliferation, and even then, those devices with touch screens were still very proprietary and basically none of them offered multi-touch. As such, Android was never originally designed for multi-touch screens; that kind of functionality is more of an evolutionary adaptation than anything else really. Android's core design principles focus on multi-tasking and cloud service connectivity in order to maximize productivity. That's why Android has always more effortlessly been good at both of those things.
iOS on the other hand was designed from ground up to be used on a multi-touch user interface. As such, iOS products have been more focused on being UI-centric, while other functions take a lower priority. Basically, when the user interacts with the screen of an iOS device, the system will drop everything it's doing (if need be) just to make sure that the UI runs smoothly. For example, say you try to interact with a webpage as it's loading on an iOS device. The device will actually stop loading the page, as long as you are touching the device to interact with it. As soon as you're no longer touching it, the page will continue to load. This is also why multi-tasking was more of an afterthought than a core principle with iOS. Apple could have easily implemented some form of multi-tasking right with their first iPhone, but considering the resource limitations at the time, that would have come at the cost of an interface that wouldn't have been as smooth or responsive.
So, to sum up:
Generally speaking, iOS will almost ALWAYS have a smoother and more responsive touch interface than Android has (unless Google basically rebuilds Android for touch screens from ground up).
That said, Android will almost ALWAYS be a better at multi-tasking and integrating cloud services than iOS (unless Apple decides to basically rebuild iOS from ground up with a bigger focus on those services).
Which is better than the other? Well, that's up to you really; it's totally subjective. If you want a simple to use UI which is smooth and responsive, then maybe iOS is better suited for you. If a more diverse ecosystem with endless customization options and very powerful multi-tasking beasts are important enough that you can accept a reasonable cost in the UI smoothness, then Android is your best bet.
Click to expand...
Click to collapse
Dont forget to give credits to Andrew Munn as the source of your "reply"
which can be found here:
https://plus.google.com/100838276097451809262/posts/VDkV9XaJRGS
Also its not true that when you touch the screen on an iOS device every thing stops, at least not on my experience.. the page still continues to load, installation still continues and things still run in the background, simply put iOS has a better frame work for keeping 60fps on the UI at any given time, nothing is stopped or placed in real time as per several replies on that article.
I actually didn't know about this article. Thanks! Most of what I know comes from my Apple Fanboy friend, so we banter a lot. Maybe he read that article
There are still room for improvement for the touch interface. Hope it gets better on ICS update.
Jade Eyed Wolf said:
I actually didn't know about this article. Thanks! Most of what I know comes from my Apple Fanboy friend, so we banter a lot. Maybe he read that article
Click to expand...
Click to collapse
It just so happens your words are exactly as the same on the article, massive coincidence eh?
I think the problem does not come from the music software. This is a problem with Android. There are very large application vendors musical (korg, IK, etc ...) that have failed them porting iOS> Android OS as this has a level of latency too high for the "Touch games."
In searching I found very interesting articles about it and even a letter to Google:
http://www.musiquetactile.fr/android-is-far-behind-ios/
http://www.musiquetactile.fr/more-thoughts-on-audio-latency-in-android/
http://www.musiquetactile.fr/open-letter-to-google-improve-android-for-music/
Of course this relates to audio latency, but Android also suffers from a general latency. the touch of a AndroPhone is less reactive than an iPhone. This is the only thing I blame my rating Galaxy.

Windows Phone 8 and What it Means to the Competition

The Write Up
Windows Phone 8 has now been out about two weeks and with its eye-catching hardware, beautiful UI, and plethora of new features; has captured the hearts of more people than even I expected. Nokia's Lumia line has been consistently sold out all over the world and is still in high demand while HTC is certainly pulling out all of the stops in bringing their most beautiful device to date into the Windows Phone market. Huaweii seems to be ready to innovate for the first time in quite some time and Samsung is bringing up the rear with the same ol' stuff they've been putting out since the Samsung Behold days but there's a market for everything.
As a student developer, I try to keep a very clear mind about phones as a whole. At present I own a Tegra HTC One X, an AT&T Galaxy Note II, an iPhone 4s, and the AT&T Nokia Lumia 920. It could simply be a honeymoon period but for the past two weeks the Lumia has been my daily driver. I have also been frequenting the forums of numerous tech blogs and news articles, scouring the web for any complaints and praise for both the Note and the Lumia. As it stands, the Lumia seems to be the more sought after of the two with the Note being slightly underwhelming compared to its predecessor. The Lumia is not without its flaws though, the battery life has been subpar on a number of the devices, there is a bug in the NFC usage that causes immense battery drain, and the photos could be slightly sharper. However, for every shortcoming, most of which Nokia says will be repaired with a software update, there are more than enough selling points to justify it. After two weeks, I finally felt it was just to do a review comparing Windows Phone, iOS, and Android.
User Interface
First, I'll start with what you see upon powering on, the UI. The common complaint with Windows Phone, is the lack of a dedicated notification center like the ones you would see on Android or now, iOS. I was truly concerned on coming from using the One X as my daily driver and HTC's amazing Friendstream that the Lumia's activity simply would not be enough. Let me be the first to tell you that not only does the live tile system work, it's removed so many swypes and taps from my typical use that I'm probably saving an hour of battery life a day on that alone. Unlock the screen, swype down, check anything I want, done. It's very simple and very straightforward. I believe Windows Phone's initial marketing statement was, "Get in, get out, get on with your life." It's simple to do just that however it's also easy to get immersed in the live tiles. The customization available despite the lack of backgrounds is quite amazing and sometimes I'll spend half an hour deciding on a particular tile layout that suits me and my present color scheme. The OS is simply aesthetically pleasing, plain and simple. You might be able to download a dozen apps to kick your android UI into gear or Dreamboard your phone but in terms of usability I would have to give the cake to Windows Phone. That said, Android's notification system is right on par with Windows Phone and is certainly no slacker. iOS simply lags behind.
User Interface:
Android: 6
iOS: 7
Windows Phone: 9
Notifications:
Android: 9
iOS: 4
Windows Phone: 8
Camera
With our phones being an extension of our arms, it's only viable that it replace that big clunky camera on a laniard that we were once forced to tote around if we wanted to capture the moment. Now, it's as easy as pulling your phone out and snapping a picture. Windows Phone tried simplifying this further by allowing access to the camera directly from a sleeping phone, a feature imitated and executed well by the competition but born of Windows Phone and the original still seems to execute it best. Each OS aside from iOS has a variation of cameras on a variation of different phones and each have their strengths and weaknesses. My personal preference, hardware aside, is Windows Phone strictly because of the requirement of a hardware camera button. Each OS has it's own photo editing options as well, iOS being the birthing place of instagram, a photo-social network. Android having a ton of applications with filters and editors, and at least Nokia's Windows Phones implementing lenses with work amazingly well. If you haven't gotten to toy around with cinemagraphs then you simply haven't gotten to enjoy a camera on a phone. Overall, I'd say it's safe to give tens across the board on software alone as the hardware preference is just that, a preference.
Camera
Android: 10
iOS: 10
Windows Phone: 10
Hardware Choices
Your general consumer has an idea of what they want but will not be particularly picky. It has to be eye-catching but practical, it has to have screen real-estate but be pocketable. Your phone has to fit you better than you fit it. iOS in this area, is awful. You get one device that most recently has rendered a lot of games ugly due to the screen's aspect ratio shifting drastically. Overall, the iPhone 5 may be the worst in the series despite slightly improved hardware. Android of course has the broadest range of specs, 600 mhz processors making up the low-end of the spectrum and pushing into the quad-core monsters at the higher end. Until Android's most recent iteration, it suffered from a discernible lag that, while not a deal breaker, certainly offered a bit of a low-end feel. However, android is now about up to par with the competition and is finally, "Buttery smooth." on all different kinds of hardware.
Windows Phone devices are also found on a variety of hardware, however what sets it apart and really makes it pull ahead is the availability of many color options. No other OS before it has offered such an array of high end devices in such a wide variety of colors. The Lumia 920 alone comes in five different colors, 3 of which are rare to find on any other quality device. Due to the color variations, I'd have to give this one to Windows Phone as it's proven time and again that it doesn't need the ridiculous hardware to run as fluid as the competition.
Hardware
Android: 9
iOS: 2
Windows Phone: 10
Social
What are our phones for if not communication? Sure, they all make calls with varying quality, they all connect to Facebook, they all send texts and picture messages, they all get the job done. However, who gets it done best? For this comparison, I'm using stock Android. Had I chosen to use HTC's Sense then it likely would've been more favorable for Android but, spoiler alert, stock android doesn't fare too well.
iOS basicaly reinvented the smartphone and have thus created an immeasurable ecosystem spanning across millions of users. Due to this, they are able to have their own video chat that doesn't work with other devices, their own messenger client that only works on their devices, even their own social networks of sorts. They have an ecosystem, but what about the rest of us? Both iOS and Android sync your facebook contacts as well as contacts from other email clients and social networks without much fail and with the installation of third party applications have no issue notifying you of your facebook notifications. However, this isn't about the applications, just the OS itself and aside from what's mentioned, neither have a whole lot to offer. With Windows Phone, I have felt no need to install a facebook application as everything I need is built into the OS. I have facebook chat that sends me all my messages through the same messaging system that my texts come through, I can update my status from my Me tile on a number of different social networks simutaneously, I can take a picture and have it on facebook faster than any other OS, shown clearly in the Smoked by Windows Phone videos and I can do it all without installing anything additional. Facebook, Twitter, and LinkedIn being baked into the OS has accelerated my social networking to a whole new degree.
The most important aspect of a social network though, the keyboard. I mean sure you can Speech to Text everything but that seldom works out as well as you want it to. android has an excellent keyboard layout by default but the response time on it is notably slower than either other and the predicted text never quite gets me to where I want. It seems as though it doesn't know higher English and any bigger words I use are quickly transformed into two or more little words. iOS is again, a joke. The keyboard layout forces you to go to a separate page to use a period, the auto-correct has spawned numerous sites about how terrible it is, and it's very ill responsive. The first thing you notice about using a Windows Phone is the tactile responsiveness, it seems as though the button is hit maybe even a millisecond before you touch the screen it's so fast and the words are only corrected when it's actually needed. Overall, in terms of the general social networking, I have to give it to Windows Phone here as everything is so deliciously baked in. I should mention though that Android has a plethora of keyboards better than the default at your disposal.
Networking
Android: 5
iOS: 6
Windows Phone: 10
Keyboard
Android: 6
iOS: 4
Windows Phone: 8
Apps and Software and Features, Oh My!
Well, it's not all rainbows and butterflies in the Windows Phone world. The application store isn't 1/10th of the competition yet and the games we do get are often crippled versions of their Android and iOS counterparts. Not only that, we often pay more strictly for the fact that we can get Xbox Live gamer points. However, Xbox live on the phone is amazing and a selling point in itself, it still doesn't justify the sometimes ridiculous price of our games and apps.
iOS is the clear winner as far as games and apps go. Sure, Android has more games and applications but they are never as polished as those on iOS and oftentimes won't work on a good portion of the devices due to fragmentation. Both trump Windows Phone with their high def, 3D games and form fitting applications.
Android and Windows Phone now utilize NFC, iOS's only real shortcoming in this area. Windows Phone has pushed it a step further offering wireless charging on most of their higher end devices which, while gimmicky, is one hell of a gimmick. If you pick up the JBL Charging Speakers then your Nokia will absolutely blow you away.
I would like to clarify, of the 40 or so apps that are must haves on my phones, I can easily find an alternative to 36-38 of them on Windows Phone but those 2-4 apps I can't find really do seem to jump out at me a lot of the time and are a thorn in the side of WP8. That said, with access to native code this will hopefully change.
Goodies
Android: 8
iOS: 9
Windows Phone: 5
Wrap-up
Well, after owning my first long term Windows Phone device I can say that this is as unbiased as I can get aside from a possible honeymoon phase with this pretty little device. This is of course from a basic user standpoint and not a developer standpoint as so many of us like to brag about having. The final score tallied up is:
Android: 53/70
iOS: 42/70
Windows Phone: 60/70
None of the OS's are bad and each could certainly suit you and will vary with your needs. As far as the most generic needs go, Windows Phone pulled out just ahead of Android with iOS trailing behind, left in the dust. If you haven't picked up a Windows Phone and have only gone off of the rumors, I suggest you at least give it a try. Thank you for reading and I hope you all have a happy Turkey Day.
-Poecifer
Thanks for sharing! One thing that interests me about the Windows Phone is editing Microsoft Office files on the go. Currently I have many formatting and compatibility issues trying to do this with my Android device. Have you experimented much with this yet?
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
buffjam9011 said:
Thanks for sharing! One thing that interests me about the Windows Phone is editing Microsoft Office files on the go. Currently I have many formatting and compatibility issues trying to do this with my Android device. Have you experimented much with this yet?
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
Mainly just wordpad documents, I'll look more into the others and get back to you afterwards. Word files are epic though.
Strangely enough I agree with almost quite everything you say, but your scoring seems to be a little wonky. Your user interface scores were as follows:
Android: 6
iOS: 7
Windows Phone: 9
Very subjective if you ask me. You could ask ten different people what they believe that order should proceed in, and I'm willing to bet their answers will vary greatly. I don't understand how IOS could possibly have a higher interface score than Android if its simply a grid of icons with a horrendous notification system. If you wanted to replicate that on Android you very well could with a launcher, MIUI, etc. Android essentially IS iOS with flexibility; customizable grids on the homescreen, widgets, more intuitive lockscreens, etc. Giving iOS a higher score doesn't seem to make sense to me.
Hardware
Android: 9
iOS: 2
Windows Phone: 10
I'd like to think the massive range of Android phones would overcome the simple fact that Windows phones come in several new colors. I think it's fair to say Android should hold top dog in this regard.
Android: 5
iOS: 6
Windows Phone: 10
Above are the scores for social networking on each mobile OS. Again, if Android by default has every third party application installed automatically integrated, how can you justify giving it not only that low of a score, but below iOS? (While iOS only has facebook/twitter integration).
Also, I'm curious as to which keyboard you used for Android.
But great write up, honestly I don't mean to try and dismantle everything you said, I just don't entirely agree with the scoring. But good work, I gave ya a thanks )
MultiLockOn said:
Strangely enough I agree with almost quite everything you say, but your scoring seems to be a little wonky. Your user interface scores were as follows:
Android: 6
iOS: 7
Windows Phone: 9
Very subjective if you ask me. You could ask ten different people what they believe that order should proceed in, and I'm willing to bet their answers will vary greatly. I don't understand how IOS could possibly have a higher interface score than Android if its simply a grid of icons with a horrendous notification system. If you wanted to replicate that on Android you very well could with a launcher, MIUI, etc. Android essentially IS iOS with flexibility; customizable grids on the homescreen, widgets, more intuitive lockscreens, etc. Giving iOS a higher score doesn't seem to make sense to me.
Hardware
Android: 9
iOS: 2
Windows Phone: 10
I'd like to think the massive range of Android phones would overcome the simple fact that Windows phones come in several new colors. I think it's fair to say Android should hold top dog in this regard.
Android: 5
iOS: 6
Windows Phone: 10
Above are the scores for social networking on each mobile OS. Again, if Android by default has every third party application installed automatically integrated, how can you justify giving it not only that low of a score, but below iOS? (While iOS only has facebook/twitter integration).
Also, I'm curious as to which keyboard you used for Android.
But great write up, honestly I don't mean to try and dismantle everything you said, I just don't entirely agree with the scoring. But good work, I gave ya a thanks )
Click to expand...
Click to collapse
Not a problem at all, friend. I love criticism regardless and constructive is my favorite flavor. I gave UI to iOS over android because I'm trying to use vanilla android opposed to sense or touchwiz and sadly it still suffers from minute hickups. Had I been reviewing Sense, android and Windows Phone would have certainly been neck and neck.
As far as my hardware statement, as much as the hardware for android differentiates under the hood, they do little to differentiate themselves cosmetically and that seldom makes for a beautiful device even when the power under the hood is insane. It's often left looking like a bunch of generic Samsung phones.
In social networking, I ignored the existence of third party applications and only gave the bonus point to iOS for the ease of setup as both are essentially the same in that regard.
When I use android, I've been using swype since the HTC Dream days and don't feel a need to switch. Swiftkey isn't terrible though.
Again, there may be some bias as I'm still in the honeymoon phase but I made an attempt to be unbiased that at least beats out what you'll get at cNet.
Poecifer said:
Not a problem at all, friend. I love criticism regardless and constructive is my favorite flavor. I gave UI to iOS over android because I'm trying to use vanilla android opposed to sense or touchwiz and sadly it still suffers from minute hickups. Had I been reviewing Sense, android and Windows Phone would have certainly been neck and neck.
As far as my hardware statement, as much as the hardware for android differentiates under the hood, they do little to differentiate themselves cosmetically and that seldom makes for a beautiful device even when the power under the hood is insane. It's often left looking like a bunch of generic Samsung phones.
In social networking, I ignored the existence of third party applications and only gave the bonus point to iOS for the ease of setup as both are essentially the same in that regard.
When I use android, I've been using swype since the HTC Dream days and don't feel a need to switch. Swiftkey isn't terrible though.
Again, there may be some bias as I'm still in the honeymoon phase but I made an attempt to be unbiased that at least beats out what you'll get at cNet.
Click to expand...
Click to collapse
Most definitely ahaha, cnet is one of the most Apple centric tech sites I've ever seen. And I really do appreciate this write up, I always told myself if I had to move to a locked down OS Windows 8 looked like a viable choice, and now it seems I have a third party to back it up reasonably. It's sad really, most people glance at Windows phone and ate immediately turned away because of how strange the ui is initially. I think it's a beautiful design personally, and they're innovating in their own way.
One thing however. Do you really find sense more appealing then stock android? I've found the last three versions on android (4.0 - 4.2) to be wonderful. Honestly, everything from the notification bar to gapps with the blue tint looks great. I always thought sense was overrated, but more now than ever it seems to be riding on the tailcoat of its gb days. Maybe then I might've thought it sleek and edgy but lately sense hasn't seem to have changed at all, it looks dated. Everything from the app drawer to the notification panel is rather stale looking, I'd go as far to say that the touchwiz nature ux is much preferable, but that's just me.
Sent from my SPH-D710 using xda app-developers app
MultiLockOn said:
Most definitely ahaha, cnet is one of the most Apple centric tech sites I've ever seen. And I really do appreciate this write up, I always told myself if I had to move to a locked down OS Windows 8 looked like a viable choice, and now it seems I have a third party to back it up reasonably. It's sad really, most people glance at Windows phone and ate immediately turned away because of how strange the ui is initially. I think it's a beautiful design personally, and they're innovating in their own way.
One thing however. Do you really find sense more appealing then stock android? I've found the last three versions on android (4.0 - 4.2) to be wonderful. Honestly, everything from the notification bar to gapps with the blue tint looks great. I always thought sense was overrated, but more now than ever it seems to be riding on the tailcoat of its gb days. Maybe then I might've thought it sleek and edgy but lately sense hasn't seem to have changed at all, it looks dated. Everything from the app drawer to the notification panel is rather stale looking, I'd go as far to say that the touchwiz nature ux is much preferable, but that's just me.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
From a purely aesthetic perspective, I completely agree. Sense looks stale. However, it brings to the table a plethora of built in apps and widgets that I find more useful than anyone else's offerings and for that I will choose Sense over Touchwiz or stock any day. I liked the way Sony was going, too bad they can't quite get their software right.
I think you overreacted when you said iphone has score 2 as far as hardware is concerned. Just because they do not take the route android does (make up for poor software with overkill hardware) doesn't mean their hardware ain't good. They basically do just like Windows Phone: pick up a nice platform, then base everything on that so it can be optimized.
mcosmin222 said:
I think you overreacted when you said iphone has score 2 as far as hardware is concerned. Just because they do not take the route android does (make up for poor software with overkill hardware) doesn't mean their hardware ain't good. They basically do just like Windows Phone: pick up a nice platform, then base everything on that so it can be optimized.
Click to expand...
Click to collapse
They still only release one device a year with severely dated hardware and ridiculous fragility. They often have next to no real selling point aside from habit. I'd say it was justified.
dont agree with you about the keyboard. check out swiftkey.... i miss it so hard on wp8 :S
Love the write up, and I agree with most of what was said. I can support the lower hardware score for iOS because it is a gradual improvement of an existing design, as opposed to every year the hardware is cutting edge. That does have something to do with the fact that the OS doesn't require such boundary pushing hardware...
That's why I gave up on iOS. After a while you really get tired of the apps as the only attraction. Heck, jail breaking took off merely for the fact that it was a way to unlock the phone for usage on other carriers. Based on the hardware limitations, once you started to add the custom add-ons to change the looks and performance of the phone, iOS starts to lag. I'm sure things have improved with the iPhone 5, but I've got no interest in trying Apple.
It still boils down to taste. I do enjoy using WP7, and so far WP8 is a nice upgrade. As far as Android goes, I prefer stock over any other skin other there. Yes, stock used to be atrocious and not as friendly visually, but 4.0 has changed much of that. Still, I like Sense as the best skin out there, even though it has gotten bloated. sense 4 is a right step, but I won't use anything HTC Android wise until Sense gets much lighter (that's why my Galaxy Nexus will back up my Lumia 810 for the foreseeable future).
I like the WP idea of letting some customization in the form of apps and amps and hardware tweaks. But the consistent UI is my biggest draw to the platform. Now, if only MSFT can make Windowsphone.com easier to use and add a few more apps and tweaks...
Sent from my Galaxy Nexus using xda premium
Poecifer said:
They still only release one device a year with severely dated hardware and ridiculous fragility. They often have next to no real selling point aside from habit. I'd say it was justified.
Click to expand...
Click to collapse
You're not talking about Apple are you? If so, this just ruins everything you typed Severely dated hardware? Seriously ?
Don't get me wrong, everyone is entitled to their opinion; but dated hardware? ?
Sent from my iPhone using Tapatalk
vetvito said:
You're not talking about Apple are you? If so, this just ruins everything you typed Severely dated hardware? Seriously ?
Don't get me wrong, everyone is entitled to their opinion; but dated hardware? ?
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
1.3 GHz processor, underwhelming screen, no NFC, no wireless charging, nothing that sets them apart hardware-wise. At what point as of late have they innovated?
Poecifer said:
1.3 GHz processor, underwhelming screen, no NFC, no wireless charging, nothing that sets them apart hardware-wise. At what point as of late have they innovated?
Click to expand...
Click to collapse
You said severely dated hardware, didn't you? Name one phone that beats the iPhone 5 in graphics and performance? Underwhelming screen? Do people even legitimately know what the iPhone is clocked at?
NFC? Seriously, what is windows phone doing with it now besides pairing speakers?
Wireless charging, now thats palm pre innovation. Wow.
I know you can come with something better than that.
Sent from my iPhone using Tapatalk
vetvito said:
You said severely dated hardware, didn't you? Name one phone that beats the iPhone 5 in graphics and performance? Underwhelming screen? Do people even legitimately know what the iPhone is clocked at?
NFC? Seriously, what is windows phone doing with it now besides pairing speakers?
Wireless charging, now thats palm pre innovation. Wow.
I know you can come with something better than that.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Graphics is a matter of the software and developer interest, neither of which have been called into question. The screen was cool when it was introduced 2-3 years ago, now it's certainly not top tier. The iPhone 5 is clocked at 1.3 GHz which does prove we don't need ridiculous specs with optimized software. It simply hasn't been top of the line in a long while.
^ but no other chip is beating the iPhone 5 in graphics or performance right now. Not even the S4 Pro(quad core). If that isn't top of the line, then I don't know what is.
Sent from my iPhone using Tapatalk
Poecifer said:
Graphics is a matter of the software and developer interest, neither of which have been called into question. The screen was cool when it was introduced 2-3 years ago, now it's certainly not top tier. The iPhone 5 is clocked at 1.3 GHz which does prove we don't need ridiculous specs with optimized software. It simply hasn't been top of the line in a long while.
Click to expand...
Click to collapse
Genuine question, where do you find a graphics test that ignores the OS software as a whole? I want to know for personal testing.
Poecifer said:
Genuine question, where do you find a graphics test that ignores the OS software as a whole? I want to know for personal testing.
Click to expand...
Click to collapse
You don't really. Every test in SOME way is going to be more optimized for one gpu then another; you can't say "well this game runs smother on this phone thus making this gpu better". Benchmarking isn't realistic at all. To be honest I'm not sure of a great way to judge graphics card performance other then a long term
Overview of how it handles games. I could be wrong though, if someone wants to correct me feel free
Sent from my SPH-D710 using xda app-developers app
"hardware choices"
you gave more credit to one _software_platform_ (your definitions of competitors) for choice of colors....
yes, that makes sense.
ohgood said:
"hardware choices"
you gave more credit to one _software_platform_ (your definitions of competitors) for choice of colors....
yes, that makes sense.
Click to expand...
Click to collapse
Average consumer perspective. How much do cores matter to your mom or dad?

Categories

Resources