Tag: Blackberry smartphone

Using your smartphone or tablet with your network-attached storage

Why use your smartphone or tablet with your NAS

There are times when you want to upload or download files from your network-attached storage device using your smartphone or tablet computer. Examples of this include offloading files from a low-capacity device, through making media that you took or acquired through your device available at all times from your DLNA-equipped NAS to simply backing up data held on your device.

Of course, you may simply treat that NAS simply as a network transfer point for your data. Examples of this may include working with documents that you start on an iPad and want to complete on your regular computer or conceptual “rough-shot” pictures that you take you your phone’s camera and want to work with further using Photoshop and other software on your computer.

How is it done

But how am I able to do this with my network-attached storage and my mobile devices? Some network-attached storage devices may use a Web front for the file collections where as others may implement certain extensions to DLNA for uploading and downloading some media files. This latter situation is infact a long-term goal for the DLNA Home Media Network, especially when it comes to shifting or syncing multimedia files like music or images.

These environments don’t necessarily provide a consistent or ideal user experience for the mobile device user. This can typically be due to a Web front that is optimised for desktop use only to DLNA server and client apps not offering the proper sync or file-transfer functionality.

SMB file-manager apps

The preferred method that I would use is SMB/CIFS network file handling which every network-attached storage device supports thanks to Linux’s SAMBA software. Even the USB-linked file servers that are an increasing part of high-end routers like the Freebox units do support SMB as well as the Internet HTTP and FTP file transfer protocols. This has been a standard for regular computing devices with the Microsoft Windows Platform since Windows For Workgroups 3.11, then was exposed to Linux regular computers through SAMBA and has been exposed to the Apple Macintosh platform since MacOS X.

The platform-based mobile devices now can join the SMB party through the use of SMB-enabled file-manager apps. These are typically low-cost or free apps that expose the mobile device’s file system and the SMB file shares (entry points) made available by computers or network-attached storages. Some of them have file-viewer functionality for file types not supported by your device’s file handlers.

iOS

Intuitive Commander (App Store – $0.99)

FileBrowser (App Store – $4.49)

Syncsellence (App Store – $5.49, free limited version App Store)

Android

ES File Explorer – I use this on my phone (Android Market)

File Expert (Android Market)

File Manager (Android Market) / File Manager HD (Android Market) – Rhythm Software

Blackberry

File Expert (Blackberry App World – US$1.99)

File Manager Pro (Blackberry App World – US$4.99) – Terra Mobility

ArrangeIt File Manager (Blackberry App World – US$1.99) – Conceptual Designs

The various app stores for the popular mobile-device platforms will list more of the file manager apps with SMB file transfer and you can find them using the terms “SMB file transfer” in your search query.

It is also worth noting that your NAS’s vendor may offer file-transfer apps for their device on the iOS and/or Android platforms so you can transfer the files to their device. These programs may also work with the remote-access functionality that some of the consumer and SMB NAS units provide, thus keeping login credentials for the devices and streamlining the remote-access experience.

Other issues worth highlighting

iTunes-purchased content

You may have problems copying content that you purchased with iTunes on your iPhone or iPad directly to the NAS due to Apple’s setup for these devices. But they have improved the iTunes and iOS setup to allow a user to download the purchased content to an instance of iTunes run on a regular computer even though they purchased it on the iOS device. This works best if the regular computer’s iTunes library is referencing the NAS in question.

People who use iOS platform devices that aren’t updated to iOS 5 will need to tether the device to their iTunes-enabled regular computer. Then they will need to use the “Transfer Purchased Content” option in iTunes to copy the content they bought on the device to the regular computer or NAS.

It will also be important to make sure that audio content is downloaded as MP3 files rather than protected M4A files.

One way that Apple can work this situation out better is to implement read-write ability to iTunes (DAAP) servers for the iPod media-management app in their iOS platform. Here, the software could then support improved “offload” functionality. This may not come about due to Apple’s investment in and their fanbois’ preference for the iCloud as a large-capacity storage service.  But practically-minded Apple enthusiasts could place more value on a NAS as an extra-capacity data store so they know where their iTunes content is all the time.

File-transfer operating conditions

When you transfer files between your mobile devices and the NAS, make sure that you have a strong Wi-Fi signal at your mobile device and that the device has sufficient battery strength. This could be achieved through having the device connected to its charger while the transfer goes ahead.

NAS setup conditions

If you are transferring media files to the NAS, you would need to transfer them to the media folders that are referenced by the media-server software on that device. This may be made easier by using the file manager software’s “bookmark” or “favourites” options to point to the start of the NAS’s media folder tree.

