Database Develop

Help diagnosing freezes and random reboots

I am hoping someone has dealt with either of the following problems, and come up with a way to effectively diagnose and fix either.
The phone - 1101 build; running AT&T Stock KK4; rooted via kernel swap method (using stock KK4 kernel after swap, i.e., do not have clockwork recovery); some AT&T bloatware frozen with TiBu, otherwise stock with root
Problem #1 - roughly once a day, the phone will freeze when in sleep mode; I have had this happen with both the slide to unlock and Exchange PIN lock screen up; when I hit power to wake the phone, the screen wakes up but is unresponsive and then the screen won't shot off again; live wallpaper is frozen in place, but if the phone was plugged in, the battery icon continues with the animation loop. And if the phone is not plugged in, battery power drops rapidly in this state.
The phone isn't completely dead, because if I connect/disconnect it via USB (set to debug mode) to my laptop, the computer recognizes the phone is connected, but it is dead enough that if I call the phone, it does not recognize the missed call. The only way I can restore the phone is a battery pull. Usually it takes several minutes for the phone to come back after this, acting like it would if I had flushed the dalvik cache or installed an update.zip from recovery.
Problem #2 -also roughly once a day, at random times the screen will wake up momentarily, then clear, and I will hear the AT&T boot up sound, after a short while, the phone will run through the media scanner and any other startup launches, acting as though it had been turned on, but the battery stats show continuous uptime throughout. I have had this happen when using the phone, including when on a phone call (and the call did not drop).
I have seen problem #2 on virtually all of the AT&T GB leaks, and it seems to get more frequent the more apps that are installed. I had not seen problem #1 until recently.
The phone is out of warranty, and owned by my employer. I am not due for a new phone from them until July. I've done more master clear/reflash stock cycles than I care to admit, tried replacing/testing for disk errors the external SD card, etc..., and am afraid of doing that and having the problems come up again.
Any thoughts on how to diagnose either of these problems?

Hmm... I don't really think there is an exact diagnosis for any of these issues. Some phones are just problematic like that. The only thing I can suggest is trying a different ROM or kernel, and that might help your stability.

I have the exact same problems. Hope someone comes up with a fix. The only help I can give you is that when the phone freezes, instead of pulling the battery, you can hold the vol up & power buttons for 10 seconds and the phone will restart. Easier than pulling your phone apart, especially if you have it in a case, like I do.
Sent from my SAMSUNG-SGH-I897 using Tapatalk

korockinout13 said:
Hmm... I don't really think there is an exact diagnosis for any of these issues. Some phones are just problematic like that. The only thing I can suggest is trying a different ROM or kernel, and that might help your stability.
Click to expand...
Click to collapse
So, the way I see it, unfortunately these problems could be a function of:
Bad hardware
Misbehaving app
ROM issue
Kernel issue
I tried pretty much every leaked AT&T GB ROM and had random reboots with all of them. Seems to track with the number of apps installed, but can't prove that. I have not tried any custom ROMs or kernels.
Since this is technically not my phone, I am trying to avoid doing anything that can't really be undone if I need to turn the phone back in at some point. And I need something that can be a daily driver for work calls and Exchange email, and rely heavily on tethering when I am on the road.
Anyone with ideas on what to test, or how to capture enough log information to figure out where the problem is, would be a big help. Otherwise, I am stuck riding this out until July when I can get a new phone from my employer.

Nothing you do can't be undone, it's just a simple Odin flash away.
Be sure to back up your efs folder before flashing too much

studacris said:
Nothing you do can't be undone, it's just a simple Odin flash away.
Be sure to back up your efs folder before flashing too much
Click to expand...
Click to collapse
I've used Odin with the various GB leaks; if I go further afield (heck, performance is dicey already, how many more problems could I have with one of the ICS alphas), is it still a straight shot back to stock KK4, or are there other steps to do first?
And before I go down that road, any suggestions on diagnostics (other than yet again pulling apps off of the Captivate to see if one of them is the culprit...?)

stoobie-doo said:
I've used Odin with the various GB leaks; if I go further afield (heck, performance is dicey already, how many more problems could I have with one of the ICS alphas), is it still a straight shot back to stock KK4, or are there other steps to do first?
And before I go down that road, any suggestions on diagnostics (other than yet again pulling apps off of the Captivate to see if one of them is the culprit...?)
Click to expand...
Click to collapse
You actually might have less problems on ICS. But it all depends. You can always get back to stock with one, bootloader-free, safe flash. Diagnostics wise, there isn't really much you can do besides removing apps. I would only worry about the ones that are constantly running in the background, as they could possibly be screwing with the phone while in sleep. I think it's unlikely that this sort of testing would actually help though. I still say try something different.

stoobie-doo said:
Anyone with ideas on what to test, or how to capture enough log information to figure out where the problem is, would be a big help. Otherwise, I am stuck riding this out until July when I can get a new phone from my employer.
Click to expand...
Click to collapse
I am having the same issues except in my case I have tried to recreate the conditions and check memory and I am close to maxing it out. Part of my problem is that I come from a Palm background and I have found that Android, or at least the Cappy, is not as responsive (I was really spoiled by Cards on my Pre) I was thinking that my Android noobness is causing me to push the phone too hard and locking it up. FWIW, you might want to check memory issues

[Q] Recurring wifi error

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 can't turn on WIFI

I don't know if people still reads Xperia forum but here it goes.
Here's short version of this, if you don't want to go read though whole post. .
1. I remember I sent it to unlocked it before I put this into storage.
2. Charged it, turned it on, wifi and everything else worked.
3. Discharged it, charged it, turn it back on everything worked except wifi. (googled & searched for answer no go)
4. Updated via USB and Sony website and still no wifi.
5. Using MicroSD ran rom posted again everything works except wifi.
What else do you guys suggest to try?
Few days before my trip, I found old unlocked Rogers Xperia X1a sitting in a drawer and decided to bring it with my trip and play around with it. when I free time Since battery was completely discharged, I charged it and turned it on. I started to play around and turned on wifi, used internet briefly and going through my old memories of agonizing pains and fun using this before I moved to state. A guy I used to work with in Canada suggest unlock it before I leave so he took it to place he knew and unlocked it. I used it for day or two after that than I moved back to state and got Droid and off it went to the drawer.
Although it was slow Windows Mobile 6.1 worked as it should with Claro sim that I put on yesterday. It was old and roughly used but I decided to give it a new life and install rom and use it as media player/emergency/travel phone. I left it on the desk to completely discharge the battery again and charged it to full before I give it a new life. And last night I turned it on and I find it wifi not turning on. I've googled and searched this forum and the suggestion of soft and hard resetting and playing around with energy saving didn't work. I thought it was program that needed updated so I went through updating though Sony website and hoping upgrading would solve the issue but again NO WIFI. I followed instruction on http://forum.xda-developers.com/showthread.php?t=1000254 and tried to see if running Android could fix this but nope. It didn't work.
I found stable rom on Xperia x1a very responsive and I can definitely use this as everyday devices when ever I travel (old&cheap=safer) but no wifi would kill me as I had been using prepaid phone and I see data plan in most of place are ridiculously expensive.
What else can I do and try to fix wifi?

BrianXP7 said:
Sound like a hardware issue. Try looking for a solution here: http://forum.xda-developers.com/showthread.php?t=1464914
Click to expand...
Click to collapse
Thanks for reply.
I thought it was hardware issue as well and I don't know how I have missed those valuable manuals and I have looked through that post yesterday too. I have now download the manuals I needed, It said to check the check the antenna connector on mainboard and clean it. Hopefully it's that easy fix.
I'll report back with result.

OMG!!!
After following instruction on youtube I was able to get to behind camera. The plastic in this phone really DOES break really easily! The plastic near stylus holder fell off and I did not even touched that side of the phone. Maybe it was already broken from few times it fell but part of it just feel out.
Anyways.
After opening it up and doing a very careful cleaning I still don't have Wi-Fi. Bluetooth still works just like before but Wi-Fi still won't turn on.
Oh well...

[Q] Xperia T turning off when connected to network.

Help!! My XT has been running fine since I got it last September however since yesterday my device just shuts down when connected to network. Not a restart I actually have to physically turn it back. My device runs fine in airplane mode but as soon as I turn airplane mode off 3 seconds later off.
I am running a locked boot loader with non rooted 141 loaded through PCC so completely stock setup.
Is this looking like a hardware issue possibly or will reloading the stock firmware fix this?
Thanks
Sent from my Transformer TF101 using xda app-developers app

A quick update:
Issue sorted its self out in the evening, Managed to get conected to a network but only with data off, by the morning all was working fine again.
BUT
Later on saturday I had exactly the same cycle of issues again.
Device was fine all day yesterday YAY
However today has seen a return to being dead.
The difference being I didnt drive anywhere yesterday along with this rareity known as "British Summer". We have had some very warm days of recent and I am assuming the shutting down is a fail safe as the device gets too warm.
I guess there is nothing I can do but ride this out. Given we only have this sort of weather for about a week or so a year(if at all).
How do you guys who live in the more consistently warm climates cope with this device which clearly has heat issues?

Issue is getting much worse.
All last night it was out of action worrying as I use it as an alarm so ran it over night in airplane mode.
This morning working fine but now turns off everytime I send a text message.

I had an issue similar to this but it was whenever i connected to a particular WiFi network. For me changing the WiFi channel worked.

ITHORA said:
I had an issue similar to this but it was whenever i connected to a particular WiFi network. For me changing the WiFi channel worked.
Click to expand...
Click to collapse
No issues linked to WiFi seen here just when connecting to network.
issues have only come up since I updated to 141. everyone says this one prevents these issues which I never saw on earlier softwares.
I have done a repair through PCC and will see how that goes now.

Ok, device is not fixed by the repair.
I am no longer having the device randomly shut down completely but the the device is restarting. It has happened 4 times in the last hour.
1- As soon as sent a text.
2- Moving some apps around in the draw
3- Sending another text
4- unlocking phone
Does anyone have any ideas at all what is wrong with my device. Running smoothly for so many months and then now phone is becoming completely unusable.
Not sure if related but issues dont seem to arise when on charge and issues today only started once batter got below 60%.

Fire 7 7th Gen not turning on Wi-Fi or Bluetooth

While trying to install LineageOS, I noticed that while trying to fix issues I was having, so I factory reset, which led to me getting stuck on the Wi-Fi setup with "Turning on Wi-Fi...".
After getting LineageOS installed, I also noticed that Bluetooth was also struggling to turn on, which I find odd.
Some things to note, I'm not too experienced when it comes to modifying electronics, and I believe I knocked off a necessary component that allows the tablet to actually handle the connections, since while I was messing with stuff, a little part from the motherboard fell out, but I'm not sure where from. I also pretty much tore off the entire heat shield while doing stuff, although it really doesn't matter if the tablet breaks since it's a spare that I got for free