By tonemelle
Mon May 25, 2020 4:06 pm
Has any1 experienced this in 2.8?
I noticed this since 2.7 and I’ve been using 2.6 since but noticed in the 2.8 update that that bug is still there though not in 2.6. Is there a fix for this? I'm wondering if it's a firmware issue..
I noticed this since 2.7 and I’ve been using 2.6 since but noticed in the 2.8 update that that bug is still there though not in 2.6. Is there a fix for this? I'm wondering if it's a firmware issue..