Patch for enabling Google Drive/Dropbox on all device models

[imax9000]

Tested this on FW 4.38.23038 on my Kobo Libra 2.

[liups233]

There are some bugs on Clara BW version 4.39.23027. I can see Google Drive and Dropbox menus on my ereader, but I cannot login. When I click "Get Started", there is only a blank screen.

(Not my network problem, because I can access Google Drive with internal browser)

[jillmess]

There are some bugs on Clara BW version 4.39.23027. I can see Google Drive and Dropbox menus on my ereader, but I cannot login. When I click "Get Started", there is only a blank screen.

(Not my network problem, because I can access Google Drive with internal browser)

I have enabled Google Drive on my Libra 2 version 4.38.23038 using this patch but I did have to edit eReader.conf per info found at the bottom of this: pgaskin/NickelMenu#143 to get beyond the blank screen for initial setup.
I already had DropBox setup via NickelMenu so it just worked without any further changes.

[liups233]

There are some bugs on Clara BW version 4.39.23027. I can see Google Drive and Dropbox menus on my ereader, but I cannot login. When I click "Get Started", there is only a blank screen.
(Not my network problem, because I can access Google Drive with internal browser)

I have enabled Google Drive on my Libra 2 version 4.38.23038 using this patch but I did have to edit eReader.conf per info found at the bottom of this: pgaskin/NickelMenu#143 to get beyond the blank screen for initial setup. I already had DropBox setup via NickelMenu so it just worked without any further changes.

Very useful. Thank you. I just need to edit .kobo/Kobo/Kobo ereader.conf,
add https://authorize.kobo.com/{region}/{language}/LinkDropbox after dropbox_link_account_poll=, and
add https://authorize.kobo.com/{region}/{language}/linkcloudstorage/provider/google_drive after googledrive_link_account_start=

[imax9000]

I had that URL copied over from Kobo Sage from when I was trying to get it working via NickelMenu, so I did not notice a potential problem. I've dug around some more, and it seems that these values aren't shipped in the firmware images, but rather they're fetched during initial device setup via an authenticated request to https://storeapi.kobo.com/v1/initialization. I assume the returned chunk of JSON contains different values depending on the device model.

I'll update the patch description to include the config values necessary for the sync to actually work.