Problem with sprint ROMs - Droid Eris General

There seems to be an on going problem with sprint rom with regaurds to MMS I tried kaos legend build and now im on the aloysius rom. Recieving mms is fine sending is a problem, the messages says sent but the people never actually recieve them if anybody has some insight or fixes please post them thanks
MMSC says http://mms.sprintpcs.com does it need to be verizonwireless? the options are greyed out to change it
alson says mms proxy and port are not set

It will most likely be fixed in the next release. They are aware of the problem from what I understand and there is no known fix at the moment. Just use something more stable until the whole thing gets ironed out.

WalkingTaco said:
It will most likely be fixed in the next release. They are aware of the problem from what I understand and there is no known fix at the moment. Just use something more stable until the whole thing gets ironed out.
Click to expand...
Click to collapse
what he said seriously though, This is a tough one to crack or more likely I just am to stupid. Any help? dudes?

i will donate money to whoever figures this out... no joke.. and there isn't going to be a new rom out for awhile so everyone take part and find out!

Related

Android on the Cricket Android plan "Easy Web and MMS Fix"

This thread is for the talk about Android phones on the Cricket wireless Android plan. I have started this thread out of respect of "token419" to keep his thread Clean for his support and development.
If you signup or change your plan to Crickets Android plan you no longer need a WAP proxy. MMS well also work with only the need to setup your APNs. Your internet well be much faster in most cases 2x as fast.
It although can be a large pain in the A** to get cricket to make the appropriate changes to your account. There are people around the internet that can and well make account changes for a small fee. It can be done with out having to resort to that though and can take many I repeat many calls to cricket to get this done. some say all you have to do is request to be put on the "ADR Smartphone All In $55" plan. Others like my self also got there phone type listing changed form CPE "Customer Provided Equipment" to the "Kyocera M6000".
ONCE YOU GET YOUR SELF ON THE ANDROID PLAN:
Don't forget to remove your "autostart.sh" and your "u2nl". autostart.sh is in /data/opt and your u2nl is in /system/bin. Or you could simply remove autostart and reset your phone.
Please post your successes
I plan to upgrade to this plan. I have an incredible and my girlfriend has a hero. My incredible can access the internet and apps work but no mms. The hero can't access anything or send mms.
I got my data working from one of the zip files token419 uploaded will these apns work even though MMS isn't working at this point? Also not having anything work on the hero I am assuming something is wrong in the pst settings but I can not access epst from ##778# I can from ##data# but I don't think all f the needed settings are there. Any thoughts?
Thanks
MarcSummerhays said:
I plan to upgrade to this plan. I have an incredible and my girlfriend has a hero. My incredible can access the internet and apps work but no mms. The hero can't access anything or send mms.
I got my data working from one of the zip files token419 uploaded will these apns work even though MMS isn't working at this point? Also not having anything work on the hero I am assuming something is wrong in the pst settings but I can not access epst from ##778# I can from ##data# but I don't think all f the needed settings are there. Any thoughts?
Thanks
Click to expand...
Click to collapse
The APNs form Token's .zip Should work, they did for me.
On my eris some ROMs don't support diagnostic dialing. Ported froyo ROMs in my experience defiantly don't. It's more then likely the same for the Hero. your best bet is to flash to a rooted stock rom or some kind of plainJane rom then do your epst settings.
Also if you can dial ##diag you could change the appropriate pst settings from something like QPST.
whats the speed difference between the android plan and the unlimited 45 plan(which im on)?
My speeds are averaging about 500kb(download) and about 600-700(upload)...is there that much a difference? And you said MMS should now work even on AOSP roms? im on CM RC1 and was wondering this before i changed over my plan to the android plan.
t12icky0 said:
whats the speed difference between the android plan and the unlimited 45 plan(which im on)?
My speeds are averaging about 500kb(download) and about 600-700(upload)...is there that much a difference? And you said MMS should now work even on AOSP roms? im on CM RC1 and was wondering this before i changed over my plan to the android plan.
Click to expand...
Click to collapse
I average about 1150kb (Download) and about 650kb (Upload). I'm not 100% sure about MMS on a AOSP Rom. Please let me know if you find out.
Mr1337 said:
The APNs form Token's .zip Should work, they did for me.
On my eris some ROMs don't support diagnostic dialing. Ported froyo ROMs in my experience defiantly don't. It's more then likely the same for the Hero. your best bet is to flash to a rooted stock rom or some kind of plainJane rom then do your epst settings.
Also if you can dial ##diag you could change the appropriate pst settings from something like QPST.
Click to expand...
Click to collapse
Yeah it's weird I tried it on both 1.5 and 2.1 stock roms. I tried using qpst with no change maybe I missed something. I am used to flashing WM phones from the phones epst settings so qpst was new for me.
The hero is stuck saying "turning on...." for the mobile network could something else be causing this?
Thanks
ok so i think i got that all taken care of finally. so a fresh installed rom with the normal apn changes made are all thats needed now?
mms still leaves me with some questions specially when dealing with sprint roms and the evo since i know the aosp cm6 still puts sprint in the banner unless i change the eri.xml file and the stock messenger def has sprint things in it but we will figure that out soon enough
MarcSummerhays said:
Yeah it's weird I tried it on both 1.5 and 2.1 stock roms. I tried using qpst with no change maybe I missed something. I am used to flashing WM phones from the phones epst settings so qpst was new for me.
The hero is stuck saying "turning on...." for the mobile network could something else be causing this?
Thanks
Click to expand...
Click to collapse
Hmm... I don't know I'v never had that problem. In my experience flashing a WM and a android Phone are almost identical processes. Maybe on your hero you should flash over a factory rom with a factory radio return it to a completely stock phone and start over???
Mr1337 said:
Hmm... I don't know I'v never had that problem. In my experience flashing a WM and a android Phone are almost identical processes. Maybe on your hero you should flash over a factory rom with a factory radio return it to a completely stock phone and start over???
Click to expand...
Click to collapse
If I can't figure it out after upgrading her plan I will try that. Thanks for the help I will post my results for each phone after I fight with cricket to change my plan.
xTONEx said:
ok so i think i got that all taken care of finally. so a fresh installed rom with the normal apn changes made are all thats needed now?
mms still leaves me with some questions specially when dealing with sprint roms and the evo since i know the aosp cm6 still puts sprint in the banner unless i change the eri.xml file and the stock messenger def has sprint things in it but we will figure that out soon enough
Click to expand...
Click to collapse
Good to hear... That should take care of it. I don't think you even need to flash a ROM Just remove your "autostart.sh" and your "u2nl" or just uninstall autostart and you should be good to go
MarcSummerhays said:
If I can't figure it out after upgrading her plan I will try that. Thanks for the help I will post my results for each phone after I fight with cricket to change my plan.
Click to expand...
Click to collapse
Your Welcome. Good luck with Cricket... LOL
ok i will be changing my plan over to the Android plan with the Zio as my equipment. im lucky enough to have a friend that works at cricket..lol.
I will post the changes on speed and let everyone know if it works on the CM RC1 rom for the HERO. i iwll be doing this more then likely tomorrow.
t12icky0 said:
ok i will be changing my plan over to the Android plan with the Zio as my equipment. im lucky enough to have a friend that works at cricket..lol.
I will post the changes on speed and let everyone know if it works on the CM RC1 rom for the HERO. i iwll be doing this more then likely tomorrow.
Click to expand...
Click to collapse
A friend in the right place is always Nice to have . It well more then likely take up to a day to see the speed increase.
Mr1337 said:
A friend in the right place is always Nice to have . It well more then likely take up to a day to see the speed increase.
Click to expand...
Click to collapse
Agreed...btw when does the new ZIO come out? im looking forward to seeing what cricket did with there own android rom.
t12icky0 said:
Agreed...btw when does the new ZIO come out? im looking forward to seeing what cricket did with there own android rom.
Click to expand...
Click to collapse
its already out. sadly its a 1.6 device with plans of 2.1 update in the next few months
xTONEx said:
its already out. sadly its a 1.6 device with plans of 2.1 update in the next few months
Click to expand...
Click to collapse
oh that sucks...still it would be good to get that MMS.apk from cricket to see what they did to it. The structure of the ROM may also help the developers make a 2.1 rom or something..never know..lol.
xTONEx said:
its already out. sadly its a 1.6 device with plans of 2.1 update in the next few months
Click to expand...
Click to collapse
t12icky0 said:
oh that sucks...still it would be good to get that MMS.apk from cricket to see what they did to it. The structure of the ROM may also help the developers make a 2.1 rom or something..never know..lol.
Click to expand...
Click to collapse
Its already out and in the stores for sell??? Not where I'm at, here they keep saying between the 25th and the first of next month. The web site lets you pre-order but there not shipping tell the 26th and thats even just a estimation.
Ya.. It would be nice to see something good come from the Zio ROM.
Mr1337 said:
Its already out and in the stores for sell??? Not where I'm at, here they keep saying between the 25th and the first of next month. The web site lets you pre-order but there not shipping tell the 26th and thats even just a estimation.
Click to expand...
Click to collapse
theyve had it for sale here since friday
xTONEx said:
theyve had it for sale here since friday
Click to expand...
Click to collapse
Very Nice, what market are you in???
Mr1337 said:
Very Nice, what market are you in???
Click to expand...
Click to collapse
Buffalo NY (one of their test markets)

Dropped Calls on Froyo Roms

I have been discouraged from the Froyo ROMs for a while due to the problem with calls being dropped but then suddenly they aren't dropped. I really like the Froyo ROMs though so I decided to try it again and the first day I experienced it yet again on CELB 3.6. It only happened a couple of times then 3.7 was released and I flashed that and it happened again on the first call LOL. I then started looking through things in the settings and under the mobile data setting I turned on National Data Roaming, since then I have been on several calls ranging from 20 minutes to an hour and have yet to experience this problem since turning data roaming on, some of these calls were in areas that I know for certain I had the dropped and reconnected calls happen before. Maybe some others may want to try this out and see if it helps you as well. Hope this helps some people that have experienced this as well.
Has anyone else tried this yet? And if so, has it made any difference for you as well?
happens to me all the time. kaos froyo, tazz froyo, celb froyo, nonsensikal froyo. Only at my house tho. i have 3 bars there. not sure whats going on there but i have learned to live with it. Wont be long till we are on 2.3 anyway. deal with it for a month. by the new year kaos should have a completley functional 2.3 rom. maybe without camera, but still fully functional.
I've been messing around with the national data roaming for about a week now. When I have national data roaming enabled it doesn't happen, if I turn it of it does. Try enabling it and see if it makes a difference for you too. It's located under settings>wireless & networks>mobile networks
will enable it and see if it happens tonight.
Same here, after enabling it I have had no stopped call issues. Its been about a week, so far so good
Good information, I think I'm gonna try it, but first does this affect my billing at all? I'm on my parents plan and don't want to give them a heart attack if I incur extra charges
Scott586 said:
Good information, I think I'm gonna try it, but first does this affect my billing at all? I'm on my parents plan and don't want to give them a heart attack if I incur extra charges
Click to expand...
Click to collapse
It shouldn't but that would depend on what your plan is. If you have a nationwide plan with unlimited data and no roaming charges then it won't. I'd suggest checking on your plan first. Just a thought though lol.
CondemnedSoul said:
It shouldn't but that would depend on what your plan is. If you have a nationwide plan with unlimited data and no roaming charges then it won't. I'd suggest checking on your plan first. Just a thought though lol.
Click to expand...
Click to collapse
I also have this problem happen on non-Verizon based ROMs such as RCMix.
The call says it's dropped, but the person on the other end can hear everything that's going on.
Then the phone rings you back, but in reality, they were hearing everything going on around you in the meantime.
I almost lost my girlfriend because of it. Immediately flashed away from said ROM. Had the same problem with Froyo ROMs.
May switch to a CM ROM now, if this is a serious fix. Thanks very much for this.
I was hoping this would be a fix - I upgraded to CELB 3.9 a couple of days ago, and turned on National Data Roaming.
Tonight I had the same behavior - temporary call drop and reconnect along with the same symptoms that usually accompanies it (speakerphone mode toggles off, phone vibrated, yada yada).
Confirmed through examination of the (uncompressed) SYSTEM_TOMBSTONE file in /data/system/dropbox/ that yes, the usual cause is present: segfault crash of the "rild" process.
Rats! I was hoping this might provide a fix... but apparently not for me.
bftb0
bftb0 said:
I was hoping this would be a fix - I upgraded to CELB 3.9 a couple of days ago, and turned on National Data Roaming.
Tonight I had the same behavior - temporary call drop and reconnect along with the same symptoms that usually accompanies it (speakerphone mode toggles off, phone vibrated, yada yada).
Confirmed through examination of the (uncompressed) SYSTEM_TOMBSTONE file in /data/system/dropbox/ that yes, the usual cause is present: segfault crash of the "rild" process.
Rats! I was hoping this might provide a fix... but apparently not for me.
bftb0
Click to expand...
Click to collapse
Sorry ut didn't work for you.... so far now im at 3 weeks without it happening to me
I have still had this temporary dropped call problem occur just as frequently on CELBFroyo 3.6 with this "fix". And most of the time I'm in my apartment on the phone for hours when it happens, and it sometimes happens more than once during these extended phone calls.
Just as has been described before: the phone looks and acts like the call was dropped, I can hear nothing but the other person can hear everything, and then after several seconds everything is back to normal.
Oh well. Thanks for the suggestion, though.
Very interesting to hear others have been having this problem. I had thought it was due to my bluetooth earphone, because it used to happen to my wife on her old earphone with a standard cell phone. However, last night I lost my earphone and the same problem occurred while on speakerphone. Although annoying, most of the time I just deal with it. I just installed radio version 2.42.01.04.27 hoping it might help. Various versions of CELBFroyo (currently using 3.9) have done it. I will let you all know if this helps and keep checking back on this string to see if anyone else finds a fix.
farmdoc said:
Very interesting to hear others have been having this problem. I had thought it was due to my bluetooth earphone, because it used to happen to my wife on her old earphone with a standard cell phone. However, last night I lost my earphone and the same problem occurred while on speakerphone. Although annoying, most of the time I just deal with it. I just installed radio version 2.42.01.04.27 hoping it might help. Various versions of CELBFroyo (currently using 3.9) have done it. I will let you all know if this helps and keep checking back on this string to see if anyone else finds a fix.
Click to expand...
Click to collapse
Seems like its touch and go now. Works for some but not for others. I haven't had it happen to me in 3 weeks now but this hasn't worked for some others where some it has. Im using the new sprint radio now, I don't know if maybe it has anything to do with what radio you have too? I just flashed this radio about a week and a half ago though. Before that I was on the older verizon radio... not the one from july ota though... the previous one.
sent from the depths of hell
CondemnedSoul said:
Seems like its touch and go now. Works for some but not for others. I haven't had it happen to me in 3 weeks now but this hasn't worked for some others where some it has. Im using the new sprint radio now, I don't know if maybe it has anything to do with what radio you have too? I just flashed this radio about a week and a half ago though. Before that I was on the older verizon radio... not the one from july ota though... the previous one.
sent from the depths of hell
Click to expand...
Click to collapse
If I recall correctly, it has been seen on multiple radios. ( Have you seen this thread? )
bftb0
bftb0 said:
If I recall correctly, it has been seen on multiple radios. ( Have you seen this thread? )
bftb0
Click to expand...
Click to collapse
Thanks for the leads to the other threads. I had not seen them.
I have not had a chance to test with the current radio installed (2.42.01.04.27), but plan to tonight. Is there a newer radio for the Eris? Looking at the version numbers of some I have seen referenced would make me believe that there are newer ones. Where do you download these?
farmdoc said:
Thanks for the leads to the other threads. I had not seen them.
I have not had a chance to test with the current radio installed (2.42.01.04.27), but plan to tonight. Is there a newer radio for the Eris? Looking at the version numbers of some I have seen referenced would make me believe that there are newer ones. Where do you download these?
Click to expand...
Click to collapse
AFAIK, this is the most recent radio and is currently what I'm using:
http://forum.xda-developers.com/showthread.php?t=853868
roirraW "edor" ehT said:
AFAIK, this is the most recent radio and is currently what I'm using:
http://forum.xda-developers.com/showthread.php?t=853868
Click to expand...
Click to collapse
Thanks! BTW what is AFAIK?
farmdoc said:
Thanks! BTW what is AFAIK?
Click to expand...
Click to collapse
You're welcome! AFAIK = As Far As I Know

Cyanogenmod and calling 911

I heard that Cyanogenmod 7 for the Samsung Vibrant isn't able to call emergency numbers. Does anyone know if this is true? I don't want to take the risk if it is.
It is true.
I have had trouble with calling 911 and I use MIUI revamped. Luckily, I've had my wife's phone handy.
Sent from my T959 using xda premium
Roman fixed it. Not sure if OMFGB has it but his last Trigger does:
http://forum.xda-developers.com/showthread.php?t=1156123
Moped_Ryder said:
Roman fixed it. Not sure if OMFGB has it but his last Trigger does:
http://forum.xda-developers.com/showthread.php?t=1156123
Click to expand...
Click to collapse
CM team refused to put the fix in as it wasn't pretty enough for them. Seriously - it's a "hack" and so they won't do it. Lawsuit territory there - a *known* problem that could *cost lives* with a *fix available* and they refuse to do it because they don't want to add anything device specific to the source tree.
They should put a disclaimer : By using this rom you risk death.
Sent from my Nexus S using XDA App
From what I know, it varies from one area to another whether or not 911 works. I simply added my local police dept, fire dept and hospital to contacts. I use Go Dialer, which is T-9, so calling them is just three taps away.
This effectively fixes the 911 issue for me, and simply put CM7 > all others.
Oxirane said:
From what I know, it varies from one area to another whether or not 911 works. I simply added my local police dept, fire dept and hospital to contacts. I use Go Dialer, which is T-9, so calling them is just three taps away.
This effectively fixes the 911 issue for me, and simply put CM7 > all others.
Click to expand...
Click to collapse
That's fan boy territory there. It's neat and all but A Long ways away from being as stable as our crop of I9000 ginger ports. The problem with cm7 is they are taking a one size fits all approach. You are ABSOLUTELY sure to lose something along the way. And let's be completely honest here most of the vibrant users are less than 18 and more than likely not to dial 911 but to run away. If it's important to you flash something else. You will only be missing out on a laundry list of potential problems and the theme chooser. I do say this on miui. From my experience miui is far and away a much better beast than cm7 and I have done as the guy i've quoted and have my local emergency numbers saved. Sucks to be responsible but you got to do what you got to do.
Sent from my T959 using xda premium
JediDru said:
That's fan boy territory there. It's neat and all but A Long ways away from being as stable as our crop of I9000 ginger ports. The problem with cm7 is they are taking a one size fits all approach. You are ABSOLUTELY sure to lose something along the way. And let's be completely honest here most of the vibrant users are less than 18 and more than likely not to dial 911 but to run away. If it's important to you flash something else. You will only be missing out on a laundry list of potential problems and the theme chooser. I do say this on miui. From my experience miui is far and away a much better beast than cm7 and I have done as the guy i've quoted and have my local emergency numbers saved. Sucks to be responsible but you got to do what you got to do.
Sent from my T959 using xda premium
Click to expand...
Click to collapse
MiUi can't dial 911 either?
I've been meaning to schedule a test but I'm a long ways away from home atm.
Sent from my T959 using xda premium
MIUI ReVaMPeD has the bug, so I imagine MIUI does too.
MIUI is buit from CM7, they both blow everything else out of the water performance-wise (due to different filesystems and whatnot), but they both have the same bugs (give or take a few) and from there I really think it boils down to personal preference.
The Samsung based GB roms still have the reboot issues in lower %s, and from my experience have been pretty awfully laggy. If those have been cleared up, I'll be happy to give them another go, but as of now I'm happy with CM7 and I have my emergency #s stored... I only suggest anyone on MIUI/CM7 (other than Trigger) do the same as a precaution.
And for the record, I am a college student- I'm 19, so just over 18, and while I've never needed to call police, I needed to call an ambulance once when I got hit by a car, but unfortunately I landed on and broke my old flip phone (this was a few years back) in that accident. Thankfully I only had really minor injuries. I'd certainly suggest having those numbers saved.
Sucks to be responsible but you got to do what you got to do.
ARE YOU GUYS SURE 911 DOESN'T WORK????
Ok so I installed the newly released stable CM. Obviously I'm not going to call 911 and test, but I tried a different number 311 and sure enough it routed and connected me correctly to the City of Los Angeles 311 Information System. This makes me think 911 should work too.
If 311 was routed correctly to the City of Los Angeles 311 Information System, why wouldn't 911 be correctly routed and connected?
There was an explanation a while ago in the Nightly thread about how 911 is handled... I understood it worked for some people, not for others. I'd say be responsible and add those contacts, but hey, you're welcome to try calling 911
Should I be in a situation where 911 is necessary, I'll give it a go. However, I'm not deleting those emergency numbers from my contacts just in case.
911 on Cm7 and MiUI
Ok so do we finally know if 911 works on CM-7 and MiUi or not?

[Info] Radio problems - FIX

.... will not be anything that is resolved here. It is a problem with the firmware for ICS.
I was talking to somebody at sprint today while I was there and showing them my device and asking if there will be any issues caused by having a virgin mobile ROM on the device. The lady explained to me that they are exactly the same, get the same reception, same update packages, and work on the same network, etc., etc.... All of this was known to me to some extent, but wanted to hear it from somebody at the company... and told me that the only problem they are having is with ICS in general is that there have been data/radio issues with the Galaxy Nexus line as well ever since it released on their network a few weeks ago.
Furthermore, she explained that this was a known bug/issue and that she knew for a fact that an update would be coming with a fix and that it was being worked on right now.
The reason I wanted to share this was because I have seen a lot of misinformation floating around about 1.) having a virgin mobile ROM on your device and 2.) virgin mobile ROM causing data issues - which is not the cause of the issue as I mentioned just now.
Just want you all to be aware of this in case you were thinking having this software and firmware on your device would cause any issues with your billing, your contract, etc. Simply put - it will not. Virgin mobile is owned by sprint, they run on the same towers, same network, and info of accounts is stored in the same place. You could literally walk into a sprint store to pay your bill for your virgin mobile account.
All is well. All is safe. An update will come to fix the data issues, keep your eyes peeled for it folks. We are not given source code for radios, etc., so unfortunately that needs to be fixed on the carrier/manufacturer end - and as I said, it will be fixed and they are working on it. Sit tight.
Hope this cleared up any misconception floating around.
So, you don't really know how to fix it then? Forgive me for being a little confused, but your title is slightly misleading.
Oh man, you have no idea how much I was freaking out about the billing. Thanks man. (Y)
xHausx said:
So, you're don't really know how to fix it then? Forgive me for being a little confused, but you say there is a problem with the firmware and then say that there is nothing wrong with it?
Click to expand...
Click to collapse
yeah, i can see the confusion there....
re-worded, i would say it appeared to me that people thought there were data issues because of being on a virgin mobile ROM. The point I am trying to express is that the problem is the firmware, not because the ROM is for the virgin mobile 3D - if this same firmware was released for "official sprint RUU" where your banner said "sprint" they would still be having the same issues. Ex.: the lady at sprint said the galaxy nexus was having the same issue.
If that makes sense.
If not, not sure how else I can explain it.
It seemed people were crediting the problem to the fact that there device is attached to virgin mobile - this is not the case.
EDIT*** lol, nice ninja edit haus - you gotta be quicker than that roffle
xHausx said:
So, you don't really know how to fix it then? Forgive me for being a little confused, but your title is slightly misleading.
Click to expand...
Click to collapse
I thought it was the ROM side that is giving the PRL/Data roaming and all the other network problems. Not the firmware. I say this because people have posted that they flashed the firmware, flashed the VM ICS ROM. Then went back to a GB ROM (MeanROM, MIUI, etc) and they had everything working, even though they were on the leaked firmware. But if you flashed that firmware, chad and another dev found a fix, they are going to release it sometime soon.
thread: http://forum.xda-developers.com/showthread.php?t=1638225&page=30
Punk9 said:
I thought it was the ROM side that is giving the PRL/Data roaming and all the other network problems. Not the firmware. I say this because people have posted that they flashed the firmware, flashed the VM ICS ROM. Then went back to a GB ROM (MeanROM, MIUI, etc) and they had everything working, even though they were on the leaked firmware. But if you flashed that firmware, chad and another dev found a fix, they are going to release it sometime soon.
thread: http://forum.xda-developers.com/showthread.php?t=1638225&page=30
Click to expand...
Click to collapse
after half a day of having flashing back they determined the problem to be gone??
......
the issues being caused by the firmware are not constant, and apparently are rather random from what I have read. a perfect example is my own device... no issues with new firmware until today (day 3) of having it, even tho many people reported issues after just a couple of hours.
I'll talk with chad and see what he is cooking up... I havent talked to him a whole lot this weekend.
sent from ICEvo
I've been saying that the roaming problem (if it truly exists outside of people's self affirming observations) only exists on this ROM due to ICS and the lack of roaming options on the rom itself. The radios do nothing to mess up roaming. This is all due to it being a TEST rom that we flashed. It's absurd to think that there is a perfectly functional rom sitting around with no bugs if the only leak we can get is a Virgin Mobile version. We have a beta rom and beta radios, and we should realize that's what we signed up for when we flashed it in the first place.
retnuh730 said:
I've been saying that the roaming problem (if it truly exists outside of people's self affirming observations) only exists on this ROM due to ICS and the lack of roaming options on the rom itself. The radios do nothing to mess up roaming. This is all due to it being a TEST rom that we flashed. It's absurd to think that there is a perfectly functional rom sitting around with no bugs if the only leak we can get is a Virgin Mobile version. We have a beta rom and beta radios, and we should realize that's what we signed up for when we flashed it in the first place.
Click to expand...
Click to collapse
this is true... but again, what is your explanation of the galaxy nexus having the same issue, and the fact that a sprint rep was entirely aware of the issue and that is was being worked on and would come in an update?
and surprise, but any new technology is "beta" ..... whether it is an official release or not. it is the price you pay for cutting edge technology.
sent from ICEvo
So in essence this means that the firmware in the new radio update, which is necessary/part of ics to run on phones is the heart of the data, sms, etc. issues people are having?
There are some differences between how the ROM interacts with the both radios but so far it looks like everything can still be made to work.
If you're having issues with roaming try opening up the build.prop and change 'persist.radio.voice.dom.roam=0' to 'persist.radio.voice.dom.roam=1', and then use setprop to reset it. I haven't been able to test it yet but I'm fairly certain that will bring back roaming.
raptoro07 said:
So in essence this means that the firmware in the new radio update, which is necessary/part of ics to run on phones is the heart of the data, sms, etc. issues people are having?
Click to expand...
Click to collapse
from what the lady explained to me, yes it is... intermittent data loss is a bug within the new firmware for ICS
my point here is that it has nothing to do with your ROM being intended for a virgin mobile 3D. it is because of a bug within the firmware for the radios.
as i said, sprint rep explained this to me, and seemed very confident in the way she explained it - confirming it as a known issue, and also knowing that it would be fixed soon because it was being worked on and said it would be serviced as a firmware update.
sent from ICEvo
You think a sprint tech in the store is an authority !!
For one thing, many may not care, you lose VPN capabilities. Which I need and want and has nothing to do with ICS. Flashed back to GingerBread an it's still gone.
You may also lose the ability to properly update the PRI when new ones come out with official ICS.
It is not just a banner issue.
I'm not in a roaming area to confirm roaming issues but I believe folks when they say they can no longer roam on th 3G. I never touched my default roaming settings and it always worked fine. You may be right that roaming is only ICS issue. But it smells like it's way more than that by folks reports. And quite believable given the phone half believes it's on Virgin Mobile.
It is the PRI which manages routing that is not correct. And different folks will get different issues depending on their location.
I don't think chad and friends would be working so hard to fix it if it was such minor issue and I trust them more than some sprint sales person.
Like was stated above. There are two kinds of people. Those with issues and those with no issues, YET !!
And please FIX the broken subject.
This all reeks of a panic due to us not understanding the new tech in the build we have. These issues may be a side effect of the ICS ROM or could just be issues with the way ICS interacts with the radios. The only information we have is hearsay, and people tend to overestimate effects of things when they don't know what they're looking for.
We get what we deserve for flashing beta radios and a beta rom, tbh. We accepted any possible problems by flashing these and we have nobody to blame but ourselves for not researching first.
"issues" is a vague word. whats to say a person's issue is due to ICS, the radios, or anything else in particular?
The new radios made me gain 20 pounds. There's no information showing that the radios did or didn't cause this. Yet here we are proverbially attributing all these issues to one thing or the other, when in reality WE DO NOT KNOW what is causing these problems.
retnuh730 said:
This all reeks of a panic due to us not understanding the new tech in the build we have. These issues may be a side effect of the ICS ROM or could just be issues with the way ICS interacts with the radios. The only information we have is hearsay, and people tend to overestimate effects of things when they don't know what they're looking for.
We get what we deserve for flashing beta radios and a beta rom, tbh. We accepted any possible problems by flashing these and we have nobody to blame but ourselves for not researching first.
Click to expand...
Click to collapse
People here are not stupid. Most do backups before they try something.
I restored a backup and lost capabilities I had.
I reflashed every every sprint RUU, Reflash Hboot 1.40, restored back up and things are not the same.
If you flashed that freeza patch your phone has it's feet in both Sprint and Virgin Mobile and it's not good.
Yes, we know we screwed up. And some of us would like it fixed before we get more surprises of what does not work correctly.
xHausx said:
There are some differences between how the ROM interacts with the both radios but so far it looks like everything can still be made to work.
If you're having issues with roaming try opening up the build.prop and change 'persist.radio.voice.dom.roam=0' to 'persist.radio.voice.dom.roam=1', and then use setprop to reset it. I haven't been able to test it yet but I'm fairly certain that will bring back roaming.
Click to expand...
Click to collapse
What is the "setprop" an ADB command? Do you have to use it. I edited the build.prop how you said reset the phone and nothing changed. I am roaming and cannot connect to data. My phone's data works fine when in a coverage area, but obviously not when roaming. I never did any kind of firmware update. Hope that helps.
retnuh730 said:
I've been saying that the roaming problem (if it truly exists outside of people's self affirming observations) only exists on this ROM due to ICS and the lack of roaming options on the rom itself. The radios do nothing to mess up roaming. This is all due to it being a TEST rom that we flashed. It's absurd to think that there is a perfectly functional rom sitting around with no bugs if the only leak we can get is a Virgin Mobile version. We have a beta rom and beta radios, and we should realize that's what we signed up for when we flashed it in the first place.
Click to expand...
Click to collapse
This leak isn't a beta, its release keys...
sent from my nocturnaled ics 3vo
powduh09 said:
This leak isn't a beta, its release keys...
sent from my nocturnaled ics 3vo
Click to expand...
Click to collapse
+1 this is a direct pull of the ruu for the upcoming vm evo 3d
Sent from my PG86100 using Tapatalk 2
to anyone that hasn't seen it already, if you flashed this firmware, chad is working on a fix over that this thread
http://forum.xda-developers.com/showthread.php?t=1638225&page=41
xHausx said:
There are some differences between how the ROM interacts with the both radios but so far it looks like everything can still be made to work.
If you're having issues with roaming try opening up the build.prop and change 'persist.radio.voice.dom.roam=0' to 'persist.radio.voice.dom.roam=1', and then use setprop to reset it. I haven't been able to test it yet but I'm fairly certain that will bring back roaming.
Click to expand...
Click to collapse
successfully implemented this. Hope this solves the no roaming issue. Thanks
Visionikz03 said:
successfully implemented this. Hope this solves the no roaming issue. Thanks
Click to expand...
Click to collapse
How were you able to do this? I'm trying to research a little on setprop.....but still not fully understanding it
Sent from my PG86100 using xda premium

GSM/CDMA... Not even sure what to put on the subject line.

So I just wanted to share something really weird and ask if anyone has ever seen anything like it before.
I recently flashed the last AOKP update, and my phone was running phenomenally. I went out last night and my battery died because I forgot to charge it... No biggie. Got home, turned it on, no signal. Odd, since I have pretty decent service in the area. After doing the usual troubleshooting of cycling airplane mode, I tried pulling the battery and sim. That also didn't work. I went into settings to check my APNs, and instead of the usual menu, I saw only 4 options. The option to select APNs wasn't even there. The last one said "Set CDMA..." something. I forget the rest. Wish I had remembered to take a screenshot. In "About Phone", my baseband was blank. Tried reflashing back to LC5 radio. Still nothing. Did a full wipe and reflash of the ROM, and that got me back in business. Right now, all is well. I was just unaware that a phone could magically switch over to CDMA, even if there is no CDMA radio in an i777.
Any thoughts on the cause?
EDIT:
ROM: Task's AOKP 4.14
Kernel: Stock
Radio: UCLL6 when issue started. Now on UCPLC5
Not an issue that's related to the rom, as far as I know. Unless others have reported this issue and I've missed it. If you do a full wipe and re flash as you've done and don't install any programs for a good 24 to 48 hours, and nothing of the sort happens again, odds are it has something to do with an app you installed. Unless your service provider maybe was experiencing problems at the time.
Phalanx7621 said:
Not an issue that's related to the rom, as far as I know. Unless others have reported this issue and I've missed it. If you do a full wipe and re flash as you've done and don't install any programs for a good 24 to 48 hours, and nothing of the sort happens again, odds are it has something to do with an app you installed. Unless your service provider maybe was experiencing problems at the time.
Click to expand...
Click to collapse
No, definitely an anomaly. Not something that anyone else has reported. I called AT&T to verify if there were any issues in the area or with my account, and everything checked out. I haven't downloaded a new application in months. I restored from TiBu right after reflashing and everything is still good. Like I said, not trying to report it or anything; just looking for thoughts.
You meant APN and baseband NEVER come to live? If that's the case, then I haven't heard or read any report about it.
If it's up and running like normal AFTER 5 minutes, then it's has been reported many many times last week.
votinh said:
You meant APN and baseband NEVER come to live? If that's the case, then I haven't heard or read any report about it.
If it's up and running like normal AFTER 5 minutes, then it's has been reported many many times last week.
Click to expand...
Click to collapse
No... More like APN and baseband were completely fine for almost a week, and then it suddenly stopped working while I was asleep.
nycmalu said:
No... More like APN and baseband were completely fine for almost a week, and then it suddenly stopped working while I was asleep.
Click to expand...
Click to collapse
Well, that's new to me.
Reflash with clean installtion?
I know none of us want to factory reset but some cases, we have to.
This is odd but in no way, shape, or form can a i777 transform its hardware to support CDMA
Sent from my Galaxy Nexus
Pirateghost said:
This is odd but in no way, shape, or form can a i777 transform its hardware to support CDMA
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Yes I do agree. ....this is so strange that im putting my phone under 24/7 surveillance. No way I wanna see my phone transformed to CDMA
Hehe....:what:
Sent from SGH-S959G
Pirateghost said:
This is odd but in no way, shape, or form can a i777 transform its hardware to support CDMA
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
This is what I thought. I have a feeling that since AOKP is based of CM, there is code built in to support both CDMA and GSM. Somehow, the software glitched, and made the switch.
nycmalu said:
This is what I thought. I have a feeling that since AOKP is based of CM, there is code built in to support both CDMA and GSM. Somehow, the software glitched, and made the switch.
Click to expand...
Click to collapse
I did confirm your theory. ...playing around to prduce same problem and yes ...very true. ....will play with logcat on next time to save and shoot to CM Team:screwy:
Sent from SGH-S959G
samprocat said:
I did confirm your theory. ...playing around to prduce same problem and yes ...very true. ....will play with logcat on next time to save and shoot to CM Team:screwy:
Sent from SGH-S959G
Click to expand...
Click to collapse
I don't know how you did it, but I'm glad you were able to reproduce the issue. At least I know I'm not crazy.
nycmalu said:
I don't know how you did it, but I'm glad you were able to reproduce the issue. At least I know I'm not crazy.
Click to expand...
Click to collapse
Yes this prop is built in rom just can't find the way to trigger this with log cat on......just need some more playing till this occurre again
Sent from SGH-S959G

Categories

Resources