Jump to content

Search the Community

Showing results for tags 'recordings'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • FlexiSPY Public Zone
    • General Questions
    • Company News & Announcements
  • Archives
    • Other Spy Tech & Gadgetry
    • Generic (NON-FlexiSPY) SpyPhone Support
    • PreSales Questions
    • From Our Blogs
    • General Peer Discussion
    • FlexiVIEW Feedback
    • FlexiSPY Stories
    • Feature Requests
    • Android Community Edition Q&A (Closed Forum)
    • Android Club
    • Blackberry Club
    • iPhone Club
    • Symbian Club
    • Windows Mobile Club

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







How did you find us?

Found 1 result

  1. Since sometime December 8th, 2016, I have been unable to capture any more than about 10 minutes of Ambient Recording from the target device (a rooted Samsung Galaxy S5) no matter what I try. For the 4-5 weeks prior to that date that I have had this Extreme subscription, I have had no problem capturing up to about an hour of Ambient Recording. My correspondence with Flexispy's help tickets has repeatedly told me that any interruption by the user of the target device will stop a recording in progress, or cause it to miss entirely, and I understand that (I've received shortened Ambient Recordings that were obviously cut short due to a phone call, or for other reasons). I'm told that the target device must be in complete idle mode, that even a single tap on the screen could shorten the file duration. In the past, I had no problems 'stacking' commands for Ambient Recordings, and they seemed to oftentimes hold their place, executing either after interruptions, or shortly after one had completed approximately 59 minutes worth of recording. I have recordings where the target device was even sending/receiving SMS messages, or looking through settings without interrupting the Ambient Recording. It was great! Now, however, something that changed is causing me to no longer be able to experience the same great service. I have experimented with Ambient Recording at night when I can physically see that the target device is idle. Even then, I am unable to capture more than about 10 minutes. I have manually restarted the target device multiple times. I have limited all app permissions on the target device that I thought might be unnecessary, or possibly be a contributor to the problem. I have gone through the target device settings looking for anything that might cause processes to sleep after about 10 minutes, and have not found anything in this regard (Power Saving options are turned off). Has anyone experienced a similar situation, resolved a similar situation, or have suggestions that might help resolve? Perhaps I am just having trouble finding the culprit of my new found problem within the target device. I would love to be able to regain the level of service I once had with the Ambient Recording feature, and would be extremely grateful for a resolution.
  • Create New...