Database Develop

everything is Force Closing since yesterday

hey guys, I don't know what's going on with my S7 but yesterday was working fine and out of nowhere everything started to FC! From twitter to "Google Services Framwork", Gmail, browser, tweetdeck, calendar, voice, I can't pretty much use it anymore, I haven't done any new app installations so i don't know what's wrong! is it just me, or anyone else having this problem??
Any help will be much appreciated!
Thanks

That has happened to me 4 or 5 times. It's like half of the device gets erased but the apps are there. Everything force closes. I end up having to erase the device and re-install everything. Reboot into recovery if you can't figure it out and format the system and data. For some reason when i do that, i keep root. Not entirely sure how that happens, but one less step for me. I think root is power and one of the volume buttons.

djdanska said:
That has happened to me 4 or 5 times. It's like half of the device gets erased but the apps are there. Everything force closes. I end up having to erase the device and re-install everything. Reboot into recovery if you can't figure it out and format the system and data. For some reason when i do that, i keep root. Not entirely sure how that happens, but one less step for me. I think root is power and one of the volume buttons.
Click to expand...
Click to collapse
ha! i remember I already did that. After the Update we had, and I exchanged mine for a new one I decided to stay with no root (i don't know why! lol) so I guess I'll reset everything and go back to root I figured at the end I was gonna do that, but I was trying to see if it was just me or there was a fix
thanks man!

ok, so since yesterday I've been trying to factory reset the DS, and when it boots back on, everything stays the same!
I'm a little confused now, if I take a picture and I turn the tablet off, when I turn it back on, the picture disappears. Same thing happens if I move widgets, delete or create new ones on the screen, they go back to as the configuration was on friday night! GV not working, and the last message that shows there, same thing, shows the last one on friday. I don't know what can I do.... should I call dell??

duck tape and dynomite
stupid thing started crashing yesterday FC this and FC that ....cant restore it as i no longer have write access to the internal sd card
1) tried nv flash
2) tried restoring from clockwork
3) tried pushing files through adb
4) tried fastboot ....
if i didnt just dump money into this thing id blow it up ......
any help would be appreciated.......any tips to fix it or kill it completely so i can get another one
actually deleted all of the files on internal sd card and uninstalled every program on the device looked completly stock ....rebooted it and it went back to how it was yesterday ......theres gotta be a reason why other are having the same problem that started on the same day .....maybe dell pushed an OTA update and screwed us ......just a thought cause mine was fine till i went 4g yesterday so my sis could post facebook pics ....not sure but hope we can figure this out

Samething happened to me
Hi, did you ever find a solution? my streak 7 was ran out of battery, before it shut off, the screen started flickering and then it turned off. after it came back on, it looked like it was fine, everything looked normal, but then everything started force closing, haven't found a solution

jz83 said:
Hi, did you ever find a solution? my streak 7 was ran out of battery, before it shut off, the screen started flickering and then it turned off. after it came back on, it looked like it was fine, everything looked normal, but then everything started force closing, haven't found a solution
Click to expand...
Click to collapse
I'm running stock, and I discovered the hard way that you can't let the S7 battery run all the way down. The S7 will not power itself down in time. I had the same issue, and the only way around it was to do a complete factory reset, using the menu button from the main screen. I think the reset is in the "About" section, but I don't have my S7 with me now.
Being used to WM6, which powers the device down at 5%, I was not expecting the device to do this, but there it is.

dell streak 7
im not sure if I am the only one with this issue you but becareful with the streak 7 mine well both of mine wont charge properly and the newest one wont charge at all. i have to send it back to dell for them to fix it. Im not sure what cause this but my only advie is to never use a different charger for it only dell chargers. Im guessing that it messes up the battery callibration and then it gets really hot when charging

The four touch button lights won't go off when phone is turned off!

They just won't. They'll work normally when on and they'll go off after so much time of idling, but when I turn off the phone it buzzes like a complete shutdown and they just won't go off. I think it started when I loaded that leaked 2.3.3 captivate rom from SamFirmware and now it continues after a 2.1 stock downgrade and updating to 2.2 via Kies. I can't find anyone else with this problem.

hmm That's weird... if you pull the battery and replace it do they come back on?

Oh yea, I've been playing around with it and everything to see what I can do. It started happening about the same time my power/sleep button started messing up. It still is messed up, but I don't see how one would effect the other. Like I said, they work normally until I try to turn it off. Then, they don't go off until I pull the battery or boot it back up.

Jmurph3 said:
Oh yea, I've been playing around with it and everything to see what I can do. It started happening about the same time my power/sleep button started messing up. It still is messed up, but I don't see how one would effect the other. Like I said, they work normally until I try to turn it off. Then, they don't go off until I pull the battery or boot it back up.
Click to expand...
Click to collapse
if they dont go off when you turn it off until you pull the battery, it might be safe to assume your phone isnt actually off. Try reflashing whatever ROM you have going on within your cappy.

