Found crashes on Pixel, Samsung and Xiaomeme till now
The condition is much worse in Samsung and Pixels Devices
The condition is much worse in Samsung and Pixels Devices
Forwarded from แถ แตแตสณ (*inisial J)
jrInfected-v3.4.0.apk
1.6 MB
v 3.4.0 | New Stable UPDATE
+ Added Battery Landscape Mode For Havoc (Bobok Ephone and Car ).
+ Added Wifi and Signal Icon Ephone Round.
+ Added Costum Volume Unknown Style.
+ Added Bg Volume for Corvus.
+ Adding Progress Drawable Style A.
+ Added Typograpy Clock Indonesia.
+ Support more custom ROM.
+ Added Digital Clock Box.
+ Added Qs Shape L.
- Fix Some Padding.
Cheers!
Join channel - @jrmod703
Join Support group - @flowdor_theme
Join Flowdor - @flowdor
#Flowdor #JrInfected #Addon #AospQ
+ Added Battery Landscape Mode For Havoc (Bobok Ephone and Car ).
+ Added Wifi and Signal Icon Ephone Round.
+ Added Costum Volume Unknown Style.
+ Added Bg Volume for Corvus.
+ Adding Progress Drawable Style A.
+ Added Typograpy Clock Indonesia.
+ Support more custom ROM.
+ Added Digital Clock Box.
+ Added Qs Shape L.
- Fix Some Padding.
Cheers!
Join channel - @jrmod703
Join Support group - @flowdor_theme
Join Flowdor - @flowdor
#Flowdor #JrInfected #Addon #AospQ
Not Kidding! ๐
The more you tell people not to do something, they will do it anyway ๐ + it's lockdown everywhere
The more you tell people not to do something, they will do it anyway ๐ + it's lockdown everywhere
Forwarded from OC'D
In case anyone fucked up
delete all files starting with wallpaper from
delete all files starting with wallpaper from
/data/system/users/0Forwarded from Davide
Regarding the image bug: why does it happen?
So, as stated here, the image in question has a much larger color space than normal images.
The sysui crash log is this one and from here you can see that something goes out of bounds (basically you try to access an element in an array outside of the array size.
Checking the aosp code we can see that the related piece of code is this, basically y is a value larger than 255, leading to an out of bounds exception as the array has as max index 255.
The variable y used for accessing the item in the array is calculated here, and as you can see its a sum of the red + blue + green color values. This works fine if the color space is rgb (as color cant go over a value of 255), but with a larger color space colors can go over said value.
This leads to the sum being larger than the 255 max value, leading to a crash.
The easiest fix for this for now is adding
Thanks for attending my ted talk
So, as stated here, the image in question has a much larger color space than normal images.
The sysui crash log is this one and from here you can see that something goes out of bounds (basically you try to access an element in an array outside of the array size.
Checking the aosp code we can see that the related piece of code is this, basically y is a value larger than 255, leading to an out of bounds exception as the array has as max index 255.
The variable y used for accessing the item in the array is calculated here, and as you can see its a sum of the red + blue + green color values. This works fine if the color space is rgb (as color cant go over a value of 255), but with a larger color space colors can go over said value.
This leads to the sum being larger than the 255 max value, leading to a crash.
The easiest fix for this for now is adding
if (y > 255) y = 255; in this line.Thanks for attending my ted talk
Twitter
Sleepy Kuma
@UniverseIce I found the cause in the Korean tech community. It looks like a 'Google Skia' color profile issue. (P1) Gimp (P2) S10 default gallery app (L. Google Skia, R. sRGB) source : https://t.co/cQmsRXGBF9