It is also worth keeping other personal and workgroup shares on the NAS simply for backup or transfer purposes and referencing these with your file-manager app.

Conclusion

Once you are able to know that you can use the SMB file transfer method for moving data between your NAS, tablet and smartphone, you can see more value out of these mobile-computing devices.

What would you choose for your next touchscreen smartphone?

There are now three major touchscreen smartphone platforms that are available for the choosing – what would it be.

Hi everyone!

Your mobile phone contract’s up or you are about to consider moving from prepaid service to a regular mobile phone service. It’s now time to consider one of those new touchscreen smartphones.

Would you go for an iPhone or one of the new platforms – the Android or the Windows Phone 7? Would you also jump carrier if your desired phone platform or handset wasn’t provided by your current carrier?

Please leave a comment on this site about what you would consider choosing for your touchscreen smartphone. If you are following this site through its Facebook page, you can leave a comment on the Wall after the post.

Showdown on the handheld front

Two years ago, there was very little activity concerning the handheld PDA and smartphone front save for a few devices based on the Symbian S60 / UIQ platform and Windows Mobile (CE) platform.

Then Apple brought their touchscreen-enabled all-singing all-dancing iPhone on the market and businessmen became addicted to Research In Motion’s Blackberry smartphone with push e-mail functionality. Now Nokia (Symbian S60), Google Android and Microsoft have jumped on the same bandwagon as these previous companies. In the case of Nokia and Microsoft, they have released handset designs based on the iPhone-style “touchscreen” model as well as a QWERTY-style keypad. Some have even designed a handset that works sideways and uses a pull-out QWERTY keyboard. As well, Google had built up the Android Linux distribution for smartphone applications and a few manufacturers are releasing smartphones bast on this platform; while Palm, known for the classic “Palm Pilot” PDA, have come back from the dead with the Palm Pre smartphone platform.

This had stirred up things very significantly with the contract-driven high-end smartphone market. 

A new expectation was required for this class of device in the way they operated, the features they came with and how the additional software that extends their functionality is marketed. The devices will have 3G (or better) cellular voice and data interface, 802.11g WPA2 Wi-Fi networking, Bluetooth connectivity while being capable of working as a digital video camera, phone, portable media player, personal navigation unit and Internet terminal at least. Additional programs will be typically sold or provided through a PC-based or over-the-air application store hosted by the device’s manufacturer or platform provider.

As part of this showdown on the smartphone front, handset designers, operating-system and applications developers will start to develop very interesting handsets and handheld applications. The handset designers and operating-system developers will end up at the point which was common for consumer electronics in the 1970s and 1980s where manufacturers pitted themselves against each other to design the best product and as models evolved, the features that were in the top-end model gradually appeared on midrange and low-end models. Mobile service providers will also have to provide cost-effective mobile service plans which consider increased data usage on these devices as they become work and lifestyle information terminals for their users.

This could lead to inclusion of digital radio and TV reception in some of the models; 802.11n Wi-Fi networking; OLED user displays, improved battery runtime on “full-feature” use; and the like.

As far as applications are concerned, developers who write handheld applications, whether operating as a dedicated program or as a front-end to a Web page, will need to make the applications suit the different platforms and application stores. This may be easier for the Microsoft and Symbian platforms because the developer can have the option of providing the application through their Web site, a competing application store like Handango, or a mobile phone operator as well as the official application store for the platform.

There is a risk that certain features will be missing from the smartphone market during the smartphone platform showdown. One will be the support for WPS “quick-setup” functionality for Wi-Fi networks. These devices really need to benefit from this technology – how could you enter a WPA passphrase that is “security-ideal” in to a phone with a 12-key keypad or “picking through” a small QWERTY keypad. As well, most of the desireable wireless routers and access points that are being released at the moment are now equipped with WPS, These phones should have support for WPS, preferably as part of the operating system’s Wi-Fi functionality, but at least as a reliable application that the user downloads to the device for free.

As well, DLNA media-management support should be available across all of the platforms, preferably as a playback and download (to local storage) function and a media control point. Similarly, the phone could be set up to act as a media server so that pictures taken with the phone’s camera can be shown on larger screens. At the moment, Symbian is providing the functionality native to their S60 3rd Edition platform and third parties, mostly hobbyist developers, are developing implementations for use on the Apple iPhone and Windows Phone platforms.

It will be very interesting over these next few model years as we observe mobile phone manufacturers, smartphone operating-system developers, independent application developers and mobile phone service providers grapple with this new reality.