{"id":29579,"date":"2015-03-09T20:40:54","date_gmt":"2015-03-10T00:40:54","guid":{"rendered":"http:\/\/www.opensource.im\/uncategorized\/google-confirms-poor-performance-is-to-blame-for-reneged-android-lollipop-encryption-pledge.php"},"modified":"2015-03-09T20:40:54","modified_gmt":"2015-03-10T00:40:54","slug":"google-confirms-poor-performance-is-to-blame-for-reneged-android-lollipop-encryption-pledge","status":"publish","type":"post","link":"https:\/\/euvolution.com\/open-source-convergence\/encryption\/google-confirms-poor-performance-is-to-blame-for-reneged-android-lollipop-encryption-pledge.php","title":{"rendered":"Google confirms poor performance is to blame for reneged Android Lollipop encryption pledge"},"content":{"rendered":"<p><p>    It turns out there was    something to the report thathardware    performance was to blame for Google backing off its    encryption requirement for new Lollipop devices.  <\/p>\n<p>    Google issued a     statement to Engadget, confirming that many phones wont    come with encryption turned on, a reversal of the companys    original plans:  <\/p>\n<p>    In September, we announced    that all new Android Lollipop devices would be encrypted by    default. Due to performance issues on some Android partner    devices we are not yet at encryption by default on every new    Lollipop device. That said, our new Nexus devices are encrypted    by default and Android users (Jelly Bean and above) have the    option to encrypt the data on their devices in Settings    -> Security - >Encryption. We remain firmly    committed to encryption because it helps keep users safe and    secure on the web.  <\/p>\n<p>    Such problems started showing    up as early as November, when a test showed flipping on    encryption     tanked Nexus 6 storage performance. This issue has clearly    hit enough Android devices to compel Google to back off from    its original plan to require encryption in all new phones    running Lollipop.  <\/p>\n<p>    Fortunately, you can turn    this security feature on yourself by following     our encryption guide.  <\/p>\n<p>    Why this    matters:Encryption-by-default is long overdue    for Android devices. When its upgrade time, youre likely to    sell off or trade in your phone, meaning someone else will be    using your old device. If your data isnt encrypted, someone    with nefarious motives could possibly gain access to your old    stuff.  <\/p>\n<p>    For comprehensive coverage of the Android ecosystem, visit    Greenbot.com.  <\/p>\n<p>        Derek Walter is a freelance technology writer based in        Northern California. He is the author of Learning MIT App        Inventor, a hands-on guide to building your own Android        apps.        More by Derek        Walter      <\/p>\n<p>        Your message has been sent.      <\/p>\n<p>        There was an error emailing this page.      <\/p>\n<p><!-- Auto Generated --><\/p>\n<p>Continue reading here:<br \/>\n<a target=\"_blank\" href=\"http:\/\/www.pcworld.com\/article\/2893013\/google-confirms-poor-performance-is-to-blame-for-reneged-android-lollipop-encryption-pledge.html\/RK=0\/RS=z__DstfOowEo6VOwKuAfwICC58k-\" title=\"Google confirms poor performance is to blame for reneged Android Lollipop encryption pledge\">Google confirms poor performance is to blame for reneged Android Lollipop encryption pledge<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p> It turns out there was something to the report thathardware performance was to blame for Google backing off its encryption requirement for new Lollipop devices. Google issued a statement to Engadget, confirming that many phones wont come with encryption turned on, a reversal of the companys original plans: In September, we announced that all new Android Lollipop devices would be encrypted by default<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[45],"tags":[],"class_list":["post-29579","post","type-post","status-publish","format-standard","hentry","category-encryption"],"_links":{"self":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts\/29579"}],"collection":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/comments?post=29579"}],"version-history":[{"count":0,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts\/29579\/revisions"}],"wp:attachment":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/media?parent=29579"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/categories?post=29579"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/tags?post=29579"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}