Quote:
Originally Posted by supasanch24
This may be a dumb question, but does your phone need to be unlocked to run this?
|
Nope. Runs fine on a locked Sprint rom. That's what I'm using.
Quote:
Originally Posted by supasanch24
I tried installing it the "easy way" from post 1, but it seems to be stuck on some load screen. Does it take a long time to boot up?
|
First guess -- messed up SD partitioning. What's the last few lines in the console before it hangs?
Alternately, if it's stuck on the shimmery nexus one animation (the 4 color x) then it's probably something to do with the data partition. Trash data.img and try again.
Quote:
Originally Posted by hamagc
ok guys i've been playing with different apn settings and what not trying to get mms to receive and here is what i have.
i moved all the apn settings regarding mms out of the internet apn. moved them all to a second apn i setup with mms as apn type.
i can still send but not receive.
but i noticed when i replyed to an mms, about the time i would receive the mms, my 3g icon at top becomes an E icon for a split second and then back to a 3g. i believe this is the mms trying to come in. i assume e is for error? like there is an error retreving the message? maybe this can help someone figure out this problem. in the meantime, i will keep trying different things to see if i can get a different outcome.
|
Good to know the Sprint APN can be separate.
The E stands for EDGE. the RIL (I assume this is a RIL issue) pretends that the cdma network is a gsm network, so it uses GSM terminology... EDGE and 3G, instead of 1x and EvDO.
The upshot there is that the MMS is coming in to the RIL, getting mangled by it, and confusing the RIL into either dropping into 1x service for a second, or simply reporting that it's dropping into 1x service for a moment.
That's both good and bad news. Good news -- it gives a lot more credence to the guess that the problem is the RIL. Bad news -- now someone has to fix it. Which probably involves getting an AT Debug Log from WinMo for receiving an MMS, figure out how that's getting misread by the RIL, and fix it up to read it correctly. I don't think I'm qualified to do that, unless it happens to be an easy fix.
Quote:
Originally Posted by hamagc
also i noticed under the apns-conf.xml file there are no sprint or verizon specific settings (verizon seems to be having the same issue as us. can send but not receive). only generic cdma. maybe has something to do with it. it looks like every other carrier in the world is in there but no sprint and no verizon.
|
These frankenstein's monster CDMA android builds are to blame for that. They're built on all the GSM carriers stuff, but with a few bits tweaked to work on CDMA. The apns-conf.xml file is pulled from a nexus one, with some pieces added from other gsm phones. I added the one line for CDMA generic because every CDMA phone reports 310/995 as its MCC/MNC. As near as I can tell, CDMA doesn't actually use MCC/MNC, so this is just something that got hacked in to emulate it.
Anyway, apns-conf.xml just holds the defaults. When you add your own APN, it's the same thing as if it had read it from apns-conf. So whatever's missing there, it shouldn't do any harm.
I am curious how real CDMA android phones do it... do they even have an APN section in the settings?