Nexus 5

[Lava Lamp Freak]

The problem right now is that it is inconsistent. It would be cool if they kept the current implementation of the back button, made it consistent, and added the ability to quickly double-tap the multitasking button to quickly take you to the last app you were in. And really, they should change the name of the back button because it is illogical according to its name.

It is not inconsistent. It works exactly the way Google programmed it to work. You are right that it won't work in the way you are wanting it to, but that doesn't make it inconsistent -- it just makes it not work the way you want it to. I understand what you are saying and what you want it to do -- that's just not what Google thinks it should do. I like it the way it is and don't find anything inconsistent about it. I did when I first started using it, but once I figured out the logic involved, it made perfect sense.

 

[strausd]

It is not inconsistent. It works exactly the way Google programmed it to work. You are right that it won't work in the way you are wanting it to, but that doesn't make it inconsistent -- it just makes it not work the way you want it to. I understand what you are saying and what you want it to do -- that's just not what Google thinks it should do. I like it the way it is and don't find anything inconsistent about it. I did when I first started using it, but once I figured out the logic involved, it made perfect sense.

As explained above, the logic isn't there. You just seem to be missing that.

It is not inconsistent. It works exactly the way Google programmed it to work.

Imagine if someone on here said the exact same thing just said "Apple" instead of "Google." You guys would jump all over their balls. This statement reeks of "fanboyism."

Explain to me how this part is illogical:

Lets say you are driving across states to various cities. Lets say you go to 6 cities across 2 states.

You have state A and state B both with cities 1, 2, and 3.

A.1
A.2
A.3

B.1
B.2
B.3

And the cities are layed out in a linear fashion on a map so 1 comes before 2, 2 before 3 in both states. However, because of the way the highways are set up, you can go from A.1 to B.3 without going through any other cities if you want to.

You start driving from A.1 and you arrive at A.2. Then you go to B.2 and then to B.3. A.1 > A.2 > B.2 > B.3 so far. Then from B.3 you go to A.3. Then you realize you left you computer in the last city you were in and you want to go back to get it. If you go back to the last place you were in, you would go to B.3, not A.2.

It is simple logic. Going back means you would go back to the last place you were in, which was a different state. Going back doesn't mean going back linearly in the state you are in as that would do you no good and wouldn't actually take you back to where you were. It would take you "back" but from a logical standpoint it does not take you back to where you were.

You are failing to understand how the Back button works. It's as simple as that.

You are failing to understand how logic works. It's as simple as that.

 

[Lava Lamp Freak]

As explained above, the logic isn't there. You just seem to be missing that.


Imagine if someone on here said the exact same thing just said "Apple" instead of "Google." You guys would jump all over their balls. This statement reeks of "fanboyism."

You've made up your own idea of what a back button should theoretically should do, and you're frustrated that it doesn't work that way. I understand that. What you aren't understanding is that Google doesn't agree with you, and didn't program it that way. They're using a logic that says the back button only works within an app -- not between apps. If you don't agree that is fine, but you are the one with the problem, not the rest of us.

----------

Explain to me how this part is illogical:

I'm not saying that your idea is illogical, it just isn't how it works. How it works is also logical. There isn't a right and wrong way to do logic. Google chose a different logic than you are expecting. All you can do is learn Google's logic and work in that system. I don't know what else to tell you.

 

[strausd]

They're using a logic that says the back button only works within an app -- not between apps.

Wrong.

I'm not saying that your idea is illogical,

Either what I stated is logical or illogical. If it isn't illogical, then it is logical. Makes sense so far. You agreed that what I said about going back to where you were is logical. We are on the same page so far.

How it works is also logical.

You already said that going back to where you were is logical. Now you are saying going backwards to where you weren't were is logical as well? Maybe you don't understand logic.

 

[TacticalDesire]

So after two pages of arguing about the back button can we get back to discussing the Nexus 5? Please and thank you.

 

