search

robertoprato / bluecove

Automatically exported from code.google.com/p/bluecove
0 stars 0 forks source link

Midlet crack in WEME 2.0.2 #34

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?

 public boolean open(int mode,String addr ) {
        this.mode = mode;
        try {
            String url = "btspp://"+addr+":11";
            con = (StreamConnection) Connector.open(url);

            fo = con.openOutputStream();
            fi = con.openInputStream();
            return true;
        } catch ( IOException e ) {
            e.printStackTrace();
            owner.showMessage("Enviar","El servidor no responde al
servicio.",owner.STATE_MAIN);
            return false;
        }
    } 

What is the expected output? What do you see instead?
The midlet crack and exit.

What BlueCove version are you using (include build number for SNAPSHOT)? 
Bluecove 2.0.2

With WM 5 and WEME 5 & 6

¿How can debug or get system information in GameCanvas?

Thanks your

Original issue reported on code.google.com by quartoym...@gmail.com on 4 May 2008 at 4:05

GoogleCodeExporter commented 8 years ago 
There are test application 'bluecove-tester'. Can you run this app as MIDLet on 
your
mobile?  Can you start server using this app? Can you run discovery this this 
app?
Can the test app connect to Desktop....

Also please try the 2.0.3 bluecove version I fixed some IBM J9 (WEME) related 
problem
in the bluecove code to be java 1.1 compatible.

PS
 If there are some problem in a code you can only find them using emulator on Desktop
system.

 My recommendation also to try different JVM on you mobile. Do not start from MIDP
version since there are no way to debug it.

Original comment by skarzhev...@gmail.com on 4 May 2008 at 4:32

GoogleCodeExporter commented 8 years ago

Original comment by skarzhev...@gmail.com on 4 May 2008 at 4:34

GoogleCodeExporter commented 8 years ago 
I executed bctest.jar with bluecove-2.0.3-20080501.050231-69.jar.

J9 in pocketpc (Windows Mobile 5):
I get that the localdevice address is 00000000, and the local name is (null)

J9 in Linux (Ubuntu 8.04):
I get the localdevice and device friendly name. Is Ok

Original comment by quartoym...@gmail.com on 4 May 2008 at 7:55

GoogleCodeExporter commented 8 years ago 
The local name is (null) on WinCE all the time. There are no api in MS stack 
for this
name on CE.
Also since the device address is 000 then bluecove can't connect to BT API on 
your
mobile. If you done everything correctly e.g. installed widcomm or winsoc 
_ce.dll to
bin directory of your j9 installation then nothing I can do to help I only have 
for
tests Dell X30 with Win Mobile 2003. 

You don't even reported what is the device you are using. Search and ask in user
group to see if others been using the same device with bluecove.

Original comment by skarzhev...@gmail.com on 4 May 2008 at 8:30

GoogleCodeExporter commented 8 years ago

Original comment by skarzhev...@gmail.com on 10 Jun 2008 at 4:40