Popular Content

Showing content with the highest reputation since 09/22/2017 in all areas

  1. 1 point
    From June 2016, old yes but still newer than the ones in our phones! Updates OpenGL ES from version 3.1 @140 to version 3.2 @145. Backup your system then flash with TWRP. https://mega.nz/#!aIhnnQyL!R5ypufiNUnI8L6rnDUqkhZpmQ8-IGvvrBoluUlEXBeE Most of the time my phone is running experimental lineage13 but this works with stock as well.
  2. 1 point
    New update uploaded http://www.mediafire.com/file/n55eth5yidbos5c/lineage-13.0-20171007-UNOFFICIAL-p839v55.zip Improved audio volume, All sensors now working - thanks to @wbrambley, Lineage has updated to 6.0.1_r80.
  3. 1 point
    The problem is with the ltr55x sensor, it's a combination light and proxy set. We're actively looking for a solution for this. Also the problem of certain apps like Nova launcher or Ampere causing infinite boots. (If you get this reboot to recovery and use file manager to remove offending app folder in data/app/com.whatever.offending.app.)
  4. 1 point
    Having played and worked in Android since, well, basically the very beginning… I’ve seen a lot of change on the platform. I’ve talked to lots of users, had friends and family using Google’s mobile OS and talked a lot about how to stay secure, how to ensure that your device doesn’t get compromised and how to prevent apps full of malware getting on to your device. The first bit of advice I always give? If an application tells you to check ‘allow unknown sources’ in your security settings, be very, VERY careful. We are in the slightly weird situation where alternative stores such as the Amazon Appstore (which is well worth installing for most users) makes you set this option, but there is something else Google is doing to exacerbate the problem for many users, and that is their insistence on forbidding the listing of ‘real money’ gambling apps in the Play Store. It’s worth thinking about exactly what real money gambling apps are. Of course, the most obvious example is the typical bookmaker app – the stores you might see on any high street in the country. But the ban isn’t only limited to these… it also covers lottery apps (even the National Lottery, and many others that contribute to good causes) and bingo apps from the likes of winkbingo amongst many others. An interesting point to note is that Apple DO allow these kinds of apps in the App Store, subject of course to local laws, and provided they don’t collect funds via Apple themselves (itself slightly odd, as any other app HAS to use Apple for funding, so that they get their cut). So why this policy from Google? It forms part of the Developer Policy, published on the Android Developer website, which covers ‘restricted content’. Unfortunately, it is lumped in with other examples such as sexually explicit content, child endangerment, violence, hate speech etc. etc. It just doesn’t seem right. I maintain that Google is doing more harm than good by forcing people off-platform in order to find gambling content. If they don’t want to make money from it, that’s fine, but they are endangering their users. I’m really interested to hear everyone’s thoughts on this. Is Google doing the right thing by taking the moral high ground? Should we be able to choose to have a little bit of bingo fun on our devices (as one of my close friends does) without being nannied by the platform provider?
  5. 1 point
    If you've been following the launch of the Samsung Galaxy S7 / S7 Edge, you may have read that adoptable storage, a Marshmallow feature that lets you use the microSD card just like internal storage, is missing. The S7s do include a feature where you can move apps to SD card, but it's not quite the same. The good news? You can enable the feature using ADB and it seems to work great, including in hybrid ('mixed') mode. In order to set adoptable storage up, you will need a computer with working 'adb' and, of course, a microSD card in your phone, the faster the better (I personally use a 128GB EVO+ in my own device. Here's the process! 1. BACK UP THE DATA YOU HAVE ON YOUR MICROSD CARD. Your card will be formatted by this process, so make sure you have saved any pictures, videos etc. from your card to your PC before you start. 2. Decide how you want to split your card. You can either commit 100% of the card to internal storage, or split between internal storage and conventional SD. This option is useful if you like to unplug your card and put it in your PC. I would probably recommend committing the whole card. 3. Open your command window / terminal on your computer and type the 'adb shell' command (with your phone connected of course). You will need to enable USB debugging in developer settings (which in turn is displayed by tapping the build number of the device 5 times) in order to see the option. 4. Type 'sm list-disks' to list the disks available for adoption. It'll look something like below - take note of the disk ID (disk:179:160 in this example). 5. Partition the disk. For this we use the 'sm partition DISK TYPE RATIO' command. For example, to partition the disk above as fully adopted storage (aka private) I'd use the command 'sm partition disk:179:160 private'. If I wanted a 50/50 split between adopted and regular, I'd use the command 'sm partition disk:179:160 mixed 50'. Easy right? 6. This process will take a while, but when it's done, the Settings -> Additional Settings -> Storage view on your device should show the new Internal Storage. Note that, for some reason, the total space isn't reported correctly as you can see in this image, however everything seems to work OK. When you install apps, they will generally install automatically to the storage with the most space available, although you can manually move things around if you want to, perhaps for performance reasons (the real Internal storage will likely always be a bit faster). 7. If you want to see another view of how you are doing for space, you can use a third party tool such as FreeSpace or FreeSpace Plus. And that's it! Let us know how you get on, and enjoy your new, expanded S7!

MoDaCo is part of the MoDaCo.network, © Paul O'Brien 2002-2016. MoDaCo uses IntelliTxt technology.