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 :-(

In what way would it go against fcc regulations?
Trafficwise it would just be a large-scale Wi-Fi LAN wouldnt it?

Just this year there will be probably a Google Summer of Code project dealing with
adding a simple GUI for OLSR mesh protocol which would enable meshing of Android
phones in community wireless networks using OLSR:

http://wiki.freifunk.net/Ideas#Android_OLSR_GUI

But it will require a rooted phone. It would be great if it would be possible to use
ad-hoc mode, configure IPs and change routes officially.

http://www.engadget.com/2010/07/24/adobe-air-peer-to-peer-video-call-concept-android-app-hands-on/ Adobe has shown this concept using AIR and without 802.11s

Can we do it without AIR & 802.11s ?

@narendra.sisodiya P2P != mesh. You'd still need underlying IP connectivity for that AIR app to work. OLSR, 802.11s, or some other L2 routing algorithm is still needed.

@pacobell - OLSR has been ported to Android.

@csboyd07 Has olsrd been pushed upstream to the android codebase yet? Froyo integration?

We have been trying to reach Android team about OLSR integration, but without success.

There is now a GSoC project trying to bring mesh to Android:

http://wlan-lj.net/wiki/Podrobnosti/MeshApp

Yeah, I'd seen that project sometime this week. It looks promising, but I have my doubts it'll work without root. Also, being a proactive protocol, it may not be suitable for mobile devices that are CPU and energy constrained. The RA-AODV protocol that 802.11s uses would probably be a better fit in this case. Unfortunately, I don't think the IEEE has even reached a reference draft standard yet, so Google may be hesitant to pull the trigger on that just yet.

Yes. It requires root. And yes, it drains the battery in four-five hours. But this is also the problem of WiFi itself not really suitable for mobile phones. There is no much difference with power consumption of being connected to the WiFi AP and using the phone for browsing or being connected to the mesh. But yes, it would be great if you would be just able to leave mesh mode on and thus contribute to the mesh as you move around.

I would be very interesssted in wireless mesh networking as defined by 802.11s as i need a mesh-enabled mobile for my research work. We do research on wlan localization techniques here in our rsearch group and one of our approaches is a cooperative localization using wlan mesh networks.

I reiterate this for the G2. As we contemplate the likely upcoming global economic collapse, we need an alternative to the backbones for communications. We need a wireless internet of portable nodes. See http://constitution.org/wipnet/wipnet.htm

@22 I found a workaround: http://en.wikipedia.org/wiki/Amateur_radio

Ham radio is of course the old alternative for emergency communications, but it is insufficient for reliable data communications among multiple parties spread over the continent. The military has found it to be far superior to walkie-talkies, enabling every soldier with a laptop to share combat intelligence with one another in real time, to find or avoid enemies, acquire targets while minimizing collateral damage, assess situations, find IEDs, and move wounded. Civilians need similar capabilities.

google already invests in a Mesh style AP company. http://meraki.com  Having them add this ability to the phone would be AWESOME. Think about it, your in a location where WiFi or Cell Infrastructure is damaged or non existent or you and team need a private network to be on at some location. This would allow you to stay in data communication sharing media/chat/P2Talk. Combine it with GPS Google maps a team could each member have a phone on them and they could track each other down. Someone goes missing? Don't worry their current/last location/path was logged by his peers on the mesh network. Need support but can't describe where or what your seeing? record photos/video/P2Talk with gps tag, it goes out on the mesh and all your peers will see it, then their peers.

See also MeshApp at http://wlan-lj.net/wiki/Podrobnosti/MeshApp

Check out hsmm-mesh.org

KD5MFW

The recent events in Egypt and the re-introduction of the "Protecting Cyberspace as a National Asset Act" has added new urgency to this issue. Android should offer mesh networking ASAP along with OS agnostic applications that may act as anchor nodes for the mesh.

Portable wifi LAN and eventually population-wide mesh networks are where the internet has to go to survive.  Net neutrality regulation is unlikely to be enough to prevent abuse by big telcos, and many are already predicting the Splinternet.  Adding this support will put phones at the forefront of the next wave of internet development.

802.11s has officially been ratified! o11s is currently working on the HT bits, but it's pretty much ready to go, from what I've read. This technology is going to enable a whole new class of mobile interaction the like of which we can only imagine!

http://standards.ieee.org/news/2011/80211s.html

Of just around 20 nodes. :-(

Ad-hoc + support for custom routing daemons would be much better.

There is another app for this in the works: http://www.networkworld.com/community/blog/android-phones-are-connecting-without-carrier-networks

So we have at least three project working on this:
SPAN: https://groups.google.com/forum/#!forum/spandev
Serval: http://www.servalproject.org
Guardian-Commotion: https://guardianproject.info

most solutions at the moment are based on custom kernels (supplying wireless extension capabilities) and rooted devices (to be able to actually use binaries like iwconfig to activate ad-hoc on supported wlan-chipsets)...
thus it would be nice if Google (or device manufacturers who supply/use their own kernel) would incorporate those patches/fixes within their own releases

[Comment deleted]

[Comment deleted]