PDA

View Full Version : 4.2.19 on Android beta 8.1 - play anything --> app frozen



dlynch
12-01-2017, 03:15 AM
Got a new Android Beta release today that makes BP totally unusable. Not sure what to do now.

Golbez
12-01-2017, 08:51 AM
KimW this is precisely why the beta should have been taken down the moment all the reports came flooding in. "Today." Today, two weeks after the beta came out, and it's still up.

KimW
12-01-2017, 09:30 AM
KimW this is precisely why the beta should have been taken down the moment all the reports came flooding in. "Today." Today, two weeks after the beta came out, and it's still up.

Golbez, unfortunately that is not my call. I have reported feedback about the release and the bugs.

KimW
12-01-2017, 09:32 AM
Got a new Android Beta release today that makes BP totally unusable. Not sure what to do now.

dlynch, can you elaborate what makes BP "totally unusable" please? I want to report this to the development team.

You can revert back to a previous BP version in the mean time. Thank you,

dlynch
12-01-2017, 11:32 AM
Is the subject line unclear?

With the 8.1 update, when I start any episode playing the app immediately freezes. Totally unresponsive. The only thing I can do at that point is kill it.

I tried playing through the phone speaker, playing through Bluetooth headphones and casting. Same result always.

Cryptonium
12-01-2017, 12:02 PM
I can add to the above that the whole phone seems to freeze for a bit as soon as you hit the play button. While the BeyondPod app screen was visible I was not able to interact with any of its controls, I was not able to even increase or decrease the volume using the hardware buttons.

Clicking on the home button doesn't produce any effect at first but repeated clicks takes me back to the launcher and Android displays a popup saying that the BeyondPod app is not responsive and gives the option of closing it or waiting. All the while the podcast is being played, and will continue playing if you don't kill the app.

EDIT: The app was working fine on the first beta of Android Oreo 8.1, upgrading to beta 2 started the issues.

Golbez
12-01-2017, 12:47 PM
Golbez, unfortunately that is not my call. I have reported feedback about the release and the bugs.

Whose call is it? You've reported feedback, has there been any response from them, at all? If so, then what is it? If not, then who is running the show at all?

dlynch
12-01-2017, 01:10 PM
You can revert back to a previous BP version in the mean time. Thank you,

Yeah, I did that: removed myself from the Beta, uninstalled the app and re-installed.

The only problem with that is that 4.2.16 can't process the backup I made with 4.2.19 (it just spins forever). And there's nothing to be done about that: once the Beta update was installed automatically, it was already too late to make a "just in case" backup.

phalkon30
12-01-2017, 01:58 PM
I'm on oreo 8.1 DP2 and can confirm the issue in this thread. I removed myself from beta and will no longer trust being enrolled. I had to manually start from scratch on all play lists, settings, downloads, etc after reverting to production version.

Shit happens, it's a beta. But the absolute lack of a timeline for a fix and the fact that it was not immediately pulled next business day shows incompetence on the development team for how to run a business.

fredgc
12-01-2017, 03:22 PM
I'm running BeyondPod 4.2.19, on Android Oreo MR1, and I see this in the logcat when BeyondPod freezes:

