Tag Info

New answers tagged

1

The /system folder contains your operative system. That is why it won't boot anymore. Xiaomi's default MiRecovery permits only installing a ROM located in your root directory (the main folder, corresponding to location /) and named update.zip. Since you can't access your phone directly, you have to put this file in it using your computer. This will include ...


1

Just wait. Watch the news. I have been now for a while, it appears to be getting released in some countries, but you will hear about it if you watch/listen.


0

Best option (only option so far as i know) is Root + safestrap. Details: Samsung locked their bootloaders - Bootloader access is required to write new operating software (analogous to installing windows) Safestrap is a way of isolating different Operrating software; and running it without unlocking. So: If you want Lollipop You will have to Root your ...


0

As of 2015, as stated in the answer by @Ankush Google says it won't. But in practice, if you side load an APK, and an updated is pushed on play store, it does get pushed down. We tested this scenario. It is important to note that the automatic update to the phone, will happen after a few hours of the app getting published (not apk upload) on the App Store, ...


3

As of 2015 Google Play will detect apps with the same signature, but they will not be updated unless the user un-installs the app, then reinstalls from the Play Store. So in short, to answer your questions - no Google Play will not update the application if it is installed from somewhere other then the Play Store. see: ...


-1

After extensive searching found an Xposed module for it! xPrivacy! EDIT: xPrivacy (http://repo.xposed.info/module/biz.bokhorst.xprivacy) is an Xposed module that allows you to control what data apps can access (it's more powerful than app-ops or ReceiverStop but more complex). so what i did: after installing xPrivacy Scrolled in the app list to find ...


0

You can go to setting-.apps-all and then find the apps that has the "CONTACTS" word on it. I think there's two of them . Then clear the data of those and your problem is solved. it works for me!


-2

I fixed the issue by following.. Go to settings>applications>manage applications>all Look for media storage and select it now you click clear data job done. Reboot once When you open the apk file first time android would have blocked untrusted files. Even After you enable the option to trust third party applications , the blocked log is not ...


1

The APK themselves can be installed without recovery. However if an application depends on another application which doesn't exists in the current system or if it depends on features that thee currently installed dependent doesn't provide or provide in incompatible way, then you might see instabilities that wouldn't have been there if you had installed the ...


0

if doing so you have to remount the /system partition as it is mounted read only. via an adb shell mount -o remount,rw /system or from outside the device adb remount After this you can copy the content of this file onto the system partition. Keep in mind that these apk files will rely on some libraries, config files etc, which are also provided in ...


0

Installing zip from custom recovery install these apks to /system directory which is read only file system and you cant uninstall these apks later. Yes you can install manually and most probably you wont get problems if you install all necessary apks but applications will be on /data directory and used your precious storage space. you can uninstall though ...


1

After a few more exploring i found out what the problem was. It has to do with the permissions declared INSIDE the app. I plugged my phone to the Android Studio and checked the logcat looking for the moment where the error appeared. Here it is: "02-05 15:38:50.828 929-970/? W/PackageManager´╣Ľ Package motoboy.yellowlab.com.br.motoboy attempting to ...


0

You can install a vm on your Android and run the second is on the virtual machine: Here is a machine which you could use (QEMU) and an a guide: http://forum.xda-developers.com/showthread.php?t=1459153


0

It is possible that the app is not compatible with your device. Some possible conflicts may involve DPI, RAM, or Android version prerequisites. If your system specifications do not meet the requirements of the manifest of that app, you may not be able to install it at all.



Top 50 recent answers are included