freezy / freezy/android-xbmcremote
ending phone converstation does not resume palyback
- Dominant language
- Java
- Stars
- 364
- Forks
- 247
- PR merge metrics
- No merged PRs in 30d
Description
What steps will reproduce the problem?
1. Play a movie/serie
2. Get incoming call that pauses the movie
3. Talk for a few minutes will dim the screen or even turn it off (depending on your sleep settings)
4. After hanging up it seems like the app sends a play command. Instead of resuming the playback it will turn on the screen
What is the expected output? What do you see instead?
I expected XBMC to start playback
What version of XBMC Remote are you using?
version v0.8.8-beta1 revision 808
Which Android device are you using (and which ROM, if custom)?
android version 2.3.7
CyanogenMod-7-10022011-NIGHTLY-Blade
Which XBMC revision are you running and on which platform?
XBMC:11.0 (Mar 12 2012)
platform: windows 7
Please provide any additional information below.
The same thing would happen when you manually press the play button after the screen has dimmed/turned off. It will just wake up and not start playing yet. It seems like it can be solved by sending a play command twice
Contributor guide
No contributing guide indexed for this repository
Research direction
Reproduce the issue using the listed XBMC Remote, Android, device, and XBMC versions: play a movie, receive a call, let the screen dim or turn off, then hang up. Trace the playback command sent after the call and screen wake. Done means playback resumes rather than only waking the screen, including after manually pressing play.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100