New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Android 2.3.4 stops transfer data a whille after openvpn setup #43

Open
GoogleCodeExporter opened this Issue Mar 5, 2015 · 28 comments

Comments

Projects
None yet
1 participant
@GoogleCodeExporter

GoogleCodeExporter commented Mar 5, 2015

Hi,
I've been using azilink on Samsung Galaxy S, Android 2.2.1 and Linux with great 
success.

Now I've upgraded Android to 2.3.4 and have to upgrade ADB to 1.0.26 to talk to 
Galaxy S. I've newly installed azilink 2.0.2.

Everything seems to be OK BUT there are about 1000 bytes transfered IN and OUT 
and after that it stops transfer data. I can download part of the web page or 
make couple of pings and after that it stops communicate.

No errors, no logs, it just does not transfer any byte.

When I stop ADB, openvpn and azilink and run it again I can transfer some bytes 
before it stops communicate.

Milan

Original issue reported on code.google.com by milan.be...@gmail.com on 27 Jun 2011 at 2:51

@GoogleCodeExporter

This comment has been minimized.

Show comment
Hide comment
@GoogleCodeExporter

GoogleCodeExporter Mar 5, 2015

I see the same issue on my HTC Evo 4G.  Same behavior as OP, a handful of 
kilobytes make it through, then it stops.  All the byte counters stop 
incrementing.  Nothing in any logs that I can see.

Azilink 2.0.1 worked well when my phone was running Android 2.2, but when I 
upgraded to Android 2.3 it stopped working.  I upgraded to azilink 2.0.2 on the 
phone and that didn't change anything.  I'm running OpenVPN 2.1.0 under Lucid 
on the host.

Let me know if I can help with debugging in any way.

Original comment by seb.kuzm...@gmail.com on 12 Jul 2011 at 3:42

GoogleCodeExporter commented Mar 5, 2015

I see the same issue on my HTC Evo 4G.  Same behavior as OP, a handful of 
kilobytes make it through, then it stops.  All the byte counters stop 
incrementing.  Nothing in any logs that I can see.

Azilink 2.0.1 worked well when my phone was running Android 2.2, but when I 
upgraded to Android 2.3 it stopped working.  I upgraded to azilink 2.0.2 on the 
phone and that didn't change anything.  I'm running OpenVPN 2.1.0 under Lucid 
on the host.

Let me know if I can help with debugging in any way.

Original comment by seb.kuzm...@gmail.com on 12 Jul 2011 at 3:42

@GoogleCodeExporter

This comment has been minimized.

Show comment
Hide comment
@GoogleCodeExporter

GoogleCodeExporter Mar 5, 2015

Same here. Was working fine before on,
HTC Incredible 2
Stock Android 2.2
Verizon carrier
My son accidentally accepted the OTA 2.3.3 update and now azilink is broken.
My connection keeps disconnecting then reconnecting after just a few bytes.

I suspected foul play from Verizon so I reloaded EZtether beta to test and it 
still works fine.

many thanks for the great app. looking forward to a fix.
ken (help debugging also offered)

Original comment by k...@mort.net on 20 Jul 2011 at 4:58

GoogleCodeExporter commented Mar 5, 2015

Same here. Was working fine before on,
HTC Incredible 2
Stock Android 2.2
Verizon carrier
My son accidentally accepted the OTA 2.3.3 update and now azilink is broken.
My connection keeps disconnecting then reconnecting after just a few bytes.

I suspected foul play from Verizon so I reloaded EZtether beta to test and it 
still works fine.

many thanks for the great app. looking forward to a fix.
ken (help debugging also offered)

Original comment by k...@mort.net on 20 Jul 2011 at 4:58

@GoogleCodeExporter

This comment has been minimized.

Show comment
Hide comment
@GoogleCodeExporter

GoogleCodeExporter Mar 5, 2015

Same here. Working fine before
SE Xperia X8, Custom ROM 2.2
now: Custom ROM 2.3.4 --> stops at about 1000 bytes

Original comment by mag.mart...@gmail.com on 20 Jul 2011 at 11:24

GoogleCodeExporter commented Mar 5, 2015

Same here. Working fine before
SE Xperia X8, Custom ROM 2.2
now: Custom ROM 2.3.4 --> stops at about 1000 bytes

Original comment by mag.mart...@gmail.com on 20 Jul 2011 at 11:24

