Or Continue to Thread: [ROM][Nightly][ICS] Team Eos W…
Find Your Device:
4th February 2012, 06:42 AM   |  #2891  
bigrushdog's Avatar
Recognized Developer
Flag Fontana, CA
Thanks Meter: 6,085
 
3,162 posts
Join Date:Joined: Apr 2007
Donate to Me
More
Quote:
Originally Posted by mr_wrong_0

I don't think we have a fix yet but they are working on it, there are a couple die hard ad-hoc enthusiasts such as kelvie, and BRD that are working on a modified wpa_suppliplicant file that will enable ad-hoc connectivity. It's been trickier than the honeycomb version, but I promise there is work being done on it.

The root of the problem is that adhoc is a depricated technology. That being said, the reason we are having issues is adhoc conflicts with wireless peer2peer, or p2p. This is a new wireless technology possible because ics has implemented the config80211 Linux wireless api stack. Some of you may have noticed a new wireless interface named p2p0 which is a member of the wlan0 control group. Also you may have noticed that p2p is also broke. I believe this is why some ics devices utilize two wpa_supplicant binaries. Also it looks like the kernel filters ibss beacons when the p2p0 interface is up. But Im pretty sure I found the source and its an easy fix. ICS is a very different Android from past releases. ICS is very forward looking and continues to merge with Linux common. Adhoc looks doable but I recommended adhoc fans upgrade their phones
The Following 4 Users Say Thank You to bigrushdog For This Useful Post: [ View ]