It's not the lack of a Start Button that gets me. It's the whole 'forced touch-UI' experience, the fact that half the system's settings are in a classic dialog and the other half are in a Metro dialog, the complete lack of warning when the system is going to kick you in one direction or another. Performance-wise, I'm sure it's fine. But it's the user experience that completely turns me off. If they'd done it right the first time (i.e. Windows 10), then I'd probably have taken the time to upgrade. But Win8/8.1 will never have a place on any system I'm using.
Well duh, who would willingly want Windows 8 on their PC? I've been refraining from buying a new Asus ROG system until Windows 10 is available on them.
If Comcast is in the wrong here, and it wouldn't surprise me if they were, this guy is gonna be able to come in to a whole lot of money. Both from Comcast and his former employer.
All the same, internal or not, why would a guard have access to sensitive and classified internal Google data? If they do, someone needs to rapidly fire whoever is handling information security and replace them with someone competent.
What kind of idiot gives physical security staff access to private systems they don't need? Access controls are paramount for something like this. Guards shouldn't be given access to anything that isn't directly required by their position.
Are you high? Milestone 11 doesn't exist yet. It probably hasn't even been frozen yet. The most recent Milestone release is 10, which has worked flawlessly with my N7-2012, Netflix included.
How? CM already doesn't have GApps by default since at least CM7, because Google put a stop to it. You can't stop people from flashing GApps to a CM running device.
Then why did they throw a shitfit when they found out CM actually did bundle GApps early in it's lifespan? Ever since CM7 (So far as I recall, could be as early as 6), you have to flash GApps seperately or else the system is somewhat useless initially. That didn't used to be the case, nor is it with any CM edition devices like Oppo's N1 or the OnePlus One.
You do know that so long as you're running AOSP, even the compiled images that Google releases, so long as you can enable developer settings, mock locations can be enabled. You can do it from any Nexus, Moto X/G/E, and CM device. And even CM has Developer Settings disabled by default. So you can't really start complaining about Google not allowing fake geolocation, you just have to be less of an idiot to enable it.
They're still just a voip provider. You try taking a Sprint phone to them and they'll turn you out the door. Doesn't matter if they're riding Sprint's network. They won't let you use a phone without their firmware, which is only available for a scant few phones.
Republic Wireless isn't a cell carrier, they're a voip provider. If they were a real carrier, you'd be able to bring a GSM phone to them for use. You have to buy RW's phones to use their serivce, because the ROM they use has baked-in RW voip functionality.
It's not that they're fucksticks... Well, no more than usual. The Nexus 5 just doesn't have the frequency bands that Verizon requires for their network. Hardware limitation as opposed to a carrier limitation.
True, but that's the point that a I posit. But the way I'd run the experiment would see if carrier bloat has that much of an impact or if it's solely a network/hardware reason for the battery drain.
If you're testing to see if the battery drain is hardware vs network vs software, then it actually is reasonable to have a phone tested that has no Verizon bloatware at all, but still able to access the network. To do it comprehensively, across all 4 major US carriers, you'd need 8 phones. Four of them are carrier stock, no modifications at all, and updated to the most recent carrier approved version of Android. The remaining four are CyanogenMod flashed to the equivilent version that the carrier allows. i.e. the Verizon Stock phone only goes up to 4.3, then the Verizon CM phone gets flashed to the same Android version. At that point, you're able to test to see if carrier bloatware has an effect from any of them and which device lasts regardless.
I'd like to see what this test looks like with all the phones involved running the same software load. i.e. No Verizon crapware. Just scout out a handset available on all 4 carriers, install Cyanogenmod on one and leave a second one stock. Then we should get a more accurate picture of what's going on here.
Nor I. If I need GPU performance, I'm always going to go discrete with nVidia hardware. For efficiency, I'll take the i3's that make a joke out of these APUs.
Slashdot Mirror
It's not the lack of a Start Button that gets me. It's the whole 'forced touch-UI' experience, the fact that half the system's settings are in a classic dialog and the other half are in a Metro dialog, the complete lack of warning when the system is going to kick you in one direction or another. Performance-wise, I'm sure it's fine. But it's the user experience that completely turns me off. If they'd done it right the first time (i.e. Windows 10), then I'd probably have taken the time to upgrade. But Win8/8.1 will never have a place on any system I'm using.
Well duh, who would willingly want Windows 8 on their PC? I've been refraining from buying a new Asus ROG system until Windows 10 is available on them.
If Comcast is in the wrong here, and it wouldn't surprise me if they were, this guy is gonna be able to come in to a whole lot of money. Both from Comcast and his former employer.
I'll pick the one that leads to unscrupulous employees getting fired as quickly as possible. Escorted outside immediately by those very same guards.
All the same, internal or not, why would a guard have access to sensitive and classified internal Google data? If they do, someone needs to rapidly fire whoever is handling information security and replace them with someone competent.
What kind of idiot gives physical security staff access to private systems they don't need? Access controls are paramount for something like this. Guards shouldn't be given access to anything that isn't directly required by their position.
Are you high? Milestone 11 doesn't exist yet. It probably hasn't even been frozen yet. The most recent Milestone release is 10, which has worked flawlessly with my N7-2012, Netflix included.
How? CM already doesn't have GApps by default since at least CM7, because Google put a stop to it. You can't stop people from flashing GApps to a CM running device.
Then why did they throw a shitfit when they found out CM actually did bundle GApps early in it's lifespan? Ever since CM7 (So far as I recall, could be as early as 6), you have to flash GApps seperately or else the system is somewhat useless initially. That didn't used to be the case, nor is it with any CM edition devices like Oppo's N1 or the OnePlus One.
You do know that so long as you're running AOSP, even the compiled images that Google releases, so long as you can enable developer settings, mock locations can be enabled. You can do it from any Nexus, Moto X/G/E, and CM device. And even CM has Developer Settings disabled by default. So you can't really start complaining about Google not allowing fake geolocation, you just have to be less of an idiot to enable it.
They're still just a voip provider. You try taking a Sprint phone to them and they'll turn you out the door. Doesn't matter if they're riding Sprint's network. They won't let you use a phone without their firmware, which is only available for a scant few phones.
Republic Wireless isn't a cell carrier, they're a voip provider. If they were a real carrier, you'd be able to bring a GSM phone to them for use. You have to buy RW's phones to use their serivce, because the ROM they use has baked-in RW voip functionality.
But are you going to be foolish enough to risk undervolting the card?
Um, on the high end of the spectrum, a pair of 6-pin PCIe power connectors are still needed. Even with the 970.
They shouldn't bother with XP upgrades, period. Let the dinosaur die already.
You didn't do your research, huh? They're not actually going to go back to Wind'ohs.
It's not that they're fucksticks... Well, no more than usual. The Nexus 5 just doesn't have the frequency bands that Verizon requires for their network. Hardware limitation as opposed to a carrier limitation.
Yeah, except you can't use a Nexus 5 on Verizon to run that portion of the network vs software tests.
True, but that's the point that a I posit. But the way I'd run the experiment would see if carrier bloat has that much of an impact or if it's solely a network/hardware reason for the battery drain.
If you're testing to see if the battery drain is hardware vs network vs software, then it actually is reasonable to have a phone tested that has no Verizon bloatware at all, but still able to access the network. To do it comprehensively, across all 4 major US carriers, you'd need 8 phones. Four of them are carrier stock, no modifications at all, and updated to the most recent carrier approved version of Android. The remaining four are CyanogenMod flashed to the equivilent version that the carrier allows. i.e. the Verizon Stock phone only goes up to 4.3, then the Verizon CM phone gets flashed to the same Android version. At that point, you're able to test to see if carrier bloatware has an effect from any of them and which device lasts regardless.
15% is why. iOS is becoming an irrelevant minority.
I'd like to see what this test looks like with all the phones involved running the same software load. i.e. No Verizon crapware. Just scout out a handset available on all 4 carriers, install Cyanogenmod on one and leave a second one stock. Then we should get a more accurate picture of what's going on here.
That fell apart because Sony didn't anticipate what direction things would take, letting Apple overtake them along with just about everyone else.
No, though Sony could have pulled it out of the fire by partnering with a more respected content vendor, instead of trying to roll their own.
Nor I. If I need GPU performance, I'm always going to go discrete with nVidia hardware. For efficiency, I'll take the i3's that make a joke out of these APUs.