Hi,
i cannot connect to any wifi, with password or not, it just saying obtaining ip adress, and then the network disapeare or it just write saved under the network, sometimes i cannot even see any networks, i tried many roms, on all its the same.
currently i am using aokp mix rom, faux kernel 1.45.
please help, thank you
aspico said:
Hi,
i cannot connect to any wifi, with password or not, it just saying obtaining ip adress, and then the network disapeare or it just write saved under the network, sometimes i cannot even see any networks, i tried many roms, on all its the same.
currently i am using aokp mix rom, faux kernel 1.45.
please help, thank you
Click to expand...
Click to collapse
Logcat will help you.
If you are on linux:
Code:
adb logcat -d > /tmp/logcat.txt
grep -i 'wifi\|wpa' /tmp/logcat.txt
On windows, use "adb logcat" saving the output to a text file, like my example above. Try to find strings containing wifi and wpa (or wpa_supplicant).
This way you will know what is really happening.
epinter said:
Logcat will help you.
If you are on linux:
Code:
adb logcat -d > /tmp/logcat.txt
grep -i 'wifi\|wpa' /tmp/logcat.txt
On windows, use "adb logcat" saving the output to a text file, like my example above. Try to find strings containing wifi and wpa (or wpa_supplicant).
This way you will know what is really happening.
Click to expand...
Click to collapse
huh can you explain it a little more better, where i have to write this above? i am on windows...on my atrix i have terminal emuluator, have i there to write this?
There have been several reports over the months of people having trouble connecting to one manufacturers routers..........may be Belkin, but a cannot remember for sure. Also, if you are trying to connect to wireless N at 5GHz, try wireless G instead. I believe the Atrix will not connect at 5GHz, and the symptoms of trying to do so are exactly what you describe. If I try to connect to my router on the 5GHz wireless N band I get the same results as you. One other possibility is the password length. I have read that you should keep it under 8 characters with the Atrix, so maybe try shortening the password, or try connecting unsecured to test this theory out. I am using an Asus RT-N66U right now, but have previously used 2 Netgear routers without issue also. My work uses Cisco repeaters and routers and I have no issues there either.
CaelanT said:
There have been several reports over the months of people having trouble connecting to one manufacturers routers..........may be Belkin, but a cannot remember for sure. Also, if you are trying to connect to wireless N at 5GHz, try wireless G instead. I believe the Atrix will not connect at 5GHz, and the symptoms of trying to do so are exactly what you describe. If I try to connect to my router on the 5GHz wireless N band I get the same results as you. One other possibility is the password length. I have read that you should keep it under 8 characters with the Atrix, so maybe try shortening the password, or try connecting unsecured to test this theory out. I am using an Asus RT-N66U right now, but have previously used 2 Netgear routers without issue also. My work uses Cisco repeaters and routers and I have no issues there either.
Click to expand...
Click to collapse
I cannot connect to any network, 2.4 5 ghz.... secured or not secured, it finds networks, but i cannot connect to them.
CaelanT said:
Also, if you are trying to connect to wireless N at 5GHz, try wireless G instead. I believe the Atrix will not connect at 5GHz, and the symptoms of trying to do so are exactly what you describe. If I try to connect to my router on the 5GHz wireless N band I get the same results as you.
Click to expand...
Click to collapse
Just a heads up, but I can connect to my 5Ghz WiFi at home just fine. What kind of encryption are you using?
Inspiredwire said:
Just a heads up, but I can connect to my 5Ghz WiFi at home just fine. What kind of encryption are you using?
Click to expand...
Click to collapse
it has no matter with encription, i cannot connect at home, cannot connect at the city, cannot connect anywhere. its just showing up the network i try to connect it says saved and nothing happens, later the phone just turn off, i have to pull the battery to turn it on again,
logcat says this when i turn on the wifi:
E/Wifistatemachine (1553): Unable to change interface settings: java.lang.illegalstateexeption: Unable to communicate with native daemon to interface setcfg - com. android.server.NativeDaemonConnectorExeption: Cmd interface setcfg eth0 0.0.0.0 0 down broadcast running multicast failed with code 501: Flag unsupported
EWifiConfigStore (1552) : Missing id while pharsing configuration
Just installed CM7 nightly, everything works fine for now
Related
Hello
I have Router linksys with web2 password.
when i turn on Wi-Fi only appair on the screen (open network) which not secure near to me but my secure network is not shown, if i remove web2 pass. i can see again my network.
what is the problem?
abody1111 said:
I have Router linksys with web2 password.
Click to expand...
Click to collapse
Hmm are you typing with auto-correction on?
If you mean WPA2-PSK (WPA2 with password), then I can confirm that this works.
I have a similar issue with my 'O2' router (rebranded Thompson 585 V7) and have WPA+WPA2 (WPA-PSK Encryption) setup.
All devices in my home (laptops & Ipod Touch's) have no problems, but my new Hero continually fails to get an IP address. Seems to connect OK but then continualy cycles therough 'Obtaining address'... 'failed'.... 'Obtaining address'!
It did successfully connect once for about 20 mins, but after a phone off/on, has gone back to failing.
I'll experiment further, but may have to return the device
Regards,
Glenn
Volker1 said:
Hmm are you typing with auto-correction on?
If you mean WPA2-PSK (WPA2 with password), then I can confirm that this works.
Click to expand...
Click to collapse
sorry you are right
plz solve my prob. if you can
abody1111 said:
sorry you are right
plz solve my prob. if you can
Click to expand...
Click to collapse
I'm still waiting for my hero, so I might be wrong. But according to the manual, the hero can only handle WEP encryption on WiFi. WPA/WPA2 are not supported. I think, for the hero to work on WiFi, you must change the encryption on your router either to WEP or to unsecure.
gh01 said:
I'm still waiting for my hero, so I might be wrong.
Click to expand...
Click to collapse
I tried WPA-PSK and WPA2-PSK with my Hero and they definitely work. Sorry, mate ;-)
If the OP wants some help he needs to post some useful data about his setup and what works and what does not work.
I can confirm it works for wpa2-psk and PEAPv0/EAP-MSCHAPv2
Wi-FI is not working with secure network
Hi
I had same problem with BT Home Hub2 all i did was a soft rest and it worked and had no more problems so try soft resetting you routor
Well, as posted earlier, despite several hours of every possible combination of settings and factory resets, I can't get my Hero to use my WiFi (WPA+WPA2, WPA-PSK Encryption).
I have seven other devices that have no problems at all (I configured them all), so I'm assuming it's an issue with the Hero. Therefore, it's going back to it's supplier.
Regards,
Glenn
knnelg said:
Well, as posted earlier, despite several hours of every possible combination of settings and factory resets, I can't get my Hero to use my WiFi (WPA+WPA2, WPA-PSK Encryption).
I have seven other devices that have no problems at all (I configured them all), so I'm assuming it's an issue with the Hero. Therefore, it's going back to it's supplier.
Regards,
Glenn
Click to expand...
Click to collapse
Yep it may well be a faulty one if its from a store try get them to test it if they can if not the get the new one home and try again you might also wont to try it on someone else wifi see if it works on theres. Also it might be that the amount of device conected to it may be causing a problem on first time setup, you could try it on its own then let other device connect to route worth a try
You should bear in mind that sometimes certain devices just don't get on. Someone posted here earlier with a similar issue, and they found changing their router from the Orange supplied box to another one "fixed" their issue.
Regards,
Dave
I found problems connecting my Hero to our Belkin N1 Vision ADSL Modem/Router using WPA2-Personal.
In the end it turned out that re-enabling the option to broadcast the SSID solved the problem. For some reason creating a connection manually to a network which does not brodcast caused the issue for me.
Regards,
Ian
ianm said:
In the end it turned out that re-enabling the option to broadcast the SSID solved the problem.
Click to expand...
Click to collapse
So there is a generic advice, run your wifi in a standard-compliant mode. Broadcast SSID and turn off all the vendor-specific "turbo mode" and "extra-long/short" packets crap.
Problem with wpa2 enterprise
I am not able to connect to wifi at work.
We use wpa2-enterprise with PEAPv0/EAP-MSCHAPv2 and broadcast SSID.
Hero detects wifi network with incorrect security. It displays: "(network SSID) secured with WEP". When I tap on it it asks for WEP hex key...
I tried to add wpa2-enterprise network manually. It says "not in the range" and keeps offering me the above one with wrong security...
any ideas?
wifi works fine on other phones
Ok, I have read every single thread (to my knowledge) about the Wifi Connect Issue. I have tried all the manual tricks (changing router settings / channels / changed SSID / passwords / Security / reset router to factory / airplane mode / factory reset on GTab, etc) and STILL can NOT connect my GTab to home router.
I CAN connect it to my Galaxy S Vibrant Mobile AP Wireless, I can also connect every other device to my Router without issue. (Vibrant / Nook Color / Archos 70 IT / Wireless Printer, etc)
I'd be happy to toss a donation tip to whoever can help me with this...it's truly EFFIN frustrating. I can get speeds of 12-15MB/s on all my other devices off the router wireless connection. With the GTab I'm just stuck in a cycle of "Obtaining IP Address...Connecting...Obtaining...yadda effin yadda"
Running VEGAn-Tab 5.1
BTW - bought it earlier tonight...totally lovin this thing, beastly! Compared with my 4 other Android Devices, it's nutz! Thanks to all of your great info and ROMs!
***SOLVED 1/10...Bought New Router & working fine now!!***
What you are describing is what i get when i put in wrong password.
Allenfx said:
What you are describing is what i get when i put in wrong password.
Click to expand...
Click to collapse
I wish...heh heh. Nah, I've changed / reset SSID and Password multiple times as well. Definately not the issue. Woulda been funny tho...kinda like when you get a call in tech support, and ask "Is it plugged in?" lmao
Is your security WEP? I believe the Viewsonic only understands WPA.
Under settings>wireless and network>Wifi settings
What do you see?
ml_boston said:
Is your security WEP? I believe the Viewsonic only understands WPA.
Click to expand...
Click to collapse
Tried all variations of WPA...
WPA-PSK (TKIP)
WPA2-PSK (AES)
Allenfx said:
Under settings>wireless and network>Wifi settings
What do you see?
Click to expand...
Click to collapse
The usual stuff...Wi-Fi toggle / Network Notification toggle / Add wifi network
Once toggled on...several networks show up...including my Router Connection
So network and and gtab wireless are working.
Has to be a setting somewhere thats off.
Changed everything again...even matched the settings exactly the same as the settings on my Android Phone...no luck.
Did you change your wifi regulatory domain to 11 channels? If not, try that...
anlog said:
Did you change your wifi regulatory domain to 11 channels? If not, try that...
Click to expand...
Click to collapse
Just tried that as well...using Root Explorer, edited the build.prop/ ro.wifi.channels= to ro.wifi.channels=11
no change...still the connecting / obtaining loop
Have you tried disabling security? (Just for test purposes?)
pmcnano said:
Have you tried disabling security? (Just for test purposes?)
Click to expand...
Click to collapse
Yep...that too. Beginning to think GTab doesn't like my router. I have a Belkin N1 Router if anyone else has the same and could advise.
Try flashing pershoot's latest kernel. It has a VERY updated wifi driver.
http://forum.xda-developers.com/showthread.php?t=903505
anlog said:
Try flashing pershoot's latest kernel. It has a VERY updated wifi driver.
http://forum.xda-developers.com/showthread.php?t=903505
Click to expand...
Click to collapse
Nope...tried this too now...wtf
Prolly go grab a new router in the AM...see if that does any good.
Keep up the suggestions tho, puhleeze
Bandage said:
Nope...tried this too now...wtf
Prolly go grab a new router in the AM...see if that does any good.
Keep up the suggestions tho, puhleeze
Click to expand...
Click to collapse
Only other thing I can think of is wacked out router, or maybe some mac filtering, upnp, or other "helpful" crap on the router that is causing it to not connect. I don't own any Belkin devices. I stick to Linksys or D-Link...
Sorry, man...
Have you tried connecting to a different wireless network? (sorry if this was already suggested.) Coffee house or any other company with free wireless, maybe at your job?
Bandage said:
Yep...that too. Beginning to think GTab doesn't like my router. I have a Belkin N1 Router if anyone else has the same and could advise.
Click to expand...
Click to collapse
Connects to my girlfriends belkn n600. But thats a brand new router just installed last night. 69 at best buy
Couple of thoughts:
you may just have a defect. it happens. can't hurt to return for another one
not sure what type of router you have, but most if not all allow you to look at the event log. from there you should be able to tell why it's not being assigned an address (i.e. p/w wrong, range not avail, etc)
is your router restricting the type of access? (i.e. "b" but not "g" or "n")
didn't see in earlier posts, but have you been able to connect to any wifi networks? (i.e. public ones, or a mobile device's hotspot)
1) Is your router set to only serve out a small number of IP addresses via DHCP? Perhaps the available IPs have been used by other devices
2) I know you did a factory reset, but make sure MAC filtering is not turned on. Not sure what the Belkin defaults to but should be off unless you want to add the MACs manually to the whitelist.
3) If your SSID is showing up in the Wireless list on your GTablet, try deleting it (long press, then Forget) and then re-add it...You may have "cached" some old settings from your previous configurations...
Has anyone gotten their Tablet S to connect to WiFi via an ad hoc connection? I found this in the Market ZT-180 Adhoc Switcher but don't know if it works with our Murata WiFi module.
I did try the wpa_supplicant hack, but afterward I was only able to see ad hoc connections. Actually connecting to them failed each time.
I tried wifiAdHocEnabler from the market, same result, i can see the adhoc networks now but it keeps on obtaining IP address on Sony tab S when I try to connect
I tried it on my desire hd, it worked (connected to the adhoc) but no internet, I am still trying to figure out how to solve it
Hi,
This was already discuss here:
http://forum.xda-developers.com/showthread.php?t=1290313&highlight=ad+hoc
I was able to connect my tablet to my android phone internet
Thanks rimsilva for pointing out that post
the issue is still there, I can see the adhoc and the tab keeps trying to obtain IP address
I can use my iphone hotspot to connect my tablet to internet, simple and easy
SudaDreamS said:
Thanks rimsilva for pointing out that post
the issue is still there, I can see the adhoc and the tab keeps trying to obtain IP address
Click to expand...
Click to collapse
Have you tried busibox and wifiadhocenabler in the tablet.
I had the same issue with a specific rom in my android phone, the wifi tether was running but my laptop was always obtaining IP address.
In your phone you are using native tether or external application? Please try wireless tether or wifi tether beta (look in Google)
I am using htc P3600 WM6 (Trinity) as wifi hotspot with WMWifiRouter
I can detect it using other windows mobile 6 device and I can surf internet on other WM6 easily. This is why I guess the issue is in android (Sony S & htc Desire HD 2.3.3 Leedroid)
& yes I tried the wifiadhoc enabler and after trying it only i was able to detect the hotspot but I couldn't connect (obtaining IP)
I tried the adb method, root explorer method, Xoom files, Nook files all are giving same result (obtaining IP)
Sorry guys, I'm confused as to why it sounds so complicated.
I have no problem connecting my new unrooted tablet s to wifi using my iphone hotspot or connecting to wifi at Mcdonald, Starbuck or other government building or libraries.
I don't need any app at all.
Kermit33 said:
Sorry guys, I'm confused as to why it sounds so complicated.
I have no problem connecting my new unrooted tablet s to wifi using my iphone hotspot or connecting to wifi at Mcdonald, Starbuck or other government building or libraries.
I don't need any app at all.
Click to expand...
Click to collapse
Look that we're talking about different things, that may cause the connection problem.
My experience is with Android --> Android connection. I had no success with MIUI .35 Kernel in my Ideos, but with CM7 and now Aurora ICS works perfect.
I thought SudaDreamS was trying the same but no, he is on WM6 and maybe is limitation between both systems.
Now you are talking about iOS and routers....
SudaDreamS look at this thread:
http://forum.xda-developers.com/showthread.php?t=1192961
http://android.stackexchange.com/questions/17190/tethering-hc3-2-with-windows-mobile
PS: your tablet is rooted right?
rimsilva said:
Look that we're talking about different things, that may cause the connection problem.
My experience is with Android --> Android connection. I had no success with MIUI .35 Kernel in my Ideos, but with CM7 and now Aurora ICS works perfect.
I thought SudaDreamS was trying the same but no, he is on WM6 and maybe is limitation between both systems.
Now you are talking about iOS and routers....
SudaDreamS look at this thread:
http://forum.xda-developers.com/showthread.php?t=1192961
http://android.stackexchange.com/questions/17190/tethering-hc3-2-with-windows-mobile
PS: your tablet is rooted right?
Click to expand...
Click to collapse
My tablet is not rooted.
Thanks again rimsilva,
well both links didn't help much
I tried to use a static IP to overcome (obtaining IP address issue)
The great news is .. I was able to connect but no internet surfing on the tab yet and on the other wm6 as well, there was no surfing
anyhow, I'm still trying
hope some1 will suggest some solution or help by thinking with me
---------- Post added at 05:08 PM ---------- Previous post was at 05:05 PM ----------
Kermit33 said:
My tablet is not rooted.
Click to expand...
Click to collapse
You can't tether to ad-hoc then, anyhow you might tether to access points
I managed to connect by removing the security of the network, speed is fine, it works perfectly now, since I'll be using it on the go, I wont need the security that much + the WMWifirouter shows how many devices are connected, so it's gives partial sense of security
Thanks to rimsilva for trying to help
SudaDreamS said:
I managed to connect by removing the security of the network, speed is fine, it works perfectly now, since I'll be using it on the go, I wont need the security that much + the WMWifirouter shows how many devices are connected, so it's gives partial sense of security
Thanks to rimsilva for trying to help
Click to expand...
Click to collapse
Holy crap! I did the same thing and it worked. Can't believe I didn't try that before. I'm using Connectify-Lite on my laptop in Afghanistan and it was driving me nuts to not be able to connect my Tablet S.
hi all
i hit a wierd issue with adhoc p2p on my tablet S. my tablet is rooted and i have reference to all the available HC adhoc wpa_supplicant binary available out there..
scenario with adhoc connections setup on Win7 works fine(static IP setup). im able to ping the wifi ip of my Win7 from tablet S.
However, it failed to talk to talk to my adhoc device "OBDKey WLAN". It(tablet S) will see the adhoc ssid and connects to it(static ip setup). but it will goes into connect/disconnect loops. I ran a terminal to constantly ping my device adhoc IP but its always 'host unreachable'. Im constantly seeing errors :
I/wpa_supplicant( 2932): CTRL-EVENT-DRIVER-STATE HANGED
V/WifiMonitor( 155): Event [CTRL-EVENT-DRIVER-STATE HANGED]
ip route shows the correct network routing for network 192.168.0.0/16
netcfg shows my wlan0 is up and running with the static IP.
wpa logs that its able to connect to the adhoc ssid too.
(attached is the log of the occurance describe above.)
I did make sure its not the adhoc device faulty by testing with my HTC phoen. I was able to connect to my adhoc device using my HTC DHD (rooted with LeeDroid) and ping both ways.
Is there any kind souls who can point me to the right direction to solve this? am running out of ideas.
/etc/wifi/wpa_supplicant.conf contents:
$ cat /etc/wifi/wpa_supplicant.conf
cat /etc/wifi/wpa_supplicant.conf
update_config=1
ctrl_interface=DIR=/data/system/wpa_supplicant GROUP=wifi
eapol_version=1
ap_scan=1
fast_reauth=1
wpa_supplicant refs:
http://forum.xda-developers.com/showthread.php?t=1083182&page=2
http://forum.xda-developers.com/showthread.php?t=1069569&page=2
http://forum.xda-developers.com/showthread.php?t=1033314&page=14
http://androidtablethacks.com/android-tablet-hacks/how-to-enable-adhoc-wifi-on-android-tablets/
solved my issue with adhoc wifi keep d/c
zerod78 said:
hi all
i hit a wierd issue with adhoc p2p on my tablet S. my tablet is rooted and i have reference to all the available HC adhoc wpa_supplicant binary available out there..
scenario with adhoc connections setup on Win7 works fine(static IP setup). im able to ping the wifi ip of my Win7 from tablet S.
However, it failed to talk to talk to my adhoc device "OBDKey WLAN". It(tablet S) will see the adhoc ssid and connects to it(static ip setup). but it will goes into connect/disconnect loops. I ran a terminal to constantly ping my device adhoc IP but its always 'host unreachable'. Im constantly seeing errors :
I/wpa_supplicant( 2932): CTRL-EVENT-DRIVER-STATE HANGED
V/WifiMonitor( 155): Event [CTRL-EVENT-DRIVER-STATE HANGED]
ip route shows the correct network routing for network 192.168.0.0/16
netcfg shows my wlan0 is up and running with the static IP.
wpa logs that its able to connect to the adhoc ssid too.
(attached is the log of the occurance describe above.)
I did make sure its not the adhoc device faulty by testing with my HTC phoen. I was able to connect to my adhoc device using my HTC DHD (rooted with LeeDroid) and ping both ways.
Is there any kind souls who can point me to the right direction to solve this? am running out of ideas.
/etc/wifi/wpa_supplicant.conf contents:
$ cat /etc/wifi/wpa_supplicant.conf
cat /etc/wifi/wpa_supplicant.conf
update_config=1
ctrl_interface=DIR=/data/system/wpa_supplicant GROUP=wifi
eapol_version=1
ap_scan=1
fast_reauth=1
wpa_supplicant refs:
http://forum.xda-developers.com/showthread.php?t=1083182&page=2
http://forum.xda-developers.com/showthread.php?t=1069569&page=2
http://forum.xda-developers.com/showthread.php?t=1033314&page=14
http://androidtablethacks.com/android-tablet-hacks/how-to-enable-adhoc-wifi-on-android-tablets/
Click to expand...
Click to collapse
Ok, i have resolved my issue above. Even thou i was using a adhoc enabled wpa_supplicant, my adhoc wifi device is have constant disconnecting upon connecting and with Xoom adhoc HC built wpa_supplicant adhoc enabled, i get the above wifi errors (hung state) from wpa_supplicant.
After spending much time on it, i discover that my tablet S is doing wireless b,g,N. Looking further it seems my device only does a,b,g. Digged the whole /system for wifi related things and managed to find out some info in wmiconfig and wlan_tool.
So in wlan_tool, there is a commented line :
#WMODE="bg"
uncomment the above line will make your wifi to only communicate in b or g mode. And viola... problem solved. Connections remains strong and i do not face any d/c on my adhoc wifi connection to my device.
how to add ad hoc wifi capability to S
O.k., big newb here. I just read up on lots of threads on how to make the tablet S work with ad hoc wifi (I have a verizon thunderbolt). but, everything is way over my head.
Question, does the tablet S have to be rooted to enable it to work on ad hoc wifi?
I think all the forums and threads that I have read indicate that to be true. Obvious next question would be how...
Thanks in advance.
Yes, you have to have your tablet rooted to try any of the ad hoc solutions.
Hellomofo said:
I think all the forums and threads that I have read indicate that to be true. Obvious next question would be how...
Thanks in advance.
Click to expand...
Click to collapse
Here is where to begin...Tablet S root solution
Thanks. I'll start there.
No need to modify wpa_supplicant binary
I changed data/misc/wifi/wpa_supplicant.conf instead of wpa_supplicant.
Step1:First i scanned my adhoc network using Wifi Manager. It shows adhoc networks. I ignored it's warning and tried to connect. It'll fail.No problem! We now have the adhoc network listed in wpa_supplicant.conf.
Note: you can skip this step if you know how to edit wpa_supplicant.conf manually or if your device already lists adhoc networks on scanning.
Step2: You'll need to root your device if you're doing this through your device itself. If you use adb you may not need to root your device.(I had root access by default through adb. So rooting the device wasn't necessary for me). If you're using pc(windows or linux), i recommend Android Commander.
Pull and/or edit data/misc/wifi/wpa_supplicant.conf. Add the following line
ap_scan=2
Find line like
network={
ssid="your adhoc name"
bssid=*some value*
.
.
}
Delete bssid line.
Add/Change the following
scan_ssid=1
priority=1
mode=1
Push back/save the modified file.
chown ownership back to system.wifi. Type the following in adb
#chown system.wifi data/misc/wifi/wpa_supplicant.conf
Advantage: Safer than modifying system/etc/wifi/wpa_supplicant binary. Saves you the trouble of compiling modified wpa_supplicant or finding a compiled one for your platform.
Drawback: This is just a temporary solution.You'll have to repeat this process for every new adhoc network as it doesn't enable adhoc forever. It is good for connecting to your home network or other know networks, but if you want to connect to any adhoc network you scan,then this is not your method. Because, wpa_supplicant.conf will be overwritten every time you scan a new network.
Hello to all.
I was trying to start this thread in Android Software and Hacking General, but got a warning about not having enough posts to submit a thread there, so I'm going to try here.
I have a Samsung Galaxy S II phone with the newest Android version. My goal is to modify the system so that 3G and WiFi are able to run together, side-by-side, simultaneously without 3G being turned off. Now, every time I connect to a WLAN, 3G cuts.
[OK, the spam police won't let me post outside links; Google Mobisocial 3G Wifi Stanford to find the article I'm talking about.]
MobiSocial News wrote about a hack that modifies ConnectivityService.java in a rather crude way, but according to the author of that article, it works on a 2.x Android system. There's not much info about the hack, but it's at least something and sounds plausible.
I tried to follow the instructions; I downloaded newest Android source codes, modified ConnectivityService.java and built the kernel by following these instructions: [a link to source.android.com "Building the System"]. But unfortunately, make didn't produce a services.jar mentioned in the article.
---
Does anyone know anything about using 3G and WiFi at the same time? Is it even possible?
Every piece of information is valuable, so don't be afraid to post. Thanks!
Anyone?
If I was misunderstood in my previous post; I'm not looking to have simultaneous connections, I just want the mobile network device to be online while I'm doing something with WiFi. And when WiFi cuts off, for example in a train tunnel or something, 3G takes its place.
I want to do the same with you
Cherilee said:
Anyone?
If I was misunderstood in my previous post; I'm not looking to have simultaneous connections, I just want the mobile network device to be online while I'm doing something with WiFi. And when WiFi cuts off, for example in a train tunnel or something, 3G takes its place.
Click to expand...
Click to collapse
Hello from me. I done the same job with you! And the Service.jar was created and i pushed to my mobile phone. But still the same default use of the connectivity. You managed to do something?
No it is not possible.
"NEVER CALL YOURSELF NOOB BE A NEWBIE"
PM me if u need help
Sent from MOON......
Moonguy75 said:
No it is not possible.
"NEVER CALL YOURSELF NOOB BE A NEWBIE"
PM me if u need help
Sent from MOON......
Click to expand...
Click to collapse
And why they say that it works?
Cherilee said:
Does anyone know anything about using 3G and WiFi at the same time? Is it even possible?
Click to expand...
Click to collapse
It's possible with a rooted phone.
cboursinos said:
Hello from me. I done the same job with you! And the Service.jar was created and i pushed to my mobile phone. But still the same default use of the connectivity. You managed to do something?
Click to expand...
Click to collapse
Read here:
http://forum.xda-developers.com/showthread.php?t=2197776
Moonguy75 said:
No it is not possible.
Click to expand...
Click to collapse
Actually it is, I found this thread that describes how to do it on an optimus G phone, and based on that I was able to do in on vanilla android 4.3 as well (my rooted nexus 4).
You need to put a couple of scripts together, since you need a series of shell commands for turning this on and off, I recommend the wonderful SH Script Runner for this.
Here is what I did on my Nexus 4. It works perfectly but note that you don't actually see the wifi icon turning on, but if you run "netcfg | grep UP" you will see that the wlan0 interface is up and running (as well as the rmnet_usb0 mobile data interface, both of them will be up and will have the expected IP addresses) and you can access your local LAN while your mobile data 3g/4g whatever provides your default route to the outside world.
Code:
# enable dual-networking:
pkill dhcpcd
svc wifi disable
svc data enable
netcfg wlan0 up
cd /data/misc/wifi/.
wpa_supplicant -B -Dnl80211 -iwlan0 -c/data/misc/wifi/wpa_supplicant.conf
dhcpcd wlan0
ip route add x.x.x.x via x.x.x.y # add any desired local route
# disable dual-networking:
ip route del x.x.x.x/x via x.x.x.y
pkill dhcpcd
pkill wpa_supplicant
rm -rf /data/misc/wifi/wlan0
netcfg wlan0 down
svc wifi disable
svc data disable
Hi guys. I am trying to do the same on my Xiaomi m2. Can someone point me to the correct direction. Much much much appreciated.
Sent from my MI 2 using Tapatalk
wlh03212 said:
Hi guys. I am trying to do the same on my Xiaomi m2. Can someone point me to the correct direction. Much much much appreciated.
Click to expand...
Click to collapse
What's your Android version? Is the phone rooted? Did you try running the above commands I posted, and what was the output?
You could also try the similar commands that worked on another and post the output here.
sordna said:
What's your Android version? Is the phone rooted? Did you try running the above commands I posted, and what was the output?
You could also try the similar commands that worked on another and post the output here.
Click to expand...
Click to collapse
Hi I'm running on Miui v5 4.1.1
I did try the above commands. But I'm not sure about the ip route you mentioned in the coding x. X. X. X via y. Y. Y. Y.
The response of the script was permission denied. I am definitely rooted and I gave permission to SH script runner.
Sent from my MI 2 using Tapatalk
First try the commands on the terminal (adb shell, or terminal app) and make sure to type "su" first, so that all commands get executed with root permissions. After you get things working without errors on the terminal, you can put these commands in script runner.
The x.x.x stuff needs to be replaced with the subnet/netmask of your home LAN, such as 10.0.0.0/24 or whatever and the default gateway (your wireless router) to reach it via.The route stuff assumes a basic understanding of networking... Actually you can remove the route statements, they are only needed if your home LAN is on a different subnet than your WiFi subnet... most home routers put everything on the same subnet.
What is the end goal you are trying to achieve by connecting to 2 networks?
sordna said:
First try the commands on the terminal (adb shell, or terminal app) and make sure to type "su" first, so that all commands get executed with root permissions. After you get things working without errors on the terminal, you can put these commands in script runner.
The x.x.x stuff needs to be replaced with the subnet/netmask of your home LAN, such as 10.0.0.0/24 or whatever and the default gateway (your wireless router) to reach it via.The route stuff assumes a basic understanding of networking... Actually you can remove the route statements, they are only needed if your home LAN is on a different subnet than your WiFi subnet... most home routers put everything on the same subnet.
What is the end goal you are trying to achieve by connecting to 2 networks?
Click to expand...
Click to collapse
Thanks you for your reply. First of all my understanding of networking isn't anywhere basic . What i did with the xxx was replacing it with the internal ip assigned to me, aka 192.x.x.x
For the yyy, I replaced it with the ip of 3g connection. Not sure what I am doing here. Please guide me here (I know the su part which I an required to do in terminal)
And finally my goal. I have Seagate wireless plus and itself is a portable wifi hotspot to its own content. I am able to stream pictures music and video from the battery operated hardisk. I can bridge the connection of the portable hotspot to my home wifi gaining xs to the Internet.
However while I am connected to the Seagate wireless plus, I cannot connect to my 3g. That meaning I can't have Internet on the go which is a very big limitation.
Sent from my MI 2 using Tapatalk
Sent from my MI 2 using Tapatalk
OK. You don't need the "ip route" command, since your WiFi interface will give you access to the Seagate as soon as you connect to it. And the 3G interface, at least in my case, provided default gateway to the internet.
Anyway, try the other commands one by one and see which of them, if any, give you any errors. The netcfg command should show you that 2 interfaces (apart from the lo - 127.0.0.1) are UP and with expected IP addresses if everything goes well.
sordna said:
OK. You don't need the "ip route" command, since your WiFi interface will give you access to the Seagate as soon as you connect to it. And the 3G interface, at least in my case, provided default gateway to the internet.
Anyway, try the other commands one by one and see which of them, if any, give you any errors. The netcfg command should show you that 2 interfaces (apart from the lo - 127.0.0.1) are UP and with expected IP addresses if everything goes well.
Click to expand...
Click to collapse
# enable dual-networking:
............
............
.............
..........
...........
..............
..........
ip route add x.x.x.x via x.x.x.y # add any desired local route -------->( do i remove this row of code entirely? What do i do with this row of coding? Provide my default gateway? I'm not sure what's my default gateway or how i do find out my default gateway or how should i edit this coding to my default gateway.)
Anyway, try the other commands one by one and see which of them, if any, give you any errors. The netcfg command should show you that 2 interfaces (apart from the lo - 127.0.0.1) are UP and with expected IP addresses if everything goes well (In short if the i execute the above commands correctly with the correct default gateway of my 3G, the netcfg command should show my default gateway correctly? is my understanding correct?)
As I said before, you don't need the ip route command, remove that line entirely!
When all is working, netcfg | grep UP should show you your wlan interface with the IP address given to it by the Seagate, and your mobile data interface with the IP address given to it by your cellular provider.
sordna said:
As I said before, you don't need the ip route command, remove that line entirely!
When all is working, netcfg | grep UP should show you your wlan interface with the IP address given to it by the Seagate, and your mobile data interface with the IP address given to it by your cellular provider.
Click to expand...
Click to collapse
Thanks you much! Going to try out when I get home.
Sent from my MI 2 using Tapatalk
OK. Please hit the thanks buttons
sordna said:
OK. Please hit the thanks buttons
Click to expand...
Click to collapse
When i run the code line by line in terminal, i get an error message wlan0: interface not found or invalid
Do I run the code when connected to my hardisk hotspot? When exactly do I run the code.
wlh03212 said:
When i run the code line by line in terminal, i get an error message wlan0: interface not found or invalid
Do I run the code when connected to my hardisk hotspot? When exactly do I run the code.
Click to expand...
Click to collapse
If you try to understand the code you will notice it turns off your Wi-Fi and then turns it on. So actually you don't need to connect to the hotspot first.
Regarding the interface name, here is where you need to do your own investigation and figure the WiFi interface name for your own phone.
The netcfg command without any arguments displays all interfaces, and whenever you are on Wi-Fi, the relevant interface will be UP and will have your assigned IP address next to it.
Look at how much stuff I changed compared to the things posted by the other guy for the optimus phone. Look at his solution and be prepared to investigate and come up with similar amount of changes for your phone. I spent several hours trying different stuff for my Nexus 4, with my only info being the other guy's post. I read about netcfg and everything else googling various websites. You need to do the same and learn a bit about that stuff.
For all I know, the Optimus phone method could be closer to your phone than my method, perhaps. You have to do your own research and figure out the differences, then post them here to help other owners with the same device as yours.
sordna said:
If you try to understand the code you will notice it turns off your Wi-Fi and then turns it on. So actually you don't need to connect to the hotspot first.
Regarding the interface name, here is where you need to do your own investigation and figure the WiFi interface name for your own phone.
The netcfg command without any arguments displays all interfaces, and whenever you are on Wi-Fi, the relevant interface will be UP and will have your assigned IP address next to it.
Look at how much stuff I changed compared to the things posted by the other guy for the optimus phone. Look at his solution and be prepared to investigate and come up with similar amount of changes for your phone. I spent several hours trying different stuff for my Nexus 4, with my only info being the other guy's post. I read about netcfg and everything else googling various websites. You need to do the same and learn a bit about that stuff.
For all I know, the Optimus phone method could be closer to your phone than my method, perhaps. You have to do your own research and figure out the differences, then post them here to help other owners with the same device as yours.
Click to expand...
Click to collapse
Yes. I notice that the wifi switched off and then turns on again. Alright I do some research on my own! Thanks again.
Hope that I will get some breakthrough soon
Sent from my MI 2 using Tapatalk
Hi
I finally got it working. When I am connected to seagate wireless, I have to fiddle with the connection settings inside wifi settings. I assigned a static ip and assigned the gateway to 0.0.0.0
As for the ip, I set a different internal ip with the last digit increased by one. Example 172.25.0.2
Now I am connected to both 3G and LAN.
Sent from my iPhone using Tapatalk
Got a free n200 through tmobile to use as a hotspot device for my pc. I was previously getting the job done by using a galaxy note 3 and setting my pc's ttl to 65 but apparently that doesn't work with the newer phones.
I did some searching online and haven't been able to get a definitive solution to bypassing the hotspot throttle, as people seem to have varying results.
Had a lot of issues with PDAnet+, so it's definitely not a long-term solution for me.
Just sent an unlock request to OnePlus, hopefully by next week I'll get the unlock file and I'll root the phone. I'm assuming that rooting the phone will expand my options for what I want to do. Anyone have a solution that worked for them?
Yo, it's like dns hijacking, in fact, this is what you have to do to bypass this.
I'll paint a scenario, see what you make of it...
I plug my sim into a wifi router, in the control panel of this router, I set the wifi to use the 2nd ip, (yes, all isp's actually give you 2 ip's, one that is public, one the isp use's to spy on you, and the one you see in your ethernet card, usually 192.168.1.1.
Your wifi router runs adb, so it is on a different network, being 192.168.0.1, if you set your connecting device to your public ip shown by the router, and nxbogus domain your isp's private number seen in the router, (usually 100.whatever) and their dns, then set your prefered dns in the connecting device, you will bypass the throttling, but you will notice something else...
They throttle you by lowering your phones coverage lol...
Notice in your wifi setup pages your signal will drop from say 75% to 25%, and if you check the config logs, you'll see your limited 90% by the isp..
Yup, I'm isp level in this department..
didn't understand half of what you said. can you break it down a lil bit more?
l0csta said:
Got a free n200 through tmobile to use as a hotspot device for my pc. I was previously getting the job done by using a galaxy note 3 and setting my pc's ttl to 65 but apparently that doesn't work with the newer phones.
I did some searching online and haven't been able to get a definitive solution to bypassing the hotspot throttle, as people seem to have varying results.
Had a lot of issues with PDAnet+, so it's definitely not a long-term solution for me.
Just sent an unlock request to OnePlus, hopefully by next week I'll get the unlock file and I'll root the phone. I'm assuming that rooting the phone will expand my options for what I want to do. Anyone have a solution that worked for them?
Click to expand...
Click to collapse
you could always use this classic app been around for yrs its called pdanet/Foxfi........ http://foxfi.com/
PopCaps1996 said:
you could always use this classic app been around for yrs its called pdanet/Foxfi........ http://foxfi.com/
Click to expand...
Click to collapse
yea i'm using easytether rn, very similar to foxfi and pdanet+... not a permanent solution however, as it tends to randomly disconnect and i often get kicked out of games due to "network lag". Speeds are exponentially faster than the throttled hotspot, however, so i wont complain.
still, would be nice if there was a solution to this for the native hotspot/tether features... tried everything with apns and changing the ttl on the phone but it didn't work.
looks like someone found a solution for the moto g 5g here, maybe i'll try to implement this for the n200, could be a possible workaround.
l0csta said:
yea i'm using easytether rn, very similar to foxfi and pdanet+... not a permanent solution however, as it tends to randomly disconnect and i often get kicked out of games due to "network lag". Speeds are exponentially faster than the throttled hotspot, however, so i wont complain.
still, would be nice if there was a solution to this for the native hotspot/tether features... tried everything with apns and changing the ttl on the phone but it didn't work.
looks like someone found a solution for the moto g 5g here, maybe i'll try to implement this for the n200, could be a possible workaround.
Click to expand...
Click to collapse
moto g solution you posted requires a special kernel. usb tethering through PDAnet+ paid version works fine, the key is you dont enable it thru the native tethering, instead enable USB tethering through the PDAnet app and leave the phone on charging mode so it can make a ADB connection. Make sure ADB is working and you can establish a working adb connection from PC to phone first prior to attempting to tether since it will use ADB. i get full speeds tethering using the paid version.
AiM2LeaRn said:
moto g solution you posted requires a special kernel. usb tethering through PDAnet+ paid version works fine, the key is you dont enable it thru the native tethering, instead enable USB tethering through the PDAnet app and leave the phone on charging mode so it can make a ADB connection. Make sure ADB is working and you can establish a working adb connection from PC to phone first prior to attempting to tether since it will use ADB. i get full speeds tethering using the paid version.
Click to expand...
Click to collapse
yeah i've been doing this via easy tether, gets the job done for the most part
For me, PDAnet has low throughput while EasyTether runs full speed and can be used with OpenWRT. They both disconnect randomly though.
No reason to deal with that if you have root. AdGuard+VPNHotspot+noprovisioning is easy to setup and works fine for most networks.
l0csta said:
didn't understand half of what you said. can you break it down a lil bit more?
Click to expand...
Click to collapse
Only connection is WAN to WAN!
Ok, first, I use an lte wifi router, enter gui, goto lan, change router login ip to any ip not 192.168.1.1 or 192.168.0.1, the latter is hidden in router, but when trying to connect 2nd router, using this ip, problems appear, because the 1st router has adb enabled due to the lte section of 1st router being android 6, and uses's it.
So in effect, I set 1st routers address to 192.168.1.5, 255.255.254.0, 192.168.1.3 ie, this is 1st router login address. In the 2nd router I set mac address of 1st router to use 192.168.1.3, having been set in the 1st.
I do this because if I set 2nd router to match 1st routers address, the 2nd router auto changes address, when plugged in to first, and the 1st router changes too.
So now that you can goto 192.168.1.1 in 2nd router with 1st plugged in, try 192.168.1.3.
First part over, now the tricky part...
Disconnect 2nd router (this Will become your MAIN router)
Start 1st router with sim in, only to obtain public ip, because you need to set this ip in WAN of 2nd router. If your ip changes every reboot, you need to check public ip from first router match's what you set the wan ip to in 2nd router.
Now when you are in 1st router's network/lan settings, look for option to use 2nd ip. enable it, in the ip box put your public ip, ie your internet ip, and remove all access to anything else, including disabling wifi, both 2.5 and 5g.
So now plug in 2nd router WAN to first routers WAN.
Go into 2nd router, and block the PRIVATE ip seen in 1st router, the ip the isp shows you, and NX=bogusdomain your isp's private dns
In your WAN page of 2nd router, set preferred dns.
Voila.
70-80% increase in response.
The hardware method to block dns hijacking
Ps any reboot of the first router will change its ip due to being lte, so remember to check 2nd router match's after any power outage...