Hi,
Is anybody able to use Wizard as bluetooth gprs modem under Linux?
l2ping works, but /dev/rfcomm0 refusing connections.
sonyericsson T610 works just fine in the same environment.
poorotis said:
Is anybody able to use Wizard as bluetooth gprs modem under Linux?
Click to expand...
Click to collapse
i've succeeded this. try to establish rfcomm connection with channel number strictly defined:
Code:
[[email protected] ~]$ rfcomm connect 0 xx:xx:xx:xx:xx 4
in my case it works with channel=4.
eva_d said:
i've succeeded this. try to establish rfcomm connection with channel number strictly defined:
Code:
[[email protected] ~]$ rfcomm connect 0 xx:xx:xx:xx:xx 4
in my case it works with channel=4.
Click to expand...
Click to collapse
Can you post the full output of
Code:
$ sdptool records xx:xx:xx:xx:xx
cr2 said:
Can you post the full output of
Code:
$ sdptool records xx:xx:xx:xx:xx
Click to expand...
Click to collapse
it does not output anything. looks even like it does not have such command at all:
Code:
[[email protected] ~]# sdptool records 00:12:37:7B:AE:EE
[[email protected] ~]# sdptool
sdptool - SDP tool v2.15
Usage:
sdptool [options] <command> [command parameters]
Options:
--help Display help
--source Specify source interface
Commands:
search Search for a service
browse Browse all available services
add Add local service
del Delete local service
get Get local service
setattr Set/Add attribute to a SDP record
setseq Set/Add attribute sequence to a SDP record
Services:
DID SP DUN LAN FAX OPUSH FTRN HS HF SAP NAP GN HID CIP CTP A2SRC A2SNK
eva_d said:
sdptool - SDP tool v2.15
Click to expand...
Click to collapse
Mine is v2.19
I was able to establish a bluetooth connection on channel 4 after qtek firmware upgrade to 2.x.x.x with /etc/bluetooth/rfcomm.conf:
rfcomm2 {
bind yes;
# Bluetooth address of the device
device xx:xx:xx:xx:xx:xx;
# RFCOMM channel for the connection
channel 4;
# Description of the connection
comment "gprs-qtek";}
But pppd can not start, seems I using incorrect AT commands. this is from log:
pppd 2.4.4b1 started by root, uid 0
send (AT^M)
timeout set to 240 seconds
expect (OK)
^M
OK
-- got it
send (AT+CGDCONT=1,"IP","internet.mts.ru"^M)
expect (OK)
^M
^M
OK
-- got it
send (ATDT*99***1#^M)
timeout set to 22 seconds
expect (CONNECT)
^M
^M
OK^M
^M
ERROR^M
alarm
Failed
Exit.
eva_d, could you please show us your pppd/chat scripts?
cr2 said:
eva_d said:
sdptool - SDP tool v2.15
Click to expand...
Click to collapse
Mine is v2.19
Click to expand...
Click to collapse
this is on my system (SDP tool v2.24):
# sdptool records xx:xx:xx:xx:xx:xx
Service Name: Audio Video Remote Control Profile
Service RecHandle: 0x10000
Service Class ID List:
"AV Remote Target" (0x110c)
Protocol Descriptor List:
"L2CAP" (0x0100)
PSM: 23
"AVCTP" (0x0017)
uint16: 0x100
Profile Descriptor List:
"AV Remote" (0x110e)
Version: 0x0100
Service Name: A2DP
Service RecHandle: 0x10001
Service Class ID List:
"Audio Source" (0x110a)
Protocol Descriptor List:
"L2CAP" (0x0100)
PSM: 25
"AVDTP" (0x0019)
uint16: 0x100
Profile Descriptor List:
"Advanced Audio" (0x110d)
Version: 0x0100
Service Name: Voice Gateway
Service RecHandle: 0x10002
Service Class ID List:
"Headset Audio Gateway" (0x1112)
"Generic Audio" (0x1203)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 1
Profile Descriptor List:
"Headset" (0x1108)
Version: 0x0100
Service Name: Voice Gateway
Service RecHandle: 0x10003
Service Class ID List:
"Handfree Audio Gateway" (0x111f)
"Generic Audio" (0x1203)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 2
Profile Descriptor List:
"Handsfree" (0x111e)
Version: 0x0101
Service Name: OBEX Object Push
Service RecHandle: 0x10004
Service Class ID List:
"OBEX Object Push" (0x1105)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 3
"OBEX" (0x0008)
Language Base Attr List:
code_ISO639: 0x656e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"OBEX Object Push" (0x1105)
Version: 0x0100
Service Name: Dial-up Networking
Service RecHandle: 0x10005
Service Class ID List:
"Dialup Networking" (0x1103)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 4
Language Base Attr List:
code_ISO639: 0x656e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"Dialup Networking" (0x1103)
Version: 0x0100
poorotis said:
send (ATDT*99***1#^M)
Click to expand...
Click to collapse
try to dial *99#. i couldn't succeed with *99***1#
poorotis said:
eva_d, could you please show us your pppd/chat scripts?
Click to expand...
Click to collapse
i'm using GNOME PPP to make dial-up connections, no scripts. click, click & ready to go
Thank you eva_d !
You have turned me into the right direction!
I have finally solved my problem.
I am attaching a tarball with all files needed to get HTC Wizard work as bluetooth gprs modem under Linux for whom it may be interesting.
P.S.
# pppd call gprs-bt-qtek
pppd[12798]: pppd 2.4.4b1 started by poorotis, uid 0
chat[12800]: send (ATX3^M)
chat[12800]: expect (OK)
chat[12800]: ^M
chat[12800]: OK
chat[12800]: -- got it
chat[12800]: send (ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0^M)
chat[12800]: expect (OK)
chat[12800]: ^M
chat[12800]: ATX3^M^M
chat[12800]: OK
chat[12800]: -- got it
chat[12800]: send (ATM1L3DT*99#^M)
chat[12800]: timeout set to 10 seconds
chat[12800]: expect (CONNECT)
chat[12800]: ^M
chat[12800]: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0^M^M
chat[12800]: OK^M
chat[12800]: ATM1L3DT*99#^M^M
chat[12800]: CONNECT
chat[12800]: -- got it
chat[12800]: send (^M)
pppd[12798]: Serial connection established.
pppd[12798]: Using interface ppp0
pppd[12798]: Connect: ppp0 <--> /dev/rfcomm2
pppd[12798]: CHAP authentication succeeded
pppd[12798]: CHAP authentication succeeded
pppd[12798]: local IP address ZZZ.ZZ.5.47
pppd[12798]: remote IP address ZZZ.Z.235.34
pppd[12798]: primary DNS address ZZZ.Z.224.194
pppd[12798]: secondary DNS address ZZZ.Z.224.130
P.P.S. eva_d, I owe you a beer!
poorotis said:
P.P.S. eva_d, I owe you a beer!
Click to expand...
Click to collapse
heh, no problem with that btw, i'm planning to launch personal homepage with various advices about solving problems with linux, i mean problems which i personally managed to solve. connecting linux with internet via bluetooth&gprs could be one of first topics there... but as usual, i don't have much time for such projects. :/
btw, instead of running scripts from shell i'd recommend to use GNOME PPP. however you need to run it as root to make it work properly, but personally i have it integrated with gnome quite well (when i click GNOME PPP icon, system asks for root password and it's ready to go . ah, and before that just one doubleclick on icon to open bluetooth rfcomm connection.
eva_d said:
btw, instead of running scripts from shell i'd recommend to use GNOME PPP.
Click to expand...
Click to collapse
It is not suitable for me because I want to have an ability to connect/disconnect from scripts/remotely/when X not started/etc.
I can do that all with pppd and commandline interface
eva_d said:
ah, and before that just one doubleclick on icon to open bluetooth rfcomm connection.
Click to expand...
Click to collapse
My rfcomm connection is always open when my device is in accessible range. I am using bluez-utils with rfcomm.conf which can be found in my previous post and connection always initializing at my pc startup.
hy,
i am not able to get a bt-connection to my wizard.
i used the deviceadress i found when i connect the device via bt to a windows box but if i make
sdptool records 00:12:37:a5:61:48
i got:
Failed to connect to SDP server on 00:12:37:A5:61:48: Host is down
and with:
rfcomm connect 0 00:12:37:a5:61:48 4
i got:
Can't connect RFCOMM socket: Resource temporarily unavailable
can anybody help me please?
BPM said:
hy,
i am not able to get a bt-connection to my wizard.
i used the deviceadress i found when i connect the device via bt to a windows box but if i make
sdptool records 00:12:37:a5:61:48
i got:
Failed to connect to SDP server on 00:12:37:A5:61:48: Host is down
and with:
rfcomm connect 0 00:12:37:a5:61:48 4
i got:
Can't connect RFCOMM socket: Resource temporarily unavailable
can anybody help me please?
Click to expand...
Click to collapse
i never had such errors. are you sure that bluetooth is on and discoverable?
yes, i am able to bind it to the windows machine.
how can i search for devices?
BPM said:
yes, i am able to bind it to the windows machine.
how can i search for devices?
Click to expand...
Click to collapse
Code:
[[email protected] ~]# hcitool scan
Scanning ...
00:E0:03:37:AB:25 evad.6230
00:12:37:7B:AE:EE Dawid Lorenz
ok in my kbluetoothutils there is button "Additional search Options for non-discoverable devices".
with this i found my device. but how can i pair it?
BPM said:
ok in my kbluetoothutils there is button "Additional search Options for non-discoverable devices".
with this i found my device. but how can i pair it?
Click to expand...
Click to collapse
hard to say, i don't use kbluetoothutils in first place. also, i use command line to pair devices and in my case everything works fine. these messages could suggest there's problem with mobile. maybe you should try to soft-reset your wizard? hard to say, i never had such errors, so i'm not sure how can i help you with that. maybe someone else could...
can you give me a step-by-step commandlinesolution?
[email protected]:~$ hcitool scan
Scanning ...
[email protected]:~$ sdptool records 00:12:37:a5:61:48
Failed to connect to SDP server on 00:12:37:A5:61:48: Host is down
[email protected]:~$
i think the problem is that hcitool gives no results.
but if i enter the device id in my utils i can see the name of the device. so bt runs correct i think
if i make a connection with rfcomm the bluetoothsymbol in my systembar gets blue. if i move the mouse to the symbol i can read "connected to devicename".
but after a few seconds the symbol gets grey again and i get a timeout.
any hint?
Related
Of course that it will work on any Linux ! Of course that with any WM5 AKU 3 device ! Certainly that it works on 3G, EDGE, GPRS, because the PC doesn't see the WAN itself (the GSM network).
The stages are as simple as 1, 2, 3 !
1. Go (on the WM5 AKU 3.x device) to Internet Sharing, select your network, select BT-PAN profice and click Connect.
2. Open a console on Linux (root) and start writing:
root# pand -s -r PANU
root# pand -Q10
(optional, to test) root# pand -l
root# ifconfig bnep0 192.168.0.2
root# route add default gw 192.168.0.1
root# echo "nameserver 194.102.255.2" > /tmp/resolv.conf.bnep0
3. READY !
Notes upon the implied commands:
a) pand -s -r PANU // starts the PAN daemon (server) in the PANU mode and puts it to listening mode
b) pand -Q10 // performs a 10sec search for the HCI address of a PANU and connects to it
c) pand -l // view if you have connection : bnep0 00:17:83:01:38:6B PANU - in my case
d) ifconfig bnep0 192.168.0.2 // sets the IP of the virtual network interface. Please do veryfy on your PDA that the PAN interface has 192.168.0.1 already seted up. Of course that you can use other IPs, but stay in the same network !
e) route add default gw 192.168.0.1 // sets the WM5 device as the gateway for IP packets. Certainly that you can change the address for originality, but remember that it must be the IP of the PAN interface on the WM5 device !
f) echo "nameserver 194.102.255.2" > /tmp/resolv.conf.bnep0 // assigns a DNS server to be queried. Of course that you can use any DNS IP that you want.
g) REMEMBER: On Fedora, IP forward is already activated. On Debian it is not. Thus, before command number e, you must activate it by typing "echo 1 > /proc/sys/net/ipv4/ip_forward" (without the quotes).
Cheers !
We are testing IP forwarding feature on windows mobile 6.1 platform. The scenario is as following:
169.254.19.49/16 169.254.54.165/16
+--------| a +--------+
| PC1 | ----------- | Mobile |
+--------+ +--------+
\ |
\ c b |
\ |
\ |
\ +---------+
\-------------- | PC2 |
169.254.160.194/16 +---------+
We setup an Wi-Fi ad-hoc network and 3 nodes involved. This is a full mesh network. There is a direct wireless link 'c' between PC1 and PC2 and we expect the IP packets path changed to be PC1--Mobile--PC2.
We enabled IP forwarding on the mobile phone and change PC1 and PC2's routing tables. But it seems IP forwarding does not work properly. We did 'ping 169.254.19.49' from PC2 and we did get the ICMP replies. While the packet sniffer shows that those replies are originated by the middle node (source IP is 169.254.54.165) and no packets are received by 169.254.19.49. How come the mobile phone take the responsibility to answer the ICMP reply for PC1 and it even does not check the reachability to PC1.It seems there is some kind of proxy running on the mobile? Any configuration we are missing?
The modifications to the devices are attached below:
PC1
----------------------------------------------------------------------------------------
IP: 169.254.19.49/16
Routing Table:
Network Destination Netmask Gateway Interface Metric
169.254.0.0 255.255.0.0 169.254.19.49 169.254.19.49 30
169.254.19.49 255.255.255.255 127.0.0.1 127.0.0.1 30
169.254.160.194 255.255.255.255 169.254.54.165 169.254.19.49 30
169.254.255.255 255.255.255.255 169.254.19.49 169.254.19.49 30
Basically, the routing setting implies that 'to 169.254.160.194, the next hop is 169.254.54.165'.
Registry setting:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\EnableICMPRedirect = 0
The purpose is to ignore possible ICMP redirect message from the mobile phone which would change the route entry 169.254.160.194 back to a direct network route.
Mobile:
----------------------------------------------------------------------------------------
IP: 169.254. 54.165/16
Routing Table:
Network Destination Netmask Gateway Interface
Metric
169.254.0.0 255.255.0.0 169.254.160.194 0x3
25
169.254.19.49 255.255.255.255 169.254.54.165 0x3
30
169.254.54.165 255.255.255.255 127.0.0.1 0x3
30
169.254.160.194 255.255.255.255 169.254.54.165 0x3
30
169.254.255.255 255.255.255.255 169.254.2.1 0x30002
30
169.254.255.255 255.255.255.255 169.254.54.165 0x3
30
Registry setting:
HKEY_LOCAL_MACHINE\Comm\Tcpip\Parms\IpEnableRouter = 1
HKEY_LOCAL_MACHINE\Comm\Tcpip\Parms\EnableICMPRedirects = 0
PC2
----------------------------------------------------------------------------
------------
IP: 169.254.160.194/16
Routing Table:
Network Destination Netmask Gateway Interface
Metric
169.254.0.0 255.255.0.0 169.254.160.194 169.254.160.194
25
169.254.19.49 255.255.255.255 169.254.54.165 169.254.160.194
30
169.254.160.194 255.255.255.255 127.0.0.1 127.0.0.1
25
169.254.255.255 255.255.255.255 169.254.2.2 169.254.2.2
30
169.254.255.255 255.255.255.255 169.254.160.194 169.254.160.194
25
Basically, the routing setting implies that 'to 169.254.19.49, the next hop
is 169.254.54.165'.
Registry setting:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Enable
ICMPRedirect = 0
YOu shouldn't use 169.254 addressing.
169.254.0.0/16 is the "link local" block. It is allocated for communication between hosts on a single link.
Have a quick read on RFC 3330
something else in your network is probably interfering.
use 10.0.0.0/8 or perhaps 192.168.0.0/16 or 172.16.0.0/12 as these are set aside for private networking addresses.
thank you very much
farkah said:
YOu shouldn't use 169.254 addressing.
169.254.0.0/16 is the "link local" block. It is allocated for communication between hosts on a single link.
Have a quick read on RFC 3330
something else in your network is probably interfering.
use 10.0.0.0/8 or perhaps 192.168.0.0/16 or 172.16.0.0/12 as these are set aside for private networking addresses.
Click to expand...
Click to collapse
Thank you Very Much!!!! I have solve this problem!!!!
hi all,
My firewall logs are showing me that something on my Hero is regularly trying to send TCP packets to port 13 at 131.107.13.100. That IP isn't in the DNS directly, but is administered by MSN:
;; AUTHORITY SECTION:
13.107.131.in-addr.arpa. 3600 IN SOA ns1.msft.net. msnhst.microsoft.com. 2007082301 1800 900 7200000 3600
13/tcp is normally used by the "daytime" protocol, but since my phone should be getting its time from the phone network, I'm not entirely convinced.
Anyone know what this might be, please?
thanks much...
same here, only just spotted this. Any word on this?
I notice that my Hero's clock is often out, by a good few seconds, so clearly it isn't working as it should. I'd rather be able to specify a NTP server of my choosing, but last time I checked, NTP client required root access.
More on this: curiously, looking in DDMS I find that IP against time-nw.nist.gov in the log. The log tells us what pid used that InetAddress - 163 in my case, which I looked up in Device/Show process status as:
app_7 163 36 106208 18924 ffffffff afe0d3e4 S com.htc.provider (u:260, s:121)
so I'm thinking to poke around something like
sqlite3 /data/data/com.htc.provider.***
maybe swap to NTP server of my choice. I'll report how I get on.
dig time-nw.nist.gov leads me to
tf.nist.gov
which sounds like a pukka time server hosted by MS.
Of more concern to me is that I see lots of TMTTime=0 in my logs; no wonder my clock's all over the place.
I couldn't find any setting for time service in weather.db, CustomizationSettings.db or settings.db.
My HTC Desire also has persistent connections to this server:
Code:
~/data $ netstat -antp | grep :13
netstat: showing only processes with your user ID
tcp 0 0 ::ffff:192.168.1.104:39616 ::ffff:131.107.13.100:13 ESTABLISHED -
tcp 0 0 ::ffff:192.168.1.104:38180 ::ffff:131.107.13.100:13 ESTABLISHED -
tcp 0 0 ::ffff:192.168.1.104:40715 ::ffff:131.107.13.100:13 ESTABLISHED -
I wonder why to keep those connections persistent and so numerous?
I'm having issues sending & receiving MMS messages. The data connection works fine for browsing, and the APN settings are the ones from the O2 website (although I've tried several combinations from Google).
Same problem on both PPP and RMNet on michy's r11 and PPP on hastarin 7.2, can't figure it out. I've spent hours on Google and have search XDA, and can't get anywhere.
I've even tried using the Google DNS & O2 DNS servers to no avail.
I've included a logcat of what happens when I try to send an MMS in case it helps.
Does anyone have any ideas? I'm stumped.
We have 2 HD2s on O2, happens on both.
MMS works fine in WinMo.
WinMo: O2 Stock 1.72
Radio 2.12 & 2.15
Android: Bangsters 1.4 & 1.5
Kernel: michy's r11 and hastarin #7.2
Code:
I/pppd ( 2973): PAP authentication succeeded
D/MobileDataStateTracker( 304): mms Received state= CONNECTED, old= CONNECTING, reason= apnSwitched, apnTypeList= mms
D/NetworkStateTracker( 304): setDetailed state, old =CONNECTING and new state=CONNECTED
D/ConnectivityService( 304): ConnectivityChange for mobile_mms: CONNECTED/CONNECTED
V/NetworkStateTracker( 304): Setting TCP values: [4093,26280,35040,4096,16384,35040] which comes from [net.tcp.buffersize.edge]
D/NetworkLocationProvider( 304): onDataConnectionStateChanged 1
D/NetworkStateTracker( 304): addPrivateDnsRoutes for Mobile data state: CONNECTED(ppp0) - mPrivateDnsRouteSet = false
D/NetworkStateTracker( 304): adding 193.113.200.200 (-926387775)
D/NetworkStateTracker( 304): adding 193.113.200.201 (-909610559)
D/Tethering( 304): Tethering got CONNECTIVITY_ACTION
D/Tethering( 304): MasterInitialState.processMessage what=3
E/HierarchicalStateMachine( 304): TetherMaster - unhandledMessage: msg.what=3
D/GpsLocationProvider( 304): updateNetworkState available info: NetworkInfo: type: mobile_mms[EDGE], state: CONNECTED/CONNECTED, reason: apnSwitched, extra: mobile.o2.co.uk, roaming: false, failover: false, isAvailable: true
V/NetworkChange( 767): Received network change notification
D/NetworkLocationProvider( 304): updateNetworkState(): Updating network state to 2
D/ConnectivityService( 304): startUsingNetworkFeature for net 0: enableMMS
D/ConnectivityService( 304): getMobileDataEnabled returning true
D/ConnectivityService( 304): special network already active
I/GTalkService( 440): [ServiceAutoStarter] --- connectivity changed
I/GTalkService( 440): [ServiceAutoStarter] --- start GTalk service ---
I/MediaUploader( 731): No need to wake up
E/SendTransaction( 596): java.io.IOException: Cannot establish route for http://mmsc.mms.o2.co.uk: Unknown host
E/SendTransaction( 596): at com.android.mms.transaction.Transaction.ensureRouteToHost(Transaction.java:210)
E/SendTransaction( 596): at com.android.mms.transaction.Transaction.sendPdu(Transaction.java:165)
E/SendTransaction( 596): at com.android.mms.transaction.Transaction.sendPdu(Transaction.java:150)
E/SendTransaction( 596): at com.android.mms.transaction.SendTransaction.run(SendTransaction.java:118)
E/SendTransaction( 596): at java.lang.Thread.run(Thread.java:1096)
E/SendTransaction( 596): Delivery failed.
bump bump. Same problem here for me
contract or payg ?
contract.......................
In your MMS APN settings is the http://mmsc* server information in the SERVER or MMS SERVER slot?
dkl_uk said:
In your MMS APN settings is the http://mmsc* server information in the SERVER or MMS SERVER slot?
Click to expand...
Click to collapse
Tried in each and both
optiknerv said:
Tried in each and both
Click to expand...
Click to collapse
Well it definitely shouldn't be in the SERVER slot, that's part of your issue and you will receive errors regarding the lack of connection. It's trying to connect to something it's not supposed to want to connect to.
You have a choice of the following:
Data Bearer:
GPRS
Access Point Node (APN):
wap.o2.co.uk (contract)
payandgo.o2.co.uk (PAYG)
User ID:
o2wap (contract)
payandgo (PAYG)
Password:
password
Authentication
Normal
Gateway
193.113.200.195
MMS Message Server
http://mmsc.mms.o2.co.uk:8002
ENSURE there is a tick only in the MMS box.
I have tried to setup MMS in my network settings and failed, although it can be done. You should end up with two APN's, one is "default,supl" and the other is "mms".
dkl_uk said:
Well it definitely shouldn't be in the SERVER slot, that's part of your issue and you will receive errors regarding the lack of connection. It's trying to connect to something it's not supposed to want to connect to.
You have a choice of the following:
Data Bearer:
GPRS
Access Point Node (APN):
wap.o2.co.uk (contract)
payandgo.o2.co.uk (PAYG)
User ID:
o2wap (contract)
payandgo (PAYG)
Password:
password
Authentication
Normal
Gateway
193.113.200.195
MMS Message Server
http://mmsc.mms.o2.co.uk:8002
ENSURE there is a tick only in the MMS box.
I have tried to setup MMS in my network settings and failed, although it can be done. You should end up with two APN's, one is "default,supl" and the other is "mms".
Click to expand...
Click to collapse
I don't get a failed connection error. In fact I note that when I click send it disconnects from data connection then reconnects (i presume to the mms settings) it seems to show data upload and download but after a couple of minutes I get a "failed to send message after multiple attempts error"
It's just a wild guess, but I had problems with sending MMSes (while being sure that all carrier APN's settings were correct), when MMS Size setting was set to higher values than 300 KB. Although my problems were only with sending MMSes - I could receive them without any problems.
adecostres said:
It's just a wild guess, but I had problems with sending MMSes (while being sure that all carrier APN's settings were correct), when MMS Size setting was set to higher values than 300 KB. Although my problems were only with sending MMSes - I could receive them without any problems.
Click to expand...
Click to collapse
Seems this was the problem. Cheers.
This is what i get on CM12. Similar commands like 'ip route' show the same. No default gateway. But the internet connection works as the gateway is defined properly in the Android WiFi settings. But why doesn't it show up with the 'route' command?
Code:
localhost / # busybox route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.100.0 * 255.255.255.0 U 0 0 0 wlan0