Why I switched back to S5 from HTC M8

[Kevin OQuinn]

Bloatware has nothing to do with the android software, that's added after each manufacture builds the phone and sends it out to the carriers.

Read a couple posts up, I'm not the only one who agrees that on screen buttons will be the future.

Posted via Android Central App

That's not quite right. The carrier gets the software build from the manufacturer, adds their stuff, then sends it back to be loaded on the devices. We know this from HTC's infographics regarding software updates.

Sent from my HTC One_M8 using Tapatalk

 

[slackerjack]

Oh, and with regards to the on screen buttons becoming some sort of standard, I'm not sure Google will do that any time soon. They would obviously prefer it, since that's how it is on Nexus, but they provide flexibility in the guidelines for a reason. With the buttons so heavily integrated into the design of the device they would almost surely have to give advance notice to manufacturer's so they can design around it.

Yeah, I happen to agree with you on this point - but I don't think it's the altruism of Google wanting flexibility and options, it was that when they pushed on the consumer - pushed back. Look at those devices that came with on screen buttons - and most of them were really good devices, all got outsold by the Gs3/4 who kept their design language consistent, which is more than I can Google and the UI design team.

This isn't the only case where Google wants something but can't convince the consumer it's the right idea, Look at SD card support - consumer chose devices with SD card slots despite what Google may have wanted for them. The S4 in particular was really a thumb in the nose of the SD Card slot naysayer...it's been a while, but wasn't that the GE device that shipped without SD card support but ended up adding it back in? Bottom line, there's a lot of really good use cases for that functionality, and as much as Google would like you to live in the cloud - they'll lose consumers if they don't continue to support it.

It's also not that surprising that anyone with a long history of Samsung devices would prefer the S5. It just makes sense logically.

Yep - again, successful design language (and consistency in that language) has gone a long way to help Samsung stay at the top of the hill. I'd like to see HTC, LG, etc - continue to keep their recent trends (in that direction) similar and at least play on the same ball field with Samsung...hell...someone other than Apple needs to keep them in check!

Jack

 

[Skyway]

That's not quite right. The carrier gets the software build from the manufacturer, adds their stuff, then sends it back to be loaded on the devices. We know this from HTC's infographics regarding software updates.

Sent from my HTC One_M8 using Tapatalk

Yea I knew it wasn't right after I posted it lol. Too lazy to edit, I figured someone would reply with the correct info.

My point still stands though, bloatware has nothing to do with android itself. Does Google add their own services and apps to the phones, sure but that's not carrier bloatware

Posted via Android Central App

 

[Kevin OQuinn]

Yea I knew it wasn't right after I posted it lol. Too lazy to edit, I figured someone would reply with the correct info.

My point still stands though, bloatware has nothing to do with android itself. Does Google add their own services and apps to the phones, sure but that's not carrier bloatware

Posted via Android Central App

No, it's Google bloatware lol.

Sent from my HTC One_M8 using Tapatalk

 

[Skyway]

Yeah, I happen to agree with you on this point - but I don't think it's the altruism of Google wanting flexibility and options, it was that when they pushed on the consumer - pushed back. Look at those devices that came with on screen buttons - and most of them were really good devices, all got outsold by the Gs3/4 who kept their design language consistent, which is more than I can Google and the UI design team.

This isn't the only case where Google wants something but can't convince the consumer it's the right idea, Look at SD card support - consumer chose devices with SD card slots despite what Google may have wanted for them. The S4 in particular was really a thumb in the nose of the SD Card slot naysayer...it's been a while, but wasn't that the GE device that shipped without SD card support but ended up adding it back in? Bottom line, there's a lot of really good use cases for that functionality, and as much as Google would like you to live in the cloud - they'll lose consumers if they don't continue to support it.

Jack

Yet devices still continue to come with on screen buttons, even though they are outsold by devices without them. Just because they don't sell more doesn't mean that it won't become a standard. This is just my opinion of course, I respect yours as you are fully entitled to it.

Sd card, despite what consumers chose, Google still changed read/write permissions. Google didn't have to convince anyone it was best, they just changed the way they are used. It's made a lot of people unhappy, just like on screen buttons do for some but it still doesn't change the fact

Posted via Android Central App

 

[killakumes]

True... And the nexus line also runs their software with no bloat from carriers or any manufacturers since they provide them..

So by your logic is Google going to stop allowing bloatware from carriers and manufacturers?

Sent from my T-Mobile Note 3 using AC Forums.

I think your missing the point. As long as the Google apps in the stock android package are included, manufactures and carriers are pretty much free to load up what ever crap they want even if their bloatware directly competes with a Google app.

