Android 1.71 Update

** Please keep discussions in this thread about the latest updates, thanks**

Sit back relax get a coffee or tea ready cos this is gonna be long. This is my own analysis I have not spoken with Cam or Sean since the update came through.

Firstly I had been checking the app store since Thursday, twice a day looking for the update and it never appeared on my phone.Sunday afternoon I experienced some problems with the app out of the blue so i uninstalled and when i reinstalled I had the updated version. The app store still was showing the old version when i clicked install. After it was installed it was showing the new version and saying it was available from the 4th.

Anyways upon installation my problems continued. with Wangle on i couldn't do a thing not even Speed test. I ran a few other test and my ping was through the roof (over 600ms to get to Sydney). I tried swapping servers and ports didnt seem to make a difference. I uninstalled, restarted phone, installed, changed to port 443, and connected. I was then able to browse with no problems. I was visiting family, so I was on Reddit looking at funny's mostly - few videos, gifs, and news articles ( i think they had an election in america recently and people aren't happy). after about 30 minutes I checked Wangle and i was very surprised, about 211 megabytes saved of and 301 megabytes used (or about 70% savings). So i then ditched the family and came home to do proper testing.

I setup what is called a Man in the Middle attack on myself. To do this I had my laptop become a wireless network router and then capture all network traffic with a program called Wireshark. The network looked like this

Phone  <--> Laptop  <-->  Real Router   <--> Internet  <-->  Wangle

The laptop capturing every packet then let me see everything that was going in and out of my phone and how the app was working in more detail. First thing i did was set a baseline, i downloaded a 1.6 gig Linux distro (different to the previous one and from a different mirror, so that nothing could be cached). That download took 43 minutes on a capped 8 megabit connection.

I then left Wangle on the default port and settings and to be honest i didn't even let it finish. It was taking well over an hour and I had the information i needed. From the Packet Capture and the bandwidth utilization i had everything i needed.



Wangle was trying very valiantly but the data wasn't being allowed through. Every time the speed got up the ISP would smash it back down, and i could see the same thing happening in the packet capture also.

I then changed to port 443, now this port is normally used for mail clients so ISP's generally wont touch it with any sort of shaping or limiting which is why i chose it. And i have to say that the packet stream looked beautiful and predictable. Here is what the bandwidth utilisation looked like.


this photo was taken about 20 minutes after the first with the only change being the port number in the app. This clearly demonstrates that the problem that WGL identified with ISP's throttling ports is happening. I have tested this on both Telstra and Optus networks and have experienced it on both and as such i would recommend for everyone to change ports.

** Sean when you read this, tell the guys to just set another port as default, 55010 is dead as far as I can tell.

To change ports on android should just be a case of
disconnecting (recommended) -> going to settings -> selecting connection port -> and choosing one of the other options

However, it seems this has not worked for some people. So, uninstall the app, restart phone, install app, choose new port, then connect. If you still experience problems make a post and i will see what i can do.

OK on to more interesting data capturey stuff.

I can confirm that the data savings reported in the app line up with my own findings. However In my downloads I only had a couple of percent of data savings. Their was however a significant speed increase where the download went from 43 minutes with no wangle to 29 minutes with Wangle. So it saved about 1/3 of the time. This is pretty impressive. It seems this has been achieved by the way acknowledgement packets are handled and also the complete absence of error packets as far as i can tell. When i ran my normal download there was a portion of packets that were duplicated and had errors etc in them, this is completely normal in network traffic. When connected to Wangle I struggled to find any in over 5 gig of data transfers that is astounding. I am going to be going through the data more closely today but i wanted to provide you guys with some details.

Also the sequence that the packets are sent in is completely different to normal network traffic also. Wangle sends a request for acknowledgements and a burst of them gets sent all at once. I can also see that they are all encrypted which is good also.

Anyways i think that will do for now. Ill keep going through it and will try to answer your questions in this thread.

to sum up though:-

Looks like web/http(s) data saving has been enabled on Android
Good savings on general Web browsing
ISP are blocking WGL
Need to change ports
File downloads not experiencing data savings yet however speed savings still there maybe a little faster
Encryption on ACK packets
Minimal to No error on the Wangle streams when no ISP blocking

~~Maglor