Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Nexus 5
- Thread starter Explicitic
- Start date
- Sort by reaction score
I don't think they came close to selling 1 million of them. They don't advertise and its only really a big deal amongst the forum peeps.
Yeah, Gingerbread... I have a Galaxy S, model SGH-T959V. I could probably have rooted it and had a generally less frustrating experience over the last 8 months or so, but I've been busy with a lot of other things going on in life. Once I finally had some time on my hands it seemed as though the Nexus 5 was right around the corner and here we are.
I've never upgraded from one Android device to another so I'm assuming that the few apps I've downloaded will load onto the new phone after a quick trip to the Google Play store.
Yup. Many Best Buys had them (and sold them) before the official launch date, actually. It'd be great if that happened with these.
----------
I'd also recommend something like Helium (I bought the pro license for a few bucks) - it will allow you to backup settings and such for most apps and then download them to your new device. Not perfect, but a lot easier than redoing it all from scratch.
You need to install the apps first via Play, but that's pretty simple, as you said.
Where are they getting a production Nexus 5 to do these benchmarks? What is the basis for 'best gaming' phone? As a user, a 3.99" display, at 720p resolution and no game controller support doesn't seem like it would strike me as 'best gaming' anything?
Good timing. Going from Gingerbread to Kit Kat will be a world of a difference.
A Universe of a difference!
Ah yes, the typical post "I'm done" talk. I am sorry you find it so difficult to have a discussion when people don't agree with you.
Lets break this down.
GPE phones go through manufacturers. Manufacturers already have optimized drivers. They spend time with the manufacturers before being pushed out. They get decent battery life.
Nexus 4, for example, did not go through manufacturer. Did not spend time with LG who made the optimized drivers. It gets worse battery life compared to its skinned cousin.
So if we have these example where one gets good battery life and the other doesn't, we simply try and find the discrepancy. The difference here is the time with the manufacturer and likely the drivers.
So analogies to demonstrate the logic of an argument is now irrelevant? Or are you just saying that because you realized you are wrong?
You are making the assumption that my argument was for one specific way to be best, when that is not true at all. Maybe try and understand the argument before making assumptions like that.
If you put it in quotes then I must have said that, except I didn't. Making stuff up again are we? I was arguing from the very beginning that it is inconsistent. Having one button a name that suggests various actions is difficult. It can be done, I even suggested a good way, which you likely didn't read. But right now, Google's implementation of a "back" button does not always take oyu back. Why are you having so much trouble understanding it here?
If I am going to entertain your excuse for an "argument", who cares if it is Google or the developers? The fact of the matter is that it is inconsistent and doesn't always take you back despite the name of the button. Simple logic. Why are you having so much trouble understanding it here?
You clearly don't remember anything I said and are just making stuff up at this point. I was pointing out the consistencies of the back button. You with your blind bias in Google will back them up to no end. If you remember correctly, which you never do, you will remember that my suggestion was to simply add a double tap on the back button to quickly go to your last app.
Yes, they "borrow" apps. Has this ever been a point of disagreement? Or are you just getting off topic?
There is your mistake. One point I brought up way earlier was your "borrowing" example where hitting the back button didn't take me back. Or in a few cases going into an app from the switcher and then hitting the back button, despite not being at the most back position of the app, took me to the home screen. I am talking about inconsistencies here.
Except where you avoid their description saying it will always take you to your previous screen even if it is another app, which it does not.
Funny. Others have also pointed to the Back button description in the Nexus 4 guide that says it will always go to your previous screen.
First off, if you are going to say it is illogical then you better explain why. So explain how a button that is literally called "back" always taking you back to your last screen is illogical. If we want to get really technical, an infinite loop, although not user friendly, would be the most logical! But of course, that is not what I am suggesting nor have I ever suggested it. I have been talking about the inconsistencies to show how the back button is illogical. My proposed solution includes the back button having a different name, keeping its current functionality, and adding a quick double tap to go to the previous app without having to launch the app switcher and then tap on the second app.
No need. Already proven you wrong.
Lets break this down.
GPE phones go through manufacturers. Manufacturers already have optimized drivers. They spend time with the manufacturers before being pushed out. They get decent battery life.
Nexus 4, for example, did not go through manufacturer. Did not spend time with LG who made the optimized drivers. It gets worse battery life compared to its skinned cousin.
So if we have these example where one gets good battery life and the other doesn't, we simply try and find the discrepancy. The difference here is the time with the manufacturer and likely the drivers.
This is what, the 10th time you've said that? I hope you know nobody actually believes you.
Where is your evidence for all these claims? Has there been a study? An article? An actual test? A manufacturer saying that the reason the Optimus G gets 2+ hours of battery life is cause we tinkered with the drivers? I'm genuinely asking. Like I said before, if this is true, the evidence would be worth sharing and it'd be interesting to discuss. Or else, why waste my time based on what you think happened.
Even if we were to entertain your assumption, it begs the question why Google wouldn't have LG or whoever optimize the drivers for the Nexus phone. If that's all it took to add a whopping 2+ hours of battery life (talk time?), why wouldn't they do it? Why wouldn't they take the time, with months of development, to optimize their OS to the hardware that they've decided on?
Again, if there is evidence of this, it's very well worth sharing. And I'd then completely understand your concerns being carried over to the Nexus 5. Cause then, presumably, they may not optimize for the Nexus 5. I'm merely asking for evidence.
Last edited:
Strausd,
In regards to
LG does not write drivers for hardware components in their phones and aside from screens I dont believe they actually make the parts. I would imagine that is done by the parts manufacturer, Qualcomm and whatnot. The latest fight over nexus images involved Qualcomm not wanting to release the code, not LG.
I would also wager this OEM optimization period is built into the core development of android. After all, nexus is the design spec for OEMS. To say they dont optimize before release is silly IMO. Its just built into the prerelease workload. Then other OEMS like Samsung and HTC Google editions get moving with their updates after nexus has already been optimized before the update was ever released.
I would think google is working with the same driver base as LG
If LG does repackage the drivers I believe the scenario would be similar to Dell offering video card driver updates on their website, when you could just go straight to the source of ATI/Nvidia to get them. Is Dell really rewriting these drivers for better optimization than the company that actually built the part? I don't think so.
I really don't think LG is the gatekeeper of drivers for outsourced SOC / GPU / Radio etc, these manufacturers make their products with android as their purpose.
In regards to
LG does not write drivers for hardware components in their phones and aside from screens I dont believe they actually make the parts. I would imagine that is done by the parts manufacturer, Qualcomm and whatnot. The latest fight over nexus images involved Qualcomm not wanting to release the code, not LG.
I would also wager this OEM optimization period is built into the core development of android. After all, nexus is the design spec for OEMS. To say they dont optimize before release is silly IMO. Its just built into the prerelease workload. Then other OEMS like Samsung and HTC Google editions get moving with their updates after nexus has already been optimized before the update was ever released.
I would think google is working with the same driver base as LG
If LG does repackage the drivers I believe the scenario would be similar to Dell offering video card driver updates on their website, when you could just go straight to the source of ATI/Nvidia to get them. Is Dell really rewriting these drivers for better optimization than the company that actually built the part? I don't think so.
I really don't think LG is the gatekeeper of drivers for outsourced SOC / GPU / Radio etc, these manufacturers make their products with android as their purpose.
Last edited:
Not that I would like to join this argument, just my two cents.
Can't it be a new kernel? Don't the Nexus devices run on the AOSP stock kernel? That's why people release new ones that offer better performance/more battery life. However it could be possible that these kernels need some of the core components of the skin. That could be why you can't run a touchwiz kernel on a Motoblur device? Im not very good with software and understanding how all this stuff works, but I don't see drivers being an issue. Skins add more animation which use more GPU/CPU resources and in turn more battery life. If it were as simple as a driver I'm pretty sure Google would either A.) add it to the AOSP code or B.) throw it in the Nexus devices build.
Or it could come down to a totally different thing not related to software at all, maybe they use a cheaper battery in the Nexus 4 vs OG.
Once again I don't want to argue I just find this discussion interesting
The Optimus G with CyanogenMOD still gets significantly better battery life than the Nexus 4.
Dummy/production unit video although the accent in the video might indicate that it is an actual final product in some phone shop.
No way on verizon but yes on others, where did you read that?
Verizon won't sell you a device this unlocked!
Sure.
I have no clue what causes the Nexus 4 battery issues. Only one person here seems confident they do. Straus. I'm talking about Straus.
----------
Verizon doesn't deserve a Nexus phone. What they did with the Galaxy Nexus should get them permanently banned from Nexus phones.
Sure.
I have no clue what causes the Nexus 4 battery issues. Only one person here seems confident they do. Straus. I'm talking about Straus.
I know, I think I'm gonna go with they used cheap batteries. When I had my HTC Aria I bought a couple of Chinese knockoff batteries with the same mah rating and everything yet they died faster.
Yep, yep, I'm locking in my answer. Batteries, final answer.
Did the layout at the Play store change? I'm referring to choosing the storage size of devices? It seems to have been updated for the Nexus 7.
I am being purely speculative based on the facts we have. When a phone goes through a manufacturer when it has stock Android, it gets better battery life. Simple logic tells us something is going on in that time the phone is with the manufacturer, how are you not getting it?
Qualcomm and such might make the initial drivers, but whether or not OEMs do any additional optimizations to have it work in certain ways with specific hardware is not totally clear. What is clear is that something it happening during that time the phone is with the manufacturer. Could it be from optimizations in the driver? Possibly. Could it be from other under the hood optimizations that Samsung and HTC are able to put on their phones and still have it considered a GPE? Also possible. But something on the software side is happening at that time.
The problem is trying to make sense of GPE phones getting similar battery life to their skinned cousins and the last Nexus phone getting poor battery life compared to its skinned cousin. The major difference between the two is the time GPE phones spend with their respective manufacturers. And I believe GPE phones have the same kernel, but someone would need to double check.
So it could potentially be drivers or other under the hood improvements. For example, HTC, Samsung, and LG could all have battery life optimizations built into their skin that is specific for their hardware. However, this could be something that isn't bloatware or unnecessary apps. This could be some under the hood battery saving feature that is completely transparent to the user. If so, it wouldn't be too crazy to think that Samsung and HTC put this on their GPE phones to help save battery life. And if it is completely transparent to the user, it wouldn't take away from it being stock Android. They could still be classified as Google Play Edition phones since they run stock Android. And since all under the hood improvements have already been written for their hardware with their skinned version, its not like they would have to recode anything. Same kind of thing if they have more optimized drivers to work better in combination with certain hardware.
If CyanogenMod doesn't touch the hardware drivers, wouldn't that bring credibility to the drivers argument?
You should stop making crap up. I have said multiple times that maybe it is stock Android, maybe it is drivers, or maybe it is other under the hood improvements. Maybe you don't understand the meaning of the word "maybe." But just to let you know, it is far from a word that conveys confidence. I also multiple times have used words like "would," "could," "likely," "possibly," etc. A little critical reading could do you good.Sure.
I have no clue what causes the Nexus 4 battery issues. Only one person here seems confident they do. Straus. I'm talking about Straus.
And it seems like through all your off topic nonsense, you have forgotten the reason for this discussion. I am discussing this to express my skepticism that the Nexus 5 will have great battery life. Nexus 4 has bad battery life compared to the OG, and I am skeptical that the N5 will have good battery life. I am skeptical it will even have bad battery life compared to an LG G2 if it had a 2300 mAh battery.
----------
Since Google does typically skimp on some areas to keep costs down, that is another likely possibility. Which wouldn't help in an argument saying that the Nexus 5 will have much improved battery life as Google might be doing the same thing this year.
And with GPE phones, they use all the same hardware as their skinned cousin. Whereas the Nexus 4 had all the same major specs, but not all the same hardware.
In which case, this actually makes me even more skeptical of the N5 battery life as Google skimping on quality batteries makes sense to keep costs down.
I'd have to refer to someone with more experience than me -- maybe someone from XDA -- but my understanding is that CyanogenMod doesn't contain stock drivers because they are closed source.
Launch is tomorrow! Finalllllllly!
You ought to get in the habit of linking us to where you read your info. So with that in mind, source, please?
----------
He looks happy.
Looks pretty darn similar to what Evleaks put out a few days ago. Like I said, looks like the final product!
