Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add code to handle disconnects #1

Closed
philburk opened this issue Oct 23, 2017 · 0 comments
Closed

Add code to handle disconnects #1

philburk opened this issue Oct 23, 2017 · 0 comments
Labels
enhancement

Comments

@philburk
Copy link
Collaborator

The stream can become disconnected when, for example, plugging or unplugging headphones.
By default, always stop and close the stream.
Let developer override method that will reopen a new stream or whatever the app needs.
philburk pushed a commit that referenced this issue Nov 23, 2017
oboe: automatically stop and close a stream when disconnected
cfd1a01 
WARNING: API change
Modifies OboeStreamCallback onError methods.

Adds protection against stopping or closing a stream at the same time
that the error callback is being processed.

Fix issue #1
@philburk philburk mentioned this issue Nov 23, 2017
Merged
@dturner dturner closed this as completed Nov 27, 2017
@dturner dturner mentioned this issue Jan 10, 2018
Closed
dturner pushed a commit that referenced this issue Feb 12, 2018
@dturner
oboe: automatically stop and close a stream when disconnected
2140eb1 
WARNING: API change
Modifies OboeStreamCallback onError methods.

Adds protection against stopping or closing a stream at the same time
that the error callback is being processed.

Fix issue #1
This was referenced Sep 3, 2018
Closed
Closed
@Diljeet Diljeet mentioned this issue Sep 22, 2018
Open
@philburk philburk mentioned this issue Sep 22, 2018
Closed
@philburk philburk mentioned this issue Oct 9, 2018
Closed
@abhi-foss abhi-foss mentioned this issue Nov 5, 2018
Closed
@pbodilis pbodilis mentioned this issue Nov 27, 2018
Closed
@mbibas mbibas mentioned this issue Jan 2, 2019
Closed
This was referenced Jan 21, 2019
Closed
Closed
Closed
@philburk philburk mentioned this issue Feb 4, 2019
Closed
@taemincho taemincho mentioned this issue Apr 5, 2019
Closed
@extreamsd extreamsd mentioned this issue Apr 28, 2019
Closed
@taemincho taemincho mentioned this issue Jun 4, 2019
Closed
@miqouser miqouser mentioned this issue Jul 2, 2019
Closed
@mahaju mahaju mentioned this issue Feb 28, 2020
Closed
@ekurdesov ekurdesov mentioned this issue Mar 18, 2020
Closed
@herbaini herbaini mentioned this issue Apr 23, 2020
Closed
@iNeverSleeeeep iNeverSleeeeep mentioned this issue May 9, 2020
Closed
@dturner dturner mentioned this issue May 13, 2020
Open
@philburk philburk mentioned this issue Jul 8, 2020
Closed
@jie545098983 jie545098983 mentioned this issue Sep 2, 2020
Closed
@philburk philburk mentioned this issue Nov 25, 2020
Closed
@ashfaq-opn ashfaq-opn mentioned this issue Dec 4, 2020
Closed
@myj420 myj420 mentioned this issue Feb 25, 2021
Open
@FeiWang888 FeiWang888 mentioned this issue Mar 3, 2021
Closed
@paulorrfilho paulorrfilho mentioned this issue Mar 10, 2021
Open
@dturner dturner mentioned this issue Jun 10, 2021
Closed
@Jimmy198901 Jimmy198901 mentioned this issue Jan 25, 2022
Closed
@extreamsd extreamsd mentioned this issue Jan 30, 2022
Open
@anudeepburugu anudeepburugu mentioned this issue Feb 2, 2022
Closed
@Hyyzt Hyyzt mentioned this issue Aug 18, 2022
Closed
@philburk philburk mentioned this issue Dec 15, 2023
Closed
@flornil flornil mentioned this issue Jun 8, 2024
Open
@lhran99 lhran99 mentioned this issue Jun 11, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dturner @philburk