ChromeOS support

[achiyae]

Hi

tl;dr; there is a workaround by @jeffmcneill - turn off the anti-screenshot feature in the app setting.

ChromeOS now support opening Android apps.

I can open Keepass2Android on my laptop screen (google pixelbook), however if I open the app on my external monitor (4k monitor) - I get a blank screen and I need to drag it to my laptop.
Since I'm working in a docking station mode (i.e., screen closed) it is very annoying.

Google has a special page for android apps on ChromeOS - https://developer.android.com/chrome-os/intro.html

The solution to the screen size issue is here - https://developer.android.com/topic/arc/screen-size-comp.html

Thanks!

[df03438]

So.. does Keepass2Android offically support the Chrome OS on any Chromebook that has access to the Google Play Store? It sounds like it does, but want to be sure before switching from a Nexus 9 to a new Acer Chromebook Tab 10 that comes out in April. https://www.anandtech.com/show/12583/acer-announces-chromebook-tab-10-a-tablet-running-googles-chrome-os

[Karreg]

Ah ah, I was sure that was related to Chromebook tab :D
I'm interested in the answer too, but there's another solution : Keeweb is running on Chromebook. However, I don't know how it behaves with file syncing... But that's another matter.

[achiyae]

I think it does, however it has issues on non-native monitors with a high resolution.
By the way, as long as I need read only access - I use Tusk. For the rare occasion that I need to change a password or create a new entry - I disconnect the chromebook from the docking station and use K2A.

[RoamingAussie]

Hi Everyone,

I'm also experiencing this problem.

Keepass2Android was working on a Samsung Chromebook Pro in standalone portable "notebook mode" - internal screen only for a 4-5 days without any problems. I was using Dropbox to store .kdbx database, and sync'ing plus a locally stored ket file. Using Keepass2Android from the Samsung Chromebook, and Keepass on "old" Windows desktop PC to open & edit the database worked great !!!

Then started to create "docked desktop" environment with 2x external 2K monitors, wireless keyboard & mouse for the Samsung Chromebook Pro - constantly suffered "blank screen" problem in Keepass2Android window on external monitors (have tried many re-install options). But can drag window to / from internal screen where Keepass2Android app operates correctly, to "faulty" external monitors. I too am seeking to dock / close internal screen on Samsung Chromebook Pro for 80% of time.

An Acer Chromebook 14 for Business notebook was also tried in this "docked desktop" environment - exactly the same problem.

Unfortunately I don't have any app programming skills. But I am happy to provide any detailed information required, and test any code fix for this problem - both on the Samsung & Acer chromebooks.

Thanks, Cam Lynch.

[jeffmcneill]

Same problem on an Asus Chromebook Flip C101PA running Version 66.0.3359.137 (Official Build) (32-bit), which has an ARM processor, if that matters.

When connected to an external 1080p monitor via hdmi, even if I am using two screens (chromebook and external) as soon as I connect the monitor, Keepass2Android app display turns completely black. I have to disconnect the monitor, and then restart K2A to get the screen to appear. Note that the initial login screen for selecting a database works fine on the external monitor, it is the display of the list of entries and individual entries that are black and therefore illegible.

From reading the link in the initial issue report above, it appears that different calls need to be made to draw the screens in a way that is supported by ChromeOS's implementation of Android Apps.

• P.S., I've donated a large beer via info@lanna.io to help with thirst-quenching needs.

[jeffmcneill]

Hi folks, looks like it is the anti-screenshot feature that is causing the issue. I disabled that setting and no longer have a black screen on the external/extended monitor configuration.

[derBroBro]

@jeffmcneill this solved the issue for me too!

[achiyae]

@jeffmcneill solved here as well, thanks!

[lloydhazlett]

Hi folks, looks like it is the anti-screenshot feature that is causing the issue. I disabled that setting and no longer have a black screen on the external/extended monitor configuration.

I'm also affected by this issue on ChromeOS. Unfortunately I'm not able to use the workaround because I have no way of ever accessing app settings to change it! As soon as you select a database, the anti-screenshot feature takes over and I can't then interact with the app to be able to disable it. Device is the ASUS Chromebox 3 (I can probably add a screen capture if the behaviour I'm describing isn't clear).

Is there any other way to turn it off? Perhaps it should even default to off if it's not possible to reliably detect when the user won't be able to interact with the app with it on?

[achiyae]

Just change the screen to a lower resolution.

…

On Sat, Jan 26, 2019, 00:34 Lloyd Hazlett ***@***.*** wrote: Hi folks, looks like it is the anti-screenshot feature that is causing the issue. I disabled that setting and no longer have a black screen on the external/extended monitor configuration. I'm also affected by this issue on ChromeOS. Unfortunately I'm not able to use the workaround because I have no way of ever accessing app settings to change it! As soon as you select a database, the anti-screenshot feature takes over and I can't then interact with the app to be able to disable it. Device is the ASUS Chromebox 3 <https://www.asus.com/us/Chrome-Devices/ASUS-Chromebox-3/> (I can probably add a screen capture if the behaviour I'm describing isn't clear). Is there any other way to turn it off? Perhaps it should even default to off if it's not possible to reliably detect when the user won't be able to interact with the app with it on? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#272 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AJlFyzwUeJ-44yvAm8-0hSAzXdAztJ0Cks5vG4ZmgaJpZM4SSP-4> .

[lloydhazlett]

Just change the screen to a lower resolution.

@eggsterino Thanks. I thought I tried that already, but if you know that it works I'll check again. Don't suppose you happen to know exactly what resolution the anti-screenshot feature takes effect from?

[achiyae]

I think that I pressed the ctrl+shift+- twice but I'm not sure... Also, if I remember correctly, I opened the app after changing the resolution...

…

On Sat, Jan 26, 2019 at 11:18 PM Lloyd Hazlett ***@***.***> wrote: Just change the screen to a lower resolution. @eggsterino <https://github.com/eggsterino> Thanks. I thought I tried that already, but if you know that it works I'll check again. Don't suppose you happen to know exactly what resolution the anti-screenshot feature takes effect from? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#272 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AJlFy8au63ttlNOXH6J9XQIVbURvDyWAks5vHMY1gaJpZM4SSP-4> .

[lloydhazlett]

@eggsterino I still don't see way to work around this. I have tested changing resolution to 720x400, which is as low as ChromeOS will allow you to set it. There is no change, the application window is still blacked out. Given it is an application setting rather than a database setting, I don't see a way for ChromeOS users with external displays only to disable the feature.

[achiyae]

Hmm, I changed it on my native screen (and now it works on external as well). A wild experiment - try remote controlling your chrome os from a mobile phone. Another option - change the setting on your phone and copy the setting file of the application to chrome os (I have no idea if it is possible)...

…

On Thu, Jan 31, 2019, 06:20 Lloyd Hazlett ***@***.*** wrote: @eggsterino <https://github.com/eggsterino> I still don't see way to work around this. I have tested changing resolution to 720x400, which is as low as ChromeOS will allow you to set it. There is no change, the application window is still blacked out. Given it is an application setting rather than a database setting, I don't see a way for ChromeOS users with external displays only to disable the feature. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#272 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AJlFy8Qr6GEJYZvWNoDJCwrvxbSQWxYSks5vIm8bgaJpZM4SSP-4> .