Database Develop

(Q) D3 3g data dropout issue.

I'm just curious if anyone else is having an issue with their data dropping out on a stock D3.
Sent from my Incredible 2 HD using Tapatalk

Mine has been fine. What ROM stock are you running? The very first ROM that Verizon released is buggy but doihg an update to 5.6.890 is a good idea.
Sent from my DROID3 using XDA App

I believe she is currently running that.
Sent from my ADR6350 using Tapatalk

Then you need to call Verizon Tech Support and tell them the exact issue from another phone besides the one ailing. A couple simple suggestions: do a *228 options 1 and 2, and make sure it is set to Home Only on roaming. Another possibility is the battery saver data manager is running and making it so it shuts off data during specific times and comes on when the screen is on. Make sure the wireless isn't set to Global but CDMA only.
Sent from my DROID3 using XDA App

We tried all of that. Thanks for the suggestions though. Nothing seems to work though. We just got this phone like a week ago because her other was doing the same thing. The new one did it while I was on the phone activating it lol. She's tired of it and I'm tired of hearing the complaints so I told her to sell it because she wants an iPhone.
Sent from my ADR6350 using Tapatalk

[Q] Texting Issues

Strange situation happened last night/this morning...
Last night I had reflashed GV on a cache/dalvik wipe then DreadGinger. I was texting "jane" just fine then all of a sudden i would not receive any texts from her. She had sent me many and I wouldnt receive them, she could send and receive to others fine and so could I, just had the issue between us two.
1. I wiped cache/dalvik and reflashed GV and still wouldnt receive them (except i got one random one but that was it)
2. So then I redownloaded GV and wiped cache/dalvik and reflashed the new one and all is well.
Just thought inquiring minds would have any guesses on what could have caused this. If you flash a ROM so many times can it corrupt it? Or why it was just between me and her?
Lol Ik this is a lot just thought I would ask for future reference and cuz I'm afraid to flash anything now till ik what could have caused it

I've had the same problem with "Jane" a few times. She's using a stock Revo and I'm on Gvolt 1.3. I can't help with what's causing the issue but it always clears up after a reboot.
Sent from my VS910 4G

Back to not receiving again
Sent from my VS910 4G using XDA App

reboot didnt work, wiped data, and now some issues
got one every now and then, frustrating lol

I had this problem too... its because the revolution is switching to 4g voice and text soon...
Sent from my VS910 4G using xda premium

how many characters are the text messages? is "Jane" with AT&T? this will happen when exchanging long text messages with AT&T people because of the CDMA vs GSM thing....there is a workaround if this is the case....

They were short and she isn't on at&t. The issue is resolved now though! Thinking maybe it was on Verizon's end....surprise surprise lol
Sent from my VS910 4G using XDA App

revo_65 said:
They were short and she isn't on at&t. The issue is resolved now though! Thinking maybe it was on Verizon's end....surprise surprise lol
Sent from my VS910 4G using XDA App
Click to expand...
Click to collapse
Yeah, I couldn't get a text delivered to "Jane" once for a week... Verizon doesn't take kindly to these femanons...
Sent from my Galaxy Nexus using Tapatalk

Can anyone give me Jane's number? I've been lonely these last few nights.
Also, I've experienced similar issues in the upstate SC area.
Sent from my Supercharged, Blitzed LG Revolution using xda premium.

ZV8 issues.

Went to a Verizon store and they said that the reboot issue is still an issue for people. I've had 7 reboots since I updated the day the update came out.
I guess the messaging not working right, is an issue also but I don't have that issue.
Anyone having issues or am I the unlucky one lol??
Sent from my VS910 4G using Tapatalk

indyred99 said:
Went to a Verizon store and they said that the reboot issue is still an issue for people. I've had 7 reboots since I updated the day the update came out.
I guess the messaging not working right, is an issue also but I don't have that issue.
Anyone having issues or am I the unlucky one lol??
Sent from my VS910 4G using Tapatalk
Click to expand...
Click to collapse
I haven't had one issue since the update. This phone has been much more stable.
Sent from my VS910 4G using xda premium

They failed to fix the touchscreen going unresponsive at random. Back on GingerVolt2.. OC'd and loving it!!!!!

drt054 said:
They failed to fix the touchscreen going unresponsive at random. Back on GingerVolt2.. OC'd and loving it!!!!!
Click to expand...
Click to collapse
Haven't had that issue yet.
Sent from my VS910 4G using Tapatalk

Yeah never had the random reboot issue, but I can confirm the frozen screen is still happening on occasion
Sent from my VS910 4G using xda premium

indyred99 said:
Haven't had that issue yet.
Sent from my VS910 4G using Tapatalk
Click to expand...
Click to collapse
Seriously.. I have had this on 2 different revos ever since going to Gingerbread.
Back on GingerVolt2.. OC'd and loving it!!!!!

I only get the unresponsive screen here and there and that's on GV 2.0 gets quite annoying especially playing games.

Random reboots
I am willing to see if I get the random screen freezes vs the random reboots I was getting on my GV install.

Yeah
I had the same issues and called Verizon yesterday to let them trouble shoot the phone and it went south quick. They had me try a few things and eventually done a factory wipe only to get to the language screen and once I selected next to start activation BAM! Reboot so they asked me what phone I wanted! Offered me a Nexus I told them no don't like them, and it was going to be a used one to boot!! So ended up letting them give me a Brand New Razor Maxx it will be here Friday!! Love the Revo only had it 3 months, but time to move on I guess keep up the good work guys you will eventually get these to work but I cant wait that long!!!

Just had my first random reboot, should probably call Verizon before my warranty runs out.
Sent from my VS910 4G using Tapatalk

Were you unrooted at the time when you talked to Verizon xgshortbus?
Sent from my VS910 4G using xda premium

Normally replacements will be sent out overnight. Odd that you have to wait until Friday.
Sent from my VS910 4G using Tapatalk

well, just got off the phone with verizon, couldnt convince them to give me a different phone ... so I'm waiting for my replacement revo. It sucks that someone has to sign for it, now I have to wait till Mon
not too worried about the replacement ... I give it a week before it too starts having problems Then I'll give them hell

drt054 said:
Seriously.. I have had this on 2 different revos ever since going to Gingerbread.
Back on GingerVolt2.. OC'd and loving it!!!!!
Click to expand...
Click to collapse
Do you use Widget Locker?

KaneOfMars said:
well, just got off the phone with verizon, couldnt convince them to give me a different phone ... so I'm waiting for my replacement revo. It sucks that someone has to sign for it, now I have to wait till Mon
not too worried about the replacement ... I give it a week before it too starts having problems Then I'll give them hell
Click to expand...
Click to collapse
This your first replacement?
Sent from my VS910 4G using Tapatalk

indyred99 said:
This your first replacement?
Sent from my VS910 4G using Tapatalk
Click to expand...
Click to collapse
Yep
Sent from my VS910 4G using Tapatalk

majorpay said:
Do you use Widget Locker?
Click to expand...
Click to collapse
no I do not..

KaneOfMars said:
Yep
Sent from my VS910 4G using Tapatalk
Click to expand...
Click to collapse
That's why. Give it a few more times and they'll switch it more than likely. They tried to get me a different phone but they said after multiple replacements they will send a different phone.
Sent from my VS910 4G using Tapatalk

indyred99 said:
That's why. Give it a few more times and they'll switch it more than likely. They tried to get me a different phone but they said after multiple replacements they will send a different phone.
Sent from my VS910 4G using Tapatalk
Click to expand...
Click to collapse
when you call in to verizon did you have it rooted and such? im on zv8 and i am having screen lock almost everytime i open my notification bar done nothing else to it besides root it in zv7 and roll over to zv8 wondering if i should unroot before i call them and hassle them about it

cbrebel said:
when you call in to verizon did you have it rooted and such? im on zv8 and i am having screen lock almost everytime i open my notification bar done nothing else to it besides root it in zv7 and roll over to zv8 wondering if i should unroot before i call them and hassle them about it
Click to expand...
Click to collapse
I did unroot before calling but it didn't matter, I mentioned the random reboots and threw in the unresponsive screen (even though it only happened once) The rep immediately offered to send a replacement. He first asked if I had done the usual troubleshooting (powercycle, factory reset, etc...) and I said yes.
But you would definitely want to unroot it before mailing it back
I only unrooted first due to the new remote access they have ... didn't know how much info they could get with it.

[Q] Call Problems CM10.1.3-RC

Flashed cm10.1 release candidate today. Everything seemed fine, then I discovered I wasn't receiving calls and wasn't able to make calls either. Anybody have any similar issues? Anyone have any suggestions as to what I may have done to cause this or if there are any settings I may need to change? Please help. Thanks in advance.

I literally just had this problem and spent the past 5 hours with useless tech support.
Don't call Sprint tech support, they just end up doing something on their end that makes you lose your texting and data, too. They ****ed me so hard I have to go into a repair center.
I can't even get another phone correctly activated in the meantime to use as a placeholder.
I'm just as lost as you are, too.

Try ##786# menu and reset. Make sure you are in a good signal area, this will do hands free activation and update prl.
Sent from my HTCONE using xda app-developers app

Konfuzion said:
Try ##786# menu and reset. Make sure you are in a good signal area, this will do hands free activation and update prl.
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
The problem with trying that is the phone number and MSID fields are now blank, and going into the other dialer menu ##221542# and setting them that way doesn't stick past the reboot it forces when you try and apply those.

Maybe try following this thread
http://forum.xda-developers.com/showthread.php?p=45055982
Sent from my HTCONE using xda app-developers app

Tried that a couple different times with a couple different tech support reps, each time the phone number and MSID don't stick afterwards.

Sorry I tried, I don't have any other ideas. Hopefully someone else can help.
Sent from my HTCONE using xda app-developers app