The nexus line isn't a blueprint for manufactures or carriers but its a partnership that allows Google to set the standard for what it defines the android experience to be and communicates to the market its philosophy of the most current smartpjone.
The open source nature of android then let's manufactures and carriers to do what they want with that framework. But most devices also are available as a Google play edition in due time.

Sent from my SAMSUNG-SM-G900A using Tapatalk

 

[Skyway]

No, it's Google bloatware lol.

Sent from my HTC One_M8 using Tapatalk

We shall call it Googleware lol

Posted via Android Central App

 

[Almeuit]

I think your missing the point. As long as the Google apps in the stock android package are included, manufactures and carriers are pretty much free to load up what ever crap they want even if their bloatware directly competes with a Google app.

The nexus line isn't a blueprint for manufactures or carriers but its a partnership that allows Google to set the standard for what it defines the android experience to be and communicates to the market its philosophy of the most current smartpjone.
The open source nature of android then let's manufactures and carriers to do what they want with that framework. But most devices also are available as a Google play edition in due time.

Sent from my SAMSUNG-SM-G900A using Tapatalk

Oh I'm not missing the point.. You missed mine I believe .

As you said the Nexus isn't a blueprint for other Android device manufacturers... Which is what I was saying to Sky. Just because Google likes on screen buttons doesn't mean they will make it required by the other manufacturers.

Could they? Certainly but I don't see it happening soon.. I am sure they'd give them a good amount of fair warning before implementing something like that since some phones would need an entire design change.

Sent from my T-Mobile Note 3 using AC Forums.

 

[killakumes]

Oh I'm not missing the point.. You missed mine I believe .

As you said the Nexus isn't a blueprint for other Android device manufacturers... Which is what I was saying to Sky. Just because Google likes on screen buttons doesn't mean they will make it required by the other manufacturers.

Could they? Certainly but I don't see it happening soon.. I am sure they'd give them a good amount of fair warning before implementing something like that since some phones would need an entire design change.

Sent from my T-Mobile Note 3 using AC Forums.

No one ever said the change is happening tomorrow. We're just speculating about the future.

Anyone who keeps up with the nexus knows its the best prediction on the next wave of android phones

Sent from my SAMSUNG-SM-G900A using Tapatalk

 

[NYClawstudent]

Wow I did not anticipate such a strong reaction to my personal critiques of the M8. That being said- I appreciate those defending the M8 and how much the on-screen buttons are appreciated. Again, I just feel that at times the on screen buttons get in the way while typing. It could just be that I am so used to typing on the bottom of the screen from my time with the S4 and S3.

 

[Almeuit]

No one ever said the change is happening tomorrow. We're just speculating about the future.

Anyone who keeps up with the nexus knows its the best prediction on the next wave of android phones

Sent from my SAMSUNG-SM-G900A using Tapatalk

I know no one said that but we can speculate all day. He made it sound like he knew something we didn't is all.

He also said since Nexus does it one way that's how the standard is set.. So I just asked a question with that logic. Nothing wrong with asking him to explain his thought process .

Sent from my T-Mobile Note 3 using AC Forums.

 

[killakumes]

Wow I did not anticipate such a strong reaction to my personal critiques of the M8. That being said- I appreciate those defending the M8 and how much the on-screen buttons are appreciated. Again, I just feel that at times the on screen buttons get in the way while typing. It could just be that I am so used to typing on the bottom of the screen from my time with the S4 and S3.

I'm with you on that. I definitely prefer capacitative buttons, but sadly the trend looks like its on screen buttons (reminds me of the distaste people had when apple moved the original iPod controls from a stand alone row to on the scroll wheel). I hope more phone take a cue from the oneplus one announcement and give users the choice.

Another interesting point is buttons take physical space that may quite possibly be sacrificed for added hardware or design principle and cement the use of on screen buttons.

I know no one said that but we can speculate all day. He made it sound like he knew something we didn't is all .

He also said since Nexus does it one way that's how the standard is set.. So I just asked a question with that logic. Nothing wrong with asking..

Sent from my T-Mobile Note 3 using AC Forums.

Nothing wrong at all and I definitely wouldn't go as far to say a standard is set as was said earlier.

Its interesting that the oneplus one revealed a choice for users. For me it feels like a trend has definitely been formed. Opens news doors for design and capabilities.


Sent from my SAMSUNG-SM-G900A using Tapatalk

 

[freddyttt]

I want/need a phone that gives me the best possible user experience with no hiccups/no lags/no slow down...... for that for me there is only one winner.

 

[aramos87]