[strausd]

So after two pages of arguing about the back button can we get back to discussing the Nexus 5? Please and thank you.

Back on topic, I read about the MEMS camera and it is very exciting. Although seeing how many pictures it takes to give dynamic focus capabilities, I am hoping they offer a 32GB option.

 

[onthecouchagain]

Let me explain the logic behind how a back button should work.

Take a second and throw out your understanding of the current back button and focus solely on the logic. We will get to the current implementation of the back button soon, but right now throw it out.

Lets say you are driving across states to various cities. Lets say you go to 6 cities across 2 states.

You have state A and state B both with cities 1, 2, and 3.

A.1
A.2
A.3

B.1
B.2
B.3

And the cities are layed out in a linear fashion on a map so 1 comes before 2, 2 before 3 in both states. However, because of the way the highways are set up, you can go from A.1 to B.3 without going through any other cities if you want to.

You start driving from A.1 and you arrive at A.2. Then you go to B.2 and then to B.3. A.1 > A.2 > B.2 > B.3 so far. Then from B.3 you go to A.3. Then you realize you left you computer in the last city you were in and you want to go back to get it. If you go back to the last place you were in, you would go to B.3, not A.2.

It is simple logic. Going back means you would go back to the last place you were in, which was a different state. Going back doesn't mean going back linearly in the state you are in as that would do you no good and wouldn't actually take you back to where you were. It would take you "back" but from a logical standpoint it does not take you back to where you were.

Same thing goes for Android with states being apps and cities being places inside the apps. The logic makes sense.

Now lets say I am in that same situation and I go from B.3 to A.3 and need to go back. But then my car takes me to state C. That makes no sense, but that is exactly what Android does when going from Chrome to Messaging and then hitting back. It takes me to the home screen where I never was. Other times it will take me backwards within the app depending on the app.

So imagine you have a Google Autonomous car and you tell it you need to go back to your last location. It will randomly take you between various cities and states where none of which where your last location. That makes no sense. If you tell it to go back to where you last were, it should always take you back to where you last were.

Now back to thinking about the current implementation of the back button. It works like an autonomous car that doesn't understand "last location." Is the current implementation of the back button perfect? No. Would this implementation make it perfect? No. There is no perfect way to have a single "back" button that works perfectly because yes, in some circumstances you need to go backwards within the app. The problem right now is that it is inconsistent. It would be cool if they kept the current implementation of the back button, made it consistent, and added the ability to quickly double-tap the multitasking button to quickly take you to the last app you were in. And really, they should change the name of the back button because it is illogical according to its name.

You guys just don't seem to understand the logic. A back button is supposed to take you back to where you last were. Simple. Anything else is not a back button, but a "sort of" back button. bmac even admitted to this by saying it works "for the most part." By definition, it is not a back button unless it always takes you back. Simple logic you guys can't seem to grasp.

Straus, I can't believe you are actually being this daft.

There are buttons that do precisely what you're desiring already. If you want to go back to the "previous state," be it the previous app or the home screen if you had launched the app from there, you can. There's a button called App Switcher, and a button called Home.

Why should the Back button do things that there are others buttons for?

And you've yet to answer this important question that explains precisely why it should not work the way you're wishing it to: How would you go back within an app after you've launched it from Home or from the App Switcher.

If there's one thing you do here, please answer that. Remember, not all apps have a top-left corner navigational pane. In your world, wouldn't the app be stuck forever in its current state/screen, then, if the Back button brought you back to the previous app and/or the home screen?

The back button itself is perfect in what it's there to do -- take you backwards within an app until there's no more to go back to (then it takes you home). The way developers program it, however, can sometimes be not perfect. And, as said, Google can add features to it to expand its role.

The desire that you want -- going back to the previous state, no matter what that was, be it another app or the home screen -- ultimately eliminates the reason to have a Back button and undermines the App Switcher and Home buttons, which again, are there to do exactly what you're asking for!

