Related
Hello,
Is it possible for a rooted GEN8 device to connect to an AD HOC wireless network?
If yes, has anyone managed doing it?
Thanks
Root could open the door for trying the WPA Supplicant fix that is floating around. That fix involves editing a couple of files. Will it work?...I'm not sure.
Also, depending on the phone, you can use the 3G hotspot hack to connect you Archos. That's how I have my 101 tethered to my X.
My phone is the motorola Backflip loaded with custom rom (preclair - j-r0dd 1.3.1) which enables routing (by dedault backflip cannot route). The problem is that bluetooth tethering crashes my phone so my only solution is wifi tethering ... I dont think 3G hotspot hack will work in my phone or no ?? I am not an expert so any help is valuable for me.
thanks
I found this App it installs just fine on my a32 with an nice Ahoc setup . I am rooted on my archos and I allow it .. starts just fine looks like it is runing and working .
However I need to try and get it to connect to a Adhoc network . So I will test it tonight from my laptop and my WM phone ...
I will keep you updated ...
Here is the APK .
http://code.google.com/p/desire-adhoc/downloads/detail?name=desire-adhoc-0.0.1.apk
Update The program above did not work .. However There is a working FIX posted here I just tested it using wifirouter on my vx6800 WM phone and it works great my archos gen 8 a32 connects to AD-HOC and it's fast !
Here is the post http://forum.xda-developers.com/showthread.php?t=904291
Here is a copy of the steps by mindsurfer he posted :
Get root access:
1) Install SDE
2) Get the initramfs from this post (download the kernel+init.zip and extract it): http://forum.xda-developers.com/show...44&postcount=1
3) Replace the zImage with the new overclocked kernel
4) Boot into SDE recovery menu and copy the initramfs.cpio.gz and zImage through USB cable
5) Boot into SDE developer OS
6) You should get all your apps here and have superuser right now
Suddenly no wpa_supplicant was not working on mine, so you have to change configuration file wpa_supplicant.conf to get Adhoc:
1) get Rootexplorer
2) open root explorer and find /data/misc/wifi/wpa_supplicant.conf
Here is mine (second network is my normal router):
update_config=0
ctrl_interface=tiwlan0
ap_scan=2
network={
ssid="ardrone_108549"
key_mgmt=NONE
priority=1
mode=1
}
network={
ssid="BytecekG"
psk="PASSWORD"
key_mgmt=WPA-PSK
priority=1
}
4) overwrite wpa_supplicant.conf in Archos with new content
5) change rights to wpa_supplicant.conf to RW-RW-RW-
6) delete file tiwlan.ini
7) start drone and then wifi on Archos
When you restart you should repeat step 5 and step 6 and step 7.
__________________________________________________________
Great work !!!
The way I get my A70 to tether is as follows:
Root Android phone and flash Android 2.2 rom, which has wireless hotspot feature.
Create wireless hotspot on phone.
Tether A70 to phone wirelessly.
Never had any luck with bluetooth.
WIFI tether
I use the 3g hotspot of my HTC Legend 2.2 with my A70, and it's working great. I just had to change the user agent of the A70's browser in the settings, not to be charged by Vodaphone (SFR in France) extra connection fees.
I have the patched source files for wpa_supplicant based on the Archos Froyo source code with the fix from (i can't spell it right now, I know they/he/she wrote Barnacle Tether). I just do not have the means to compile it yet. I can post these when I get home if someone wants to compile the module. Should show adhoc networks in the list with an asterisk. The Nook Color group is using this mod.
Thanks a lot for this tethering method.
Works great on a A70it, latest 2.1.2 rom, rooted with Archangel.
I managed to have a thether connection with an LG GW620 running openetna and Barnacle Wifi Tether.
FYI enabling AdHoc in tiwlan.ini didn't work for me but this method of removing the tiwlan.ini worked like a charm.
Wireless Tether for rooted phones works in infrastructure mode. All you have to do to your tablet is connect. Just another option not mentioned.
The topic is about ad-hoc networks, let's try to stick to it.
Archos' firmware specifically disables ad-hoc networking, it seems enabling it back is as simple as editing a configuration file. So you need root (to have the right to edit that file) and you need to do it at every boot since the filesystem is read only.
At least that's what I've understood by looking on those threads.
Im trying write sh script to switch wpa_supplicant.conf files and turning wi-fi on/off.
How can i manualy with root right stop and start wi-fi?
example sh script for activate adhoc
Code:
#ifconfig wlan down ??
cp /data/misc/wifi/wpa_supplicant.conf /sdcard/wpa_supplicant.backup
cp /sdcard/wpa_supplicant_adhoc.conf /data/misc/wifi/wpa_supplicant.conf
rm /data/misc/wifi/tiwlan.ini
#ifconfig wlan up ??
do deactvate we need copy backup file back
4qu4rius said:
The topic is about ad-hoc networks, let's try to stick to it.
Click to expand...
Click to collapse
koukobin said:
My phone is the motorola Backflip loaded with custom rom (preclair - j-r0dd 1.3.1) which enables routing (by dedault backflip cannot route). The problem is that bluetooth tethering crashes my phone so my only solution is wifi tethering ... I dont think 3G hotspot hack will work in my phone or no ?? I am not an expert so any help is valuable for me.
thanks
Click to expand...
Click to collapse
I was actually trying to be helpful to the person who started this topic (which wasn't you). He did state that ANY help was valuable to him.
4qu4rius said:
It seems reading the first post of the topic is pretty often a good idea to know what the topic is about.
Click to expand...
Click to collapse
It is helpful to read ALL of the messages. As you can see from his other post, his objective is wifi tethering, and he may have been under the FALSE impression that ad-hoc networking was required for it to work.
ske714 said:
Wireless Tether for rooted phones works in infrastructure mode. All you have to do to your tablet is connect. Just another option not mentioned.
Click to expand...
Click to collapse
Only if the phone supports it. Some phones (like my Eris) do not do infrastructure, no matter which tethering app you try. Believe me, I've tried...
strongergravity said:
Only if the phone supports it. Some phones (like my Eris) do not do infrastructure, no matter which tethering app you try. Believe me, I've tried...
Click to expand...
Click to collapse
I assumed that most any phone would work in infrastructure once rooted, since that is native functionality used to connect with the phone to wireless access points. That's a bummer. Thanks for setting me straight.
In theory, at least with UrukDroid, this should be possible. I'm not home to test.
http://forum.archosfans.com/viewtopic.php?f=59&t=45943
computerfreek said:
I found this App it installs just fine on my a32 with an nice Ahoc setup . I am rooted on my archos and I allow it .. starts just fine looks like it is runing and working .
However I need to try and get it to connect to a Adhoc network . So I will test it tonight from my laptop and my WM phone ...
I will keep you updated ...
Here is the APK .
http://code.google.com/p/desire-adhoc/downloads/detail?name=desire-adhoc-0.0.1.apk
Update The program above did not work .. However There is a working FIX posted here I just tested it using wifirouter on my vx6800 WM phone and it works great my archos gen 8 a32 connects to AD-HOC and it's fast !
Here is the post http://forum.xda-developers.com/showthread.php?t=904291
Here is a copy of the steps by mindsurfer he posted :
Get root access:
1) Install SDE
2) Get the initramfs from this post (download the kernel+init.zip and extract it): http://forum.xda-developers.com/show...44&postcount=1
3) Replace the zImage with the new overclocked kernel
4) Boot into SDE recovery menu and copy the initramfs.cpio.gz and zImage through USB cable
5) Boot into SDE developer OS
6) You should get all your apps here and have superuser right now
Suddenly no wpa_supplicant was not working on mine, so you have to change configuration file wpa_supplicant.conf to get Adhoc:
1) get Rootexplorer
2) open root explorer and find /data/misc/wifi/wpa_supplicant.conf
Here is mine (second network is my normal router):
update_config=0
ctrl_interface=tiwlan0
ap_scan=2
network={
ssid="ardrone_108549"
key_mgmt=NONE
priority=1
mode=1
}
network={
ssid="BytecekG"
psk="PASSWORD"
key_mgmt=WPA-PSK
priority=1
}
4) overwrite wpa_supplicant.conf in Archos with new content
5) change rights to wpa_supplicant.conf to RW-RW-RW-
6) delete file tiwlan.ini
7) start drone and then wifi on Archos
When you restart you should repeat step 5 and step 6 and step 7.
__________________________________________________________
Great work !!!
Click to expand...
Click to collapse
beware, after reboot, you'll encounter problem connecting back to your normal wifi network again. There's a way to fix this by changing the permission of wpa_supplicant.conf after every reboot. This is gonna be a manual and painful process
My phone were able to connect to sprint to and is ready to accept connections but my EVO VIEW did not detect it. I have no problem detecting my home wifi but not my TP2 using Energy rom.
Any help would be great. I have not update the rom on this View.
ohh man i was having the same problem, and after searching for close to 2 hours i found how to make it work. unfortunately i didnt save any of the links, but i can tell u what to look for.
1. first thing is your evo view needs to be rooted.
2. need to download root explorer, paid app, or es file explorer and manually set it to have root access.
3. then u need to do a search for adhoc or wpa supplicant, which is the file u would get from the adhoc search.
4. turn off wifi.
5. go to system\bin folder and save your old wpa supplicant file. people recommend renaming it as wpa supplicant.old.
6. paste new wpa supplicant file in the system\bin folder.
7. configure permissions for new file.
8. i reset the device but i didnt see anything that said it was necessary.
for some reason the flyer/view does not have permission to connect to adhoc which is what the tp2 tether works as.
rotor nuts said:
ohh man i was having the same problem, and after searching for close to 2 hours i found how to make it work. unfortunately i didnt save any of the links, but i can tell u what to look for.
1. first thing is your evo view needs to be rooted.
2. need to download root explorer, paid app, or es file explorer and manually set it to have root access.
3. then u need to do a search for adhoc or wpa supplicant, which is the file u would get from the adhoc search.
4. turn off wifi.
5. go to system\bin folder and save your old wpa supplicant file. people recommend renaming it as wpa supplicant.old.
6. paste new wpa supplicant file in the system\bin folder.
7. configure permissions for new file.
8. i reset the device but i didnt see anything that said it was necessary.
for some reason the flyer/view does not have permission to connect to adhoc which is what the tp2 tether works as.
Click to expand...
Click to collapse
How do I root the View? Thanks for the help.
sprintsero said:
How do I root the View? Thanks for the help.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1194709
I just did it. However your View must be the correct software and hboot versions.
The Stock ROM will not see Ad-Hoc WiFi points, and the NRG ROM will force reboot if one tries to set it up that way. I gave up on changing NRG and just rooted my tablet.
BTW no need to reset the device as a last step, just stop and restart the WiFi.
stevedebi said:
http://forum.xda-developers.com/showthread.php?t=1194709
I just did it. However your View must be the correct software and hboot versions.
The Stock ROM will not see Ad-Hoc WiFi points, and the NRG ROM will force reboot if one tries to set it up that way. I gave up on changing NRG and just rooted my tablet.
BTW no need to reset the device as a last step, just stop and restart the WiFi.
Click to expand...
Click to collapse
I did read thru the steps, where do I download the drivers? Desktop or the View?
HTC View version 1.13.0000
sprintsero said:
I did read thru the steps, where do I download the drivers? Desktop or the View?
HTC View version 1.13.0000
Click to expand...
Click to collapse
You click on the links in the instructions and your browser downloads the files.
Sent from my HTC HD2 using xda premium
stevedebi said:
http://forum.xda-developers.com/showthread.php?t=1194709
I just did it. However your View must be the correct software and hboot versions.
The Stock ROM will not see Ad-Hoc WiFi points, and the NRG ROM will force reboot if one tries to set it up that way. I gave up on changing NRG and just rooted my tablet.
BTW no need to reset the device as a last step, just stop and restart the WiFi.
Click to expand...
Click to collapse
true. plus i used wrong wordage. it should be reboot instead of reset. definitely dont want to reset.lol
RECENT NEWS: Fixed wifi tether on newest ICS rom, the problem was the exact same firmware issue from the original GB roms. HTC had two AP firmwares just as with the original GB roms. See notes below about the firmware for GB for more information, attached is a zip file that will replace the non-tether compatible firmware with the firmware that does work for tether. I found it interesting that HTC's firmwares from prior ICS versions worked fine without modifications, but the latest one required this hack just like the original GB HTC roms.
Looking to get your Gingerbread Rezound's wireless hotspot to work in Infrastructure mode?
Having problems with your Ice Cream Sandwich Rezound's wireless hotspot stuttering while playing online games in Infrastructure mode?
You found the right thread!
Con247 suggested I move the quick-start guide to the top of this thread.
WARNING: DO NOT FLASH THE ZIP FILE ON ICS ROMS, DO NOT FLASH THE ZIP FILE ON ICS ROMS!
I am now an official developer and committer for the Android-Wifi-Tether project. Now that is awesome!
See list here
---KNOWN ISSUES BEGINS HERE---
1. The file wifi_tether_v3_2-pre1.apk downloaded as wifi_tether_v3_2-pre1.zip?!?
This is actually a common issue when downloading any APK via a web browser and is a result of your web browser recognizing the file format for a ZIP file and the fix is very easy. Rename wifi_tether_v3_2-pre1.zip to wifi_tether_v3_2-pre1.apk and it will install.
2. When tethering to my phone over my 4G connection, the internet gets very laggy and unresponsive...but on 3G it works fine?!?
This is a common problem among those with 4G phones in 4G areas using tethering apps. Sometimes those devices are unable to operate both the 4G radio and the WIFI radio at the same time...either due to the amount of heat generated...power consumed...or possibly hardware required for both to operate that can not be shared. Unfortunately there is no fix to make it work over 4G without an issue if you are having problems. You maybe one of the lucky ones who can use it in which case this won't apply to you. If you have issues try tethering with a 3G connection, usually this will resolve the problems.
To my knowledge this is an issue that affects all tethering apps including Verizon's Hotspot. Reports on success or failures in this forum are appreciated.
3. Your post has too many words...Lots of words make things useless, can you reduce it to an index card size or just delete it all?
I'm glad you asked. You see as a person inclined to work with things on a technical level I often find myself browsing hundreds of thousands of pages of what the layman would consider "jiberish". While the "jiberish" is of no use to a layman, it is very important to other persons of the technical inclination such as computer programmers, software developers, and the like. We share details of our changes to the "jiberish" with each other openly to help further future discoveries and fixes in the realm of computer science. If I were to say remove half of the development blog attached at the bottom of this post then I would have done the equivalent of starting the next episode of your favorite tv show (ex: Jersey Shore) halfway through an episode you never saw. While missing half an episode of Jersey Shore might not seem very important, it might have been an episode that had Snookie conceiving a child with The Situation before the second half where they all go out drinking and eventually get in a fight over the way The Situation starts grinding on some other chick. Which too any Jersey Shore fan would have been monumental. The development blog is just as monumental to us technical types. I hope that my work in getting wifi tether working on GB Rezound can help others get wifi tether working on their on devices that may be having a similar problem. So in short, no I will not shorten the post.
Click to expand...
Click to collapse
---KNOWN ISSUES ENDS HERE---
---QUICKSTART BEGINS HERE---
Most problems with Wifi Tether not working are related to not replacing the firmware correctly or not uninstalling the old apk before installing the new one. Remember if your Wifi Tether is in system you will have to use a special app like Titianium Backup or Root Explorer to remove it before attempting to replace it with my patched version.
The EasyFix zip file will attempt to remove any original Wireless Tether (having it's original APK name ie: com.googlecode.android.wifi.tether-?.apk) installed if it exist, this will also fix any force close issues you are having from a incomplete or improper install of Wireless Tether as noted earlier in this thread that some have experienced. The script for EasyFix will perform a more complete fix. The update.zip contains the updated firmware and apk. It will copy the apk to your /data/app folder and the firmware to /system/etc/firmware. Enjoy!
WARNING: DO NOT FLASH THE ZIP FILE ON ICS ROMS, DO NOT FLASH THE ZIP FILE ON ICS ROMS!
EASYFIX for GB - How to enable wireless tether on the Rezound GB! In 10 EASY Steps!
1. You need GBOnly-WifiTetherComplete32P1.zip (includes my modified apk - attached) located at the bottom of this post, CleanROM 1.7+, access to terminal/adb, and root.
2. UNINSTALL ALL COPIES OF ANDROID WIFI TETHER
3. Reboot to recovery and flash GBOnly-WifiTetherComplete32P1.zip
4. Reboot back to Android.
5. Open Wifi Tether (That you just installed, It will know you using a Rezound and use NetD by default)
6. Enable encryption if desired (it works)
7. Check MSS Clamping and Routing fix (I used both in my work)
8. Check access control (if you want it)
9. Turn on Wifi Tether
10. PARTY!!!
EASYFIX for ICS - How to fix wireless tether stutter on the Rezound ICS! In 9 EASY Steps!
1. You need to download wifi_tether_v3_2-pre1.apk to your SD card (only the apk - attached) located at the bottom of this post, an ICS ROM, and root.
2. UNINSTALL ALL COPIES OF ANDROID WIFI TETHER
3. Install wifi_tether_v3_2-pre1.apk using your favorite file manager.
4. Open Wifi Tether (That you just installed, It will know you using a Rezound and use NetD by default)
5. Enable encryption if desired (it works)
6. Check Routing fix (Required)
7. Check access control (if you want it)
8. Turn on Wifi Tether
9. PARTY!!!
If for some reason you want AD-HOC tethering, simply change "Setup-Method" to WEXT (remember AD-HOC/WEXT does not support encryption). Typically everyone is wanting AP mode so Auto/NetD is likely what you are wanting.
Click to expand...
Click to collapse
---QUICKSTART ENDS HERE---
Development Blog Begins Here
I noticed that this device has 4 firmware images for the wifi radio in GB and 6 in ICS. I think part of our problem is restrictions placed in the firmware by HTC for VZW. In short you can find the firmware in /etc/firmware/fw_bcm*.bin and if you replace fw_bcm4330_apsta.bin with fw_bcm4330b2_apsta.bin (backup your firmware folder first!) you can now open an access point with wpa2 encryption. I however have not been able to get a complete connection, and it always gives up waiting on dhcp address and iptables shows no packets routed or dropped. I'll look into it further after the weekend is over right now all I have is my phone and development further than this might not be possible without my PC. I think the VZW hotspot is loading firmware b2 of the access point firmware (apsta) for it's work while standard android use loads the first firmware.
#2: ifconfig shows I have a valid interface and traffic on it but forwarding does not appear to be happening. (Packet count increases with attempts to visit website, I setup static Ip on the client to avoid DHCP failure during my tests.) Looks like I'm missing a route as well.
#3: and the interface has not been assigned an IPv4 address so that explains the lack of a route.
#4: I can get the Rezound to communicate to a (both ways if the Rezound initiates the connection/ping) tethered device but I can not get the tethered device to communicate with the Rezound (as if the data just goes into a black hole). But ARP routeing tables show correct information on both sides of the connection. I appear to have a missing route somewhere and it's getting late.
TO REPRODUCE:
You need Wifi Tether 3.1-beta 11, CleanROM 1.7+, access to terminal/adb, and root.
TURN OFF WIFI / TETHER APPS IF ON
Create a backup of /etc/firmware/fw_bcm*.bin
Replace fw_bcm4330_apsta.bin with fw_bcm4330b2_apsta.bin
Open Wifi Tether
Set device as Google NexusOne
Set method as NetD (master)
Enable encryption if desired (it works)
Change Lan (Select 192.168.2.0/24)
I have not determined if MSS Clamping or Routing fix are needed but my tests include routing fix.
Turn on Wifi Tether
in terminal do the following without qoutes:
"su"
"/system/xbin/ifconfig eth0 inet 192.168.2.254 netmask 255.255.255.0 mtu 1500"
On the device you want to connect to the hotspot with do the following
Set static ip information (DHCP will not work at this time)
IP: 192.168.2.103
Netmask: 255.255.255.0
Gateway: 192.168.2.254
DNS1: 192.168.2.254
DNS2: 192.168.2.254
Connect device to hotspot.
Device (not the Rezound) will show connected but have no network access at this time.
On the Rezound in the terminal you can verify the device is connected with ping
"ping 192.168.2.103"
You will see the ping replies! (Press volume down + "C" to stop once confirmed if using terminal)
WOOT! We're half way there! I think if Wifi Tether setup the interface with the IPV4 address properly instead of us having to go back and set it after the fact that this may work without any further trouble.
Once we have Wifi Tether resolved, I will have my dream device! ...at least for the next 6 months \\
#5: I HAVE IT! I will post a working fix/update within a few hours! It works!
#6: FINAL SOLUTION!
The problem was two fold, first the phone has two sets of firmwares and by default loads a non-accesspoint capable version when trying to setup an accesspoint. I've already explained that part in my first post. The second problem, the accesspoint interface firmware operates on eth0, which is NOT what wireless tether expects...so I either had to intercept tether's scripts and fix the interface name OR modify tether to use the proper interface name (which I did both, but the fix I am posting is a modified tether without scripts...it is simpler, and EASY FOR THE WIRELESS TETHER TEAM TO FIX).
ADVANCED FIX - How to enable wireless tether on the Rezound! In 12 EASY Steps!
Please scroll down to EASY FIX 2 for instructions on using con247's zip in recovery instead of moving files around in root explorer yourself.
Download the attached MODIFIED WIFI TETHER APK, it has the interface names for the networking accesspoint corrected to eth0 and not wl0.1 (which was the default for google nexus).
1. You need Wifi Tether 3.1-beta 11b2 (my modified version), CleanROM 1.7+, access to terminal/adb, and root.
2. TURN OFF WIFI / TETHER APPS IF ON
3. Create a backup of /etc/firmware/fw_bcm*.bin
4. Replace (existing) fw_bcm4330_apsta.bin with fw_bcm4330b2_apsta.bin in /etc/firmware
5. Install modified Wifi Tether
6. Open Wifi Tether
7. Set device as Google NexusOne
8. Set method as NetD (master)
9. Enable encryption if desired (it works)
10. Check MSS Clamping and Routing fix (I used both in my work)
11. Turn on Wifi Tether
12. PARTY!!!
For those with trust issues download apktool and decompile wifi tether yourself, open smali/com/googlecode/android/wifi/tether/system/Configuration.smali
using a NON DESTRUCTIVE TEXT EDITOR! I.E. one that will not change anything you do not specifically change! I used JEdit on Ubuntu, I read Notepad++ on windows will work good too.
Under ".method private setupSoftapGoogle()V"
Change line 2707:
.line 327
const-string v0, "wl0.0"
To:
.line 327
const-string v0, "eth0"
Save and rebuild & sign apk.
Have a great day!
This hack is all of my own work, please give me credit if you use this or include it in your rom/mod!
Donations are always welcome as I do appreciate a good beer ;-D
Update:
Questions about will it work on my ROM or Kernel, you will just have to try it. Remember to backup your firmware folder to revert incase you make a mistake. This method should work on any GB rom and should work on ICS as well. So long as the kernel/rom dev has not radically modified their ROM/Kernel in the wifi/tether department. Enjoy!
Also attached some nifty images with my chicken scratch on them to help point out the original file differences (in size) as well as what we are replacing in case there was any confusion.
EASYFIX 1/2 & INSTRUCTIONS REMOVED - PLEASE SEE EASYFIX
Enjoy, Thanks goto con247 who packaged up a recovery zip to move the firmware!
This fix has been updated and is now using Beta12 of Wifi Tether.
The patch is slightly different instead of patching Google's Nexus driver I just copied it to it's own routine patched the device name as indicated in the above patch instructions, renamed it to HTC Rezound GB and added it to the device menu. No more looking like a hack here. The Wifi Tether team could easily add this patch to their base code (I did this using a text editor on the smali code), but it would only benefit HTC Rezound GB users with rooted devices. Oh well...Enjoy Everyone!
Update 04/11/12: Fixed downloads...not sure what was wrong. Re-uploaded the files and all is well. Sorry for the inconvenience.
Update 04/12/12: Really fixed downloads...I do not know what has happened. I tested them when they first went up and they worked fine. Could be a browser issue maybe? I was using Chrome, this time FireFox. Never had any issues uploading before. I downloaded both files again completely to be sure this time, everything looks good. Again I apologize for the inconvenience.
Update 04/23/12: Updated patch to latest beta14.
Update 04/28/12: Corrected firmware/module file locations for Rezound. Removed SoftAP (does not work on Rezound GB profile anyway). Tested Wext on Rezound profile (works for those wanting Adhoc, note: encryption not supported on Adhoc). Added patch notice to App title bar so you know what is installed (default vs patched). Also gave myself credit for the patch in the about box and added a link to this thread for future reference and added a donation button in the about box for those who feel generous (Don't forget about the Wifi Tether team, without which non of this would be possible!). Enjoy! (Fixed Download: I forgot to sign the APK, sorry everyone!)
Update 05/02/12: Moved quickstart guide to top per con247's suggestion. Also note this fix is NOT needed for any ICS variants, only GB.
Update 05/18/12: Per feedback from Kidney Poker I have patched the Wifi Tether Application to include a Rezound ICS profile, in that profile I added correct ICS firmware folder/filenames (The Rezound's firmware/modules are in different locations than Google ICS), the result of which I believe caused some stuttering in the connection was running applications requiring a consistent and low ping (I.E. Online Games). I appreciate any additional feedback anyone would like to add on this matter, let me know if this patch improves your tethering experience or not. Thanks! ICS does not need firmware files moved for AP mode to work so do not flash the zip, you only need the apk of the patched Wifi Tether application. DO NOT INSTALL WifiTetherFixCompleteR14B.zip on ICS!!!
Update 06/01/12: Added beta15 PUBLIC TEST 1 UNOFFICIAL Wifi Tether with my changes that I am submitting to the Wifi Tether team. Give it a try, fiddle with the options, tell me how it works! Post your feedback and Thanks!
Update 06/02/12: Beta15 PUBLIC TEST 2: Fixed bug where Automatic quota shutdown appeared twice in settings. Configure ed keep-alive shutdown timer option to be disabled when keep-alive is set to retry indefinitely.
Update 06/27/12: Android wifi-tether now has an official download with my changes includes and some new features added! Woot Woot!
Update 07/14/12: I am now an official developer and committer for the Android-Wifi-Tether project. Now that is awesome!
Update 08/21/13: Updated post to include fix for latest ICS release, the firmware issue from GB returned to this version of ICS. Simply replacing fw_bcm4330_apsta_b1.bin with fw_bcm4330_apsta_b2.bin located in /system/etc/firmware/ and this change will enable wifi tether using android-wifi-tether. Updated zips to include latest non-experimental version v3.3 beta 2 and attached for direct download. GB firmware zip is intended only for GB roms, and ICS Latest zip is intended only for the latest ICS version v4.03.605.2 710RD. You will need a custom kernel to tether, the stock kernel will not work as it lacks the proper NAT layers to do so.
Click to expand...
Click to collapse
!!! STOP HERE - DOWNLOADS BELOW !!!
Wow. I'm impressed. Keep up the good work. It sounds like you're on to something.
Sent from my ADR6425LVW using xda premium
omg if you get this to work I will give you all the cookies your heart desires!!!
I understood about a total of 6 words in the OP, but I do know that this will be awesome if you can get it working. Nice work
any update on this?
Unfortunately I've not been able to resolve the routing issues yet, communication starting from the client towards the tether point (rezound) arrives but does not seem to get past the interface device (packets are counted but data is getting dropped after reaching the rezound. I am still trying to resolve this.
I got it, will post a working update within a few hours!
#2: MOD COMPLETE! ENJOY!!!
Fantastic work!
will this not work on ineffabilis 1.3?
It should work on GB roms.
will this work If im rooted and have ziggy's oc kernal but still on stock debloated (by me) vzw gb rom?
I looked in the firmware folder and I couldn't find the bcm* file to backup and both of the files I'm supposed to replace each other with are already in there.
antispiral said:
I looked in the firmware folder and I couldn't find the bcm* file to backup and both of the files I'm supposed to replace each other with are already in there.
Click to expand...
Click to collapse
I believe you are supposed to rename the one with the b2 in it to remove the b2 and let it replace the one that is already there WITHOUT the b2. if that makes any sense.
Regards to other roms/kernels:
You will have to try it yourself, but this method should work on all Rezound GB Roms as long as the firmware folder is there and the dev has not modified anything related to tethering/wifi in a radical way.
That is absolutely right! Replace the existing file fw_bcm4330_apsta.bin with the fw_bcm4330b2_apsta.bin file.
con247 said:
It should work on GB roms.
Click to expand...
Click to collapse
Con where's the flashable zip man? J/K but that would be awesome. This may make me go back to GB. Thanks for this
Sent from my ADR6425LVW using XDA
Doddzilla said:
Con where's the flashable zip man? J/K but that would be awesome. This may make me go back to GB. Thanks for this
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
This is one of the reasons I haven't went to ICS yet. I have everything I wanted (minus ICS) with this phone running Gingerbread now. Once ICS source is out, that may change.
SirGatez said:
That is absolutely right! Replace the existing file fw_bcm4330_apsta.bin with the fw_bcm4330b2_apsta.bin file.
Click to expand...
Click to collapse
so can't I just delete the fw bcm4330 instead of replace since the fw bcm4330b2 is already in the folder?
Confirmed working on Ineffabilis 1.3. Tethering to my Mac running Lion and I didn't have to change any settings in the Wifi Prefs. DHCP worked just fine.
antispiral said:
so can't I just delete the fw bcm4330 instead of replace since the fw bcm4330b2 is already in the folder?
Click to expand...
Click to collapse
Yes, delete fw bcm4330 (or backup to another location) and rename fw bcm4330b2 to fw bcm4330
Wifi Not working in Root Box and SuperNexus 2..(Stuck on "Obtaining IP adress")
Hi,
I Have GSIII I9300. It's rooted and I have installled latest Siyah Kernel and running Latest Jellybean Touchwiz 4.1.2. All is well.
I decided to try another Rom as secondary rom. I installed the Rootbox Rom and gapps as per instructions. And it booted
all is working except that the Wifi gets stuck at "Obtaining IP address". It connects to my network but doesn't get IP address from DHCP.
I thought it was a rom specific issue, So I tried SuperNexus 2.0..Still the same issue! I also tried installing them as Primary rom.
Still it gets stuck at "obtaining IP address".
Anyone have any inputs on what could be the issue here??
Finally Figured it out...
All you have to do is, Install a Touchwiz rom. Setup your Wifi.
Then go to "System/Etc" and copy the 'wifi' folder onto your External SD CARD. take note of the permissions on it before hand.
And then boot into your second (Or problematic) rom, turn off Wifi, and delete the same folder from same location (OR BACK IT UP!) and paste in your prev. copied folder in it's place. and set the permssions accordingly. And then Start Wifi!
Sorry I can't write properly. I am typing this using Wifi with PA ON MY SGS3!
Hi I don't no what the problem is but I have the same issue with rootbox and most new builds of cm10.1 AOKP aosp I found the way to fix it was using a static IP address also it doesn't matter what router I use even trying to tether to my wife's gs3 she dose not have this problem on hers running the same roms
Yes. I also can run with static ip, but then it loses Internet connectivity for some reasons.. sometimes it will come back and sometimes not.
Yes. Only happens in CM and AOSP roms..
i use rootbox most of the time and the first rom it stoped working on was nightly 20130125 i looked in the changelog and found this
rootBox Project name: vendor_samsung
•codeworkx - smdk4412: cleanup
•codeworkx - smdk4412: update bt and wifi firmware
•codeworkx - smdk4412: add t0ltei
i think the wifi firmware upgrade may be the problem as all nightleys before worked and none since have, hope this helps you work out the problem
I am running the latest stable release. BTW, I found thst it neither works in any non touch wiz ROM. When I set static IP. It connects to the network for a while and then disconnects.... connects but internet doesn't work.. really frustrating.
mine is the exact same i never noticed about conection to internet as i have unlimted data and olny use the router for straming meadia around house i also think not many s3 have this problem like i said my wife has a s3 and on the same roms her conection is fine so dont think it will be fixed any time soon if at all and searching the foroms has not showed up anything
WiFi problems worth trying a different kernel.
jje
thanks tried siayh,yank555,stock cm and temaseks none have worked fore me
So.....No custom roms for us???....damn sucks.....that's the reason I bought S3 for just now.
Finally Figured it out...
All you have to do is, Install a Touchwiz rom. Setup your Wifi.
Then go to "System/Etc" and copy the 'wifi' folder onto your External SD CARD. take note of the permissions on it before hand.
And then boot into your second (Or problematic) rom, turn off Wifi, and delete the same folder from same location and paste in your prev. copied folder in it's place. and set the permssions accordingly. And then Start Wifi!
Sorry I can't write properly. I am typing this using Wifi with PA ON MY SGS3!
thanks for the fix will give it a try in the morning and let you know if it works for me to
edit dont use dual boot and usally use yank555 kernel it dident work tried with siayh it worked thanks again
NHS2008 said:
Finally Figured it out...
All you have to do is, Install a Touchwiz rom. Setup your Wifi.
Then go to "System/Etc" and copy the 'wifi' folder onto your External SD CARD. take note of the permissions on it before hand.
And then boot into your second (Or problematic) rom, turn off Wifi, and delete the same folder from same location and paste in your prev. copied folder in it's place. and set the permssions accordingly. And then Start Wifi!
Sorry I can't write properly. I am typing this using Wifi with PA ON MY SGS3!
Click to expand...
Click to collapse
Thanks NHS2008 - how exactly did you do the file swapping? The file explorers/managers I have tried aren't able to do it for some reason!
deafmetal said:
Thanks NHS2008 - how exactly did you do the file swapping? The file explorers/managers I have tried aren't able to do it for some reason!
Click to expand...
Click to collapse
I used ES Explorer on Standard TouchWiz Rom and used CM File manager that was present in PA Rom.
Sadly, Roms like SuperNexus and Rootbox don't come with ANY file manager by default.
Though you can of course use your data to download ES File explorer on other roms..
AND you need to be rooted to be able to access these folders.
In Es Explorer, Go into Settings/Root Settings and enable first three options.
The 'wifi' folder is located in "/sytem/etc/.."
(Press back when in SD CARD in ES)
also when i used the wifi file from a touchwiz rom although the wifi worked it stoped my wifi teather from working so i went back to the last rootbox rom that had wifi and wireless teather working extrated wifi folder pasted and now both are working. again many thanx for the fix
neilster2020 said:
also when i used the wifi file from a touchwiz rom although the wifi worked it stoped my wifi teather from working so i went back to the last rootbox rom that had wifi and wireless teather working extrated wifi folder pasted and now both are working. again many thanx for the fix
Click to expand...
Click to collapse
Great! What was last one with Wifi working??
rootbox Nightly-20130119 and you dont need to load up the rom just extract the file
It's not working for me unfortunately - wifi's not even switching on anymore!
deafmetal said:
It's not working for me unfortunately - wifi's not even switching on anymore!
Click to expand...
Click to collapse
i had same problem last night when using touchwiz wifi folder either change the kernel to siayh or use the wifi folder from rootbox as above
Working
Well, this worked for me! (Finally)
I did this procedure.
1: I wiped my device, installed a touchwiz rom (Darky S3 v8.8).
2: Downloaded ES File Explorer
3: In ES FE, I asked for root access, R/W ability on system.
4: Copied the wifi map to my external sd card,
5: Went back to recovery, wiped my device again.
6: Installed new rom (SuperNexusRom 2.0 build 4)
7: Downloaded ES File Explorer
8: In ES FE, I asked for root access, R/W ability on system.
9: Copied my backup from external sd card back.
10: For rebooting, I activated the wifi. (Didnt work the first time)
11: Rebooted my device.
12: After booting, worked like a charm. (Now rebooted 20 times or so)
Hopefully this works for you guys to.
Notes:
- Having some glitches when turning on Bluetooth. Wifi connection is killed several times, but comes back up.
- Havent tried wifi tethering, dont use it here.
grtz DarkMarkus
Hi all
I have successfully rooted my hudl tonight (first ever go at rooting!) and all is fine - system works, apps work OK.
I need to be able to connect it to ad-hoc networks but am struggling....
I am using the tablet to run Sky Safari, a planetarium software that has telescope control. The plan is to connect to the SkyFi wireless unit that connects to the telescope's goto system. Then when selecting an object from the planetarium and hit GO, the scope moves to the right part of the sky.....
I found an updated wpa_supplicant ( do you think I can find the link now....!!!!) but this does not work and actually stops wifi from being enabled at all.
Its definitely something around this file because as soon as I switch back the original, wifi will start again....
This was the thread for the initial rooting instructions http://forum.xda-developers.com/showthread.php?t=2376077
Found the link for the wpa_supplicant file... http://androidtablethacks.com/android-tablet-hacks/how-to-enable-adhoc-wifi-on-android-tablets/
I have no idea how to edit/create the wpa file but hoping someone on here can help - or point me in the right direction!
Thanks
Daz