Daily Archives: 23 Jan 2017

Official Galaxy Note 7 investigation blames small battery cases, poor welding | Ars Technica

23 Jan 2017 By in News, Technology Tags: , , ,

 

Samsung have finally revealed details regarding the battery explosions. It doesn’t stop me from keeping being a Samsung person – there’s not many other brands I trust out in the market at the moment. So I’ll keep with Samsung for now,

Two different production problems from two different suppliers killed the Note 7.

Source: Official Galaxy Note 7 investigation blames small battery cases, poor welding | Ars Technica

The Meitu selfie app unlocks your anime beauty and personal data

23 Jan 2017 By in Android, Terrorism Tags: , , , , , , ,

Meitu has been taking off — everywhere I look on my Facebook, Twitter, I see pictures run through the app.

But do you actually check to see what permissions it asks for? A crazy amount it seems. I just checked on Google Play (https://play.google.com/store/apps/details?id=com.mt.mtxx.mtxx) and these are the current permissions

Version 6.1.0.2 can access:
Device & app history
  • retrieve running apps
Location
  • approximate location (network-based)
Phone
  • read phone status and identity
Photos / Media / Files
  • read the contents of your USB storage
  • modify or delete the contents of your USB storage
Storage
  • read the contents of your USB storage
  • modify or delete the contents of your USB storage
Camera
  • take pictures and videos
Wi-Fi connection information
  • view Wi-Fi connections
Device ID & call information
  • read phone status and identity
Other
  • receive data from Internet
  • view network connections
  • change system display settings
  • full network access
  • change your audio settings
  • run at startup
  • reorder running apps
  • control vibration
  • prevent device from sleeping
  • Google Play licence check

For the most part, these aren’t too much of a concern but these two might be:

Phone
  • read phone status and identity
 Device ID & call information
  • read phone status and identity

These relate to reading the device information such as the IMEI and call information. I’m not too concerned about the call side — you can block this with later version of Android’s permission manager (and I use that a lot with different apps), but I’m not sure if I can block attempts to read phone status.

Their justification of this to track usage in China because it is blocked, I guess does make sense, but am I the only one who thinks doing it this way leaves it way too open for abuse and misuse?

Source: The Meitu selfie app unlocks your anime beauty and personal data

Update & Build Prep – Lineage OS – Lineage OS Android Distribution

23 Jan 2017 By in Android, Technology Tags: , , ,

Cyanogen’s fork is beginning to take shape. Currently my devices aren’t showing but fingers crossed it will.

Few points worth noting from their site:

  • The build roster is ever growing, but we are supporting Marshmallow and Nougat capable devices.

    • We’ll list the 80+ devices in a separate post.

  • Our release cadence will be ‘weekly’ by default (to be nice to all the donated hardware).

  • We will NOT be shipping root baked into the ROM.

    • Root will be a downloadable zip based install similar to gapps installation (only need to flash it once).
    • Home builders that want to bake su back into the ROM can use the command ‘export WITH_SU=true’ prior to building.

  • Our official builds will all be signed with a private key for authentication and signature permission control

However, also notable and I’m really happy about this:

Regarding installation, we recommend that users wipe when switching to LineageOS, and reinstall their gapps. However, we recognize that this can be time consuming, so we are offering an EXPERIMENTAL (read as, if it fails, you’ll have to wipe anyways) solution.

  • Alongside the ‘weekly’ release for your supported device, we’ll provide an EXPERIMENTAL data migration build.
  • This build will allow you to ‘upgrade’ from CM to the signed LineageOS weekly
  • This build may wipe permissions (you’ll have to re-allow app permissions), but should retain all user data
  • This build will be watermarked with an ugly banner to ensure that you don’t permanently run this EXPERIMENTAL release, and upgrade to a normal weekly after.
  • The process for this installation will be as follows:
    • Install EXPERIMENTAL migration build on top of cm-13.0 or cm-14.1 build (don’t try to install LineageOS 13.0 on top of CM 14.1, that will not work).
    • Reboot
    • Install LineageOS weekly build
    • Reboot
    • Re-setup your application permissions

Given the EXPERIMENTAL nature of this process, we are going to remove this option in two months time.

All systems operational

Source: Update & Build Prep – Lineage OS – Lineage OS Android Distribution

%d bloggers like this: