I have a RAW-enabled camera phone, LG G4 (H-815), which outputs DNG files, but RT has some problems with these.First, it crops the very edges of the DNG as compared to the JPEG, exactly the opposite of what normally happens (however, in this case the JPEG might contain the whole frame without cropping, I'm not sure). I was unable to solve it through camconst.json.

The second problem is the images having abnormal white balance, resulting in the erroneous request of WB range extension (as a DNG from this phone happened to be my first shot of a fully HPS-illuminated scene I deemed worth processing, I thought it's a general problem ).

Yes, I took it myself near noon, and according to my notes, it was sunny with almost no clouds. I wore a black cloth to minimize reflections. A grassy slope was about 100m away, but that was the best place I found in realistic distance. Made with a (hopefully) genuine ColorChecker. The profiles created using the software shipped with it aren't very convincing, though, I had to play a lot with the L*a*b* tool to get anywhere near the camera-JPEGs.

Just for clarity (I replied in a hurry with many distractions, sorry), the not-that-convincing profiles I mentioned primarily relate to different cameras, but none of them can be considered a good reference, one of them doesn't even natively support RAW, only with CHDK. I only wanted to say "I made the CC shot I provided according to the recommendations as far as I could, but don't rely on it too much, it might be good as well as terrible"

Is the 4px-wide cropping of the edges hard-coded? As far as I remember, I couldn't solve it by tweaking camconst.json. While it's mostly psychological for a 16Mpx sensor, it would be cool to get no less data than what the camera-JPEG contains...