Closed fawzy46 closed 7 years ago
Did you force closed YouTube/rebooted device? Check logs.
On Thu, Sep 7, 2017, 12:34 fawzy46 notifications@github.com wrote:
Dose not work with last update 12.34.55
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/pylerSM/YouTubeBackgroundPlayback/issues/339, or mute the thread https://github.com/notifications/unsubscribe-auth/AMxxbGn_DsqBlHWF14AYCcikN0jEmO-Jks5sf8atgaJpZM4PPnoQ .
Yes I have rebooted my phone but dose not work,do you need xposed logs ??
Yes, please. They should help for now.a
On Thu, Sep 7, 2017, 12:51 fawzy46 notifications@github.com wrote:
Yes I have rebooted my phone but dose not work,do you need xposed logs ??
— You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/pylerSM/YouTubeBackgroundPlayback/issues/339#issuecomment-327765026, or mute the thread https://github.com/notifications/unsubscribe-auth/AMxxbIAQvjsjxtvVLH1JqEBdOx83jv36ks5sf8qlgaJpZM4PPnoQ .
https://drive.google.com/file/d/0Bz9tTgInjOvlMm5aLU5JVTMyRTg/view?usp=drivesdk
Thx for the fast response
Can you try disabling ad away? Also, is it whole log? I can't see anything related to YTBP module. Maybe it's drive on phone not showing it. I will check it again later.
On Thu, Sep 7, 2017, 12:59 fawzy46 notifications@github.com wrote:
https://drive.google.com/file/d/0Bz9tTgInjOvlMm5aLU5JVTMyRTg/view?usp=drivesdk
Thx for the fast response
— You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/pylerSM/YouTubeBackgroundPlayback/issues/339#issuecomment-327766593, or mute the thread https://github.com/notifications/unsubscribe-auth/AMxxbC2Qj7L4upYZSVkEkEDj8e01Fn-Dks5sf8yIgaJpZM4PPnoQ .
I don't think the ad away is the proplem because I didn't update it and YTBP was working well before update youtube but I will try to disable it and see what will happen and I will check the log again
I just want to add that it does not work for me either anymore. The Xposed logs are similarly useless:
09-07 16:52:03.029 I/Xposed ( 330): -----------------
09-07 16:52:03.029 I/Xposed ( 330): Starting Xposed version 87.1 (custom build by dkcldark / 20161129), compiled for SDK 21
09-07 16:52:03.029 I/Xposed ( 330): Device: GT-I9515 (samsung), Android version 5.0.1 (SDK 21)
09-07 16:52:03.029 I/Xposed ( 330): ROM: Built.with.SuperRs.Kitchen
09-07 16:52:03.029 I/Xposed ( 330): Build fingerprint: samsung/jfveltexx/jfvelte:5.0.1/LRX22C/I9515XXU1BQD2:user/release-keys
09-07 16:52:03.029 I/Xposed ( 330): Platform: armeabi-v7a, 32-bit binary, system server: yes
09-07 16:52:03.029 I/Xposed ( 330): SELinux enabled: yes, enforcing: yes
09-07 16:52:03.059 I/Xposed ( 330): -----------------
09-07 16:52:03.059 I/Xposed ( 330): Added Xposed (/system/framework/XposedBridge.jar) to CLASSPATH
09-07 16:52:03.469 I/Xposed ( 330): Detected ART runtime
09-07 16:52:03.489 I/Xposed ( 330): Found Xposed class 'de/robv/android/xposed/XposedBridge', now initializing
09-07 16:52:05.041 I/Xposed ( 330): Loading modules from /data/app/com.pyler.youtubebackgroundplayback-2/base.apk
09-07 16:52:05.071 I/Xposed ( 330): Loading class com.pyler.youtubebackgroundplayback.YouTubeBackgroundPlayback
09-07 16:52:05.091 I/Xposed ( 330): Loading modules from /data/app/ma.wanam.xposedlollipop-1/base.apk
09-07 16:52:05.121 I/Xposed ( 330): Loading class ma.wanam.xposedlollipop.Xposed
I installed the version posted in #336 by @th3an7. I have also rebooted, force stopped YT and tried clearing application caches both in the OS and from the recovery menu. Relevant versions:
YouTube: 12.34.55 YT Background Playback: 2.0.4
So far the only thing that has worked for me is to go down to a different version. Currently using 12.21.57 and no problems so far.
Does the module work with the previous version of YT? I mean with 12.34.54?
If the answer is yes, then they indeed changed version naming and we need to find a fix for that.
The previous versions were named as XXXXXXXXXX (10 numbers), now they probably started to naming it as XX.XX.XX (as we can see it with-in the app). This may become a problem...
I can't recall if module writes something to logcat, but you can check it :P
Nevermind... I don't want to remove that comment. For now :P
Can you check if it's working now? Apparently I've put wrong classes...
Seems like I shouldn't do anything at 4AM :P
Yup, working fine now. Thanks for the quick fix
It's working fine thx
Should I close the issue now??
No need, I will do it :)
Glad it works again :P
Dose not work with last update 12.34.55