Support for Grunt devices

[Glen5CD2]

We use scan with our district Chromebooks and it's a great tool for the classroom; however, it isn;t supported on all Chromebook architectures.   Specifically, the AMD/Stoney Ridge devices (Grunt board in Google's naming scheme).    Any chance of that getting added?

[Ria Tagra]

Hi Glen5CD2,

Hope you are doing well.

Thank you for posting your query here. We appreciate that you bring this to our knowledge. It's in a future enhancement pipeline. You will get an official announcement as well as a notification when this will roll out.

 If you have any further queries please feel free to reach out to us. We would be more than happy to assist you.

Regards

Ria (edited)

[Sonny29821069esjf]

Ahh! We've been trying to figure out why Adobe Scan is not showing up on our 300e 2nd Gen AST Lenovo Chromebooks.

We are hoping to be able to use Adobe Scan in our classrooms, thank you!

[S. S]

Hi @Sonny29821069esjf,

Thank you for writing in!

Let me check with the team on this and get back to you.

-Souvik

[S. S]

Hi @Sonny29821069esjf,

A few more details are needed for the team to review.

1. Do you not see Adobe Scan when opening the Play Store?

2. If you can see the application name on the search list, do you experience issues with installing it?

3. If not, are there any usage constraints that you see?

More details about the usage and the experience would help here.

-Souvik

[Glen5CD2]

I'm the OP from 2021.  We force install Scan to all our Chromebooks via Google Admin; however it doesn't load on AMD Stoney Ridge (Chrome OS nomenclature =  Grunt) based machines or appear on the play store    When I load the play store on a PC which lets me designate an app for any device I "own", I can see that the Google Grunt device is grayed out with a notation that "this item is not compatible with your device."   My understanding for this to occur would mean that there is something in the app manifest designated as a hardware requirement that AMD Stoney Ridge does not support (or at least Grunt on Treeya boards) and thus the play store will not permit it to be loaded.  

[Sonny29821069esjf]

Thank you very much for returning to the post!
This would confirm the behavior we are seeing as well.
We can get a 'install on other devices' button which then pops up a scroll down list (this is on the google play store web page).
In that scroll down list it lists Grunt as not available.
Your post was the only way I was able to find this out as it was just not showing up in our managed google play store even after allowing it and most importantly there were no error messages.
Thanks again for coming back to give the details you shared!

[Sonny29821069esjf]

Good morning,

We can find the App by going to the Google Play website where the following
happens:

Please find included 2 screenshots:

1 ) which shows a device selection dropdown when trying to install Adobe
Scan. It shows other Chromebook models where we have successfully installed
Adobe Scan. It also lists 'Grunt' as an unsupported device type. It is the
first item in the list.

2) The second screenshot shows the Adobe Scan page after pressing the
install button (while using a lenovo 300e). The App is not actually
installed/appearing on the 300e afterwards(which we believe is a grunt
model). It then shows an 'install on other devices' button with text that
says the app is available on 'some of your devices'

[image: image.png]

[image: image.png]


For the Google Play store APP on Chromebook, we use a managed store where
we approve the application. The application correctly shows and installs on
other models, but on the 300e it won't even show up in the Google Play
Store app.


Thank you for your assistance!

Sonny Nicolas

Director of I.T. Services

Directeur Services T.I.


[PII removed by moderator]

[Sonny29821069esjf]

As I replied by email and the images did not carry over here they are:

The logged in account has been used on many Chromebook models which is why we believe we have the dropdown list of models.

[S. S]

Thanks @Sonny29821069esjf @Glen5CD2. for getting back.

I have shared the details with the team. 

I will update you once I hear back from them.

-Souvik

[S. S]

Hi @Glen5CD2 @Sonny29821069esjf,

We have removed all the blacklisted devices for download limitations. Please check if you are now able to install Adobe Scan.

Thanks,

Souvik

[GDrager]

Well the good news is that it is now available for us to install.   The bad news is it crashes immediately upon opening (at least on the test device I have handy).    I have at least one more Grunt model I can test on so I will try--but it's a reference architecture so I presume if it fails on one it will fail on all.

[Sonny29821069esjf]

Good morning,

Thank you for looking into this. 

The app is now showing up in our Google Play Managed store. Unfortunately, the app closes immediately on open with our 'Grunt board' model Chromebooks. The model is a Lenovo 300e 2nd GEN AST.

I'd be glad to provide any logs/details/remote sessions that could help.

Cheers

[GDrager]

Yup.   Lenovo 100e Gen 2 & 300 Gen2.   Also, to expand the problem I realized I do have some newer AMD CROS devices in some Lenovo Yoga C13s (these are on the Zork boards with a Picasso/Dali processor).    Scan also goes into a crash loop on those. So it looks like it may be a larger issue with AMD in general.

Looking at trying to gather some logs.

[S. S]

Hi @GDrager @Glen5CD2 @Sonny29821069esjf 

I had a detailed discussion with our development team on the topic, and we had to blacklist AMD devices again.

Here is a brief of the conversation:

Right after removing the Google grunt Chromebook from our blacklist, we’re seeing increasing crash on this particular device. They’re all crashing in the ARM translator, and we do not have immediate solutions for this issue, therefore we will add this device back to the blacklist. We’re sorry but users will soon find that Adobe Scan Android is unable to install on their device via Google Play Store.

The cause of crash is due to insufficient ARM emulation on these devices. Possible solutions are

1. Board manufactures fix their ARM emulation
2. Adobe Scan Android provides x86 native support

Unfortunately, we’re importing some native libraries which support only ARM architecture.

This has to do more with the architecture of the processor than the devices. For native libraries, the team is referring to Google Libraries.

Hope I was able to explain most of it.

-Souvik

[Glen5CD2]

Thanks so much for trying.   This was what I expected to be the answer.  Because of this incompatability with your app and others, we are already well along the path to Intel only CBs as they seem to have the best compatibility with Anroid Apps, which I now assume means the best ARM emulation.

[S. S]

@Glen5CD2 Thank you for your kind understanding.

-Souvik