Tag Info

New answers tagged

0

I'm running an older version, 4.1.1, on a cheap tablet. On this unit, it's Settings-->HDMI-->HDMI Resolution. HTH


0

Turn off the Android HDMI port in Settings. It is likely either Settings-->HDMI-->Off or Settings-->Display-->HDMI-->Off


0

The technique mentioned by Bo Lawson here and taken from this answer by Omar isn't working on my Lollipop at all. Neither it is switching the call into speaker, but adjusting the volume of the earphones only in my Kitkat 4.4.2. You can use combination of keyevents to achieve the goal. The important ones you would need are: 19 --> "KEYCODE_DPAD_UP" 20 ...


-1

Using adb you can clear cache. rm - r /data/dalvik-cache rm - r /cache/dalvik-cache


0

The fix for me was using a different micro-usb cable. No software change, no drivers to update, just the usb cable. Apparently they aren't all created equal.


1

One thing I noticed not mentioned in what you have tried that will make your device invisible. Have you enabled USB debugging on your Nexus 5. USB debugging helps operating systems communicate with each other and without it things get lost in translation. To enable USB debugging Go into Android settings menu and scroll down to the about phone menu next go ...


0

So it seems the problem was with the settings of the device. Having a Screen Lock (even if SmartLock is enabled, and you are in a "safe location") disconnects ADB on device idle. Only way around it for me was to disable the device screen lock.


0

I wrote a Bash (Linux) script that runs adb pull and then compares the md5sums of the pulled files with the original files. If the md5sums don't match, the script will automatically remove the corrupted pulled files and then retry adb pull again. I put the script on Pastebin here (thanks to the tip from GiantTree).


1

From what I have seen so far (and I use adb pull very often), there is no verification process going on. If a file, that has been pulled, is corrupted, you will get no notification about it whatsoever.


-1

in that App Info (though grey out), click the three vertical dots and use Uninstall for All Users.


0

Could be SE linux getting in the way. Try getenforce If it returns 1 or Enable setenforce 0 Then try your command again.


0

The workaround was to set the desktop backup password under Developer settings. It seems there is a bug in backup process. If you din't set a desktop backup password under the developer options settings the above problems occurs and your backup will eventually be incomplete(empty backup file). However I couldn't find an official source for this bug report ...


0

This functionality has not been implemented in ADB yet. However, there are workarounds that some users have come up with. Check out this thread on XDA Developers for more information on how you can work around this limitation.


0

If you've never connected your phone to the computer before, you may be out of luck. Since the later versions of 4.X, (I think at least JB 4.3), you must authorize the host computer to connect via ADB, which will popup the first time you connect with USB. When using Wifi, this authorization MUST already be established, or it will not accept the ADB over ...


4

I have not tried this myself, but there's an app named ADB Wireless (no root) which, as the name suggests, claims to make this possible without involving root: This app is for developers wanting adb access over WiFi without rooting your phone. … *** NO ROOT REQUIRED *** Usage instructions can be found on the app's playstore page – looks pretty easy ...


2

This is not a final answer, as it is not generic (only works on some devices) – but it's a start at least: As we've figured out, at least CM based ROMs with Kitkat (Android 4.4) and above ship with the aapt binary available in /system/bin1. If your ROM doesn't have it, and installing the binary on the device is an option, you can find it here. Using aapt, ...


1

Try disabling verification, via safestrap, and try both methods + Sideload again. I should ask, why heimdall and safestrap? Use Clockworkmod recovery instead of safestrap and ODIN over heimdall. Yes, they require you to get your stuff online beforehand, but clockworkmod has got me out of a lot of soft-bricks If I was boring, everyone I know would not ...


0

Personally, I am a Nexus user. But having repaired a friend's international varient S3 before, I do know some things about Samsung. And since you dont have custom recovery, you cannot access /data (the partition where data is stored). So the way I know of will use a custom recovery to backup/restore data. This voids your warranty. I am assuming you already ...


1

You may check-out my updated answer dealing with the question in entirety, or consider the following info: High accuracy: gps,wifi,network or gps,network (if you don't want Wi-Fi enabled) Battery saving: wifi,network or network only Device only: gps E.g: adb shell settings put secure location_providers_allowed gps,wifi,network To disable Location mode ...


1

I especially wonder why adb backup doesn't cover this. It is not that adb backup doesn't want to cover the app com.android.providers.telephony. This app is not much different from any other system app based on its AndroidManifest.xml. The problem is with the flag its developer has declared in the manifest which as a default mechanism for some reason adb ...


0

None on the internet however I did get this information while searching here's the link http://www.tomsguide.com/forum/id-1818822/galaxy-note.html download and install the suitable USB drivers for your device, you can download Samsung KIES for verifying if the suitable drivers are installed on your PC. Secondly, download the Official Jelly Bean 4.1.2 ...


1

It's unlikely that you need to copy the entirety of your tablet's storage in order to find a file from one application. Assuming the app you're using is this one, you should only need to check in /data/data/bn.ereader/. IIRC, you can pull that to your PC with adb pull /data/data/bn.ereader/ . (the dot may or may not be necessary).


1

The correct reference would point to our nandroid tag-wiki, as a Nandroid backup is what covers all content. However, this is only available via custom recoveries. An alternative to that would be the dd command ("Disk Duplicator"1). Disclosure: the following describes an application I wrote and maintain: My tool Adebar is able to generate you dd scripts ...


0

I never flashed a ROM using a .zip in fastboot. The proper way I've ever seen is to flash individual files, and some of the important commands are: fastboot flash boot boot.img fastboot flash cache cache.img fastboot flash recovery recovery.img fastboot flash system system.img fastboot flash userdata userdata.img // 64GB users need userdata_64G.img ...


0

You need to flash custom ROMs from within recovery, not within the bootloader. Detailed instrunctions on how to install CyanogenMod can be found here. NOTE: those instructions are not for the Cyanogen, Inc. factory images. Offical factory images can be found on the Cyanogen, Inc. website


5

As for the first part: Yes, that definitely means your device is rooted. For the second part of your question, IMHO it's close to impossible to figure the exact timestamp of rooting (apart from yourself noting it in some document). Though there seem to be tools reporting it, as mentioned in this answer1, I'm afraid that timestamp is not much reliable ...


1

There are some couple of ifs and buts. I have not tried this, but this is just an idea that comes to my mind which is an extension of my previous answer. Through this post, I learn that intents can be invoked through adb command prompt. So, if the device is rooted and has Xposed framework, the above can be done.



Top 50 recent answers are included