MobileRead Forums - View Single Post

kguil · 12-26-2012, 08:45 AM

So, Kindle does this as does Readmill. Stanza, Kobo and Bluefire don't.

BUT... Stanza, Kobo and Bluefire, implement brightness control using a black layer and vary its opacity to simulate brightness. This is not true hardware brightness control. This was/is the norm for reading apps that allow you to control brightness on iOS 4 and before. Brightness control APIs were introduced in iOS 5+. The big disadvantage of this method is that the brightness 'appears' to be reduced but, physically, the screen could still be working full throttle resulting in faster battery drain.

All in all, I'd rather leave Marvin use physical brightness control and accept this iOS 'artefact'. In fact, all the apps I tried that let you change physical brightness manifest this behaviour. What do you think?

12-26-2012, 08:45 AM	#358
kguil Addict Posts: 1,215 Karma: 1836966 Join Date: Feb 2010 Location: Malta, Europe Device: Marvin for iOS	So, Kindle does this as does Readmill. Stanza, Kobo and Bluefire don't. BUT... Stanza, Kobo and Bluefire, implement brightness control using a black layer and vary its opacity to simulate brightness. This is not true hardware brightness control. This was/is the norm for reading apps that allow you to control brightness on iOS 4 and before. Brightness control APIs were introduced in iOS 5+. The big disadvantage of this method is that the brightness 'appears' to be reduced but, physically, the screen could still be working full throttle resulting in faster battery drain. All in all, I'd rather leave Marvin use physical brightness control and accept this iOS 'artefact'. In fact, all the apps I tried that let you change physical brightness manifest this behaviour. What do you think?