I have a nexus 7 running CM10.1 . For some reason i cannot reach it from my laptop on the same wifi network. I cannot ping in either direction. In the past i have been only able to ping one way.
Just tried out on my stock htc sensation and havent the same issue. Also the nexus and htc cant reach each other either.
I have had similar problems with other android devices, in the past i was developing an app and i could not establish a socket connection from the android device to my computer. Once i was able to successfully ping the laptop form my device everything worked.
This isn't persisant, in the past i fiddled around they eventually talked but there was no consistant solution at the time, i never got to the root cause.
I have obvsered this on 2 different wifi networks
Not sure what is happening here my understanding of networks isn't this deep.
My first guess (assuming you're using the right IP, no firewall conflicts etc.):
Check the WiFi Sleep Policy in the WiFi-Settings of your device. You should set it to Never and then try to ping it once more.
That's the way you'll find the option on your android device:
Settings -> Wireless & Network Setting -> Wifi Settings -> Press Menu button -> Advanced -> WiFi Sleep Policy
Related
I am using chrome://inspect/?#devices to connect with my android device.
After ~20 minutes my device gets disconnected automatically every single time.
After it gets discontinued my device asks for allowing usb device again. And if I run adb devices on my Mac, I am unable to see my device since it got disconnected.
I wanted to know the why this is happening and is there a fix available for this or not.
Aim: I want to connect my android device at least for 3 hours without interruption.
I have tried this with multiple devices, multiple data cable and multiple physical conditions but I don't think the issue is from hardware side. USB Debugging is on and the connection stays for a few minutes without any issue, everything works fine for some minutes(not fixed but it is around 20 minutes).
Adding images of my android device and macbook after the connection gets disconnected:
If you are facing similar issues then here are the things that you can try:
Try different USB cable(s)
Try different USB ports on your machine(for some people using 2.0 port worked out)
Try the same process, with unchecked 'Discover USB Devices' in chrome://inspect (then Chrome will connect through the ADB server, not directly) ==> This solution worked in my scenario.
I'm trying to connect my Raspberry Pi's to a WiFi network without success. Ethernet connection works flawlessly, but as I attempt to connect to WiFi using ADB as mentioned here, nothing happens. I have also tried to use the Android Things Setup Utility without success as can be seen in the terminal output.
When I try to connect through the menu option while running with a monitor connected, my particular network is not visible, even though my work's corporate networks are visible in the same menu. It should be noted that other devices are able to connect to the WiFi in question, and using any corporate network is not possible the project.
I have also tried
Using a cell phone as hotspot with similar result
Unplugging the ethernet cable when attempting to find networks(through the monitor interface)
Changing between password/open network
Both 2.4G and 5G
Changing SSID from uppercase to lowercase
Manually changing the /data/misc/wifi/wpa_supplicant.conf but cannot find any OS files on the SD card.
Reinstalling OS image.
I'm running Google iot_rpi3 v1.0.3
There seems to be no documentation on this issue, has anyone else encountered this problem?
Did you trie 20MHz bandwidth for 2,4GHz? Some devices can not find wifi network with 40MHz bandwidth or 12 and 13 channel number.
Solved! Solved again!
It appears as if the Wi-Fi list in the GUI only can display at most three network SSID's. This lead to the corporate networks effectively 'jam' access to my Wi-Fi as the list appears to be sorted by signal strength, and my network's RSSI was weaker than the corporate one's.
Edit: It appears as if the device does not retain the connection setup when powered down and moved to a location where other networks are present, thus rendering any other network, with weaker signal than the top 3 present, unusuable.
Edit2: Changing the router's channel from 12 to 6 seemed to do the trick. Something appears to be wonky with Raspberry Pi and channel 12. Could not update the locale either to lose the region lock.
I made a program to backup files in android devices. To put it simply, it works in background of Windows like a server and when a defined android device (with its LAN IP) connects to home's WiFi network it looks for specific files in specific folders in device and backups them.
My problem is, for some devices (e.g Samsung Note 4), after a few successful WiFi connections (or a few days later) the device starts to appear offline. To fix this, I need to reset the authorities in device or do the reconnection procedure of my program with USB cable again. I researched the web in-depth but couldn't find a way to make offline devices online automatically.
Most of 'ADB offline' solutions on the web works well, but i need to do this automatically over WiFi within my program.
-ADB kill-server & start-server, not working,
-ADB disconnect & connect, not working too.
Disable your antivirus and then try again or add adb.exe as exception in your antivirus.
I want to let my laptop and tablet communicate via OSC using OscP5 java library.
Tablet is android device and application is made on android studio.
Laptop is Windows 8.0 and application is running on Processing 2.2.1. Both uses same library OscP5.
WiFi network is very huge and strong in public government office. Both devices are obviously in same WiFi network named - Public WiFi Free. Both devices are using wireless(WiFi)
What I'm doing is very simple.
Send some integer from tablet to laptop through UDP unicast.
When I confirm IP address,
Laptop : 192.168.25.219
Tablet : 192.168.26.83
It's strange that they have different address which are 25 and 26.
I tried to reconnect on both device many times, but they always get same IP.
Problem is not port. I certainly confirmed that port is same(13000).
and laptop is just listening 13000 port and not sending anything.
Tablet is just sending to laptop IP on 13000 port.
I searched a bit and people are saying that if 1st, 2nd,and 3rd part of IP address is not same, OSC doesn't work. Is this the problem? and if so, Why? I'm kind of noob about network so please explain easily..
Problem was firewall...
Anyone who came to this post must confirm whether firewall is blocking your port or not. There are 2 possibility that firewall is blocking your port on router level or your OS level.
The first case, you have to access administrator setting page of your router and enable VPN(Virtual Private Network) pass-through or open port.
The last case(mostly in Windows because firewall is option in OS X), you simply go to settings and disable Home network level firewall, or you can add exception for you port.
I hope someone will not have hard time like me because of firewall.
So, let me start off by saying that I am 'relatively' familiar and comfortable with making Android apps and using both LogCat and DDMS to debug.
That being said, I'm encountering more of a logistical issue than anything else right now - I am making a locative app, where the GPS is fuelling and controlling other methods in my Activity, and after a while, it is crashing.
Now, because it is locative, I am walking around to test it, in order to receive different GPS locations. Because of this, I am not connected to my computer at the time that it crashes, so have no way (that I know of) to read the stack trace, etc.
In my particular instance, I am navigating through a series of activities, and finally reach the penultimate screen in my app, and while I am running the application in my studio, it runs indefinitely without issue. It is only when I take the device outside that it crashes...
I am wondering if anyone has any tips or tricks with this issue - I'm sure give the prevalence of locative apps, it must have come up, but I cant seem to find the right search terms. It could be as simple as saving the LogCat to file, and/or the stackTrace, but I'm not sure that's the answer...
Thanks in advance.
If I got you right, this is what you are looking for:
https://play.google.com/store/apps/details?id=org.jtb.alogcat&hl=de
Edit: Also there are many more apps like this. You can just browse around in Google Play Store
You can debug the app without rooting your android, unlike the other responses. start off by plugging the android into your computer, then run adb devices to make sure the device is there. Then, run tcpip 5555 to change the android to tcp mode, which will allow debugging over wifi. Disconnect the android from the computer, and connect to it by typing adb 192.168.x.xxx, replacing the x's with your android's IP address. It should connect with no issues, as long as port 5555 is open, and both the android and your computer is on the same wifi.
Simple: Wireless ADB
One of the reason that I choose to run CyanogenMod on my testing devices is that it is a stripped down version of Android that has some additional developer tools, one of those being the ability to access the wireless portion of the ADB system.
As you are probably unaware, you are able to establish an ADB connection to your device over WiFi, however, if running a stock ROM, this requires root access, as it can be potentially harmful to your device, as Wireless ADB will work even over your cellular network, meaning that you could potentially receive apps from other insert carrier here's devices.
If you wish to run WirelessADB, here is a Play Store app that will help you to enable the feature on your device. Requires ROOT
It is as simple as connecting your device to your local WiFi network, (same one the development computer is connected to), enable Wireless ADB, and then running the following command on your computer:
adb connect 192.168.1.101
Replacing 192.168.1.101 with the IP address of your android device.
By establishing this connection, you can run everything just as you would if the device was plugged in via USB Cable.
I recommend ACRA (Application Crash Reports for Android ). It allows you to send crash reports to a number of different destinations. See https://github.com/ACRA/acra/wiki/BasicSetup