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

"Check for update not available" error

Here's a new one, at least for me...when I hit my system update check button in about phone, my Bionic is spitting out
"check for update is not available
at this time.
Try again later,"
Has anyone else ever seen this message? It looks like its happening on 4G or wifi, haven't forced 3g and tried yet.
Usually I expect the "Your phone is up to date" message, but this one's new to me.
I'm bone stock, btw...no rooting yet.

I got that a few times yesterday and then tried again 10min later and it ran the check successfully but didn't find an update. When I ran the check for updates this morning it found the update and downloaded/installed successfully.

Well, that's encouraging I suppose...every time I think I really like this phone, something like this pops up...ugh, I want bionic speed and HP, but with my OG droid and droid X's "it just works" reliability.

I think the only reason you're seeing this error is because the servers are under a very heavy load pushing out the updates. I never saw this error before yesterday. But I'm with you on the frustration factor. I'm on my 4th Bionic now, if I continue to get the black screen of death, random reboots, or data connection issues, I'm going to do whatever I can to get a different phone. I've never had to return a phone to Vz before this model, nor I have ever spent so much on a phone. I certainly don't feel like I'm getting what I paid for. How this phone made it thru user testing with these issues blows my mind.

I had been getting that message ever since I replaced my SIM a couple months ago. I figured it wouldnt interfere with me getting any OTA's, but last night I decided to do a factory reset to see if that cleared it up. Low and behold i hit system updates and it said my system was up to date. An hour or so later I did it again and I got the update!

Good to know. I read a thread somewhere, I think it pertained to battery issues, and someone suggested that when you first take the phone out of the box the first thing you should do is a factory reset b/c it helps with overall performance. I don't know if there's any truth to that but that's what I've done on all of my replacement Bionics and I do perceive there to be some improvement. I don't know if it was necessary but I ran the reset after receiving the OTA today too just to rule that out if I have issues going forward - that's the first thing tech support makes you do when you have problems from my experience anyway.

I've been getting that message a lot too when checking for the update. I got the update today and it installed fine. Still have the data drops though. VERY frustrating.
One think I HAVE noticed with this update is that the battery stats are completely reversed. It used to be the display was down in the 3-5% region, as well as the Android OS. Now, those 2 are at the top, and my phone has just been laying on my desk most of the day.

