Related
I've try the wifi tether for root user. But it seems not work on infrastructure mode. How can I tether in infrastructure mode instead of ad-hoc mode?
The same in MIUI
The same problem in MIUI.
Just ad-hoc. In Eclair and Froyo the infrastucture was possible with "thether for root users".
That isn't the same on MIUI. Just ad-hoc, even with the same software.
Any suggestion?
My Defy running uk stock 2.2 generates a hotspot in infrastructure mode and it works well with my Asus Transformer.
I have seen comments in the CM7 thread that suggest that to generate a tether spot you need to install wireless tether for root - I think others have mentioned that this is only adhoc.
Obviously I am not running CM7 so can't confirm this for you.
Have a look at the main CM7 thread.
Infact the "wifi tether for root" worked in infrastructure in Eclair and in Froyo, but just in ad-hoc in MIUI and CM.
I really can not figure why ...
i posted this in CM7 thread, just to answer your question, im pasting it here:
found it!
thanks to a thread at modaco, just copy hostapd file from /system/bin of any Defy froyo rom, and paste it in CM7 /system/bin , chmod 755, run wifi tether for root, it will now have WPA/WPA2 not only WEP, and also run as infrastructure mode!
file is attached for those who want the solution quick and dont have froyo at hand.
What's the exact name of the wifi tether app you guys are using? I couldn't find one named "wifi tether for root users" in the market. I found this one googling around though: http://code.google.com/p/android-wifi-tether/. Is this the one?
Thanks
twa_priv said:
What's the exact name of the wifi tether app you guys are using? I couldn't find one named "wifi tether for root users" in the market. I found this one googling around though: http://code.google.com/p/android-wifi-tether/. Is this the one?
Thanks
Click to expand...
Click to collapse
yes it is.
Hello! I used to use Wireless Tether(the released version, not the beta one) and it worked fine on my default eclair. now that i have CM7 RC0, i have some problem, but ONLY if i activate access control.
Tried the version above, the beta one, and i couldn't even be able to find the network(and don't have the hide SSID option to be enabled )
any idea of what could it be?
soueumesmoaki said:
Hello! I used to use Wireless Tether(the released version, not the beta one) and it worked fine on my default eclair. now that i have CM7 RC0, i have some problem, but ONLY if i activate access control.
Tried the version above, the beta one, and i couldn't even be able to find the network(and don't have the hide SSID option to be enabled )
any idea of what could it be?
Click to expand...
Click to collapse
try version 2.07:
http://code.google.com/p/android-wi...etail?name=wireless_tether_2_0_7.apk&can=2&q=
Hey guys... i'm sorry for what i'll say now.. but i'm not a developer =(
BUT, i can find some solutions on the web. (=
well.. here is the deal... As i said before, i used to use Wireless tether(what seems to be the non-beta version of this wifi tether, as the interface is pretty much the same)
after upgrading my cellphone to Gingerbread CM7 RC0, i tested it today and got a problem on activating access control...
Well.. i guess that i found some possible solution for this:
Why does the "access-control"-feature not work or is disabled.
If the feature "CONFIG_NETFILTER_XT_MATCH_MAC" is missing the "access control"-feature will not work correctly (you will see a "failed"-status in "Show log" for "Enabling access control"). To detect if all kernel-option were enabled in your current kernel the following kernel-options should be enabled: CONFIG_PROC_FS, CONFIG_IKCONFIG, and CONFIG_IKCONFIG_PRO. This dumps the current kernel-config to /proc/config.gz.
Click to expand...
Click to collapse
the ONLY problem, is that i have no idea on how to do what is written above
could anyone help?
nolimitzz said:
try version 2.07:
http://code.google.com/p/android-wi...etail?name=wireless_tether_2_0_7.apk&can=2&q=
Click to expand...
Click to collapse
Heya. thanks for answering, but I just checked. the version i'm using and having problem, is the 2.0.7.
when i tried the beta, couldn't even broadcast the SSID, so got back to the "market" version
nolimitzz said:
i posted this in CM7 thread, just to answer your question, im pasting it here:
found it!
thanks to a thread at modaco, just copy hostapd file from /system/bin of any Defy froyo rom, and paste it in CM7 /system/bin , chmod 755, run wifi tether for root, it will now have WPA/WPA2 not only WEP, and also run as infrastructure mode!
file is attached for those who want the solution quick and dont have froyo at hand.
Click to expand...
Click to collapse
hay mate, how do you copy to the sys dir?
bit of a novice
You have to use some application capable of remounting the /system partition as read/write (it is read-only by default) and copy the file, and you need a way to edit permissions.
I've used root explorer to do both things above. Remember the file has to be named hostapd (all in small caps). It works for me -- now I have infrastructure tether in my CM7 defy.
I'm not having any luck with MIUI 1.10.8 with Hostapd & android-wifi-tether unfortunately.
Tether starts with an error in the log in 2.0.7, "Starting hostapd... failed" & "Activating WiFi interface... failed" but I can't see further details than this.
Tether starts without error in 3.1-beta6 but SSID does not come up.
Permissions of Hostapd (with uppercase H) are "rwx rwx rwx", using ES File Explorer, and have rebooted between attempts.
After an hour or so of searching for the right file, I want to share with A100 owners how to enable ad-hoc support for their ICS-running tablets. All the work was done by other users on this forum, but I just want to compile the right links and method here.
1) Root your device. Follow the instructions on http://forum.xda-developers.com/showthread.php?t=1531646 and you should be set.
2) Remount /system as rw. In a root terminal,
Code:
$ su
# mount -o remount,rw /dev/block/mmcblk0p3 /system
For the next few steps, I recommend using a file manager.
3) Navigate to /system/bin and backup your original wpa_supplicant file.
4) Copy the wpa_supplicant from http://forum.xda-developers.com/showpost.php?p=25356357&postcount=136 to /system/bin.
5) Change the permissions of your new wpa_supplicant file to match the old one. It should be -rwxr-xr-x.
And you're done! Ad-hoc networks are now prefixed with a (*) symbol. Tether your tablet to your phone and free your ICS from hotspots!
It's does not work on my phone.
My phone is Galaxy note ICS.
bunkhun said:
It's does not work on my phone.
My phone is Galaxy note ICS.
Click to expand...
Click to collapse
The right wpa_supplicant varies by device, which is why it took so much trial-and-error for me to find the right one. This one I can confirm to work on Acer A100 running ICS. You'll have to look for a wpa_supplicant that works on the Galaxy Note. Look around on the forums and experiment with wpa_supplicants and you might get lucky (just don't forget to backup your existing one)
Sent from my A100 using XDA
I guess I'm not sure what this ad-hoc really does. I can tether my phone's 3G network as a hotspot. My A100 running Flexreaper ROM can connect to it and browse the internet just fine without modifying the wpa_supplicant. Maybe civato already included the modified wpa_supplicant in the ROM?
That's probably right; the Flexreaper ROM probably has an ad-hoc compatible wpa_supplicant. I'm pretty sure Cyanogenmod has, too. Ad-hoc allows a wireless device to connect to another peer-to-peer style (i.e., without a router). Cell phones that broadcast hotspots are ad-hoc networks. For some reason the stock Android OS does not allow connecting to ad-hoc networks, so a modified wpa_supplicant must be used.
Sent from my A100 using XDA
I copied the file over. I used root explorer for everything. I will check it momentarily.
---------- Post added at 12:58 PM ---------- Previous post was at 12:53 PM ----------
Are you tethering using Bluetooth or are you using a cable? If you are using a cable, what kind of cable. I have looked for a micro usb to micro usb cable but cannot find one. Please advise.
---------- Post added at 01:33 PM ---------- Previous post was at 12:58 PM ----------
Okay, it's working perfectly over Bluetooth. My speed to New Orleans was 1.9mbps down and .9 mbps up. Not bad at all on 3g, Bluetooth. I am very pleased. Now if I could SMS my son. He does not care for google chat or google plus, but he has unlimited texting. I don't because I don't text much.
Thanks for compiling this for us.
Thanks!
Thank you! That was really quick and painless! I now can connect my A100 to my Nokia E72 using Joikuspot!!
Initially, I followed the instructions but I could not mount RW even after successful rooting - not sure why. If you have the same problem, you can try the following:
1. Turn off your Wifi before proceeding
2. Save the modified wpa_supplicant provided in the given link to your PC - e.g. the desktop (you'll need to unzip it)
3. Connect your A100 to the PC via the USB cable.
4. Copy the wpa_supplicant file to anywhere in your A100 (temporarily) using your PC's usual file manager.
5. Use a good file explorer on your A100 (I used Root Explorer - very powerful! But must purchase from Googleplay - $5 Singapore dollars only) to get into the file directories of your A100 and find the modified wpa_supplicant file. Long touch the file until the menu appears and choose 'cut' from the menu.
6. Use Root Explorer to set "mount R/W" which is a convenient button near the top left of the screen
7. Now navigate to the /system/bin folder and find the original wpa_supplicant file - long touch it until the menu appears. Rename it to something like 'wpa_supplicant_original' or whatever you like.
8. Paste the new wpa_supplicant file
9. Exit and go back to settings to turn on the Wifi
10. You should be able to see a (*) next to E72-Joikuspot_XXXXXXX (assuming your phone is on and Joikuspot is on). Now just connect the usual way and now you have adhoc access!
CombatCube said:
And you're done! Ad-hoc networks are now prefixed with a (*) symbol. Tether your tablet to your phone and free your ICS from hotspots!
Click to expand...
Click to collapse
I have the Archos Arnova 7 G3. All AdHoc Networks are prefixed with (*) but I cannot connect. Does anyone have a wpa_supplicant that will work with the Archos Arnova 7 G3?
childoftheworld said:
I have the Archos Arnova 7 G3. All AdHoc Networks are prefixed with (*) but I cannot connect. Does anyone have a wpa_supplicant that will work with the Archos Arnova 7 G3?
Click to expand...
Click to collapse
Way wrong forum for that device, but, post yours up, and see what we can come up with, never know.
pio_masaki said:
Way wrong forum for that device, but, post yours up, and see what we can come up with, never know.
Click to expand...
Click to collapse
Which forum should I be posting this in?
childoftheworld said:
Which forum should I be posting this in?
Click to expand...
Click to collapse
Either your device specific forum, if there is one, or if not there's a forum for devices without their own forum. Some things are universal to a point and others aren't, so if something here doesn't work it'll likely need something based on your device or one with similar hardware.
Tapatalked from my Galaxy S II.
i've searched and searched so if i missed it please point me in the right direction. i would love it if you did.
it seems t-mobile has removed the ability to tether via bluetooth which is really the only tethering i need.
from what i can see using the images below, they use their own software to take things over.
if at all possible any of the following should work in theory:
kill their app
enable something somewhere
install another workaround app (least favorite option)
i would like to avoid going to an aftermarket rom if at all possible since this is really my only issue and i'm so over tinkering (no offense).
Attached shows t-mobiles tether options and the rest of the worlds tether options.
THANK YOU FOR ANY HELP!!!
so in regards to number 3 "install another workaround app (least favorite option)", it seems that FoxFi and CobaltBlue3 work for windows and other devices. I was not able to get it to work on Linux Mint or inside a the car.
i really hate t-mobile right now for doing this. why are they attacking me personally like this?
we need option 1 or 2. 3 sucks.
figured out option number 1 and it was terrible for someone that is tired of tinkering. is there a good way to do this without these steps? if not we need to make one.
the following steps were taken:
root and cwm
cwm backup
remove system/app/TetheringProvision.apk
copy res-framewrok.apk to ext_sdcard
decompile using apk-manager
*edit xml (http://forum.xda-developers.com/showthread.php?t=2057344)
compile
create framework-install.zip (http://forum.xda-developers.com/showthread.php?t=1840098)
install with cwm
reboot
*only sections: How to Enable Native Tethering steps 1 and 2 and How to Enable Bluetooth Tethering step 1
So, here it goes.
My goal is to connect to a network using certain MAC address. Wanted network is marked with "open" and I know that it allows access only to certain devices (according to MAC) on which the administrator have gave a permission to. Once your MAC passes the verification, device gets connected to the network and then I'm asked to enter username and password through WEB browser (well known for me, because it is a procedure that I do on my other device, as well as all my colleagues do).
For example, I was allowed to provide one personal MAC address to administrator to connect to this network. I would like to set the MAC address of my other personal device and set it on my I9195 so that I can access the same network.
So, what have I done so far: I9195 is rooted, it has Android 4.2.2 on it and Busybox installed. I have changed MAC on it using following apps: MacChanger (blue WIFI logo), MAC Address Ghost (green ghost logo), using Android Terminal Emulator commands and via MAC Spoofer (black circle with green text logo). What can I conclude: As soon as superuser has granted the access to these apps, all of them manage to change the MAC. I've done the verification using Terminal Emulator. I also have to add that the MAC remains original if viewed from WIFI advanced menu BUT this shouldn't be an issue because:
1.) Colleague of mine is using his S4 (rooted etc.), while using MAC Address Ghost that does not change the original address (viewed from WIFI advanced menu) but he manages to make a spoof (verified from the Android Terminal Emulator, as all of this apps actually do) and he manages to connect without any problems in the same way as I connect with another device that I have!
2.) I had time to make a small test at home which put a light on the idea that the problem should be focused on the Samsung (and not on the router, especially because I am unable to modify anything on the router on this facility, not even restarting it). My home network works in a similar way as the network that we are discussing about. My S4 Mini has been included in it with his original MAC and it connects to the network without any problems. My other device is also included to the network using its MAC (the one that I am using for spoofing). My other device is turned OFF, router has been reset and I am normally accessing the network with S4 Mini. Then I run the MAC Address Ghost to spoof the MAC on my S4 Mini. In that moment, I have lost the connection that I had which means that the MAC spoofer actually did something. I tried to reconnect to the network but then I am asked to enter the password for my network. I have checked and re-checked it many times, tried to forget the network and doing it all over again but it does not accept the CORRECT password. Changing my MAC back to the original one connects S4 Mini back to the network, while accepting the password immediately.
Problem is represented in a way that it either says “saved” and does not connect to the network or every few times displays a message “Authentication error occurred”.
I have tried I would say every possibility that I’ve seen over the internet. That includes:
1.) Installing WiFi Connection Manager (it provided some info regarding the network that I wish to connect to: IEEE 802.11g standard, 54 Mb link and CH:11). I’ve used its function to fix the WIFI (advanced fix (root required)) but it didn’t help.
2.) All sorts of staying close to the rooter, while enabling and disabling the Power save mode (accessed via *#0011# command) or while having GSM signal.
3.) Browsing through system, data etc. folders to try to find the file that contains the MAC address information (like it did on older android versions in the nvram file). I’ve been unable to find this file or any sort of file that displays my MAC for the purpose to modify it.
I have a plan to upgrade Android to version 4.4.2 later today and make a test.
Please, feel free to suggest anything else! If I do not succeed, I will have to replace my S4 Mini with something else.
Kind regards,
QUICK REPLY: After installing CyanoGEN MOD 4.4.2, the problem remains!
I think there could be a shorter solution! On Sony Xperia Acro S with 4.1.2 Android it was just a matter of changing the MAC address within the file data/etc/wifi/fw! One minute modification...
So, please, if somebody knows the path to the file that contains MAC on CyanoGEN MOD 4.4.2 or on Android 4.2.2, PLEASE HELP!
Kind regards!
Hello,
I am running Resurrection Remix v5.0.5-20140309 on my Note 2, upgraded from v5.0.2-20140212.
And since then, it doesn't connect to some WiFi networks like my home WiFi. When I activate WiFi, no automatic connection and when trigerring a manual connection from the WiFi menu, it directly to disabled state and doesn't even try to connect (it seems).
Hoewever, it connects normally to my work WiFi.
Note that my home wifi runs on 2,4GHz, my work wifi on both 2,4 and 5GHz.
Any thoughts ?
Thanks.
.ant1
Go to the /data/misc/wifi/ way with a root file manager and open this text file name as wpa_supplicant.conf . Find your home wifi. Look the text "autojoin=" is 0 or 1. If it 0, change to 1.
Try it, maybe work.
OguzhanVarsak said:
Go to the /data/misc/wifi/ way with a root file manager and open this text file name as wpa_supplicant.conf . Find your home wifi. Look the text "autojoin=" is 0 or 1. If it 0, change to 1.
Try it, maybe work.
Click to expand...
Click to collapse
No mention of autojoin in my wpa_applicant.conf file.
However, I don't know how, it happens that when I was editing the file, my device shows the WiFi icon on the header. But it disappeared right after and back to the same situation.
.ant1
ant1fr said:
No mention of autojoin in my wpa_applicant.conf file.
However, I don't know how, it happens that when I was editing the file, my device shows the WiFi icon on the header. But it disappeared right after and back to the same situation.
.ant1
Click to expand...
Click to collapse
If delete this file dont worry. Reboot your phone, device is make a file
OguzhanVarsak said:
If delete this file dont worry. Reboot your phone, device is make a file
Click to expand...
Click to collapse
Actually it recreates the file from itself without the need of rebooting the phone. And the new file has all my previous known WiFi networks connection details.
But it still doesn't fix anything.
.ant1