Menu screens don't use all vertical soace

[prutledge]

Got new RPi b+ yesterday, installed rasplex (0.4.1) and it is working great and the whole system is beginning to get a pretty decent WAF! Calibrated video so it fits my Samsung 55" TV (1920x1080). Videos and pictures fit the screen perfectly, but the menu screens and music screens leave some blank space (black) at the bottom (not the sides or the top) that isn’t filled with the background image.


I tried returning the overscan settings to 0,0 for both corners. That didn’t change anything and only caused parts of the screen to disappear (as one would expect with incorrect overscan settings, I mow have it back to normal).


Any ideas on what I’m missing or is this normal? If normal it looks a little janky…

[system]

Got new RPi b+ yesterday, installed rasplex (0.4.1) and it is working great and the whole system is beginning to get a pretty decent WAF! Calibrated video so it fits my Samsung 55" TV (1920x1080). Videos and pictures fit the screen perfectly, but the menu screens and music screens leave some blank space (black) at the bottom (not the sides or the top) that isn't filled with the background image.
I tried returning the overscan settings to 0,0 for both corners. That didn't change anything and only caused parts of the screen to disappear (as one would expect with incorrect overscan settings, I mow have it back to normal).
Any ideas on what I'm missing or is this normal? If normal it looks a little janky... :)

This is not normal, suggest reflashing the card again as obviously something you have set it not quite right.

Regards

[prutledge]

Thanks Ned. After reflashing several times, I pinned the issue down to when I edited my overclock settings using:

mount -o remount,rw /flash
nano /flash/config.txt
reboot

I was able to achieve what I wanted for overclocking, but every time it would cause what I described in the OP.

The solution was to edit the config.txt file after flashing on my Windows 7 machine before I put it in the Pi to boot for the first time, avoiding the mount/remount.

Thank you very much for your help!

[system]

Thanks Ned. After reflashing several times, I pinned the issue down to when I edited my overclock settings using:

mount -o remount,rw /flash
nano /flash/config.txt
reboot

I was able to achieve what I wanted for overclocking, but every time it would cause what I described in the OP.
 
The solution was to edit the config.txt file after flashing on my Windows 7 machine before I put it in the Pi to boot for the first time, avoiding the mount/remount.
 
Thank you very much for your help!

That's the best way to do it. Glad it's working OK now.

Regards

[dlanor]

Thanks Ned. After reflashing several times, I pinned the issue down to when I edited my overclock settings using:

mount -o remount,rw /flash
nano /flash/config.txt
reboot

I was able to achieve what I wanted for overclocking, but every time it would cause what I described in the OP.

I think you could have avoided that problem by remounting as read-only after your editing.
 

The solution was to edit the config.txt file after flashing on my Windows 7 machine before I put it in the Pi to boot for the first time, avoiding the mount/remount.

That's a good way to avoid Linux mount complications. I edit config.txt on a Win7 PC every time.

Best regards: dlanor

[system]

I think you could have avoided that problem by remounting as read-only after your editing. That's a good way to avoid Linux mount complications.

It always remounts as read only when rebooting, so no need to remount as read only after editing as you have to reboot for changes to take effect.

Regards

[dlanor]

It always remounts as read only when rebooting, so no need to remount as read only after editing as you have to reboot for changes to take effect.

I see what you mean, but my guess is that his leaving it in read-write mode after his editing (for an unknown period of time and usage) caused some more changes apart from what he had intended, since the simple "config.txt" change he did make could not possibly cause those symptoms he described. Something else must have happened, and probably did so while the filesystem was unprotected.

My point is just that after setting the filesystem to read-write mode for some change, it's always safest to set it back to normal once that change is completed.

Best regards: dlanor