IssueTracker

+Chris/Adam

This is in fact an important problem for ActionBarCompat.
One cannot add any other action item when SearchView is included in always-expanded mode.

Having attribute app:showAsAction="always|collapseActionView" for searchView and calling MenuItem.expandActionView() in code as a workaround doesn't really have the same effect.

Please review its priority.
Forcing the user to use SearchView with 2 taps decreases the quality of user experience on our part.

I agree with #4.

[Comment deleted]

[Comment deleted]

Additional information that can be useful:
The issue only happens when SearchView is included in ActionBar menu.xml and setIconifiedByDefault(false) is applied.

SearchView item definition from menu.xml:

<item android:id="@+id/menuSearch"
        app:actionViewClass="android.support.v7.widget.SearchView"
        app:showAsAction="always"
        android:title="Search">
</item>

Including SearchView as custom view works correctly, like in this scenario:

@Override
public void onCreate(Bundle savedInstanceState) {
    super.onCreate(savedInstanceState);

    SearchView searchView = new SearchView(this);
    searchView.setIconifiedByDefault(false);
    getActionBar().setCustomView(searchView);
    getActionBar().setDisplayShowCustomEnabled(true);
}

It's the same for ActionBar not only ActionBarCompat.

Ditto this is an ugly bug.  It prevents this use case:
- search is done via a REST API whenever someone types a character in
- search takes a while to happen so we should display a progress indicator to user so they don't kill the app because it's not responsive

