bluelinelabs / bluelinelabs/Conductor
Animation Glitch
- Dominant language
- Java
- Stars
- 3.9k
- Forks
- 338
- PR merge metrics
- No merged PRs in 30d
Description
This is the second time I use Conductor with a project, but the first time I stumble on this glitch. The gif attached should show the apparent glitch with the HorizontalChangeHandler which can be viewed on the top of the actionBar where you could see a random vertical gray line appear. Now I'm not sure if its because of the way I have layed out things; however, I doubt because I haven't done anything extra in the project yet. Moreover, I tried with several Samsung devices of these android APIs Samsung A5 6.0.1, Samsung A5 5.1.1, and Samsung A8 6.0.1 and the bug can not be seen on Samsung A8; however could be seen on both of the others. Also tried on the emulator on Nexus One 7.1.1 the glitch could be seen and other devices.
What I thought the problem is and what I have tried so far. I started using constraint layout for my layout files, just experimenting around with it, thus most layout hierarchies were wrapped around a constraint layout, changed them to coordinator layouts or anything else to make the layout work, that didnt work.
I'm running a customized style for my activity; however, changing it up made no difference as well. Moreover, I have a welcome screen that takes me to the sign in page which both have no action bars, also does the same bug while animating.
The main lead that I have is that devices that have Density of hdpi, mdpi have this glitch, this glitch can not be seen on xhdpi or xxhdpi, i'm not sure what this finding translates to.

Contributor guide
Research direction
Start by reproducing the attached GIF around HorizontalChangeHandler on the listed Samsung devices and Nexus One emulator, comparing hdpi/mdpi with xhdpi/xxhdpi. Trace the animation entry point and determine whether the random vertical gray line appears during transitions; done means the artifact is no longer visible in the affected density and device cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100