cgk
New member
Are you always this sunny and optimistic or did someone piss in your Cheerios?
There is a difference between optimistic and losing touch with reality.
Sent from my Nexus 7 using Tapatalk HD
Are you always this sunny and optimistic or did someone piss in your Cheerios?
Samsung isn't savvy? Ok.... The largest phone maker isn't savvy.
User experience is purely opinionated. Some prefer this while others prefer that, you know.
Savvy doesn't mean much in that context (shrewed? informed?). Based on previous posts I must assume you mean to say Samsung's core hardware (SoC etc) is technically superior to everyone else's, which explains part of their success. That is BS, but possibly I'm just misunderstanding you.
Of course Samsung isn't worse in the core hardware department either, but that area is not the foundation of their success.
Obviously, but you're just failing to understand. This was about profiling OS' native UI stacks (time from API call or touch input to updates hitting the frame buffers) and determining how this varied accross various hardware configurations. Again: WP proved much more efficient than Jellybean on comparable low end hardware. Same results on high end hardware, but the difference isn't noticable to humans.
There is a difference between optimistic and losing touch with reality.
Sent from my Nexus 7 using Tapatalk HD
Samsung is so savvy that they have dual cores matching the competitors low end devices.
I'm referring to Samsung's entire mobile division when I say Samsung is savvy. I'm referring to the pricing and availability of their phones. I'm not only talking about chips.
Windows phone is more efficient at touch based objects? Sure I give you that.
My blame lies with Portico. Pre portico my battery life was pretty decent, now its just horrid.
No. I had 6 horrible months with Lumia 800 what a disappointment. Switched to Motorola RAZR Maxx, it's night and day, what a joy to use and I get at least 40 hours from one charge compared to Lumia's 20. And that's not a fair comparison as Lumia had battery saver on permanently, no automatic updating of email or anything else whereas the RAZR has no such restrictions on it.
I would disagree. I run jelly bean on a Motorola Xoom and its disgusting how slow the tablet got after installing jelly bean. It ran better on ICS. As was the same experience with my HTC One X. Android adds certain functions to help the phone run smoother, but what type of phones does this really apply to? The high end phones. Wheras the low will still preform low.correct but not against a Jelly Bean designed device. Nevertheless you are 100% correct about the battery life.
Your experience may vary. But I'm not the only one whose battery life suffers after the update, even after two hard resets.Mine shipped with portico already installed, and my battery's been amazing since day 1. I used it for that whole first day, from when I bought it at 11am until I went to bed at midnight on the 61% charge it shipped with and still had juice left when I plugged it in that night.
The RAZR MAXX also has literally double the battery capacity.
I do know that. Why other phones don't use a larger battery is a mystery. The RAZR is no larger, thicker or heavier than any other top end phone
Yes, I'm astounded how laggy even Tegra 3 devices are. How much of that lag is down to the OS, or to the individual app, but it's pretty bad.
My Dell Venue Pro is smooth as silk all the time, but it'll never see the light of WP7.8... or will it?
hey crazeee, I can back freestaterocker up on this. I've conducted measurements on a lot of devices and WP's performance on low-end hardware is spectacular compared to android... including JB. I see this as WP's best chance at gaining marketshare, but the 620 is still a tad too expensive. Shave off another $100, which will happen within 12 months, and WP's usability advantages over similarly priced Android handsets becomes glaringly obvious. This is not opinion, but fact.
The explanation:
Google must develop Android without making any assumptions about the underlying hardware. As a result, they can make absolutely no hardware based performance optimizations. They leave this up to OEM's, which invest as little in this area as possible. On low end devices such efforts are skipped entirely, as doing so is extremely costly.
Microsoft has no such restrictions. They know exactly what hardware the OS will run on (exclusively Qualcomm S4) and they use that knowledge to squeeze every last drop of performance out of the SoC that they possibly can. Those optimizations exist on all levels, and aren't just restricted to drivers as on Android. This explains why Microsoft could squeeze jellybean level UI performance out of a 2008 era SoC on WP7, which was laughably underpowered compared to the Android competition, yet performed better. WP OEM's need do nothing more than install it... no optimization work required, whatsoever.
I think you are letting your bias overlook a few things here.