Goodness gracious.

 

[Lava Lamp Freak]

Wrong.
Image


Either what I stated is logical or illogical. If it isn't illogical, then it is logical. Makes sense so far. You agreed that what I said about going back to where you were is logical. We are on the same page so far.


You already said that going back to where you were is logical. Now you are saying going backwards to where you weren't were is logical as well? Maybe you don't understand logic.

Here is Google's logic, in Google's own words.

The system Back button is used to navigate, in reverse chronological order, through the history of screens the user has recently worked with. It is generally based on the temporal relationships between screens, rather than the app's hierarchy.

When the previously viewed screen is also the hierarchical parent of the current screen, pressing the Back button has the same result as pressing an Up button—this is a common occurrence. However, unlike the Up button, which ensures the user remains within your app, the Back button can return the user to the Home screen, or even to a different app.

It works the way Google designed it work. It is consistent in this manner. It always does what Google has designed it to do. You have misunderstood the graphic you posted. The back button will take you to the previous app IF the previous app is in the hierarchy. (For example, clicking a link in an app taking you to Chrome. Once in Chrome, back will take you back to where you clicked the link.) Every time you manually switch apps, you break that hierarchy and the back button will take you home or to a previous screen in that app. That is the logic Google used to design it.

http://developer.android.com/design/patterns/navigation.html

 

[onthecouchagain]

You've made up your own idea of what a back button should theoretically should do, and you're frustrated that it doesn't work that way. I understand that. What you aren't understanding is that Google doesn't agree with you, and didn't program it that way. They're using a logic that says the back button only works within an app -- not between apps. If you don't agree that is fine, but you are the one with the problem, not the rest of us.

----------



I'm not saying that your idea is illogical, it just isn't how it works. How it works is also logical. There isn't a right and wrong way to do logic. Google chose a different logic than you are expecting. All you can do is learn Google's logic and work in that system. I don't know what else to tell you.

Very very well said. All of it.

Straus, you can use all the semantics of logic/illogic or hypothetical examples of traveling through inter-states and leaving your computer behind you want (your analogy is awfully flawed. by the way. Your analogy would only work if in Android the App Switcher and Home buttons didn't exist, but they do), it won't change the fact that Google programmed the Back button to do exactly what it's there to do (again! There are two other buttons that will do precisely what you're wishing for).

Like I said before, it's not like the Back button has been "broken" for five years since the inception of Android.

----------

Here is Google's logic, in Google's own words.



It works the way Google designed it work. It is consistent in this manner. It always does what Google has designed it to do. You have misunderstood the graphic you posted. The back button will take you to the previous app IF the previous app is in the hierarchy. (For example, clicking a link in an app taking you to Chrome. Once in Chrome, back will take you back to where you clicked the link.) Every time you manually switch apps, you break that hierarchy and the back button will take you home or to a previous screen in that app. That is the logic Google used to design it.

http://developer.android.com/design/patterns/navigation.html

Yes. All yes.

Straus, you have gravely misinterpreted and misunderstood that graphic. Which is why I helped by posting this:

-Return to previous app when on the last activity and the app was launched through intent from another app

 

[onthecouchagain]

Straus, answer me this, please:

-I open the Play Store to a list of apps.

-I click an app and it takes me to the app description.

-Then I hit back, it takes me back to the list of apps.

-Then I hit back again, what should it do?

In your world where the back button always literally takes me back to the previous screen/state, wouldn't that put me in an infinite loop between the app description and the list of apps?

You want the Back button to always literally take you back to the previous state/screen, no matter what or where that was, right? That's what you said and have been preaching:

It is simple logic. Going back means you would go back to the last place you were in

Wouldn't that put you stuck in between two screens forever???

Talk about logic!


------


EDIT: Actually, let's use your own example.


-I'm in Chrome. I hit App Switcher to go to Tapatalk. You want the back button to go back to Chrome, right?

