blah blah blah... I talk to myself in webforum : ) k3-cdma works... stock K3 are able to detect and activate modem, bring up PPP connection, create route, etc. I have not tried to pass traffic; my unit is not in any position to communicate with Amazon right now... I'll try it on my GF's "unhacked" unit soon.
http://igor.chudov.com/manuals/AT_Co...lcomm_U300.pdf seems to mostly accurately reflect the Qualcomm commands.
modemcmd -v -c "AT\$QCMIPGETP", for example, spits out the EVDO profile like I got from the Sprint software. The following from my "non working" modem, included for example only...
Code:
[root@kindle root]# modemcmd -v -c "AT\$QCMIPGETP"
modemcmd 0.3.3 Copyright (C) 2008, 2009 Amazon Technologies, Inc. All
rights reserved.
Profile:1 Enabled
NAI:shrek7?????@SPP0??.dl.sprintpcs.com
Home Addr:0.0.0.0
Primary HA:255.255.255.255
Secondary HA:68.28.18.18
MN-AAA SPI:1234
MN-HA SPI:1234
Rev Tun:1
MN-AAA SS:Set
MN-HA SS:Set
modemcmd -v -c "AT+CSS?" seems like the CDMA way to gather signal strength and connection status. Nonworking SPCS module gives me "?,Z,99999,0" which indicates "Mobile is not registered" or somesuch. With NV2 modem, registered, I see
[root@kindle root]# modemcmd -v -c "AT+CSS?"
1,PD,4376,6
OK
got NV2 to connect... the "wancontrol" script relies on variables in /var/local/wan/info to determine which modem module is in use. Remove /opt/wan/firstboot.done and /var/local/wan/info, reboot, and the file gets rebuilt. I neglected to save a copy of the stock file, but with the SPCS modem (which I can't get to connect… I wonder if it is not really a Kindle modem or the account is blacklisted)
Code:
WAN_INFO_VERSION=4
WAN_TYPE=1
WAN_PROVIDER=1
WAN_CARRIER=1
WAN_PEER=1
WAN_FW_VERSION=m6801B-RAPTOR65_S_HYBRID-131
WAN_INFO_UID=0101
With the NV2
Code:
WAN_INFO_VERSION=4
WAN_TYPE=1
WAN_PROVIDER=2
WAN_CARRIER=1
WAN_PEER=2
WAN_FW_VERSION=m6801B-RAPTOR65_S_HYBRID-132
WAN_INFO_UID=0201
peers are defined under /etc/ppp, I added -v to the chat line to make it more talkie.
For some reason I had to send an AT&F before "wancontrol pppstart" would work for me, but it might just be a software problem on my part - previously I was getting a failure "NO CARRIER".
syslog:
Code:
info 100731:002635 system: I wancontrol:pc:processing "pppstart"
notice 100731:002635 pppd[5425]: pppd 2.4.4 started by root, uid 0
info 100731:002636 chat[5429]: timeout set to 60 seconds
info 100731:002636 chat[5429]: abort on (BUSY)
info 100731:002636 chat[5429]: abort on (ERROR)
info 100731:002636 chat[5429]: abort on (NO ANSWER)
info 100731:002636 chat[5429]: abort on (NO CARRIER)
info 100731:002636 chat[5429]: send (ATZ^M)
info 100731:002636 chat[5429]: expect (OK)
info 100731:002636 chat[5429]: ^M
info 100731:002636 chat[5429]: OK
info 100731:002636 chat[5429]: -- got it
info 100731:002636 chat[5429]: send (ATE0V1^M)
info 100731:002636 chat[5429]: expect (OK)
info 100731:002636 chat[5429]: ^M
info 100731:002636 chat[5429]: ATE0V1^M^M
info 100731:002636 chat[5429]: OK
info 100731:002636 chat[5429]: -- got it
info 100731:002636 chat[5429]: send (ATD#777^M)
info 100731:002636 chat[5429]: expect (CONNECT)
info 100731:002636 chat[5429]: ^M
info 100731:002637 chat[5429]: ^M
info 100731:002637 chat[5429]: CONNECT
info 100731:002637 chat[5429]: -- got it
info 100731:002637 chat[5429]: send (^M)
info 100731:002637 pppd[5425]: Serial connection established.
info 100731:002637 pppd[5425]: Using interface ppp0
notice 100731:002637 pppd[5425]: Connect: ppp0 <--> /dev/tts/USB0
info 100731:002638 PPP Deflate Compression module registered
It is interesting the Sprint seems to support compression; this would tend to make things faster and reduce wireless bandwidth usage. This has the side effect of making it IMMEDIATELY obvious if you attempt to connect using a Windows or Mac. According to the scripts, this compression is explicitly disabled for GSM.
Code:
notice 100731:002638 pppd[5425]: local IP address xxx.xxx.xxx.xxx
notice 100731:002638 pppd[5425]: remote IP address xxx.xxx.69.241
notice 100731:002639 lipc-get-prop[5471]: I lipc:gip:prop=shouldRoute,
source=com.lab126.wan:Get int property
info 100731:002639 system: I ip-up:def:PPP interface up ppp0
/dev/tts/USB0 230400 xxx.xxx.xxx.xxx xxx.xxx.69.241
[root@kindle root]# netstat -nr
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
xx.xx.69.241 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0
207.171.165.149 xx.xx.69.241 255.255.255.255 UGH 0 0 0 ppp0
207.171.165.150 xx.xx.69.241 255.255.255.255 UGH 0 0 0 ppp0
10.xx.xx.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0
0.0.0.0 10.xx.xx.1 0.0.0.0 UG 0 0 0 wlan0
We see here that specific, static routes to Amazon get created; perhaps these are because of DNS. A default route was not created, probably because my wifi was active.