×

Discussion Board

Results 1 to 15 of 15
  1. #1
    Registered User
    Join Date
    Apr 2003
    Posts
    5

    Real Connection Extremely slow on Nokia 7650

    I have tested the application on the J2ME wireless toolkit and deployed it on the mobile phone 7650.

    However, while running it i've found that the connection failed to connect to my home tomcat server where stores servlet. I donno what is the problem, or its a bug of nokia series phone?

    Also I've found that even if i deploy the sample applications which are provided by J2ME wireless toolkit on the phone, the connection also does not succeed.

    What's the problem? I urgently need to answer and solution as i am hurrying to hand on the project to my supervisor.

  2. #2
    Regular Contributor
    Join Date
    Mar 2003
    Location
    Canada
    Posts
    101
    If you're using a WAP access point, try switching to an Internet access point with a gateway IP address of 0.0.0.0.

    Also make sure that you make the HTTP connection on a separate thread.

    Try using Reqwireless WebViewer on your device to check whether the issue is with your code or your connection settings. If WebViewer works, there's likely a problem with your code; if not, there's likely a problem with your connection settings.

  3. #3
    Registered User
    Join Date
    Apr 2003
    Posts
    5
    i've tested the webviewer and found that there is no problem on the connection setting.

    However, i've tested the program on the emulator and contains no error.

  4. #4
    Regular Contributor
    Join Date
    Mar 2003
    Location
    Munich, Germany
    Posts
    76
    Hi LiamQ,

    about your suggestion to use another thread for the HTTP connection: I have nothing but trouble with that (see my other posts in this forum).
    How is the HTTP working for you. No problems? Maybe you have any tips you can share with us on how to get _stable_ http downloads on the 7650.

  5. #5
    Registered User
    Join Date
    Apr 2003
    Posts
    5
    thanks!
    i think the solution of using new thread works for me. Now the application can work but i have to change the code. Also i need to set a variable in order to let the run() fuction know what network function i need to use. It seems quite inconvenient for us.................

    Actually is it a bug of Nokia 7650? If upgrading the firmware can the problem be solved?

  6. #6
    Regular Contributor
    Join Date
    Mar 2003
    Location
    Canada
    Posts
    101
    Hi Juggle4Evr1,

    I haven't found any stability problems with HTTP on the Nokia 7650, but I've never been able to test on this device since it doesn't work in my part of the world. However, I work for Reqwireless, and we have many Nokia 7650 users of our WebViewer and EmailViewer MIDlets, and we haven't heard of any stability complaints.

    We encourage 7650 users to use an Internet access point instead of a WAP access point since HTTP over a WAP access point seems not to work on many 7650s. So if you're using a WAP access point, I would try switching to an Internet access point with a gateway IP address of 0.0.0.0.

  7. #7
    Registered User
    Join Date
    Apr 2003
    Posts
    5
    Actually I am just a beginner about writing J2ME and the main issus of the problem i mentioned is due to the bug contained in the phone i think.

    For all 7650 users, if you really want your program be running smoothly. Be sure to seperate the thread between the main operation and the network operation. This will solve a lot of problem about networking.

    I donno whether upgrading the firmware helps the condition or not. But I now can run my program smoothly, just by putting all the network operation into another thread, and it takes me a whole night to complete the whole amendment. My God..............

    Anyway, I will try to upgrade the firmware tomorrow at nokia support center and see if it can help anything about the problem.

  8. #8
    Regular Contributor
    Join Date
    Mar 2003
    Location
    Munich, Germany
    Posts
    76
    Hi LiamQ,

    you saved my life (I think). I'm now using a connection without WAP-gateway and it seems to work perfect.

    Thank's a lot for that hint!!

    It also had the effect that the data transfer is much cheaper because when using the WAP gateway, I saw in my webserver log that for each HTTP request there was a different IP address. That would mean that the connection is closed after each request and reopened again for the next request. T-D1 in Germany charges a full 10kB block for each new connection even if you transmit only 1 kB.

    Without using the WAP-gateway I always get the same IP address (within a time frame of about 1.5 minutes and this looks mch better) which means that the whole 10kB of the block can be used.

  9. #9
    Registered User
    Join Date
    Mar 2003
    Posts
    16

    using WebViewer with orange.fr ?

    Liamq says :
    "Try using Reqwireless WebViewer on your device to check whether the issue is with your code or your connection settings. If WebViewer works, there's likely a problem with your code; if not, there's likely a problem with your connection settings."

    However, I tried WebViewer with my orange.fr connection settings, which work perfectly well with other midlets (for example HTTPGetter from midlet.org). The strange thing is :
    Setting the gateway IP to 0.0.0.0 would not work, neither with WebViewer nor with any other midlets.
    Seting the IP to 192.168.10.100 (wap gateway) would make HTTPGetter or midlets I wrote work but not WebViewer.

    HTTPGetter can be downloaded at :
    http://midlet.org/repository/spruce/httpgetter/SpruceHTTPgetter.jad

  10. #10
    Regular Contributor
    Join Date
    Mar 2003
    Location
    Canada
    Posts
    101
    When you set the gateway IP address to 0.0.0.0, you need to be using an Internet access point rather than a WAP access point. gerodol, were you using an Internet access point with 0.0.0.0?

  11. #11
    Registered User
    Join Date
    Mar 2003
    Posts
    16

    in response to liamq

    Liamq,

    thanks for the quick answer.

    I was using the "orange.fr" access point, which is the one mentionned at http://reqwireless.com/download-webviewer.html

  12. #12
    Regular Contributor
    Join Date
    Mar 2003
    Location
    Canada
    Posts
    101
    gerodol, did you configure the gateway IP address to be 0.0.0.0?

  13. #13
    Registered User
    Join Date
    Mar 2003
    Posts
    16
    liamq,

    As I said in my first post in this thread,
    with orange.fr, setting the IP to 0.0.0.0 would result in either case (WebViewer or other midlets) into a -20015 error.
    With IP=192.168.10.100 some midlets work (but not WebViewer).

    Is there a "howto" somewhere about how to configurate nokia phones for internet with various operators ?

    AG

  14. #14
    Regular Contributor
    Join Date
    Mar 2003
    Location
    Canada
    Posts
    101
    I don't know of a howto other than what's written on the download-webviewer page.

    I think some plans from mobile operators don't support TCP/IP. You may need to contact your mobile operator to get full Internet access.

    When you try using 192.168.10.100 with WebViewer, what error do you get? Are you using WebViewer 3.0 or an earlier version?

    (Sorry for the 0.0.0.0 question... I must have forgotten to read before replying.)

  15. #15
    Registered User
    Join Date
    Mar 2003
    Posts
    16
    Thanks for your answer.
    With WebViewer I am getting a "503" error. More precisely I get an alarm :
    Unexpected server response : 503 Wap Gateway Response : application/vnd.wap.wmlc;Charset=iso-8859-1

    I just downloaded the program from your website, the version is 3.0.

    The point is, as far as I understand, "standard" orange france subscribers only have access to orange.fr (for wap) and orange.acte (for mms) access points. When I use either of these APN with IP=0.0.0.0 with any program I obtain error = -20015 .
    When I use orange.fr with IP=192.168.10.100, it works with several midlets. But I have seen that the gateway both transforms the headers (eg : you specify connection=close, the server sees connection=keep-alive) and suppresses headers it does not know of.

    AG

Posting Permissions

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