2nd step is impossible :-(

This does seem semi-important as it could be the basis for some differentiate apps.

I have submitted a patch to the master branch for adding Adhoc Wifi support.  The
patch only provides the ability to programatically add or connect to a Wifi Network.
 It does not modify the Settings App to take advantage of that.  However, the
settings app could easily be modified to use the code.  I may submit a patch for that
soon as well.

Link is here:
https://review.source.android.com/9714

option to share 3G connection to a PC using ad-hock would be awesome and realy a hit
for business users, connect your laptop and phone on teh go wirelessly over wifi

anyone knows the current status of this?

So, I have the same question as koliaskostas... Ad hoc support will be very useful and
seems to be very easy to implement. I don't want to root my phone but without ad hoc
support I'll do it probably.

Please add support for adhoc networks. I want to connect to internet through my laptop
shared lan connection.

And how do I Edit that file to enable as hoc on my Magic.

[Comment deleted]

You CAN connect your HTC Hero to an ad-hoc network. I've done it with mine.

The process is a bit complicated, but it's explained on the internet. Basically, you
have to root your Hero and edit 2 wifi configuration files in order to manually add
your wifi ad-hoc network.

It should be done with care, though, because wrong settings can remove the wifi
functionnality from the phone. You would then had to do a factory reset to get it back.

So back up your phone before doing this tweak.

[Comment deleted]

Sent you an email.

To other people with the same issue :

Basically followed that :
http://blog.joint.net/2009/07/connecting-android-phone-through-adhoc.html

But changed some things as my adb shell has no root rights by default, so I couldn't
do the adb push commands.

Had to copy the files on the sd card, and get then back to their place using dd
command + chown and chmod.

We should be able to do this without rooting the phone. It doesn't make sense! When you
root your mobile phone you can share files on bluetooth too, Android is supposed to be
open-source so they should see these applications and add these functionalities faster
but I guess we will not have Bluetooth file transfer on 1.6 either :( I paid a lot of
money for my Hero but I keep using my Nokia 6630 since it can connect to my pc over
bluetooth and also it can share files on bluetooh...

we bought this hero for such a thing and now we find its not possible, that sucks bad.

How long does it take to allow users to change three config lines? Apparently at
least 21 months (and still counting)

Our application needs this functionality, because its core service is to connect people
around. In WinMobile we have already implemented this connectivity and would like to
make the app crossplatform.

Our studio would also find this useful for a game we're developing. Keeping my
fingers crossed that it gets official support.

So I see people talking about adhoc where mobile connects to a laptop. Can a adhoc
network be formed between mobiles, say 4 friends want to chat without using wifi AP.

I read that sdk does not provide adhoc capability to the application developer !!

You might want to look at Issue 36905835 and also Wi-Fi Direct, neither of which are
currently supported.

I dont know if it´s useful for you, but for me it worked fine.
There is a Software called Connectify http://www.connectify.me/ wich is using a
feature of Windows 7 that can provide an Infrastructure WLAN from a normal PC or
especially a Notebook.
That works fine even it´s Beta!

Hope I can help you

Unfortunately it does not support many network adapters. And I have Intel 4965!
http://www.connectify.me/docs/index.html

This sucks. connectify doesn't work with 99% of intel wifi cards.  Please add adhoc
networking support :)

[Comment deleted]

I am supporting a free-for-everyone wireless mesh operating in adhoc-mode...but my G1
cannot connect easily to it. Annoying!

I found this article and it works fine with my MT3G

http://bink.nu/news/windows-7-as-an-wifi-accesspoint.aspx

It is reported from 2008 Jan, and now it is 2010 Jan. Anyone know what the hell is
going on? I don't want to root my milestonn!!

as happy as i am with android 2.01 there are little things like this that bug me to
the point where i'm considering rooting my droid.  I've seen enough apps that can be
controlled via sms that makes me worried about granting super user priveliges, but
it looks to me that i can't rely on an update to get these trivial tasks completed.  
2 years is too long to wait for parameter changes.  guess i got no choice but to
void my warranty and put my handset in a weakened state of security

[Comment deleted]

I have been trying to get Google to apply this into their branch, and while they at
first said this would certainly be added soon, they are now ignoring the issue
completely. Technically the changes are very very very very MINOR, and they could
have added it immediately if they wanted to. They don't want to. They are afraid.
Afraid operators will complain and withdraw their support, but don't care what
customers say, operators are more important.

The benefit of an open source system is that we can provide much of the work to fix
these bugs, and fix them in our own systems if we want to.

I see discussion from Google engineers of problems with the one patch noted above by
drew.jacobs:

 https://review.source.android.com/#change,9714

but it seems that no one followed thru and fixed the patch.

lanilsson, can you point to any relevant patches you've proposed, archives of
discussions etc.?

I see some folks having success on rooted phones here:

 Connect G1 to Ad-hoc network: http://modmygphone.com/forums/showthread.php?t=22681

Has anyone deployed a patched system that resolves this bug?  I note requests for
cyanogen to do so here:
http://forum.xda-developers.com/showpost.php?s=b9f683bc4fc1403a7d078a1afbe7f1d5&p=4864323&postcount=4007

I suppose that developer could revise UI in order to include wifi TTLS/PAP with
certificate option. It is a very important issue, at least in almost all European university and enterprise environments, as you can see in ID 1386.
Its very easy to develop because linux already has it, its only a change in
wpasupplicant.conf, (its already possible using wifihelper app but we need to root
device to use it and so voiding warranty).
I assure it is a very important fault repeating an iphone initial fault. (I think it
is a USA centric problem... because we in Europe use open encryption standards (non
MS centered) and cisco rooters)

Please add ad-hoc mode. This enables some very interesting and unique use cases for
Android devices such as group coordination in places with no network infrastructure
of any kind. Very useful to university research groups.

Interesting - I put Wireless tethering on my Android G1. My friend's iPod Touch can
connect to it, but a non-hacked Android phone cant :-(

Since you were discussing it, there's a new 1.1 version of Connectify that supports a
lot more Intel cards (like the 5100 and 5300... maybe more). www.connectify.me 

I'm trying to create an application that talks to a wifi device.  Without the adhoc feature I can't create this
application.  I am trying to develop an Android version.  There are already iPhone versions so apparently, the
iPhone supports adhoc wifi mode.  SO WHY DOESN'T ANDROID?  Can we please get some idea of the status of
this?  It been pending for 2 years!!!

How funny...googling "android adhoc network" brings this issue up as first result.
Developers, do you hear the bells ringing?

Similar to rsbrodie50, I am also trying to write an app that will use a wifi device.
 The device in question uses adhoc wifi.  There is an app available for the iPhone to
work with this device.  I know there are android users who want to use similar
devices.  I would also like to see an updated status from the Engineers.

[Comment deleted]

limassol, thats windows 7, not Android. Windows and Windows Mobile already has decent
support for ad hoc networking, as has already been pointed out. Android don't, and
that's what we are requesting.
Also, IPhones can connect to an ad hoc network, such as a laptop in ad hoc mode, but
can not set up the network itself.

I have composed two new patches to handle some of the issues requested here.  The
patches can be applied to the master branch.  If anyone uses them, please let me know
how they work and what needs to be accounted for so that I can improve the
functionality.  The patches are as follows:

Adhoc Connection Changes:
https://review.source.android.com/13291

Changes to Settings App:
https://review.source.android.com/13292

Drew, I appreciate your efforts in creating these patches!  For me, accessing an
adhoc networking programmatically is all that I need to communicate with the device
for which I want to develop an app.  In fact, I would prefer it that way so as not to
require the user to have to go to Settings to connect to the device.  That is a
requirement on the iPhone, but I think it would be more user friendly to be able to
handle it programmatically.  The device uses a static IP so that is not an issue for me.

While I understand, I should be able to accomplish this by rooting the phone, I
certainly prefer not to and since I’m trying to develop a sellable app, I can’t
imagine that would go over well with people wanting to use the app.

Forgive my ignorance, but are the patches something I can apply to the SDK myself
(assuming that’s where they belong) to test this out or do I have to wait for someone
at Google to apply these.

Can someone at Google provide some information about this, please?  I would be
interested in helping to test this.  I’ve already invested in the hardware to develop
this app and now I’m stuck with having spent the money for nothing as well as it’s
preventing me from potential income from the app.  It never occurred to me that
Android would not support the device.  There are already 3 iPhone apps that support
this device and there is definitely an interest to have an Android version.

rsbrodie50,

If you want to access Adhoc wifi programmatically, you will need to apply patch
13291.  The Settings App changes are not necessary to access the functionality via
other programs.  However, you cannot just apply this patch to the SDK.  You have to
apply the patch to the open source OS master branch and recompile the OS.  After
doing so, you can flash the OS onto your devices and use the new functionality.  My
hope is that after review and tweaking, these patches can be applied to the OS in a
released version so that it is available to everyone and not just those who can
compile the OS themselves.

I hope that helps.
- Drew

Drew,

Thank you for doing this so quickly.  Is there any way for us to track the status of
this?  Specifically, how will we know if these patches are going to be applied in a
release?

Thanks!

mfmjos,

You can track the status of the tickets during the review process through the links I provided before.  Updates
will be placed there if/when google engineers review the tickets.  This will also tell you when they get merged
into the open source branch.  Beyond that, I don't know of a good way to tell if a specific android device
release will carry the changes.  I will also try to update this ticket if I make any changes to the patches or hear
any news on the topic.

- Drew

Thanks for coming back with more patches, Drew!  Have you tested them?  On real
hardware?  Is an image available for testing, e.g based on http://www.cyanogenmod.com/

nealmcb,

The patches were testing using ADP1 devices.  I don't have an image built, but you can build one yourself
following the instructions for building/installing for the ADP1 on source.android.com.

- Drew

Drew,

Should these patches be able to run on the ADP2 as well? (I'm trying to decide if I should buy an ADP.)  Also, any
ideas on how we communicate with and/or encourage Google engineers to review and implement the patches?  I
would love to develop an app that communicates with a particular adhoc wifi device, but it would be necessary
for your patches to be released for the publishing of the app to be feasible.  Thanks.

Bob

i hope the process could be more effective, because a lot of people are counting on
it!

rsbrodie50,

I don't see why the patches wouldn't work for the ADP2.  There aren't any hardware specific changes that should
cause it to not work.  I assume since the ADP1 supports adhoc wifi on the chipset and wifi driver, that ADP2
would also support that feature.  If so, the usage should be the same.

- Drew

this is great and all but i can't afford to root my phone and flash images onto it.
is there a way i can access adhoc networks? T-Mobile voids your warrentee on the
phone and if it fails i need that warentee

Connectifyme IT IS REALLY COOL PROGRAM !!! I tried everything to connect my nexus one
to my laptop, but wlan card does not support access point mode, but nexus one does not
allow connect to AD-HOC. Connectifyme create an access point at my laptop and nexus one
can connect to it.

Thanx developer!

Hi Drew,
     Thanks for providing the patch for the Ad Hoc mode setting. I am trying out the
patch ( 13291 && 13292 )with my mobile phone. I need a clarification for the same in
setting the phone in Ad Hoc programmatically. After I boot the mobile phone,I try to
get into Ad-hoc mode through the following steps. 1. "iwconfig <interface> mode
ad-hoc" 2. "iwconfig <interface> essid <ssid_name>". 3. "iwconfig <interface> channel
<channel_number>" 4. "ifconfig <interface> <IP_ADDR>.
         The other way is through GUI APP where we prompt for the User to set these
values. I tried out the patch. But there was no prompt as such in
Settings->Wifi_sub_menu. Is my understanding right??

Regards,
Arjun

Hi Arjun,

The patches don't require you to make any changes using iwconfig.  The patches work in the following way(s):

1) When an adhoc signal is in range, you will see it in the signals list in the Wifi Settings.  All you have to do to
connect is select the signal and it will connect to the signal.  The WifiConfiguration for the signal will be
marked as adhoc, but the Settings App will not show any signal as adhoc (nor do I have it configured to allow
you to create an adhoc signal that doesn't exist, that has to be done programmatically).

2) To programmatically start an adhoc connection, you must create a WifiConfiguration object, set it's adhoc
property to true, use WifiService to save & enable the signal, then set the WifiService adhoc mode to true
(otherwise it won't set AP_SCAN=2 and can't connect).  The final step is to call WifiService.reconnect() and
other devices will now see and be able to connect to your adhoc signal.  One thing to note though, if you are
the originator of the adhoc signal, you won't show up as connected until another device connects to you.  This
is because you are technically not connected to anything without another node.  Also, no device is running
DHCP server, your device will disconnect because it fails to obtain an IP Address.  The way around this is to set
a static IP address either programmatically or via the Wifi Settings App.  Set the DNS to a reachable address
and the connection will stay.

Also, if anyone has any good ideas for solving some of the caveats I mentioned in this post, please let me
know and I will make changes to the patches to the best of my ability.

- Drew

Hello,

I would like to try out Drew's two patches (13291 & 13292).  I was wondering if one
of you could help me out with my approach.  I would prefer to focus my attention on
application development using the SDK, rather than modifying the SDK, but I would
really like to test adhoc mode support in a wifi application that I have.  I have
setup a Ubuntu system, downloaded the tools for getting and building the Android
source, performed a repo sync, and performed a make.  How do I add the patch files to
the baseline that I downloaded?  Do I simply issue the repo/git commands referenced
on the patch pages?  If anyone has gone through this procedure and could help me out,
I would really appreciate it.

Thank you much!

Dan

So guys, is here any chance to get this functionality without rooting|hacking device?
What actually means  status "Received", was it assigned to somebody, is it in
progress now? The milestones?
What's the official position of Google Android team about that problem?

Eventually the device costs over 500 bucks and totally internet oriented!

A lot of question, i know, but i didn't find answers reading posts...
Regards,
AG

AG,

I am wondering the same thing.  I am trying to figure out if I can test this
functionality with rooting the device.  I have pulled the Eclair branch, applied the
two patches that Drew checked in.  Now I am trying to find out if I can load the
patched baseline onto a Nexus One.  I can't seem to get an answer of the forums or
mailing lists as to whether this is possible or not.

Dan

I think the problem is that the developers simply don't have enough time to deal with
issues that don't get big publicity. Looking at the patches submitted for this issue
and the communication between patch-submitter and developers, either the submitter
didn't reply soon enough, or the developers didn't look at the patch quick enough, and
so when trying to apply the patch later it broke things. It's annoying, but that is
what we have to live with I suppose. Unless, of course, you spend enough time to get
commit rights for yourself and can integrate this sort of thing yourself :-).
A++

[Comment deleted]

Hi Drew,
      Thanks for the clarification. Now, Adhoc Mode works if there is a Adhoc signal
is in the range. About IP addressing, Static IP Address assignment through App ->
Advanced Setting should be sufficient. This is already exisiting and is a good
solution for Adhoc mode.
        But there is an issue referring to the point 2 provided in comment 64. Every
time I need to configure my laptop in Ad hoc mode, only then my mobile phone latches
on to the signal and displays the corresponding network in App. What if I need to
talk to another mobile? in this scenario it will not be possible as both the phones(
assuming they are Android mobiles and have the same fix) will be trying to latch on
to a Adhoc signal which is not existing. This is a popular Use Case which many people
go through where many don't use Laptops to get their mobile in Ad hoc mode.
         So, a better fix would be to enable a Adhoc signal programmatically and get
connected only when another mobile device is in the range. Let me know your comments.
     

Regards,
Arjun

Success!

I added the patches to sapphire and flashed my ADP2.  I programmatically created an
adhoc network using an application with the updated SDK.  I monitored the network and
saw the 802.11 probes being broadcasted with the SSID that I specified in the
WifiConfiguration.  While I am still testing the functionality, it appears that the
setting of the frequency in the WifiConfiguration is not changing the channel of the
network.  I have changed the frequency to channels 1-5 and I only see the channel
ultimately set to 11.  I'll keep testing the functionality, but so far it looks
great!  Now we need it approved into a release baseline!

Dan

Hi Dan,
     Could you please share us the patch you have made to programmatically create an
Adhoc network ??

Regards,
Arjun

Hi Drew,

   When will your patches release with the OTA update? I desire it and I really don't
want void the warranty by rooting my nexus one. Hope you can drive this feature to
public.

Thanks
Leo

Hi Drew,

   I have the same question with yhliao1977, Do you have a plan to public these two
patches? I do not want to void the warranty.

Thanks
Bluishssky

我认为这确实是一个问题
首先，Android在默认情况下无法自动搜索到Ad-Hoc类型的连接；
第二，如果通过修改配置文件以达到目的，方便性和安全性上暂且不提，它可能会造成无法连接某
些AP，在我的环境中是这样的；
第三，其似乎还不能支持带WEP和其他类型安全设置的Ad-Hoc连接，它的配置实在是有些繁琐。

所以，希望google能够在今后的FM版本中加入对Ad-Hoc无线网络的支持。

LeavesCoffee, 如果你用中文,大部分的人不會懂你的意思.在這裡請用英文.

This is a forum in english only! Please use english.

Hm, it would be handy if google translate worked on code.google.com like it does on
gmail. Here's what it says for LeavesCoffee's message:

-------------------------
I think this is a problem first of all, Android by default does not automatically
search for Ad-Hoc type connection;
Second, if by modifying the configuration file to achieve the purpose, convenience
and safety of the put aside, it may cause can not connect to certain AP, in my
environment is so;
Thirdly, its seems to not support with WEP and other types of security settings of
the Ad-Hoc connection, its configuration is somewhat cumbersome.

So I hope that google be able in future to add on the FM version of the Ad-Hoc
wireless network support.
--------------------


Is it true the patch doesn't support WEP over ad-hoc networks? That seems like a
valid complaint.

Sorry, ironically, forgot to translate my own. Translation: "If you use Chinese most
people won't understand. Please use English."

Hrnytd,
Its good to see your success using the patches.  The bug with frequency is one that I am seeing myself as well.  
I have set the frequency value and called (what I think is) the correct methods to have the frequency written
into the wpa_supplicant.conf.  However, when I check the file after the call, frequency is not written.  Because
of that, it defaults to channel 11 when running. I will keep you updated if I can track down the problem of why
it is not writing or saving the frequency value.

Arjun,
Glad to see you have had some success with the patches I provided.  Your problem of mobile devices not
broadcasting their Adhoc SSID for connection shouldn't be a problem if you correctly create the
WifiConfiguration object with Adhoc mode set, then save the configuration and call reconnect().  I have
successfully been connecting multiple phones together without using a laptop to initiate the signal.

yhliao1977, bluishssky -
I am not in control of when/if the patches I submitted are placed in an actual release build.  Once my patches
are submitted, I have to wait for google to respond with accept/deny/change requests for those patches.  I'll
do my best to address any requirements google might have for those patches once they have reviewed them.

Lets keep up this discussion!  The more we work and test things, the more likely Google will review these
patches and we can all have Adhoc functionality.

- Drew

You are doing a great job. I hope this patches get included into the official Nexus One
software in the next OTA update. I really need this feature

To anyone following this and wanting it to get fixed, I suggest you search for an
appropriate android mailing list that one of the google devs write on (JBQ is
probably best) and ask when they will look at the fix. As I have mentioned, unless
you get a google dev to look at the fix in the near future, when they get around to
it it will no longer work with the code. So ask politely on an appropriate list and
one of the devs might look at it while it is still a good patch!
Cheers
Anton

@melser.anton,
Hi mate,
Can you advise of an Android mailing list to use as I would really like to mail a
dev about this. A specific link would be great.

Cheers,
Mark

Every day I get a little more disappointed by all the things this phone should be
able to do, but can't.  Connecting via Ad-hoc is just another one of those things.
Thanks to everyone working on this, I wish I could help.

If nexus provide adhoc mode, we can use it for academic use

adhoc is very important for travelers .....pls herry up "fix" this issue

Yes, adhoc is veeeeeeeery important function for me, which should be to save my
money, and improve the access internet speed in some locations, ASAP give us the FIX
pls, thx.

Yes, please add this in next fix.

i need adhoc

Instead of leaving pointless "me too :(" comments, just star (favorite) this issue
number (82). You will be notified by email of any updates to the situation, just like
I am. Those notifications, incidentally, include one for each pointless comment like
the last five before this one.

I second FlamingSpinach. By stars this issue ranks as 26th. By adding your star you
will help to raise the ranking of this issue. BTW even though there are twenty-five
issues with more stars, this issue is the oldest of them. Older than Arabic language
support and app storage on the SD card. -hgb

flamingspinach wrote:
>Instead of leaving pointless "me too :(" comments, just star (favorite) this issue
>number (82). You will be notified by email of any updates to the situation, just
like
>I am. Those notifications, incidentally, include one for each pointless comment like
>the last five before this one.

Adhoc is so essential, why it is still not supported on nexus one till now?

I'm using Nexus one and I need ad-hoc to share my laptop's internet for it

Ding Hui wrote:
> I'm using Nexus one and I need ad-hoc to share my laptop's internet for it

You don't need Ad Hoc wifi to do that. You can use the USB.

To tether your Android, visit:

http://www.softsailor.com/how-to/mobile-how-to/15567-3-simple-ways-to-tether-an-
android.html
http://mobile-stream.com/easytether/android.html

Please don't use this forum to discuss USB tethering. Take those questions elsewhere.

I would like to known the status of the Drew Jacobs's patches described in comment
#51

http://code.google.com/p/android/issues/detail?id=82#c51

asicwizard, You misunderstand the topic of this Issue. It's not tethering, instead,
it is sharing the laptop's internet to Nexus one.

Need support ad hoc networking.

Pls. support ad hoc

ding wugui

pls.....support ad hoc.......it's a VIP thing for me

Seems no progress on this issue. But it is very useful functionality. What is a pity
that the IPhone of my friend could work with my laptop, but my nexus one didn't.

Hope google can have patch on it very soon.

Thanks.

i'm looking forward to this function rolling out.

please add this standard features to Android ! and also publish an api to create and
configure (wep key, priority, ip configuration...) an adhoc network.

We want to add great apps on Android !

Thx in advance.

Franck

I need adhoc support for multiplayers game developpment...

please help

Thanks

when i used android 1.5, i hacked its tiwlan.ini and then i could share the internet
with my laptop.

but it failed with my android 2.1.

what a pity!!!

I need adhoc support for multiplayers game developpment...

please help

Thanks

非常有必要加入该功能！

I use tether with hero from wireless. My iPhone can get it and browser internet, but my
N1 could not find out the SSID. So I wish Google can release adhoc function.TKS

Thanks to Drew, Hrnytd and the discussions from many others in this thread, I have
successfully applied the patches and flashed my phones. Right now I am still testing
the ad hoc wifi functionality (in a programming way) between two phones.

My question is: is the multi-hop ad hoc mode also supported? In Drew's description,
it seems that first one phone creates an ad hoc network, then the other phones
connect to this network and talk to the network-creator directly. So they form a star
topology? Is the mesh mode supported here?

[Comment deleted]

ugly for the patch in the next update !

I need ad-hoc to share my laptop's internet

I need ad-hoc to share my laptop's internet too

hope i can use this function with next nexus one update.

hope i can use this function with next nexus one update too

I think the adhoc is very usefull, please add this function to Android.

PLease Add Adhoc Mode!!!
I need it!!

[Comment deleted]

iPhone has had this ability for nearly 3 years, since it was first released. Winmo
has had it for some time now, too.

Why is this one issue such a problem for Android? It seems like such a minor issue,
and a selling point (or non-selling point) for a lot of users.

What exactly is the hold up? Can't one engineer spend one day on this? Why should
users be spending a year and a half hacking their way through this, when someone at
Google surely know sthe fix?!

GOOGLE, WAKE UP

cheers ;)

