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.

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

App force stops whenever i try playing any song. #17

Closed
realrufans opened this issue Jan 4, 2019 · 15 comments
Closed

App force stops whenever i try playing any song. #17

realrufans opened this issue Jan 4, 2019 · 15 comments

Comments

@realrufans
Copy link

App version: 1.1.10

Screenshots

Screenshot_20190104-110429.png

Screenshot_20190104-110445.png


Device info

Screenshot_20190104-110740.png

@n76
Copy link
Owner

n76 commented Jan 4, 2019

I cannot duplicate this problem, can you get me the output of "adb logcat" showing the force close? With that I might be able to figure out what the problem is.

Also, does this happen on every song or just on one song? If on every song it might be an Android O change. If on one song, it might be something in the song file.

@realrufans
Copy link
Author

I happens to any song I pick.

And how do I get the adb logcat ? My device isn't rooted.

@n76
Copy link
Owner

n76 commented Jan 28, 2019

Sorry for my tardy response: I did not notice you had replied to my request for additional information.

To get a logcat:

  • Enable developer mode, then within developer options enable "Android debugging".
  • On you desktop/laptop computer, install Android Debug Bridge (ADB).
  • Plug your phone into your computer and type "adb logcat" in a terminal window.

Since it is happening on every song and since the song names, performers and album artwork are showing, I suspect this is a permissions issue. The name, performers, etc. are gotten via calls to the Android media manager. The album art is also acquired that way but by a different API. Actually playing the track requires that Symphony can read the track file so the permissions on storage access matter for that.

@n76
Copy link
Owner

n76 commented Jan 28, 2019

Odd thing on the screen shot of Symphony you posted: The player controls at the bottom don't look like a track has been picked. Even on a clean install (or with app data cleared) Symphony should have selected a (default) track to display data for. I suspect that tapping play on the player will cause issues because of that. If you tap on a track title above the player controls does it still crash?

@realrufans
Copy link
Author

realrufans commented Jan 28, 2019

It played now then crashed ..

I will make a gif soon

@realrufans
Copy link
Author

@n76
Copy link
Owner

n76 commented Jan 28, 2019

Definitely crashing, but unless I can somehow get a trace of the crash I'll not be able to fix it.

@n76 n76 reopened this Jan 28, 2019
@realrufans
Copy link
Author

i will provide you with the logcat.

@ergodaveh
Copy link

I have recently built the latest version on my Android 9 with One UI version 1.0 and the app crashes on selecting a Song with this error message

V/MediaPlayer-JNI: getDuration: 191242 (msec)
V/MediaPlayer-JNI: getCurrentPosition: 0 (msec)
D/AndroidRuntime: Shutting down VM
E/AndroidRuntime: FATAL EXCEPTION: main
Process: org.fitchfamily.android.symphony, PID: 23594
android.app.RemoteServiceException: Bad notification for startForeground: java.lang.RuntimeException: invalid channel for service notification: Notification(channel=null pri=0 contentView=null vibrate=null sound=null tick defaults=0x0 flags=0x42 color=0x00000000 vis=PRIVATE semFlags=0x0 semPriority=0 semMissedCount=0)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1872)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:214)
at android.app.ActivityThread.main(ActivityThread.java:7045)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:964)
V/MediaPlayerNative: message received msg=211, ext1=0, ext2=0
unrecognized message: (211, 0, 0)
callback application
back from callback
I/Process: Sending signal. PID: 23594 SIG: 9
Disconnected from the target VM, address: 'localhost:8613', transport: 'socket'

@realrufans
Copy link
Author

Thanks for this . I have been looking for ways to make one.

@n76
Copy link
Owner

n76 commented Apr 20, 2019

Sorry it has taken me this long to get back. . . Looks like the API for notifications has changed and I need to detect if the app is running on 8.1 or higher and if so create a unique channel ID.

Unfortunately, I am having difficulty getting to developer.android.com to read up on the changes and won't have time to get to this again for a couple more days.

Since I don't have a phone that runs that new a version of Android, I am hoping that one of you can do some testing for me, probably sometime next week. Thanks1

@ergodaveh
Copy link

No worries I can contribute a revised method. I will request a pull or would you prefer something in the comments.
Cheers

@n76
Copy link
Owner

n76 commented Apr 20, 2019

No worries I can contribute a revised method. I will request a pull or would you prefer something in the comments.
Cheers

If you have the time to contribute a revised method, I would accept a pull request. Thanks1

@n76 n76 closed this as completed in 50975fd Apr 28, 2019
@n76
Copy link
Owner

n76 commented Apr 28, 2019

@realrufans and @ergodaveh - I think I have this fixed. Please re-open this issue or create a new one if you are still having problems.

@realrufans
Copy link
Author

@n76 Works fine now. Thank you for this simple app.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants