Nitrio Mobile Blog

Click Here to see a walkthrough demo of Nokia Podcasting
__________

Some podcasters are wondering why the “Content may not play on your device” warning is popping up for normal audio files. Our development team gives the answers:

The determining factor for whether or not the podcasting app displays this warning is actually not the file extension, but the mime type that is provided in the enclosure tag. (We only use the file extension for display on the UI.)

Whatever content you use, just make sure you provide a MIME type that is supported in our phones.

A complete list of Browser MIME types in Nokia GSM Devices can be found here:
http://www.forum.nokia.com/info/sw.nokia.com/id/444aa596-38d4-473c-81ed-657da920d163/Browser_MIME_Types_in_Nokia_GSM_Devices_v1_8_en.pdf.html
(look in Chapter 7 for S60 3rd edition).

One exception to this is MP4 (video and audio mp4 content). Because MP4 is a container format and we have no idea if the content within the MP4 container will be played correctly, for audio/mp4 or video/mp4 content we display the warning “might not display properly” and don’t auto-download these episodes.

If your audio show is in aac format, the best MIME type would be “audio/aac” - that doesn’t display any warnings.

And when creating an audio podcast specifically for a mobile audience, I would recommend to use AAC (or better yet, eAAC+) because of the smaller filesize and/or better quality at the same file size, compared to MP3.

The Nokia Music Manager from the Nokia PC Suite (download here) is able to convert your mp3 files into eAAC+.

NOTE: If you want your video podcast optimized for mobile (size, playback compatibility and no warning), use the format 3gp. (Most compatible devices are able to play frames per second (fps), newer devices like N95, N81, N93, etc can play 30 fps)

HACK!
OK….I realize you shouldnt need a workaround, but if you know your video format is compatible with the Nokia devices and you want to make sure the warning message doesnt come up, here is a way to “cheat”.

If you have an MP4 video file in a format that for sure plays on our devices, you can set file extension to “.mpeg” and the mime type in the enclosure to “video/3gpp” to avoid that warning message and to allow auto-downloads … a bit hacky, but works nicely. Please note that the .mpeg extension is important, too.

Here’s an example entry from an RSS feed:

Original post by jan

Click Here to see a walkthrough demo of Nokia Podcasting
__________

Some podcasters are wondering why the “Content may not play on your device” warning is popping up for normal audio files. Our development team gives the answers:

The determining factor for whether or not the podcasting app displays this warning is actually not the file extension, but the mime type that is provided in the enclosure tag. (We only use the file extension for display on the UI.)

Whatever content you use, just make sure you provide a MIME type that is supported in our phones.

A complete list of Browser MIME types in Nokia GSM Devices can be found here:
http://www.forum.nokia.com/info/sw.nokia.com/id/444aa596-38d4-473c-81ed-657da920d163/Browser_MIME_Types_in_Nokia_GSM_Devices_v1_8_en.pdf.html
(look in Chapter 7 for S60 3rd edition).

One exception to this is MP4 (video and audio mp4 content). Because MP4 is a container format and we have no idea if the content within the MP4 container will be played correctly, for audio/mp4 or video/mp4 content we display the warning “might not display properly” and don’t auto-download these episodes.

If your audio show is in aac format, the best MIME type would be “audio/aac” - that doesn’t display any warnings.

And when creating an audio podcast specifically for a mobile audience, I would recommend to use AAC (or better yet, eAAC+) because of the smaller filesize and/or better quality at the same file size, compared to MP3.

The Nokia Music Manager from the Nokia PC Suite (download here) is able to convert your mp3 files into eAAC+.

NOTE: If you want your video podcast optimized for mobile (size, playback compatibility and no warning), use the format 3gp. (Most compatible devices are able to play frames per second (fps), newer devices like N95, N81, N93, etc can play 30 fps)

HACK!
OK….I realize you shouldnt need a workaround, but if you know your video format is compatible with the Nokia devices and you want to make sure the warning message doesnt come up, here is a way to “cheat”.

If you have an MP4 video file in a format that for sure plays on our devices, you can set file extension to “.mpeg” and the mime type in the enclosure to “video/3gpp” to avoid that warning message and to allow auto-downloads … a bit hacky, but works nicely. Please note that the .mpeg extension is important, too.

Here’s an example entry from an RSS feed:

Original post by jan

Click Here to see a walkthrough demo of Nokia Podcasting
_______________

I ran across this gem from The PodLounge while surfing the internet.

If anyone else out there is developing things that work with Nokia Podcasting, please let us know. Cool stuff like this puts a smile on my face.

From The PodLounge Forum:

For those of you with a Nokia mobile, the Nokia Podcasting Application is a real treat.

What’s more - you can easily set The PodLounge to be your directory of choice for podcast searches:

Within the application go to: Options> Settings> Connection> Search Service URL and type in the following URL:

http://mobile.thepodlounge.com/nokia_search.php?q=#

____

By following the above instructions, the next time you use the SEARCH feature, it will utilize ThePodLounge’s directories. (Current default is from our friends at www.DigitalPodcast.com)

The ability to manually change your default Search directory is another way to personalize your mobile podcasting experience to get the content most relevant to your needs. Thanks to the PodLounge for offering this.

You can download Nokia Podcasting from the link above or click here to get detailed instructions.

Original post by jan

Hello,

I’ve been silent lately and now I can share why: I changed jobs at Nokia and joined the Mobile Web Server team. This means I won’t be blogging here but instead I created (well, Phil helped a LOT) a new blog and it’s called - (drums) - Mobile Web Server Blog.

I want to thank you all of my readers, fellow bloggers, mom and John Cleese in particular for the fun times so far. I hope you check out my new blog as well and stick around if you find it’s worthy.

-Jukka

Original post by Devin Balentina

I read over on N-Gage Future Watch that the Nintendo Wiimote controller could be used to control N95 (N95 runs on S60 3rd Edition Feature Pack 1). Since I have a Wii at home I was pretty excited about the possibility of using my Wiimote with my S60 3rd edition FP1 devices. A group of university students created a Wiimote driver for S60 called WiiConnect, that allows a Wiimote and an S60 3rd edition FP1 device to connect and communicate with the Wiimote via Bluetooth. The students also made a motorcycle racing Java game called WiiRider that communicates with the Wiimote and lets you control the racer using the Wiimote as a steering wheel. The accelerometer in the Wiimote is used to measure the movements and if you hit any cows or logs in the game the Wiimote vibrates. For those of you that are curious how this was done the sourcecode is available for both the S60 Wiimote driver and the Java game. The download and further description of the game are available from Symbian Resources.

I brought my Wiimote into work and tried it out with the N95. It worked really well! In the WiiConnect driver there is even a test mode to activate the vibrate and LEDs on the Wiimote or view X, Y, Z coordinates of the Wiimote. The only part of the Wiimote that I did not see utilized was the speaker. Audio from the game could have been played from the Wiimotes speaker making the game even more interactive. I showed several of my coworkers and most said that it was cool. A couple of guys on the software integration team were especially interested, they said maybe the Java game could be modified to take input from the accelerometer in the actual S60 device instead of the Wiimote. Accelerometers are in many S60 devices (N95, N93i, N93, etc.), mostly used for detecting if a landscape or portrait photo is being taken with the camera. This would mean that you could control the game by rotating the S60 device. I think that using an accelerometer in more games would be a great option, especially in racing or 2D shooting games to control the car or ship. I hope that more game developers look at this project and see what is possible. Maybe we’ll see more S60 games in the future using the Wiimote as a controller.

Original post by Devin Balentina