Forums | developer.brewmp.com Forums | developer.brewmp.com

Developer

Forums

Forums:

We're experiencing the following problem with Application Directed SMSs. In our application, when the handset received the AppDirSMS, it is supposed to start our BREW app and then the app automatically logs into our server to get data. If the handset is in an LG native screen, this works correctly.

If the handset is already in our BREW app and connected to our server when the AppDirSMS arrives, the SMS arrives and is processed successfully.

BUT if the phone is in our BREW app but DISCONNECTED from the server, then the handset opens a socket to attempt to connect the socket and this FAILS. Not only does it hang while trying to connect the socket, the process times out and the ROAM indicator and QNC data icon start blinking. At this point, the phone is hosed and we must exit from BREW to get things working again. Once we exit BREW, all the icons stop blinking and everything goes back to normal.

This is reproducible 100% of the time. What is going on here? Has anyone ever seen this?

This really sounds like a phone bug. If have seen similar types of behaviour on a few other handsets.
What phone is it?

This really sounds like a phone bug. If have seen similar types of behaviour on a few other handsets.
What phone is it?

This is the VX-6000. What have you seen on other handsets?

This is the VX-6000. What have you seen on other handsets?

what happens in the emulator ?

what happens in the emulator ?

Lots of weird behaviour with BREW directed SMS and network connections, including handset resets, trashing BREW network connections until re-start, incorrect signaling at the CDMA layer causing problems with the SMSC etc etc.
If indeed it is a VX6000 bug then I don't know what you can do in the short term as this handset is already released commercialy.
Do you have any other handsets you can try it on?

Lots of weird behaviour with BREW directed SMS and network connections, including handset resets, trashing BREW network connections until re-start, incorrect signaling at the CDMA layer causing problems with the SMSC etc etc.
If indeed it is a VX6000 bug then I don't know what you can do in the short term as this handset is already released commercialy.
Do you have any other handsets you can try it on?

The emulator emulates the Application Directed SMS, of course, so we don't see the problem there. The App works correctly.

The emulator emulates the Application Directed SMS, of course, so we don't see the problem there. The App works correctly.

We tried it on the A530 only to realize that App directed SMSs don't work via vtext.com. We don't have another handset on which to try the experiment.

We tried it on the A530 only to realize that App directed SMSs don't work via vtext.com. We don't have another handset on which to try the experiment.

I know in NYC metro area Verizon has not enabled BREW directed SMS support.

I know in NYC metro area Verizon has not enabled BREW directed SMS support.

Benjamin, this isn't commercially available in Verizon, yet. Application Directed SMS is only possible via test bit enabled phones and application directed SMS through vtext.com.

Benjamin, this isn't commercially available in Verizon, yet. Application Directed SMS is only possible via test bit enabled phones and application directed SMS through vtext.com.

We traveled to San Diego to demonstrate this problem and the SMS wakeup while already in the BREW app but disconnected worked 100% of the time. So it appears to be a problem with Verizon's switching software in the Bay Area and we'll discuss it with them. We'll also experiment to see whether it works or fails in other areas of the U.S..

We traveled to San Diego to demonstrate this problem and the SMS wakeup while already in the BREW app but disconnected worked 100% of the time. So it appears to be a problem with Verizon's switching software in the Bay Area and we'll discuss it with them. We'll also experiment to see whether it works or fails in other areas of the U.S..

We upgraded our phones to the new VX-6000 operating system (T60VZV06) and the bug has disappeared. Phones that we haven't yet upgraded still experience the bug. I wonder what else LG fixed in this release?

We upgraded our phones to the new VX-6000 operating system (T60VZV06) and the bug has disappeared. Phones that we haven't yet upgraded still experience the bug. I wonder what else LG fixed in this release?

Steve,
do you know how to determine the version of the OS running on this phone ?
Regards,
Ben

Steve,
do you know how to determine the version of the OS running on this phone ?
Regards,
Ben

Sure, Benjamin. On your phone, press MENU (left softkey) then 992.

Sure, Benjamin. On your phone, press MENU (left softkey) then 992.

Thanks Steve. So you sent the phones to LG to get the OS upgraded ?
Cheers,
Ben

Thanks Steve. So you sent the phones to LG to get the OS upgraded ?
Cheers,
Ben

You can walk into any Verizon store and the customer service counter folks should be happy to upgrade your OS. It takes about 30-45 minutes if no one is in front of you.

You can walk into any Verizon store and the customer service counter folks should be happy to upgrade your OS. It takes about 30-45 minutes if no one is in front of you.

I'm assuming that after this firmware upgrade, I'd need to send phone to Qualcomm to test enable it (again)? Is that correct?

I'm assuming that after this firmware upgrade, I'd need to send phone to Qualcomm to test enable it (again)? Is that correct?

No, that's not correct. Upgrading the OS leaves your data intact, including the test bit enabled.

No, that's not correct. Upgrading the OS leaves your data intact, including the test bit enabled.

Cool. Thanks again Steve.
-Ben

Cool. Thanks again Steve.
-Ben

Quote:No, that's not correct. Upgrading the OS leaves your data intact, including the test bit enabled.Thanks for the info!

Quote:No, that's not correct. Upgrading the OS leaves your data intact, including the test bit enabled.Thanks for the info!