App Review failed. 'Asking for excessive permissions'. Can someone shed some light on this?

[viewport]

We have an app that failed app review. The only test that failed is the permissions test. Oculus says 'The test that failed
is the permissions test.  This app seems to be asking for excessive
permissions that don’t make sense within the context of the app’s
functionality. '

Our app downloads stereo 360s from a server, which are saved to the device so that you don't have to download them again to view. It also checks the time on the device to switch between night and day in the main menu.

Upon unpacking the apk we can see the permissions that Unity 5.40b25 has added are only one to our existing manifest., which is the 'WRITE_EXTERNAL_STORAGE' permission. Everything else seems to be in order. 

    <uses-permission android:name="android.permission.INTERNET"/>
    <uses-permission android:name="android.permission.WAKE_LOCK"/>
    <uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE"/>
    <uses-permission android:name="android.permission.VIBRATE"/>
    <uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE"/>

These permissions do not seem excessive considering what we need to do - download and store images, check time of day.

How can we continue on from here?

[vrdaveb]

WRITE_EXTERNAL_STORAGE is added to enable OVRMonitor during development. I wouldn't expect an app to be rejected for using it. Most likely, VIBRATE is the problem. Do you actually vibrate the phone while it's on the user's face?

[viewport]

Haha no, we don't vibrate the phone when its on someones face... Figured it was part of notifications coming through from Android system eg SMS notifications. But come to think of it I don't recall the phone vibrating when notifications are received, 

VIBRATE was in a manifest for a project successfully approved for the store called 'The Reef Two Rocks'. Which is why we left it in. 

We will remove VIBRATE and resubmit.