-So let's say I hit Back and it goes back from Tapatalk to Chrome, as you so desire.

-If I hit Back again, by your own logic, shouldn't it go back to Tapatalk, then?

Now, the Back button is doing what you want, right? Going back to the previous state/screen, even if it's a different app. So in this scenario, if we keep hitting the Back button, it'll be forever stuck between Chrome and Tapatalk. Remember, now I am using your logic for what the Back button should do.

Please, Straus, I beg of you; explain this.

 

[strausd]

Here is Google's logic, in Google's own words.

HAHAHA Google even admits to it being inconsistent by using the word "generally!"

Then they say, in the picture used previously, that it will open the previous screen no matter what. You guys are just blind by your Android bias.

Face the fact, Google is inconsistent.

Straus, you can use all the semantics of logic/illogic or hypothetical examples of traveling through inter-states and leaving your computer behind you want (your analogy is awfully flawed. by the way. Your analogy would only work if in Android the App Switcher and Home buttons didn't exist, but they do), it won't change the fact that Google programmed the Back button to do exactly what it's there to do (again! There are two other buttons that will do precisely what you're wishing for).

You may think the analogy is flawed, but you're wrong. It's simple logic. Either it takes you back to where you were or it doesn't. You guys are thinking too much and missing the simple facts.

Explain to me how this part is illogical:

Lets say you are driving across states to various cities. Lets say you go to 6 cities across 2 states.

You have state A and state B both with cities 1, 2, and 3.

A.1
A.2
A.3

B.1
B.2
B.3

And the cities are layed out in a linear fashion on a map so 1 comes before 2, 2 before 3 in both states. However, because of the way the highways are set up, you can go from A.1 to B.3 without going through any other cities if you want to.

You start driving from A.1 and you arrive at A.2. Then you go to B.2 and then to B.3. A.1 > A.2 > B.2 > B.3 so far. Then from B.3 you go to A.3. Then you realize you left you computer in the last city you were in and you want to go back to get it. If you go back to the last place you were in, you would go to B.3, not A.2.

It is simple logic. Going back means you would go back to the last place you were in, which was a different state. Going back doesn't mean going back linearly in the state you are in as that would do you no good and wouldn't actually take you back to where you were. It would take you "back" but from a logical standpoint it does not take you back to where you were.

(your analogy is awfully flawed. by the way. Your analogy would only work if in Android the App Switcher and Home buttons didn't exist, but they do),

The addition or subtraction of the home and multitasking button has no affect on the basic logical structure of this analogy. Maybe you just don't understand it, and thats fine. But the fact is, regardless of the home button and multitasking button, the back button does not take you back to where you were. You could include in the analogy a personal teleportation button that always takes you to your house. And another teleportation button that always takes you to an airport to take you anywhere you want. What you fail to understand (time and time again might I add), is that the addition of going directly to your house or an airport doesn't change the fact that the car won't take you to your last location.

Straus, you have gravely misinterpreted and misunderstood that graphic.

"Opens the previous screen you were working in." Either it does or it doesn't! You are the one pushing different interpretations on it.

Straus, answer me this, please:

-I open the Play Store to a list of apps.

-I click an app and it takes me to the app description.

-Then I hit back, it takes me back to the list of apps.

-Then I hit back again, what should it do?

In your world where the back button always literally takes me back to the previous screen/state, wouldn't that put me in an infinite loop between the app description and the list of apps?

You want the Back button to always literally take you back to the previous state/screen, no matter what or where that was, right? That's what you said and have been preaching:



Wouldn't that put you stuck in between two screens forever???

Talk about logic!

I have already responded to that. You just continually fail to read.

Now back to thinking about the current implementation of the back button. It works like an autonomous car that doesn't understand "last location." Is the current implementation of the back button perfect? No. Would this implementation make it perfect? No. There is no perfect way to have a single "back" button that works perfectly because yes, in some circumstances you need to go backwards within the app. The problem right now is that it is inconsistent. It would be cool if they kept the current implementation of the back button, made it consistent, and added the ability to quickly double-tap the multitasking button to quickly take you to the last app you were in. And really, they should change the name of the back button because it is illogical according to its name.

----------

You guys can continue to cherry pick parts out of this post to respond to. And I am sure you will because you both love to argue. But really doing so is just rehashing what has already been said, so it would be pointless and a waste of time.

So let's put everything up to this point behind us because you don't agree with me, and I don't agree with you. Why waste time on something we will never agree on? I try and follow logic, you follow Google.

Let's try and break this down and have it be as simple as possible.

Answer me this one question with a simple yes or no answer: Does the current implementation of the back button always take you to the previous screen as Google says it does?

If the answer is yes, well, you're lying. If the answer is no, by definition it is not a "back" button but instead a button that should be called something else. I am trying to strip it down to its simplest form, that being logic.

 

[onthecouchagain]

HAHAHA Google even admits to it being inconsistent by using the word "generally!"

Then they say, in the picture used previously, that it will open the previous screen no matter what. You guys are just blind by your Android bias.

Face the fact, Google is inconsistent.



You may think the analogy is flawed, but you're wrong. It's simple logic. Either it takes you back to where you were or it doesn't. You guys are thinking too much and missing the simple facts.

Explain to me how this part is illogical:




The addition or subtraction of the home and multitasking button has no affect on the basic logical structure of this analogy. Maybe you just don't understand it, and thats fine. But the fact is, regardless of the home button and multitasking button, the back button does not take you back to where you were. You could include in the analogy a personal teleportation button that always takes you to your house. And another teleportation button that always takes you to an airport to take you anywhere you want. What you fail to understand (time and time again might I add), is that the addition of going directly to your house or an airport doesn't change the fact that the car won't take you to your last location.



"Opens the previous screen you were working in." Either it does or it doesn't! You are the one pushing different interpretations on it.



I have already responded to that. You just continually fail to read.


----------

You guys can continue to cherry pick parts out of this post to respond to. And I am sure you will because you both love to argue. But really doing so is just rehashing what has already been said, so it would be pointless and a waste of time.

So let's put everything up to this point behind us because you don't agree with me, and I don't agree with you. Why waste time on something we will never agree on? I try and follow logic, you follow Google.

Let's try and break this down and have it be as simple as possible.

Answer me this one question with a simple yes or no answer: Does the current implementation of the back button always take you to the previous screen as Google says it does?

If the answer is yes, well, you're lying. If the answer is no, by definition it is not a "back" button but instead a button that should be called something else. I am trying to strip it down to its simplest form, that being logic.

Straus, please, respond to this:

EDIT: Actually, let's use your own example.


-I'm in Chrome. I hit App Switcher to go to Tapatalk. You want the back button to go back to Chrome, right?

-So let's say I hit Back and it goes back from Tapatalk to Chrome, as you so desire.

-If I hit Back again, by your own logic, shouldn't it go back to Tapatalk, then?

Now, the Back button is doing what you want, right? Going back to the previous state/screen, even if it's a different app. So in this scenario, if we keep hitting the Back button, it'll be forever stuck between Chrome and Tapatalk. Remember, now I am using your logic for what the Back button should do.

Please, Straus, I beg of you; explain this.

You claim to have responded to this gigantic flaw in your logic of how the Back button should work, but all you've explained is 1) the way you want it to work cannot work, which you basically said yourself here:

Would this implementation make it perfect? No. There is no perfect way to have a single "back" button that works perfectly because yes, in some circumstances you need to go backwards within the app.

and 2) you don't understand how it's working in its current iteration.

