gitmahmud / sandrop

Automatically exported from code.google.com/p/sandrop
0 stars 0 forks source link

Drony 1.2.85 does not work on Android 5.1.0 #117

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
Since I upgrade my phone from Android 5.0.x to 5.1.0, Drony does not work 
anymore.

I think one or more security mechanism has changed by Android 5.1.0. I observed 
the startup behavior of Drony, and found:

1. I rebooted the phone, and click the ON button of Drony, there should be a 
popup of VPN trust message and let me confirm the trust of VPN, but in 5.1.0, 
the popup never appear.

2. I checked the log of output, Drony looks unable to bind the local port 8019 
and 8020.

Hope you can take a look on this issue. The performance of Android 5.1.0 is 
pretty good than I expected, much faster than 5.0.x and 4.x. I am not going to 
rollback to the old version of system.

Original issue reported on code.google.com by janvier....@gmail.com on 18 Mar 2015 at 1:36

Attachments:

GoogleCodeExporter commented 8 years ago
Please reboot again. And clear Drony data in os settings.
But will try to look at it on 5.1 asap. At least vpn should start properly...

Original comment by supp.san...@gmail.com on 18 Mar 2015 at 4:01

GoogleCodeExporter commented 8 years ago
I have stopped Drony service, cleared Drony data and rebooted the phone, but 
ends up I got the same result as previous.

But, I also noticed there is a loop that Drony was trying to establish the VPN 
tunnel but failed, and establish again and failed again. I think the issue 
should be on the establishment of VPN tunnel because I still unable to see the 
system popup of VPN confirmation.

Original comment by janvier....@gmail.com on 18 Mar 2015 at 9:27

GoogleCodeExporter commented 8 years ago
One more interesting thing - I just found there is a null pointer exception in 
the log messages. I am using an AOSP compiled ROM on Galaxy Nexus right now. 
Not sure whether your Nexus 5 has such one ROM on XDA or somewhere else, or you 
can wait for the OTA update from Google.

Original comment by janvier....@gmail.com on 18 Mar 2015 at 9:35

Attachments: