Printable View
Hi,
I am developing a video streaming application in Series 40 SDK 2.0.
I use platformRequest method to call and play the RTSP video.
The problem is everytime i call RTSP link, the app always prompt to open browser. Can we hide the platformRequest prompt, so users can browse and play video smoothly?
Will appreciate your help.
Hi ickroo,
You must have your MIDlet signed with manufacturer or operator, inorder to bypass the default MIDP security prompts.
[QUOTE=ickroo;907050]Hi,
I am developing a video streaming application in Series 40 SDK 2.0.
I use platformRequest method to call and play the RTSP video.
The problem is everytime i call RTSP link, the app always prompt to open browser. Can we hide the platformRequest prompt, so users can browse and play video smoothly?
Will appreciate your help.[/QUOTE]
Unless untill the application is signed , for sure you will get the popups thrown out by the device os .
The reason is that unless you sign the application by a trusted CA . The device considers the application as unstrusted one .
For further information about the signing the application , you can go through the given link
[url]http://www.developer.nokia.com/Resources/Library/Java/#!developers-guides/security/midp-security/signing-a-midlet-suite.html[/url]
Hi all,
thank you for your answer.
I've read that signing only remove popups which related with the API permissions in the JAD file.
Could you show me any information about API permissions to remove rtsp popups?
--
Regards,
Ray Rizaldy
When you sign the app you can specify which kind of api-calls are OK, so that you wont be getting a pop-up (even though, if I remember correctly, some pop-ups will be shown a first time only!)...
The rtsp call will trigger a pop-up because it is making use of networking (which might or might not result in additional costs if you dont have a data plan)...
So after having white-listed the connectivity API during signing you shouldn't be seeing those popups, unless its one of the one I was mentioning before which will still be shown once...
You also need to educate the user to set the required permissions for the app - manually via settings on first launch of the app - as on some devices, signing do make the permission available to set and do not set them automatically.