Silly question: What is the new ANX demo image?

[gotomech]

I saw a phosh anx and plasma mr1235 demo image on the PmOS site. I didn't mess with the mr1235 one, cause I prefer phosh, but I tried the phosh anx images. It worked like a lot of the previous post-March phosh images haven't for me, but it has no network in it. Even rfkill only showed bluetooth.

What does the anx version do differently? Or is it a version made for someone specifically? Or is it something really obvious and I'm being stupid?

Thanks for anyone who can scratch this curiosity itch!

[MartijnBraam]

It's a build with a different kernel that has a WIP driver for the anx7688 usb-c controller but doesn't have all other functionality enabled, it's not useful for general use.

[gotomech]

It's a build with a different kernel that has a WIP driver for the anx7688 usb-c controller but doesn't have all other functionality enabled, it's not useful for general use.

Thanks, I was really curious since I've been playing with it. While I got you, is there a file I can mess with to change the minimum brightness setting in PmOS? Cause the auto brightness pulls down to black screen a lot until I got into the settings to turn it off, but I like the feature, and the screen being dim, but it's hard to keep it from going black.

[MartijnBraam]

yeah I've noticed this issue, I'm looking into a fix. the current brightness is set in the kernel dtb so not easy to manually change. main issue is that autobrightness is behaving very broken.

[gotomech]

yeah I've noticed this issue, I'm looking into a fix. the current brightness is set in the kernel dtb so not easy to manually change. main issue is that autobrightness is behaving very broken.

Yea, it definitely seemed a little all over the place, but I figured it would get fixed after a little bit anyway.

I just want to get the manual brightness slider under control so that the user experience for people getting the PmOS version of PP don't accidentally black their screens with no clue how to fix it. However, I'm also hoping that you dont go as conservative as mobian and a few others seem to. I like my screen DARK, and I dont know where the voltage cut off is, but I like that I can get my screen very low with the current bar, I just have to be careful not to go too far...

Hopefully I can keep learning enough to be able to just submit some code for you all at some point, but I'm still pretty new to coding for hardware.

[MartijnBraam]

The issue is that brightness is not linear, and some slight manufacturing difference like the specific voltage drop of the leds will cause the point where the screen cuts off to be on different values, due to the nonlinearity of it it also means that the "dark" levels are very close together, so giving the cut-off point some margin for manufacturing differences will mean that for some people the lowest brightness setting is way brighter.

[gotomech]

The issue is that brightness is not linear, and some slight manufacturing difference like the specific voltage drop of the leds will cause the point where the screen cuts off to be on different values, due to the nonlinearity of it it also means that the "dark" levels are very close together, so giving the cut-off point some margin for manufacturing differences will mean that for some people the lowest brightness setting is way brighter.

Understandable, guess I just won the silicon lottery then. Screen too efficient to make it dark and memory too slow to run any of the speed increases everyone tried.

Cant complain too much though, I was one of the first batch of PP's in the US.

Thanks for the knowledge and the hard work. Might have to try the silicon lotto again on a PmOS version of PP in July.

[MartijnBraam]

your display can definetly be as dark as any other phone, it's just that the current pmos config is calibrated to my specific braveheart and that causes issues for some people, we still need to figure out how to do some sort of calibration for that.

[gotomech]

your display can definetly be as dark as any other phone, it's just that the current pmos config is calibrated to my specific braveheart and that causes issues for some people, we still need to figure out how to do some sort of calibration for that.

Could you build a brightness test that runs on a timer? It could be a button in the settings, like "Set Minimum Brightness". Could start at full brightness (or lower to save time) and just reduce by 5-10% or so (dont know the voltage scale for the screen) and just pop up asking if you can still see the screen. If the user clicks yes, go down again, if no, it times out, saves the last state and sets it to the bottom possible value on the brightness scale.

That should allow for people to retest if they get a new screen or mess up, but also be variable for everyone with a new screen. But that's just me spitballing, feel free to ignore.

I'd build it myself to try to show an example, but I still dont even know how to set a minimum brightness...