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 ...
Update: Try cleanup and reinstall of drivers as mentioned here. Seems to have worked for others.
This seems to be a known issue, and many have had success by using a different cable, connecting to a USB 3 port etc, but clearly, those won't work in your case.
Not sure what your usual usage is, but for file transfers, you can use Airdroid, which connects ...
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 ...
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 /...
There are several steps/things you can do before you do advanced troubleshooting. Most of the problems can be solved following these steps.
Backup your data. Backup your data first (of course, if possible). You don't need to risk it. Keep it somewhere else. It is better to have backups for personal data and app data separately.
Try rebooting your device. ...
There are apps that let you look at the system log, like CatLog.
What I would do is start logging before you charge it at night and then take a look at the result in the morning. The log will probably be staggering but the errors should show up in red.
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.
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.
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
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 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 ...
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.
I'm not sure of the Motorola methodology for answering or ignoring a call, but on my Samsung, merely touching the green or red button is insufficient; it requires a swipe to convey the intention. I believe this was re-engineered to prevent accidental accepts or hangups through a mere button press. The green button has green arrows and a swipe in the arrow ...
Before you flash a modem, try another dialer app, just in case it is at fault. Check if 3g/LTE/WiFi are working at all. Chances are that it is the modem that is causing the issue but it is easier to install an app or two before flashing basebands.
On the Samsung Galaxy S4 International LTE model: GT-I9505 you cannot flash a Modem through recovery. You must ...