@GoogleCodeExporter

This comment has been minimized.

Show comment
Hide comment
@GoogleCodeExporter

GoogleCodeExporter Mar 5, 2015

Is anybody trying to fix this?

Original comment by ronnie...@gmail.com on 4 Sep 2011 at 1:19

GoogleCodeExporter commented Mar 5, 2015

Is anybody trying to fix this?

Original comment by ronnie...@gmail.com on 4 Sep 2011 at 1:19

@GoogleCodeExporter

This comment has been minimized.

Show comment
Hide comment
@GoogleCodeExporter

GoogleCodeExporter Mar 5, 2015

I seem to have this same issue on my HTC Evo since upgrading to Android 2.3.3.  
I noticed my lockups seems to occur after dns lookups which use the udp 
protocol.  I downloaded the source for azilink and seem to have traced the 
problem to a lockup occurring in UdpDriver.onRead() when calling mChannel.read( 
dat ) the second time through the for loop.  I think this is related to a 
blocking problem with DatagramChannel introduced by gingerbread.

I found this related issue:  
http://code.google.com/p/android/issues/detail?id=16579 (DatagramChannel and 
ServerSocketChannel do not respect non-blocking mode)

I didn't figure out how implement the work arounds they noted but came up with 
my own temporary until someone who knows more can solve the problem or they fix 
gingerbread.

I don't know the total consequences, but my work around has been to remove the 
loop surrounding the mChannel.read( dat ) in UdpDrive.onRead().  I may just be 
having luck with it since udp is mostly used for dns lookups.  Maybe problems 
or slow downs will occur with larger streams using udp.  I've attached my copy 
of my UdpDriver.java source.


Original comment by joexx...@gmail.com on 11 Sep 2011 at 1:29

Attachments:

GoogleCodeExporter commented Mar 5, 2015

I seem to have this same issue on my HTC Evo since upgrading to Android 2.3.3.  
I noticed my lockups seems to occur after dns lookups which use the udp 
protocol.  I downloaded the source for azilink and seem to have traced the 
problem to a lockup occurring in UdpDriver.onRead() when calling mChannel.read( 
dat ) the second time through the for loop.  I think this is related to a 
blocking problem with DatagramChannel introduced by gingerbread.

I found this related issue:  
http://code.google.com/p/android/issues/detail?id=16579 (DatagramChannel and 
ServerSocketChannel do not respect non-blocking mode)

I didn't figure out how implement the work arounds they noted but came up with 
my own temporary until someone who knows more can solve the problem or they fix 
gingerbread.

I don't know the total consequences, but my work around has been to remove the 
loop surrounding the mChannel.read( dat ) in UdpDrive.onRead().  I may just be 
having luck with it since udp is mostly used for dns lookups.  Maybe problems 
or slow downs will occur with larger streams using udp.  I've attached my copy 
of my UdpDriver.java source.


Original comment by joexx...@gmail.com on 11 Sep 2011 at 1:29

Attachments:

@GoogleCodeExporter

This comment has been minimized.

Show comment
Hide comment
@GoogleCodeExporter

GoogleCodeExporter Mar 5, 2015

I tried the workaround described in comment 5, but it failed for me. A security 
exception would ultimately be thrown.

I've had a hard time tracking where the problem is. I can set breakpoints in 
Eclipse, but as soon as I try to connect my computer to my phone, the debug 
connection is lost. Furthermore, absolutely none of my log messages appear in 
DDMS. How did you trace the execution to UdpDriver?

Original comment by crj...@gmail.com on 15 Sep 2011 at 1:03

GoogleCodeExporter commented Mar 5, 2015

I tried the workaround described in comment 5, but it failed for me. A security 
exception would ultimately be thrown.

I've had a hard time tracking where the problem is. I can set breakpoints in 
Eclipse, but as soon as I try to connect my computer to my phone, the debug 
connection is lost. Furthermore, absolutely none of my log messages appear in 
DDMS. How did you trace the execution to UdpDriver?

Original comment by crj...@gmail.com on 15 Sep 2011 at 1:03

@GoogleCodeExporter

This comment has been minimized.

Show comment
Hide comment
@GoogleCodeExporter

GoogleCodeExporter Mar 5, 2015

Can't imagine why commenting out the "for loop" in UdpDrive would cause a 
security exception to be thrown.  Something else different?

