Download to device no longer working

Jan Krohn
Jan Krohn Member Posts: 3,766 ✭✭✭
edited November 21 in English Forum

I recently wiped my phone and re-installed Logos. I'm no longer able to download resourced to the phone from the desktop app.

The phone has been added to the dvice list again.

However, the devices list on the app is much shorter...

The e-reader not appearing on this list is the normal thing to happen, however, the phone has always been on there. I've already re-installed the Logos app to see if the device apperas on the second attemp, but also nothing. How can I get my device back into the list?

Tagged:

Comments

  • Lew Worthington
    Lew Worthington Member Posts: 1,538 ✭✭✭

    I'm passionately interested in the outcome of this discussion since I've had this problem for years. Thanks for bringing it up.

  • Kevin A
    Kevin A Member Posts: 1,041 ✭✭

    If I recall correctly Jan there is apparently a limit on the number of devices you can have on the account that shows in the library 'information' and, as I also have this issue after factory reset, think a new device includes a factory reset. I have not been able to use this feature for years due to this, which was how I populated my devices.

    At the time, it was very laborious to choose the resources from the device to download to it, however that has been improved, I don't think there is even anymore a limit to 100 items at a time, you just search/filter and install the results.

    My devices also show in the device list, but not available in the library to 'send' to.

    I will try to dig up a thread

    Edit - https://community.logos.com/forums/t/206739.aspx is a blue post, but I am sure there was one a few years before.

    Edit - https://community.logos.com/forums/t/185084.aspx - blue post about the former mobile 100 at a time resource download limit, which does not seem to be the case anymore, but at the time caused great annoyance when compounded with this issue.

  • Jan Krohn
    Jan Krohn Member Posts: 3,766 ✭✭✭

    Thanks for the threads. Good to know that the issue is actively being worked on since April 2022. With 18+ months of active work, the fix is surely gonna be great.