B4A has completely crippled me ...

G

GuyBooth

Active Member
Licensed User
Longtime User
I have been using the B4A bridge for development when I reach critical stages. Once or twice I have seen a message "Destination Host Unreachable" but by rebooting my phone and stopping and starting B4A I have always been able to get it to restart - until now.
Now I cannot get it to communicate at all with my phone.
It is working ok with my Tab (different IP address).
I can ping my phone from the same computer I am runnig B4A
I have tried turning off the firewall and the antivirus software.
I have tried rebooting my wireless modem.
I have tried downloading a new copy of the bridge to my phone.

At this point I am completely dead in the water. Has anyone else had this experience and found an answer?
Is there any other way for me to load my app (still in development) to my phone so I can keep going?

Any assistance appreciated!
 
Sort by date Sort by votes
Peter Simpson

Peter Simpson

Expert
Licensed User
Longtime User
Hey GuyBooth. I've been getting the same thing lately, I posted about it a few days ago. I too get the same message sometimes.

I was not sure if it was the B4A-Bridge or Android 4.2.1 on my phone or tablet. The internet is always working when I test that on devices.

Last night it was not too bad, but the night before I ended up connecting my N7 to my laptop via a cable so that I could do some design work :confused:

It's a strange one because my WiFi never turns itself off on any devices.

My IP addresses are static and never get changed.

Sent from my Nexus 7 using Tapatalk 2
 
Last edited:
Upvote 0
G

GuyBooth

Active Member
Licensed User
Longtime User
I've been able to set up the USB and it is working.
Still not able to use the Wireless B4A bridge though - I'll keep trying ...
I've attached a png of the error message.
 

Attachments

  • b4aBridgeError.png
    b4aBridgeError.png
    11.9 KB · Views: 203
Upvote 0
E

enonod

Well-Known Member
Licensed User
Longtime User
This may be stupid but the only time I get that message is if the IP has changed and I didn't notice. The difference shows on the device as 192.168.1.71 and then for some reason changes and shows 192.168.1.74 and I did not bother to look close enough in B4A dialog. Changing the last digits in the B4A dialog cures it of course.
 
Upvote 0
canalrun

canalrun

Well-Known Member
Licensed User
Longtime User
Hello,
I have had a similar problem once or twice – since you can ping from your computer, maybe this does not apply.

I normally use B4A bridge and wireless connection. The phone IP is something like 192.168.0.xx. For some reason the phone loses the wireless connection temporarily and it connects to the cellular data network with an IP something like 308.XX.YY.ZZ. B4A reports "cannot connect".

Within a few minutes the wireless connection is back, the phone IP is returned to 192.168.0.xx, and the bridge works again.

May be this is the problem. I have no idea why the phone loses its wireless connection temporarily. This has only happened once or twice.

Barry.
 
Upvote 0
E

enonod

Well-Known Member
Licensed User
Longtime User
I think we can combine here, because the reason for my post was exactly the same as yours except that upon return a different IP was assigned, your xx, without it being noticed.
 
Upvote 0
Beja

Beja

Expert
Licensed User
Longtime User
Hello GuyBooth and guests..
you may be surprised if I told you I never used the bridge at all, not even once and I am OK with that...
After compiling the test app, I copy the APK file from Objects folder to my
device, then install it from there.. all this without physically disconnecting the'device from the PC..
the only thing I do is click on Disconnect USB, because
before you do that you can't access the device folders.
sorry can't help you but sincerely wish you a good luck.
 
Upvote 0
G

GuyBooth

Active Member
Licensed User
Longtime User
Yet once again I rebooted the phone - and now I have access!

This is after I turned off the wireless service and turned it back on again, and turned off the data service and turned it back on again - but I'm not sure that is what cured it.
I checked the IP address (many times!) and it wasn't that.
This is still a bit of a mystery.
 
Upvote 0
You must log in or register to reply here.
Top