Hmm, announcement is coming "soon".![]()
If I had a dime for every time I heard this, I'd probably have close to three dollars by now.
Hmm, announcement is coming "soon".![]()
I don't recall saying I would not discuss something with someone on this site again bashing someone. In my experience with you no matter how smooth the discussion is going. If at any point you disagree. It starts a long back and forth of you trying to prove me, or anyone else how they are wrong. Implying they are stupid without using any term like that. If you want to call me being responsible, and understanding that arguing with you accomplishes nothing bashing you. Then go right ahead.
All I will say about the battery is that GPE prove nothing. Just because they take a week longer to see the new update means nothing. Some of the N4 take longer to update then others. Does not mean anything special was done to them. The reason the GPE take longer is because Google gets the update pushed to Nexus user first. Then it goes to GPE. I highly doubt Samsung and HTC in a week have time to optimize a battery for the new update.
----------
Well I hope we will be the one taking these pictures soon.
The point is, Straus doesn't know why the Nexus 4 has battery woes. That's all I needed to hear.
I'd drop it.
Geez, this is so far down the road. I dont buy multiple phones. Just not my thing. I do homework and go from here.
So for me-
I have a GS3 and ive mentioned couple times already that its going to be the G2 or N5 for me.
The above you mention-
Not interested in a iPhone. 3 years running with nothing that interesting and now ive lost all interest and Android is just so good.
Not a Sony fan so no interest there...but never say never,... wasnt much of a LG fan either but they have come to compete.
The Moto X is very interesting to me but im not going to pay $600 to get one( $200 more than a 32GB N5) and ill assume that ill still be the case w/ the M2...which is a bummer for T-Mobile users. I just dont pay that for phones upfront but ill do $400 for the N5.
Not a HTC fan either but they are worth keeping an eye out but they havent come close to reeling me in again. Dont care for aluminum backs and their batteries suck( in my experience)
S5 i think will be interesting im sure Not interested in paying $629 for a Google addition. For now im looking forward to getting my new G2 or N5...preferably the N5 if the battery is good.
It was taken by Nickyyy. She's planning on more pictures later on.
I 100% trust Evleaks...I never have recalled them being wrong before so I won't doubt the November 1st date. And the fact that its coming to Sprint C:
Ugh... sucks being on the east coast and needing to be at work at 6am on weekdays, 5am on weekends. What time of day is typical for announcements?Hmm, announcement is coming "soon".
If I were you, I would get those accounts set up and ready for Google Play.This weekend will be fun.
Only wrong once, that I can recall, but they quickly acknowledged it.
https://twitter.com/evleaks/status/376980602542501888
https://twitter.com/evleaks/status/377793294253568000
The back button (in Gingerbread at least...) annoys me in that I can launch something like Facebook and be on someone else's profile / notifications / whatever, hit the back button expecting to be dropped off at the FB home screen but it exits FB altogether. I get back in, now I'm at the home screen. I prefer the way iOS handles it where the home button takes me home / back button within an app just takes me up a level within the app itself.I'm assuming this is referring to your highway analogy? If so, no one said it wasn't logical, only that it was irrelevant.
And speaking about logic, the moment I pointed out that your "solution" to the Back button would put us in an infinite loop between two screens should have been the logical moment when you gave up your argument. You sort of did by saying "well, then there's no real way to make the Back button work right." But there is. And it's Google's way. The issue comes when developers don't follow the guidelines of the Back button. This is partly to blame on Google, too, but it doesn't mean the Back button in itself is "broken." You keep talking about logic -- why are you having so much trouble understanding it here?
As I've said, even while the Back button is once in a rare while inconsistent, it's still leagues better than what you want the Back button to do.
Also...
Since our conversation about the Back button, I've been paying close attention to what the Back button does. It makes perfect sense. There are many examples where apps have to launch another app, wherein if you press the back button, it goes back to the previous app. For example? Say you're browsing Flipboard and you want to "View on Web." When you click that, what does it launch? Chrome (or whatever default browser you use). Why? Because Flipboard is not a web browser. It has to, in essence, "borrow" another app to accomplish the task. And so, when you hit the Back button after it launches Chrome, it goes back to Flipboard. This makes perfect sense because the OS still assumes you are using Flipboard. It must still assume you're using Flipboard because all you asked was to view an article on the web via Flipboard. There are many many examples of apps doing this, "borrowing" another app to accomplish a task because the original app can't.
However, if you actually chose the App Switcher (like in your original example) and switch from Flipboard to Chrome, and hit the Back button then, it takes you back within Chrome. The OS now assumes, per your command of using the App Switcher, that you're essentially done with Flipboard and want to use Chrome actively.
I've used Google's own description to explain this, others have pointed to Google's own developer guidelines for the Back button to demonstrate this, and I've used countless examples (including your own) to demonstrate why the Back button, at its core, works and works brilliantly and logically. But you don't get it. Not only do you not get it, but you want the Back button to do something inherently illogical, which undermines the App Switcher button, and essentially destroys the point of the back button. So, are you sure I'm the one having trouble grasping logic here? Might want to reflect on that, Captain-of-Logic.
Yeah. I chock that up to more confusion than being wrong. Regardless, when release/event date draws near, Evleaks is a sniper. He's always on target.
I'd count on something November 1st.
It's looking more like Google will just do a soft announcement and/or a tiny event for this (ala the Google+ presentation). Hopefully that's before November 1st.
It's looking more like Google will just do a soft announcement and/or a tiny event for this (ala the Google+ presentation). Hopefully that's before November 1st.
I think they may do something tomorrow and say, "goes on sale Friday"
It was taken by Nickyyy. She's planning on more pictures later on.
My only question is what is the Nexus 5 doing on the screen? Is that is just the protective screen they put on for shipping, or is that going to be the new boot up screen?
That make sense. Yea from what I have heard in rumors, and those videos we got early on. The boot up is going to be like the GPE phones.Apparently it's the wrapping, the person who took the picture works at a phone store and they got the phone in stock. It's not necessarily the poster's own phone which makes sense since otherwise we would have gotten more pictures and maybe a video instead of this fast sneaked photo.
If the camera is as good as my GS3 then ill be fine with it. If it stinks and the battery isnt that great then ill go with the G2.
Im ready for a new phone so this anouncement is holding me up,lol.
The back button (in Gingerbread at least...) annoys me in that I can launch something like Facebook and be on someone else's profile / notifications / whatever, hit the back button expecting to be dropped off at the FB home screen but it exits FB altogether. I get back in, now I'm at the home screen. I prefer the way iOS handles it where the home button takes me home / back button within an app just takes me up a level within the app itself.
I think they may do something tomorrow and say, "goes on sale Friday"
The day before would be even better, as then people wouldn't be driving around, checking their smartphones for announcements and not looking out for small children.Yup. A Halloween announcement for kit kat makes the most sense. Though I guess a day after is okay too.
I see the photo must have been taken with a Nexus 4. I'd recognize that lack of focus anywhere!Unboxed by someone somewhere.
The day before would be even better, as then people wouldn't be driving around, checking their smartphones for announcements and not looking out for small children.
Really, in the interests of child safety, they should announce today. And, hey, put the Nexus 5 up for sale as well. Just, you know, for the kids. To keep them safe.
I see the photo must have been taken with a Nexus 4. I'd recognize that lack of focus anywhere!
She's a beauty. I see the photo was taken by an HTC One (in that it's blurry and it sucks).![]()
To me. It doesn't look like Google really wants to sell many Nexus 5's.
What makes you say this? Because it hasn't been announced yet?
Last year, Google announced it at the end of October, and released it early/mid November. They're still, more or less, on track to do that this year.
I think Google wants to and expects to sell many Nexus 5's, not necessarily for sales numbers' sake, but to get Android out to as many people as they can.
To me. It doesn't look like Google really wants to sell many Nexus 5's.
They have never sold Nexus in volume to began with. And google doesn't care about the holiday selling season either.
I just want to order the nexus 5. If I get it before end of December I am fine.
I think they are well aware of the interest in the N5 and if the new Nexus 7 launch is anything to go by then we will see a lot of N5's in stock and available at stores such as Best Buy.
The N7s weren't.But won't the Best Buy phones be marked up?