Frequently Asked Questions

Q: What can I use STORICA for?

A: The STORICA main screen lends itself to daily episodes of some sort, such as from daily diary over capturing your holiday experiences to workout tracking. You can experience your captured photos, your movements, various sensor information (as timelines or tag clouds) as well as your personal stories based on events that are meaningful to you.

Q: What visualisations does STORICA offer?

A: STORICA offers four main groups. First, there is your daily story, grouped around meaningful events throughout the day. Then, there is your daily media gallery, enriched with map and context information. And there is also your map of the day, where you can fly through your day in a special flight mode as well as retrieve context information for each tracked location. Finally, you can view detailed views of different information as timelines or tag clouds.

Q: Can you add other visualisations?

A: Of course, we can add other visualisations. If you have any particular idea or suggestion, please send an email to our development team.

Q: What are the diaries used for?

A: On the main screen, you can select different so-called diaries from the drawer menu (swipe from left). These diary modes filter shown event and context information to suit specific usage purposes. For instance, the travel diary focuses on surrounding information and tones down social information (such as hangout messages, SMS, …), while the lifelogging diary provides the most comprehensive view of all recorded values that we visualize.

Q: Can I just start recording?

A: Almost! Storica comes preinstalled with the Lifelogging template, which is a good compromise between recording rich life data and battery life. See here how to tweak settings and what we recommend to record and why. However, you will to set a few settings values to your personal environment. For instance, you want want to use your heart rate monitor (Zephyr HxM or any BT Smart compatible one), you will need to configure this particular sensor in the heart rate monitor settings. You might also need to check that camera snapshots are properly recorded, if your device manufacturer is not using the standard folders for storing the photos! See here for how to configure the various Recording Settings that can be reached from the Settings menu in the drawer menu of the main screen (although the screen shots show the AIRS configuration, the interface looks similar for our current Storica version).

Q: Can I view STORICA stories while recording?

A: Yes, you can! Sometimes there might be a slight delay in visualisations to appear. This is due to possible locking of the shared database while writing currently recorded values into the database.

Q: Can I share my stories with my social network?

A: Yes you can – if you have the latest version of Storica installed. Earlier versions of Storica (up until V1.3) had only limited sharing due to issues with the Google Maps V2 API. However, the latest version of Storica allows for sharing story events, maps, media gallery pictures and timelines/tag clouds to any program on your phone that can share pictures (e.g., Facebook, G+).

Q: Why are my snapshots not showing?

A: Since KitKat, you will need to save any photos to the internal SD card due to restrictions introduced in KitKat. Storica won’t be able to read any photos stored on an external card.

Q: Is my data safe?

A: YES! It has been the philosophy of both AIRS and Storica to store everything directly on your device, using efficient SQLite database technology. Nothing is stored in the cloud, any particular sharing needs to be specifically done from your side. We believe that this approach will ultimately keep your data safe!

Q: Why does STORICA need so many permissions?

A: In order for Storica to visualise the many data you can record, we need many permissions for accessing this data. As mentioned above, we store all recorded data directly on your device, so nothing is transferred off for some sinister purpose or advertising. Here is the list of permissions that we require:

READ_CALENDAR: for CA sensor, showing you current calendar events

READ_CONTACTS: show contact names in IC, OC, SR, SS sensors (i.e., call and SMS log)

READ_PHONE_STATE: read IMEI for sensing authorization and detecting incoming phone calls (for IC sensor)

PROCESS_OUTGOING_CALLS: capture outgoing phone numbers (for OC sensor)

WRITE_EXTERNAL_STORAGE: write sensor values to database

ACCESS_COARSE_LOCATION: for cell identifier information

VIBRATE: use vibrator for widgets and watchdog function as confirmation

WAKE_LOCK: wake-lock for wifi scanning or permanent sensing

ACCESS_NETWORK_STATE: obtain information about connected to wifi or cellular

READ/RECEIVE_SMS: obtain received & sent SMS info

BLUETOOTH: perform BT discovery as well as enable BT-enabled sensors, such as heartrate sensors

BLUETOOTH_ADMIN: enable BT programmatically, if wanted by user

BATTERY_STATS: read battery stats

ACCESS_FINE_LOCATION: obtain various GPS information (all Gx sensors)

RECORD_AUDIO: record environmental noise level (for AA, AF sensors)

ACCESS_WIFI_STATE: allow for scanning wifi

CHANGE_WIFI_STATE: change wifi to on, if wanted by user

INTERNET: connectivity for weather information as well as obtaining Google Maps tiles

GET_TASKS: get list of running tasks for TR/TV sensors

PACKAGE_USAGE_STATS: get list of running tasks for TR/TV sensors in Lollipop+. You will need to enable the reading of task statistics in the system settings

ACCESS_LOCATION_EXTRA_COMMANDS: control A-GPS reloading option

GET_ACCOUNTS: set Google Drive account for uploading your recordings to your GDrive, if you so wish

RECEIVE_BOOT_COMPLETED: set timer for uploads after boot and restart recording if recording was running when rebooting