redkenji said:
if they dont go off when you turn it off until you pull the battery, it might be safe to assume your phone isnt actually off. Try reflashing whatever ROM you have going on within your cappy.
Click to expand...
Click to collapse
It has happened on two different ROMs. The 2.3.3 leak and then again when I flashed back to stock 2.1 and even after I updated to 2.2 via Kies mini.

maybe try calling samsung then. They may be able to address the issue. My friend has a vibrant that he bricked, hard bricked and they fixed it for free so, they might be able to help you out. it might be a hardware issue they can help you out with.

redkenji said:
maybe try calling samsung then. They may be able to address the issue. My friend has a vibrant that he bricked, hard bricked and they fixed it for free so, they might be able to help you out. it might be a hardware issue they can help you out with.
Click to expand...
Click to collapse
Very possible. I won't have a phone for that time, though. Haha....oh how we can't live without our mobile devices...

Att will send you a replacement first, then you send you old one back. If its still under warranty. I just told them I don't have a home phone, and they overnighted the replacement for free.
Sent from my Captivate running Continuum 5.6

Well, it randomly stopped. It shuts down and when it buzzes the backlights won't stay on. Idk what I've done for it to stop. I still have a busted power button, time to send in for a replacement.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App

Phone won't turn on

Hey Everyone,
Just seeing if anyone might have a solution to my problem that I'm facing. I had rooted my phone when the root originally came out, and everything seemed to be working fine. I had been texting on my phone when it suddenly froze, I waited to see if it would come back, but it never did so I pulled the battery.
The phone originally booted to the M logo, but froze, after another battery pull the phone now won't turn on at all. As in it's not responding to the power button press at all. It's not being recognized by a computer, and there doesn't seem like much I can do.
Any suggestions out there? If my phone is bricked and can't even turn on, will a Verizon store know this? How could they?
thanks.

If u froze something like a system app that may have bricked it. Theres something u can flash which was a cracked version of an ota update that should fix it but u may not be able to receive official updates if u do that. Other option is to wait for an official sbf file
Sent from my DROID3 using XDA App

How can I flash something? There doesn't appear to be a way for me to access my phone. I can't get into restore or the bootloader.

What happens when you plug the phone into your charger(using the stock charger and cable)?

Nothing, no light, no anything

I actually haven't tried it in a situation like that so I can't give instructions :/
Sent from my DROID3 using XDA

Just take the phone into Verizon and tell them it has stopped working. You don't have to go into any detail at all.

g3m1n1 said:
Just take the phone into Verizon and tell them it has stopped working. You don't have to go into any detail at all.
Click to expand...
Click to collapse
I think that might be what I do, I can't imagine they would have a way of knowing it's rooted if the phone won't even turn on, charge, or anything.
Thank you, btw.

Try taking out the battery and plugging it in to the wall without it in it. If it starts to boot, let it. Then replace the batter and plug it into the wall again and let it charge up. Happened to my Droid X before and I was able to get it working by doing this.

Tried this, but couldn't get it to work.
Took it to a Verizon store and they said they would send me a new one tomorrow, and then all I do is send mine in afterwards.
Is there a chance that after I send them my phone they could find out I rooted it? I'm worried they would charge me full price for the phone they sent me if they discover it.

Niviac said:
Tried this, but couldn't get it to work.
Took it to a Verizon store and they said they would send me a new one tomorrow, and then all I do is send mine in afterwards.
Is there a chance that after I send them my phone they could find out I rooted it? I'm worried they would charge me full price for the phone they sent me if they discover it.
Click to expand...
Click to collapse
Honestly the Magnuson-Moss act protects you in that VZW has to prove that rooting caused the phone to fail. However in practice you end up having to take them to court which is too costly and time consuming. But to answer your question yes they could pretty easily figure it out.
But to put it differently no one else that I've read about has had a failure like yours. People have bootlooped and such, but no one has just had nothing happen on power-up. It doesn't sound like you did anything other than root, which couldn't possible cause this. Freezing apps and deleting system apps only causes force closes and bootlooping, you had neither.

Random reboots

My phone has been randomly rebooting about once every two days. I'm completely stock, not rooted. In the middle of the night last night while it was plugged in it rebooted about 4 times in a row, so I shut it off then restarted it in the morning. It's been doing fine so far today. I can't figure out how to reliably reproduce the reboots so I don't know how to go about testing whatever is causing it. It doesn't seem to be caused by any actions I perform (it's happened while I'm using the phone as well as while it's completely idle) Any suggestions? I know there's not much useful info to go off of here...
I keep sending the crash reports to HTC but I don't know what to look for in them. Anybody know how to interpret the crash logs?

Had one this morning. Rooted, but no changes.

