After probing the firewall logs, it appears that the grey/blue icon is triggered depending on whether or not your device has access to Google Play. In our case, I had to open tcp-udp port 5228 (as per http://support.google.com/googleplay/bin/answer.py?hl=en&answer=2651367) and after turning wifi off and back on again, the icon became blue.
I can't ...
Looking at the installation instructions of the ROM you flashed, I am guessing in the TWRP/ CWM options, under Advanced Wipe , one of the options " Wipe Dalvik Cache, Cache, System and Data " (likely data) was missed out leading to the current situation.
Thanks to OP for confirming that wiping data was missed out by him while installing CM. A ...
tl:dr; Based on your observation that it works with Moto but not with LG, my guess is that it is due to conflicting TRRS standards -there are two standards. OMTP which is the older standard and CTIA/ AHJ which is the standard all newer Android devices are expected to follow
Details and solutions to overcome are listed
From TS/TRS/TRRS/TRRRS: Combating the ...
I had same problem and endlessly researched and did everything except hard reset. Then, when testing the usb cable on another phone, I realized that I wasn't using the usb cable that came with my Galaxy S3 i9300. Once I plugged in the "stock" usb cable, my phone was instantly recognized. Why this is I don't know as the cable I had been using works on all ...
What is a "blue screen"?
Certain Android devices sometimes become unresponsive and display a plain bright blue screen with no text on it. See photo.
What should be done?
(This answer is based on what someone on IRC once told me.)
If you only ever see a blue screen once or twice a month, ignore the problem and restart your phone when it happens.
If you ...
Battery contains the chip which provides information to fuel gauge hardware and drivers. Since you have already done that, next is to determine if the problem is with fuel gauge drivers/ software or hardware.
Wipe clean your phone (cache, dalvik and system) and flash stock ROM for your phone. Don't install apps. Switch to safe mode, charge for about three ...
If it were to happen to me, my preferred approach would be:
Step 1: Clear data of Magisk Manager app
Whatever way your Android supports, open the App info page for your Magisk manager app, force stop the app, and clear its data/storage. Reboot (optional). Now launch the Magisk Manager app. If the problem still persists, follow the steps below.
Step 2: ...
You can simply see the crash stack trace after any crash happens.
Use ADB command below,
adb logcat -b crash #default
adb -d logcat -b crash #show from device when multiple device
adb -s logcat -b crash #show from simulator when multiple device
Yes, tcpdump is an administrator-level application (I highly doubt there will ever be an Android permission level to view all other apps' network traffic). Once rooted, if you have tcpdump binary (compiled for your device's cpu type) on sdcard, try:
mount -o remount rw /system/
cp ./tcpdump /system/xbin
Now you can use tcpdump command.
You don't use adb to connect to a device when it's in the bootloader menu: you need to use the fastboot command instead. That's why it's called "fastboot mode"! Not all phones support fastboot: in particular, older HTC phones use a proprietary protocol called HBOOT instead, but I think the newer ones support fastboot.
Also experienced the same problem. In my case, discovered that the cause was from doing a backup in QPST and forgetting to revert the USB settings.
i.e. *#7284# to access PhoneUtil > "Qualcomm USB Settings" > set it to "MTP + ADB"
Do you have custom recovery installed? I have had this problem twice on a Galaxy S2, and what fixed it for me every time was running a permissions fix from recovery mode.
If that doesn't work, try deleting your WiFi config file. Not sure what it is on the Nexus, but I'm guessing it'll be something along the lines of /data/misc/wifi/wpa_supplicant.conf or /...
If you want to execute an adb pull comand and at the same time monitor the on-device log via adb logcat you can do so by executing each command individually in it's own terminal/cmd.exe instance.
adb is not limited to a single connection (as the MTP protocol is). Hence you can execute two or more adb command simultaneously. Even multiple adb push or pull ...
Download MPT (Media Transfer Protocol) Porting Kit and then install it to your computer. You can download the MPT Porting Kit installation file through the Microsoft’s official website directly.
Reboot your computer.
Reconnect your mobile phone to your computer by using the USB cable.
It turns out that the issue was that Location Reporting was enabled. Disabling this misfeature increased my battery life almost three-fold, stopped the notification popups (which I've since learned are called toasts), and now the spooks will have only a slightly harder time to find out where I've been.
Apps and their data are stored on a different partition (/data) from media (/sdcard0) and removable storage (/sdcard1). If you are rooted, you can use an app like Disk Usage to check what's taking up space on your internal memory.
There are multiple ways to obtain useful information. But as Dan pointed out, on-device solutions will require root (starting with JellyBean) – and off-device solutions ADB:
adb logcat was already described in Dan's answer. For more details, you can see our logging tag-wiki.
adb bugreport > report.txt gives very detailed information, including details ...
I don't think you'll be able to control start-ups but you can surely monitor CPU usage. Open Settings>Developer options - and under Monitoring section enable Show CPU usage. CPU usage and processes will be shown as overlay on screen. Also there are number of apps in Play Store to serve the purpose.
I have installed Babbel app(version 5.2.1) and it works fine on my Xolo Q1010i.
I had even tried cleaning the cache and reopening the app again, but then also it works the same way. Maybe you should try restarting your Sony LT22i and give it a try then.
Hope this helps!
Probably too late for you, but in case others stumble across this page while seeking help, like I did.....
I had a similar problem and contacted them via their chat function on their website. I was advised to hold both the power and the volume down buttons for 30 seconds. This brought up the android recovery screen - I followed the instructions and the ...
I found out, the following WiFi Manager App was the reason:
Wi-Fi Privacy Police (Prevent leaking sensitive data on WiFi)
The problem disappears whenever I disable this app. Here is how to disable it:
(System) Settings / Memory / Apps started on boot / Wi-Fi Privacy Police / Start at boot: DISABLED
So you disabled the App's bootup autostart. Now ...
install 3rd party app like Link2SD or DevTools
get the pkgname for hidden Magisk Manager
uninstall hidden Magisk Manager from cmd line
adb shell cmd package uninstall <pkgname>
reinstall Magisk Manager
Alecxs answer (thanks) led me to a different and easier solution.
I uninstalled the manager and tapped on the hidden manager and it opened up with the correct status! Ridiculously simple.
Note to myself :Remember to unhide Magisk Manager before updating next time
I just found the solution here basically you need to install the HackTool, reboot the phone, open the hack app and select "force wifi" and also "activate traces". Then open Android Reverse Tethering Tool and job is done ;) Enjoy full Tethering!
BBS is more confusing than GSAM battery companion. It provides more detail, but GSAM + root can tell you a lot. If you could provide screenshots of full charge, to fully dead we can point you in right direction; if this happens in 7 hours with the screen off and no interaction all the better it should be very trivial to find.
From there, you could use ...
It's not necessarily the installation process which goes wrong.
A file which is non-essential (a sound file for example) may have been corrupted for any number of reasons, and a simple re-install re-writes the corrupted file.
It's the same principle as with a computer application. An error pops up at a random time, yet the rest of the program still works.
You can go to Settings -> Developer Options -> Running Services to see the active services that are running. From there, you can click on "Show cached processes" to check the apps that may be not running but are cached by the OS in case you need to run them so they can be started quickly. You can then stop running process or cached processed.
In Lineage, ...
In most cases, if USB debugging is turned on, you can use adb logcat to see the exception output. This usually includes a stack trace, but that's not often useful unless you have the app's source code. All the same, the developer of the app will probably be grateful if you include it in any bug report.