[**SOLVED**] 2.3.12 REenable ad hoc wifi networks under ICS - wpa_supplicant

Search This thread
Wireless tethering used to not work for me.

The update that finally rolled out to Aus 2 nights ago seems to have fixed it for me. I tethered last night through my Samsung Galaxy S2 that is stock standard. I haven't flashed or ROM'd either my GS2 or my Prime.
 

demandarin

Senior Member
Apr 7, 2010
7,021
2,038
Alexandria, Va
Wanna know why people leave XDA? Because when they post things that definitely DO work for them and others, people immediately jump down their throat and try to make them feel like idiots. I have no idea why 2.0.7 works for me and several friends that own both primes and tbolts but it does. Period.

Sent from my ADR6400L using XDA App

Don't take what he said personally. ALTHOUGH some members can be like what you described, its just out of frustration for issues going on with tethering.

THIS issue is crazy because its hit or miss on several devices. IM confident it will be resolved soon though through developement.
 

vincepg13

Senior Member
Jul 23, 2011
961
135
any news?

before I upgraded my TF to ICS I used barnacle tether. after i realised it didn't work because of ad-hoc I now use wifi tether b6 which works great if you change its start up method to softap.

i use a sensation to tether it and today i upgraded it to senseless ics which is so dam awesome its the first time ive paid my phone attention since i got the prime. but then i realised for some reason wifi tether on softap stopped working :(

with the exact same settings on gingerbread sense it works fine, dont know what's going on there must be an incompatibility with ics. Either way i really want support for ad-hoc so i can use internet on my transformer and have ics on my phone!!
 

youngnex

Senior Member
Sep 29, 2011
295
82
Tampa, FL
Creamy Goodness, you only have 1 post.

how can we trust you? i could of tried it if we had a recovery...but i dont want to brick my prime

needing this badly
 

Lock-N-Load

Senior Member
Aug 25, 2010
1,618
392
Under Your Skin
You tried this yet lock n load? Its release was just the other day if this is a new file.

I have not, but I will today and post back up. I do not hold out much hope. I have tried maybe 5 wpa files, none for us, all for other devices, none work. Even found out some devices under ICS still only use 1 wpa file while we now have 2 and they work together so... don't get to excited.

I did see this the other day but blew it off given it is not for our device.

I second that notion, please test it.

Gesendet von meinem Transformer Prime TF201 mit Tapatalk

Yeah, I bet you would like me to be the guinea pig :)
 

Swiftks

Retired Forum Moderator
Mar 16, 2011
3,741
1,910
The Woodlands, TX
HOLY ****... IT WORKED!!!!

Not how I expected, but I solved it nevertheless.

testing now - will report back what I did and how I got it to work

Just backed up wpa file and replaced with new one? Second one not affecting the new one?

Actually, looks like just the one @ /system/etc/wifi ????

^^^ Nevermind, wrong file type :p ^^^
So, the one at /system/bin
 
Last edited:

Swiftks

Retired Forum Moderator
Mar 16, 2011
3,741
1,910
The Woodlands, TX
Confirmed working on laptop AD HOC wifi tether as well!

This is great, I spend Monday thru Wednesday in a hotel usually, and as with most hotels, wifi sucks and is slower than $hit. The only saving grace is the LAN line runs about 1.5mbs, put that still didn't help my Prime, until now... Now I can use LAN line for laptop and setup a AD HOC wifi network between my laptop and Prime, thus using the LAN line for my Prime as well. :D

Thx again for figuring out that wpa_2 was the problem file... who would have thought... makes me wonder if the other wpa files might have worked if we supplemented them for the second one as well... oh well, all is fine now.
 

Lock-N-Load

Senior Member
Aug 25, 2010
1,618
392
Under Your Skin
I tried that wpa_supplicant2 trick a few times and it never worked, this time I did. It is always kind of scary as I was always afraid to brick as we have no ROM backup. But I just took the risk and always had wpa backups of the OG files.

My protocol was typically:

1. replace wpa_supplicant, leave wpa_supplicant2 untouched - test
2. replace wpa_supplicant, use same file and replace wpa_supplicant2 - test
3. leave wpa_supplicant, replace wpa_supplicant2 - test

On top of this, you have multiple tether apps and multiple settings.

This time, #3 worked. This time, I just said F it and only tested Wireles Tether 2.0.7 as it gets cumbersome with 1-3 AND testing different config settings in all of those Wireless tether beta apps. And hey, who cares, it now works and everyone can use it.
 
Jun 3, 2010
17
6
interesting, i just overwrote wpa_supplicant on my tab 10.1 and it worked. Anyways, I don't see what the risk of bricking it comes from. If you rename the old file you can always restore it if needed, right?
btw, thanks for linking to my post. next time I post something I might have more than one "thanks" and you guys will believe me :D
 
