-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FeatureRequest: Google Drive support #143
Comments
Same here |
Yes, I also would appreciate Google Drive support, same as it is now for Dropbox. |
+1 Thanks for nickelmenu! It rules! |
Yes, I also would appreciate Google Drive support, same as it is now for Dropbox. |
+1 Hugely appreciate NickelMenu and Google Drive support would be the cherry on top! Thank you! :) |
i'd love that |
I really gotta get the release pipeline migrated to GH Actions so I can get this stuff implemented and do another release... |
How to launch Google Drive using nickle menu, it's already there in the system |
There's a symbol |
Can confirm that Google Drive integration works perfectly well on Libra 2, but I had to patch hardcoded device model checks in |
I added this symbol to the code, and the Google setup page appeared. However, we need the URL of googledrive_link_account_start to link the Google Drive account. Since Dropbox used the URL like https://authorize.kobo.com/{region}/{language}/LinkDropbox. So I tried a lot of combos like LinkGoogleDrive, LinkGoogle, LinkDrive, etc. None of them works. We need help with what this link URL is. |
One example of the Dropbox URL is https://authorize.kobo.com/us/en/LinkDropbox. When you try this on the computer, it will show an error, but the URL remains the same and won't be redirected. |
|
Thank you so much! I succeeded in adding the Google Drive functionality to my Kobo Clara Colour!
Then add this to your NickelMenu
All the code I modified is in the action_cc.cc file Thank you so much for providing this information! |
Also see this pgaskin/kobopatch-patches#139 if you're using kobopatch |
No problem, I'm glad I could help! Thanks for making that build! |
This is awesome, thanks for sharing! @kingo132 Could you open a pull request for your updates? 🙏🏻 |
Hi, new to github and dealing with code, so was wondering if you could provide some clarification about how you enabled google drive? I managed successfully with Dropbox and did the same steps with the information you provided for Google Drive i.e. edited the Kobo eReader.conf and added menu item to the nickelmenu. However, when I try to open it on my Kobo I get the following popup "unknown view 'godrive' (in 'library:godrive') (check failed: sym_f) The only missing piece I can think of is what was mentioned earlier as "a symbol" _ZN14MoreController11googleDriveEv Will I need to uninstall my nickelmenu and install your modified version instead, or can I edit it on my end? (I however can't find a file in my kobo's folders called action_cc.cc to edit!) Any guidance is appreciated! 🙏🏼 |
@Krabbis07 sounds like you didn't install the modified Nickelmenu - look at the last comment by kingo132 - he has a link to a KoboRoot.zip - install that Nickelmenu update then it will work. I did it the other day on my Kobo mini running Kobo Glo firmware (4.38) and it worked beautifully |
The above mentioned KoboRoot.zip for the updated NickleMenu doesn't work. I have installed it and still the "godrive" isn't known by NickleMenu - I get a failure message.....unknown view 'godrive' (in libary:godrive') My firmware: 4.38.23038 on Kobo Libra 2 |
I have tried and failed miserably to install this on my partners Kobo Clara Color. Followed the instructions above, Unzip and installed KoboRoot.zip and put it into .kobo folder, and modified the .kobo/Kobo/Kobo eReader.conf, but Nickelmenu does not show up when I reboot the device. |
Recently Kobo new firmware officially supports Google Drive (software version 4.37 or higher). Hope to add the feature as for Dropbox.
https://help.kobo.com/hc/en-us/articles/15335985512983-Add-books-to-your-eReader-using-Google-Drive
The text was updated successfully, but these errors were encountered: