Bug 117076 - Can't see the thumbnails on Impress Remote 2.3.0 (from Yalp Store) through WiFi
Summary: Can't see the thumbnails on Impress Remote 2.3.0 (from Yalp Store) through WiFi
Status: RESOLVED DUPLICATE of bug 116169
Alias: None
Product: Impress Remote
Classification: Unclassified
Component: Android Remote App (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-04-17 23:32 UTC by aru
Modified: 2018-04-21 16:07 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Attachments
A presentation with 8 pages (with are NOT blank on my computer) (32.58 KB, image/png)
2018-04-17 23:33 UTC, aru 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description aru 2018-04-17 23:32:02 UTC 
Description:
I can connect it with my laptop though WiFi but the pages are shown as blank in my phone (Android 7.1.2). No problem seeing it on my laptop (using LibreOffice 6.0.3.2 on Manjaro). Can't tell about Bluetooth because I don't have Bluetooth in my computer.

Can't use the pointer so that's probably IR not loading correctly the .odp but it passes the pages correctly.

Steps to Reproduce:
1. Download Impress Remote from Yalp Store (you can find it on F-droid)
2. Sync it through WiFi to the device
3. Start the presentation remotely

Actual Results:  
Doesn't load the pages on the phone

Expected Results:
The opposite 


Reproducible: Always


User Profile Reset: Yes



Additional Info:
(See description)


User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:59.0) Gecko/20100101 Firefox/59.0
Comment 1 aru 2018-04-17 23:33:59 UTC 
Created attachment 141438 [details]
A presentation with 8 pages (with are NOT blank on my computer)
Comment 2 raal 2018-04-21 16:06:07 UTC 
I can confirmr. Impress remote 2.3; Android 5; wifi and bluetooth connection.
Comment 3 raal 2018-04-21 16:07:39 UTC 

*** This bug has been marked as a duplicate of bug 116169 ***