Supported Devices

[stoker]

We haven't tested on any of the following Android devices:

- HTC EVO 4G LTE (3rd gen evo) - Sprint

- HTC EVO 4G (1st gen evo) - Sprint

- LG Optimus L3670 - Sprint

- Samsung Dart SGH-T499 - Tmobile

- Asus EEPad Transformer TF101 (1st generation Transformer)

 But I did some research online.

- I couldn't find a hardware teardown for the Samsung Dart SGH-T499 or LG Optimus L3670.

- The Asus EEPad Transformer TF101 seems to use a Murata wireless chip. I don't have any familiarity with it.

- The HTC EVO 4G LTE uses the Qualcomm WCN3660 wireless chip. I don't have any familiarity with it.

- The HTC EVO 4G uses the Broadcom BCM4329 wireless chip according to this teardown: http://www.ifixit.com/Teardown/HTC-Evo-4G-Teardown/2979/2

We have had great success with the BCM4329, so out of the above devices I recommend using the HTC EVO 4G. You will need to ensure it's rooted and that the kernel has wireless extensions (wext) support. The easiest way to do that is to try using the iwconfig binary. If it fails, you will need to recompile the kernel with wext support. We can help you with that.

In the following edify script we check the device type before configuring it for ad-hoc mode: https://github.com/monk-dot/android-manet-service/blob/master/AndroidManetService/res/raw/adhoc_edify

You will most likely need to add the HTC EVO 4G to the conditional check along with the other devices we support: Samsung Galaxy Tab 10.1, Samsung Galaxy Nexus, ASUS Transformer Prime, Samsung Galaxy S II 4G Epic Touch. 

If you want to buy a device, I recommend the Samsung Galaxy Nexus but the Samsung Galaxy S II 4G Epic Touch works very well and you might be able to buy one for cheap.

[Jeremiah Alfrey]

how about the Samsung Galaxy Tab 2 (tablet)? I can get them off of google for $158 each. 

[stoker]

We haven't tested the Samsung Galaxy Tab 2, but according to the following teardown it uses the Broadcom BCM4330 wireless chip: http://www.techrepublic.com/blog/cracking-open/galaxy-tab-2-70-teardown-reveals-efficient-hardware-layout-and-replaceable-battery/575 

We've had a lot of success with the BCM4330.

[Jeremiah Alfrey]

It looks like toys-R-us is coming out with $150 table called Tabeo

http://www.toysrus.com/product/index.jsp?productId=13265885

Would be cool if it would run the mesh. 

[m0nk]

Cool!

m0nk

------------------------------

Sent from ...

--
 
 

[co...@servalproject.org]

Hi,

I'm currently working on a project where I need to form a mesh of 10 - 20 of these devices.

I'm hopeful from your post that I can get ad hoc wifi enabled on the device. If I understand the other posts in this group correctly I'll need to recompile the Android kernel for the device.

For a variety of reasons I'm using CyanogenMod 9.1 with this device:

http://wiki.cyanogenmod.org/index.php?title=P3110_Info

It appears that the Kernel source is available online.

So with this in mind, what would I need to do to compile a kernel that enabled ad hoc WiFi.

I've been developing Android apps for a while now, but I've never compiled a Linux Kernel, let alone an Android Kernel so simple instructions / places to look would be very welcome.

With thanks.

-Corey

[m0nk]

The source.android.com site has a great tutorial on kernel builds.

Also, I thought the cyanogen mod site had a step by step walk through.
Let me/us know if we can help!

m0nk

------------------------------
Sent from ...

> --
>
>

[Corey Wallis]

Hi,

Thanks for the reply.

I'll take a look at the tutorials tomorrow.

I'm assuming that not only do I need to build the kernel I need to
modify it in some way to enable ad hoc wifi. After all, if the stock
CyanogenMod rom kernel worked I wouldn't need to recompile.

With this in mind, what changes do I need to make, or what do I need
to look for in order to help work out the changes that are needed.

With thanks.

-Corey

> --
>
>

[stoker]

Hi Corey,

Take a look at the second post in this thread:

https://groups.google.com/forum/#!search/NL80211_IFTYPE_ADHOC/spandev/q_K7ELMTnjg/q44GfsCA51IJ

You'll know it's the right post if it has "NL80211_IFTYPE_ADHOC" in it. 

- stoker

[coug...@gmail.com]

Any way to proof the app working without any friends?
I broadcasted to myself successfully.

My Phone:
HTC Desire-Z/G2/vision
Cyanogenmod (7 not so fresh nightly)

cheers and cool app!

[stoker]

Hmm trying it out on multiple phones would be best if you have more than one.

If your phone is truly in ad-hoc mode the SSID should show up as a wireless "ad-hoc" / "device" network in Mac or Windows (maybe Linux too). I know that on a Mac you can connect to the "device" network, assign yourself a static IP address in the same subnet, and ping the phone. Note that the phone won't recognize the Mac as a node on the network (in Routing Info or the Visualizer app) unless it's also running the OLSR routing protocol. You can get the OLSR Windows / Mac clients here: http://www.olsr.org/?q=download

- stoker

[magnusw...@gmail.com]

Hi
Is there any of the newer HTC phones you can recommend trying? Or any other device other than Samsung that somebody have been successful with?

Regards
Magnus

[Jeffrey Robble]

Hi Magnus,

We haven't done any SPAN development HTC phones at this time, so I
can't recommend one. Other than Samsung, we have got SPAN running on
an ASUS Transformer Prime TF201. It might work on never versions of
that tablet or possibly ASUS phones, like the PadPhone, but I can't
make any guarantees.

- stoker

> --
> You received this message because you are subscribed to the Google Groups "Smart Phone Ad-Hoc Networks" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to spandev+u...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

[eug.s...@gmail.com]

On Friday, February 15, 2013 6:00:22 PM UTC-5, stoker wrote:

> If your phone is truly in ad-hoc mode the SSID should show up as a wireless "ad-hoc" / "device" network in Mac or Windows (maybe Linux too).

Using my LG P-999 (cyanogen mod 7.1.0-RC1-G2x) running "iwlist scanning" under Linux reports:

ESSID:"AndroidAdhoc"
Mode:Ad-Hoc

Yes, it shows up under Linux.

One complaint I have seen in the Play Market is the message "Adhoc not running". The only way I fixed this for myself was randomly setting the Wireless Interface setting to wlan0.

Any thoughts on adding the batman-ng routing protocol? I'd love to be able to share my data connection through an Open-Mesh router network.

[Jeffrey Robble]

Yeah, we don't officially support the LG P-999 at this time, but I'm glad it works for you on that devices. The app has a hardcoded map of device models to wireless interfaces. LG P-999 isn't in the list, so it makes sense you had to select the correct wireless interface manually.

We have many things on our TODO list. One of them is adding support for more routing protocols, like batman-ng. SPAN currently runs the OLSR protocol, so you could set up a mesh of DD-WRT routers and share your connection that way: http://www.dd-wrt.com/wiki/index.php/Mesh_Networking_with_OLSR

- stoker

[Eugene Smiley]

On Wednesday, May 1, 2013 9:40:01 AM UTC-4, stoker wrote:

Yeah, we don't officially support the LG P-999 at this time, but I'm glad it works for you on that devices. The app has a hardcoded map of device models to wireless interfaces. LG P-999 isn't in the list, so it makes sense you had to select the correct wireless interface manually.

It might be good to mention somewhere that one might need to make some "adjustments" and ask them to send an email when they find a working setup. This would fix all those negative reviews in the market.

[Jeffrey Robble]

Sure. I added a troubleshooting section to the Manet Manager description on Google Play. It probably won't show up until tomorrow. 

--

[bill...@gmail.com]

Hey Stoker, are there plans to support the new LG Nexus 4 devices?

Otherwise could you point me to a Nexus 4 kernel with wireless extension support?

Thanks!
Billy

[Jeffrey Robble]

Hi Billy,