Here are some pics of the M7 on the left (4.7" screen) vs. the M8 on the right to support your comments about lack of screen real estate.
The M8 useable screen area measures out to about 4.75"....such a huge phone for such a small screen.
[url]http://i1223.photobucket.com/albums/dd501/Seatttle/M7ampM8_zpsfa80e909.jpg[/URL]

The M7 seems to have full screen enabled or something, considering the toolbar isn't at the top. On the M8 it is still there, without it I'm sure it would look very similar.

Posted via Android Central App

 

[Aquila]

Here are some pics of the M7 on the left (4.7" screen) vs. the M8 on the right to support your comments about lack of screen real estate.
The M8 useable screen area measures out to about 4.75"....such a huge phone for such a small screen.

On a 1920x1080p device, the navigation row is 96 pixels tall and thus takes up 5% of the display area.

For the "usable space" the M8 is approx 4.81" vs the 4.7" in the M7, so only about 2% larger diagonally, which translates to only about (10.143-9.427)/9.427 ~= 7.6% increased area.

In immersive mode or whatever they are calling it, it would be (10.662-9.427)/9.427 ~= 13.1% more area, so one could say we're losing about 42% of the total screen area increase to the on-screen buttons when they are on the screen.

For those overly concerned with this, it is possible to get ROMs or other MODs that allow users to change the DPI settings of the navigation row, limiting it's height to 48 pixels or 24, as examples or remove it entirely and replace it with PIE controls, etc. There are many options to mitigate the impact if you see this as a negative, but no matter what those options look like, the fact remains that the S5 and G2 will be larger no matter what, so if you are trying to maximize screen size, this isn't the biggest display out there by any means.

Math for the 4.81" is in this thread: http://forums.androidcentral.com/ht...e-up-any-larger-display-size.html#post3553025

 

[BBSeattle]

So you believe that the content on the lighted portion known as "the screen" determines the size of the screen? Unfortunately no matter what you put on the lighted portion known here on as the screen has no bearing on the size of the screen. Let me know if you need a picture, I would be happy to post one. Also, Kevin posted a pic of identical content a few posts back. Go have a look.

The M7 seems to have full screen enabled or something, considering the toolbar isn't at the top. On the M8 it is still there, without it I'm sure it would look very similar.

Posted via Android Central App

 

[BBSeattle]

Well thought and written.

On a 1920x1080p device, the navigation row is 96 pixels tall and thus takes up 5% of the display area.

For the "usable space" the M8 is approx 4.81" vs the 4.7" in the M7, so only about 2% larger diagonally, which translates to only about (10.143-9.427)/9.427 ~= 7.6% increased area.

In immersive mode or whatever they are calling it, it would be (10.662-9.427)/9.427 ~= 13.1% more area, so one could say we're losing about 42% of the total screen area increase to the on-screen buttons when they are on the screen.

For those overly concerned with this, it is possible to get ROMs or other MODs that allow users to change the DPI settings of the navigation row, limiting it's height to 48 pixels or 24, as examples or remove it entirely and replace it with PIE controls, etc. There are many options to mitigate the impact if you see this as a negative, but no matter what those options look like, the fact remains that the S5 and G2 will be larger no matter what, so if you are trying to maximize screen size, this isn't the biggest display out there by any means.

Math for the 4.81" is in this thread: http://forums.androidcentral.com/ht...e-up-any-larger-display-size.html#post3553025

 

[zipro]

But here's what was the most frustrating. Despite having nearly identical screen sizes, the on screen navigation buttons for the M8 drove me insane.

I know what you mean - I also have a Nexus 5 and there it's never bothered me, but with the M8 it was a problem for me. I guess the shape of the phone also plays a part in this.

Anyway, I ended up selling the S5 as well because of the constant performance issues. It's not a slow phone per se, but it just doesn't feel fast, either. The N5 runs circles around in perceived performance.

 

[anon5664829]

IPS is better then AMOLED.

 

[Aquila]

IPS is better then AMOLED.

Better at...? (You know I always have to ask that)

The S5 has gotten some great reviews of the screen they are using, saying that it has caught up to IPS in several categories. So far the Nexus 5 still has the best (in terms of accuracy) screen on a phone, and it is IPS, but it sounds like some exciting things are happening in display tech, and Sammy is using some of them to make a screen that people are really loving. So while it may not be the most accurate out there, it is doing well in the categories of brightness, it didn't do poorly in accuracy and a lot of people really like the "pop" that over-saturated screens provide. My laymen's guess at the 'top 5 screens' on shelves today only includes 1 SAMOLED, but this is that one.