Note: You should update any bookmarks to point to https://kb.filewave.com We will be working on links from FW Central/Anywhere that still come to this Atlassian site over the next couple of releases and then phasing out this site entirely in Jan 2024.


Customizing the Filewave Android Client

Description

This recipe shows you how to customize the name, logo, icon, and main activity name in the Filewave client for Android

Ingredients

Directions

  1. Create a new project in Virtuous Ten Studio using File – New Project.

  2. From the “Import a file” dialog, select the APK file for the Filewave Client, then click the “Import” button.
  3. Enter a Solution name in the “Solution Name” text box and click the “OK” button. 
    The APK will be automatically decompiled and will be ready for modification.
  4. To modify the name of the application, double-click on the “AndroidManifest.xml” file within Solution Explorer and replace “@string/app_name” with “YourCustomAppName” within both the application and activity elements.  This changes the name of the icon that is displayed in the Android launcher as well as the name of the main activity that is displayed when the Kiosk is open.
  5. Next, right-click the “res” folder and choose “Open in explorer”
  6. Within the res folder exist the image resources that correspond to the logo displayed in the kiosk as well as the launcher icon and persistent status notification icon.

    Modify each of the resources with the logo of your choosing, making sure to keep the size in pixels and the name/location the same.  Directly replace the existing files with your new modified ones in the Virtuous Ten Studio Project folder for this project.

    Image Resource

    Path

    Size (pixels)

    Kiosk Logo

    /res/drawable/logo.png

    1024x1024

    High Density Launcher Icon

    /res/drawable-hdpi/ic_launcher.png

    72x72

    High Density Notification Icon

    /res/drawable-hdpi/ic_stat_notify.png

    24x24

    Medium Density Launcher Icon

    /res/drawable-mdpi/ic_launcher.png

    48x48

    Medium Density Notification Icon

    /res/drawable-mdpi/ic_stat_notify.png

    32x32

    Extra High Density Launcher Icon

    /res/drawable-xhdpi/ic_launcher.png

    96x96

    Extra High Density Notification Icon

    /res/drawable-xhdpi/ic_stat_notify.png

    48x48

    Extra-Extra High Density Launcher Icon

    /res/drawable-xxhdpi/ic_launcher.png

    144x144

    Extra-Extra High Density Notification Icon

    /res/drawable-xxhdpi/ic_stat_notify.png

    72x72

    Table  SEQ Table \* ARABIC 1 - Filewave Client Image Resources

  7. Click the “Build all” button on the Virtuous Ten Studio ribbon bar to build your newly-modified Filewave Android Client APK.
  8. Right-click the “FileWaveClient-8.0.1 (Basic theming)” solution within the “FileWaveClient-8.0.1” project, and choose “Open in windows explorer”.
  9. Browse into the “Binary” folder to find your newly-compiled and signed APK, which may now be installed on an Android device to test your modifications.
  10. Once you have confirmed that your modifications look nice and do not cause any functionality problems, place the APK file on a web server under your control and of your choosing.  In my case, we do not use the built-in OS X web server, but the default page stating “No web services are available at this time” was still there, so I placed the APK in the directory corresponding to this default page which happens to be /usr/share/collaboration/FileWaveClient-8.0.1.apk.
  11. Modify /usr/local/filewave/django/android/templates/android/welcome.html, replacing http://downloads.filewave.com/8.0.1/FileWaveClient-8.0.1.apk with the link to the modified APK on your web server.  In my case, this was http://yourfilewaveserver.com/collaboration/FileWaveClient-8.0.1.apk
  12. Test installing the APK via the android enrollment page.




Note: You should update any bookmarks to point to https://kb.filewave.com We will be working on links from FW Central/Anywhere that still come to this Atlassian site over the next couple of releases and then phasing out this site entirely in Jan 2024.