Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

samsung j5: pixel rain #335

Open
chr-chr opened this issue Oct 23, 2023 · 3 comments
Open

samsung j5: pixel rain #335

chr-chr opened this issue Oct 23, 2023 · 3 comments
Labels
help wanted Extra attention is needed

Comments

@chr-chr
Copy link

chr-chr commented Oct 23, 2023

Hi,

The display works good, but ...
I get a pixel rain on certains colors, e.g. it doesn't like #d4d4d4

This also happens on posh/wayland.

Any help appreciated

IMG_20231023_213345
@wonderfulShrineMaidenOfParadise
Copy link

It's a known issue, but the cause is unknown. I almost forgot it happens.

Some clues about the panel driver:

Perhaps we need some sort of flags for these 2 modes, but I don't even understand what they are.

@chr-chr
Copy link
Author

chr-chr commented Oct 26, 2023 •
edited
Loading

Well,

I'm already hacking on this, my devices uses "ams497hy01":

#333

However, I almost got the assumption this is broken HW since the displays do have some cracks.
But ... the rain modulates with system load and not by applying mechanical force.

I have 2 devices in a row having this glitch. On posh hardly to notice since it doesn't use that colour. But uploading a screenshot of the mate desktop shows the same glitches.

Meanwhile I flashed another 2 devices with PMOS mate/posh: flawless.

And I reflashed one of the pixel rain back to lineage: flawless !

And one devices, lineage ok but with PMOS just a flickering screen ...

Actually I assume all my devices are the same type and I updated baseband fw on all of them. Going to double check if these devices differs.

@stephan-gh stephan-gh added the help wanted Extra attention is needed label Oct 26, 2023
@wonderfulShrineMaidenOfParadise
Copy link

Currently it's confirmed on both J5(X), with unscratched panels.
Fun fact: The glitch pattern varies on different phones, even on the same variant of J5X.

TravMurav pushed a commit that referenced this issue Jul 17, 2024
@borkmann
selftests/bpf: Extend tcx tests to cover late tcx_entry release
5f1d18d 
Add a test case which replaces an active ingress qdisc while keeping the
miniq in-tact during the transition period to the new clsact qdisc.

  # ./vmtest.sh -- ./test_progs -t tc_link
  [...]
  ./test_progs -t tc_link
  [    3.412871] bpf_testmod: loading out-of-tree module taints kernel.
  [    3.413343] bpf_testmod: module verification failed: signature and/or required key missing - tainting kernel
  #332     tc_links_after:OK
  #333     tc_links_append:OK
  #334     tc_links_basic:OK
  #335     tc_links_before:OK
  #336     tc_links_chain_classic:OK
  #337     tc_links_chain_mixed:OK
  #338     tc_links_dev_chain0:OK
  #339     tc_links_dev_cleanup:OK
  #340     tc_links_dev_mixed:OK
  #341     tc_links_ingress:OK
  #342     tc_links_invalid:OK
  #343     tc_links_prepend:OK
  #344     tc_links_replace:OK
  #345     tc_links_revision:OK
  Summary: 14/0 PASSED, 0 SKIPPED, 0 FAILED

Signed-off-by: Daniel Borkmann <[email protected]>
Cc: Martin KaFai Lau <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Martin KaFai Lau <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
help wanted Extra attention is needed
Milestone
No milestone
Development

No branches or pull requests
3 participants
@stephan-gh @chr-chr @wonderfulShrineMaidenOfParadise