Anyways, I only used the logcat portion of DDMS with the command "adb -d logcat 
| grep -i azilink"
I also set VpaNatEngine.sLog = true to utilize existing Log.v statements and 
added my own Log.v statements to narrow down the fact that the UdpDriver looped 
once and then never came back from the second time mChannel.read(dat) was 
called.   I haven't tried using break points on my actual phone.

Original comment by joexx...@gmail.com on 15 Sep 2011 at 3:00

GoogleCodeExporter commented Mar 5, 2015

Can't imagine why commenting out the "for loop" in UdpDrive would cause a 
security exception to be thrown.  Something else different?

Anyways, I only used the logcat portion of DDMS with the command "adb -d logcat 
| grep -i azilink"
I also set VpaNatEngine.sLog = true to utilize existing Log.v statements and 
added my own Log.v statements to narrow down the fact that the UdpDriver looped 
once and then never came back from the second time mChannel.read(dat) was 
called.   I haven't tried using break points on my actual phone.

Original comment by joexx...@gmail.com on 15 Sep 2011 at 3:00

@GoogleCodeExporter

This comment has been minimized.

Show comment
Hide comment
@GoogleCodeExporter

GoogleCodeExporter Mar 5, 2015

Guys,

So I've used the pointers from the posters above to modify UdpDriver, and it 
seems to be working on the gingerbread now (got it on verizon droid2). Attached 
is the modified source file.

Original comment by alex.bur...@gmail.com on 12 Nov 2011 at 5:09

Attachments:

GoogleCodeExporter commented Mar 5, 2015

Guys,

So I've used the pointers from the posters above to modify UdpDriver, and it 
seems to be working on the gingerbread now (got it on verizon droid2). Attached 
is the modified source file.

Original comment by alex.bur...@gmail.com on 12 Nov 2011 at 5:09

Attachments:

@GoogleCodeExporter

This comment has been minimized.

Show comment
Hide comment
@GoogleCodeExporter

GoogleCodeExporter Mar 5, 2015

[deleted comment]

GoogleCodeExporter commented Mar 5, 2015

[deleted comment]
@GoogleCodeExporter

This comment has been minimized.

Show comment
Hide comment
@GoogleCodeExporter

GoogleCodeExporter Mar 5, 2015

I tried the new UdpDriver fix from alex above but my browser seemed less 
responsive compared to my shortcut.  But, I modified alex's fix by replacing 
selector.select(500) with selector.selectNow() on line 182.  This is working 
for me and seems more responsive.  Was there a reason for using the select with 
a 500 millisecond delay?  It seems like that would add a half second delay to 
every dns lookup.

Though there is only a tiny difference I've attached my new modified UpdDriver.

Original comment by joexx...@gmail.com on 13 Nov 2011 at 5:11

Attachments:

GoogleCodeExporter commented Mar 5, 2015

I tried the new UdpDriver fix from alex above but my browser seemed less 
responsive compared to my shortcut.  But, I modified alex's fix by replacing 
selector.select(500) with selector.selectNow() on line 182.  This is working 
for me and seems more responsive.  Was there a reason for using the select with 
a 500 millisecond delay?  It seems like that would add a half second delay to 
every dns lookup.

Though there is only a tiny difference I've attached my new modified UpdDriver.

Original comment by joexx...@gmail.com on 13 Nov 2011 at 5:11

Attachments:

@GoogleCodeExporter

This comment has been minimized.

Show comment
Hide comment
@GoogleCodeExporter

GoogleCodeExporter Mar 5, 2015

I was just going by some example on use of Selector (I'm new to Android), and 
didn't have enough time on Friday to debug the code. Thanks for the fix!

Original comment by alex.bur...@gmail.com on 13 Nov 2011 at 11:21

GoogleCodeExporter commented Mar 5, 2015

I was just going by some example on use of Selector (I'm new to Android), and 
didn't have enough time on Friday to debug the code. Thanks for the fix!

Original comment by alex.bur...@gmail.com on 13 Nov 2011 at 11:21

@GoogleCodeExporter

This comment has been minimized.

Show comment
Hide comment
@GoogleCodeExporter

GoogleCodeExporter Mar 5, 2015

Joe,

I've checked your changes, and I can see you only modified one select(500) to 
selectNow(). Perhaps the second one (inside the loop) needs to be modified too ?

Original comment by alex.bur...@gmail.com on 13 Nov 2011 at 11:37

GoogleCodeExporter commented Mar 5, 2015

Joe,

I've checked your changes, and I can see you only modified one select(500) to 
selectNow(). Perhaps the second one (inside the loop) needs to be modified too ?

Original comment by alex.bur...@gmail.com on 13 Nov 2011 at 11:37

@GoogleCodeExporter

This comment has been minimized.

Show comment
Hide comment
@GoogleCodeExporter

GoogleCodeExporter Mar 5, 2015

You're right.  I've attached UdpDriver with both changed.  It seems to be 
working good for me.

Original comment by joexx...@gmail.com on 14 Nov 2011 at 12:50

Attachments:

GoogleCodeExporter commented Mar 5, 2015

You're right.  I've attached UdpDriver with both changed.  It seems to be 
working good for me.

Original comment by joexx...@gmail.com on 14 Nov 2011 at 12:50

Attachments:

@GoogleCodeExporter

This comment has been minimized.

Show comment
Hide comment
@GoogleCodeExporter

GoogleCodeExporter Mar 5, 2015

Can anyone compile a version of 2.02 for me with the new UDPDRIVER.java in it? 
I could probably compile it but im not sure I understanding how to sign it for 
a release so I can use it on my phone.

Original comment by QuadDra...@gmail.com on 15 Nov 2011 at 6:42

GoogleCodeExporter commented Mar 5, 2015

Can anyone compile a version of 2.02 for me with the new UDPDRIVER.java in it? 
I could probably compile it but im not sure I understanding how to sign it for 
a release so I can use it on my phone.

Original comment by QuadDra...@gmail.com on 15 Nov 2011 at 6:42

@GoogleCodeExporter

This comment has been minimized.

Show comment
Hide comment
@GoogleCodeExporter

GoogleCodeExporter Mar 5, 2015

I had to figure this out as well - wrote the few simple steps here - 
http://pullmonkey.com/2011/11/15/azilink-is-working-again/ if you are 
interested.  Also attached the apk.

Original comment by charles....@skizmo.com on 15 Nov 2011 at 1:44

Attachments:

GoogleCodeExporter commented Mar 5, 2015

I had to figure this out as well - wrote the few simple steps here - 
http://pullmonkey.com/2011/11/15/azilink-is-working-again/ if you are 
interested.  Also attached the apk.

Original comment by charles....@skizmo.com on 15 Nov 2011 at 1:44

Attachments:

@GoogleCodeExporter

This comment has been minimized.

Show comment
Hide comment
@GoogleCodeExporter

GoogleCodeExporter Mar 5, 2015

I'm still not getting this to work. I've checked out the SVN trunk, overwritten 
UdpDriver.java with the modified version, run "android update project" to make 
a build file, and then run "android debug install" to put Azilink on my device. 
However, soon after starting the service, it crashes with a SecurityException:

11-15 13:01:18.129: E/AndroidRuntime(16391): java.lang.SecurityException: 
Permission denied
11-15 13:01:18.129: E/AndroidRuntime(16391):    at 
org.apache.harmony.luni.platform.OSNetworkSystem.connect(Native Method)
11-15 13:01:18.129: E/AndroidRuntime(16391):    at 
dalvik.system.BlockGuard$WrappedNetworkSystem.connect(BlockGuard.java:357)
11-15 13:01:18.129: E/AndroidRuntime(16391):    at 
org.apache.harmony.nio.internal.DatagramChannelImpl.connect(DatagramChannelImpl.
java:160)
11-15 13:01:18.129: E/AndroidRuntime(16391):    at 
org.lfx.azilink.net.UdpDriver.<init>(UdpDriver.java:102)
11-15 13:01:18.129: E/AndroidRuntime(16391):    at 
org.lfx.azilink.net.UdpEngine.readRawPacket(UdpEngine.java:114)
11-15 13:01:18.129: E/AndroidRuntime(16391):    at 
org.lfx.azilink.net.VpnNatEngine.vpnRead(VpnNatEngine.java:239)
11-15 13:01:18.129: E/AndroidRuntime(16391):    at 
org.lfx.azilink.net.VpnLink.onRead(VpnLink.java:205)
11-15 13:01:18.129: E/AndroidRuntime(16391):    at 
org.lfx.azilink.net.SelectThread.run(SelectThread.java:144)
11-15 13:01:18.129: E/AndroidRuntime(16391):    at 
java.lang.Thread.run(Thread.java:1019)

The problem is that at UdpDriver.java:101, addr is occasionally {-1, -1, -1, 
-1}. Does anyone know how this is getting a bad value or what can be done about 
it?

Thanks for any help.

- Chris

Original comment by crj...@gmail.com on 15 Nov 2011 at 7:10

GoogleCodeExporter commented Mar 5, 2015

I'm still not getting this to work. I've checked out the SVN trunk, overwritten 
UdpDriver.java with the modified version, run "android update project" to make 
a build file, and then run "android debug install" to put Azilink on my device. 
However, soon after starting the service, it crashes with a SecurityException:

11-15 13:01:18.129: E/AndroidRuntime(16391): java.lang.SecurityException: 
Permission denied
11-15 13:01:18.129: E/AndroidRuntime(16391):    at 
org.apache.harmony.luni.platform.OSNetworkSystem.connect(Native Method)
11-15 13:01:18.129: E/AndroidRuntime(16391):    at 
dalvik.system.BlockGuard$WrappedNetworkSystem.connect(BlockGuard.java:357)
11-15 13:01:18.129: E/AndroidRuntime(16391):    at 
org.apache.harmony.nio.internal.DatagramChannelImpl.connect(DatagramChannelImpl.
java:160)
11-15 13:01:18.129: E/AndroidRuntime(16391):    at 
org.lfx.azilink.net.UdpDriver.<init>(UdpDriver.java:102)
11-15 13:01:18.129: E/AndroidRuntime(16391):    at 
org.lfx.azilink.net.UdpEngine.readRawPacket(UdpEngine.java:114)
11-15 13:01:18.129: E/AndroidRuntime(16391):    at 
org.lfx.azilink.net.VpnNatEngine.vpnRead(VpnNatEngine.java:239)
11-15 13:01:18.129: E/AndroidRuntime(16391):    at 
org.lfx.azilink.net.VpnLink.onRead(VpnLink.java:205)
11-15 13:01:18.129: E/AndroidRuntime(16391):    at 
org.lfx.azilink.net.SelectThread.run(SelectThread.java:144)
11-15 13:01:18.129: E/AndroidRuntime(16391):    at 
java.lang.Thread.run(Thread.java:1019)

The problem is that at UdpDriver.java:101, addr is occasionally {-1, -1, -1, 
-1}. Does anyone know how this is getting a bad value or what can be done about 
it?

Thanks for any help.

- Chris

Original comment by crj...@gmail.com on 15 Nov 2011 at 7:10

@GoogleCodeExporter

This comment has been minimized.

Show comment
Hide comment
@GoogleCodeExporter

GoogleCodeExporter Mar 5, 2015

Chris,

Are you sure you configured your vpn client right and are using the right dns 
address?  Udp is used mostly for dns lookups. My Mac's tunnelblick 
configuration has the dns set to 192.168.56.1  Or you could have some app on 
your computer using udp and trying an invalid address.  Admittedly, that 
shouldn't crash the service but that would fall under another issue.  


Original comment by joexx...@gmail.com on 16 Nov 2011 at 1:31

GoogleCodeExporter commented Mar 5, 2015

Chris,

Are you sure you configured your vpn client right and are using the right dns 
address?  Udp is used mostly for dns lookups. My Mac's tunnelblick 
configuration has the dns set to 192.168.56.1  Or you could have some app on 
your computer using udp and trying an invalid address.  Admittedly, that 
shouldn't crash the service but that would fall under another issue.  


Original comment by joexx...@gmail.com on 16 Nov 2011 at 1:31

@GoogleCodeExporter

This comment has been minimized.

Show comment
Hide comment
@GoogleCodeExporter

GoogleCodeExporter Mar 5, 2015

The DNS address on my Ubuntu system is the same as yours and is consistent 
across  *.ovpn and resolv.conf. I can get a few UDP requests through before a 
bad one comes down the pipe. I'm also on Android 2.3.3 on my Droid 2, if that 
makes any difference.

Original comment by crj...@gmail.com on 16 Nov 2011 at 3:42

GoogleCodeExporter commented Mar 5, 2015

The DNS address on my Ubuntu system is the same as yours and is consistent 
across  *.ovpn and resolv.conf. I can get a few UDP requests through before a 
bad one comes down the pipe. I'm also on Android 2.3.3 on my Droid 2, if that 
makes any difference.

Original comment by crj...@gmail.com on 16 Nov 2011 at 3:42

@GoogleCodeExporter

This comment has been minimized.

Show comment
Hide comment
@GoogleCodeExporter

GoogleCodeExporter Mar 5, 2015

Chris,
No idea why you're getting a bad ip.  Still could be some app on your linux 
computer.  You could try catching the SecurityException, logging the address 
and throwing an IOException instead.  This will hopefully drop a single 
UdpDriver and allow the azilink service to continue running.   Then look for 
stuff having problems or associated with the appearance of the bad address - 
look at running apps, play with nslookup, browse different sites, etc. 
Joe

Original comment by joexx...@gmail.com on 17 Nov 2011 at 1:57

GoogleCodeExporter commented Mar 5, 2015

Chris,
No idea why you're getting a bad ip.  Still could be some app on your linux 
computer.  You could try catching the SecurityException, logging the address 
and throwing an IOException instead.  This will hopefully drop a single 
UdpDriver and allow the azilink service to continue running.   Then look for 
stuff having problems or associated with the appearance of the bad address - 
look at running apps, play with nslookup, browse different sites, etc. 
Joe

Original comment by joexx...@gmail.com on 17 Nov 2011 at 1:57

@GoogleCodeExporter

This comment has been minimized.

Show comment
Hide comment
@GoogleCodeExporter

GoogleCodeExporter Mar 5, 2015

Perhaps it's failing to perform VpnNatEngine.getDnsIp(), which uses hidden API 
to retrieve the IP from the device. You can modify that method to return some 
IP at all times, like the default 4.2.2.2.

Original comment by alex.bur...@gmail.com on 17 Nov 2011 at 2:19

GoogleCodeExporter commented Mar 5, 2015

Perhaps it's failing to perform VpnNatEngine.getDnsIp(), which uses hidden API 
to retrieve the IP from the device. You can modify that method to return some 
IP at all times, like the default 4.2.2.2.

Original comment by alex.bur...@gmail.com on 17 Nov 2011 at 2:19

@GoogleCodeExporter

This comment has been minimized.

Show comment
Hide comment
@GoogleCodeExporter

GoogleCodeExporter Mar 5, 2015

Throwing IOException on addr = {-1, -1, -1, -1} seems to do the trick. This 
post is evidence. Thanks for the suggestion.

Original comment by crj...@gmail.com on 18 Nov 2011 at 1:59

GoogleCodeExporter commented Mar 5, 2015

Throwing IOException on addr = {-1, -1, -1, -1} seems to do the trick. This 
post is evidence. Thanks for the suggestion.

Original comment by crj...@gmail.com on 18 Nov 2011 at 1:59

@GoogleCodeExporter

This comment has been minimized.

Show comment
Hide comment
@GoogleCodeExporter

GoogleCodeExporter Mar 5, 2015

Am I right in concluding that azilink is a dead project?. It appears that 
nobody got it working on 2.3.4, 2.3.5 (my Samsung Stratosphere) and nothing has 
moved in this project since last year. I guess there is no other option but 
trying some of the other solutions, even if I have to pay a little for them.

Original comment by ptal...@gmail.com on 21 Apr 2012 at 6:51

GoogleCodeExporter commented Mar 5, 2015

Am I right in concluding that azilink is a dead project?. It appears that 
nobody got it working on 2.3.4, 2.3.5 (my Samsung Stratosphere) and nothing has 
moved in this project since last year. I guess there is no other option but 
trying some of the other solutions, even if I have to pay a little for them.

Original comment by ptal...@gmail.com on 21 Apr 2012 at 6:51

@GoogleCodeExporter

This comment has been minimized.

Show comment
Hide comment
@GoogleCodeExporter

GoogleCodeExporter Mar 5, 2015

I ran a 'release' build which includes Joe and Alex fix and has also the moth 
icon. It works fine on Samsung Strtosphere (gingerbread). Thank you Joe and 
Alex for the fix, and Charles for the short and to-the-point tutorial on 
building the Android app. It served as a nice intro to something new to me. I 
am attaching the build. Tempting to call this azilink-2.0.3.apk ...
Polo

Original comment by ptal...@gmail.com on 23 Apr 2012 at 4:24

Attachments:

GoogleCodeExporter commented Mar 5, 2015

I ran a 'release' build which includes Joe and Alex fix and has also the moth 
icon. It works fine on Samsung Strtosphere (gingerbread). Thank you Joe and 
Alex for the fix, and Charles for the short and to-the-point tutorial on 
building the Android app. It served as a nice intro to something new to me. I 
am attaching the build. Tempting to call this azilink-2.0.3.apk ...
Polo

Original comment by ptal...@gmail.com on 23 Apr 2012 at 4:24

Attachments:

@GoogleCodeExporter

This comment has been minimized.

Show comment
Hide comment
@GoogleCodeExporter

GoogleCodeExporter Mar 5, 2015

Chris, even though I don't have the problem you describe, could  you post your 
"Throwing IOException on addr = {-1, -1, -1, -1} seems to do the trick." 
solution? the .java affected, I mean, so that I can include your fix into the 
build. One little problem less for other brave users that dare to install this 
unsupported app. Thanks!
-Polo

Original comment by ptal...@gmail.com on 23 Apr 2012 at 9:09

GoogleCodeExporter commented Mar 5, 2015

Chris, even though I don't have the problem you describe, could  you post your 
"Throwing IOException on addr = {-1, -1, -1, -1} seems to do the trick." 
solution? the .java affected, I mean, so that I can include your fix into the 
build. One little problem less for other brave users that dare to install this 
unsupported app. Thanks!
-Polo

Original comment by ptal...@gmail.com on 23 Apr 2012 at 9:09

@GoogleCodeExporter

This comment has been minimized.

Show comment
Hide comment
@GoogleCodeExporter

GoogleCodeExporter Mar 5, 2015

Well, I can't recommend the solution. Verizon just pushed out the 2.3.4 update 
(I had 2.3.3). After commenting out my hack fix and reinstalling, the problem 
appears to have been resolved.

While the workaround was in place, my connection was slow and flaky.

Original comment by crj...@gmail.com on 24 Apr 2012 at 2:05

GoogleCodeExporter commented Mar 5, 2015

Well, I can't recommend the solution. Verizon just pushed out the 2.3.4 update 
(I had 2.3.3). After commenting out my hack fix and reinstalling, the problem 
appears to have been resolved.

While the workaround was in place, my connection was slow and flaky.

Original comment by crj...@gmail.com on 24 Apr 2012 at 2:05

@GoogleCodeExporter

This comment has been minimized.

Show comment
Hide comment
@GoogleCodeExporter

GoogleCodeExporter Mar 5, 2015

I will confirm that I am now successfully connecting with the apk from Comment 
15.  I tried it a few months ago on my Droid 2 running 2.3.4 and it failed, but 
now it is working with the 2.3.4, I'm running build number 4.5.1_57_DR4-51.  

Original comment by Tully.Foote on 18 May 2012 at 6:42

GoogleCodeExporter commented Mar 5, 2015

I will confirm that I am now successfully connecting with the apk from Comment 
15.  I tried it a few months ago on my Droid 2 running 2.3.4 and it failed, but 
now it is working with the 2.3.4, I'm running build number 4.5.1_57_DR4-51.  

Original comment by Tully.Foote on 18 May 2012 at 6:42

@GoogleCodeExporter

This comment has been minimized.

Show comment
Hide comment
@GoogleCodeExporter

GoogleCodeExporter Mar 5, 2015

The azilink-release.apk build worked like a charm on my Droid 4 with whatever 
the current android release is on Verizon. Thanks, you really saved me.

Original comment by gone...@gmail.com on 20 Jun 2012 at 12:15

GoogleCodeExporter commented Mar 5, 2015

The azilink-release.apk build worked like a charm on my Droid 4 with whatever 
the current android release is on Verizon. Thanks, you really saved me.

Original comment by gone...@gmail.com on 20 Jun 2012 at 12:15

@GoogleCodeExporter

This comment has been minimized.

Show comment
Hide comment
@GoogleCodeExporter

GoogleCodeExporter Mar 5, 2015

The azilink-release.apk build also works for me with my Droid Incredible 
running 2.3.4, thanks a lot!

Original comment by mcase...@gmail.com on 4 Jul 2012 at 2:10

GoogleCodeExporter commented Mar 5, 2015

The azilink-release.apk build also works for me with my Droid Incredible 
running 2.3.4, thanks a lot!

Original comment by mcase...@gmail.com on 4 Jul 2012 at 2:10

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment