Samsung underlined its consumer credentials at the Mobile World Congress in Barcelona last week with the announcement from NXP Software that it had integrated its LifeVibes MusicPlayer into Samsung’s new SGH-F250 mobile phone. This enables high-end MP3 functionality on phones that are not themselves at the cutting edge.
Samsung made a splash at the Mobile World Congress in Barcelona last week, showcasing its ongoing ability to connect to consumers’ lifestyle choices in cellular phones.
One of the most compelling examples of this was also one of the least visible, coming through an announcement by NXP Software that it had integrated its LifeVibes MusicPlayer into Samsung’s new SGH-F250 mobile phone.
A DJ at the NXP sand at the Mobile World Congress demonstrates
Described as a complete, pre-integrated middleware solution, NXP Software’s MusicPlayer supports local playback, downloading and streaming, and offers dedicated features for easy navigation. A multi-standard solution, it supports both Windows Media and 3GPP compliant playback. This lowers development risks and costs and speeding time-to-market.
The Samsung SGH-F250 music phone
The MusicPlayer’s focus on easy access to content and synchronization is designed to enable an enjoyable, seamless user experience. It supports both Windows Media Digital Rights Management (WM DRM) and open-standards OMA DRM. Compatibility with Microsoft’s Media Transfer Protocol (MTP) provides access to a vast choice of songs and playlists, along with their associated metadata. The software is also compliant with Microsoft’s PlaysForSure and Napster OTG, guaranteeing that any compatible content will play on the phone.
LifeVibes MusicPlayer provides comprehensive navigation controls ,including: start, stop, pause, jump and next song. By supporting metadata, it also ensures all songs appear in the navigation regardless of their source or where they are stored.
The Samsung SGH-F250 music phone can store up to 1,500 tracks in various formats.
email this to a friend tt tt printer friendly version
“,”body-href”:””}]