January 27th, 2013, 10:51 AM
Thread Author (OP)
Join Date: Jul 2012
Location: Birmingham, Alabama USA
Device(s): Samsung Galaxy S5 SM-G900T, Android 4.4.2, Baseband G900TUVU1ANE6, Kernel 3.4.0-1616466, Build K0T49
Thanked 9 Times in 9 Posts
Just want to update this with more information about exactly what I wanted to do and how I resolved the issue.
First off, the issue I was having was that I could not record the remote voice on a phone call within the phone. To be clear, the only way I could get both sides of a conversation was to use speakerphone. After several months of bantering to and fro in forums and beating my head against the wall and getting nothing but failure and frustration, I decided it was the stock version of Android on this Samsung Galaxy Note that was blocking direct access to the hardware. Several guys over at XDA Developers and other forums seemed to be of that opinion.
I tried to find someone there who would modify my phone for me and in my months of frustration with this six-hundred-dollar, useless-to-me brick, I offered to ship the phone and a one-hundred-dollar bill to anyone who would. XDA closed the thread.
Finally, after asking at several TMobile stores in my area, I got a suggestion to go to a repair center named PowerOn in Trussville, Alabama. The store owner said they don't do custom ROMs; but, suggested I could give the job to one of his employees as a private deal as long as I understood the store is not involved.
I gave the job to A. W. He installed one ROM that did not work; but, I posted again in the XDA Developers forum and got a suggestion to use CyanogenMod 10. End of story. It worked.
This confirmed the theory posited by users in other forums that it was the later versions of Android (above about 2.3.5) that was blocking the recording programs' direct access to the hardware on this particular phone (and maybe other phones).