App crashes when clicking on a recording

[orschiro]

Hi all,

Every time I click on a recording to play it, the app crashes.

I sent my feedback to you.

Is there anything else I can do to help?

[werman]

Hi,

What version of RadioDroid do you have? What version of Android? Does this recording exist on disk?

Thanks!

[orschiro]

Hi @werman,

• RadioDroid 0.66
• Android 7.1.2
• Yes, it does exist. I was able to play it using VLC

Thanks!

[werman]

Could you get stack trace from logcat?

[orschiro]

Sure, can you tell me how?

-- https://orzanna.de

On Sat, 5 Jan 2019 at 15:45, Danil notifications@github.com wrote:

Could you get stack trace from logcat?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/segler-alex/RadioDroid/issues/421#issuecomment-451661540, or mute the thread https://github.com/notifications/unsubscribe-auth/AAKbw76NwpI168d1wYh4Ad32e4Zv-mG5ks5vALqLgaJpZM4ZwadA .

[werman]

Assuming you have adb installed, connect the device with cable, execute adb logcat in terminal - it will print a lot of logs, make radiodroid crash and copy appeared logs with crash

[orschiro]

Thanks Danil.

I am going to try to get that information for you in the coming days.

At the moment, my phone is saying "USB debugging connected" (so ADB seems to be working and is enabled under developer options) but my Linux laptop just says:

[orschiro@x230 ~]$ adb logcat

• waiting for device -

-- https://orzanna.de

On Sat, 5 Jan 2019 at 15:52, Danil notifications@github.com wrote:

Assuming you have adb installed, connect the device, execute adb logcat in terminal - it will print a lot of logs, make radiodroid crash and copy appeared logs with crash

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/segler-alex/RadioDroid/issues/421#issuecomment-451662172, or mute the thread https://github.com/notifications/unsubscribe-auth/AAKbw93allO9dmmIHmLWNw8KvtXdV6juks5vALxHgaJpZM4ZwadA .

[werman]

ADB is a strange beast, the standard magic moves are:

• disconnect phone
• adb kill-server
• adb start-server
• reconnect phone

or

• adb kill-server
• adb devices (should show your connected phone)

or

Sometimes something going wrong with debugging authorization and you need more advanced magic moves.

Also you can look into dmesg and see if phone even recognized, something like:

 usb 5-2.4: new high-speed USB device number 4 using xhci_hcd
 usb 5-2.4: New USB device found, idVendor=18d1, idProduct=4ee7, bcdDevice= 2.32
 usb 5-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
 usb 5-2.4: Product: Nexus 5

[orschiro]

Hmm. I tried all recommended steps but it didn't work.

Will report back once I have found a solution!

Maybe someone else can jump in with similar issues and can provide the debugging output?

-- https://orzanna.de

On Sun, 6 Jan 2019 at 12:19, Danil notifications@github.com wrote:

ADB is a strange beast, the standard magic moves are:

• disconnect phone
• adb kill-server
• adb start-server
• reconnect phone

or

• adb kill-server
• adb devices (should show your connected phone)

or

Sometimes something going wrong with debugging authorization and you need more advanced magic moves https://stackoverflow.com/a/30565982.

Also you can look into dmesg and see if phone even recognized, something like:

usb 5-2.4: new high-speed USB device number 4 using xhci_hcd usb 5-2.4: New USB device found, idVendor=18d1, idProduct=4ee7, bcdDevice= 2.32 usb 5-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 usb 5-2.4: Product: Nexus 5

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/segler-alex/RadioDroid/issues/421#issuecomment-451733741, or mute the thread https://github.com/notifications/unsubscribe-auth/AAKbw8UPyb1kiHuCstqRYbNtKyMloXqCks5vAdvAgaJpZM4ZwadA .

[iheinze]

I installed the App today and tested it. I have the same problem. RadioDroid version 0.66. Android version 8.1.0. It is not a big issue for me because I do not intend to use this feature. Anyway, here is what happened in my case:

