The engine is showing none of the usual signs of an old / faulty battery. As I said, all other functions seem totally fine.
Besides, would a battery be the cause of such a specific issue? Perhaps it would, I'm not sure, but it seems unlikely to me.
This is how I understand the rename process.
The remote or instance of the app has a database with the ID slots. The displayed name is a value in one of the tables or locations. When you edit name, you are making an overlay name- in other words, that edit is in the remote database and just displaying a new name for that ID slot. Again the data and especially that display name is stored in the remote.
That said- only with an MTH upgrade kit chain files PS3 (or firmware PS2 upgrade kit) boards had a firmware with a BLANK name. This firmware also would get sent the updated name as part of the renaming process at the end and could store that name in the engines memory. I must warn- this is NOT permanent. This is stored in the engine- however, if you did a reset to factory defaults- this name reverts back to totally blank. Again this is specific to MTH upgrade kit boards- and if you happen to flash new chain files- this function goes away. As such it does not apply to all stacker boards- only those that again- came as an upgrade kit and flashed with upgrade kit chain files.
So- as a guess- this is a normal engine (meaning non upgrade kit) situation, you as a consumer are not able to change anything in the engine serial number file because you do not have access and yes- displayed name is part of that file. Only Authorized MTH service techs with Dealer loader can change that value.
But again, what I think is- this is 99.999999999999% in the remote, You edit the name and at the last step are doing the "D" for done which saves and updates the remote- and yes in theory sends a command to the engine- and that command would not execute to save in the engine side- for anything but an upgrade kit board based engine- which yours is not.
Again, what I am saying is- this failure is possibly all in the remote firmware. Something in your engine list database in the remote, or firmware, or some other glitch is preventing you from saving IN THE REMOTE- it's got NOTHING to do with the engine- I mean yes, it sends the command but even in failure- the remote should still be saving and yet is not.
This makes me ask?
What version of firmware is on the remote and your TIU? Ideally 6.1
I realize it is a pain, but have you deleted and then re-added the engine, and THEN tried to rename?
Last resort- have you tried restoring a remote to factorty defaults thus clearing your entire database (probably back it up before doing this to PC) and then attempting to add and change the name of this engine?