jadonk / jadonk/rowboat

wifi and 3g interface, and android-wifi-tether problems

Open
#125 0 comments 0 reactions 0 assignees View on GitHub
auto-migrated Priority-Medium Type-Defect
Dominant language
No language data
Stars
1
Forks
0
PR merge metrics
No merged PRs in 30d

Description

```
Hi, all
I port rowboat android 2.2, wifi driver and 3g driver to Beagleboard-xM
successfully.

Linux kernel version : 2.6.32

I have some problems:

1.
I first turn on the 3g, then the 3g will enable. After turning on the wifi, 3g
will disable. But 3g will not auto enable when wifi turn off.
What is the problem?

2.
The wifi and 3g interface can not coexist at the same time.
I want to turn on wifi and 3g at the same time and use netfilter to decide
output interface.
How can I keep wifi and 3g at the same time by modify the rowboat android 2.2
source code?

3.
I try to use the android-wifi-tether app on beagleboard-xM.
(1)Download the source code. (http://code.google.com/p/android-wifi-tether/)
(2)root beagleboard-xM. (http://forum.xda-developers.com/showthread.php?t=682828)
(3)compile and install the source code to beagleboard-xM successfully by eclipse IDE.
(4)run the app, then beagleboard-xM will crash after executing su -c /data/data/android.tether/bin/tether start 1

The last message is

Code: e15c0003 lafffe15 e3560000 0afffecc (e5963098)
---[ end trace 8e8064a261d61eb8 ]---
Kernel panic - not syncing: Fatal exception

I try to use the android-wifi-tether app on Google Nexus S and it is ok.

What is the problem?

4.
android-wifi-tether app resource are in android-wifi-tether-read-only\res\raw
the resource source code maybe in android-wifi-tether-read-only\native
How can I rebuild android-wifi-tether app resource?

Thanks!
```

Original issue reported on code.google.com by `kingrex...@gmail.com` on 18 Aug 2011 at 12:43

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the WiFi and 3G interface behavior on the Beagleboard-xM with the rowboat Android 2.2 and Linux 2.6.32 setup, then inspect the android-wifi-tether native and res/raw sources around the reported kernel panic. Done means the interfaces can coexist, 3G recovers after WiFi is disabled, tethering no longer panics, and the resource rebuild path is documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, linux
Domain
mobile-dev, networking, operating-systems
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.