GNOME Bugzilla – Bug 622576
Network Manager don't detect NTT A2502(= Anydata ADU635)
Last modified: 2011-08-02 17:20:53 UTC
Network-manager don't detect NTT A2502 on Ubuntu Linux from 8.04 to 10.04. There are 2 reason for it. 1. A2502 don't return registration state. it returns always IDLE(0) against AT+CREG 2. newer ModemManager includes mm-plugin-anydata. It only supports CDMA modems. I made plugin for anydata gsm/HSDPA modems which includes workaround for NTT A2502, which is oem of Anydata ADU635. pls pull from http://github.com/miurahr/ModemManager/ There is an a2502 topic branch. This problem is also reported on launchpad.net issue tracker. It is for Anydata ADU 635. https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/569685
Created attachment 164480 [details] [review] anydata gsm/hsdpa plugin
Created attachment 164481 [details] [review] NTT A2502 workaround A2502 patch on anydata gsm/hsdpa plugin
What does the modem return for "AT+CGREG?" ? Do either of AT+CREG or AT+CGREG return the actual status?
When I am in Home network reachable place, I got a result as follows with A2502: ati NTT DoCoMo OK ati1 FOMA A2502 HIGH-SPEED OK AT+GCAP +GCAP: +CGSM,+DS,+ES OK AT+GMI AnyDATA.NET OK AT+GMM FOMA A2502 HIGH-SPEED OK at+CGREG? +CGREG: 0,1 OK AT+CREG? +CREG: 0,0 OK AT+CGREG=1 OK AT+CGREG? +CGREG: 1,1 OK AT+CREG? +CREG: 0,0 OK AT+CREG=1 OK AT+CREG? +CREG: 1,0 OK AT+CREG=? +CREG: (0-1) OK It seems AT+CREG don't work but AT+GCREG seems to work. Now, I found a manual in English. http://jcrcorp.com/mobile/manuals/a2502/A2502_E_All.pdf It don't say about AT+CREG but say about AT+GCREG in p.91 -------------- n=0(default): Do not notify n=1: Notify when outside and inside the service area is changed. Execute「AT+CGREG?」 then appears as 「+CGREG:<n>,<state>」 <state> 0:Not registered 1:Registered Home Network 4: Unknown 5: Registered (while roaming) --------------
Reopening as the requested information has been provided.
I think what we want to do here is to always check both CREG (circuit-switched registration) and CGREG (packet-switched) and if either is registered, then connect.
I think this got fixed last year by 72a1a6caf67a15655ade8dc5eed4f94f86107171 and 88ee478bb659e6660b3bca1e8f2bd45b667a603b; the code appears to check CS reg state for home/roaming (which in this case isn't available), and then checks PS reg state and will permit dialing then. So I believe this is fixed with latest MM releases from July 2010 onward.