Geekzone: technology news, blogs, forums
Guest
Welcome Guest.
You haven't logged in yet. If you don't have an account you can register now.


Batman

Mad Scientist
30014 posts

Uber Geek
+1 received by user: 6217

Trusted
Lifetime subscriber

#272310 18-Jun-2020 23:16
Send private message


Filter this topic showing only the reply marked as answer Create new topic
Batman

Mad Scientist
30014 posts

Uber Geek
+1 received by user: 6217

Trusted
Lifetime subscriber

  #2507797 18-Jun-2020 23:17
Send private message

something about colour profile and a single pixel bricking phone!

 

(yes i watched it but it's a bit tricky to fully understand)




jamesrt
1666 posts

Uber Geek
+1 received by user: 946

ID Verified
Trusted
Lifetime subscriber

  #2507850 19-Jun-2020 08:36
Send private message

I killed a phone once with a wallpaper - it was a very-high-res (almost gigapixel, from memory) shot of the moon, which I rescaled to appropriate size for the phone, but it still died horribly.

 

The user interface kept crashing on reboot, so there was no way to reset the wallpaper back again - a factory reset from recovery mode fixed it, of course; and almost everything self-restored from "the cloud" with the exception of a couple of work-related 2FA tokens (which is pretty much what you'd expect).

 

I thought at the time I'd just not been careful enough with resizing the wallpaper and I'd blown the memory buffer size(s) or something; but who knows?

 

There are many, many cases on the internet with Android dying due to wallpaper - seems a little fragile if you ask me!


bazzer
3438 posts

Uber Geek
+1 received by user: 267

Trusted

  #2507942 19-Jun-2020 11:03
Send private message

I don't know if I buy the explanation. For a start (255, 255, 243) looks nothing like the pixel he's talking about (it would be pretty much a yellowish white). If what he's saying is true then, without knowing the details of the rounding, anything with (>254, 255, >236) would exhibit the same issue, surely?

 

It's possible he just dumbed down the explanation for his video but I'm still too scared to make it my wallpaper. :)




concordnz
492 posts

Ultimate Geek
+1 received by user: 277

Trusted
EMT (R)

  #2507963 19-Jun-2020 11:31
Send private message

Pretty much just a bug in android colour rendering

(Androids own rounding of colourspace values causes a "over maximum acceptable value")

It's exceedingly rare - because very few images have these extreme colours (only if they have been edited/tweaked) - & likely to occur only in 'artifacts' - so probably less than 0.000001% chance.

It will happen with 'any' image where this occurs.
(I could see malicious actors now specifically posting wallpapers with this error - to specifically brick people's phones 'just for fun'.....)
So we are likely to see an increase now.

The rendering error is 'compounded' when you set it as a wallpaper - because Androids 'default behavior' in this instance is to try rebooting to fix the problem (which it cant do - because it's a built-in design bug)

So the phone gets stuck in a endless bootloop.

Pretty sucky bug - but no different to many of Microsoft's BSOD's bootloops caused by bugs in their updates

They are fixing it in the next release of Android.
(& a patch likely be released for existing devices at some point)


Filter this topic showing only the reply marked as answer Create new topic








Geekzone Live »

Try automatic live updates from Geekzone directly in your browser, without refreshing the page, with Geekzone Live now.



Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly to your computer or smartphone by using a feed reader.