Android running on US Cellular data service **Solved for most***

[chrialex]

Mine worked with the default generic APN entry with no user/pass after updating to the newest RootFS and the files from the other day. Using the same data.img and startup as I was before. Good Job!!!!

[bytethegroove]

Which kernal are you using chrialex?

The kernal site is confusing to me, not sure which build I should I grab..

thanks
byte

[eval-]

Originally Posted by bytethegroove

Which kernal are you using chrialex?

The kernal site is confusing to me, not sure which build I should I grab..

thanks
byte

if you want fixed double-tap bug (maybe this is a diamond-only prob?) i would download something newer than march 17th (i fixed it on the 14th but a clean patch by bzo didn't get merged until a bit later)

if you want stinebd's wifi tethering to work you should get newer than the 19th. in general, newer is better, unless it breaks something. then just try a slightly older one... you can see people vote positive/negative on:
http://glemsom.anapnea.net/android/htc-msm-android/

i tend to avoid the kernels with many negative votes =)

as for rootfs:
http://xdandroid.southcape.org/rootfs/

i almost always grab the latest and keep it unless something broke. a lot of good changes have been made recently, but there's still always the possibility some of these changes are bad for your device (even if they were good for a diamond or diamond2 or whatever). so, get an older one until it works again. (rootfs is something to try changing if you get lots of 3G disconnects, etc)

you only ever need to update zImage & modules (in case of kernel) or rootfs.img (in case of rootfs) so you can leave your system.sqsh, data.img, startup.txt, conf/ folder and all that alone. just back up your working zImage/modules/rootfs in a folder so you can always revert if needed.

[dfgas]

Originally Posted by eval-

if you want fixed double-tap bug (maybe this is a diamond-only prob?) i would download something newer than march 17th (i fixed it on the 14th but a clean patch by bzo didn't get merged until a bit later)

if you want stinebd's wifi tethering to work you should get newer than the 19th. in general, newer is better, unless it breaks something. then just try a slightly older one... you can see people vote positive/negative on:
http://glemsom.anapnea.net/android/htc-msm-android/

i tend to avoid the kernels with many negative votes =)

as for rootfs:
http://xdandroid.southcape.org/rootfs/

i almost always grab the latest and keep it unless something broke. a lot of good changes have been made recently, but there's still always the possibility some of these changes are bad for your device (even if they were good for a diamond or diamond2 or whatever). so, get an older one until it works again. (rootfs is something to try changing if you get lots of 3G disconnects, etc)

you only ever need to update zImage & modules (in case of kernel) or rootfs.img (in case of rootfs) so you can leave your system.sqsh, data.img, startup.txt, conf/ folder and all that alone. just back up your working zImage/modules/rootfs in a folder so you can always revert if needed.

the rootfs files that are on there are they for gsm or cdma? i tried one and i couldn't use phone service. i just figured they were gsm only.

[eval-]

Originally Posted by dfgas

the rootfs files that are on there are they for gsm or cdma? i tried one and i couldn't use phone service. i just figured they were gsm only.

Good question. It looks like there's a separate RIL for CDMA that MrPippy made, and prolly USCC people need it too. So we have to wait until MrPippy incorporates the latest fixes into his htcgeneric-ril.c ...

Sorry I pointed you all the to autobuilt rootfs, that's a mistake... =/
(I have a diam500, only now realizing what you rhod400/500 deal with...)

[skuddy]

Originally Posted by dfgas

Cliffture post @ #86
Eval post @ #112 This whole post is a copy of eval's post. Thank you both and the people you worked with at getting this resolved. Please press thanks on their posts for their hard work.

STEP 1: find the right username@uscc.net for /etc/ppp/pap-secrets & options.smd1

Play around until you find your username. Usually it is your phone number, sometimes it can be your ESN or MEID number. Edit these files after dialing ##778 and pressing "View." If dude420420 is right, this should give you your account username. You might have to call USCC to find out.

pap-secrets needs to look like:

username@uscc.net * username

options.smd1 needs to have:

user username@uscc.net

as the last line. (leave all the others)

After changing these files, try Airplane On / Airplane Off to test. If it works, move to Step 2. If it doesn't, try to figure out why. Try a different username. If you can't find one that works, look up 'adb' & 'logcat' in the forums and online and look for lines with "pppd" in your logcat.


STEP 2: Copy /etc/ppp/pap-secrets and /etc/ppp/options.smd1 into /init.etc/ppp
You may have to do this "as root" in a terminal or console after typing "su" (hint; the "cp" command copies... "cp /etc/ppp/options.smd1 /init.etc/ppp" would work for the first file... same step for pap-secrets)

STEP 2 should allow those files to be created on boot. So once you have found the right settings, and managed to copy them into /init.etc/ppp you should be good to go from then on. Please reboot and confirm this for me since I am not on USCC and cannot test anything I suggest.

NOTE: /init.etc/ppp/pap-secrets and /init.etc/ppp/options.smd1 may not have the permissions necessary for you to be able to overwrite them. This is why you might have to go into a shell and type "su" and "chmod a+rw /init.etc/ppp/pap-secrets" and "chmod a+rw /init.etc/options.smd1" before you can copy over them, especially if you are using a GUI file explorer to copy, and not running everything as root (after "su") in the terminal shell.


GOOD LUCK! And don't forget to thank EVAL posts if you found them helpful


PS: /init.etc is "persistent" UNTIL YOU CHANGE YOUR ROOTFS. If you do, you will have to repeat these steps. So it is probably a good idea to keep a backup copy of your working pap-secrets and options.smd1 until this issue is fixed in the latest rootfs, so that in case it is not, you can overwrite the /init.etc files again easily. Hopefully a new rootfs will fix this problem altogether, but current reports are inconsistent that the RIL changes do.

Above is all from eval post

For people that know how to get around in teminal in linux this is what i used to exit the rootfs.img straight. After i edited it i put the micro sd card back in my phone and booted android and it worked perfect. This may help with anything else that you may need to edit or try to change
mount -o loop rootfs.img /mnt/android

its actually your MSID fyi.

MSID@USCC.net pw is MSID

[eval-]

Originally Posted by skuddy

its actually your MSID fyi.

MSID@USCC.net pw is MSID

Some people have used phone number, some people ESN, IMEI, some people other things. Are you saying MSID is set to these things and it's _always_ whatever the MSID is set to? (Be it your phone#, IMEI/ESN or whatever?) That would help USCC people know what to find out / ask for if it's always so consistent. Multiple people confirm this?

Like I said, I don't have USCC, I don't even have a TP2. Just a diam500 user on Sprint trying to help y'all out. Seems USCC is pretty varied in what they set the MSID, or alternately user/pass to for ppp auth.

[chrialex]

I have a RAPH800 and using the default APN settings work for me with the rootfs from the 21st. No user/pass in it. Using the all-in-one package from my sig with updated zimage and rootfs. Before that it wouldn't work.

[skamphax0r]

Originally Posted by chrialex

I have a RAPH800 and using the default APN settings work for me with the rootfs from the 21st. No user/pass in it. Using the all-in-one package from my sig with updated zimage and rootfs. Before that it wouldn't work.

Just did this and it worked great! also have the tethering working. Thanks a million!

[skuddy]

Originally Posted by eval-

Some people have used phone number, some people ESN, IMEI, some people other things. Are you saying MSID is set to these things and it's _always_ whatever the MSID is set to? (Be it your phone#, IMEI/ESN or whatever?) That would help USCC people know what to find out / ask for if it's always so consistent. Multiple people confirm this?

Like I said, I don't have USCC, I don't even have a TP2. Just a diam500 user on Sprint trying to help y'all out. Seems USCC is pretty varied in what they set the MSID, or alternately user/pass to for ppp auth.

i run 2 us cellular stores. and every time we have problems with internet access it is the MSID that gets you online. those are ALWAYS the server settings at USCC. if anyone needs their MSID call 611 and ask for it. they will be more than happy to give you the information. they will have to verify you and you will have to be authorized on the account however. if you need an unlock code for your phone PM your IMEI to me and i will pull it up for you. we have a little tool to look them up.


p.s. due to the way the network works, you have 2 phone numbers technically. your CTN (phone number) and your MSID (the number the network uses to track your phone number. due to porting into and out of different carriers these may be different or they may be the same if you have had your phone number for a long time or if no one has used the phone number ever. FYI