Parallax effect and Merged AppBar problems
luis901101 opened this issue · 7 comments
I have had problems with the parallax effect (BackdropBottomSheetBehavior) and the (MergedAppBarLayoutBehavior) in some specific devices: LG K20 Android 7.0 and Samsung Note 8 Android 7.0 The Backdrop element doesn't move always, some times it freezes anywhere in the middle when changing from COLLAPSED to ANCHOR_POINT and reverse. In addition the MergedAppBarLayoutBehavior behaves similar when changing from EXPANDED to ANCHOR_POINT.
Watch this video to see better: https://mega.nz/#!NJVWQASD!LU7CMAHwDy0CiAyD14dCygUVPoiK8G3owR5G22O3Zmg
I don't understand why this is happening.
Neither I but I'm guessing it's related to Android 7.0 . Have you tried with devices with another SO version? like 5.0, 6.0, 7.1.1, 8
It would be good if we can know in which OS is happening.
At this moment I'm too bussy, so I can't help you in the search, if you can found the problem and create a pull request with the solution, the community will say thank you :)
I have tested all that versions, even custom and stock in devices like Samsung, HTC, LG, Xiaomi, BLU, Sony and only this 2 devices shows the problem, I think is something related to a firmware customization by OEM because I have tested in Note 8 but diferent android version and works fine, then after update OS, the problem shows again
So can we say it's happening only in LG K20 Android 7.0 and Samsung Note 8 Android 7.0 as you said before right?
If so we have 2 options:
- you can debug the library using those device in order to find whats going on and create a pull request.
- if you don't have time for it, you can leave the steps needed to reproduce the issue and I hope some day I can have free time to check it. Besides I will change the tilte of the issue for something more accurated to this issue.
I wouldn't like to say only in LG K20 and Note 8 Android 7.0 because there are lots of devices I have not tested but it is a start point. I had the chance to debug the lib in the LG K20 (a friend's phone) but it was too little time and I didn't get anything wrong.
I have the apk lib sample installed in my phone (S7 in which works perfectly) and every time I can I test it in other devices in order to know if there is any pattern or whatever.
The steps to reproduce the issue is very simple just run the sample you provide, that's all I did in the video I shared (the device of the video is the LG K20)
I don't understand about the LG K20, can you reproduce the issue in a real device or not?
The steps to reproduce the issue is very simple just run the sample you provide, that's all I did in the video I shared (the device of the video is the LG K20)
Of course the issue can be reproduced in a real device that's what I have been talking all the time specifically the LG K20 and Note 8. (Sorry if I wasn't clear about this) To reproduce the issue just clone this lib, open it with Android Studio and click Run... The issue appears only in LG K20 and Note 8 with Android 7.0 AFAIK.
I had the chance to debug the lib in the LG K20 (a friend's phone) but it was too little time and I didn't get anything wrong.
I mean I didn't find any bug debugging but the lib behaves wrong.
Like you I don't have too much time right now, but it will be really nice to fix this because I had used this lib in some projects and I recommended it to some friends to use it too.
Thanks in advance
oh I got it! well first of all thank you for sharing what you found.
Second, you are right, we need to found what's going on in those devices.
and third, thank you for recommend the library :D.