Related
I couldn't find it in any search, sorry if I missed it. So, here's my deal:
When composing an e-mail, text message or searching on the internet sometimes I won't be able to long press a key to get to the other keys (like long pressing 'K' to get '?'). It happens across the keyboard and is getting more frequent. If I reboot it will work again or sometimes if I just kill the program it will work. Does that mean it's a software issue or hardware or both? I am also curious if anyone else has passed by this issue and, if so, what you did to fix it. Thanks for any help.
I'm running everything stock. Stock messaging app. Dolphin HD browser. Stock e-mail clients. Phone version 002 with latest update.
orris said:
I couldn't find it in any search, sorry if I missed it. So, here's my deal:
When composing an e-mail, text message or searching on the internet sometimes I won't be able to long press a key to get to the other keys (like long pressing 'K' to get '?'). It happens across the keyboard and is getting more frequent. If I reboot it will work again or sometimes if I just kill the program it will work. Does that mean it's a software issue or hardware or both? I am also curious if anyone else has passed by this issue and, if so, what you did to fix it. Thanks for any help.
I'm running everything stock. Stock messaging app. Dolphin HD browser. Stock e-mail clients. Phone version 002 with latest update.
Click to expand...
Click to collapse
That's not normal at all. I'd take it to Sprint before even bothering to figure it out.
As for the root of the problem, it could be software, hardware, or both. I remember on my HTC Vogue (Touch), I would get screen problems, but, a hard reset would always fix it. So, it could be a variety of things, and even more reason for you to just take your phone in and get it swapped.
TJDuckett said:
That's not normal at all. I'd take it to Sprint before even bothering to figure it out.
As for the root of the problem, it could be software, hardware, or both. I remember on my HTC Vogue (Touch), I would get screen problems, but, a hard reset would always fix it. So, it could be a variety of things, and even more reason for you to just take your phone in and get it swapped.
Click to expand...
Click to collapse
Thanks, I'll try it.
This probably isn't your problem, but you can't long press a key if you hit a key, then slide to the key that you want to long press on, so if you're hitting a key accidentally then sliding to the key you want it won't work. That's just a suggestion
MINE HAS DONE THIS EVER SINCE THE UPDATE, AND I HAVE HEARD OF OTHERS DOING THIS AS WELL. Sometimes it works, other times it wont. Hit or miss.
i've had this since day one. long pressing on links in xscope sometimes took multiple tries.
I called Sprint and they are shipping me a new/referb phone. Didn't think I'd get it for a while but it shipped the next day and I should have it tomorrow. I hope I get a good one and the problem is fixed.
I think i discovered a huge issue with the new firmware. When i have a second line calling me the screen does not wake up allowing me to switch to the second call. In the past, when a second call comes in the proximity sensor would wake the screen and allow me to take or reject the call. Now i cant even see who is calling. Since i use the phone for business, this is a big, big issue. Anyone else experience this?
Can anyone please check this for me please by calling their voicemail and then dialing their own cell # from another phone please. Thanks
you're right. phone does not wake up but you can push the power button wake it up.
I tested.
When the phone beeps to tell me a have another call i take phone away from my head and proximity censor takes a little longer..like 5 sec before screen comes on.
But mine doesn't stay off like yours...tested 5 times
coachmai said:
you're right. phone does not wake up but you can push the power button wake it up.
Click to expand...
Click to collapse
My screen does come on eventually about 5 seconds. Before it used to be instant. Hitting the power button doesn't wake the phone like the other user mentioned. Do u guys think a factory reset will help. I am reluctant to take the plunge cause its such a pain in the neck to reinstall everything.
I have the same issue as well. I tested 3 times and the issue existed every time. I tried to unlock the phone with power button but it wouldn't unlock it (maybe lag?) because after I pressed power button 4 times, THEN it lit up for a moment but by that time, the waiting call already ended.
I'm surprised more people aren't bothered with this serious issue.
Got the same issues, updated via ODIN, argh that's gonna be fun.
Interesting...it would be great if you guys contacted Samsung via email/other method to let them know about the issue. Hopefully they can fix this bug.
ShinyBuddha said:
Interesting...it would be great if you guys contacted Samsung via email/other method to let them know about the issue. Hopefully they can fix this bug.
Click to expand...
Click to collapse
I would love to contact them, just not sure where/how. Even if they do fix it, it will only come with another bug fix OTA or Froyo whichever comes first. Given Samsung's track record, this will probably take a while. To me personally, this is an earth shaterring issue since i use the phone exclusively for business being on multiple lines often. Its so bad for me that if it isnt fixed by the time the new mytouch HD comes out, I will have to dump the vibrant even though i love it so much. Me missing calls far outweighs the "love" for this handset.
Its been a few days now since many of us have gotten the update and I am surprised so few of us have not reported this. Has anyone been able to come up with a temporary fix or a replacement dialer to alleviate the horrible issue??
its been a few days now since many of us have gotten the update and i cant believe how so few people have complained about this. It is so annoying not to see who is calling on the second line .
I just got the firmware today and I'd be willing to go back. I missed three calls today because of it. Now what do I do?
Hello,
Lately I have been unable to send or receive text messages that contain pictures or videos. The error message is always the same "National access coverage not available."
I called Verizon, on Thursday of last week (1-13), and the technician was unable to figure out the problem. He escalated it to the next level and said that someone would be contacting me in a day or 2. Well it's now Wednesday (1-19) of the following week and so far, nothing!
Has anyone else run into this problem? If so, what's the fix? Any help would be appreciated, especially since Verizon has been no help at all!
I'm using a Moto Droid2 ver, 2.3.2 Rooted and OC'd @ 2.25Ghz
Thanks,
Scott
Dial *228 and update your PRL.
silverfang77 said:
Dial *228 and update your PRL.
Click to expand...
Click to collapse
Thanks for the reply.
Unfortunately, it didn't work. I updated it waited the 15 minutes. When it didn't work I rebooted the phone figuring maybe it needed to be refreshed or something, (long time windows tech, reboot fixes everything!) but still nothing. Just that same message.
I get the exact same error when sending or receiving MMS 50 percent of the time with the first initial try... *228 does not fix this.. verizon cannot fix it either...
OK, got tired of waiting for Verizon to call back. On the phone with 2nd tier support now for about the last hour, so far nothing.
Mine started doing that on mms after using juice defender app and I had to do a factory reset to fix it.
OK, got finished with the Verizon tech, who was very helpful, but we still could not resolve the issue.
She removed and reloaded my data from the server, switched me to another IP address and did a few other behind the scenes things but nothing worked. She suggested doing the factory reset, but I'm ready to give up troubleshooting this issue yet. If all else fails, then I guess I will have no other option.
Since sending MM text's in not a huge part of what I use my phone for, I may just wait for the next release of the software and hope that fixes it.
In the mean time I'll just keep playing with settings and searching Google and the message boards in the hope that someone can come up with a fix that doesn't involve having to wipe it.
rtfield said:
Mine started doing that on mms after using juice defender app and I had to do a factory reset to fix it.
Click to expand...
Click to collapse
I used to use that app, but removed it long before this started happening. I wonder if it left behind some orphan files that are somehow in there wreaking havoc?
Since the problem still existed even running the phone in safe mode, I would think that would not be the case, but anythings possible.
my phone does the same thing with same message... if i try again to download message it will usually come through, but if it happens on outgoing message it will never go through
1250x said:
my phone does the same thing with same message... if i try again to download message it will usually come through, but if it happens on outgoing message it will never go through
Click to expand...
Click to collapse
That's the thing. Since so many people are having the same or similar issue, I just find it hard to believe it's not something on Verizon's side or with their software. This many people screwing up their phone's in the exact same way all around the same time just seem a little suspect to me.
Mine happened 6 months ago. Just reset it and see what happens. All your apps with reinstall by themselves.
rtfield said:
Mine happened 6 months ago. Just reset it and see what happens. All your apps with reinstall by themselves.
Click to expand...
Click to collapse
Yeah, I guess I'm going to have to try something. I want to make a nandroid backup first just to be safe and then I'll give it a shot.
Thanks.
This is great!
So, I just finished the factory reset (which DID fix the problem) and was starting to configure all my custom settings when the Verizon tech I spoke with called me back. She said that she had just spoken to Motorola and they said it was a known problem with their phones! They are not sure what it is yet, but they are working on it. In the mean time, the only thing they can suggest is to reset the phone as a work around!
I asked the Verizon tech if there was any kind of documentation about this that she could send me, but of course there isn't. And there's also nothing on the Motorola site about the error either, at least nothing I could find.
While it doesn't make the situation go away, it does make me feel better knowing what the root of the problem is, sort of. Only problem is, there is no guarantee that it won't happen again.
i turn airplane mode on then off... works for me
Im having the same problem. I even reflashed to stock motorola, still does it. I noticed if i hold down on failed pics or tap download a few times it works. The problem seems to be triggering the data on and off from the send button.
Sent from my LogicPD Zoom2 using XDA App
S.Meezy said:
i turn airplane mode on then off... works for me
Click to expand...
Click to collapse
Yes, I had heard that worked for some people, and I did try that but it still didn't work. Even so, that would only be a work around and not really fixing the issue.
V.A.T.Juice said:
Im having the same problem. I even reflashed to stock motorola, still does it. I noticed if i hold down on failed pics or tap download a few times it works. The problem seems to be triggering the data on and off from the send button.
Sent from my LogicPD Zoom2 using XDA App
Click to expand...
Click to collapse
Interesting, since I did the factory rest I haven't had a problem. If it happens again, I'll be sure to check that.
so i'm a new fascinate user and not even 1 month in, i noticed my phone randomly reboots. as days pass, it looks like it's getting a lot more frequent. i also noticed that when i tap or hit my phone little hard, it reboots? is this common? i'm not rooted yet(just waiting for the gingerbread) or done anything to my phone yet. just recently updated to 2.2.1 and installed a sd card but that couldn't be it right? also calls get dropped a lot.
please help
No this not common, exchange it for a new one
Yep...sounds like a hardware problem. Take it back and get a new one
Swyped via Tapatalk
yeah i did a factory reset and didn't install anything. left bare stock and still when i "slap" the phone down to my palm, it reboots.
thanks all
please close this thread
Might be the battery.
Sent from my SCH-I500 using XDA App
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.