Last edited:

Lock-N-Load

Senior Member
Aug 25, 2010
1,618
392
Under Your Skin
interesting, i just overwrote wpa_supplicant on my tab 10.1 and it worked. Anyways, I don't see what the risk of bricking it comes from. If you rename the old file you can always restore it if needed, right?

Well, the Tab 10.1 is not the Prime. The Prime has 2 wpa_supplicant files, the Tab I will assume does not like the Xoom does not. So, EVERY post on the web you will find about doing a trick like this talks about only wpa_supplicant, so having a wpa_supplicant2 for us made it tougher to figure it all out and in the end, it looks like wpa_supplicant2 is the key and NOT wpa_supplicant

Anyway, yes, a brick in this mod is very very low likelihood BUT you are in fact messing with the system and well, it is always a risk plain and simple and the Prime has no recovery yet as we do not have unlocked bootloader.
 
  • Like
Reactions: Creamy Goodness
Jun 3, 2010
17
6
yeah, I was just surprised that the prime has two of those files.
I wonder why google even disabled adhoc networks. There is no technical reason.
If you want the maintainer of your ICS rom or whatever you call it to add this, I *think* this patch file is all they need: hxxps://github.com/mrdeadlocked/external_wpa_supplicant_8/commit/2eb2b22af720e42f3852c24e8b4fd6d821ad0f28#diff-0
There's also this app, based on some version of this patch, but not sure if it's the correct one. Maybe worth a shot for ppl that can't follow the other instructions for whatever reason...
hxxp://arenddeboer.com/wifi-ad-hoc-enabler-for-android/
 

Top Liked Posts

  • There are no posts matching your filters.
  • 12
    ICS on the Prime, for many, took a step back and now claims "ad hoc networks are not supported". So, many of us who have been tethering the last few weeks via a tethering app now cannot as ICS is seeing the network as ad hoc and is now reporting that is not supported. I personally used wireless tether under Honeycomb every single day on my Prime. Now, for me, and many, we cannot. I have a whole growing thread in the general area and it really seems this is the root of the issue for those of us that do not have built in wifi hot spots and use a tether app.

    So, is this something a dev can sort out? How to get back ad hoc network support under ICS on the Prime? I have seen topics on it in google like this one, but this "fix" did not work.

    (BTW - if a mod thinks this is not in the right place and wants to move it to the General thread, please just delete this as there is already a thread there, but a help request in the dev area seemed logical. If not, sorry.)

    ///////////////////////////////////////////////////////////////////

    IT HAS BEEN SOLVED 2.3.12

    Based on a post I read the other day, and that I was asked to test today, I decided to try 1 more time and it worked!! But not how I expected. I tried 3 tests... the final one worked!!

    So, here is the process:

    1. root is required AND make sure you have your file system app (like Root Explorer) set to make files R/W so you can edit/rename/set permissions
    2. turn off wifi
    3. go into system/bin and rename wpa_supplicant2 to wpa_supplicant2.bak - that's right folks.. it is NOT wpa_supplicant but wpa_supplicant2 that is running the show
    3. download the wpa_supplicant file found here post #24 in my other thread
    4. unzip it
    5. rename it wpa_supplicant2 NOT wpa_supplicant
    6. move it to system/bin and paste it
    7. set permissions to xxx, x, xxx (columns) - see more details below if confused
    8. go back and start up wifi
    9. turn on wifi analyzer and you will see (*)AndroidTether with no red Ad Hoc notation!!
    10. click to connect
    11. surf and tether away!!

    No rebooting needed, it is instant

    I am using the good old original Wireless tether 2.0.7 app I always used! None of those beta releases and picking settings and blah blah

    Yes, I was able to connect right back to my local wifi with no issues as well!

    PLEASE hit the thanks button, I worked long and hard on trying to get this to work

    #7 details if you don't understand permissions settings

    When you set permissions (long press the file) a pop-up opens and it shows 3 columns with 3 checkboxes in each. Each "x" is to be checked

    Read...Write...Execute
    x..........x..........x
    x......................x
    x......................x
    6
    hxxp://tabletroms.com/forums/ice-cream-sandwich-adam/4262-working-ni-adam-ics-adhoc.html

    tested and works fine on my 10.1 tab running ICS
    YMMV

    -edit- tried to add as attachment
    1
    While I understand that it's easier to just talk to a dev over IRC, I really hope a working solution can be released here soon.
    1
    I seriously wish people would research the true issue before just posting up that "it works"... there is a whole HUGE thread that explains why it does not AND IF IT DOES why it does work for you and not others.

    Not only that... there are whole trial and error tests with ALL versions of Wireless tether - including all beta versions.
    1
    check post 1.. directions and screenshot are in place!!

    (please hit the thanks button :) )