when will be ad hoc mode...thanks

i guess they don't care..!

i hope nexus one will support wifi ad hoc

need it so much!!!

need it now! it is very important!!!

need it now! it is very important!!!

[Comment deleted]

I was provided with this link
http://blog.joint.net/2009/07/connecting-android-phone-through-adhoc.html

seems to be possible to modify two files and from there to connect to adhoc networks

Business traveler here with the same issue. Just provide the fix asap, please. Flood of
messages should be annoying enough for any responsible Google engineer. Just get it
done or provide another feasible workaround.

hope i can use this function with next nexus one update.

27 Months and still no go! What is going on Google??

Was expecting this to be available. 27 months.....

hope i can use this function with next nexus one update too

I have a data contract with gigabytes of allowance a month, yet I can't use my Nexus as a Bluetooth
modem or wireless router. This just sucks, my N95 is better connected in this regard

hope i can use this function with next nexus one update too

I am so embarrassed! I buy a Nexus 1 and rant on all my iphone groupie friends about
the glories of open-source. Then I find out you can't copy and paste from an email or
use ad-hoc networking unless you HACK YOUR OWN PHONE!
I'm so embarrassed.

I would hate to root my N1 to be able to share my 3G internet connection with my
laptop on the go (over WiFi). Looking forward for it on the next Android update.

Ad hoc Wifi: what's really missing is the ability to disciver and connect to
existing ad-hoc Wifi networks...

This would allow reverse tethering - using wired connection of the laptop though
ad-hoc wifi network.

I also need ad hoc wifi connexion for professional reasons, as well as support for
wifi proxy. This exists on other phones...

I need ad hoc wifi connection just like other phones

As Adhoc is part of 802.11 this should be also done on Android properly.

Please add ad-hoc to release!

Come on, Google, this is pathetic. It's not like Linux can't handle an ad-hoc network
connection. I have a tablet which can run Android, but Android can't tether via my
cellphone with Bluetooth or ad-hoc wifi; how the heck am I meant to get it online?
Sheesh.

Please!Please!Please! add ad-hoc to release

This bug is a eternal, and looks more like a business bug.

Oh, I think it's bad. I don't want to root my phone.
Ad hoc network connection is useful and avoid users to spend a lot of money.
If many people ask for, there could be a reason.
So, what about this ?
This issue is like a neverending story, as I can read.
Google can you kindly tell us if you are interesting in solve it ?

I have just received my Nexus One and am SHOCKED that it won't support ad-hoc
networks!!! What!!?

Come on Google, this is insane, you've crippled my phone!

Anyway, I came here to see if there was any progress and it seems there are people
who have been asking for this for over two years! How can it take two years to change
a few lines of code?

