Related
I'm postivie i received two text, from my self, and my friend sitting next to me; They were delayed until i made a phone call. Any fixes? Surely would appreciate it!
Rom - Stock 2.1 Rooted
I'm thinking of going back to Cyanogen 6.1 when this problem is fixed
Thanks!
Are you going through a SMS app, like Handcent, or using the stock messaging program? I had a huge delay in sending/receiving texts when I used those programs. If you are using a non-stock program, try using the stock one to see how it responds first.
Yeah, i am using the stock app, but ill try using handcent and see if it works like that
Sorry, Handcent was the one giving me problems, not the stock app. How is the other data flowing, like browser and what not? Seen any drop in data coverage or anything? Do you have the newest baseband radio?
jlopez512 said:
I'm postivie i received two text, from my self, and my friend sitting next to me; They were delayed until i made a phone call. Any fixes? Surely would appreciate it!
Rom - Stock 2.1 Rooted
I'm thinking of going back to Cyanogen 6.1 when this problem is fixed
Thanks!
Click to expand...
Click to collapse
Do you have a "low space" warning? I know I've had problems receiving mms/texts when I'm low on internal space. Once I cleared up the space (>19MB Free I believe) by uninstalling a bunch of apps I never use, all the texts came in
Just a thought
Well, i got it fixed, went to the sprint store, (unrooted of course) and they fixed it within an hour, they reset the entire phone, not the same reset as Settings>Privacy>Factory Data Reset.
text and phone calls not getting through
my wife and i both got HTC incredible with Verizon service, this been almost two months ago. my phone is completely awesome, hers on the other hand has an issue her phone will stop receiving text, and or phone calls out of the blue. we will be texting back and forth and all the sudden hers just stops getting my text, so i will call her and it will ring on my end, till her voice mail picks up. this has happen few times a day ever since she has had the phone. if she makes a call out or restarts the phone then she will get all the texts, and voice messages at once. this happen with stock phone apps and ones like handcent. it happen when phone was s-on and after i rooted and installed new kernels and all that jazz. i have talk to Verizon and they talk me through reset and few other things but still doing it. guess i am going to have to see about taking it in, unless anyone has any other advise i have not thought of. all of her software versions are same as mine.
Azag Thoth said:
my wife and i both got HTC incredible with Verizon service, this been almost two months ago. my phone is completely awesome, hers on the other hand has an issue her phone will stop receiving text, and or phone calls out of the blue. we will be texting back and forth and all the sudden hers just stops getting my text, so i will call her and it will ring on my end, till her voice mail picks up. this has happen few times a day ever since she has had the phone. if she makes a call out or restarts the phone then she will get all the texts, and voice messages at once. this happen with stock phone apps and ones like handcent. it happen when phone was s-on and after i rooted and installed new kernels and all that jazz. i have talk to Verizon and they talk me through reset and few other things but still doing it. guess i am going to have to see about taking it in, unless anyone has any other advise i have not thought of. all of her software versions are same as mine.
Click to expand...
Click to collapse
You might have better luck asking on the dinc forums.
-----
Sent from my CDMA Hero. I got some hot Gingerbread-on-Hero action here!
not just a dinc issue...!?
yea, i know, i put it here because, it seems like same issue this guy was having and i have been searching around and have found many instances of the same problem on many different android phones.
i am un-rooting it and reinstalling the original software and taking it into Verizon tomorrow to see if they can do anything. should have done it sooner but every time i would try a fix it would seem like it was fixed for a day or so and then back to the same thing.
i will copy it over there just for posterity, and hopefully i can amend it tomorrow evening with the fix and a solved!
Picked up my NC 1.0.1 today. Rooted without issue. After having a Google Talk conversation, I lost access to Marketplace, and all Google Apps? Can't log back in?
Anyone else having similar issues?
P.S. My wallpaper was changed as well ?!?!?!?!?!
p.p.s. My browsing history and favorites are gone too? Please tell me an update or something was just pushed out. I feel like I just wasted a few hours of my life here.
My rooted 1.0.1 nook has problems as well. Gets authorization error and resets data. After restoring through the clockwork recovery, had it up just for 5 minutes before it automatically reset again. Lost all my apps, market access, youtube, etc. Don't know if this issue has been discussed before. May just have to go back to stock.
It appears that something is amiss. I cannot sign back into any Google Services.
Can't establish a reliable data connection to the server
This could be a temporary problem or your phone may not be provisioned for data services. If it continues call Customer Care.
Click to expand...
Click to collapse
Would a simple re-rooting solve the issue?
Same here. Was using everything fine Saturday. Turned on the device and in a few minutes I got an error, something about a problem with the registration and it said it was rebooting. It did and wiped everything of my rooted install except the market. Can't login to google account now.
abexman said:
Same here. Was using everything fine Saturday. Turned on the device and in a few minutes I got an error, something about a problem with the registration and it said it was rebooting. It did and wiped everything of my rooted install except the market. Can't login to google account now.
Click to expand...
Click to collapse
I might add that I got my device it was at 1.0.0 and I rooted then reflashed to stock to upgrade to 1.0.1 and rerooted. Then I noticed after today's unexpected reboot/data wipe (the status screen during the reboot says it was wiping data) it again gave a message that it had just upgraded to 1.0.1 so I initially thought this was an issue with the device thinking the firmware upgrade was not quite done...
Mine quit working as well. Mine is a 1.0.0 that was auto-nootered. Everything was fine and I used it daily. Now it is a brick, nothing I do seems to make it boot. Every once in a while I can get the backlight to come on but nothing else and it just goes off again in a few seconds.
Rather than troubleshoot, I busted an 8 times reboot to go back to stock then re-rooted. Seemed like less headache, panic and stress.
If your NC dosen't boot at all. Try doing a dd of snowfox's boot.img in dev section. See thread for more info. You'll need to boot into NF from SD.
Sent from my HTC Desire using XDA App
scottfish said:
Rather than troubleshoot, I busted an 8 times reboot to go back to stock then re-rooted. Seemed like less headache, panic and stress.
Click to expand...
Click to collapse
I have tried rerooting, and restoring through clockwork...it seems to always revert and bootloop. Although the reroot lasted a week and clockwork restore hasn't lasted 24hrs twice now.
Not sure what to do but My wife is ready to kill me! I'll have to go stock till someone finds a way to bust up this authorization or just wait I read some ROMs are being developed.
Have any of you disabled the otacerts.zip?
If you haven't it may be the problem.
I have and same on my wife's and neither of us have had any issue, and we use them daily.
I hadn't realized I should be doing this. I will try it. I am actually thinking that my first store purchase came w/ an update (my issue seemed to start right after a magazine trial purchase was made).
Thanks.
>DARKMAN< said:
Have any of you disabled the otacerts.zip?
If you haven't it may be the problem.
I have and same on my wife's and neither of us have had any issue, and we use them daily.
Click to expand...
Click to collapse
Thank you, I will try that. All the searching I did was for disable OTA NC and such but actually searching for OTACerts brought out many many threads that were archived on this subject... I can't wait to get home to try it!
I did not rename the ota file.... will give it a go.
Hey there.
I have a stock Samsung Galaxy S4 Active on the AT&T network. Recently, I've been plagued by a number of troubles.
Bit of background:
For a while, I had the most bizarre issue: the screen thought I was touching it when I wasn't, near the bottom-middle of the screen, and would attempt to open/click on anything in that area. Often turning the screen on and off would help, for a little while. I was reaching my wits' end, because that would obviously be very frustrating to someone who uses their phone frequently throughout the day.
I thought maybe it had been new software I had installed, so I did a factory reset. Problem remained. I factory reset with NO backups. Problem remained. I updated to 4.4.2 via OTA. Problem remained...
And then mysteriously went away on its own.
I've been working in tech for a decade now, mainly in PC and server architecture, so I know better than to look a gift horse in the mouth - but I also know better than to think a problem that "mysteriously" goes away is gone for good. So the first part of my question: does anyone know what could have possibly been causing this?
I'm not super phone-savvy. I've rooted and flashed a few phones in the past couple years, but I'm by no means developer-level.
---------------------
Which brings me to my next problem... around the time that this issue went away, another one cropped up. Randomly, my phone will stop sending/receiving texts/calls, and the data connection will not function. This will continue until I turn on airplane mode and turn it off--at that point I receive all my missed texts, and it works again... sometimes for 5 minutes, sometimes for nearly 2 days. It's really frustrating. I've tried factory resets, I've tried restoring default APNs... but I'm at my wit's end with this. Can anyone help?
Thanks!
I should add that, with my last issue, it still shows a data connection in the notification bar - but there is none, or at least, no activity on it. It doesn't simply act as if it's in airplane mode and go "wah no data network" as soon as I try using it--it just simply hangs for ~30 seconds, then times out. Messages don't get received, webpages don't load, calls don't get placed, etc.
I installed that update that upgraded the phone to 4.4.3 and enabled Wi-Fi calling about a week ago. And since then, the SMS app has been incredibly laggy to the point where it is near unusable. I am not exaggerating, it takes literally about 20 seconds from me tapping a letter, for the phone to vibrate that it recognized I touched the screen and display the letter on the screen.
I know that internally the SMS is working fine since I can get replies back on my Pebble before the message I sent that they are replying too even appears on my screen.
Also, this only happens to specific contacts, but always the same ones.
Everything was working perfectly before this update, but directly after installing it this happened. Any ideas?
Cyber Akuma said:
I installed that update that upgraded the phone to 4.4.3 and enabled Wi-Fi calling about a week ago. And since then, the SMS app has been incredibly laggy to the point where it is near unusable. I am not exaggerating, it takes literally about 20 seconds from me tapping a letter, for the phone to vibrate that it recognized I touched the screen and display the letter on the screen.
I know that internally the SMS is working fine since I can get replies back on my Pebble before the message I sent that they are replying too even appears on my screen.
Also, this only happens to specific contacts, but always the same ones.
Everything was working perfectly before this update, but directly after installing it this happened. Any ideas?
Click to expand...
Click to collapse
Backup & do a hard reset will take care of it. I always recommend doing a hard reset after any kinda of big update anyway. I would also do a profile update once the hard reset is complete. There was some issues with connectivity for this update that a profile update should take care of, although it's not going to solve your sms problem.
Sim-X said:
Backup & do a hard reset will take care of it. I always recommend doing a hard reset after any kinda of big update anyway. I would also do a profile update once the hard reset is complete. There was some issues with connectivity for this update that a profile update should take care of, although it's not going to solve your sms problem.
Click to expand...
Click to collapse
Wouldn't restoring the backup bring the problems back though?
Cyber Akuma said:
Wouldn't restoring the backup bring the problems back though?
Click to expand...
Click to collapse
It's possible, doesn't really hurt to try. I usually try and restore as little data as possible and do everything by hand. One thing you can do if you wanna keep your sms, is export it, then import sms only back in after the rest. I have had good luck with it. Certain apps I use titanium backup to restore, but a lot of stuff I do by hand. I have tried HTC's backup on a friends phone, it actually worked better than I thought. Sometimes it's nice to not do a backup (other than like sms & photos) It will clear out the old apps you don't wanna use.
For the last few weeks, my AT&T Note 3 has started randomly rebooting. It can happen when I'm viewing email, when the phone is in my pocket, or even in the middle of the night when it is just sitting recharging. The rebooting is roughly once per day: somedays more than once, other times it can go over 24 hours. The problem seems to have started after I updated to 5.0. I have tried a factory reset, but the problem came back. I called AT&T support and they said that they've had a lot of problems with Samsung devices after the 5..0 roll out, with random rebooting, or the Bluetooth failing, or the WiFi failing. They said that they need to replace the Note 3, but because it is over a year old I must pay $100 for the replacement through Asurion (I have been paying the insurance fee).
Searching on line has not provided much on this problem. Does the AT&T comment make sense? If I need to replace the phone, shouldn't it be for free because the problem was caused by AT&T?
I'd appreciate any comments.
Note that I realize it could be related to an App I use being incompatible with 5.0, but I need to use my phone for work pretty much constantly, so troubleshooting which one (if any) is not practical.
Mine started doing the same thing about a week ago. Till then it was not having any problems with the 5.0 version.
They need to figure out the problem and push out a update. Otherwise it is like they don't care about us, unless we go out every year and buy a new phone !
Problem solved?
After trying a reset and cleaning checking the battery contacts didn't work, I looked for other patterns. It seemed to me that one of the most common times it rebooted was when I checked my email with the K9 email client - something that is always running in the background, and could have caused it to reboot when on charge overnight.
I uninstalled K9 and that didn't help - the phone rebooted after about 9 hours. However, since that reboot it has now gone nearly 48 hours without rebooting. Maybe I was right about K9 and uninstalling it wasn't enough - I should have also manually rebooted the phone.
The phone has been rebooting at random times, sometimes as short as about 5 hours apart and sometimes more than a day apart. It could be that right now I'm at one extreme and it will reboot randomly today. But if it makes it through tomorrow morning without rebooting then K9 was probably the problem.
It has now been over 72 hours since the last reboot, which does suggest that the original problem was the K9 email client, crashing and forcing a reboot on the phone after the Android 5 update.
Problem NOT resolved!
A few minutes ago, roughly 76 hours after the last random reboot, when I thought that the problem was resolved, I heard the reboot tone coming from my phone that was sitting on the table.
So, while removing K9 reduced the frequency of the reboot, it did not solve the underlying problem.
Use Titanium Backup and backup all user apps and data. Factory reset and reflash stock if you want to take the extra step. Use standard Google and Samsung apps for a while. Do not restore accounts or system data automatically. Removing and reconnecting accounts and clear data for an app in app manager are always good quick troubleshooting options. Restore apps as you need them, if you really need them. Favor stability over extraneous features.
.......................................................
Galaxy Note 3 - AT&T (sm-n900a)
Since I removed K9 and rebooted the phone, it has only rebooted randomly once in 5 days: this was at 72 hours, and now it has been up for 65 hours since then. Trying what you suggest would take weeks, given the current frequency of random rebooting. Plus, my phone is used for work constantly - I couldn't get by with just the Samsung and Google apps built into the basic phone image.
For the moment, I will just live with the phone as-is and hope that Samsung issues a new version of 5 soon.
Now at nearly four days since the last crash/reboot, or only one in seven days. At that frequency, it is certainly not worth the effort of trying to track down the secondary cause (it could take months), now that I know that K9 was the main problem.
It has been a while since I started this discussion, with no conclusion. The phone still randomly reboots - only once all of last week, but then it woke me up on a reboot at 4:30 am this morning, and rebooted again while I was checking Facebook at 7 am.
I'm having a rebooting issue as well with my Note 3. It started about a week ago and will do it many times during the day. I have tried wiping the cache partition, doing a factory reset and the other day I downgraded the software from 5.0 to 4.4.2 and rooted it and froze the over the air update from AT&T but still have random rebooting. I have had the reboot issue with and without the SD card installed so I know that is not the issue either. I was thinking it was a software issue so that is why I did all of the stuff listed but now I'm wondering if it could be hardware. I guess I'm just at a loss of what to try know and was hoping someone on here had any suggestions.
I hope that with your additional post that we'll get some answers. One thing: does it happen when sitting idle on charge too, or only when not sitting idle? In the later case, it could be a simple as dirty battery contacts.
jeffp25 said:
I hope that with your additional post that we'll get some answers. One thing: does it happen when sitting idle on charge too, or only when not sitting idle? In the later case, it could be a simple as dirty battery contacts.
Click to expand...
Click to collapse
It happens both when charging and when sitting unplugged. I even tried swapping the battery for a new one and the contacts and also clean
Well, it was an idea. I did the same thing, buying a new OEM battery and hoping it would help. It didn't. But then again, mine often reboots at night (it woke me up at 4 am this morning), so I knew it was unlikely to be a battery issue in my case.
Yeah thanks for the idea but it seems like I'm running out of things to try
I feel the same. The only thing left would be to wipe out the phone and try it with nothing but stock, non-upgrades, apps. But I use the phone for work, and it can go more than a week between reboots (or less than a day), so that isn't practical.
I might just end up mailing my phone into Samsung to be repaired but now that I have it rooted is there any special steps that need to be done to unroot it? I was just going to do a factory reset and let AT&T android 5.0 do it's update if that will kill the root. I'm not worried about warranty since it is no long under warranty.
Maybe use logcat and letting it run and wait for a reboot to happen so you can see what is going on. However the logs could get big and it might not capture what happens right before it reboots.