Cannot start start session - android pocket device
MichelJean
Posts: 7
in F-Secure KEY
Hello folks,
I pay for a premium license for my computer and tablet.
Now, it's the first time I'm trying to use f secure key with a small android device.
It's a samsung GT-S5312C galaxy pocket neo duos, with a tiny screen.
I miss the buttons in the UI for first time using fsecure key.
How should I handle this situation?
I can't log in at all.
Michel J.
0 Like
This discussion has been closed.
Comments
Hi Michel J,
What is the OS of your new device? Are you able to login to Key? How does the screen look like (a screenshot might help)?
Thank you for your reply, Laksh.
It's an android 4.42; I cannot login to Key.
The attached pictures show what I can see on initial screens.
I miss the ok/connect buttons.
Login images
Michel J.
Hi Michel J,
A button to proceed should appear when you fill input in the box; otherwise it is not visible. Can you try to fill in and check?
Dear Laksh,
this is the problem: there is no button to proceed.
I am stuck after typing a master password or code for connecting devices.
How should I proceed?
Michel J.
Hi Michel J,
If you are unable to see the button after entering the master password, how did you get to the screen to put the sync code? How did the app initialize then if you didn't see the button after entering the master password?
Dear Laksh,
have you you seen the screen shots I have attached in a previous post?
The app initializes with both buttons to put a master password or connect to a device.
After that, going in one way or another, I can't see any OK-PROCEED-CONNECT button.
I just cannot complete the second step to initialize the software.
I am stuck there and cannot proceed.
What should I do?
Michel J.
Hi Michel J,
Yes, I saw your screenshots. It is recommended to get in touch with our support team via chat or phone so that they can investigate this further.
This is a problem with screens with small resolution e.g. 360 x 480. The chat or phone can't help with this issue. Optimizing the app for smaller resolutions would fix this. Thank you!