or Connect
New Posts  All Forums:

Posts by EricTheHalfBee

 No way to really know how much is due to kernel exploits. I used the term "kernel" to refer to the base OS itself, outside of Google Play Services. Google Play has no ability to modify the kernel so any past (or future) exploits outside of Google Play will not be able to get updates via Google Play. All Verify Apps/Google Play will do is get the people writing malware to specifically target areas of Android that are outside their control.
If you bothered to read more about it you'd realize the "fix" in ICS was so half baked it wasn't really a fix. They did the equivalent of installing a lock on the front door but leaving the keys under the mat. There are numerous articles about how poor ASLR was in ICS. It was fully fixed in JB.No need to post something I already know. The bottom line is Google only counts devices where the user initiates access. Google used to count all automatic access (for example, if...
80%? Where did you get that figure from. According to Google, it's 64%. And as I'm sure you remember, Google changed the way they calculate the percentage of users on each version. They used to count ALL devices. Now they only count devices that SPECIFICALLY visited Google Play within the previous 7 days (in other words, the user visited the Store). Of course, when Google made this accounting change we suddenly had an increase in reported users on newer versions and a...
DING DING DINGWe have a winner. Funny to see the uninformed responses claiming you're wrong. Google Play Servics IS NOT the Android kernel, and it can't make changes to the kernel to correct security flaws.
You know exactly how to do that since it's you're trademark. Don't get offended when someone returns the favor.You shouldn't talk about security when you know nothing about how OS's are designed. For starters read this:http://en.wikipedia.org/wiki/Address_space_layout_randomizationOnly Android JB has fully implemented this feature.
There, fixed another one of your posts.
If you're part of the OHA you're not allowed to release a device running a forked version of Android. So that means Samsung can sell Android, Windows or Tizen phones. Now it appears Google doesn't even want to share the same device with another OS. It makes sense. Nothing will show a user how utterly $hitty Android is then to run it on the same device as Windows and let the user experience the glaring shortcomings first hand. And people wonder why Apple says they won't...
But but but, Android users are always telling us how Koh favours Apple and is biased against Samsung.
Who cares? Tesla is a niche player in the automotive market. Why should Apple waste time trying to get them on board?
I can see Apple finally making the move to quad core with a smaller process (like 20-22nm). The A7 cores are so far ahead of everyone else who uses ARM I just don't see how Apple is going to be able to make their usual "double the performance of last year" claim with the A8 simply by sticking to two cores and the same clock speed. But a quad core A8 (using A7 cores) would be a beast. I think Intel should be worried. Apple has been making huge improvements to their...
New Posts  All Forums: