Hi @RaeW,
Thank you for these answers.
It’s possible to personalize your Trezor homescreen, but if you didn’t modify it then this isn’t an issue here. These homescreens may use more memory in your Trezor, so signing transactions later may fail because of too little memory.
What I meant by sending mining transactions directly to Trezor, was that if you’re mining BTC in a mining pool and have set up the rewards in sats to be sent directly to a receive address in your Trezor wallet, the wallet will receive a lot of small amounts. Hardware wallets like Trezor aren’t meant to be a receiver of so many small transactions of Bitcoin. Instead, people who utilize mining should accumulate the sats rewards in a software wallet or exchange account until the amount is larger and then transfer that amount to the hardware wallet.
Why is many small transactions of BTC type bad for a Trezor? Because, unlike Ethereum, which adds/subtracts transactions from the total in the blockchain, BTC retains all transactions separately so that the total can be calculated from them. This also means all the connected transactions to a Bitcoin must be transmitted together with the amount when you send it and this may be a problem with the memory if there are many transactions to send.
Therefore I think your problem, when the signing is stuck, is because there are too many connected transactions to the BTC you try to send. Memory inside Trezor fills up before it can load all the transactions it needs to send as inputs to the verification process.
When you split up the BTC by sending smaller amounts of BTC at a time, fewer transactions will follow that amount as input for verification and hence the memory isn’t overloaded.
That’s why you can send small amounts but not large amounts of Bitcoin. I think. 
See also: Bitcoin Change Addresses and What is UTXO?
About the other thread I asked if you had the same problem in - @NIYAK asked for your Ticket ID there 16 days ago. It’s unfortunate that you haven’t received a reply on your ticket yet, but they have a standard reply time of upto 20 days. If you want to speed up your ticket process you should post your Ticket ID in the thread - or send it on PM/DM directly to the Community support representative who asks for it.