Even if its current iteration is inconsistent (it's not; not unless a developer messes it up), but again, even if it was inconsistent, it's still better than your idea of how the back button should work because the way your back button works could forever put you in an infinite loop between two apps.

 

[jamezr]

long posts about back button

Strausd and Couch.....can you guys take this stuff offline? Its hard to find the latest news on the Nexus 5 if we all have to wade through all the very long posts about your arguments about the back button. Thanks guys!

 

[King Shady]

Please stop arguing about the back button. It works just fine in Android and iOS, we don't need a debate on the back button, in the Nexus 5 thread.

 

[onthecouchagain]

Strausd and Couch.....can you guys take this stuff offline? Its hard to find the latest news on the Nexus 5 if we all have to wade through all the very long posts about your arguments about the back button. Thanks guys!

Fear not. I'm done. Everyone seems to understand perfectly how the Back button works, except Straus. There's nothing else I can add.

My apologies.

----------

Please stop arguing about the back button. It works just fine in Android and iOS, we don't need a debate on the back button, in the Nexus 5 thread.

I agree.

I'm done. My apologies to all, genuinely.

 

[Lava Lamp Freak]

Answer me this one question with a simple yes or no answer: Does the current implementation of the back button always take you to the previous screen as Google says it does?

If the answer is yes, well, you're lying. If the answer is no, by definition it is not a "back" button but instead a button that should be called something else. I am trying to strip it down to its simplest form, that being logic.

The problem is that you're wanting an app history back button while Android gives you task history back button. The app switcher already fits what you're looking for. Call the back button whatever you like, but it works exactly as Google has explained in detail on their developer page. Read the section titled Navigation Between Apps. It illustrates in detail exactly how the task system works when switching between apps. If you think it is illogical, so be it, but it is what it is and what it has always been. I won't clutter this thread with any more replies about this topic for the sake of the thread.

http://developer.android.com/design/patterns/navigation.html

 

[onthecouchagain]

The problem is that you're wanting an app history back button while Android gives you task history back button. The app switcher already fits what you're looking for. Call the back button whatever you like, but it works exactly as Google has explained in detail on their developer page. Read the section titled Navigation Between Apps. It illustrates in detail exactly how the task system works when switching between apps. If you think it is illogical, so be it, but it is what it is and what it has always been. I won't clutter this thread with any more replies about this topic for the sake of the thread.

http://developer.android.com/design/patterns/navigation.html

I just read through this and it was fascinating. I actually have a newfound appreciation for the back button now. Thanks for sharing this. It really does explain everything.

 

[Saturn1217]

Yea but I thought I read in that article $446 somewhere. Could be wrong

The article (and the rumor) was referring to the UK prices in pounds and some other article then did a straight conversion to dollars and reported that. Correct me if I'm wrong but I don't think Apple's prices work that way so it probably won't be $446 USD. It will likely be ~half the US iPhone price of $650/2 = $325.

 

[THE JUICEMAN]

The article (and the rumor) was referring to the UK prices in pounds and some other article then did a straight conversion to dollars and reported that. Correct me if I'm wrong but I don't think Apple's prices work that way so it probably won't be $446 USD. It will likely be ~half the US iPhone price of $650/2 = $325.

Sounds great to me. Bring it on google

 

[onthecouchagain]

While I'm happy to hear rumors that it'll retain it's low price point, I hope that doesn't mean there are compromises, like say, with the available storage options.

If 16GB is the max, it'll be an instant no. I'm not going from my 64GB HTC One to a 16GB Nexus 5.

 

[whoknows87]

Please stop arguing about the back button. It works just fine in Android and iOS, we don't need a debate on the back button, in the Nexus 5 thread.

I came to look for pictures, rumors about price and maybe camera updates lol
didn't know the back button is so important haha

 

[THE JUICEMAN]

While I'm happy to hear rumors that it'll retain it's low price point, I hope that doesn't mean there are compromises, like say, with the available storage options.

If 16GB is the max, it'll be an instant no. I'm not going from my 64GB HTC One to a 16GB Nexus 5.

Really? Do you keep a bunch of music or videos on the phone? I know everyone's usage is different but to me the benefits of Nexus outweigh the storage. I know that's just my opinion of course.

 

[strausd]

Straus, please, respond to this:

You claim to have responded to this gigantic flaw in your logic of how the Back button should work, but all you've explained is 1) the way you want it to work cannot work, which you basically said yourself here:

and 2) you don't understand how it's working in its current iteration.