And it just happened again. Phone was just sitting there with the screen off... I tried to copy and paste the error log but it wouldn't let me select all the text. The only app I have running in the background usually is Twilight. I'm going to try uninstalling that and seeing if it helps. The problem is the reboots happen randomly so I can't really tell if anything I change actually has an effect! Yarggghhh.
EDIT: Managed to get the error log here: http://pastebin.com/Xynv9qMP

Tried rebooting into Safe Mode, then a factory reset. Neither worked so I exchanged the device at a Sprint store. Hope this one works better!
Sent from my 831C using Tapatalk

phsteve said:
Tried rebooting into Safe Mode, then a factory reset. Neither worked so I exchanged the device at a Sprint store. Hope this one works better!
Sent from my 831C using Tapatalk
Click to expand...
Click to collapse
How did it go? I have the same issue on my international version.

Completely fixed it. I don't have insurance but was able to exchange it within Sprint's return period. My new phone works great
Sent from my 831C using Tapatalk

phone turns off by itself

Hi, this happend already to me few times so I decided to put it on here.
Sometimes when I pick up my phone and try to unlock it nothing happens, fingerprint and button all the same it looks like it completely Off. Then i have to press few times a button to actually start it and it's booting. There is huge battery loss after it boot up. See image.
I am in Stock 4.0.2 no root just few standard apps installed. Nothing fancy. This happend already few times to me. I left the phone locked and when I want to unlock its dead. Also it is behaving weirdly, when I turn it off manually I just need to press longer a button and it's turning on, but here I need to press it few times to work.
Does it happen to anyone else?

terragady said:
Hi, this happend already to me few times so I decided to put it on here.
Sometimes when I pick up my phone and try to unlock it nothing happens, fingerprint and button all the same it looks like it completely Off. Then i have to press few times a button to actually start it and it's booting. There is huge battery loss after it boot up. See image.
I am in Stock 4.0.2 no root just few standard apps installed. Nothing fancy. This happend already few times to me. I left the phone locked and when I want to unlock its dead. Also it is behaving weirdly, when I turn it off manually I just need to press longer a button and it's turning on, but here I need to press it few times to work.
Does it happen to anyone else?
Click to expand...
Click to collapse
Honestly, there's not enough information to understand exactly why it's happening. You need to get a logcat in the time before the reboot; unfortunately, logcats get erased during a reboot so it might be a little tricky getting it if the reboot is seemingly random. Someone had posted this as a possible way of getting the log:
"Retrieving the logs is tricky, since the log cache gets erased on reboot. If the phone reboots even while sitting on a charger, try running adb logcat continuously (you will need Android SDK and USB drivers installed and configured on your PC.) When the phone reboots, look at the last several pages in the command prompt window for any errors or abnormalities."
Click to expand...
Click to collapse
Otherwise, it's hard for anyone to help. I'm not much help in actually figuring out the issue, but I know if you can get the log, someone else probably can help.
For more information on logcats: Logcat Tutorial

Yeah I was trying to connect it to PC but nothing, so it is turned off. I will try next time to run command when turning on, maybe there will be something but I do not see it working before it gets erased. I was hoping that anyone else is having this problem so it might be rom related. It is completely random so you can;t guess when it happens.
I had it only few times so it's not super annoying but still it is not normal behavior. In addition it is weird that battery went from 55% to 33%, just phone reboot will not drain that much... I hope there is nothing wrong with the phone itself.

terragady said:
Yeah I was trying to connect it to PC but nothing, so it is turned off. I will try next time to run command when turning on, maybe there will be something but I do not see it working before it gets erased. I was hoping that anyone else is having this problem so it might be rom related. It is completely random so you can;t guess when it happens.
I had it only few times so it's not super annoying but still it is not normal behavior. In addition it is weird that battery went from 55% to 33%, just phone reboot will not drain that much... I hope there is nothing wrong with the phone itself.
Click to expand...
Click to collapse
Check in advanced to see if schedule off is on

Nope it's off

Happened to me to on 4.0.2. Rebooted twice a day.
Solution to me was Qualcomm flash back to stock 3.5.1 and uodate from internal to 3.5.4. OTA 4.0.2.
The theard "how to unbrick".
Not one reboot until now in days.

I think I found a culprit responsible for it. It is Hill Climb 2 game which doesn't close properly sometimes and I think it causes some kind of crash in the system. Is it possible?

terragady said:
I think I found a culprit responsible for it. It is Hill Climb 2 game which doesn't close properly sometimes and I think it causes some kind of crash in the system. Is it possible?
Click to expand...
Click to collapse
It's possible. Not necessarily the reason, but it might be. Either uninstall the app or freeze it using Titanium. Greenify might also work, but that allows the app to start itself up and potentially continue the issue. See if that stops the crashes for a couple of days.

The problem is that it doesn't happen often and only when I quit the game and lock the phone immediately after that. I am not sure if that's a reason though, just guessing because it happens after this last time. I will uninstall this game anyway, it's just time eater