12-01 12:18:11.097 W/ActivityManager( 1137): Error showing notification for service
12-01 12:18:11.097 W/ActivityManager( 1137): java.lang.RuntimeException: invalid channel for service notification: Notification(channel=null pri=0 contentView=mobi.beyondpod/0x7f0c00cf vibrate=null sound=null defaults=0x0 flags=0x40 color=0x00000000 category=transport actions=4 vis=PUBLIC)
12-01 12:18:11.097 W/ActivityManager( 1137): at com.android.server.am.ServiceRecord$1.run(ServiceR ecord.java:532)
12-01 12:18:11.097 W/ActivityManager( 1137): at android.os.Handler.handleCallback(Handler.java:790 )
12-01 12:18:11.097 W/ActivityManager( 1137): at android.os.Handler.dispatchMessage(Handler.java:99 )
12-01 12:18:11.097 W/ActivityManager( 1137): at android.os.Looper.loop(Looper.java:164)
12-01 12:18:11.097 W/ActivityManager( 1137): at android.os.HandlerThread.run(HandlerThread.java:65 )
12-01 12:18:11.097 W/ActivityManager( 1137): at com.android.server.ServiceThread.run(ServiceThread .java:46)
12-01 12:18:11.131 D/AndroidRuntime(10763): Shutting down VM
12-01 12:18:11.131 E/AndroidRuntime(10763): FATAL EXCEPTION: main
12-01 12:18:11.131 E/AndroidRuntime(10763): Process: mobi.beyondpod, PID: 10763
12-01 12:18:11.131 E/AndroidRuntime(10763): android.app.RemoteServiceException: Bad notification for startForeground: java.lang.RuntimeException: invalid channel for service notification: Notification(channel=null pri=0 contentView=mobi.beyondpod/0x7f0c00cf vibrate=null sound=null defaults=0x0 flags=0x40 color=0x00000000 category=transport actions=4 vis=PUBLIC)
12-01 12:18:11.131 E/AndroidRuntime(10763): at android.app.ActivityThread$H.handleMessage(Activit yThread.java:1768)
12-01 12:18:11.131 E/AndroidRuntime(10763): at android.os.Handler.dispatchMessage(Handler.java:10 6)
12-01 12:18:11.131 E/AndroidRuntime(10763): at android.os.Looper.loop(Looper.java:164)
12-01 12:18:11.131 E/AndroidRuntime(10763): at android.app.ActivityThread.main(ActivityThread.jav a:6494)
12-01 12:18:11.131 E/AndroidRuntime(10763): at java.lang.reflect.Method.invoke(Native Method)
12-01 12:18:11.131 E/AndroidRuntime(10763): at com.android.internal.os.RuntimeInit$MethodAndArgsC aller.run(RuntimeInit.java:438)
12-01 12:18:11.131 E/AndroidRuntime(10763): at com.android.internal.os.ZygoteInit.main(ZygoteInit .java:807)
12-01 12:18:11.268 V/BeyondPod(10763): !!! Unhandled exception !!! reason: [ android.app.RemoteServiceException ] Bad notification for startForeground: java.lang.RuntimeException: invalid channel for service notification: Notification(channel=null pri=0 contentView=mobi.beyondpod/0x7f0c00cf vibrate=null sound=null defaults=0x0 flags=0x40 color=0x00000000 category=transport actions=4 vis=PUBLIC)android.app.RemoteServiceException: Bad notification for startForeground: java.lang.RuntimeException: invalid channel for service notification: Notification(channel=null pri=0 contentView=mobi.beyondpod/0x7f0c00cf vibrate=null sound=null defaults=0x0 flags=0x40 color=0x00000000 category=transport actions=4 vis=PUBLIC)
12-01 12:18:11.268 V/BeyondPod(10763): at android.app.ActivityThread$H.handleMessage(Activit yThread.java:1768)
12-01 12:18:11.268 V/BeyondPod(10763): at android.os.Handler.dispatchMessage(Handler.java:10 6)
12-01 12:18:11.268 V/BeyondPod(10763): at android.os.Looper.loop(Looper.java:164)
12-01 12:18:11.268 V/BeyondPod(10763): at android.app.ActivityThread.main(ActivityThread.jav a:6494)
12-01 12:18:11.268 V/BeyondPod(10763): at java.lang.reflect.Method.invoke(Native Method)
12-01 12:18:11.268 V/BeyondPod(10763): at com.android.internal.os.RuntimeInit$MethodAndArgsC aller.run(RuntimeInit.java:438)
12-01 12:18:11.268 V/BeyondPod(10763): at com.android.internal.os.ZygoteInit.main(ZygoteInit .java:807)
12-01 12:18:11.268 V/BeyondPod(10763): (214 ms. since last trace) [BeyondPodApplication]

jdellachiesa
12-06-2017, 11:38 AM
This is the main problem with this version. Everything else would be normal beta issues, but this makes the app literally unusable.