-
-
Notifications
You must be signed in to change notification settings - Fork 160
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
can't get gemini nano to run with page assist on chrome v130 on win11 #227
Comments
Hey, first of all, thanks for your sponsorship! The Gemini Nano is not fully stable. Two weeks ago, it was working fine, but now it's showing an error. I’ll investigate what's happening. Thank you for the video. I’ll let you know once it’s fixed. Thanks! |
Sorry, guys. This issue may take longer to fix since Chrome changed the APIs. :/ I’ll let you know if there are any updates |
The issue has been fixed. Please let me know if it's working or not. :) |
No joy. Go to chrome://flags/#prompt-api-for-gemini-nano and select "Enable". "Optimization Guide On Device Model" doesn't exist on my v. of chrome after reinstalling chrome: "Optimization Guide On Device Model" chrome://settings/help |
still not joy |
same |
Same here ;-( |
but after some time away from it I ran this in my chrome developer console so in chrome dev console I ran |
on chrome v 130
I followed the instructions:
In order to use Chrome AI, you need a browser version greater than 127, which is currently in the Dev and Canary channels. After downloading the supported version, follow these steps:
Go to chrome://flags/#prompt-api-for-gemini-nano and select "Enable".
Go to chrome://flags/#optimization-guide-on-device-model and select "EnabledBypassPrefRequirement".
Go to chrome://components, search for "Optimization Guide On Device Model", and click "Check for Update". This will download the model. If you don't see the settings, repeat steps 1 and 2 and relaunch your browser.
I followed the steps. no joy
Here's a vid showing all steps
https://youtu.be/NxKXcMgiz5k
thank you
The text was updated successfully, but these errors were encountered: