|
@ gameross - IF, and only if a device were to support the PAM NAI (which the Mogul does not appear to have the capability), and you were to use the WModem app, then yes I believe the hack would have some credibility. Since we have what appears to be a non PAM supportive device with the Mogul, there is no reason to bother hacking the value as it won't have any effect anywhere else in the system.
I still wonder about my original assumption though... why on earth would the ICS program not dial the connection when called through itself? Why do we have to connect PIE first and then share the web? Methinks that the ICS installed on the Mogul, is a patched version to deter casual tethering... ICS only reports PAM as a connection option because Sprint has a separate PAM account setup under connections from the factory. ICS is simply reporting all the connections it sees under the connections control panel. If you delete the PAM connection, it disappears under ICS. So why can a 6700 user hit connect on his/her Apache and it will connect fine, but the same program on the Mogul throws up 67 errors?
I wish I had the patience/time to sit and fiddle with it myself... perhaps someone such as colonel or ImCokeMan could extract the ICS files from the Mogul and compare them to the one used with Apache builds... I just can't help but wonder if - by replacing the Mogul's ICS with the older build we used on the Apache - perhaps ICS would funtion once again without the added step of connecting first through PIE?
* once again... just thinking out loud *
|