View Single Post
  #3115 (permalink)  
Old 06-27-2010, 07:17 PM
makkonen's Avatar
makkonen
TouchPro Android Guy
Offline
Threadstarter
 
Join Date: May 2007
Posts: 585
Reputation: 3280
makkonen is still contributing even after becoming a VIPmakkonen is still contributing even after becoming a VIPmakkonen is still contributing even after becoming a VIPmakkonen is still contributing even after becoming a VIPmakkonen is still contributing even after becoming a VIPmakkonen is still contributing even after becoming a VIPmakkonen is still contributing even after becoming a VIPmakkonen is still contributing even after becoming a VIPmakkonen is still contributing even after becoming a VIPmakkonen is still contributing even after becoming a VIPmakkonen is still contributing even after becoming a VIP
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Re: Linux/Android on CDMA Touch Pro -- Cricket data connection

Quote:
Originally Posted by 209pcs View Post
So I had stopped pursuing this project after getting my hands on a Droid, but in bringing it over to Cricket I learned a few things that could be applied here. When the flashing process first began and it was rooted and activated, I still didn't have a working connection even though the APN had been configured correctly.

I don't know if the Proxy field within the APN is just for looks or if it actually does something, but data still wasn't working. It seems as if nothing is handling the task of tunneling system-wide traffic through wap.mycricket.com:8080. u2nl solves this problem by performing the aforementioned task. You can get it at www.whiterabbit.org/android/ (it's the the link labeled precompiled arm binary for Droid and other arm based devices ). You'll need to have autostart installed; if you have a Wifi connection you can get it from the market, as well as the Android SDK on your PC. Assuming your working ADB (Android Debugging bridge; make sure it is enabled on your phone) directory is C:/android/tools/, copy u2nl and autostart.sh to C:/android/tools. Do:

adb remount
adb push c:/android/tools/u2nl /system/bin/u2nl
adb push c:/android/tools/autostart.sh /data/opt/autostart.sh
adb shell
chmod 0755 /system/bin/u2nl
chmod 0755 /data/opt/autostart.sh
reboot

++++NOTE++++
The /'s in the paths beginning with C: (Windows' paths) should be changed to backslashes. The Droid keyboard does not have them, so I had to use forward slashes (/) for Windows paths instead. adb commands WILL NOT work unless switched.


I haven't tested this, as my Touch Pro is no longer active, but in theory it should work. Maybe it's time to pull that Pro out of the box again..
I am curious about this. I had never actually considered that the proxy field might not be doing anything -- it wouldn't actually surprise me in the least, though. (Anyone on any carrier have it not work before adding a proxy, and work after?)

There should also be a way to deal with it via some lower level stuff -- netfilter/iptables or some such; anyone on cricket know their way around linux enough to play with this? (The subtext here -- I don't know my way around iptables very well, so if you ask for my guidance, you will probably end up being led far astray.)
Reply With Quote