Running MANET Manager on Galaxy S III or other ideal device

[sjoer...@gmail.com]

Hi everyone,

For a school project me and my fellow student need to figure out how we can use a MANET in emergency situations. To test the MANET Manager app, we are provided with two Samsung Galaxy SIII devices (model for the Netherlands). Somewhere else we read that for the Samsung Galaxy S III we need to recompile the kernel for a country-specific devices. While we rooted our phones and installed CyanogenMod 10.1, we still can't run the MANET Manager (ad-hoc mode not running- toast is displayed). We are not that much of UNIX nerds so we can't figure out how to recompile the kernel for our specific device.

What we tried:

- Custom kernel from the Manet Github downloaded for Samsung Galaxy S III
- Unmkbootimg this kernel so we can use the ramdisk from our device
- Take the ramdisk from our device
- mkbootimg with zImage from downloaded kernel + ramdisk from our device

After flashing this new bootimage, our device won't boot. We won't see the CyanogenMod screen.

Are we missing some steps? Can you explain us how to compile our own kernel, and some steps to get the ramdisk from our device, to see if we did the right thing???

Because it's a school project, we also have the possibility to buy some new devices. Do you recommend any devices that are able to run the MANET Manager when rooted, not with a specific built kernel?

Thanks for any replies,

Sjoerd

[Jeffrey Robble]

Hi Sjoerd,

Here's a list of supported devices:

- Samsung Galaxy Tab 10.1

- Samsung Galaxy S II Epic Touch 4G SPH-D710

- Samsung Galaxy Nexus SCH-I515 (custom kernel)

- Samsung Galaxy S III GT-I9300 I9300UBDLJ1 (Latin American countries) (custom kernel)

- Samsung Galaxy S III GT-I9300 I9300XXBLH1 (Nordic countries) (custom kernel)

- ASUS Transformer Prime TF201 (custom kernel)

- ASUS Nexus 7 (custom kernel)

Most modern devices require a custom kernel, but if you don't want to mess with kernel stuff then buy a few Samsung Galaxy S II Epic Touch 4G SPH-D710 phones. They're old and should be cheap.

Did you try wiping the cache partition and dalvik cache through ClockworkMod recovery after installing your new kernel on the Galaxy S III? I assume you're trying to use this kernel:

https://github.com/monk-dot/SPAN/tree/master/kernels/Samsung%20Galaxy%20S%20III%20GT-I9300/CyanogenMod%2010

Make sure you have the full CyanogenMod 10.1 ROM installed (not a newer version) before you flash the above kernel. It might work even without messing with the ramdisk stuff.

- 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.

[Macy Cronkrite]

Can you go into more detail on what a custom kernel for a new device would entail?

I want to use HTC or Motorola - but not sure what is involved to create support for that.

e.g. custom kernel?

thx

-macy

[Jeffrey Robble]

Hi Macy,

At the moment we only support Broadcom wi-fi chips. I know that some Motorola devices (like the Razr Maxx) use a TI wi-fi chip. Some device use Qualcomm or Murata wi-fi chips.

Android is lagging behind Linux and thus has limited support for the new nl80211 wireless API. Instead most Android devices should use the Wireless Extensions (wext) API. If it's not already included in the kernel, you will need to compile the kernel with CONFIG_WIRELESS_EXT (which may require you to enable other options through menuconfig depending on how the dependancies for your device are related to one another).

Refer to this thread:

https://groups.google.com/forum/#!msg/spandev/oCtyKHE1G3s/R-mINca-4cEJ

We also needed to enable ad-hoc support in the Broadcom driver by making these changes:

https://github.com/ProjectSPAN/android_kernel_samsung_smdk4412/commit/8fa45142b269a6c0870083846c045f02abad869f 

I'm not sure what would be required to enable ad-hoc support on non-Broadcom drivers.

- Jeff

[kendal...@gmail.com]

On Tuesday, October 1, 2013 at 5:28:44 AM UTC-4, Sjoerd van der Vis wrote:
> Hi everyone,
>
> For a school project me and my fellow student need to figure out how we can use a MANET in emergency situations. To test the MANET Manager app, we are provided with two Samsung Galaxy SIII devices (model for the Netherlands). Somewhere else we read that for the Samsung Galaxy S III we need to recompile the kernel for a country-specific devices. While we rooted our phones and installed CyanogenMod 10.1, we still can't run the MANET Manager (ad-hoc mode not running- toast is displayed). We are not that much of UNIX nerds so we can't figure out how to recompile the kernel for our specific device.
>
> What we tried:
>
> - Custom kernel from the Manet Github downloaded for Samsung Galaxy S III
> - Unmkbootimg this kernel so we can use the ramdisk from our device
> - Take the ramdisk from our device
> - mkbootimg with zImage from downloaded kernel + ramdisk from our device
>
> After flashing this new bootimage, our device won't boot. We won't see the CyanogenMod screen.
>
> Are we missing some steps? Can you explain us how to compile our own kernel, and some steps to get the ramdisk from our device, to see if we did the right thing???
>
>
>

> Thanks for any replies,
>
> Sjoerd

I am in a similar situation, except Samsung Galaxy S3, US Cricket version, SCH530c. I have updated the software to CM11 2015 and tried MANET Manager and Serval without success. I wonder if I need to replace the wpa_supplicant.conf file with a modified one to get the ad hoc wifi network. any help appreciated.