Can't send messages about simple-android-instant-messaging-application

[GoogleCodeExporter]

hello,

how did u fix the registration ? I get a error when I try to register a user. 
please help.

Original comment by [email protected] on 16 Feb 2013 at 7:11

[GoogleCodeExporter]

//One is connected through 3G, and the other is connected through WIFI.

3G n WIFI are different constants value? in SocketOperator its use 
DEFAULT_NETWORK_PREFERENCE.









public static final int TYPE_BLUETOOTH

Added in API level 13
The Default Bluetooth data connection. When active, all data traffic will use 
this connection by default.

Constant Value: 7 (0x00000007)
public static final int TYPE_DUMMY

Added in API level 14
Dummy data connection. This should not be used on shipping devices.

Constant Value: 8 (0x00000008)
public static final int TYPE_ETHERNET

Added in API level 13
The Default Ethernet data connection. When active, all data traffic will use 
this connection by default.

Constant Value: 9 (0x00000009)
public static final int TYPE_MOBILE

Added in API level 1
The Default Mobile data connection. When active, all data traffic will use this 
connection by default.

Constant Value: 0 (0x00000000)
public static final int TYPE_MOBILE_DUN

Added in API level 8
A DUN-specific Mobile data connection. This connection may be the same as 
TYPE_MOBILE but it may be different. This is used by applicaitons performing a 
Dial Up Networking bridge so that the carrier is aware of DUN traffic. It may 
coexist with default data connections.

Constant Value: 4 (0x00000004)
public static final int TYPE_MOBILE_HIPRI

Added in API level 8
A High Priority Mobile data connection. This connection is typically the same 
as TYPE_MOBILE but the routing setup is different. Only requesting processes 
will have access to the Mobile DNS servers and only IP's explicitly requested 
via requestRouteToHost(int, int) will route over this interface if a default 
route exists.

Constant Value: 5 (0x00000005)
public static final int TYPE_MOBILE_MMS

Added in API level 8
An MMS-specific Mobile data connection. This connection may be the same as 
TYPE_MOBILE but it may be different. This is used by applications needing to 
talk to the carrier's Multimedia Messaging Service servers. It may coexist with 
default data connections.

Constant Value: 2 (0x00000002)
public static final int TYPE_MOBILE_SUPL

Added in API level 8
A SUPL-specific Mobile data connection. This connection may be the same as 
TYPE_MOBILE but it may be different. This is used by applications needing to 
talk to the carrier's Secure User Plane Location servers for help locating the 
device. It may coexist with default data connections.

Constant Value: 3 (0x00000003)
public static final int TYPE_WIFI

Added in API level 1
The Default WIFI data connection. When active, all data traffic will use this 
connection by default.

Constant Value: 1 (0x00000001)
public static final int TYPE_WIMAX

Added in API level 8
The Default WiMAX data connection. When active, all data traffic will use this 
connection by default.

Constant Value: 6 (0x00000006)

Original comment by [email protected] on 27 Feb 2013 at 8:27

[GoogleCodeExporter]

go to user table
check user port number 

adb -s emulator-5554 forward tcp:12345 tcp:12345

adb -s emulator-5556 forward tcp:54321 tcp:54321 
replace port number with 12345 if user1 login in emulator-5554 than use user1 
port number with replacing 12345
as so on
run this in command promt

Original comment by [email protected] on 11 Apr 2013 at 1:14

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I have the same problem.  Everything works fine through the internet except for 
sending messages.  Has anyone found a solution?

Original comment by [email protected] on 19 Apr 2013 at 10:09

[GoogleCodeExporter]

when i'm looking on this source i think the problem is that 
sending messages isnt done "server sided" so you would have the assigned port 
to be routed on both devices.

Device send's a message directly to the destination ip and port.

I'm currently trying to send and receive messages through the server API.
A nice Pro for this way would be that your messages are saved on the server so 
you would receive messages when you're comming back online.

I will post my source if it works ;)

Original comment by [email protected] on 4 May 2013 at 2:03

[GoogleCodeExporter]

These "Chat Message couldn't be sent" is caused by sending/receiving directly 
through sockets.

some operators provide private IP-Adresses so it is just impossible to connect 
(send/receive) on devices in their net.

I just got the commitment rights to maintain this project, my first update will 
include sending and receiving messeges through the XML Api which will fix these 
Issues.

Original comment by [email protected] on 6 May 2013 at 4:34

• Changed state: Started

[GoogleCodeExporter]

Hey i've just uploaded the preview APK with the Fix for the send/receive "bug", 
try it out!
http://code.google.com/p/simple-android-instant-messaging-application/downloads/
detail?name=AndroidIMu2.apk&can=2&q=

I think i get the source ready till tomorrow, you'll find it under downloads.
Update 2

Original comment by [email protected] on 13 Jul 2013 at 2:01

• Added labels: Component-Logic, Priority-Critical
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Original comment by [email protected] on 13 Jul 2013 at 4:00

• Changed state: Fixed