I have been using Nokias for ages, and they suck, but at least I can connect it to my
ad-hoc network. I was really looking forward to getting this Nexus and thought Google
would do a great job, but like I said, they seem to think it wise to cripple the
phone! I'm baffled.

Luckily, I have a seven day cooling off period and the Nexus is already in the mail
being returned for a refund, I am not prepared to wait another two years to get, what
is a very, very basic and standard facility.

I can't tell you how disappointed I am with Google, now where's that N97?

:( :( :(

need support for connecting to ad-hoc networks.  just like everyone else.

Seriously, this is a simple request; I guess rooting my phone is going to be the only
option.

gogogo

also confused why this isn't in yet - ad hoc should be an option

I really don't understand why they haven't added it yet. I have a couple of apps that
use the ad hoc mode, and it works really well. But, I need to be root activate it,
and thats the ONLY reason i rooted the phone. Doesnt make any sense. I also have apps
for IPhone, Symbian, Windows Mobile etc and there ad hoc works. Come on Google, what
are you doing?

It seems we will finally have ad hoc available in the upcoming 2.2 release!
http://www.theinquirer.net/inquirer/news/1636745/android-includes-tethering-wifi-hotspot-creation

lanilsson: well, I hope so. But note that the 2.2 announcements only deal with it
*the other way around*: the Android device creating the ad-hoc network, rather than
connecting to an ad-hoc network created by another device. You'd hope both would
work, but you never know...

There are other use scenarios that would greatly benefit Ad-Hoc capabilities.  One of
which is the possible development of an app to interface with this device.

http://www.innovatemotorsports.com/products/ot2.php

According to the developers of this product, it uses Ad-Hoc network abilities only
and is the reason why they currently only support Iphones and Ipod Touchs and not the
Android OS... this was a deal breaker for me.

this is so frustrating...

Just tried connecting to an ad-hoc network with 2.2; didn't work :-|

Beyond ad hoc, clustering technology can be enabling. Clustering can allow for many very useful and
interesting apps.

What happen if I rooted the nexus one? No void in software update or maintenance by HTC
, right?

wow no ad-hoc network support for 2.2?? It makes no sense why something this simple wasn't added.

oh...2.2 still can't support ad-hoc WIFI?
This is a frustrating result...

Please add this simple feature.
Thanks

I went bought a wireless card (that supports adhoc) for my home PC to allow my nexus
one to wirelessly connect and i cant.. How annoying.
Im running froyo, and although tethering is available - i want reverse tethering!

I need reverse tethering too.

i just want a goddamn cookie

Has anyone figured out how to enable connecting to an ad hoc network on 2.2?

Please enable ad-hoc wifi connections!!

http://www.wissamidrissi.com/2010/02/how-to-connect-android-phone-to-your-ad.html

got this. Everything looks OK, but when I'm trying to connect, connection fails
during IP retrieving. Any idea?

gotcha! I've set IP and it's work!
like here:
http://static.commentcamarche.net/en.kioskea.net/pictures/configuration-reseau-images-proprietes-protocole-internet-general.png

for My HTC HERO IP is 192.168.0.3
I'm working on a remote Windows control application, so it's useful for me.

orkru666: You need to ROOT your phone to do that. That solution has been known
forever, and is not a workable solution for the standard user.

No ad hoc networking in 2.2? BAD Google. Isn't tethering using the ad hoc mode?

Anyway, the patch set by Drew Jacobs that add these features to the source tree was
rejected by Google on the grounds that it was conflicting by their internal ad hoc
implementation. That means that the google internal tree has these features in the
pipe, and we should at least eventually receive these features.

I was hopeful about 2.2 as well.  This is a another disappointment.  The comment on
the patch that Drew Jabobs submitted states: "We have an ongoing internal ad hoc
implementation that will conflict with this patch."  They are looking at the patch.
Are they looking at this issue?  I see that it is moving up in rank.  Perhaps Irfan
Sheriff could chime in to let us know if there is a plan to enable the internal ad
hoc implementation.  

Really surprised to see this thread, been working on my motodroid for weeks, rooted and
followed those common guide(even stated in here) and glad to see I'm alone, just ONE
more VOTE from me, please implement this feature... soon, or maybe a third party
developer should make this and it'll probably become one of the most popular apps in
the android market... if they let you... like the guy who made wifi analyzer here
http://sites.google.com/site/farproc/wifi-analyzer what he said about the future about
his app to be able to connect to ad hoc... if anyone who make this first, he'll
probabaly be famous....

penthoy: You can not write an app that modifies system settings without using the
official APIs. The official APIs do not currently have the option to set the device
hardware into ad hoc mode. This is what we are asking for here. In order to write an
app that puts you into ad hoc mode, you need to be ROOT. Its very very easy, but
again, you need to be ROOT. I have two apps that do just that, and there are several
other apps out there for you.