We understand this but I don't think Apple's target demographic does (like my Nana, for example). It's a very odd thing for Apple to market. Besides, the current ARMv7 designs are already woefully overpowered for what 99.9% of people use their phones for. ARMv8 cores currently offer no practical or perceivable benefit yet outside of servers--which might be part of the reason no one has really jumped on the Cortex-a57 yet.
I think Android is targeted more because it isn't inherently tied to the Play store, and not so much because of devices not being updated. The app signature verification works for 2.3 and up, which covers 96% of Google's Android devices. Getting malware on a phone or tablet still generally requires installing a malicious app, and it's far easier to be careless about that on Android.
I'd wager that every sports fan in the world wants this, and Google is best positioned to provide it with the infrastructure they already have in place--they have live streamed events and premium channels on Youtube already. Of course it's a business move, but that doesn't preclude it from being in the best interests of consumers either.
TV coverage of sports is a mess, and it's a little different than other TV programming. Sometimes sports are blacked out of their local markets, for no reason. Some events are aired over broadcasting networks and some through cable. If your college team isn't in the top 25, you're probably not going to be watching many games on TV, similar to how the coverage of the Olympics truly sucks. There's no reason for this in the age of digital streaming. If Google can break the stranglehold of sports' coverage, it should open the door for competing providers, just like digital music.
This isn't accurate. Fastboot will only flash something that's signed by the manufacturer, unless the bootloader is unlocked, which won't matter anyway if the device is encrypted. Nexus devices are locked too, and unlocking the bootloader wipes all data, so you still won't get access to anything. ADB sideloading requires ADB to be enabled and the RSA fingerprint of the PC to be accepted.
My understanding is that the Play store was patched, so this vulnerability can't be exploited for apps uploaded to and downloaded from there. The AOSP patch addresses the part of Jellybean that verifies the cryptographic signature of sideloaded apps. That has to be updated on the device end--it's the "Verify Apps" option in the security menu. It's not part (yet?) of Google Play Services; it works without GApps installed. However, if you don't download.apk's from the internet, which 99.9% of people don't do, then it's immaterial whether your device is patched because that function isn't being used anyway.
So you're absolutely right that it was blown out of proportion.
Disney has made an innumerable amount of money on others' works in the public domain, like Grimms' Fairy Tales. Yet, they have lobbied and pushed for copyright laws to prevent their work from being used the same way.
They have an ARM license and I think they tested a 28nm SOI ARM design a while back. They may not be as advanced as Intel, but I don't think they are over capacity either.
Apple has licensed the ARM cpu design, PowerVR GPU, and Qualcomm radios for years. They may design the layout, but not the IP. As far as I'm aware, only Broadcom, Qualcomm, and Marvell have ARM architecture licenses that allow them to design custom logic compatible with the v7/v8 instruction sets. Everyone else is building SOC's with the reference implementation provided by ARM.
The damage has been done. Chasing him down and prosecuting him is just a waste of taxpayer resources, and likely won't prevent any more leaks anyway. The self-aggrandizing NSA hypocrites need to salvage their egos and move on.
There's really no reason to buy a Nook now that there are better tablets at the same pricepoint and comparable ones for less. A lot has changed in two year's time.
They're using an OMAP SOC for the explorer editions. TI stopped development and is phasing out manufacturing of mobile chips. For Google to deliver the millions of Glass devices that they anticipate, they must find another hardware solution. That's a pretty good indication that the current hardware isn't final. The 4430 is overkill anyway, and a more purpose-designed SOC should be more cost-effective and yield improved battery life.
The problem with these patent agreements with Microsoft is that the details are kept confidential. No one but Microsoft knows what the patents cover, the conditions or fees, and which patents Microsoft is licensing in return--which is more likely to be the case. Microsoft releases these puerile press releases announcing something that probably happens in the business world on a daily basis, yet only they feel the need to do this. I have my doubts that these agreements are as one-sided as Microsoft brags, especially since ZTE is a telecommunications giant in China.
My transformer came with Polaris and I also own Quickoffice. They're both pretty good for document compatibility, but the interfaces take a little getting used to. That's the main gripe I have. However, with the tablet is docked in the keyboard, it's much more intuitive--like running an office suite on a laptop.
It may not be the most elegant solution, but hosting your own Mumble server works pretty well for secure private IM and voice chat. There's a really slick Android client called Plumble, and I believe iOS has a basic one as well. The built-in authentication and encryption is sufficient, and the newer builds support the OPUS codec.
Isn't this more of a problem of enforcing device security policies? If the data is encrypted, does it really matter if the device is locked by PIN, pattern, fingerprint, facial recognition, or some other mechanism?
I think there's a bigger picture here that most people don't consider. Internet sales, except for digital downloads, require shipping...and that's not free. I might be wrong, but I imagine that some portion of these shipping costs that everyone pays find their way back to the states in different forms such as road tolls, airport fees, income taxes of employees and so forth. In fact, I'd wager that the USPS would be in far worse shape if shipment of online goods hadn't filled the hole that email has caused. Again, I could be wrong, but I don't think that the states are being screwed like they claim they are, money is just coming to them in a different form. It will be interesting to see what effect this will have on our economy--will consumer confidence fall? For states like CT with huge budget deficits, will increased taxation of consumers take the place of making cuts to overspending?
*There is a standard way to exit...it's called the home button. Really.
*There could be an option to unlock the homescreen orientation, but only you and a hand-full of people would probably notice. Really.
*MTP sucks...I'll give you that, though the monolithic data partition was the right thing to do. Something like Airdroid is probably the way to go. It's fast enough for most things over wifi, and if you use USB tethering with it, you can tranfer gigabytes in minutes. QtADB isn't bad either.
*I think I've only seen maps crash once. Ever. Honest.
*Given the amount of time Google has spent getting the Android pieces accepted into the mainline kernel source, I don't know how one could argue that they are pretending that Android isn't Linux.
*Unlocking and relocking the bootloader, and rooting is absolutely perfect on the Nexus. Period. I'd say it's probably half-hearted on non-Google devices because that process sometimes wipes the DRM keys and you have to either flash a custom ROM or modify some root files to get that functionality back. There's nothing Google can do about that though.
*It would be nice if Google would collaborate more with the community on merging patches and bug fixing, but I don't know that Android would survive solely as a community project. This industry is moving fast.
I still think Google should have thrown their money at Libreoffice and financially supported the efforts to port it to Android, instead or in addition to purchasing Quickoffice.
And it's hyperthreaded, so both are capable of processing the same number of threads. Atom wins some and loses others, despite a significant clockspeed advantage.
For myth 2, the A15 design is significantly faster than A9, which was a big step up from the A8's. In four years we've gone from A8 to A15. It's quite impressive to consider how fast the phones in our pockets have gotten is such a short time, and I think it's a little early to forecast the trend. For myth 3, the Qualcomm Krait design is pretty equal to the A15 reference platform, and it's using a very power-efficient asynchronous design. Big-little isn't necessary, it's a less-elegant design solution that ARM chose. I think by the holiday season, the market will be flooded with A15-based phones. I believe the Apple A6 is also an A15 reference CPU, since they don't have an architectural license like Qualcomm and Marvell.
So if you leave your garage door open, the police can also walk up your driveway and search your house because it's not locked...otherwise they need a warrant. That makes sense.
Slashdot Mirror
We understand this but I don't think Apple's target demographic does (like my Nana, for example). It's a very odd thing for Apple to market. Besides, the current ARMv7 designs are already woefully overpowered for what 99.9% of people use their phones for. ARMv8 cores currently offer no practical or perceivable benefit yet outside of servers--which might be part of the reason no one has really jumped on the Cortex-a57 yet.
It's not by Google, but it does what you're asking for: http://prometheusx.net/
I think Android is targeted more because it isn't inherently tied to the Play store, and not so much because of devices not being updated. The app signature verification works for 2.3 and up, which covers 96% of Google's Android devices. Getting malware on a phone or tablet still generally requires installing a malicious app, and it's far easier to be careless about that on Android.
I believe many automotive onboard computers are PPC based also.
I'd wager that every sports fan in the world wants this, and Google is best positioned to provide it with the infrastructure they already have in place--they have live streamed events and premium channels on Youtube already. Of course it's a business move, but that doesn't preclude it from being in the best interests of consumers either.
TV coverage of sports is a mess, and it's a little different than other TV programming. Sometimes sports are blacked out of their local markets, for no reason. Some events are aired over broadcasting networks and some through cable. If your college team isn't in the top 25, you're probably not going to be watching many games on TV, similar to how the coverage of the Olympics truly sucks. There's no reason for this in the age of digital streaming. If Google can break the stranglehold of sports' coverage, it should open the door for competing providers, just like digital music.
This isn't accurate. Fastboot will only flash something that's signed by the manufacturer, unless the bootloader is unlocked, which won't matter anyway if the device is encrypted. Nexus devices are locked too, and unlocking the bootloader wipes all data, so you still won't get access to anything. ADB sideloading requires ADB to be enabled and the RSA fingerprint of the PC to be accepted.
My understanding is that the Play store was patched, so this vulnerability can't be exploited for apps uploaded to and downloaded from there. The AOSP patch addresses the part of Jellybean that verifies the cryptographic signature of sideloaded apps. That has to be updated on the device end--it's the "Verify Apps" option in the security menu. It's not part (yet?) of Google Play Services; it works without GApps installed. However, if you don't download .apk's from the internet, which 99.9% of people don't do, then it's immaterial whether your device is patched because that function isn't being used anyway.
So you're absolutely right that it was blown out of proportion.
Disney has made an innumerable amount of money on others' works in the public domain, like Grimms' Fairy Tales. Yet, they have lobbied and pushed for copyright laws to prevent their work from being used the same way.
They have an ARM license and I think they tested a 28nm SOI ARM design a while back. They may not be as advanced as Intel, but I don't think they are over capacity either.
You also have to consider the amount of fuel spent on delivering gas/diesel to filling stations.
Apple has licensed the ARM cpu design, PowerVR GPU, and Qualcomm radios for years. They may design the layout, but not the IP. As far as I'm aware, only Broadcom, Qualcomm, and Marvell have ARM architecture licenses that allow them to design custom logic compatible with the v7/v8 instruction sets. Everyone else is building SOC's with the reference implementation provided by ARM.
The damage has been done. Chasing him down and prosecuting him is just a waste of taxpayer resources, and likely won't prevent any more leaks anyway. The self-aggrandizing NSA hypocrites need to salvage their egos and move on.
There's really no reason to buy a Nook now that there are better tablets at the same pricepoint and comparable ones for less. A lot has changed in two year's time.
They're using an OMAP SOC for the explorer editions. TI stopped development and is phasing out manufacturing of mobile chips. For Google to deliver the millions of Glass devices that they anticipate, they must find another hardware solution. That's a pretty good indication that the current hardware isn't final. The 4430 is overkill anyway, and a more purpose-designed SOC should be more cost-effective and yield improved battery life.
The problem with these patent agreements with Microsoft is that the details are kept confidential. No one but Microsoft knows what the patents cover, the conditions or fees, and which patents Microsoft is licensing in return--which is more likely to be the case. Microsoft releases these puerile press releases announcing something that probably happens in the business world on a daily basis, yet only they feel the need to do this. I have my doubts that these agreements are as one-sided as Microsoft brags, especially since ZTE is a telecommunications giant in China.
My transformer came with Polaris and I also own Quickoffice. They're both pretty good for document compatibility, but the interfaces take a little getting used to. That's the main gripe I have. However, with the tablet is docked in the keyboard, it's much more intuitive--like running an office suite on a laptop.
It may not be the most elegant solution, but hosting your own Mumble server works pretty well for secure private IM and voice chat. There's a really slick Android client called Plumble, and I believe iOS has a basic one as well. The built-in authentication and encryption is sufficient, and the newer builds support the OPUS codec.
Isn't this more of a problem of enforcing device security policies? If the data is encrypted, does it really matter if the device is locked by PIN, pattern, fingerprint, facial recognition, or some other mechanism?
I think there's a bigger picture here that most people don't consider. Internet sales, except for digital downloads, require shipping...and that's not free. I might be wrong, but I imagine that some portion of these shipping costs that everyone pays find their way back to the states in different forms such as road tolls, airport fees, income taxes of employees and so forth. In fact, I'd wager that the USPS would be in far worse shape if shipment of online goods hadn't filled the hole that email has caused. Again, I could be wrong, but I don't think that the states are being screwed like they claim they are, money is just coming to them in a different form. It will be interesting to see what effect this will have on our economy--will consumer confidence fall? For states like CT with huge budget deficits, will increased taxation of consumers take the place of making cuts to overspending?
*There is a standard way to exit...it's called the home button. Really.
*There could be an option to unlock the homescreen orientation, but only you and a hand-full of people would probably notice. Really.
*MTP sucks...I'll give you that, though the monolithic data partition was the right thing to do. Something like Airdroid is probably the way to go. It's fast enough for most things over wifi, and if you use USB tethering with it, you can tranfer gigabytes in minutes. QtADB isn't bad either.
*I think I've only seen maps crash once. Ever. Honest.
*Given the amount of time Google has spent getting the Android pieces accepted into the mainline kernel source, I don't know how one could argue that they are pretending that Android isn't Linux.
*Unlocking and relocking the bootloader, and rooting is absolutely perfect on the Nexus. Period. I'd say it's probably half-hearted on non-Google devices because that process sometimes wipes the DRM keys and you have to either flash a custom ROM or modify some root files to get that functionality back. There's nothing Google can do about that though.
*It would be nice if Google would collaborate more with the community on merging patches and bug fixing, but I don't know that Android would survive solely as a community project. This industry is moving fast.
I still think Google should have thrown their money at Libreoffice and financially supported the efforts to port it to Android, instead or in addition to purchasing Quickoffice.
And it's hyperthreaded, so both are capable of processing the same number of threads. Atom wins some and loses others, despite a significant clockspeed advantage.
For myth 2, the A15 design is significantly faster than A9, which was a big step up from the A8's. In four years we've gone from A8 to A15. It's quite impressive to consider how fast the phones in our pockets have gotten is such a short time, and I think it's a little early to forecast the trend. For myth 3, the Qualcomm Krait design is pretty equal to the A15 reference platform, and it's using a very power-efficient asynchronous design. Big-little isn't necessary, it's a less-elegant design solution that ARM chose. I think by the holiday season, the market will be flooded with A15-based phones. I believe the Apple A6 is also an A15 reference CPU, since they don't have an architectural license like Qualcomm and Marvell.
So if you leave your garage door open, the police can also walk up your driveway and search your house because it's not locked...otherwise they need a warrant. That makes sense.