You can find an explanation to what’s happening in here:
The simple version is that when the content area defined in your config.lua doesn’t perfectly match with the user’s device resolution, there will some “unused” area that will be handled as mentioned in that post.
You can always find the edges by using math. I’ve written a module that does exactly this. You can find it and a demo project of it over at: