fMobi gets updated to v1.2b – updated to v1.2.1

fMobi gets updated to v1.2b - updated to v1.2.1 1
Recently reviewed Facebook client for Symbian^3, fMobi, has received a major update today from v1.2 to v1.2b. The newer version brings:

Advertisements
  • Back button
  • Searches: Feed, Places, Events, Groups, Friends, Pages
  • Fullscreen photo viewing
  • “User Agent fix”
  • Places to support non satellite positioning methods
  • Recent checkins
  • Nokia Pure font
  • Share link
  • Links are clickable in feeds/comments/chat
  • Fullscreen view
  • New sounds for alerts
  • Time to chat messages
  • Refresh button for status and checking for new comments
  • New settings: Enable T9 (then you have the last word missing bug), Louder sounds, Font size
  • UI fixes
  • Bug fixes

fMobi gets updated to v1.2b - updated to v1.2.1 2
I have the update installed and running on my Nokia E7 already, and everything seems to work fine, except for the following:

– the Chat menu displays a blank screen; no users or chats are displayed.
– When you select the Dark theme, it is not persistent. Shutting down and restarting the app returns it to the Light theme.

Update 1 (31st July): The above issues don’t happen if you uninstall the previous version first then install the new version clean. Be sure to uninstall any existing versions from your device first.

This updated version is significant in almost everyway, enhancing usability and bringing additional features and benefits.

Update 2: (31st July) A bug fix has been released as version v1.2.1

Download fMobi v1.2b.

Advertisements

0 thoughts on “fMobi gets updated to v1.2b – updated to v1.2.1”

  1. Advertisements
    Loading...
  2. This fMobi guy is really doing a lot of work getting these updates pushed out. Wish all app developments take this pattern. The best facebook ap for symbian yet… Cheers

  3. Just downloaded the latest version of fMobi. V1.2.1. It couldn’t load to the home page. Instead, a white screen appeared after the intro. What could be the problem? Please help.

  4. Solved: It’s a known issue on their site… Uninstalled Qt components and Qt stick components before reinstalling. Now in perfect condition. Nice Update.

Leave a Reply