I'm not sure whether this post belongs here, but I have googled high and low and I have not found anything that directly pertains to my Samsung Galaxy S2 issue. And here at XDA, the VPN questions seem to be about private VPNs (not commercial).
I am currently running Android 2.3.4 Gingerbread.XXKG6
I follow these steps for connecting to a LT2P
www_dot_hopthewall_dot_com/wiki/wiki/Android_L2TP_Over_IPSec
And these for PPTP
www_dot_hopthewall_dot_com/wiki/wiki/Installing_personalVPN-PPTP_on_Android_Mobile_Phone
I have tried the PPTP and L2TP
Both fail to connect
L2TP yields:
"Unable to connect to network. Try again?"
But no additional error message.
PPTP however, seems to allow the connection.
I connected a few times.
I used pptp.sfo.witopia.net. as the VPN server
That seemed to let me connect a few times;
and according to hide-my-ip.com I had an L.A. IP
But now, when I try to connect, I'm getting an error message that reads:
"Server hung up. User name or password incorrect. Try again?"
But I didn’t do or change anything. I just tried to connect as usual.
I've tried
restarting the phone.
waiting a while.
Connecting with the computer (connects without a problem)
I tried connecting to the different VPN servers.
I also tried connecting changing the VPN server from URL to an IP address,
but that just tells me "Unable to connect to network. Try again?"
I am at a loss...
I have tried at home, on my wifi account...
The same one that my computer is on, but no dice.
The VPN service provider is also at a loss.
They said "...iPhones connect all day..." (talk about a kick in the teeth)
They asked me if I wanted to cancel my account and request a refund.
Nice.
Thanks for the replies.
This forums are always so helpful.
No, that's okay, don't get up. I'll get that.
A two part work around I found was:
PART I
Sharing the VPN Connection Over WiFi by Converting my Laptop into WiFi VPN Router. An article by BESTVPNSERVICE.COM
Using a Windows 7 machine with a Wi-Fi NIC
1) Click on your computers start button and in the search box type “cmd” and wait for it to appear on the menu.
2) After it appears, right click on it and select “Run As Administrator”.
3) When the Black Command Prompt Opens up, type the following command and press enter
4) netsh wlan show drivers
5) You will see something like the following image. If the ‘Hosted Network Supported’ (in the red square) say ‘Yes’, it means the driver is installed and if it says ‘No’, download the drivers.
6) Once it is made sure that you have the required driver, it’s time to set it up.
7) Type netsh wlan set hostednetwork mode=allow ssid=test key=password. Following Screen would appear. (Devices will detect network SSID as “test” change it to anything you want. Moreover, ‘key’ is your password which in this case is ‘password’, change it to whatever you want, I would suggest you to not to use numbers in password)
8 ) Then type, netsh wlan start hostednetwork. You will see the messages illustrated in the snap shot.
9) If you see the message that the ‘hosted network couldn’t be started’, then your WiFi driver is outdated, the best way to update the WiFi driver is Run you Windows Update or download the latest version from its official website.
10) Now that we have setup hosted network, we will make sure that it is shared on public Wi-Fi.
11) To do this, click on your Wi-Fi signal buttons on the bottom right hand corner of your screen.
12) Click on ‘Open Network and Sharing Center’.
13) Then click on Change adapter settings.
14) Click on the Connection that has description of ‘Your Created VPN Connection’ and right click on the Icon to go to its properties.
15) In Properties, go to ‘Sharing’ tab and check on ‘Allow Other Network User to connect through this computer…’
16) From the drop down menu of ‘Home Networking Connection’, Select the connection which had a description of ‘Microsoft Virtual WiFi Miniport Adapter’/’Virtula AP’ or it can be ‘Wireless Network Connection 2’ as in my case.
17) Check on the ‘Allow other network users to control or disable….’ Option as well.
18) Click ok and you are all set to go now.
19) Connect your VPN and ask your Friends or Colleague to discover your VPN enabled WiFi Connection.
20) Now, whenever you will restart your computer, your Shared WiFi connection will be disabled. You will have to reenter only the following command in the command prompt to enable it again.
netsh wlan start hostednetwork (or create a custom batch file for this, if you want to avoid reentering the command every time).
PART II
If the wi-fi direct on your phone isn't discovering your freshly created network,
you may need enable Ad Hoc connections for it.
For that I looked at an article here; but instead of Root Explorer is simply used ES Explorer:
Download this version of wpa_supplicant
Like I said, I used "ES Explorer"
• use "ES Explorer" to mount /system/bin/ and make a backup of wpa_supplicant
• rename the current one to wpa_supplicant.bak and copy the new wpa_supplicant to /system/bin
• then we need to adjust the permissions on the file to:
ticked - All options in the read and execute columns; and write column owner row
unticked - write column & group row; write column & others row.
• change /system/bin back to read only
• disable and re-enable wireless
• now your adhoc wireless network should be listed with the other wireless networks and you can connect.
After this two maneuvers, I was able to connect my phone to my laptop using my laptop's internet access and thus connecting to the VPN.
I find that the order of network activation matters.
What I mean is:
First connect to the internet (router, modem, or however that may be)
Then connect to the VPN
And then activate and connect to the hostednetwork.
I hope this helps someone, despite the fact that you have to be within wifi range of your windows machine. It's not quite the same as being on the streets and connecting to your VPN -but Android can't [consistently and reliably] connect to VPNs. And since no one replied to me here it stands to reason that no one knows how to get Android to connect to commercial VPN services (not even WiTopia's tech support).
(tl;dr, experienced modders: skip to the steps section below)
I've spent several days trying to set up sharing of my mobile phone's Internet connection with my tf201. The phone (Nokia 6120 classic, running Symbian S60) has neither WIFI, nor bluetooth PAN (don't worry, the terminology is explained below), and there's no PDANet version available for it, which left me with two ways to tether with it: wired USB connection or bluetooth DUN. I show here how to configure both. You might want to do this if you're in a similar position as myself, but also if you want to replace wifi tethering with bluetooth DUN (bluetooth is said to be less power-hungry).
While I'd like the howto to be accessible to novices (such as myself), I can't cover basic/trivial parts and in general will assume a reader capable of googling and with a basic Linux familiarity.
This post does NOT relate to the issue of enabling bluetooth DUN on your Android phone or changing the server side of the connection in other ways. Please don't comment about that in this thread.
My primary source is this outstanding article in Russian, which solves the same problem for a different tablet: notioninkinfo.ru/telefon_kak_3g_edge_modem_dlya_adama/
The process turned out to be much simpler for Prime, since it has most of the necessary software in place.
Background
Sharing internet connection from your mobile phone to another device is called "tethering". Obviously, tethering has great importance when mobile devices are involved, thus a naive soul could hope that it works perfectly in Android. Surprisingly, the opposite is the truth: Android hates tethering with passion; so much that (stupidity being inapplicable) I have no choice but to suspect malice on Google's/ASUS's part. It's not that they lack the resources to implement it; or that the feature requires some kind of special know-how they don't have. No: all these features are present and work in vanilla Linux; the appropriate kernel drivers exist and work; in some cases, the features worked in earlier versions of Android, but have been disabled in later ones. Some bugtracker issues related to this have not received any attention, despite having tens to hundreds of comments from angry users. code.google.com/p/android/issues/detail?id=16717&q=dun&colspec=ID%20Type%20Status%20Owner%20Summary%20Stars
/rant
About tethering
There are multiple ways to do tethering that I know of (and probably then a few more). Most of them, unfortunately, are not enabled out of the box or even implemented in Prime at all.
1. Wifi hotspot: this works well *if* your phone supports it. "Hotspot" means that the device acts as a kind of router that is "meant" to accept connections from other devices and not just "happens" to have wifi. AFAIK, from the practical perspective, the only distinction is that the devices present themselves differently.
2. Adhoc wifi: this is the opposite of "hotspot wifi". Transformer Prime with Ice Cream Sandwich (ICS) does not currently support connecting to an adhoc wifi network directly. The feature was present and worked fine in some previous Android versions, but thanks to an offending kernel commit, no longer works in ICS. The only known workarounds are PDANet (see below) or making a custom ROM with a patched kernel. I don't recommend trying the latter at this time, as very few brave souls have already done it, and that was the last anyone heard of them I don't know if all the issues have been ironed out.
3. Bluetooth. There are two ways of connecting through Bluetooth (that I know of). In order to work, both require certain capabilities, or profiles, to be enabled on your phone. It is quite possible none of the two profiles are enabled or even implemented, in which case you're screwed.
3.1. PAN (Personal Area Network): treats the phone as an intelligent device. When connecting to the Internet, the client "asks" the server to establish the link and only forward data from and to the client. This is one of the best ways to do tethering, and fully supported by Prime's user interface out of the box.
3.2. DUN (Dial-Up Networking): treats the phone as a "dumb" device: the client takes over the phone's modem and uses it directly by sending it both commands and data through an emulated serial (RS232) link. This has several disadvantages, among them it requires the client to be aware of the line provider's dial-up config, such as service number, service name, user and password. Prime does not support it out of the box, despite (as we will see) having adequate hardware and software for it.
4. PDANet: this is an application (accessible from the market) that somehow circumvents Prime's and Android's restrictions on wifi and BT connectivity. You install it on both devices, configure it, and it should work. This method is only applicable to a few platforms that PDANet supports, including Android, but not Symbian.
5. USB: if your Prime has the dock, you've got a full-size USB port on it, which can act as a USB host. You can use this port to connect to your mobile phone (if your phone supports it). In some cases, connecting the phone will cause the Prime to discover the phone's modem, and once it is discovered, you can use it just like DUN.
Methods available out of the box: (1), (3.1). Methods this howto is concerned with: (3.2) and (5).
Prerequisites
1. Ice Cream Sandwich (ICS). It is possible the guide will work with earlier versions, but I didn't try it.
2. The tablet is rooted.
3. adb is installed.
There are plenty of other topics that explain how to get these.
Steps
(Note that I'm writing this from memory, so some inaccuracies are inevitable.)
1. connect the tablet to your PC with adb and execute:
Code:
adb shell
2. become superuser:
Code:
su
3. make /system writable:
Code:
mount -o rw,remount /system
4. download the attached ppp scripts
5. download a pre-compiled rfcomm binary here: omappedia.org/wiki/Android:_Working_with_pre-built_binaries
... or build it yourself. Or, if you're stupid enough to trust a random person on the internet, you can use the rfcomm binary included in the attachment.
6. gather the necessary info:
6.1. for USB:
6.1.1. connect your phone to the tablet by USB cable and try to make the tablet recognize it as a modem. This could vary from phone to phone. My 6120c Nokia needs to be connected in "Nokia PC Suite" mode.
6.1.2.
Code:
ls /dev/tty*
. If it worked, you should see new device(s) in the list. In my case, I got /dev/ttyACM0 and /dev/ttyACM1. I'm not sure why it creates two devices instead of one, but using /dev/ttyACM0 seems to work fine.
6.2. for DUN:
6.2.1. enable bluetooth both in the tablet and in the phone and pair them
6.2.2.
Code:
sdptool search DUN
The output should look like this:
Code:
Searching for DUN on [B]00:1E:A4:66:94:2E[/B] ...
Service Name: Dial-Up Networking
Service RecHandle: 0x10019
Service Class ID List:
"Dialup Networking" (0x1103)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: [B]2[/B]
7. Using the above information, fill the placeholders in the scripts you downloaded. In particular, the following must be replaced with real settings:
7.1. the device on line 8 in 3g_usb. Replace "/dev/ttyACM0" with the device you got in step 6.1.2
7.2. MAC and channel in 3g_bt_up. Use the values you got in step 6.2.2.
7.3. username and password in 3g_usb and 3g_bt. If you can use mobile internet from your phone, these values are already stored in the phone, so you just need to find them in the settings. Failing that, search for the correct values for your operator on the net (they are often the same for all users of the operator) or inquire the operator.
7.4. host name in 3gchat. Again, this varies from operator to operator. Note that the host name need not end with "com" or another valid root domain, and can thus sound nonsensical, e.g. "internet.internet". In my case (Israeli operator called Rami Levi), it was "internet.rl".
7.5. There are more operator-specific settings you might need to change in 3gchat, e.g. the dial-up number. In case the current value (*99***1# in my script) doesn't work, you can most likely find those on the net. If it doesn't work, search the net with query like "pppd chat <MY OPERATOR>" (without the quotes).
8.
Code:
adb push 3gchat /etc/ppp/
adb push 3g_bt_pdown /system/bin/
8.1. for usb connectivity:
Code:
adb push 3g_usb /etc/ppp/peers/
adb push 3g_usb_pup /system/bin/
6.2. for DUN connectivity (mind the trailing slashes):
Code:
adb push 3g_bt /etc/ppp/peers/
adb push 3g_bt_pup /system/bin/
adb push rfcomm /system/xbin/
7.
Code:
adb shell
chmod 0755 /etc/ppp/3gchat /system/bin/3g_usb_pup /system/bin/3g_usb_pdown /system/bin/3g_bt_pup /system/bin/3g_bt_pdown /system/xbin/rfcomm
8. try running 3g_bt_pup and 3g_usb_pup in adb
9. if it works, find a way to run these scripts directly on the Prime. E.g., you might want to make a GUI launcher for every one of 3g_bt_pup, 3g_usb_pup, 3g_pdown. The author of the original article recommends an app called GScript. I personally never tried it, as I just use Terminal Emulator from the market.
10. (Don't forget to remount /system in ro mode.)
Known issues
1. DNS refuses to work when you connect through the scripts. A workaround that I found is to connect to a wifi, then disconnect, then connect using the scripts. DNS will continue working until the next reboot. (I didn't have enough time to play with it yet, so not sure this is consistent.)
2. I consistently get 2-3 times slower download speed through DUN than through USB. Perhaps this has something to do with my phone, OTOH could be a problem in the scripts.
Enjoy! Corrections, tweaks, fixes are welcome.
Thank you very much!
I was trying to bring the tablet into the internet using bluetooth DUN for days. Your rfcomm, skripts and complete explanations did the trick: Archos G9 10.1 with Android 4.0.4 (Archos: 4.0.25) connects to Nokia N79 and dials into the internet.
neatfires said:
Known issues
1. DNS refuses to work when you connect through the scripts. A workaround that I found is to connect to a wifi, then disconnect, then connect using the scripts. DNS will continue working until the next reboot. (I didn't have enough time to play with it yet, so not sure this is consistent
Click to expand...
Click to collapse
Do you already have a solution for this problem?
I see strange behavior:
What I tried:
I had a look into syslog (using logcat) which reveals the DNS servers of the 3g provider.
Then I entered this IP-address in /etc/resolv.conf
Result:
* traceroot resolves the names but
* ping does not,
* ICS Browser+ does not and
* K9 does not resolve the DNS names
Do you have any idea how this problem could be solved?
Best regards,
Pfeffer2de.
Hi pfeffer2de,
Unfortunately, I don't have any other solution to this problem than the workaround I mentioned (connecting to the wifi before using DUN). I haven't used DUN at all since late spring, so I have no new input on this. If you find a solution, please post it here for other people to learn about it.
Hi neatfires!
neatfires said:
Unfortunately, I don't have any other solution to this problem than the workaround I mentioned (connecting to the wifi before using DUN). I haven't used DUN at all since late spring, so I have no new input on this. If you find a solution, please post it here for other people to learn about it.
Click to expand...
Click to collapse
I have to admit that I do not really understand what do you mean: Of couse the tablet has been connected to an Wifi access point some time before.
I rooted the device, connected to a wifi hotspot, made your steps and connected bluetooth DUN finally. Ok, I had some tries to succeed in connecting DUN. Anyway I had the DNS problems. So what is the difference to your work a round, at what point in time the wifi should be connected?
BTW: I switched wifi off before connecting bluetooth DUN.
Best regards,
Pfeffer2de.
pfeffer2de said:
Hi neatfires!
I have to admit that I do not really understand what do you mean: Of couse the tablet has been connected to an Wifi access point some time before.
I rooted the device, connected to a wifi hotspot, made your steps and connected bluetooth DUN finally. Ok, I had some tries to succeed in connecting DUN. Anyway I had the DNS problems. So what is the difference to your work a round, at what point in time the wifi should be connected?
BTW: I switched wifi off before connecting bluetooth DUN.
Best regards,
Pfeffer2de.
Click to expand...
Click to collapse
I can't remember all the details now, but the post says that you need to connect to a wifi, and then DNS works until the reboot, so it must be true . Anyway, try this:
1. fill in a valid DNS host in resolv.conf
2. connect to a wifi network, make sure you can reach internet
3. disconnect from the wifi network, but don't turn off the wifi
4. connect through the DUN
If it works, try doing the same but turn off the wifi. I can't remember currently if I had to have wifi on or off (I think I didn't), but this is the only thing I can think of.
Almost working, bit missing on
neatfires said:
I can't remember all the details now, but the post says that you need to connect to a wifi, and then DNS works until the reboot, so it must be true . Anyway, try this:
1. fill in a valid DNS host in resolv.conf
2. connect to a wifi network, make sure you can reach internet
3. disconnect from the wifi network, but don't turn off the wifi
4. connect through the DUN
If it works, try doing the same but turn off the wifi. I can't remember currently if I had to have wifi on or off (I think I didn't), but this is the only thing I can think of.
Click to expand...
Click to collapse
I tried it on my Motorola Atrix 4G which doesn't support 'reverse DUN' as such and I had to use my GPRS phone due to data plans reaching limits on Atrix 4G.
OK, here is original '3gchat' file, I just filled in releavant APN
--------------------------------------------------------------------------
#!/system/bin/sh
exec /system/bin/chat \
TIMEOUT 5 \
ECHO ON \
ABORT '\nBUSY\r' \
ABORT '\nERROR\r' \
ABORT '\nNO ANSWER\r' \
ABORT '\nNO CARRIER\r' \
ABORT '\nNO DIALTONE\r' \
ABORT '\nRINGING\r\n\r\nRINGING\r' \
'' AT \
OK ATH \
OK ATE1 \
OK 'AT+CGDCONT=1,"IP","<APN>","0.0.0.0",0,0' \
OK ATDT*99***1# \
TIMEOUT 22 \
CONNECT ""
----------------------------------------------------------------------------
It hangs at $ exec /system/bin/chat \ 'Permission Denied'
If i delete above line (exec /system/bin/chat \ ) from 3gchat, it connects and remain conencted to BTDUN to my GPRS phone until I diconenct it, however there is no data. Following is after deleting line "exec /system/bin/chat \ "
-----------------------------------------------------------------------------
#!/system/bin/sh
TIMEOUT 5 \
ECHO ON \
ABORT '\nBUSY\r' \
ABORT '\nERROR\r' \
ABORT '\nNO ANSWER\r' \
ABORT '\nNO CARRIER\r' \
ABORT '\nNO DIALTONE\r' \
ABORT '\nRINGING\r\n\r\nRINGING\r' \
'' AT \
OK ATH \
OK ATE1 \
OK 'AT+CGDCONT=1,"IP","<APN>","0.0.0.0",0,0' \
OK ATDT*99***1# \
TIMEOUT 22 \
CONNECT ""
---------------------------------------------------------------------------------
Infact, there wasn't any /system/bin/chat directory so I created one to comply with 3gchat sript. Yet above permission denied issue remained, until I deleted the "exec...." line.
I found someone adding follwing line in the shell script file connecting his chat file to /usr/sbin/chat :
connect '/usr/sbin/chat -v -f /etc/ppp/<chatfile name>'
Above quotes /usr/sbin/chat while '3gchat' script uses /system/bin/chat.
I am missing something here.
One a side note, I tried BlueVPN from the marked which worked.
UPDATEver
OK I installed BlueDUN on my Xolo X900 (which doesn't support reverseDUN, i.e. it doesn't natively support Bluetooth Dial-Up Modem profile, butr it can dial-up other Bluetooth Dial-Up Modems, i.e. other phones). This software enabled Xolo X900 to become a software Bluetooth Dial-Up Modem (as it natively doesn't have this feature like most android devices)
On another anrdoid device (Atrix 4G) I installed BlueVPN (please note this becomes almost mandatory somehow as until target phone natively supports reverseDUN, other btDial-Up softwares will not be able to detect (via sdptool) target phone until it has native reverseDUN (Bluetooth SPP per say). Then removed old pairing and repaired both devices again. After that, the most importatnt is to swicth on WiFi Tethering on target phone (in my case Xolo X900) and connect host phone (Atrix 4G in my case) to the WiFi Tether of Xolo X900. Whie WiFiTether is active, start BlueDUN on target phone (Xolo X900) and then start BlueVPN on host android device (Atrix 4G). This will make a working internet connection and you will be able to connect it via VPN setup. After net is connected you can turn off WiFi tethering and switch off wifi on both devices. WiFi thethering is required initially till internet starts working as it sorts out DNS issues.
As long as target phone is 3G or 4G, speed is not a problem. I am usining this BlueDUN + BlueVPN combo to post this.
I am resolved that BT tethering method of OP will not work in my setup wihout setting up VPN because I have been able to establish connection but still couldn't get any net traffic.
For the record, its not android that "hates tethering" - its the carriers that block, disable, or remove those capabilities, because they want to charge you more for the same service based on what device (eg your laptop) you use it with.
I have a Samsung Galaxy S III and I have a problem which occurs on all the roms I have tried so far: Paranoid Android, Cyanogenmod and Ultimarom: When using Automateit to frequently turn wifi on and off, wifi breaks after a while (no fixed time, sometimes there are days without problems), which means wifi can not be turned on again, neither manually, nor automatically. When turning it on, no networks are shown. The only fix is a reboot.
Now I am looking for a solution which could avoid the reboot. I want to now if there are shell commands to restart/reload the wifi module manually. Then I could use the Automateit-Shell extension to frequently do this automatically. Does anyone know how to do this?
Samba
sambahb said:
I have a Samsung Galaxy S III and I have a problem which occurs on all the roms I have tried so far: Paranoid Android, Cyanogenmod and Ultimarom: When using Automateit to frequently turn wifi on and off, wifi breaks after a while (no fixed time, sometimes there are days without problems), which means wifi can not be turned on again, neither manually, nor automatically. When turning it on, no networks are shown. The only fix is a reboot.
Now I am looking for a solution which could avoid the reboot. I want to now if there are shell commands to restart/reload the wifi module manually. Then I could use the Automateit-Shell extension to frequently do this automatically. Does anyone know how to do this?
Samba
Click to expand...
Click to collapse
From terminal on your phone:
1.
Code:
su
ls /sys/class/net
It will list your interfaces. For wlan it will probably be wlan0.
Then:
2.
Code:
ifconfig wlan0 down
For bringing it up:
3.
Code:
ifconfig wlan0 up
Tried on my stock 4.3 now, works ok for going down. But it automatically brings it up after ~ 10 secs.
Hi. I have very weird issue with my both WiFi and cellular icons on my OPX_Lin15 phone.
What I am experiencing is that both WiFi and cellular icons have small 'x' symbol in the strength bar and basically it says that "connected, not internet" .
I can browse an internet on both WiFI and cellular, but I cannot download any apps from Google Play "Pending Download".
This started suddenly without system being updated and it happens on all networks (tested home/office wifi and cell provider)
Have tried follows
- reboot home router
- reset network settings
- reset / delete cache and data of Google Play
- flash the latest Lineage 15 ROM
Still same issue, Thank you
vecoo said:
Hi. I have very weird issue with my both WiFi and cellular icons on my OPX_Lin15 phone.
What I am experiencing is that both WiFi and cellular icons have small 'x' symbol in the strength bar and basically it says that "connected, not internet" .
I can browse an internet on both WiFI and cellular, but I cannot download any apps from Google Play "Pending Download".
This started suddenly without system being updated and it happens on all networks (tested home/office wifi and cell provider)
Have tried follows
- reboot home router
- reset network settings
- reset / delete cache and data of Google Play
- flash the latest Lineage 15 ROM
Still same issue, Thank you
Click to expand...
Click to collapse
You have got 2 options:
1) If you have got root, you can enable the local terminal in developer options, then open the terminal and then write:
su -c "adb shell settings put global captive_portal_mode 0"
enter & reboot the phone.
2) over usb cable connected to the phone with adb on your PC:
Open a comand line window and go to the dir where you've got the adb & fastboot.
Write:
adb shell<enter>
settings put global captive_portal_mode 0<enter>
reboot the phone
I got this but i managed to fix it.
Code:
adb shell
settings put global captive_portal_mode 0
Now switch on airplane mode then switch it back off
Code:
settings put global captive_portal_https_url https://clients3.google.com/generate_204
settings put global captive_portal_http_url https://clients3.google.com/generate_204
settings put global captive_portal_mode 1
Now switch airplane mode on then switch it back off.
Fixed and you retain your ability to have captive portal detection