My older phone is finally activated (took well over an hour for calls and data to come back to it, by far the longest I've ever seen a phone take). So at least I have a phone again.
Good luck OP, I'm going to visit a Sprint store tomorrow to see what they say. Report back in on whatever it is you try and what you find does/doesn't work.

Did you try set ril.class to HTCCDMAQUALCOMMRIL in the build.prop
Sent from my One using Tapatalk 4

david279 said:
Did you try set ril.class to HTCCDMAQUALCOMMRIL in the build.prop
Sent from my One using Tapatalk 4
Click to expand...
Click to collapse
I couldn't seem to find that line but I'll look for it again after work. What line is it numerically and what exactly does the line say?
Sent from my XT897 using Tapatalk 2

ro.telephony.ril_class
Sent from my One using Tapatalk 4

david279 said:
ro.telephony.ril_class
Sent from my One using Tapatalk 4
Click to expand...
Click to collapse
Thanks, I'll report back in 4-5 hours.
Sent from my XT897 using Tapatalk 2

Yeah, I just read through the entire thing, that line is missing. I'll add it in and see what changes.
Posting again instead of editing for the sake of the bump.

Let me know if this works for you. This is driving me crazy.
Sent from my HTCONE using xda app-developers app

jmlape said:
Let me know if this works for you. This is driving me crazy.
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
It didn't do anything. I'm heading to a Sprint store right now.
Sent from my XT897 using Tapatalk 2

Back from the Sprint store, the rep I had happens to be a flasher like one of us. I explained to him what had happened and he got right to ordering me a new phone after a $50 deductible.
So, OP, we were both SOL. The MSID had gotten corrupted (similar to how in the early days of the Galaxy S3, it had a chance to lose its ESN) and couldn't be re-written. Only thing to do is get a replacement.

MMS compression

My AT&T Moto X is sending MMS pictures that are to large to open. My Galaxy S4 always shows that its automatically decompressing when to large. Why does the Moto X not do this and what is the solution. Thanks in advance.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

Anyone know the answer?? If this thing can't properly send a picture message I may get rid of it.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

Compresses fine for me. Are you using a 3rd party messenger? Stock messaging and hangouts both will resize automatically. If they're not, you've likely altered something or aren't using the native messaging apps.
Sent from my XT1080 using Tapatalk

No, everything is factory set. No third party apps or anything like that. Most pics are sending fine, but some will say "to large" and show a hazard type sign... No idea. Thanks for the input
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

Same thing is happening on mine. I've tried sending pics to an S3 and the recipient gets " The media content was not included due to a picture resolution or message size restriction". I checked the details and the message size is in the 300-400kb range while picture messages I sent with an HTC doubleshot where usually under 100kb. Am I missing a setting? I am also using the stock messaging app, btw
Sent from my XT1053 using xda app-developers app

I set hangouts to be the default messaging app and have successfully sent mms to other Android devices... So there's that.
Sent from my XT1053 using xda app-developers app

mojoffdawal said:
Same thing is happening on mine. I've tried sending pics to an S3 and the recipient gets " The media content was not included due to a picture resolution or message size restriction". I checked the details and the message size is in the 300-400kb range while picture messages I sent with an HTC doubleshot where usually under 100kb. Am I missing a setting? I am also using the stock messaging app, btw
Sent from my XT1053 using xda app-developers app
Click to expand...
Click to collapse
My wife has the same problem with her XT1053 on T-Mobile. Sometimes instead of the picture, the recipient gets the media content size message.
We've tried sending the same image and different times and on or off wifi. Sometimes it works. Sometimes it doesn't. We have not figured out a pattern.
We've also tried both the epc and fast apn and with or without MMS proxy set in the apn settings.
She's coming from an iPhone so anything that doesn't "just work" is a glaring deficiency.

poorgrad said:
My wife has the same problem with her XT1053 on T-Mobile. Sometimes instead of the picture, the recipient gets the media content size message.
We've tried sending the same image and different times and on or off wifi. Sometimes it works. Sometimes it doesn't. We have figured out a pattern.
We've also tried both the epc and fast apn and with or without MMS proxy set in the apn settings.
She's coming from an iPhone so anything that doesn't "just work" is a glaring deficiency.
Click to expand...
Click to collapse
whats the pattern you notice because mine has no pattern. I'm having the same issue, on tmobile using the t-mobile XT 1053. I attached a screenshot of the error message I'm getting.
Its been going on for week with me using AIO and using T-mobile, using 4.4 and 4.4.2. I even got my phone warrantied because of it. Still happening, obviously there is a software bug with the stock messaging app. also, my signal randomly disappears -___- I'm waiting on a call back from a level 3 technician.
Motorola, please take note of the moto x bug!

Try using hangouts. I can send anything. But I'm still on 4.4
MOTO X SLAPPED

I had the same problem with the stock app on my T-Mobile moto x. Switched to 8sms and it works fine.
Sent from my Nexus 7 using xda app-developers app

drago10029 said:
whats the pattern you notice because mine has no pattern. I'm having the same issue, on tmobile using the t-mobile XT 1053. I attached a screenshot of the error message I'm getting.
Its been going on for week with me using AIO and using T-mobile, using 4.4 and 4.4.2. I even got my phone warrantied because of it. Still happening, obviously there is a software bug with the stock messaging app. also, my signal randomly disappears -___- I'm waiting on a call back from a level 3 technician.
Motorola, please take note of the moto x bug!
Click to expand...
Click to collapse
Sorry that was a mis-type. We have NOT figured out a pattern.

poorgrad said:
Sorry that was a mis-type. We have NOT figured out a pattern.
Click to expand...
Click to collapse
ok, thanks for clarifying. I haven't been able to replicate it either. my girlfriend and i have been working on this issue for days lol. Next step is to get a refund. This says too much about Motorola and the state of android. grrrr!!! #fasterupdates

try 8sms.
maybe carrier restriction?

It's not a carrier restriction. Fact is, the MMS apk file does not include the code to compress down the image. I believe this is also happening with the AOSP Messenger as well. I'm not sure why, but I was having this exact same issue on some other ROMs on my RAZR HD. It's my guess that Google removed the auto-compression code from the AOSP messaging app in an effort to get people to use Hangouts.
Sent from my Nexus 7 using Tapatalk

I have same problem when sending it to someone with nexus 5. It's weird.
Sent from my XT1056 using xda app-developers app

I gave up on the stock messaging app and hangouts and use 8sms instead. Pictures are fine but I can only get mms through mobile data, not wifi. I'm on Tmobile so I think this is a limitation of the service... Unless anyone knows a way around this.
Sent from my XT1053 using xda app-developers app

I use the stock MMS.apk and I have never had this issue. I've sent pics to iPhones, GS3/GS4, Nexus 5s, you name it. Never had anyone tell me they couldn't see my images. I'm still on Jellybean though, maybe it's a KitKat thing?
Sent from my Moto X

arcanexvi said:
Compresses fin
e for me. Are you using a 3rd party messenger? Stock messaging and hangouts both will resize automatically. If they're not, you've likely altered something or aren't using the native messaging apps.
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
jshahanii said:
No, everything is factory set. No third party apps or anything like that. Most pics are sending fine, but some will say "to large" and show a hazard type sign... No idea. Thanks for the input
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
[email protected] said:
Try using hangouts. I can send anything. But I'm still on 4.4
MOTO X SLAPPED
Click to expand...
Click to collapse
_MetalHead_ said:
I use the stock MMS.apk and I have never had this issue. I've sent pics to iPhones, GS3/GS4, Nexus 5s, you name it. Never had anyone tell me they couldn't see my images. I'm still on Jellybean though, maybe it's a KitKat thing?
Sent from my Moto X
Click to expand...
Click to collapse
***IF YOU ARE HAVING THE ISSUE PLEASE READ THE FOLLOWING***
So I'm curious as to what carrier you guys are using? Also is the problem sporadic or constant?
HYPOTHESIS: I have a good case that T-mobile's network is to blame, in my situation. I've been using t-mobile with 2 different moto x (I exchanged because the compression issue) I am currently using a t-mobile HTC One which I will be returning since I thought the issue was my moto x. The issue still occurs on T-mobile HTC One.
So I've had MMS messages always send but some arrive and some don't, using The HTC One as well as the moto x, using t-mobile. What's interesting is this:
All messages take long to send
Some say sent (verified by checking the time stamp and also clicking on the view details for the picture) but after asking the recipient they would tell me they never received it.
I tested with friends from other networks (Sprint and AT&T), they've sent me images and I have no problem receiving them
I've sent messages to friends using other carriers (non-tmobile) they had no issues receiving mine but they would take long to send
Doing the t-mobile customer service test ((SENDING A MMS TO MYSELF, SOMETIMES THEY DON'T ARRIVE BUT WHEN THEY DO THEY ALSO TAKES A CONSIDERABLE AMOUNT OF TIME))
My GF and I both have tmobile branded phones on tmobiles network and all the above situations happen to us both. all the ISSUES I mentioned occur when we text one another too.
I've been testing MMS messages for 2-3 weeks texting a T-mobile iPhone 5 and my HTC One (T-mobile) and 2 Moto X (T-mobile) (XT 1053) all phones were running latest software. So this rules out pretty much every variable. We both have good coverage and have not dropped our phones at all.
THEORY: T-mobile has been aggressively bringing in new customers for months now with all the new plans and marketing and whatknot. So I believe that Tmobiles network is either having proxy issues with MMS or simply they are experiencing network congestion with all the new customers. This is similar to the network issues people were experiencing when AT&T got the iPhone for the first time. Things were pretty bad around those time for AT&T customers and a lot of people.
last, This is the hardest evidence I could get so far being that I can't indirectly test each and every carrier lol
I really do hope this helps!

Tmobile user here.
Sent from my XT1053 using xda app-developers app