I've done a search of the forum and haven't seen my exact issue here. Just picked this phone up to replace my HTC. It's the ATT version if that helps. I updated last night to 4.4 NE3, then performed towelroot.
I was on wifi last night and didn't notice, but today I noticed that my data service completely drops when my screen goes off. When I wake the phone, sometimes data starts immediately, and other times it takes a minute or two for data to start up.
Is this a known issue with some kind of power saver? I turned off power saving mode and no change.
I did find this thread, http://forum.xda-developers.com/showthread.php?t=2689218 for the Baseband & IEMI fix, but I'm not sure if that is the same issue.
Anyone else experience this? I was about to odin back to stock and start again but thought I would ask first.
Thanks,
Related
I have a tilt and for some reason the last couple of days it will just turn its self off. It has done it twice while I was in the middle of a call. Any know what could be causing this. ATT stock ROM... Second one already exchanged one with same problem, No Software installed....
Me too! I have the same issue. I tried to reset Tilt (from Setting options) and it did not solve the problem. I am seeking ways to solve this issue before I have to call ATT.
Please Help!!!
this started happening to me about 1 month ago, it's progressively gotten worse (phone turns off after 2min call even with full battery). At first I thought maybe the phone was overheating because immediately turning the phone back on after it shut-off during a call the phone would get half way through booting and then turn off again.
Luckily my phone is under warranty for another couple weeks (cutting it pretty close!) I called att and they think it's a battery problem. they sent me a new one... I just got it today. Going to do some heavy use and see if I can get it to turn off.
keep ya posted.
charged the new battery completely and then ran it all the way down testing it with phone calls / internet surfing / downloads... no crash or power off. looks like the battery was the problem.
Long time lurker, first time poster.
I woke up today to see my captivate screen showing blank screen (active black screen with buttons lighted up) being unresponsive. It was on it's charger from the night.
I pulled the battery to shut it down. It rebooted. I thought nothing about it until I tried to use it about an hour later.
I have had it on stock Froyo, with no root. Never have flashed any other ROM besides updates through kies.
Problems and things I've noticed so far:
No puzzle lock screen. Can't find it under "set screen lock". Only None, Pattern, PIN, Password available.
Home button and search button do not function(they light up like they are pressed, but not action occurs in any apps or home screen).
No data. Usually i'd see edge or 3g, but I have no data connection.
Text messages wiped. None available through "Messages"(though call log shows history of messages).
Keyboard was on stock android rather than swype(since changed back to swype).
Holding power button only shows "Power off" option. Before there was at least Airplane mode.
GPS was on(I hardly ever use it).
Location settings seemed to be default("use wireless networks" was unclicked)
Most other settings/app data seems fine.
About phone info:
Model Number: SAMSUNG-SGH-i897
Firmware version: 2.2
Baseband version: I897UCKB1
Kerner version: 2.6.32.9
Build number: FROYO.UCKB1
Click to expand...
Click to collapse
Other related things:
Day or two before I received a text message from AT&T to download Kies and use Froyo(Don't remember exact wording, lost the text message, but something to the effect it looked like a mass mailing text to update to Froyo using Kies). I was already on Froyo(flashed as soon as I found out it was available few months back).
I also got a text message about downloading their at&t app to manage my minutes and pay my bill(also already had that app).
My Captivate would randomly freeze/unresponsive a few times, but I didn't think much of it.
Google Music app seemed to randomly start playing the audio file i paused(just in my pocket, or once when i put headphones in to make a call).
Searching the forums, haven't found too much related.
One thread suggested using "home switcher", which I have tried(both Froyo and regular versions, though can't press home button for Froyo version). Neither seems to know what my default Home App is, but it only sees TwLaucher(I only have TouchWiz).
Tried installing an alternative launcher(ADW,LauncherPro), still no home/search button.
I'm without my computer for the weekend, so I can't backup my files and reset to factory just yet.
Anyone have any thoughts to fix this or know what may have went wrong?
I might finally make the jump to a Custom ROM if it'll fix this.
Yes, you should either flash a custom rom or do a factory reset. I will say an event similar to this, also involving text messaging, is what made me make the leap to Assonance, and then Serendipity, and I haven't looked back.
Sent from a state of Serendipity
At the least, try a master reset.
You're not alone....
Two Saturdays ago, I woke up, grabbed my phone to see what time it was and my phone was going haywire. It as blinking, flickering and rebooted on its own a couple of times...without me touching it.
When I DID manage to access the phone after a reboot there was no connection. I couldn't call, send/receive texts, nor could I access most of the features (during one of the haywire moments, the phone popped open my "Gallery" folder and started running a slideshow and then shut down. Again, all without me touching it!) There was a distinct blue circle with a slash where the 3G bars used to be on the top right corner of the phone.
I did a factory reset and didn't help. Wiped everything off the phone, but the device was still going nuts.
I got the phone in mid-December and have absolutely pampered that thing. Never dropped, never scratched, never abused. So I was surprised when I took it into the AT&T replacement center that the lady told me that my battery was wet! Not the phone, but the battery. Those two white-that-turn-pink indicators are so close to each other on the phone that I can't see how one gets wet while the other doesn't.
So they give me a new phone. One thing I noticed right away was that my data usage went WAY UP with the new device. To put it in perspective, I used 100 mb of data in 29 days and 64mb IN ONE DAY with my new phone. I thought it may be a one-time fluke, but it's not. I am only 10 days into my new month and am already at 164mb out of 200mb in my plan. I have NEVER used 164 mb in the 6 months previous, let alone in 10 days.
Fun's not over yet. I noticed a lot of crashes and "Force Closes" with the new phone too. I didn't even have any apps downloaded yet and things were still crashing. Last night I pull my phone out to take a picture and...nope. Screen was all kinds of whacked out and it crashed. And still does now every time I open the camera function. I managed to get in camera mode fast enough to do a reset, but didn't work. The screen is fine otherwise. So looks like I'm back to A&T tomorrow for another round.
I'm glad you posted this, cause the same morning all this happened -- literally, within 10 mins of me waking up -- my computer (brand new - 2 days old) went berserk and shut off and my stereo started flipping channels, turning the volume, treble, bass up and down..BY ITSELF without me touching ANYTHING! It was pretty freaky. I wondered if I was struck by lightning the night before.http://media.xda-developers.com/images/smilies/eek.gif
I was finally able to get back home today and do a factory reset. This (somewhat) solved the problem. Everything is mostly back to normal(home button and search button work on home screen, lock screen is there).
Lost a couple of game saves as I had no method to pull a save file(was doing adb pull on some known file locations).
I did run adb logcat before resetting, and home button and search button seemed to trigger something, just not follow through(Search button did work in a card game as a forward button and home button worked in the kies app to exit, just never as a return to home button in apps).
I'll be looking to root and flash a custom ROM, especially root so I can do a proper backup in case anything like this happens again.
I just want to say thank you posting in q&a and doing research before and after your flashing started. Then searched after your problem. You're a new member of a breed that are few and far between. I will hit your thanks when I get on my computer, app doesn't have it. You will go far here.
I complained about this issue originally in the MavRom thread but was advised this isn’t a known issue with the ROM, so after more troubleshooting, here I am. This is the chain of events:
- Bought the Droid 3 unlocked so I could use it on Rogers
- Instantly flashed CM9, lived with the various issues hoping they’d be resolved soon
- They weren’t, so I started looking for a permanent GB rom. Tried MavRom
- Noticed a day or two later the following issue:
Wifi will just randomly encounter an error and turn off. It typically happens without me noticing, and then I’ll be at home and notice I’m on data when I should be on wi-fi. If I try to turn it on using the power widget it will briefly light up as though it’s trying to turn on, but eventually give up. If I try to turn it on through settings, where it normally would say “wifi is on” or “wifi is off”, it just says error. I used to reboot the phone to fix it, but just realized a few weeks ago that I just need to turn airplane mode on and off, then turn wifi back on.
This isn’t the worst thing in the world but it should not happen. There is also no pattern to it, or any apparent triggering event. It can happen half an hour after the last time, or it can go a whole day without happening. My phone is in essentially the same state all night while I am sleeping, so the same thing should happen every time. But sometimes I wake up and the error has occurred, other times it hasn’t.
So as I said, I complained in the MavRom thread, they insisted it wasn’t related to Maverick. So I flashed Eclipse to try it out. Right away I realized that this error was happening in Eclipse too. So, somewhere in all the clearing data and cache and flashing of ROMs, etc, I managed to wreck the wifi in a way that reflashing doesn’t appear to fix.
Realizing this, I tried to go all the way back to stock to see if that would work. I used the .906 to .890 patch (since it’s the only way to go back to .890 or at least mostly), then had to use quick unbrick to fix it when it wouldn’t start up. Everything was fine; it was a stock motobloat Droid 3 again. After a few hours of usage I was pretty convinced that the wifi error was gone.
So I installed Eclipse again. For most of the day everything seemed fine but the same problem reared its ugly head last night just like it used to. It sounds like I need to somehow update the part of the Gingerbread OS specifically related to wifi but I have no idea where to go from here. Has anyone else seen a problem like this before? Any troubleshooting advice?
seventieslord said:
I complained about this issue originally in the MavRom thread but was advised this isn’t a known issue with the ROM, so after more troubleshooting, here I am. This is the chain of events:
- Bought the Droid 3 unlocked so I could use it on Rogers
- Instantly flashed CM9, lived with the various issues hoping they’d be resolved soon
- They weren’t, so I started looking for a permanent GB rom. Tried MavRom
- Noticed a day or two later the following issue:
Wifi will just randomly encounter an error and turn off. It typically happens without me noticing, and then I’ll be at home and notice I’m on data when I should be on wi-fi. If I try to turn it on using the power widget it will briefly light up as though it’s trying to turn on, but eventually give up. If I try to turn it on through settings, where it normally would say “wifi is on” or “wifi is off”, it just says error. I used to reboot the phone to fix it, but just realized a few weeks ago that I just need to turn airplane mode on and off, then turn wifi back on.
This isn’t the worst thing in the world but it should not happen. There is also no pattern to it, or any apparent triggering event. It can happen half an hour after the last time, or it can go a whole day without happening. My phone is in essentially the same state all night while I am sleeping, so the same thing should happen every time. But sometimes I wake up and the error has occurred, other times it hasn’t.
So as I said, I complained in the MavRom thread, they insisted it wasn’t related to Maverick. So I flashed Eclipse to try it out. Right away I realized that this error was happening in Eclipse too. So, somewhere in all the clearing data and cache and flashing of ROMs, etc, I managed to wreck the wifi in a way that reflashing doesn’t appear to fix.
Realizing this, I tried to go all the way back to stock to see if that would work. I used the .906 to .890 patch (since it’s the only way to go back to .890 or at least mostly), then had to use quick unbrick to fix it when it wouldn’t start up. Everything was fine; it was a stock motobloat Droid 3 again. After a few hours of usage I was pretty convinced that the wifi error was gone.
So I installed Eclipse again. For most of the day everything seemed fine but the same problem reared its ugly head last night just like it used to. It sounds like I need to somehow update the part of the Gingerbread OS specifically related to wifi but I have no idea where to go from here. Has anyone else seen a problem like this before? Any troubleshooting advice?
Click to expand...
Click to collapse
I would sbf and stay on stock, if it reappears, bring it to verizon. Im afraid I've never heard of this problem before. Since it happened with 2 separate roms, it seems more like hardware. Otherwise the sbf should have fixed it.
Sent from my XT860 using xda premium
Odd. I know that this was a problem on most ICS roms. Haven't heard of it happening on a GB rom. This happens to me on Gummy 1.2. Same symptopms: wifi kills with no cause and no pattern. I toggle airplane and keep browsing as I only turn on wifi when I am actively using it.
Sent from my DROID3 using xda premium
I'm running 4.3 rooted on ML2, stock ROM. Within the last week I started experiencing a strange problem - after every single phone call made or received, I lose all network connection for about ten seconds. I get the circle with the line through it. Going into settings shows actual connection drop, not just the icon. Then, the connection reappears. I've made no modifications since rooting it in April, nor do I recall removing or freezing any apps any time recently. Powering down and/or removing the battery has done nothing to help.
Any ideas what would cause this? I can't find any threads here, or through a google search, discussing this problem. Any help is appreciated.
Update - same problems when running in safe mode.
Well, this seems to have been a local network problem, as the issue has magically disappeared. Nothing exciting to report.
fullboogie said:
Well, this seems to have been a local network problem, as the issue has magically disappeared. Nothing exciting to report.
Click to expand...
Click to collapse
Remove SIM card and clean?
Yep - did every trick in the book. Even reflashed via Odin to be sure I didn't have a corrupted radio file. It just started working again. I"ve seen the same problem reported in other parts of the country, apparently the result of something AT&T was doing to the network.
I am currently experiencing continuous reboot on my Single Sim Z3+ phone on .253 firmware. It used to be ok but about a week ago I started experiencing this problem as soon as I reboot the phone after setting it up from a fresh install with full wipe. It seems to work normal on earlier builds like 28.0.A.8.266 so only happens on 32.1.A.1.185; 32.2.A.0.224 - .253. I repeat, I have done fresh install with Full wipe several times but problem still exists. Urgent help needed.
Thanks
yawo76 said:
I am currently experiencing continuous reboot on my Single Sim Z3+ phone on .253 firmware. It used to be ok but about a week ago I started experiencing this problem as soon as I reboot the phone after setting it up from a fresh install with full wipe. It seems to work normal on earlier builds like 28.0.A.8.266 so only happens on 32.1.A.1.185; 32.2.A.0.224 - .253. I repeat, I have done fresh install with Full wipe several times but problem still exists. Urgent help needed.
Thanks
Click to expand...
Click to collapse
Hello yawo76,
I have the same device, and I had the same problem, what I did is the next:
With flashtool, download the stock firmware via xperia firm on the same tool (I have successful with E6553_32.2.A.0.253_1295-0156_R6C), after that, in the options, be sure that the MiscTA Exclude options are check, that's the clue. After that complete the setup menu, and try again.
Regards! and sorry for my horrible english.
I do have the same issue. I have Z3+ Dual. Random reboot and/or sleep of death.
What I saw from other posts about hardware issue (no other proof), is about the NFC antenna. But I tried and nothing changed.
I have my phone fresh ROM .253 MM installed and click all the way to home screen and let it sit. Well, nothing happened for many hours 5-6hr. Almost every other hardware functions off. However, once I turned on WIFI, something happened. Blank screen and 3 red LED blinks to reboot. A few moments later at home screen.
Soon, sleep of death (SOD). It is like, when the phone is standby (black screen sleep), when I pushed power button to wake the phone, it won't turn screen on. Like it's hang or something. No choice but to hard reset so that I could turn back on.
Then, I played with WIFI setting and saw a "Keep Wifi On during Sleep". I switched to "never" and tried let it sit again. I found out problem was gone for 10 hours (this is best record now, usually 2-3 hours, reboot happened).
I am still monitoring.
Wish you can try and confirm this.
I ran many tests about this issue. Found out it was the material of board or CPU or power which was not made strong enough. I tried tuning the CPU a little (just like PC of CPU tuning). So that it will not cause SOD, random reboot issue. It was also adjusted such that the battery saves much and prolong the usage of the phone.
With sitting of standby the phone is not running warm. Messages or phone calls will not delay in receiving. Plus, it draws about 2% of juice during standby of 6-8 hours.
Worth the try.