×

Discussion Board

Page 4 of 5 FirstFirst 12345 LastLast
Results 46 to 60 of 63

Thread: Known Issues

  1. #46
    Regular Contributor
    Join Date
    Aug 2005
    Posts
    192

    Re: Known Issues

    Looking into this a bit closer it seems like the error occurs when the image is 31x27 pixels exactly, has transparent pixels and is png 8-bit... really strange

  2. #47
    Registered User
    Join Date
    Mar 2003
    Posts
    4,105
    Technology: Bluetooth (JSR-82)
    Reported against: Series 40 3rd Edition
    Subject: 32-bit UUID with high-bit set fails
    Detailed description: If you do a service search for a 32-bit UUID or you receive a 32-bit UUID while searching for all service (search UUID = 0x0100L) and the highest bit of this UUID is set (for example 0x80000000L), then the service will not be present in DiscoveryListener.servicesDiscovered.
    Example: Search for 0x0100L on a remote device like a Sony Ericsson P1 (SJP-3, …) or a Sony Ericsson K850 (JP-7, JP-8, …) which have service with UUID 0x8e771301 (Sony Ericsson [SEMC] High Level Authentication [HLA]).
    Severity: Actually a 32-bit UUID is a bug already and should not be used very often, consequently this bug is not that important. Nevertheless, there is a bug in Series 40 as the same code works in all my Sony Ericsson and S60 devices. Furthermore, UUIDs like 0x7fffffffL work even in Series 40.
    Last edited by traud; 2008-02-05 at 09:26.

  3. #48
    Registered User
    Join Date
    Mar 2003
    Posts
    4,105
    Technology: Bluetooth (JSR-82)
    Reported against: S60 (verified on Nokia 6680)
    Subject: ServiceRecord DataElement (like Long) values are in Little-Endian
    Detailed description: Click…

  4. #49
    Registered User
    Join Date
    Oct 2007
    Posts
    19

    Re: Known Issues

    MIDlet.platformRequest("sms:" + phNo) does not work on Nokia 6500 (Serise 40 E3_FP1) Slider. On this request it throws ConnectionNotFoundException : Invalid URL.

    Has anyone encountered such problem ???

  5. #50
    Super Contributor
    Join Date
    Apr 2003
    Location
    USA, CA
    Posts
    7,191

    Re: Known Issues

    bharatpatel, in general you need to use WMA API for sending SMS messages. The MIDP spec allows phone manufacturers to implement support for other than tel and http, but it is by no means required to support sms, especially as there is a separate API for that.

    Hartti

  6. #51
    Regular Contributor
    Join Date
    Aug 2008
    Posts
    166

    Re: Known Issues

    Issue reported on e60 and n72 when we display system time works fine for gmt+1,2,3 but has problem if min field is there ie GMT+3:30 or GMT+5:30 or GMT+5:45 etc this considered as GMT+3 ,GMT+5 ,GMT+5 respectively

  7. #52
    Regular Contributor
    Join Date
    Jan 2008
    Posts
    387

    Re: Known Issues

    @bharatpatel85

    it will definately throw, use following code for it.

    void sendSms()
    {
    (t=new Thread(this)).start();
    }

    public void run()
    {
    MessageConnection conn=null;
    try{
    conn=(MessageConnection)Connector.open(url);
    TextMessage textMessage=(TextMessage)conn.newMessage(MessageConnection.TEXT_MESSAGE);
    textMessage.setAddress(url);
    textMessage.setPayloadText(msg);
    conn.send(textMessage);
    }catch(Throwable te){System.out.println("error in sending "+te);te.printStackTrace();}
    finally{
    try{
    conn.close();
    }catch(Exception e){System.out.println("error in closing "+e);}
    }
    }
    Thanks and Regards,
    Manjul.

  8. #53
    Registered User
    Join Date
    Dec 2004
    Posts
    369

    Re: Known Issues

    Hi ron/traud sorry if i double post this but this is kinda urgent to me...

    I have came across the following problem.
    when i try to create a player using file system path to file as the URI scheme if the path length is very long the application exits (with no error/exception that are catchable , i tried catch throwable).
    when i call
    Manager.createPlayer("file:///e:/realyrealyrealyrealyrelayrealyrealyrealyrealyraelyrealyrealylongdirname/video.3gp");
    my application (and my guess the jvm) crashes with no exception thrown.
    when i use the same file and my path is shorter it works with no prolbem like so
    Manager.createPlayer("file:///e:/shortdir/video.3gp");

    i came across this problem on nokia 6120 & e71
    my 6120 firmware version is v06.01
    02-09-08
    rm-243

    i've tried the same on a friends n95 and it seem to work perfectly...
    (updating firmware is not an option cause this should go public and i cant force normal users to update firmware)

    can you cofirm that this issue is indeed as i described and perhaps already known/unknown and has a work-around/solution?

    (i know i can open the file perfectly well if i open it by myself with fileconnection using Connector and i can then pass the inputstream to Manager.createPlayer but wouldnt it crash some devices due to memory usage? cause i know when using Mananger.createPlayer with an inputstream it reads the inputstream in full and load it to memory and my video can be very big in size).

    thanks

  9. #54
    Registered User
    Join Date
    Feb 2009
    Posts
    1

    JVM or JIT breaks application logic

    Technology:
    JVM / JIT

    Reported against:
    N5800, E52, probably other recent S60 devices

    Subject:
    JVM or JIT breaks application logic

    Detailed description:
    There appears to be an error in the JIT employed on the more recent S60 devices. A fairly simple series of if-statements will malfunction on the aforementioned devices. It seems one of the conditionals in the following code is factored out by some optimizing technique.

    Reproduce:
    Create a MIDlet which continously invokes the following method, compile it without obfuscation and run.

    Code:
      private final int FULL = 100000;
    
      private final int HALF = 50000;
    
      public boolean test(int num) {
        num %= FULL;
        
        if(num<0) {
          num = -num;
          if(num > HALF)
            num = FULL - num;
          return num <= HALF;
        }
        if(num > HALF)
          num = FULL - num;
        return num <= HALF;
      }
    The method will always return true on emulators, s40 devices, older s60 devices and other device brands. N5800, E52 and probably other recent S60 devices such as N97 will return false on about 1/3 of the invocations.

    A test MIDlet as described may be downladed as a Netbeans project: http://j2me.no/N5800Test.zip

    - Martin

  10. #55
    Registered User
    Join Date
    Mar 2003
    Posts
    4,105
    Not sure if this thread is still active, anyway a new interesting one for Series 40 and its javax.bluetooth package.

  11. #56
    Registered User
    Join Date
    Mar 2009
    Location
    Gdansk, Poland
    Posts
    139

    Possible bug with Thread.join()

    Filed against:
    5500 Sport, 5700 Xpress, 6110 Nav, 6120 Classic, E51, E61, E63, E65, E66, E70, E71, N73, N80, N81, N82, N90, N95

    Devices that work correctly:
    3120, 5230, 5320 Xpress, 5800 Xpress, 6710 Nav, 5630 Xpress, E52, E55, E71x, E72, N78, N79, N85, N96, N97, N97 mini

    Details: on the 'non-working' devices, Thread.join() appears to always take at least 1 second to complete.
    On 'working' devices, Thread.join() returns immediately as soon as the thread being joined() exits.

    More details: http://discussion.forum.nokia.com/fo...d.php?t=188357

    Midlet to verify the issue:
    PHP Code:
    import javax.microedition.midlet.*;
    import javax.microedition.lcdui.*;

    public class 
    Join extends MIDlet implements CommandListenerRunnable {

        private static final 
    Command EXIT = new Command("Exit"Command.EXIT, 1);
        private 
    long startTime;
        private 
    Form form;

        public 
    void startApp() {
            if (
    form == null) {
                
    form = new Form("Join");
                
    form.addCommand(EXIT);
                
    form.setCommandListener(this);
                
    Thread t = new Thread(this);
                
    startTime System.currentTimeMillis();
                
    t.start();
                try {
                    
    t.join();
                } catch (
    InterruptedException e) {
                    
    // ignore
                
    }
                
    time("Thread death");
            }

            
    Display.getDisplay(this).setCurrent(form);
        }

        public 
    void pauseApp() {
        }

        public 
    void destroyApp(boolean unconditional) {
        }

        private 
    synchronized void time(String s) {
            
    form.append(": " + (System.currentTimeMillis()-startTime) + "\n");
        }
        
        public 
    void commandAction(Command cmdDisplayable disp) {
            if (
    cmd == EXIT) {
                
    notifyDestroyed();
            }
        }

        public 
    void run() {
            
    time("Enter run()");
            try {
                
    Thread.sleep(100);
            } catch (
    InterruptedException e) {
                
    // ignore
            
    }
            
    time("Exit run()");
        }

    On 'working' Nokia devices (as well as in Sun's emulator, and all competition phones I've checked) , you're going to see something like
    Code:
    Enter run(): 10
    Exit run(): 100
    Thread death: 100
    On 'non-working' devices, you're going to see numbers close to
    Code:
    Enter run(): 10
    Exit run(): 100
    Thread Death: 1000
    Last edited by Utumno; 2009-12-14 at 08:14.

  12. #57
    Super Contributor
    Join Date
    Jun 2003
    Location
    Cheshire, UK
    Posts
    7,395

    Re: Possible bug with Thread.join()

    I have an issue, known at least to me, with the high level UI component in S60 5th Ed. Read my other thead for details; I'm posting here in the hope of getting other people to look at the thread, and perhaps get more details of the actual issue (or, being hopeful, a workaround).

    Graham.

  13. #58
    Registered User
    Join Date
    Dec 2010
    Posts
    17

    Re: Known Issues

    Hi,
    I am developing an application which has a form filled with custom items. The problem i am facing is if the number of items exceeds the number displayed on the screen and if i scroll up or down using the scroll bar the application has a white line at the edge of the screen where the last displayed custom item was. Then the rest items are displayed. I am not handling any traversals on custom item so it is being automatically handled in the form. Any idea what is causing this?

    http://www.my-image-host.com/show.ph...00036.jpg.html
    http://www.my-image-host.com/show.ph...00034.jpg.html
    Thanks and Regards,
    Abhijeeth

  14. #59
    Super Contributor
    Join Date
    Apr 2003
    Location
    USA, CA
    Posts
    7,191

    Re: Known Issues

    Abhijeeth, no comment on the bug, but the links in your message are broken

    Hartti

  15. #60
    Registered User
    Join Date
    Dec 2010
    Posts
    17

    Re: Known Issues

    Please find the image that i rehosted.

    Thanks and Regards,
    Abhijeeth

Similar Threads

  1. GCCE issues
    By apsaarin in forum Symbian Tools & SDKs
    Replies: 18
    Last Post: 2010-06-18, 13:13
  2. 6820 memory issues
    By jennydeng in forum Mobile Java General
    Replies: 2
    Last Post: 2009-09-15, 18:33
  3. S60 Known Issues
    By Nokia Ron in forum Symbian
    Replies: 68
    Last Post: 2008-04-25, 07:48
  4. Series 60 graphics and sound issues
    By Teh_Architect in forum Mobile Java Media (Graphics & Sounds)
    Replies: 0
    Last Post: 2005-08-08, 11:03
  5. WAP Push Viewer issues on 3650
    By wapian in forum Digital Rights Management & Content Downloading
    Replies: 2
    Last Post: 2003-10-14, 07:49

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
×