Tag Info

Hot answers tagged

10

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 ...


4

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 ...


2

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 ...


1

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.


1

I think this part of your question is key: I've switched from DHCP to static IP addresses. Doing so reduced the frequency of problems and seems to have eliminated my earlier issue where wifi would be randomly dropped. IP addressing issues could certainly cause you troubles like this. Static addressing is only treating the symptoms, though, not curing ...


1

This can have multiple reasons. First thing to look for is always whether a "user app" might have caused this. This can be done by booting into safe-mode: if everything works here, at least the hardware is fine, and the system as well. In that case, next steps would be: Boot into recovery-mode, and clear (wipe) cache. This is possible on rooted and ...


1

After a lot of searching around and trial and error I stumbled across the answer to this. 1) What is the location on the Internal Memory that is considered as Device Memory? I mean is it a Folder? Yes. Device Memory is calculated from the Data folder present under root. 2) How exactly does Android go about calculating that "Apps & Media" ...


1

There are some ways to pin down your problem. The easiest way should be reading out the last_kmsg which is normally stored under /proc/last_kmsg. The kernel logs everything in there and it can be read until the next reboot. So reading last_kmsg always shows things that happened before the device rebooted the last time. Another way would be using "adb ...


1

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: su mount -o remount rw /system/ cd /sdcard cp ./tcpdump /system/xbin Now you can use tcpdump command. ...


1

I am using the same version of the OS on my HTC One X and I have never had this problem before. So I am thinking this is maybe a problem concerning the hardware of your phone. Maybe you should contact HTC for this problem. They can probably help you some more. But you could always try to do a hard factory reset (this is something which HTC support will ask ...


1

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. ...


1

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.


1

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 ...



Only top voted, non community-wiki answers of a minimum length are eligible