...sigh........No, ldeveraux, this is NOT a useless thread. In fact, according to my research, this thread may just contain the key for the entire non-Google Android privileged code development community. Here is why I think so.
ahmad83it wrote on 28th August 2015, 07:06 PM:
"...so , how to unlock the hotspot wifi..."
This is AN EXTREMELY IMPORTANT QUESTION. You all may be thinking that I'm the only one with this issue. NOT. Here's a perfect example of what I'm talking about:
http://developer.samsung.com/forum/board/thread/view.do?boardName=GeneralB&messageId=178834
This developer had to root his phone to test and debug privileged code. That was in 2012. But nowadays:
- We know that the publicly available retail editions of Verizon Samsung devices are protected with qfuse-enhanced, signed, locked bootloaders. Any attempt to change the core system code in these devices, even by a Google certified developer (which I am), will trip a qfuse and brick the device.
- We know that the publicly available developer editions of LTE-enabled Samsung devices have unlocked, unprotected bootloaders - but they also are NOT configured for any LTE carrier, so you cannot get online via an LTE protocol (3G, 4G) with these devices. Therefore, privileged code or not, one CANNOT write code that communicates online through LTE protocols that will work. This includes code that communicates with web services, CDNs, online databases, and cloud-based services.
Now...landshark68 wrote: "...I don't think [enabling WIFI connectivity] can be done, but you should look through the titles of the threads in the general and Q&A sections to see if any of them deal specifically with the WiFi tether on the OE1 or OG5 builds..."
This is a critical point. Given my information that I outlined above, based on my research, the ONLY way that a 3rd party developer - in other words, a developer that is not an employee of Verizon or Google - can test and debug privileged code and/or code that communicates with the internet, on a genuine Samsung device, is on a developer edition of the device WITH WIFI ENABLED.
I have emailed a member of the Samsung security team, explaining this issue. Hopefully, an answer will come from it.