How to keep USB device (action cam) from going to sleep?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
7
down vote

favorite
1












I've got an action cam (iON Air Pro Lite WiFi). It uses an SD card and can be connected to the PC via USB cable. It comes with only Windows and Mac support. However, once connected via USB and turned on, the cam does show up as a 32 GB Volume (size of the SD) in Nautilus, which let's me edit the cam's config via a simple file and, most importantly, view, copy and delete the actual video files. That's all I need. It works the same on Windows, basically.



While connected and powered on, lsusb shows the cam as:



Bus 003 Device 013: ID 4255:1000 GoPro 9FF2 [Digital Photo Display]


The problem is: connected to my Linux (Debian 9) machine, the cam turns itself off again after only 1 to 10 seconds. If I manage to navigate to the video files folder and start copying a file, then the cam will stay on as long as the copy process is doing its work. Once the file is copied, the cam powers itself off after just a few moments. This does not happen when connected to a Windows machine.



My question is, what can I do to keep the device from turning itself off?

Seeing how this does not happen when connected to Windows and also not while keeping the device busy, I assume there should be a way. However, I really have no idea where to start. My line of thought currently is:




  • Could be a driver issue. As I have no knowledge about drivers, I wouldn't know how to go from here, unless someone would be holding my hand or could point me to amazing sources.


  • Maybe there is a way to poll/ping a USB device in some generic way and maybe that would be enough to keep it alive. If so, this sounds like something that could be solved with some code. My current research led me to the GET_STATUS Standard Device Request but that doesn't seem to do the trick (see below).

  • Worst case, a script that constantly copies dummy files from and/or to the device (or even just renames/moves files on the device) should probably do the trick. I would need to find a way to have it auto-run when this particular device is connected. This option seems feasible, but not very clean (after all, constant read/writes do shorten an SD card's lifetime, and given that a few moments of inactivity can lead to a power-off, these operations would need to run constantly).

EDIT 1: I found PyUSB and wrote a simple script that would send a GET_STATUS to the camera every 2 ms (via the ctrl_transfer function). This did not keep the cam from powering off at all.



EDIT 2: I still haven't found a solution. Also, in about one out of 5 cases, the cam turns off even while copying a file from it. Please share any ideas regarding possible causes and/or solutions.










share|improve this question























  • This is maybe related to Powernap / laptop mode? https://askubuntu.com/questions/80638/how-to-disable-auto-power-off-of-usb-devices-like-usb-mouse
    – Dfaure
    May 15 '17 at 16:21










  • @Dfaure thanks for the pointer. Sadly, none of those suggestions worked. Also, I'm on a desktop machine.
    – domsson
    Jun 13 '17 at 19:37






  • 1




    Your lsusb output gave me the idea that maybe your cam appears to Linux as a GoPro and that tricks/problems for the GoPro may apply to your iON Air Pro. That's where I would start. This may be applicable: copy-files-from-gopro-over-usb-on-linux
    – Glenn
    Feb 19 at 0:38










  • While this link may answer the question, it is better to include the essential parts of the answer here and provide the link for reference. Link-only answers can become invalid if the linked page changes. - From Review
    – Jeff Schaller
    Feb 19 at 1:37










  • @jeffschaller Do we make an exception for link-only answers when the link is another SE site?
    – Shadur
    Feb 19 at 13:02














up vote
7
down vote

favorite
1












I've got an action cam (iON Air Pro Lite WiFi). It uses an SD card and can be connected to the PC via USB cable. It comes with only Windows and Mac support. However, once connected via USB and turned on, the cam does show up as a 32 GB Volume (size of the SD) in Nautilus, which let's me edit the cam's config via a simple file and, most importantly, view, copy and delete the actual video files. That's all I need. It works the same on Windows, basically.



While connected and powered on, lsusb shows the cam as:



Bus 003 Device 013: ID 4255:1000 GoPro 9FF2 [Digital Photo Display]


The problem is: connected to my Linux (Debian 9) machine, the cam turns itself off again after only 1 to 10 seconds. If I manage to navigate to the video files folder and start copying a file, then the cam will stay on as long as the copy process is doing its work. Once the file is copied, the cam powers itself off after just a few moments. This does not happen when connected to a Windows machine.



My question is, what can I do to keep the device from turning itself off?

Seeing how this does not happen when connected to Windows and also not while keeping the device busy, I assume there should be a way. However, I really have no idea where to start. My line of thought currently is:




  • Could be a driver issue. As I have no knowledge about drivers, I wouldn't know how to go from here, unless someone would be holding my hand or could point me to amazing sources.


  • Maybe there is a way to poll/ping a USB device in some generic way and maybe that would be enough to keep it alive. If so, this sounds like something that could be solved with some code. My current research led me to the GET_STATUS Standard Device Request but that doesn't seem to do the trick (see below).

  • Worst case, a script that constantly copies dummy files from and/or to the device (or even just renames/moves files on the device) should probably do the trick. I would need to find a way to have it auto-run when this particular device is connected. This option seems feasible, but not very clean (after all, constant read/writes do shorten an SD card's lifetime, and given that a few moments of inactivity can lead to a power-off, these operations would need to run constantly).

EDIT 1: I found PyUSB and wrote a simple script that would send a GET_STATUS to the camera every 2 ms (via the ctrl_transfer function). This did not keep the cam from powering off at all.



EDIT 2: I still haven't found a solution. Also, in about one out of 5 cases, the cam turns off even while copying a file from it. Please share any ideas regarding possible causes and/or solutions.










share|improve this question























  • This is maybe related to Powernap / laptop mode? https://askubuntu.com/questions/80638/how-to-disable-auto-power-off-of-usb-devices-like-usb-mouse
    – Dfaure
    May 15 '17 at 16:21










  • @Dfaure thanks for the pointer. Sadly, none of those suggestions worked. Also, I'm on a desktop machine.
    – domsson
    Jun 13 '17 at 19:37






  • 1




    Your lsusb output gave me the idea that maybe your cam appears to Linux as a GoPro and that tricks/problems for the GoPro may apply to your iON Air Pro. That's where I would start. This may be applicable: copy-files-from-gopro-over-usb-on-linux
    – Glenn
    Feb 19 at 0:38










  • While this link may answer the question, it is better to include the essential parts of the answer here and provide the link for reference. Link-only answers can become invalid if the linked page changes. - From Review
    – Jeff Schaller
    Feb 19 at 1:37










  • @jeffschaller Do we make an exception for link-only answers when the link is another SE site?
    – Shadur
    Feb 19 at 13:02












up vote
7
down vote

favorite
1









up vote
7
down vote

favorite
1






1





I've got an action cam (iON Air Pro Lite WiFi). It uses an SD card and can be connected to the PC via USB cable. It comes with only Windows and Mac support. However, once connected via USB and turned on, the cam does show up as a 32 GB Volume (size of the SD) in Nautilus, which let's me edit the cam's config via a simple file and, most importantly, view, copy and delete the actual video files. That's all I need. It works the same on Windows, basically.



While connected and powered on, lsusb shows the cam as:



Bus 003 Device 013: ID 4255:1000 GoPro 9FF2 [Digital Photo Display]


The problem is: connected to my Linux (Debian 9) machine, the cam turns itself off again after only 1 to 10 seconds. If I manage to navigate to the video files folder and start copying a file, then the cam will stay on as long as the copy process is doing its work. Once the file is copied, the cam powers itself off after just a few moments. This does not happen when connected to a Windows machine.



My question is, what can I do to keep the device from turning itself off?

Seeing how this does not happen when connected to Windows and also not while keeping the device busy, I assume there should be a way. However, I really have no idea where to start. My line of thought currently is:




  • Could be a driver issue. As I have no knowledge about drivers, I wouldn't know how to go from here, unless someone would be holding my hand or could point me to amazing sources.


  • Maybe there is a way to poll/ping a USB device in some generic way and maybe that would be enough to keep it alive. If so, this sounds like something that could be solved with some code. My current research led me to the GET_STATUS Standard Device Request but that doesn't seem to do the trick (see below).

  • Worst case, a script that constantly copies dummy files from and/or to the device (or even just renames/moves files on the device) should probably do the trick. I would need to find a way to have it auto-run when this particular device is connected. This option seems feasible, but not very clean (after all, constant read/writes do shorten an SD card's lifetime, and given that a few moments of inactivity can lead to a power-off, these operations would need to run constantly).

EDIT 1: I found PyUSB and wrote a simple script that would send a GET_STATUS to the camera every 2 ms (via the ctrl_transfer function). This did not keep the cam from powering off at all.



EDIT 2: I still haven't found a solution. Also, in about one out of 5 cases, the cam turns off even while copying a file from it. Please share any ideas regarding possible causes and/or solutions.










share|improve this question















I've got an action cam (iON Air Pro Lite WiFi). It uses an SD card and can be connected to the PC via USB cable. It comes with only Windows and Mac support. However, once connected via USB and turned on, the cam does show up as a 32 GB Volume (size of the SD) in Nautilus, which let's me edit the cam's config via a simple file and, most importantly, view, copy and delete the actual video files. That's all I need. It works the same on Windows, basically.



While connected and powered on, lsusb shows the cam as:



Bus 003 Device 013: ID 4255:1000 GoPro 9FF2 [Digital Photo Display]


The problem is: connected to my Linux (Debian 9) machine, the cam turns itself off again after only 1 to 10 seconds. If I manage to navigate to the video files folder and start copying a file, then the cam will stay on as long as the copy process is doing its work. Once the file is copied, the cam powers itself off after just a few moments. This does not happen when connected to a Windows machine.



My question is, what can I do to keep the device from turning itself off?

Seeing how this does not happen when connected to Windows and also not while keeping the device busy, I assume there should be a way. However, I really have no idea where to start. My line of thought currently is:




  • Could be a driver issue. As I have no knowledge about drivers, I wouldn't know how to go from here, unless someone would be holding my hand or could point me to amazing sources.


  • Maybe there is a way to poll/ping a USB device in some generic way and maybe that would be enough to keep it alive. If so, this sounds like something that could be solved with some code. My current research led me to the GET_STATUS Standard Device Request but that doesn't seem to do the trick (see below).

  • Worst case, a script that constantly copies dummy files from and/or to the device (or even just renames/moves files on the device) should probably do the trick. I would need to find a way to have it auto-run when this particular device is connected. This option seems feasible, but not very clean (after all, constant read/writes do shorten an SD card's lifetime, and given that a few moments of inactivity can lead to a power-off, these operations would need to run constantly).

EDIT 1: I found PyUSB and wrote a simple script that would send a GET_STATUS to the camera every 2 ms (via the ctrl_transfer function). This did not keep the cam from powering off at all.



EDIT 2: I still haven't found a solution. Also, in about one out of 5 cases, the cam turns off even while copying a file from it. Please share any ideas regarding possible causes and/or solutions.







debian usb usb-device






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jun 13 '17 at 19:40

























asked Apr 20 '17 at 21:41









domsson

1477




1477











  • This is maybe related to Powernap / laptop mode? https://askubuntu.com/questions/80638/how-to-disable-auto-power-off-of-usb-devices-like-usb-mouse
    – Dfaure
    May 15 '17 at 16:21










  • @Dfaure thanks for the pointer. Sadly, none of those suggestions worked. Also, I'm on a desktop machine.
    – domsson
    Jun 13 '17 at 19:37






  • 1




    Your lsusb output gave me the idea that maybe your cam appears to Linux as a GoPro and that tricks/problems for the GoPro may apply to your iON Air Pro. That's where I would start. This may be applicable: copy-files-from-gopro-over-usb-on-linux
    – Glenn
    Feb 19 at 0:38










  • While this link may answer the question, it is better to include the essential parts of the answer here and provide the link for reference. Link-only answers can become invalid if the linked page changes. - From Review
    – Jeff Schaller
    Feb 19 at 1:37










  • @jeffschaller Do we make an exception for link-only answers when the link is another SE site?
    – Shadur
    Feb 19 at 13:02
















  • This is maybe related to Powernap / laptop mode? https://askubuntu.com/questions/80638/how-to-disable-auto-power-off-of-usb-devices-like-usb-mouse
    – Dfaure
    May 15 '17 at 16:21










  • @Dfaure thanks for the pointer. Sadly, none of those suggestions worked. Also, I'm on a desktop machine.
    – domsson
    Jun 13 '17 at 19:37






  • 1




    Your lsusb output gave me the idea that maybe your cam appears to Linux as a GoPro and that tricks/problems for the GoPro may apply to your iON Air Pro. That's where I would start. This may be applicable: copy-files-from-gopro-over-usb-on-linux
    – Glenn
    Feb 19 at 0:38










  • While this link may answer the question, it is better to include the essential parts of the answer here and provide the link for reference. Link-only answers can become invalid if the linked page changes. - From Review
    – Jeff Schaller
    Feb 19 at 1:37










  • @jeffschaller Do we make an exception for link-only answers when the link is another SE site?
    – Shadur
    Feb 19 at 13:02















This is maybe related to Powernap / laptop mode? https://askubuntu.com/questions/80638/how-to-disable-auto-power-off-of-usb-devices-like-usb-mouse
– Dfaure
May 15 '17 at 16:21




This is maybe related to Powernap / laptop mode? https://askubuntu.com/questions/80638/how-to-disable-auto-power-off-of-usb-devices-like-usb-mouse
– Dfaure
May 15 '17 at 16:21












@Dfaure thanks for the pointer. Sadly, none of those suggestions worked. Also, I'm on a desktop machine.
– domsson
Jun 13 '17 at 19:37




@Dfaure thanks for the pointer. Sadly, none of those suggestions worked. Also, I'm on a desktop machine.
– domsson
Jun 13 '17 at 19:37




1




1




Your lsusb output gave me the idea that maybe your cam appears to Linux as a GoPro and that tricks/problems for the GoPro may apply to your iON Air Pro. That's where I would start. This may be applicable: copy-files-from-gopro-over-usb-on-linux
– Glenn
Feb 19 at 0:38




Your lsusb output gave me the idea that maybe your cam appears to Linux as a GoPro and that tricks/problems for the GoPro may apply to your iON Air Pro. That's where I would start. This may be applicable: copy-files-from-gopro-over-usb-on-linux
– Glenn
Feb 19 at 0:38












While this link may answer the question, it is better to include the essential parts of the answer here and provide the link for reference. Link-only answers can become invalid if the linked page changes. - From Review
– Jeff Schaller
Feb 19 at 1:37




While this link may answer the question, it is better to include the essential parts of the answer here and provide the link for reference. Link-only answers can become invalid if the linked page changes. - From Review
– Jeff Schaller
Feb 19 at 1:37












@jeffschaller Do we make an exception for link-only answers when the link is another SE site?
– Shadur
Feb 19 at 13:02




@jeffschaller Do we make an exception for link-only answers when the link is another SE site?
– Shadur
Feb 19 at 13:02










1 Answer
1






active

oldest

votes

















up vote
0
down vote













It may be USB autosuspend.



Look at /sys/fs:



find /sys/devices/ -name autosuspend


And see if the relevant sysfs file contains "1"






share|improve this answer




















    Your Answer







    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "106"
    ;
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function()
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled)
    StackExchange.using("snippets", function()
    createEditor();
    );

    else
    createEditor();

    );

    function createEditor()
    StackExchange.prepareEditor(
    heartbeatType: 'answer',
    convertImagesToLinks: false,
    noModals: false,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );













     

    draft saved


    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f360310%2fhow-to-keep-usb-device-action-cam-from-going-to-sleep%23new-answer', 'question_page');

    );

    Post as a guest






























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    0
    down vote













    It may be USB autosuspend.



    Look at /sys/fs:



    find /sys/devices/ -name autosuspend


    And see if the relevant sysfs file contains "1"






    share|improve this answer
























      up vote
      0
      down vote













      It may be USB autosuspend.



      Look at /sys/fs:



      find /sys/devices/ -name autosuspend


      And see if the relevant sysfs file contains "1"






      share|improve this answer






















        up vote
        0
        down vote










        up vote
        0
        down vote









        It may be USB autosuspend.



        Look at /sys/fs:



        find /sys/devices/ -name autosuspend


        And see if the relevant sysfs file contains "1"






        share|improve this answer












        It may be USB autosuspend.



        Look at /sys/fs:



        find /sys/devices/ -name autosuspend


        And see if the relevant sysfs file contains "1"







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Oct 4 at 0:04









        V13

        2,220612




        2,220612



























             

            draft saved


            draft discarded















































             


            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f360310%2fhow-to-keep-usb-device-action-cam-from-going-to-sleep%23new-answer', 'question_page');

            );

            Post as a guest













































































            Popular posts from this blog

            How to check contact read email or not when send email to Individual?

            Bahrain

            Postfix configuration issue with fips on centos 7; mailgun relay