Even if its current iteration is inconsistent (it's not; not unless a developer messes it up), but again, even if it was inconsistent, it's still better than your idea of how the back button should work because the way your back button works could forever put you in an infinite loop between two apps.

I already responded in post 512.

because the way your back button works could forever put you in an infinite loop between two apps.

Funny how you don't mention how pressing alt-tab or command-tab can give you an infinite loop between apps.

The problem is that you're wanting an app history back button while Android gives you task history back button. The app switcher already fits what you're looking for. Call the back button whatever you like, but it works exactly as Google has explained in detail on their developer page. Read the section titled Navigation Between Apps. It illustrates in detail exactly how the task system works when switching between apps. If you think it is illogical, so be it, but it is what it is and what it has always been. I won't clutter this thread with any more replies about this topic for the sake of the thread.
http://developer.android.com/design/patterns/navigation.html

No, read more carefully. No implementation of a single "back" button is perfect. I am just pointing out the flaws. You two are just blinded by your Android bias and refuse to recognize the back button's inconsistencies.

Fear not. I'm done.

Oh really...?

I just read through this and it was fascinating. I actually have a newfound appreciation for blah blah blah blah blah

Everyone seems to understand perfectly how the Back button works, except Straus. There's nothing else I can add.

You count you and lavalamps as everyone? Maybe you missed the other people who have also stated the inconsistencies of the back button.

For whatever reason, you seem to not understand simple logical statements. You also can't even stick to your own word about being "done." Your blind bias keeps you from realizing the problems with the mobile operating you are so in love with. Some people just need a gentle nudge in the right direction. For whatever reason you have this false fantasy where everyone in the world thinks like you and I am the only one who notices the flaws in the back button. Guess what, you're wrong (surprise surprise).

 

[tbayrgs]

Really? Do you keep a bunch of music or videos on the phone? I know everyone's usage is different but to me the benefits of Nexus outweigh the storage. I know that's just my opinion of course.

I'm in total agreement with Couch here. I do prefer to keep my music/audiobooks stored locally to reduce data usage, I have a few GB of apps and I generally take quite a few videos. I've used nearly half the storage of my HTC One's 64 GB so 32 GB is the minimum I'll be able to get by with, regardless of the device. No 32 GB model and sadly, I'll have to pass.

 

[Saturn1217]

I already responded in post 512.

Funny how you don't mention how pressing alt-tab or command-tab can give you an infinite loop between apps.

No, read more carefully. No implementation of a single "back" button is perfect. I am just pointing out the flaws. You two are just blinded by your Android bias and refuse to recognize the back button's inconsistencies.

Oh really...?


You count you and lavalamps as everyone? Maybe you missed the other people who have also stated the inconsistencies of the back button.

For whatever reason, you seem to not understand simple logical statements. You also can't even stick to your own word about being "done." Your blind bias keeps you from realizing the problems with the mobile operating you are so in love with. Some people just need a gentle nudge in the right direction. For whatever reason you have this false fantasy where everyone in the world thinks like you and I am the only one who notices the flaws in the back button. Guess what, you're wrong (surprise surprise).

Please open another thread to discuss this issue. This thread is about the Nexus 5. I come here to check on updates about the Nexus 5. FWIW I agree with you that the back button could be more consistent but most people who are interested in the Nexus 5 have no issue (or very little issue) with how the android back button works. If you do have an issue open a NEW thread to discuss it and/or send feedback to google. But PLEASE STOP DISCUSSING IT HERE!