I missed this a while back. You were referring to this in the code, right?
When I get a chance I’ll switch that to a ‘\r’ like it is in the mainline code and see if that helps. If so, I can add it into my repo and do an updated build.
Someone else had mentioned an issue with the keyboard input in my build but didn’t mention anything specific of the error they said they received, so I won’t know what to go on for that until I hear back. But maybe I can get this input issue fixed too. 
I wasn’t sure why some of the code changes were made in the PicoCalc patch, but just to be safe I tried to carefully port everything over in my build. Figured bug fixes could follow later, and my main goal was to get something as close to the original PicoCalc version as possible.