Related
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
I sold my 3D to someone and have been trying to put a new rom on it for em. Everytime I flash a 2.3.4 rom everything works EXCEPT during a call you can hear the person talking but they cant hear you. And I know the speaker works because voice commands work fine but during it call it doesn't work, period.
Sounds Like a personal phone issue..I've been on 2.3.4 with multiple roms and never had this issue.
Sent from a little place called ETERNITY in the 3rd Dimension.
I never had that problem running 2.3.4 ROMs either.
I honestly don't get it. Every 2.3.4 rom I tried to put on the phone would have the issue with not being able to be heard during a call. I tried 4 different roms and had the same issue everytime. Put a 2.3.3. rom on it and I could be heard during calls fine. I dunno but I got tired of fooling with it.
I did notice one thing though... when wiping in recovery I got an error that said
E:can't give path "/sdcard/.android_secure" to format_volume
Think that might have something to do with it?
OP, did you do the EVRC-B mod? If so, undo it.
Compusmurf said:
OP, did you do the EVRC-B mod? If so, undo it.
Click to expand...
Click to collapse
I don't even know what that is lol. This is basically the scenario. I can flash ANY 2.3.3 rom or lower than that and everything works perfectly fine. But as soon as I flash any rom with a 2.3.4. base everything works except for callers being able to hear me. It's crazy... I even tried the stock 2.3.4. deodexed update and it was the same thing. Flash a 2.3.3. rom and boom, they can hear me again.
brownhornet said:
I don't even know what that is lol. This is basically the scenario. I can flash ANY 2.3.3 rom or lower than that and everything works perfectly fine. But as soon as I flash any rom with a 2.3.4. base everything works except for callers being able to hear me. It's crazy... I even tried the stock 2.3.4. deodexed update and it was the same thing. Flash a 2.3.3. rom and boom, they can hear me again.
Click to expand...
Click to collapse
The EVRC-B mod enhances voice, the same settings found on Verizon phones but in some cases it might not be supported by the tower. Its accessed in the EPST edit menu, via your MSL code.
But if you're flashing the ROMs with voice performance changing, I'm not sure whats going on. As I seriously doubt the EPST settings get changed by the ROM.
I could be wrong.
I don't know either... im clueless. First time i've ever had a hangup like this when flashing. I put it on the phone for her and everything was all good until she got a call and realized they couldn't hear what she was saying. I thought maybe it was a bad flash but hell i've tried every rom in the development forum almost.
none
Give the guy his money back, put it under your car tire, then smoke the tires, that phone sounds retarded.
Try revolution by Mike and see if that shows the same issue.
If it does then either your doing something wired while flashing, have some app messing crap up, or its hardware problem somehow.
Likely its user error somehow though. I dunno any roms that flip evrb on for voice by default for the mere fact that its not supported everywhere.
Sent from my PG86100 using XDA App
But how would it be user error only for the 2.3.4. roms lol. Im sayin... i'm not doing anything different. Just download, transfer from pc to sd and flash through recovery like I always have. If it was user error it seems like id have problems with the 2.3.3. roms too. I gave up on it though.. technically it's not even my phone anymore lol
Hello everyone,
I'm not sure if I'm the only one or not since I haven't seen this issue in any of the threads for any JB Roms. This doesn't seem to be a problem for any 1 Rom, so I'm thinking it has to do with the CM10 base everyone is using. Here is the problem:
Everything is fine on the Rom for a few days - I can browse the web, make calls, get emails, etc... Then, I'll make a call, and the call will connect (call timer starts on screen), but I can't hear the person on the other end, and they can't hear me. I know this for a fact because I called my wife's phone which I was using as a test.
It would continue to stay like this (even after rebooting normal, rebooting to recovery and wiping cache / dalvik). The only thing that seemed to fix the problem would be to re-install the Rom.
For now I'm back on one of the CM9 Roms, and everything is ok. I really like CM10, but don't want to potentially get into an emergency situation, and then not be able to use my phone, or go to make a business call, and look like an idiot because people can't hear me, etc...
I just wanted to know if anyone else has experienced this, or has a fix? Thanks for your input.
what Rom ? (specific)
what carrier? ( is this an ATT device running with a different carrier? )
what region? (are you in the US, Canada, or elsewhere? )
Most reports are leaning toward the modem as the issue. If we know the above information, we can suggest a fix or patch based on them....g
gregsarg said:
what Rom ? (specific)
what carrier? ( is this an ATT device running with a different carrier? )
what region? (are you in the US, Canada, or elsewhere? )
Most reports are leaning toward the modem as the issue. If we know the above information, we can suggest a fix or patch based on them....g
Click to expand...
Click to collapse
Rom: I've tried all of the CM10 Roms currently available, and it happened on each of those. Most recent was CM10Hybrid Paranoid Android.
Carrier: AT&T
Region: US. More specifically - South East.
The last modem I flashed directly (unless one was cooked into a rom), was UCLF6.
scotty2hotty1125 said:
Rom: I've tried all of the CM10 Roms currently available, and it happened on each of those. Most recent was CM10Hybrid Paranoid Android.
Carrier: AT&T
Region: US. More specifically - South East.
The last modem I flashed directly (unless one was cooked into a rom), was UCLF6.
Click to expand...
Click to collapse
Lets test this a bit more....
Download and flash the Stock, UCLA1 modem, then reboot it 3 times. then try a call to a test device.
I've had marginal success with the modems above the UCLA range, and am using the UCLA1 Modem on virtually all of the roms I use. ( now if I could get all 1352 apn's from the stock rom to work...LOL ).....
It may show up as "unknown" in the "about phone" settings, but based on the tests I've done with it, you should be safe on the IMEI loss issue that some TMO users are reporting.
There is always that chance, but where you are US based on ATT, and that is their modem, you should be fine.
Test that bad boy out, and report back if ya would...thank you....g
I think its just the cm10 roms ..mainly because I've seen a post like this in all the JB forums...
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
scotty2hotty1125 said:
Hello everyone,
I'm not sure if I'm the only one or not since I haven't seen this issue in any of the threads for any JB Roms. This doesn't seem to be a problem for any 1 Rom, so I'm thinking it has to do with the CM10 base everyone is using. Here is the problem:
Everything is fine on the Rom for a few days - I can browse the web, make calls, get emails, etc... Then, I'll make a call, and the call will connect (call timer starts on screen), but I can't hear the person on the other end, and they can't hear me. I know this for a fact because I called my wife's phone which I was using as a test.
It would continue to stay like this (even after rebooting normal, rebooting to recovery and wiping cache / dalvik). The only thing that seemed to fix the problem would be to re-install the Rom.
For now I'm back on one of the CM9 Roms, and everything is ok. I really like CM10, but don't want to potentially get into an emergency situation, and then not be able to use my phone, or go to make a business call, and look like an idiot because people can't hear me, etc...
I just wanted to know if anyone else has experienced this, or has a fix? Thanks for your input.
Click to expand...
Click to collapse
I second that as the same happened to me, but all I did was reboot and it solved the issue. Happens at least once or twice a day for me.
Sent from my SAMSUNG-SGH-I717 using xda premium
Have any of you tried a scheduled cache clearing app ?
I've found many issues due to cache building in the background APK's....
It effectively bogs down everything , and once cleaned , fixes "a lot " of issues ...
Could someone test this and report back ?
At least we would know where to look at fixing the issues, rather than assuming it's a modem issue .....g
On every Jellybean rom, I have calling issues. On some roms, call audio wont work. On the rom I just flashed, it would not make or receive calls all together. Also, this happens only after a certain period of time. And it goes from sporadic occurances to permanent. It takes about a day or two for these issues to start appearing. This is so god damn frustrating because in the beginning the rom works perfectly, I spend all my time setting it up, and then a day or so later, I get these issues that make the phone completely unusable. Its absolutely ridiculous, and If anyone has any ideas, please please let me know. I love the JB roms but they all seem to make my phone unusable after a short time.
Please help....
JB roms are still a work in progress. And your problems could be caused/made worse by your setup (apps, widgets, tweaks, etc...). If you are using different kernels/radio, it can also contribute to problems. There are just too many variables.
My answer : use an ICS rom. ICS roms are alot more stable on our phone right now.
H0rn3t920 said:
On every Jellybean rom, I have calling issues. On some roms, call audio wont work. On the rom I just flashed, it would not make or receive calls all together. Also, this happens only after a certain period of time. And it goes from sporadic occurances to permanent. It takes about a day or two for these issues to start appearing. This is so god damn frustrating because in the beginning the rom works perfectly, I spend all my time setting it up, and then a day or so later, I get these issues that make the phone completely unusable. Its absolutely ridiculous, and If anyone has any ideas, please please let me know. I love the JB roms but they all seem to make my phone unusable after a short time.
Please help....
Click to expand...
Click to collapse
I am observing similar issues. I didn't used to happen before. I mean it did happen but it was a rare thing. But now it is more often. Almost everyday I have to reflash because of loosing phone audio.
I was rocking AOCP 3.1 , Worked really sweet and then decided to update to go for AOCP 4.1 and since then no rom that I tried have saved me. In fact I had to revert back to stock. What rom are you using?
People, it's a known issue on all JB Roms.
Don't open a thread about it.
xaragen said:
I am observing similar issues. I didn't used to happen before. I mean it did happen but it was a rare thing. But now it is more often. Almost everyday I have to reflash because of loosing phone audio.
I was rocking AOCP 3.1 , Worked really sweet and then decided to update to go for AOCP 4.1 and since then no rom that I tried have saved me. In fact I had to revert back to stock. What rom are you using?
Click to expand...
Click to collapse
I have the exact same issue now, It doesnt look like any rom is saving me right now.. my phone wont make calls or receive texts at all. I was running cookies and cream 4.1.2 and everytime i flash a JB rom it just seems to get worse and worse...
EDIT: I got it back on ICS. I guess I will just have to wait to use any JB roms... its unfortunate cause I love the JB roms hahaha
I have had issues with JB as well. I, just like the OP, would experience a perfectly working phone for a day or two then **** would hit the fan for no apparent reason. The phone would start locking up, randomly rebooting, apps would fail or not load, etc etc etc.
On most ROM's I didn't even have anything installed outside of the stock apps that CAME with the ROM.
Since then I have moved to a deoxed stock ICS ROM and honestly am not looking back. ICS is fast, stable, feature packed, and JUST WORKS.
My thing with JB was it's speed...but I was also comparing a barebones JB to the stock Gingerbread that came with the phone. I wasn't aware of how fast ICS was or I would have just gone with it long before hand!
But yeah, either way it goes, for me, no matter the ROM, JB always seemed to mess up at one point or another. Got annoying. Been going with ICS for over a week now with ZERO issues what so ever. No reboots, no crashes, no freezing, no nothing.
NEVERMIND..... ICS worked for one call, and now no calls work... great....
ICS roms are very stable.
You may have flashed your rom/kernel/radio incorrectly, or made some tweaks, or installed incompatible apps... There are too many variables.
Revert back to completely stock setup and see if the problems persist.
H0rn3t920 said:
NEVERMIND..... ICS worked for one call, and now no calls work... great....
Click to expand...
Click to collapse
I'll take a stab, what gapps? Do you use a call blocker of any kind?
Sent from my Samsung-SGH-I717 using xda premium
Same. I think it's the same for a lot of people, and I think the ones who say things run great either ignore the problems or are just extremely lucky.
Switch to Padawan. It's rock solid and you get all the fanciness of jelly bean. Since switching to it I've completely lost the itch to try out random JB ROMs. I have cool animations, Google Now, and ICS Browser+. And until I rebooted earlier to mess with stuff, I was at 142 hours uptime without any problems.
I'm not calling anyone a liar, though. I just think some people ignore more or are, as stated, lucky. I've done wiped everything, went back and wiped stuff post ROM, ran 3rd party (3rd ROM party) kernels and the ones that come with it. I've set cron to fix permissions on boot. And other than gapps -- which I always flash what the dev says to -- I run about ten 3rd party apps, and that's mostly made up of solid apps -- dropbox, exdialer, ics browser+.. etc..
Padawan, or even Nebula.
These ROMs are by the same dev, and the only difference is that Nebula is based off of Canadian version, which has even less bloat. It is better than stock.
I have been on Nebula for about a week, and no random reboots, no lockup, no phone problems. Everything just works.
ddochi11 said:
Padawan, or even Nebula.
These ROMs are by the same dev, and the only difference is that Nebula is based off of Canadian version, which has even less bloat. It is better than stock.
I have been on Nebula for about a week, and no random reboots, no lockup, no phone problems. Everything just works.
Click to expand...
Click to collapse
I like padawan, and Im on it now. But i still am getting this random issue where calls do not go through. Its so aggravating that Im about to smash my phone against the wall. Its happening all the time now and when I need to make a call, I cant. god damnit
have you flashed the most recent modem?
Yes, that was my next question.
Have you at any point flashed a different kernel/radio/modem? If you have, or if you do not know, search for stock kernel/radio/modem and flash them to see if it helps.
yes, uclf6 modem but eventually it just gives out.. idk what the issue is here everything works fine for a few days and out of the blue when I need my phone i cant receive or make calls anymore its INFURIATING
yes, uclf6 modem but eventually it just gives out.. idk what the issue is here everything works fine for a few days and out of the blue when I need my phone i cant receive or make calls anymore its INFURIATING
Revert back to complete stock and see if the issue still exists.
Mobile Network Type
Ltilt2 said:
People, it's a known issue on all JB Roms.
Don't open a thread about it.
Click to expand...
Click to collapse
I have had a similar issue with the JB rom's...so far I've tried only two and seem to find the aokp_quicyatt_jb_milestone-1 rom. I have noticed issues with my phone and LTE network coverage...meaning, I can see the signal go from 4G LTE to 3G to H, then gone...I looked at the phone status settings and noticed the mobile network type with this rom is LTE:13 and with the stock ICS rom (prior to rooting and flashing) it was LTE:14...is there a way that I can change it via terminal? Thank you in advance for any help on this. The one big difference I can see so far is the battery life...much better. Any help is greatly appreciated.
Issues are known....Thread Closed & Thank You.
I had CodeFire on my DNA for about a month. All was running well. I just installed whatever was current around 2/23 and never installed a nightly update. Last week, I started having problems texting. I thought the ROM was going belly up on me. So I flashed SlimKat. I still cannot text without cycling Airplane Mode in between each. Alternatively, I can wait about an hour to sent a subsequent test message after a successful one.
I just re-flashed the latest radio hoping that would fix it. I'm at a loss. Do I need to call VZW and have them do something on their end?
mdphoenix said:
I had CodeFire on my DNA for about a month. All was running well. I just installed whatever was current around 2/23 and never installed a nightly update. Last week, I started having problems texting. I thought the ROM was going belly up on me. So I flashed SlimKat. I still cannot text without cycling Airplane Mode in between each. Alternatively, I can wait about an hour to sent a subsequent test message after a successful one.
I just re-flashed the latest radio hoping that would fix it. I'm at a loss. Do I need to call VZW and have them do something on their end?
Click to expand...
Click to collapse
Nothing? Just flashed another ROM. Phone is dead. Am I beating a dead horse with this question? Someone point me in the right direction then, please. Everything I've read states that the SMS issues are related to showing double texts. I can't find this exact problem.
My phone is useless to me now.
mdphoenix said:
Nothing? Just flashed another ROM. Phone is dead. Am I beating a dead horse with this question? Someone point me in the right direction then, please. Everything I've read states that the SMS issues are related to showing double texts. I can't find this exact problem.
My phone is useless to me now.
Click to expand...
Click to collapse
The kit kat roms are ported. There are several issues with them that cannot be "fixed" until the source code is released. If the phone does not respond to any commands including trying to boot.... leave it on a factory charger for 24 hours. Then try to work with it
mdphoenix said:
Nothing? Just flashed another ROM. Phone is dead. Am I beating a dead horse with this question? Someone point me in the right direction then, please. Everything I've read states that the SMS issues are related to showing double texts. I can't find this exact problem.
My phone is useless to me now.
Click to expand...
Click to collapse
What do you mean by "phone is dead"? Completely non responsive or no signal. I've been on cfx since I ported it over with no issues besides the random signal drop here and there. But that's maybe a few times per week and happens to me on all ROMs. What do you wipe when flashing a new ROM? Have you tried a RUU?
Sent from my HTC6435LVW using xda app-developers app
danjull said:
What do you mean by "phone is dead"? Completely non responsive or no signal. I've been on cfx since I ported it over with no issues besides the random signal drop here and there. But that's maybe a few times per week and happens to me on all ROMs. What do you wipe when flashing a new ROM? Have you tried a RUU?
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Dead as in Roaming again. My apologies for the exaggeration. I'm a bit frustrated here. I cannot seem to win with this thing. I hated my Thunderbolt at the end, but at least it worked. RUU brings back mobile data and texting. I've tried CM 10.2 several times. Each time, it gets stuck in roaming. I cannot change the NV setting. Changing it, then checking it again and it's right back. I've tried flashing with the SIM in. With it out. I've cycled Airplane mode a few times. Rebooted. Installed GApps. Rebooted. Cycled Airplane mode. I'm missing something. Apparently.
I just want a phone without Sense or the Verizon crap. CFX was awesome until this texting issue.
mdphoenix said:
Dead as in Roaming again. My apologies for the exaggeration. I'm a bit frustrated here. I cannot seem to win with this thing. I hated my Thunderbolt at the end, but at least it worked. RUU brings back mobile data and texting. I've tried CM 10.2 several times. Each time, it gets stuck in roaming. I cannot change the NV setting. Changing it, then checking it again and it's right back. I've tried flashing with the SIM in. With it out. I've cycled Airplane mode a few times. Rebooted. Installed GApps. Rebooted. Cycled Airplane mode. I'm missing something. Apparently.
I just want a phone without Sense or the Verizon crap. CFX was awesome until this texting issue.
Click to expand...
Click to collapse
EDIT: Just installed the latest CFX and AGAIN I have the god blessed SMS issue. I can't sent sequential texts. I have to turn on Airplane mode after each one before sending the next.
mdphoenix said:
EDIT: Just installed the latest CFX and AGAIN I have the god blessed SMS issue. I can't sent sequential texts. I have to turn on Airplane mode after each one before sending the next.
Click to expand...
Click to collapse
omfg. I just installed a stock Odexed, Rooted 3.06.605.4. SMS works but now I'm stuck in 3G. Is there a ROM out there that works so I can use my phone for work and play or should I Just suck it up and put it back to a full stock OTA ROM?
mdphoenix said:
omfg. I just installed a stock Odexed, Rooted 3.06.605.4. SMS works but now I'm stuck in 3G. Is there a ROM out there that works so I can use my phone for work and play or should I Just suck it up and put it back to a full stock OTA ROM?
Click to expand...
Click to collapse
Have you considered hardware issues? If it was a ROM issue it wouldn't be a one person issue. Or provide a log of what's happening when you send SMS. You're just not giving us much to go by, except what's not working. Are you doing full wipes between flashing roms, or just cache or factory resets?
Sent from my HTC6435LVW using xda app-developers app
danjull said:
Have you considered hardware issues? If it was a ROM issue it wouldn't be a one person issue. Or provide a log of what's happening when you send SMS. You're just not giving us much to go by, except what's not working. Are you doing full wipes between flashing roms, or just cache or factory resets?
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Full Wipes between flashes.
I've had this phone for about two months. I initially had issues flashing CM and being stuck in roaming. No CM ROM I attempt to flash will work. They always end up stuck in roaming. I think the problem is that I can't switch from NV. When I change it, it always goes right back. Not sure what's up there.
I just flashed ★ ☆ [ROM/RADIO][4.2.2] Stock 3.06.605.4 | Rooted | Odex-Deodex | Sense5 And now SMS works, but I'm stuck in 3G.
I hadn't considered hardware only because with each ROM, the previously broken feature works, but then something new pops up.
With one, I can text, but am in 3G. With another, I've got 4G but can't text without cycling Airplane mode.
I sincerely apologies for coming off as a d!ck. I've nothing to contribute to the community but my bug reports and money. It's frustrating to see how quickly some phones are abandoned, though.
I've always been thankful for everyone's help and tried to offer bug reports and donations where applicable.
I just want my phone to work, with a plain vanilla OS and tethering. I don't need Sense. I don't need fancy mods. Just a phone that works.
Please accept my apology, and thanks again for the help.
mdphoenix said:
Full Wipes between flashes.
I've had this phone for about two months. I initially had issues flashing CM and being stuck in roaming. No CM ROM I attempt to flash will work. They always end up stuck in roaming. I think the problem is that I can't switch from NV. When I change it, it always goes right back. Not sure what's up there.
I just flashed ★ ☆ [ROM/RADIO][4.2.2] Stock 3.06.605.4 | Rooted | Odex-Deodex | Sense5 And now SMS works, but I'm stuck in 3G.
I hadn't considered hardware only because with each ROM, the previously broken feature works, but then something new pops up.
With one, I can text, but am in 3G. With another, I've got 4G but can't text without cycling Airplane mode.
I sincerely apologies for coming off as a d!ck. I've nothing to contribute to the community but my bug reports and money. It's frustrating to see how quickly some phones are abandoned, though.
I've always been thankful for everyone's help and tried to offer bug reports and donations where applicable.
I just want my phone to work, with a plain vanilla OS and tethering. I don't need Sense. I don't need fancy mods. Just a phone that works.
Please accept my apology, and thanks again for the help.
Click to expand...
Click to collapse
Verizon is sending me another phone. Stay tuned.
mdphoenix said:
Verizon is sending me another phone. Stay tuned.
Click to expand...
Click to collapse
Have you considered the fact that the recovery itself is causing your issues? I would give TWRP a try to see if there are differences. TWRP is a must to flash KitKat roms and the version used is critical.
RLGL said:
Have you considered the fact that the recovery itself is causing your issues? I would give TWRP a try to see if there are differences. TWRP is a must to flash KitKat roms and the version used is critical.
Click to expand...
Click to collapse
Nope. I didn't consider that. Because most of my problems were with CM 10.2.1. Which is JB, correct?
That being said, I've tried both CW and TWRP to no avail. After being stuck in 3G for two days across multiple ROMs, I'm convinced the hardware went belly-up.
New SIM?
HTC DNA
LG Optimus G
mdphoenix said:
Nope. I didn't consider that. Because most of my problems were with CM 10.2.1. Which is JB, correct?
That being said, I've tried both CW and TWRP to no avail. After being stuck in 3G for two days across multiple ROMs, I'm convinced the hardware went belly-up.
Click to expand...
Click to collapse
Santod has a process to recover the unit from the conditions you describe. It is fairly simple and doesn't appear to require much time.
I don't have time to search for it at the moment.
RLGL said:
Santod has a process to recover the unit from the conditions you describe. It is fairly simple and doesn't appear to require much time.
I don't have time to search for it at the moment.
Click to expand...
Click to collapse
I did lots of searching before asking. I try to do my due diligence before bothering you all.
The replacement phone did not resolve the problem. The replacement SIM did.
Now on to bigger and better things. Thanks for putting up with me.
And now I can't text without cycling Airplane mode again.
Sent from my HTC6435LVW using Tapatalk
RLGL said:
Santod has a process to recover the unit from the conditions you describe. It is fairly simple and doesn't appear to require much time.
I don't have time to search for it at the moment.
Click to expand...
Click to collapse
Are you certain it was Santod? He's only got 19 posts on this board and I don't see anything directly related to the SMS problem I'm having.
mdphoenix said:
Are you certain it was Santod? He's only got 19 posts on this board and I don't see anything directly related to the SMS problem I'm having.
Click to expand...
Click to collapse
Yes it is on This page
RLGL said:
Yes it is on This page
Click to expand...
Click to collapse
Since my last update, I've received a new DNA, and a new SIM card.
Check out the last few posts here: http://forum.xda-developers.com/showthread.php?p=51465109
This is bizarre. Either I'm doing something wrong, or... I don't know. SMS works on a stock ROM but not on a custom ROM, with a new phone, with a new SIM.
I think you are doing something wrong.
RUU the latest firmware, factory reset, wipe data, cache, and system, install a ROM and DO NOT restore anything.
I think youre not completely wiping and/or are restoring things.