I am not rooted. I've been getting that message since I got the phone in October. It only happens when I am on 3G. I haven't checked it on 4G (don't live near one) and it says "...up to date" when I am on WiFi.
Sent from my DROID BIONIC using xda premium

I am getting frustrated... I have been getting the same error for three days now. I am rooted, but am on 5.5.886 and everything still the same. My partner is still original stock, and he's getting the same errors as well. Perhaps this is a regional thing? Anyone in the DC area get the update rolled out to them?
Additionally, can I just flash the update file that is posted here on the forums to upgrade manually? Or should I just wait?

Works!
I was getting the same "check for updates not available at this time" message, however I rebooted (used Quickboot, battery pull is not necessary). After the reboot went back to "Check for upgrade" and it worked; BUT just like the previous upgrade the process checks your file system and if you removed/altered any bloatware then it will fail and reboot. After the first time, I decided instead to create a folder "bloatware" in the system direction and move all bloatware apps to that folder. So this time around all I had to do was move all the bloatware back to the "app" folder in one shot. Very easy and straight forward (I also wrote down the bloatware apk filenames so I didn't forget that I moved over last time). Tried the update again, installed just fine, and phone is up and running.
AND....root is INTACT!
Btw...I had no idea there was a new update available until my friend who just got a new Bionic said he's having problems rooting on software v5.9.902

[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%.

[Q] Moto X turning off suddenly

Hi all, I need help.
It happened a couple of days ago that overnight, with aero mode on, my not rooted xt1053 didn't wake me up since it just turned off sometimes before the alarm. Even if it had never happened before (just one week before it reached the amazing uptime of 650 hours without any reboot), I decided for a factory reset, since it's very important to me that it works as an alarm too. Yesterday, after the factory reset, it turned off while using whatsapp, all on a sudden. Tonight, it happened again, and I missed the alarm again.
Everytime I turn it on, I have the notification that Google Maps stopped working, or alternatively Google Keep. Battery is always at the same level it was before, I mean, it's still charged with at least 50% battery when this happens. Now I tried to uninstall Google Keep to see if there was something wrong with the last update, but it seems strange to me that it may be the cause.
Does anyone has any idea of what to do?
Any help would be really appreciated.

I have the SAME exact problem. Don't know why...

Julienjarod said:
I have the SAME exact problem. Don't know why...
Click to expand...
Click to collapse
I have the suspect that is Google Keep that now shows also the map on the notes...somehow Keep and Maps have some conflicts maybe? I unistalled Keep and for the moment no sudden death...let's see...

luxpast said:
I have the suspect that is Google Keep that now shows also the map on the notes...somehow Keep and Maps have some conflicts maybe? I unistalled Keep and for the moment no sudden death...let's see...
Click to expand...
Click to collapse
I tried uninstalling most of the apps, but it still happen. I've tried with brazilian soak test, but it still happens.
What should I do to understand the problem? I was thinking about going back to the original rom and try to use it in safe mode...do you think it could help?
With the brazilian lollipop soak test, I do not have any Maps or Keep stopped working once turned back on. Moreover, last times it did happen during the day, while in my hand or on the desk. Twice a day, more or less.
Please, help!

Mine has the same issue. Maps will randomly force close, or just crash back to the home screen. Usually though, Google Maps locks the phone for 30 seconds and then it reboots.
Happens twice a day. It got so bad that I've given up on my Moto X and bought an LG G3. Now I'm sitting on a boot loader unlocked Moto X xt1060 that literally will not last half a day without randomly rebooting.
It does this on any firmware, custom or stock.

bobdamnit said:
Mine has the same issue. Maps will randomly force close, or just crash back to the home screen. Usually though, Google Maps locks the phone for 30 seconds and then it reboots.
Happens twice a day. It got so bad that I've given up on my Moto X and bought an LG G3. Now I'm sitting on a boot loader unlocked Moto X xt1060 that literally will not last half a day without randomly rebooting.
It does this on any firmware, custom or stock.
Click to expand...
Click to collapse
I've bought a Z3 Compact too in the meantime, but I still would like to fix the Moto X since is a beautiful phone otherwise. It's a shame this thing of rebooting or randomly turning off, since I need a reliable phone... It was just two weeks ago that I reached 30 days without turning off and with any rebooting. I can't believe there's nothing I can do to fix it, it doesn't seem an hardware issue...

I'm not so sure my issue isn't a hardware problem. I've never dropped it, but its gotten wet a couple times by accident. (Rain, spilling things on my lap, etc...) I'm notoriously horrible with phones though.
Its always worked afterwords, though. And the reboot problem just recently showed up randomly.
I also had an issue making or receiving a call. I could use data, send MMS and SMS, but it would not make or receive a phone call.

Nexus 6 (rooted, stock rom) won't turn on anymore. Please help

Hello everyone,
I'm experiencing a pretty tough issue mith my beloved (and, so far, flawless) Nexus 6. It had root and a stock rom on it, 6.0.1 (MMB29V). I had unlocked the bootloader and rooted the phone right after buying it more than a year ago and I've been flashing new factory images a couple times (specifically when 6.0.0 and 6.0.1 were released). I usually do everything via Wugfresh's NRT, not because I can't use adb and fastboot, just because it works fine and I'm lazy.
Yesterday, while I was working, I used "Tiny Scanner Pro" to scan a document (legit copy bought on the store, as any other premium app in my phone) and it got stuck for a while, then a popup about Google Play Services came up. I dismissed it and another appeared, and it kept going like that. I was at a client's and I was in a hurry, so I took the pic with my tablet and forced the phone off. Later I turned it on, it seemed to boot regularly, but when the SIM unlock screen appeared and I entered the (right!) PIN, it said that no SIM was found, then the home screen appeared but after a while the screen went black and it started rebooting. Recovery (TWRP) and fastboot were working, so I decided to take it home and re-flash the stock rom: it had been a while since the last time anyway, a new version was out and the OTA update notification was getting annoying. I connected to my PC in recovery mode and transfered my pics and data via adb while I downloaded the latest stock rom (6.0.1 MOB30D). Then I user NRT to flash it (selecting "Soft-bricked/Bootloop" as current status). It appeared to work fine as it went through the usual copying and unpacking. Then, when the phone was supposed to reboot, it just blacked out. I waited a long time, in fact I went out and came back a few hours later, and it was still that way. Now it doesn't power up, no matter how long or hard I press any combination of the three buttons, adb and fastboot do not detect it in any way, of course, and it doesn't seem to charge either (i.e. I left it plugged to its original charger overnight and it still feels dead cold). By the way, the phone warranty shouldn't have expired, but I'm afraid it wouldn't cover this since it should still have the custom recovery and unlocked bootloader in its comatose body.
I've taken a look at similar threads but none of them describes the very same situation. Is there something, anything I can try to do before giving up? I hope somebody can help me. I thank you all very much in advance.
lupus

lupusyon said:
.... I'm afraid it wouldn't cover this since it should still have the custom recovery and unlocked bootloader in its comatose body.
Click to expand...
Click to collapse
Bricked!. When the phone is still under warranty send it for repair. Do not use arguments.
Just: phone will not switch on and does not charge.

Because this is a Nexus device, the custom recovery shouldn't affect your warranty. It is however, a moot point. The device is totally dead, and a call to Motorola is in order.

lupusyon, I had a discussion with Google about an 18-month-old Nexus 5 on which the radio had died - the "no SIM found" error that seems very popular. They asked me what I'd done to try to fix it. I told them that I'd tried several different radios, half a dozen different ROMs (not just Google stock), in short I'd messed around with it over a long period (it had been rooted with custom recovery pretty much since I bought it).
Response? No quibbles. "Here's a refurbished N5. Just send the broken one back in the enclosed pre-addressed pre-paid bag."
Go for it...

dahawthorne said:
lupusyon, I had a discussion with Google about an 18-month-old Nexus 5 on which the radio had died - the "no SIM found" error that seems very popular. They asked me what I'd done to try to fix it. I told them that I'd tried several different radios, half a dozen different ROMs (not just Google stock), in short I'd messed around with it over a long period (it had been rooted with custom recovery pretty much since I bought it).
Response? No quibbles. "Here's a refurbished N5. Just send the broken one back in the enclosed pre-addressed pre-paid bag."
Go for it...
Click to expand...
Click to collapse
I bought it on Amazon Italy Marketplace, I'm not sure if they're supposed to handle the thing or if I should contact Motorola. I'll just check with them first. Thank you everybody for the kind advice, I'll let you know how this turns out. :good:

I confirm what dahawthorne wrote above: it took them about a month but Motorola repaired my Nexus under warranty, no questions asked. It seems they replaced the Mainboard PCB.
Thanks everybody!