We have a Nexus 4 but haven't had much time to test SPAN on it. I don't know if the stock Nexus 4 supports wext, but it's easy to find out. Install the Manet Manager on it, "adb shell" into it, run the "su" command, and then run "/data/data/org.span/bin/iwconfig". What output do you get?

Even if wext is supported, the wifi kernel driver may need to be modified to support ad-hoc mode. Thus, a custom ROM may still be required.

- stoker

[Eric de Vries]

hi there,
if I'm not mistaken you might want to get the latest nightly of cyanogenmod 10.1 for the Nexus 4, it should have been patched to support adhoc !!!
According to those pathces that is :
http://review.cyanogenmod.org/#/c/36123/

Op woensdag 8 mei 2013 16:13:13 UTC+2 schreef stoker het volgende:

[bill...@gmail.com]

Hey Stoker,

Thanks for the quick reply! I ran the iwconfig script and got the following output:

...

wlan0 Qcom:802.11n ESSID:off/any
Mode:Managed Frequency:2.412GHz Access Point: Not-Associated
Bit Rate: 0kb/s Tx-Power=0 dBm
RTS thr=2347 B Fragment thr=8000 B
Encryption key:off
...

p2p0 Qcom:802.11n ESSID:off/any
Mode:Managed Frequency:2.412GHz Access Point: Not-Associated
Bit Rate: 0kb/s Tx-Power=0 dBm
RTS thr=2347 B Fragment thr=8000 B
Encryption key:off


Each other interface had "no wireless extensions."

It might be worth noting that I selected wlan0 in the MANET Manager app when trying to get it to work yesterday. Trying p2p0 just now didn't work either.

I am able to send messages to myself, but I can't see the messages on the other Nexus 4 running MANET Manager configured with wlan0 or p2p0.

Furthermore I can't see the ad-hoc network on my Linux laptop.

I will try flashing to the latest nightly cyanogenmod like Eric de Vries mentioned while I wait for your response!

Thanks again,
Billy

[bill...@gmail.com]

Hey all,

I just wanted to confirm that the nightly build (2013-05-07) of cyanogenmod 10.1 [cm-10.1-20130507-NIGHTLY-mako.zip] enabled the MANET Manager to successfully start ad-hoc mode.

I am able to see the ad-hoc wireless network on both CM 10.1 Nexus 4 devices as well as my linux laptop! I ran the iwconfig script again and got the same output as mentioned earlier.

...now to figure out how to get an app running on top of MANET Manager.

[Jeffrey Robble]

Hi Billy,

That's great!

Since you saw output for wlan0, that means the Nexus 4 supports wext. I assume the problem was that the stock wifi driver didn't support ad-hoc mode, but the CM one does, as Eric mentioned.

- stoker

[Billy Hass]

The patch mentioned by Eric de Vries was only for the Broadcomm drivers. Therefore I'm still unable to connect Nexus 4's to ad-hoc wifi networks even though I can see them. 

Although iwconfig returns Qcom:802.11n, according to iFixit, the Nexus 4 uses a Murata SS2908001 802.11 a/b/g/n Wi‐Fi and Bluetooth module. 

I'll post back when I can connect to ad-hoc wifi networks with my Nexus 4.

[alan...@gmail.com]

how about htc desire 616???

[alan...@gmail.com]

how abt htc desire 616???

[nathan...@gmail.com]

Any chance this would work on an x86 version of android 4.4? I have a live cd around somewhere and was just wondering... thanx

[Jeffrey Robble]

It's not so much a matter of the underlying architecture as whether or not the kernel supports Wireless Extensions and ad-hoc mode.

On Tue, Jan 6, 2015 at 8:44 PM, <nathan...@gmail.com> wrote:

Any chance this would work on an x86 version of android 4.4? I have a live cd around somewhere and was just wondering...    thanx

--
You received this message because you are subscribed to the Google Groups "Smart Phone Ad-Hoc Networks" group.
To unsubscribe from this group and stop receiving emails from it, send an email to spandev+u...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[nathan...@gmail.com]

