Why would DRM content downloaded through bluetooth or IrDA not work?
It is handset dependent thing. On Nokia handset it shows File format Unknown error.. But on Sony Ericsson handsets, it would just work fine.
There is no work around to this because it is firmware specific thing.
I tried transferring a .dm file (created by wrapping a jpg through NMIT) with bluetooth and encountered a Unknown file format. Why does it not work?
I've similar problem with Carbide.j 1.5 and my N70 device. The forward locked midlet (*.jad & *.dm) generated by the tool doesn't install on device either over bluetooth or OTA. I've tested both my own application and the Boids sample midlet provided by the tool. Device seems to download the DRM archive successfully, but prints out an "Unable to install" message. Same applications without a forward lock install without problem. I suppose Nokia devices should accept at least DRM files generated by Nokia's tools.
I dont understand DRM Forward Lock, when I use a DRM packager I get 2 files, a meta-texfile *.dd and a contents file *.dm.
but if I use a 'obex-push'er (PUT) to a DRM protected Bluetooh Mobile I can only upload 1 file, so I choose a DM file, this file is not recognized and so I cant see the contents of that DM file on my Mobile.
How can you upload DRM Forward Lock File(s) via Obex Bluetooth?
I found a Obex Pusher on this site but thats on the nokia?!? And no a sample DRM Forward Lock File(s).
Does some1 have an executable that can run on WinXP PC with BT dongle?
And which Stack is used? And can you include example DRM Forward Lock File(s) (image or jar file).
I use MS BT stack & an example project of 32feet.net to push the files.