adnan-SM / adnan-SM/android-vnc-viewer
disconnection on application focus switch
- Vorherrschende Sprache
- Java
- Sterne
- 1
- Forks
- 1
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Beschreibung
```
What steps will reproduce the problem?
1. Establish connection from phone to internet connected PC
2. On motorola droid, android 2.2 hold down the 'Home' key to bring up task
switch interface.
3. Select another application
4. Attempt to switch back to vnc viewer
You will see that VNC viewer must re-establish the connection.
What is the expected output? What do you see instead?
It is expected that the connection will stay established in the background, I
use this to task switch while initial frames download, the clipping of the
established connection may be occuring at a lower level - the OS. This occurs
on the Verizon network.
What version of android-vnc-viewer are you using?
0.4.7
Which VNC server/version are you using? On which platform?
Free VNC server 4.1.3. On Windows XP
What is the size of the desktop you are trying to access (i.e. 1024x768,
1920x1080...)?
1900x1200
What device are you using?
Motorola droid
Are you using a custom ROM? If so, which?
Stock android 2.2 supplied via Verizon
Please provide any additional information below.
Happy to collaborate, please contact when you are free and I can help test.
```
Original issue reported on code.google.com by `bryant.e...@gmail.com` on 11 Oct 2010 at 5:07
Beitragsleitfaden
Für dieses Repository ist kein Beitragsleitfaden indexiert
Rechercherichtung
Start by reproducing the reported Android lifecycle case: connect with android-vnc-viewer, switch away with Home/task switcher, then return and observe whether the VNC connection is dropped. The issue names no files or tests, so first read the app's activity lifecycle and connection-management entry points. Done means the connection survives backgrounding/focus switching or the behavior is clearly explained as an OS/network limitation.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- android, java
- Bereich
- mobile, networking
- Issue-Typ
- Bug
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Aktivitätsstatus
- Veraltet
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 28/100