ok, so i have got an epic 4g touch- sph-d710 a galaxy s2-sgh-t989 and a tmobile g2x.. the g2x running cyanogen works with no problems, but with the 2 samsungs, i cant find anything that puts any of the steps in laymen's terms where i would be able to get manet manager working on them.. do you know of an easy step by step kernel how too, or even better a preconfigured kernel for these models that i could just download and get up and running?
Thanx for your time...

[Jeffrey Robble]

We haven’t posted instructions anywhere. The requirements are:

1. A rooted device.

2. A kernel that supports wireless extensions.

We have a pre-compiled kernel for the Samsung Galaxy S II Epic Touch 4G SPH-D710, but not the Samsung Galaxy S II SGH-T989. Here’s a link to the Samsung Galaxy S II Epic Touch 4G SPH-D710 ROM:

https://github.com/monk-dot/SPAN/blob/master/kernels/Samsung%20Galaxy%20Nexus/myupdate-galaxynexus.zip

You can install it using ClockworkMod Recovery. Note that I’ve only tested the kernel (Linux kernel 2.6.35) with Android 2.3.6 Gingerbread. Later versions of Android use a more recent Linux kernel. For example, Android Ice Cream Sandwich uses Linux kernel 3.0.1. That said, you should downgrade the Android OS to Gingerbread before installing our kernel, if you need to.

Here’s the procedure I used:

0. Downgrade to Android 2.3.6 Gingerbread. If you need help with this, let me know.

1. Install the pre-rooted Zedomax ROM (which includes ClockworkMod Recovery) from this site:

http://forum.xda-developers.com/showthread.php?t=1269437

You want “v2. CWM Recovery+Preroot+1.6OC” tar for ODIN link.

2. Install the Zedomax ROM via ODIN: 

http://forum.xda-developers.com/attachment.php?attachmentid=581913

3. Install “myupdate-galaxynexus.zip” via ClockworkMod Recovery.

[nathan...@gmail.com]

ok, so here is the problem i am running into... I have downloaded all the files you have provided links for, but i cant seem to find a gingerbread download. every one i come across gives me a 404 page not found.. is it too old/extinct? also what is the difference between el13 and el29. does it matter? not that i can find a working download for either, but would be nice to concentrate my search efforts on the right one.
Thanx again

[nathan...@gmail.com]

i have rolled back to android 2.3.6 build el29/. i followed your instructions but now when the phone turns on i get the yellow triangle with the exclamation point in it. it also says galaxy sII gt-I9000. when i try to connect to a wifi network it searches for the network but doesnt find it, and if i try to manually add the network it says it doesnt exist...

[stoker]

Below are some notes I left for myself a while ago. I hope they help you out. I uploaded the files you need here:

https://www.dropbox.com/s/qd0d60d3k8bk8gu/Odin3-v1.85.zip?dl=0

https://www.dropbox.com/s/tfzfdxzudbzknps/Epic%204g%20Touch%20Pit.pit?dl=0

https://www.dropbox.com/s/w500lh80iuwfz9n/SPH-D710_SPR_D710USEG30.zip?dl=0

https://www.dropbox.com/s/46ydj5gf0q9is6v/SPH-D710_Zedomax_EpicTouchKernel-v2.tar?dl=0

# UNBRICK / REVERT BACK TO GINGERBREAD

http://www.youtube.com/watch?v=h9rmJGlRKik

# ROOT ON WINDOWS

