I had downloaded 1 of Mik's roms a while back (version 2.0.1 to be exact) and saw this 3.0 as his latest work on his website so figured I would give it a try. I see that he is aware that there are still remnants of this ROM that was made for Sprint EVO devices apparently, but I'm having a unique issue.
Whenever I attempt to make a call it alerts me that I am in roaming mode (which I double checked and i have it checked OFF so my DINC will dont roam) and if I would like to continue anyway. When my lock screen comes up it says "Verizon Network" on top and I am receiving and able to send text messages just fine. I have not seen anyone else having this issue in the forums and the last thing I want is to receive a higher bill from Verizon at the end of the month because of a new ROM. Also, the alert is simply annoying.
Please help.
manthis22 said:
I had downloaded 1 of Mik's roms a while back (version 2.0.1 to be exact) and saw this 3.0 as his latest work on his website so figured I would give it a try. I see that he is aware that there are still remnants of this ROM that was made for Sprint EVO devices apparently, but I'm having a unique issue.
Whenever I attempt to make a call it alerts me that I am in roaming mode (which I double checked and i have it checked OFF so my DINC will dont roam) and if I would like to continue anyway. When my lock screen comes up it says "Verizon Network" on top and I am receiving and able to send text messages just fine. I have not seen anyone else having this issue in the forums and the last thing I want is to receive a higher bill from Verizon at the end of the month because of a new ROM. Also, the alert is simply annoying.
Please help.
Click to expand...
Click to collapse
Sounds like you need to update your prl. You do this by dialing *228 and selecting option 2.
I forgot to mention that that's the first thing I did. I even accepted the alert and went with it anyway knowing it wouldn't take but a minute. It programmed the phone successfully.
Still occuring obviously.
manthis22 said:
I forgot to mention that that's the first thing I did. I even accepted the alert and went with it anyway knowing it wouldn't take but a minute. It programmed the phone successfully.
Still occuring obviously.
Click to expand...
Click to collapse
Hmm not sure then. I know sprint ported roms tend to be touchy on the verizon network. I gave up on using them after synergy rom awile back, because my data connection would constantly break, requiring a compleete ruu and factory reset to get it working again. Just flashing a new rom wouldnt fix it.
Have you tried flashing the .0808 evo radio. I know it works on the incredible and mabey since its a sprint ported rom the evo radio would work better, or mabey not just a sugestion.
Its in call settings or wireless and networks. It's called roam guard. Unchecked it and you'll be fine.
-My life is a shooting range, people never change-
watt9493 said:
Its in call settings or wireless and networks. It's called roam guard. Unchecked it and you'll be fine.
-My life is a shooting range, people never change-
Click to expand...
Click to collapse
I actually had to turn ON data roaming to check off Data Roam Guard. It didn't work. But out of desperation I checked OFF Call Guard and that fixed it. Maybe that's the option that you meant. Either way, the alert has stopped and my outgoing calls no longer give me that message while I have roaming OFF.
Thanks for the replies.
cmlusco said:
Sounds like you need to update your prl. You do this by dialing *228 and selecting option 2.
Click to expand...
Click to collapse
Doing this on sprint ROMs have a tendency to break data. I don't recommend doing this. Also other development don't recommend it either. If you start having data issues, you may need to go back to stock, redo *228, the reflash what you want. I'm currently running my port of MikG 3.0 and have not had the warning. I did what you have done and its fine. I've made sure that the NETWORK thinks we are in fact Verizon, but the ROM somehow thinks we are Sprint.
Sent from my HTC Droid Incredible
manthis22 said:
I actually had to turn ON data roaming to check off Data Roam Guard. It didn't work. But out of desperation I checked OFF Call Guard and that fixed it. Maybe that's the option that you meant. Either way, the alert has stopped and my outgoing calls no longer give me that message while I have roaming OFF.
Thanks for the replies.
Click to expand...
Click to collapse
Yes. Sorry. That's what I meant, my girlfriend had more attention at the time then my phone. We all know where that goes.
-My life is a shooting range, people never change-
Related
Hey all,
I got the July 27 leaked Froyo and went ahead and rooted to 2.2.
I have noticed a pretty serious buggy issue regarding the phone not detecting a 3G network so when I'm away from my wireless router, it only shows bars, no 1X or 3G.
I have two options at this point, one of which has done me no good. Perhaps someone can help me.
Option 1: Downgrade back to Android 2.1. (More on this later)
Option 2: Try and find a way to keep this version and get back on 3G.
Lemme explain: I tried placing the PB31IMG.zip on the SD card and going through recovery to return the phone to stock. Each time I attempted this, it told me the version was old and it failed. Is there a workaround on this or do I need to find a different stock ROM?
I used unrEVOked to root the phone and have not been trying to do any frivolous additions or subtractions. I just wanna be back on my 3G. Any and all help would be HIGHLY appreciated.
Thanks!
Did you try *228 and update your PRL?
Yes. It did not help.
Always have 3G coverage where I'm at too. So more than likely phone is issue unless a tower around here is down (which I highly doubt).
Toggle Airplane Mode on, then off.
JC
Sadly, toggling airplane mode has done nothing to help either.
Upgrade to the 8/1 version...see if that helps.
JC
Try shutting the phone off, then powering back on. Or possibly that combined with an airplane mode toggle. Also make sure your mobile network is on in the settings for wireless networks. This problem was common with the first leak. I have not had it happen since switching to the second leak of 2.2.
Considering the missing apps and media in the 8/1 Leak would it be ok to do Sky Raider or should I just try the 8/1 Leak done by aiccucs?
ContraMan said:
Considering the missing apps and media in the 8/1 Leak would it be ok to do Sky Raider or should I just try the 8/1 Leak done by aiccucs?
Click to expand...
Click to collapse
I believe mrozzeh also gave a link to the full version of the 8/1 leak, if you are concerned about missing apps/media...
Doing that update has not helped me.
I guess I'll have to go down to 2.1 again. However, as I said, it won't load the PB31IMG.zip. It says the file is old. Any ideas?
Stupid question....you did upgrade the radio right?
Yes. Radio is the 2.x baseband.
I would be VERY finicky to update that again as I do NOT want to brick my phone.
Ok, it seems I have found a bit of the issue that is causing it. My phone number and IMSI are not detected as my current phone number. Is there a way to program this or is it an issue where I'll have to have it reprogrammed by the local Verizon rep?
ContraMan said:
Ok, it seems I have found a bit of the issue that is causing it. My phone number and IMSI are not detected as my current phone number. Is there a way to program this or is it an issue where I'll have to have it reprogrammed by the local Verizon rep?
Click to expand...
Click to collapse
try a *228 and option 1 so the phone is reprogrammed. then do a test call to your vm(*86) and make sure it connects, you should not see the 3G symbol, when you end the call, the 3G should be displayed...give it a whirl
This did not work. There has to be a way to program the phone number into the phone. Any ideas?
i've been having this same issue... messing with airplane mode and rebooting a few times got it to fix... *228 and option 2 worked sometimes. just loaded up Adryns new evo hybrid rom, working fine so far (the problem was rare, maybe twice a day tops) and did *228 1, we shall see!
To no avail on these. I think I'm going to have to see a rep tomorrow and see if we can get the phone number (my actual phone number) programmed back into the phone. I think that's a VZW thing as I'm sure they won't run me through the methods to program a phone number.
I hate that I have to go back to Big Red over this, but it is important for me to have this phone up and running. Besides internet, I have NO other form of contact.
3g issue
I had the same problem and so have many others, I flashed Skyraider Rom and problem is gone so we know its not a buggy radio, I don't think there is a fix right now, but I've never seen a Rom so stable as the new Skyraider, so you might wanna think about flashing that Rom.
Coincidence. I've heard the same with my roms, from both ends of the spectrum. Its for sure a buggy radio, and how it interacts with Froyo. Once we get a 100% Froyo ready radio, I doubt we will ever hear about the issue again.
This is the first I've heard of someone not being able to get the 3G connection back at all. Is that what you are describing? I had it not turn on, then come back after a *228/2 or power cycle - but it always came back on. Just curious but are you on an Alltel plan by chance?
Can you make calls Contra? Did you pay your phone bill?? Are you wiping all data before flashing? Try the full second leak that they added to that post. I've been using it and haven't had the 3G drop in two days now. I just took that rom and removed a handful of apps I would never use. It's working quite well.
I have an HTC Hero that keeps entering "Emergency Callback Mode" for what seems to be no reason at all. It mostly happens as soon as I answer an incoming call but also randomly in between.
This mode kills all data conenctions and prevents outgoing calls for 5:00. But, even if I say cancel, or wait the 5 minutes, it still stays on and I have to reset the device. It usually resolves itself after 45 mins or so. It happens once or twice a day.
I have researched the issue on google and I have found very little information about this problem. On some phones, this mode is enabled immediately after calling 911 to allow rescuers to call you back and locate you via GPS. I have never called 911 on this device.
I am currently running Cyanogen 7.1 RC2 ROM but I had the same issue on many different ROMS I tried so its not related to that.
on baseband 2.42.01.04.27. Maybe I should try downgrading it? How can I do that safely?
I really don't want to try reverting back to a stock ROM...
EDIT:
I think I posted this in the wrong forum, mod please move, sorry.
Hmmmm........so a complete doesn't solve the issue? And when you say ''sense'', does that mean with sense, it doesn't happen, but with the other Roms it does?
Try updating your radio to the latest .29
Yea its Me Again With the
Modified Hero
I just upgraded to the lastest baseband and it's still doing it.
I also figured out I can trigger the problem immediately by going to mobile network settings and changing my roaming preferences.
I should probably not that I recently repaired this phone and used QPST service programming tool to copy settings over from a touch pro 2 to the Hero. Could there maybe have been a wrong setting from the TP2 that is affecting the CDMA on this phone??
Just did a PRL update. No luck...
Did a succesful over-the-air profile and PRL update. Same problem...
ki1022 said:
Could there maybe have been a wrong setting from the TP2 that is affecting the CDMA on this phone??
Click to expand...
Click to collapse
Sounds like it. Is there no way to put everything back to default manufactured settings?
oohaylima said:
Sounds like it. Is there no way to put everything back to default manufactured settings?
Click to expand...
Click to collapse
I am considering using a stock RUU to completely wipe the phone to factory settings, but am trying to exhaust all my other options first so I won't have to re-root it and set everything up again... I'm almost at that point though.
ki1022 said:
I am considering using a stock RUU to completely wipe the phone to factory settings, but am trying to exhaust all my other options first so I won't have to re-root it and set everything up again... I'm almost at that point though.
Click to expand...
Click to collapse
!!!!!!!!!!!
FIXED IT SUCKAS.
Did a ##786# which reset all the CDMA settings, then re-did my NAM and data profile settings and it works. Go figure. Doing the ##786# on this phone also retained nearly everything including meid, baseband, recovery, and ROM. All it did was fix the problem. Awesome.
I still have no idea what was causing this to begin with, it was driving me crazy. Hopefully this thread will be helpful to someone else who has the issue.
On a side note, how dumb is this emergency mode?? So you call 911, then you can't call anyone else after that?? What if you need to call your wife and kids to say you love them one more time?! Haha.
Awesome!!!!!! Glad it's fixed. Now I'll just star this just in case it happens to me.
Using stock sense and sprint/gv integration and i can receive texts in gv as well as send them from the stock messaging app and gv.
i've contacted sprint on the phone a couple times and got to the highest level tech support and they couldn't fix it. also tried the sprint store and they just want to give me another evo. they have one on order, but i'd much rather keep my rooted evo! the new one will likely have 2.3 installed stock and i'll need to wait for root.
this really doesn't seem like a hardware issue anyways, seems like it's a network side problem.
i've made sure sms forwarding is enabled to my mobile number on gv, tried factory and hard resets multiple times. tried unintegrating and reintegrating my sprint number with gv.
the weird thing is even when i'm unintewgrated and using just vanilla sprint i don't receive texts at all. i can send them, make and receive calls too but never does a text come to my phone.
there doesn't seem to be anyone else reporting this problem i8n my area.
phone is rooted, stock rom, the problem started after iu hard reset my phone. i was hoping a hard reset would fix some buis i was experiencing with the GB update. i can't say for sure this was because i hard reset, buit it's a huge coincidence that it happened at approximately the same time. i can't think of any logical reason the hard reset would affect my sms this way.
btw i installed a rooted version of 2.3.3 as well as the latest combo radio pack. that was over a week ago though and this issue just cropped up yesterday.
hopefully this post wasn't too jumbled and i gave enough info, any ideas?
edit: crap, should be in the Q&A forum, please move if necessary :/
Try updating your profile
Sent from my PC36100 using XDA Premium App
i've done that a bunch of times, so did sprint.
[Q] If you call one of the people you text, does the return text from them show up after the call?
dpilcher said:
[Q] If you call one of the people you text, does the return text from them show up after the call?
Click to expand...
Click to collapse
No it doesn't.
Brandito said:
No it doesn't.
Click to expand...
Click to collapse
Not what I was going through a few months back then, but I could make calls but not receive calls. I don't use GV either so probably not the same issue. Just thought I would ask, turns out those issues for me was my 3G going out on my phone. Ended up getting it replaced.
Hope you find a solution, I know how frustrating it is.
dpilcher said:
Not what I was going through a few months back then, but I could make calls but not receive calls. I don't use GV either so probably not the same issue. Just thought I would ask, turns out those issues for me was my 3G going out on my phone. Ended up getting it replaced.
Hope you find a solution, I know how frustrating it is.
Click to expand...
Click to collapse
sprint is ordering me another phone, hoping against it being a refurb, though then i likely have to wait for a new root method for gingerbread.
preferably they'd get it working on my current evo. i really think it has to be a network issue.
Brandito said:
sprint is ordering me another phone, hoping against it being a refurb, though then i likely have to wait for a new root method for gingerbread.
preferably they'd get it working on my current evo. i really think it has to be a network issue.
Click to expand...
Click to collapse
You should be good, I had two replacement refurbs as early as last week and they both had 3.7 on them. Watch for the sunspot on the screen when it boots initially (bright white spot in the lower half towards the middle), both of the refurb replacements had the bad screen. You can't see it if it boots all the way..you'll have to go to a bright screen to see it but it will just get worse to where you will see it all the time. Finally the rep gave me a NIB 004..also 3.7. Just make sure they don't update it, I would ask if you could do the activation as well so you can look for the screen issue on initial boot. Good Luck! Guess I didn't have to quote due to it being right above mine...lmao
Think they'll give me any trouble if I turn in my phone still rooted? I don't feel like unrooting it, not to mention if the new/refurb doesn't fix my issue I'm going to keep my current evo anyways.
I mean they've already approved me for the replacement.
I had the same problem
I had the exact same situation happen last weekend. All I did to fix it was to flash back to a Stock Sense 2.2 ROM, Update Profile/PRL, and then open EPST and Reset Data connection using THIS little tutorial.
foxtrotftw said:
I had the exact same situation happen last weekend. All I did to fix it was to flash back to a Stock Sense 2.2 ROM, Update Profile/PRL, and then open EPST and Reset Data connection using THIS little tutorial.
Click to expand...
Click to collapse
can't even get it to do anything after entering ##3283#, never even pops up a dialog.
foxtrotftw said:
I had the exact same situation happen last weekend. All I did to fix it was to flash back to a Stock Sense 2.2 ROM, Update Profile/PRL, and then open EPST and Reset Data connection using THIS little tutorial.
Click to expand...
Click to collapse
Ya..did all that and then some to mine..no dice. But good advice. Hardware issue won't be solved by software no matter the method I found out. Believe me..even went as far as unrooting and seeing if stock would be the same..it was.
The unrooting process is very easy and with the replacement coming in, why not. Sounds like hardware anyway. Here is what I did to go back and forth:
http://forum.xda-developers.com/showthread.php?t=1113620
You can also look at the stickies at the top of general/Q&A for options.
Good Luck.
dpilcher said:
Ya..did all that and then some to mine..no dice. But good advice. Hardware issue won't be solved by software no matter the method I found out. Believe me..even went as far as unrooting and seeing if stock would be the same..it was.
The unrooting process is very easy and with the replacement coming in, why not. Sounds like hardware anyway. Here is what I did to go back and forth:
http://forum.xda-developers.com/showthread.php?t=1113620
You can also look at the stickies at the top of general/Q&A for options.
Good Luck.
Click to expand...
Click to collapse
doesn't seem like hardware at all to me though. and if that's the case and I unroot and end up keeping this phone i just shot myself in the foot by locking my bootloader.
i wish i would have had them try activating another phone today to see if another phone would be able to receive the texts.
No need to unroot! Go to voice.google.com, click on the "gear" icon to go into Voice Settings. Find your gv/sprint phone number, click Edit and check the checkbox for "receive text messages on this device." Hit save, and enjoy.
jesuspgt said:
No need to unroot! Go to voice.google.com, click on the "gear" icon to go into Voice Settings. Find your gv/sprint phone number, click Edit and check the checkbox for "receive text messages on this device." Hit save, and enjoy.
Click to expand...
Click to collapse
that's only the FIRST thing I tried, along with unchecking, rechecking, removing integration, readding it..twice! and about a dozen combinations of applying settings, checking and unchecking boxes and finger crossing.
Brandito said:
that's only the FIRST thing I tried, along with unchecking, rechecking, removing integration, readding it..twice! and about a dozen combinations of applying settings, checking and unchecking boxes and finger crossing.
Click to expand...
Click to collapse
Apologies, but you didn't mention that you did this in your post. Had no way of knowing that you've already tried this.
jesuspgt said:
Apologies, but you didn't mention that you did this in your post. Had no way of knowing that you've already tried this.
Click to expand...
Click to collapse
I actually did in my first post, though that post is a bit of a mess I realize, it's hard to really put everything I've already tried in any neat order.
No worries either way, any suggestions are welcome at this point.
I was running tx_dbs_tx Hybrid X 3.0 up until this morning when my phone suddenly kept popping up the Data Roaming Guard. Whenever I would attempt to make a call, it would alert me to a Verizon error to reboot my phone -I am on Sprint. I flashed with Odin the stock OK1 software, and besides having Knox and ItsOn back on my phone and battery life being horrible once again, I am still receiving the Data Roaming Guard splash screen and still receiving the Verizon error when making calls. I was able to make a single call after using the Activate Device self-service, but it didn't even last 20 minutes.
Again, back on stock OK1 ROM from Sammobile, re-rooted with Freeza's OK1 stock kernel, SuperSU Beta 2.52, any help would be greatly appreciated.
BGray210 said:
I was running tx_dbs_tx Hybrid X 3.0 up until this morning when my phone suddenly kept popping up the Data Roaming Guard. Whenever I would attempt to make a call, it would alert me to a Verizon error to reboot my phone -I am on Sprint. I flashed with Odin the stock OK1 software, and besides having Knox and ItsOn back on my phone and battery life being horrible once again, I am still receiving the Data Roaming Guard splash screen and still receiving the Verizon error when making calls. I was able to make a single call after using the Activate Device self-service, but it didn't even last 20 minutes.
Again, back on stock OK1 ROM from Sammobile, re-rooted with Freeza's OK1 stock kernel, SuperSU Beta 2.52, any help would be greatly appreciated.
Click to expand...
Click to collapse
Do you live in a 4G Sprint area? If not this EXACT same thing happened to me and my wife right before they started 4G in our area. Even service calls went to Verizon first. Evidently even the Sprint reps had no idea that 4G was getting turned on in my area, they had me do all the #* dialer codes and both our phones said we were in roaming for like a day or two.
ianmb said:
Do you live in a 4G Sprint area? If not this EXACT same thing happened to me and my wife right before they started 4G in our area. Even service calls went to Verizon first. Evidently even the Sprint reps had no idea that 4G was getting turned on in my area, they had me do all the #* dialer codes and both our phones said we were in roaming for like a day or two.
Click to expand...
Click to collapse
Yes, San Antonio was one of the first markets with Sprint to have 4G WiMax and then 4G LTE. It had been running just fine for months, but suddenly stopped working. Even after flashing stock back on without root or any added apps besides Sprint's auto-downloads, it still had the problem. Took it to the store yesterday and baffled them all for 2 hours before they ordered me a replacement. They even tried a new sim card because I told them that I've had problems intermittently in the past with the Roaming Guard popping up and forums stated it could be a bad sim card. The Sprint # codes wouldn't even work. Anyways, they ordered me a replacement- won't have it until Tuesday but thanks for the response. I had never heard of anything like this happening before and it struck me as odd. I even checked the settings for the network and they all checked out fine, Sprint store reps did the same and were just as perplexed as I was.
Mine was doing almost the same. Seemed like it had to go to verizon when it would go between towers. Then back to sprint. So I did the ##72786# that is suppose to launch the hands free activation. Although it didnt launch it(due to custom rom), it did run the provisioning stuff and fixed mine. Hasn't went to roaming yet.
No promise it will work. But hopfully it will fix yours. Assuming you are on a note 4.
Txdaredvl said:
Mine was doing almost the same. Seemed like it had to go to verizon when it would go between towers. Then back to sprint. So I did the ##72786# that is suppose to launch the hands free activation. Although it didnt launch it(due to custom rom), it did run the provisioning stuff and fixed mine. Hasn't went to roaming yet.
No promise it will work. But hopfully it will fix yours. Assuming you are on a note 4.
Click to expand...
Click to collapse
Yes, I am on Sprint Note 4, but the pound codes wouldn't even work. As soon as I put in the last # sign it just cleared out the dialer. I found a complete list of # codes on sammobile or samfirmware site, can't remember which, and even Sprint attempted them. I had flashed back to stock available on Sammobile prior to going to Sprint, but it still didn't work. You don't think different flashes or ROMs or kernels could have caused this do you?
Anyways, I have the insurance through Sprint and have a new one on the way Tuesday. I just hate not being able to figure out a software related problem. I was also trying to find a way to do it manually while rooted, but couldn't find the right edits because I cannot even remember how to get into the correct settings at the moment-mind cluttered with too many projects.
I appreciate all of the responses though and really enjoy learning about my device on xda and hope to either create my own apps or even cook a ROM in the near future.
Hey all!
I purchased my Essential phone brand new from Sprint yesterday. I switched from an S7. I'm trying to use the default android messages app (what I used on my S7) and I tried to enable enhanced messaging to receive stuff via WiFi. I get horrible reception at my desk in my office, so texting over WiFi is super helpful. Well, when I go to turn on enhanced messaging in the app, It just clocks, and eventually says "Excuse the wait... messages will let you know when this step is complete." I click "Got It", then it proceeds to do nothing...
Has anyone else figured how to turn on enhanced features on this device? Sprint is my carrier.
Runnerman14 said:
Hey all!
I purchased my Essential phone brand new from Sprint yesterday. I switched from an S7. I'm trying to use the default android messages app (what I used on my S7) and I tried to enable enhanced messaging to receive stuff via WiFi. I get horrible reception at my desk in my office, so texting over WiFi is super helpful. Well, when I go to turn on enhanced messaging in the app, It just clocks, and eventually says "Excuse the wait... messages will let you know when this step is complete." I click "Got It", then it proceeds to do nothing...
Has anyone else figured how to turn on enhanced features on this device? Sprint is my carrier.
Click to expand...
Click to collapse
Has happened to me on all my devices I've owned when starting from a clean slate. Just give it time. Check back and reinitiate if needed. Think it has something to do with the carrier side network refresh to see your device or something.
mrcooter said:
Has happened to me on all my devices I've owned when starting from a clean slate. Just give it time. Check back and reinitiate if needed. Think it has something to do with the carrier side network refresh to see your device or something.
Click to expand...
Click to collapse
Thanks for the quick reply! Very strange... Do you remember roughly how long it took for your's to communicate back to the carrier and get up and running?
Runnerman14 said:
Thanks for the quick reply! Very strange... Do you remember roughly how long it took for your's to communicate back to the carrier and get up and running?
Click to expand...
Click to collapse
Sorry, little bit longer on the reply this time. Lol. Busy day at work. But it's happened to me with different time lengths. It's been successful within 30 minutes and it's also taken up to 2 days. Sorry I can't be more help. Not sure of the technical side of things on what exactly causes it to know for sure and the fact that I'll just check it and it's done. Because of this, not always sure when exactly it went through either, just know that eventually it starts working and it's happened on my Essential and previous Nexus devices with Sprint, and that out of everything I'd try, time was the only thing that fixed it for me.
Hello I am experiencing the exact same issue with my new Essential phone through Sprint I purchased yesterday. Has your enhanced Features issue resolved itself yet? Any pointers? Sprint was absolutely no help.
Ana
Made me look. I'm on rooted Oreo 8.1, everything checked off.
Sent from my PH-1 using XDA Labs