preFlect Frequently Asked Questions
Refer to these questions and answers if you are having any problems using preFlect.
Where is My "FlectEvents" Folder on Google Drive?
After running preFlect v1.3 or above, I can no longer see my "FlectEvents" folder on Google Drive.
Possible Cause #1
If you were running a previous version of preFlect v1.2 or below, which used a folder named "FlectEvents" on Google Drive to store published event information, this folder will be automatically upgraded to the new folder naming convention used by preFlect v1.3 and above.
This upgrade happens when you first run the newer version of the App.
For more information on the new folder naming convention used by preFlect, please refer to How preFlect uses Google Drive.
Why Can't Analyze Detect Any Event Information in a Photo?
You received a copy of a photo that you previously flected. You can see the flect ID in the photograph, but analyzing the photo fails to reveal the original event information captured when the photo was taken.
Possible Cause #1
The flect ID is blurred or distored in the photograph. This prevents it from being captured clearly in the photograph, and subsequently prevents it from being parsed during analysis.
While flecting photographs, make sure that you hold your phone or tablet steady, so the flect ID can be captured clearly into the photographers photo. In addition, the photographer has to have taken a steady shot. This is usually a given when someone wants their photo to be clear. For more information on flecting, refer to flecting.
Possible Cause #2
The flect ID is either overexposed (too bright), or underexposed (not bright enough) in the original photograph, relative to the surrounding level of light. This prevents the flect ID from being captured clearly in the photograph, and subsequently prevents it from being parsed during analysis.
If the flect ID appears overexposed, lower the screen brightness of your phone, so that it displays clearly, relative to the surroundling level of light in your current location. If it appears underexposed, increase the screen brightness of your phone.
Possible Cause #3
The flect ID was successfully detected and parsed from the photo, but the additional information it references is not available. This might be happen if you don't have an Internet data connection, or you have not yet published the event information. For more information, refer to publishing event information.
While flecting photographs, make sure that you hold your phone or tablet steady, so the flect ID can be captured clearly into the photographers photo.
Possible Cause #4
The flect ID is not being captured clearly in the original photograph, because a screen protector or privacy filter is interfering with the ability to clearly display the flect ID. Glare from screen protectors, and the inability to view your phone from an angle while using a privacy screen can prevent the flect ID from being captured clearly in a photograph, and subsequently prevents it from being parsed during analysis.
Temporarily remove the screen protector, or privacy filter from your phone to see if this resolves the problem. If it does, then you can try adjusting your screen brightness level to compensate for the dimming effects of the screen protector or privacy filter.
If using a privacy filter, holding the phone or tablet as perpendicular as possible to the photographer will help maximize the clarity of the captured flect ID.
Matte vs. gloss screen protectors can help reduce the glare on your device display while flecting, which prevents distortion of the flect ID.