I have found that none (or every app i tried) of the available Series 60 applications will work properly on my 7650 - where a HTTP connection is required (using GPRS/WAP).
In order to work out why I have written some J2ME applications which finally allow this sort of functionality for me in my own software - and thought I'd share my experience. If this has been covered already - my apologies(!)
My WAP/GPRS browsing was working correctly on the real device however - and the setttings for my J2ME applications matched. Even though the example J2ME applications worked fine on the Emulator the moment I tried to run them on the real device I would just get errors.
I tried Nokia Tech Support in Australia as well as my Mobile Phone/GPRS providor - and they couldn't help me at all. They seemed also very new to these technologies and didn't really understand what I was talking about. I basically got nowhere.
I remembered however (from some previous work done with WAP) - that my Mobile Phone Company (Singtel/Optus in Australia) used GPRS Gateway products made by CMG. These products are designed for WAP content however and are defaulted to actually parse the WML content that passes through and only allow certain mime types (such as WBMP's and WMLS). Basically unless your content complies with these standards it will actually replace the content with an error message (even though it was able to source the request).
I have a feeling this is also a limitation for many people around the world. Whilst Gateways are configured to support the new .jad/.jar file types - many operators dont understand that people also want it for customized use where only specific raw data is downloaded (in applications like PocketTV for example) - and restrict all other content.
As a solution I would ask people writing apps to consider this issue for many of us, and implement the following workaround :
Bring your Raw data through packaged into a compliant WML,WMLS or WBMP file - and then parse for it within your application. (Remember that this is not just the extension required but the format OF DATA required).
Your Web server should also be configured to support the correct MIME-TYPES required for WAP content (such as text/vnd.wap.xml etc etc)..
For example your application could request the following WML page. This page would not be for browsing with your WAP browser - but rather disguised as valid content for the purpose of it getting through the GPRS gateway.
<p id="start">#### INSERT YOUR RAW TEXT DATA IN HERE #####</p>
<p id="moredata">#### INSERT OTHER RAW TEXT DATA IN HERE #####</p>
If you setup the correct encoding attributes in your WML file you can also bring through binary encoded data in this manner. Additionally - I believe you may be able to get away with shoving data inside a WBMP file (by having a correct header and using the pixel data area).
For downloading images however - GIF is normally supported and can be directly sent through most gateways. So for example if you were writing a Weather Report application, you could directly download a .GIF file - however the associated weather forecast data would need to be embedded into a WML file and parsed on your end.
Doing this has it's advantages - as the WML is XML - you can easily parse it to find the start/end tokens for your data. Alternatetively - simply searching for all text between <p id="start"> and </p> may be sufficient (just using the string object).
So - If you are writing applications please remember consider these workarounds - and maybe even make it an option inside your application - so those without these limitations can still download the raw data without the additional chars for the WML tags! (Nokia - also please consider maybe addressing this issue with your Application Style Guides)
Thanks - any comments welcome/appreciated!