Daily Builds page for 2123 says :
This sounds very interesting. How can we, the app devs make use of this new capability? Thanks much.
You could save it to an analytics service. You could print it in your log files.
It’s to gather debug information for you to provide us if you run into a problem where the hardware/drivers might be suspect.
Rob
I’m sorry for badly phrasing my question. I understand and love the idea! Thanks much for building this capability into the product. My question is how to activate it in my code. Is there an API doc page you can link me to? Thank you.
Have you looked in the console log to see if we are outputting it automatically? I’ve not downloaded that version yet.
Rob
It outputs on loading the simulator, but I think ksan is asking if there’s a function to grab that info in the API.
Precisely. It seems to print this info to Console but this is of little use as I can’t use it to troubleshoot customer problems. If we could use an API to grab the info then we could include it in an “email support info” etc type button somewhere in our app or even load to Flurry for statistical reference. Thanks much
Please go to http://feedback.coronalabs.com and add a feature request for this. I’ve not talked to engineering about this. We could be outputting this before Lua takes over and I’m not sure what all would be needed to get it into the Lua state.
Rob
Ok. Nevermind. Not going to happen then. Thanks.
Jeeze, Kerem, you’re so cynical for someone so young! (I have no idea how old you are…) 
I see the Feedback system like this –
CL Engineer #1: I’m not sure whether to add feature X or feature Y this week. I think they’d both be neat.
CL Engineer #2: Well, Y has more feature requests, let’s do that one.
CL Engineer #1: Okay!
And…
CL Engineer #1: Hey, feature Z is the most requested this week. Should we do that?
CL Engineer #2: Naw, that’s stupid. Let’s do feature T instead.
CL Engineer #1: Almost nobody requested that, but it *is* cool. Okay!
In other words, in case of a tie (what users vote on - what CL engineers want to work on) then the feature request list comes into play.
Jay
PS - The above is a work of fiction. I have no idea how closely it relates to real life. I just know that if I had a feature request list, that’s how I’d run it. 
[EDIT: Now that I think about it, that’s how I work on Outlaw. Do you think the most asked for feature has been implemented? Nope.]
Hey Jay, you forgot what probably happens next…
Weekly Incident Review & Strategy Meeting
CL Engineers #1 & #2 - Hey frontline support guys. Lets hear it. What are the whiners whining about these days… Those unappreciative sods…
CL Frontline Guy 1 - There is this [insert expletives of choice] guy… Keeps harping about these year old bugs… Ah the nerve…
CL Boss #2 - What? Thats only 1% of what we do. Forget it. Tell him to go write some feature requests…
CL Engineers #1 & #2 - Talking of which… We couldn’t decide which feature requests to tackle next
CL Boss #1 - Our strategic direction bla bla, competitive pressure, etc etc… Go do Graphics 2 with a side of Doorz support.
CL PR person - But but but, what about all that stuff we published on Roadmap?
All head turn to her … in unison
On that note, anyone seen any Roadmap updates of late?
Someone needs to turn this thread into an off-Broadway play.
I’m not really sure what is being asked for here … the complete implementation of the “feature” is:
-- Output support info to debug log print("Platform: " ..tostring(system.getInfo("model")) .." / " ..tostring(system.getInfo("architectureInfo")) .." / " ..tostring(system.getInfo("platformVersion")) .." / " ..tostring(system.getInfo("GL\_RENDERER")) .." / " ..tostring(system.getInfo("GL\_VERSION")))
As you can see it uses nothing but existing, documented API calls. If you want to put the same info in a string and send it somewhere, you are more than welcome to do so.
Perry, thanks much for this clarification. It makes all the difference to have a clear and specific answer as opposed to a blanket “Submit a feature request” response. Thank you.
You could save it to an analytics service. You could print it in your log files.
It’s to gather debug information for you to provide us if you run into a problem where the hardware/drivers might be suspect.
Rob
I’m sorry for badly phrasing my question. I understand and love the idea! Thanks much for building this capability into the product. My question is how to activate it in my code. Is there an API doc page you can link me to? Thank you.
Have you looked in the console log to see if we are outputting it automatically? I’ve not downloaded that version yet.
Rob
It outputs on loading the simulator, but I think ksan is asking if there’s a function to grab that info in the API.
Precisely. It seems to print this info to Console but this is of little use as I can’t use it to troubleshoot customer problems. If we could use an API to grab the info then we could include it in an “email support info” etc type button somewhere in our app or even load to Flurry for statistical reference. Thanks much
Please go to http://feedback.coronalabs.com and add a feature request for this. I’ve not talked to engineering about this. We could be outputting this before Lua takes over and I’m not sure what all would be needed to get it into the Lua state.
Rob
Ok. Nevermind. Not going to happen then. Thanks.