03-10 18:11:30.617 10225 21510 21510 D AndroidRuntime: Shutting down VM 03-10 18:11:30.621 10225 21510 21510 E AndroidRuntime: FATAL EXCEPTION: main 03-10 18:11:30.621 10225 21510 21510 E AndroidRuntime: Process: net.programmierecke.radiodroid2, PID: 21510 03-10 18:11:30.621 10225 21510 21510 E AndroidRuntime: android.os.FileUriExposedException: file:///storage/emulated/0/Music/Recordings/2ROCK_Stevie_Ray_Vaughan_Double_Trouble_Voodoo_Child_Slight_Return_2019-03-10_18-11.mp3 exposed beyond app through Intent.getData() 03-10 18:11:30.621 10225 21510 21510 E AndroidRuntime: at android.os.StrictMode.onFileUriExposed(StrictMode.java:1960) 03-10 18:11:30.621 10225 21510 21510 E AndroidRuntime: at android.net.Uri.checkFileUriExposed(Uri.java:2356) 03-10 18:11:30.621 10225 21510 21510 E AndroidRuntime: at android.content.Intent.prepareToLeaveProcess(Intent.java:10622) 03-10 18:11:30.621 10225 21510 21510 E AndroidRuntime: at android.content.Intent.prepareToLeaveProcess(Intent.java:10576) 03-10 18:11:30.621 10225 21510 21510 E AndroidRuntime: at android.app.Instrumentation.execStartActivity(Instrumentation.java:1617) 03-10 18:11:30.621 10225 21510 21510 E AndroidRuntime: at android.app.Activity.startActivityForResult(Activity.java:4621) 03-10 18:11:30.621 10225 21510 21510 E AndroidRuntime: at android.support.v4.app.BaseFragmentActivityApi16.startActivityForResult(BaseFragmentActivityApi16.java:54) 03-10 18:11:30.621 10225 21510 21510 E AndroidRuntime: at android.support.v4.app.FragmentActivity.startActivityForResult(FragmentActivity.java:67) 03-10 18:11:30.621 10225 21510 21510 E AndroidRuntime: at android.support.v4.app.ActivityCompat.startActivityForResult(ActivityCompat.java:152) 03-10 18:11:30.621 10225 21510 21510 E AndroidRuntime: at android.support.v4.app.FragmentActivity.startActivityFromFragment(FragmentActivity.java:793) 03-10 18:11:30.621 10225 21510 21510 E AndroidRuntime: at android.support.v4.app.FragmentActivity$HostCallbacks.onStartActivityFromFragment(FragmentActivity.java:907) 03-10 18:11:30.621 10225 21510 21510 E AndroidRuntime: at android.support.v4.app.Fragment.startActivity(Fragment.java:1009) 03-10 18:11:30.621 10225 21510 21510 E AndroidRuntime: at android.support.v4.app.Fragment.startActivity(Fragment.java:998) 03-10 18:11:30.621 10225 21510 21510 E AndroidRuntime: at net.programmierecke.radiodroid2.FragmentRecordings.ClickOnItem(FragmentRecordings.java:35) 03-10 18:11:30.621 10225 21510 21510 E AndroidRuntime: at net.programmierecke.radiodroid2.FragmentRecordings$1.onItemClick(FragmentRecordings.java:53) 03-10 18:11:30.621 10225 21510 21510 E AndroidRuntime: at android.widget.AdapterView.performItemClick(AdapterView.java:350) 03-10 18:11:30.621 10225 21510 21510 E AndroidRuntime: at android.widget.AbsListView.performItemClick(AbsListView.java:1674) 03-10 18:11:30.621 10225 21510 21510 E AndroidRuntime: at android.widget.AbsListView$PerformClick.run(AbsListView.java:4085) 03-10 18:11:30.621 10225 21510 21510 E AndroidRuntime: at android.widget.AbsListView$10.run(AbsListView.java:6573) 03-10 18:11:30.621 10225 21510 21510 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:790) 03-10 18:11:30.621 10225 21510 21510 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:99) 03-10 18:11:30.621 10225 21510 21510 E AndroidRuntime: at android.os.Looper.loop(Looper.java:164) 03-10 18:11:30.621 10225 21510 21510 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:7000) 03-10 18:11:30.621 10225 21510 21510 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method) 03-10 18:11:30.621 10225 21510 21510 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:441) 03-10 18:11:30.621 10225 21510 21510 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1408)

[werman]

Huh, thanks for posting the exception, now we know where to look!