[http://forums.androidcentral.com/epic-4g-touch-rooting-roms-hacks/120624-kernel-zedomax-epic-touch-kernel-1-6ghz-oc-quadrant-4000-acs.html]

Download kernel tar file (v2. Stock Recovery+Preroot+1.6OC + CWM Recovery):

http://downloadandroidrom.com/file/Epic4GTouch/kernel/ZedomaxEpicTouchKernel/SPH-D710_Zedomax_EpicTouchKernel-v2.tar

[http://www.wowtechy.com/how-to-root-samsung-galaxy-s-2-sgsii-i9100-using-odin/]

Download Odin:

http://www.wowtechy.com/wp-content/uploads/android/Odin3-v1.85.zip

Power off device.

Restart and hold power + vol down until warning screen appears.

Press vol up.

Run Odin3 v1.85.exe.

Ensure there is a yellow "ID:COM" entry.

Click the "PDA" button and select SPH-D710_Zedomax_EpicTouchKernel-v2.tar.

Click "Start" button.

Device will reset. SuperUser.apk, su, busybox, and ClockworkMod recovery are now installed.

[percype...@gmail.com]

Hi Stoker

Seems Manet Manager works fine in Moto E (Android 4.4.2), but message forwarding is not working as expected.

I have set a mobile network using three moto E smartphones (A, B C) where every one is connected to each other except A and C (A<->B<->C). Routing information on each mobile looks fine, A and C select B as Multipoint Relay node ( forwarder ) for the nodes A and C. What is not clear for me yet, is then why a message sent from A is unable to reach C.

Is this something related with Moto-E only or I am missing something? Could you please point me where I am wrong?

Cheers

On Friday, August 10, 2012 at 4:15:30 AM UTC+1, stoker wrote:
> We haven't tested on any of the following Android devices:
>
>
>
> - HTC EVO 4G LTE (3rd gen evo) - Sprint
> - HTC EVO 4G (1st gen evo) - Sprint
> - LG Optimus L3670 - Sprint
> - Samsung Dart SGH-T499 - Tmobile
> - Asus EEPad Transformer TF101 (1st generation Transformer)
>
>
>  But I did some research online.
>
>
> - I couldn't find a hardware teardown for the Samsung Dart SGH-T499 or LG Optimus L3670.
> - The Asus EEPad Transformer TF101 seems to use a Murata wireless chip. I don't have any familiarity with it.
> - The HTC EVO 4G LTE uses the Qualcomm WCN3660 wireless chip. I don't have any familiarity with it.
> - The HTC EVO 4G uses the Broadcom BCM4329 wireless chip according to this teardown: http://www.ifixit.com/Teardown/HTC-Evo-4G-Teardown/2979/2
>
>
> We have had great success with the BCM4329, so out of the above devices I recommend using the HTC EVO 4G. You will need to ensure it's rooted and that the kernel has wireless extensions (wext) support. The easiest way to do that is to try using the iwconfig binary. If it fails, you will need to recompile the kernel with wext support. We can help you with that.
>
>
> In the following edify script we check the device type before configuring it for ad-hoc mode: https://github.com/monk-dot/android-manet-service/blob/master/AndroidManetService/res/raw/adhoc_edify
>
>
> You will most likely need to add the HTC EVO 4G to the conditional check along with the other devices we support: Samsung Galaxy Tab 10.1, Samsung Galaxy Nexus, ASUS Transformer Prime, Samsung Galaxy S II 4G Epic Touch. 
>
>

> If you want to buy a device, I recommend the Samsung Galaxy Nexus but the Samsung Galaxy S II 4G Epic Touch works very well and you might be able to buy one for cheap.

[percype...@gmail.com]

Hi

Forwarding is not done by Manet Manager, is OLSRd the one who manage it. I was trying to send message when my links were asymmetric. Last night I trace the data packets and found that links between nodes should be symmetric, this because the ack of the receiver. Please correct me if i am pointing to the wrong direction.

Anyway, now my 3 Moto-E config is working fine, it is a lot fun !

[moon...@gmail.com]

Hi I would like to ask if MANET MANAGER app work on Samsung s4 or not ?

[nathan...@gmail.com]

Will 2 mobile phone working on span network be able to utilize Byzantium nodes since they are both using the same protocol?

[ahmedq...@gmail.com]

I have Brava DM-993, android version 4.0.4, and I want to enable the ad-hoc mode of it. I have used a number of android applications like Barnacle Wireless, MANET Manager, Wi-Fi Tether etc. but I got no success so far.

Will you please help me, what should I do to enable the ad-hoc mode.