3G USB modem support
Chih-Wei Huang
An experimental support of 3G USB modem has been pushed into
donut-x86 branch of the git server. Use repo sync to get it.
The tested 3G USB modem is Huawei E160.
Just plugin the USB modem, then you should see
the radio signal icon at top right corner becomes active.
Now you can use Messaging to send or recive short messages.
To test 3G internet connection, you have to use command line.
Use Terminal (or Alt-F1) to run "start ppp". Then use
"netcfg" to check if the connection is established.
Since it's an experimantal feature, some settings are hardcoded.
If your 3G modem is not the same as mime, you may
have to modify them by hand before building the iso:
* Driver for 3G USB modem is set to "option" module.
(in 0-auto-detect script, EXTMOD variable)
* 3G internet port is set to /dev/ttyUSB0
(in system/core/rootdir/etc/ppp/peers/gprs)
* 3G MMS port is set to /dev/ttyUSB1
(in vendor/asus/eeepc/init.rc, service ril-daemon)
Good luck and enjoy the new feature.
--
Chih-Wei
Android-x86 project
http://www.android-x86.org
Kjaergaard
Setup:
- eeepc 1005HA
- Huawei E180 with subscribion to the network provider "3" in Denmark
- android-x86 1.6r2 (and a corresponding build from the repository)
My experience so far is that I am missing the possibility to provide
the SIM PIN. I have however circumvented this problem by entering the
PIN by Ubuntu minicom and then boot into Android. When I then issue
start ppp and inspects the log I see the ppp PAP/CHAP exchange (see
log below), but it doesn't bring up the data connection fully. As the
PAP/CHAP exchange is running the basic kernel modules are loaded OK,
and the serial devices ttyUSB0 ttyUSB1 is running.
I can get a 3G connection from ubuntu 9.10 with the same hardware.
Could I have some help for the questions below it would ease my
trouble shooting.
1) I believe that the chat script in /etc/ppp/gprs-connect-chat need
to be modified to fit my 3G network provider. Correct ?
2) Is it possible to turn on some logging to see the initial AT
command handshake with the modem ? How ?
3) The menus won't allow me to enter an APN. Where should the APN name
occur ? In the initial AT handshake, or during the PPP
initialization ?
4) If I try to connect without entering the PIN prior to starting
Android I get the following fault:
[ 124.404330] rild[2590]: segfault at 4 ip 80b019e1 sp 100ffc34 error
4 in libreference-ril.so[80b00000+6000]
How can I locate this in the source ?
5) What are missing to be able to enter the PIN through the telephony
application ?
6) Are there any plans to move the 3G code to eclair ? Will there be
any obvious obstacles ? Some advice how I could do it myself ?
Jens Kristian Kjaergaard
================
I/pppd ( 2627): Serial connection established.
D/pppd ( 2627): using channel 1
D/vold ( 2382): [UEVENT] Sq: 2192 S: net A: 0 P: /devices/virtual/
net/ppp0
D/vold ( 2382): DEVPATH=/devices/virtual/net/ppp0
D/vold ( 2382): INTERFACE=ppp0
D/vold ( 2382): IFINDEX=5
D/vold ( 2382): No uevent handlers registered for 'net' subsystem
I/pppd ( 2627): Using interface ppp0
I/pppd ( 2627): Connect: ppp0 <--> /dev/ttyUSB0
D/pppd ( 2627): sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic
0x169420ca> <pcomp> <accomp>]
D/pppd ( 2627): rcvd [LCP ConfReq id=0x0 <mru 1440> <asyncmap 0x0>
<auth chap MD5> <magic 0x10e5e2a> <pcomp> <accomp>]
D/pppd ( 2627): sent [LCP ConfAck id=0x0 <mru 1440> <asyncmap 0x0>
<auth chap MD5> <magic 0x10e5e2a> <pcomp> <accomp>]
D/pppd ( 2627): rcvd [LCP ConfNak id=0x1 <mru 1440>]
D/pppd ( 2627): sent [LCP ConfReq id=0x2 <mru 1440> <asyncmap 0x0>
<magic 0x169420ca> <pcomp> <accomp>]
D/pppd ( 2627): rcvd [LCP ConfAck id=0x2 <mru 1440> <asyncmap 0x0>
<magic 0x169420ca> <pcomp> <accomp>]
D/pppd ( 2627): rcvd [LCP DiscReq id=0x1 magic=0x10e5e2a]
D/pppd ( 2627): rcvd [CHAP Challenge id=0x1
<6c36ed392a0a9004bc4d8b8cbab99c0d>, name = "UMTS_CHAP_SRVR"]
W/pppd ( 2627): Warning - secret file /etc/ppp/chap-secrets has
world and/or group access
D/pppd ( 2627): sent [CHAP Response id=0x1
<7877f2c81a2c718dbc0a1ebc6d9a363b>, name = "localhost"]
D/pppd ( 2627): rcvd [CHAP Success id=0x1 ""]
I/pppd ( 2627): CHAP authentication succeeded
D/pppd ( 2627): sent [CCP ConfReq id=0x1 <deflate 15>
<deflate(old#) 15> <bsd v1 15>]
D/pppd ( 2627): sent [IPCP ConfReq id=0x1 <compress VJ 0f 01> <addr
0.0.0.0> <ms-dns1 0.0.0.0> <ms-dns3 0.0.0.0>]
D/pppd ( 2627): rcvd [LCP ProtRej id=0x2 80 fd 01 01 00 0f 1a 04 78
00 18 04 78 00 15 03 2f]
D/pppd ( 2627): rcvd [IPCP ConfNak id=0x1 <ms-dns1 10.11.12.13> <ms-
dns3 10.11.12.14> <ms-wins 10.11.12.13> <ms-wins 10.11.12.14>]
D/pppd ( 2627): sent [IPCP ConfReq id=0x2 <compress VJ 0f 01> <addr
0.0.0.0> <ms-dns1 10.11.12.13> <ms-dns3 10.11.12.14>]
D/pppd ( 2627): sent [IPCP ConfReq id=0x2 <compress VJ 0f 01> <addr
0.0.0.0> <ms-dns1 10.11.12.13> <ms-dns3 10.11.12.14>]
D/pppd ( 2627): sent [IPCP ConfReq id=0x2 <compress VJ 0f 01> <addr
0.0.0.0> <ms-dns1 10.11.12.13> <ms-dns3 10.11.12.14>]
D/pppd ( 2627): sent [IPCP ConfReq id=0x2 <compress VJ 0f 01> <addr
0.0.0.0> <ms-dns1 10.11.12.13> <ms-dns3 10.11.12.14>]
D/pppd ( 2627): sent [IPCP ConfReq id=0x2 <compress VJ 0f 01> <addr
0.0.0.0> <ms-dns1 10.11.12.13> <ms-dns3 10.11.12.14>]
D/pppd ( 2627): sent [IPCP ConfReq id=0x2 <compress VJ 0f 01> <addr
0.0.0.0> <ms-dns1 10.11.12.13> <ms-dns3 10.11.12.14>]
D/pppd ( 2627): sent [IPCP ConfReq id=0x2 <compress VJ 0f 01> <addr
0.0.0.0> <ms-dns1 10.11.12.13> <ms-dns3 10.11.12.14>]
D/pppd ( 2627): sent [IPCP ConfReq id=0x2 <compress VJ 0f 01> <addr
0.0.0.0> <ms-dns1 10.11.12.13> <ms-dns3 10.11.12.14>]
D/pppd ( 2627): sent [IPCP ConfReq id=0x2 <compress VJ 0f 01> <addr
0.0.0.0> <ms-dns1 10.11.12.13> <ms-dns3 10.11.12.14>]
D/dalvikvm( 2401): GC freed 12354 objects / 604112 bytes in 33ms
D/pppd ( 2627): sent [IPCP ConfReq id=0x2 <compress VJ 0f 01> <addr
0.0.0.0> <ms-dns1 10.11.12.13> <ms-dns3 10.11.12.14>]
W/pppd ( 2627): IPCP: timeout sending Config-Requests
D/pppd ( 2627): sent [LCP TermReq id=0x3 "No network protocols
running"]
D/pppd ( 2627): sent [LCP TermReq id=0x4 "No network protocols
running"]
I/pppd ( 2627): Connection terminated.
D/vold ( 2382): [UEVENT] Sq: 2193 S: net A: 1 P: /devices/virtual/
net/ppp0
D/vold ( 2382): DEVPATH=/devices/virtual/net/ppp0
D/vold ( 2382): INTERFACE=ppp0
D/vold ( 2382): IFINDEX=5
D/vold ( 2382): No uevent handlers registered for 'net' subsystem
I/pppd ( 2627): Modem hangup
On Mar 13, 4:03 pm, Chih-Wei Huang <cwhu...@android-x86.org> wrote:
> Hi,
> An experimental support of3GUSB modem has been pushed into
> donut-x86 branch of the git server. Use repo sync to get it.
>
> The tested3GUSB modem is Huawei E160.
> Just plugin the USB modem, then you should see
> the radio signal icon at top right corner becomes active.
> Now you can use Messaging to send or recive short messages.
>
> To test3Ginternet connection, you have to use command line.
> Use Terminal (or Alt-F1) to run "start ppp". Then use
> "netcfg" to check if the connection is established.
>
> Since it's an experimantal feature, some settings are hardcoded.
> If your3Gmodem is not the same as mime, you may
> have to modify them by hand before building the iso:
>
> * Driver for3GUSB modem is set to "option" module.
> (in 0-auto-detect script, EXTMOD variable)
> *3Ginternet port is set to /dev/ttyUSB0
> (in system/core/rootdir/etc/ppp/peers/gprs)
> *3GMMS port is set to /dev/ttyUSB1
gabriele vidali
http://topup.altervista.org
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To post to this group, send email to andro...@googlegroups.com.
To unsubscribe from this group, send email to android-x86...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/android-x86?hl=en.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To post to this group, send email to andro...@googlegroups.com.
To unsubscribe from this group, send email to android-x86...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/android-x86?hl=en.
gabriele vidali
http://topup.altervista.org
Yi Sun
gabriele vidali
Yi Sun
Android-x86
Chih-Wei Huang
2010/4/16 gabriele vidali <gabriel...@gmail.com>:
gabriele vidali
Chih-Wei Huang
Flex is a tool for creating text pattern recognizers.
You may also need bison, which cooperates with flex.
If you are using debian or ubuntu, you may just
apt-get install flex bison
Read the build requirements carefully.
2010/4/16 gabriele vidali <gabriel...@gmail.com>:
>
>>
>> You don't install flex, a necessary tool to compile android.
gabriele vidali
gabriele vidali
$ git checkout -b android-2.6.32 x86/android-2.6.32thanks, installed everything necessary and trying again now
Kjaergaard
Huawei modem I am able to connect to my 3G provider.
According to my questions I have found some of the answers:
ad 1 + 3.)
The connect chat script /etc/ppp/gprs-connect-chat must be modified.
The APN must be inserted as the last parameter in the AT+CGDCONT=....
line.
A full implementation should insert the APN name from the settings
menu. How should this be done ?
ad 2.
All the logging from the telephony service goes to the radio log
buffer. To read the radio log buffer you may issue the command: logcat
-b radio. I find it convenient also to include the timestamp
information by adding the -v time option to the call, i.e. the final
log retrieval becomes:
logcat -b radio -v time -d
I would still be glad to have some feedback on my remaining questions.
Best regards
Jens Kristian
gabriele vidali
I'm trying with sim pin disabled but can't scan 3g networks. It says error while scanning networks and that my sim does not allow connection.
Also can't modify gprs-connect-chat due to read only file
Il giorno 17/apr/2010 21:03, "Kjaergaard" <ted...@mail.dk> ha scritto:
I have made good progress on this. By disabling the SIM PIN on the
Huawei modem I am able to connect to my 3G provider.
According to my questions I have found some of the answers:
ad 1 + 3.)
The connect chat script /etc/ppp/gprs-connect-chat must be modified.
The APN must be inserted as the last parameter in the AT+CGDCONT=....
line.
A full implementation should insert the APN name from the settings
menu. How should this be done ?
ad 2.
All the logging from the telephony service goes to the radio log
buffer. To read the radio log buffer you may issue the command: logcat
-b radio. I find it convenient also to include the timestamp
information by adding the -v time option to the call, i.e. the final
log retrieval becomes:
logcat -b radio -v time -d
I would still be glad to have some feedback on my remaining questions.
Best regards
Jens Kristian
On Apr 15, 9:55 pm, Kjaergaard <ted...@mail.dk> wrote:
> I have been trying the 3G modem support in...
Kjaergaard
I didn't have success in scanning the networks from the telephony
application either, but the modem seems to be OK with this as long as
the preferred network matches the APN.
I am build the Android 1.6r2 equivalent from source so that I can
modify gprs-chat-connect.
/Jens Kristian
gabriele vidali
On my rooted android tattoo I have read and write access to everything. It remount the fs accordingly.
It should be possible here too
Il giorno 18/apr/2010 15:37, "Kjaergaard" <ted...@mail.dk> ha scritto:
I didn't have success in scanning the networks from the telephony
application either, but the modem seems to be OK with this as long as
the preferred network matches the APN.
I am build the Android 1.6r2 equivalent from source so that I can
modify gprs-chat-connect.
/Jens Kristian
On Apr 18, 2:37 am, gabriele vidali <gabriele.vid...@gmail.com> wrote:
> I'm trying with sim pin di...
> Il giorno 17/apr/2010 21:03, "Kjaergaard" <ted...@mail.dk> ha scritto:
>
> I have made good progress on this. By disabling the SIM PIN on the
> Huawei modem I am able to c...
> --
> You received this message because you are subscribed to the Google Groups "Android-x86" group.
> T...
> For more options, visit this group athttp://groups.google.com/group/android-x86?hl=en.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
...
Chih-Wei Huang
Android-x86 uses a compressed filesystem
so it's absolutely read-only.
You can't modify it even you are root.
Building from source is an easier solution.
2010/4/18 gabriele vidali <gabriel...@gmail.com>:
> remount the fs accordingly.
> It should be possible here too
gabriele vidali
http://topup.altervista.org
Kjaergaard
I havn't analysed the reason why we can't scan the network on the USB
modem. I believe that the generic ril isn't working properly together
with the USB modem. The generic-ril expect to have a full phone, but
the modem is missing the voice part and has the SIM and the datapart
only.
ad 2)
My experience is that I was able to have the ppp connection setup by
inserting the APN in the chat-script.
/Jens Kristian
On 18 Apr., 16:34, gabriele vidali <gabriele.vid...@gmail.com> wrote:
> ok so i guees i have to
> modify ./system/core/rootdir/etc/ppp/gprs-connect-chat before compiling
>
> #/etc/ppp/gprs-connect-chat
> # chat script for China Mobile, used HuaWei GTM900-B GPRS module.
> TIMEOUT 15
> ABORT "DELAYED"
> ABORT "BUSY"
> ABORT "ERROR"
> ABORT "NO DIALTONE"
> ABORT "NO CARRIER"
> TIMEOUT 40
> '' \rAT
> OK ATZ
> OK "ATQ0 V1 E1 +FCLASS=0"
> OK AT+CGDCONT=1,"IP","tre.it"
> OK ATDT*99#
> CONNECT ''
>
> can you pls confirm these questions ?
> 1) i can't scan mobile networks because the 3g usb pen doesn't have GSM
> module, correct?
> 2) i don't need to set the APN since this script does it all (i tried
> setting the APN but it does not save datas)
>
> Gabriele Vidalihttp://topup.altervista.org
>
>
>
>
>
> > Unfortunately, this is not a mobile phone.
> > Android-x86 uses a compressed filesystem
> > so it's absolutely read-only.
> > You can't modify it even you are root.
>
> > Building from source is an easier solution.
>
> > It
> > > remount the fs accordingly.
> > > It should be possible here too
>
> > --
> > Chih-Wei
> > Android-x86 project
> >http://www.android-x86.org
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Android-x86" group.
> > To post to this group, send email to andro...@googlegroups.com.
> > To unsubscribe from this group, send email to
> > .
> >http://groups.google.com/group/android-x86?hl=en.
>
> --
> You received this message because you are subscribed to the Google Groups "Android-x86" group.
> To post to this group, send email to andro...@googlegroups.com.
> To unsubscribe from this group, send email to android-x86...@googlegroups.com.
gianm
corner I have a signal in white (is it supposed to be green?)
My sim has a pin number I can't get rid of.
Is there an easy way to put the pin before trying to connect?
gianm
upper right corner.
Is there a way to put the pin before trying to connect?
Noli Sicad
and where is it located.
For example bluetooth, is located here.
http://git.android-x86.org/?p=platform/external/bluetooth/bluez.git;a=summary
For 3G USB Modem where is it?
I want to find out if my huawei e1762 is supported in the source tree
Thanks. Noli
Chih-Wei Huang
Android already has 3G support.
We just need to enable the driver and
change some settings or parameters.
See the changes in kernel, system/core(init),
ppp and ril.
Try 1.6-r2 to see if it detects your modem.
(check /dev/ttyUSB*)
2010/4/19 Noli Sicad <nsi...@gmail.com>:
> and where is it located.
>
> For example bluetooth, is located here.
> http://git.android-x86.org/?p=platform/external/bluetooth/bluez.git;a=summary
>
> For 3G USB Modem where is it?
>
> I want to find out if my huawei e1762 is supported in the source tree
>
cruz
> Android already has 3G support.
> We just need to enable the driver and
> change some settings or parameters.
>
How can I apply the driver patch to Android-x86 source for kernel re-
compilation?
Thanks,
cruz
Kjaergaard
I have done the following changes to eclair:
- included the drivers as listed for the EXTMOD in the 1.6r2 release
- included the /etc/ppp subtree from the 1.6r2 branch
- included the chat program as an external program
- updated init.rc with service definitions for ril and ppp
The ppp parts works fine, i.e. when I issue the command "start ppp" it
brings up the 3G connection.
However the RIL part isn't working as it does in 1.6r2. It claims
connection to /dev/ttyUSB1 , but the log doesn't show any log entries
from "AT" and it doesn't seems to get any answers from the 3G modem.
Am I missing some changes in the RIL ? (The source tree for /hardware/
ril in 1.6r2 and eclair are identical.)
/Jens Kristian
Chih-Wei Huang
No idea why it doesn't work for eclair.
I'll try when I have spare time.
2010/4/22 Kjaergaard <ted...@mail.dk>:
>
> I have done the following changes to eclair:
> - included the drivers as listed for the EXTMOD in the 1.6r2 release
> - included the /etc/ppp subtree from the 1.6r2 branch
> - included the chat program as an external program
> - updated init.rc with service definitions for ril and ppp
>
> The ppp parts works fine, i.e. when I issue the command "start ppp" it
> brings up the 3G connection.
>
> However the RIL part isn't working as it does in 1.6r2. It claims
> connection to /dev/ttyUSB1 , but the log doesn't show any log entries
> from "AT" and it doesn't seems to get any answers from the 3G modem.
>
> Am I missing some changes in the RIL ? (The source tree for /hardware/
> ril in 1.6r2 and eclair are identical.)
Chih-Wei
Android-x86 project
Kjaergaard
The eclair release in contrast to donut sets:
setprop ro.simulated.phone true
in init.rc. This setting is derived from build/target/board/
generic_x86/init.rc and must be removed so that the 3G modem is used
instead.
Unfortunately removing this setting isn't sufficient. After a good
deal of investigation I found that RIL couldn't open /dev/ttyUSB1.
Doing chmod 666 on /dev/ttyUSB1 allowed RIL to proceed. Changing the
access rights before the last step in a debug startup didn't help. My
assumption is that the access rights for /dev/ttyUSB1 (and /dev/
ttyUSB0) are changed somewhere, but where ?
After doing these tricks with the access rights, RIL is able to
determine the radiostate and the right icon appears on the screen.
During my inspection of init.rc i found two setting which pussled me:
setprop ro.radio.noril yes
setprop ro.radio.use-ppp no
I havn't been able to determine the use of these properties. Does
someone have an explanation ?
/Jens Kristian
>
> læs mere »
Chih-Wei Huang
You forgot the change in init/device.c of system/core.
2010-4-24 上午6:26在 "Kjaergaard" <ted...@mail.dk> 提到：
I have got at least one step further on the porting to eclair.
The eclair release in contrast to donut sets:
setprop ro.simulated.phone true
in init.rc. This setting is derived from build/target/board/
generic_x86/init.rc and must be removed so that the 3G modem is used
instead.
Unfortunately removing this setting isn't sufficient. After a good
deal of investigation I found that RIL couldn't open /dev/ttyUSB1.
Doing chmod 666 on /dev/ttyUSB1 allowed RIL to proceed. Changing the
access rights before the last step in a debug startup didn't help. My
assumption is that the access rights for /dev/ttyUSB1 (and /dev/
ttyUSB0) are changed somewhere, but where ?
After doing these tricks with the access rights, RIL is able to
determine the radiostate and the right icon appears on the screen.
During my inspection of init.rc i found two setting which pussled me:
setprop ro.radio.noril yes
setprop ro.radio.use-ppp no
I havn't been able to determine the use of these properties. Does
someone have an explanation ?
/Jens Kristian
On 21 Apr., 23:11, Kjaergaard <ted...@mail.dk> wrote:
> I am trying to port the 3G code extensions ...
> For more options, visit this group at ...
>
> læs mere »
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
...
Kjaergaard
This solves the protection problem and RILD proceeds right away.
Unfortunately it stops quite soon after some 20-30 RIL request. As
this didn't appear when I enabled RIL by changing protection after
Android startup, I believe this is a timing issue. I will investigate
further.
/Jens Kristian