Database Develop

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

Samsung Galaxy S3 GT-i9305 random restarts even in Safe Mode

Hi Guys,
I have this phone for many years, but suddenly the random reboots started approx 2-3 months ago, running originally KitKat 4.4.4 at this time. Before that I was rooted the phone and I supposed it could be something with that. However, flashing back & factory resets didn't help at all, clearing dalvik caches as well. What I tried up to now:
1. Upgraded/Downgraded the bootloader -- no change
2. Tried different recovery modes -- CWM & TWRP(the current one)
3. Different ROMs -- no change, the sudden restarts persist.
(4. Updated the radio -- the signal got quite better)
Three days ago I've upgraded to Lollipop 5.1.1 (the Cyanogenmod 12.1), the same story continued after a while (different applications installed).
There's one thing for sure: flashing the factories always results into a very stable phone at the beginning, installing some more applications leads to the same state -- random and frequent restarts.
I've checked the hardware -- the power button looks ok, it's definitely not the main cause b/c it reboots without touching! The CPU temp & free memory look quite good too.
Now, the current situation is as follows:
- flashed ROM (official one): 2016-03-03 Poland (T-mobile) 4.4.4 I9305XXUFOL2 I9305TPLFOL2 (seems like the most stable till now)
- installed ATK (Advanced Task Killer) -- configured to kill all applications aggressively when the screen goes off.
For me it looks like the ATK helps much, although I don't know the reason. Also, memory checked, I've executed all kind of possible tests up to the phone -- all appears as OK. Also, I don't know if it's related to the issue but I moved all possible apps installed to the SD card. The internal memory has been formatted via TWRP before the last ROM installation... Does anyone have any idea what could be the reason for the sudden restarts? It restarts even in Safe Mode, without any obvious reason and not touching the phone at all. The CPU load at the times of restart is quite low, the temperature as well. I doubt if the RAM is corrupted or maybe the NAND has some bad blocks. Are there any useful utils for tests that could be executed?
PS: I attach some log file, which I gathered once I was running the Cyanogenmod 12.1 (Lollipop). As I stated above the situation is the same when running 4.4.4 and 5.1.1. Sometimes after such a restart, it sticks in a boot-loop (if I boot manually via the GUI in recovery or download mode it will not).
Current versions:
---------------------
Android: 4.4.4
Baseband: I9305XXUFOA1
Kernel: 3.0.31-4282983/[email protected] #1
Build: KTU84P.I9305XXUFOL2
SELinux: Enforcing
Recovery: TWRP
I beg for your help on this! Cheers!

Same problem here...
Hi there
I'm having this same annoying issue with my Samsung GT-I9305. It suddenly restarts without doing absolutely nothing but looking at the screen or scrolling a text or just sending a sms/whatsapp/whatever.... I started trying to restart the phone (nah) turning it off and back on (nah) changing the battery for another one that I have here with me (nah)... After that, I extracted the SD Card and leave the phone only with internal storage (again, nothing happened but restarting randomly). I tried not installing apps such as FB, even Pebble App or just stopped sycronizing my phone with my Pebble Time via Bluetooth, but with the same and well known result: still restarting suddenly. I have noticed that when Google Play detects that there are few apps with a newer version asking to be updated, the phone restarts too! I tried deactivating this option in Google Play, just letting me to decide when and how to upgrade my apps, but It seems that it still detects the app upgrading needs and keep doing it the same way.
About a year ago, I found the same problem with my phone, but in that time it was related to the power button, it seems that it was pressed all the time and the device felt into a rebooting cycle. I check some blogs and I solved the problem cleaning the button with this electronic cleaning spray. I almost drowned my Samsung but I let it dry for a few hours. It worked fine, until now.
My cellphone is still in Android 4.3 (I9305ZHUCNB1) I don't know why I can't upgrade it to a newer version, even when I see that the 4.4 is available for this model. Right now, I'm thinking about change the cellphone and just forget the whole problem. But I'm just exploring again to see if I can find a last solution that tackles this annoying issue.
Did you manage to solve this problem??
Thanks in advance!

Unfortunately not, I had to buy a new phone. I guess the processor or other element suddenly broke, there's no other explanation to me. Also, as you see no any reasonable support in the forum.. Anyway, wish you a good luck with this.

Not so good here too...
Thank you. But unfortunately for me too... Today my phone went black screened suddenly, when booting only got to Samsung GTI9305 logo... I tried to restart through secure mode and the other one you get pressing power plus home plus volume high, and when tried to do a cache cleaning and rebooting it showed some mmcblk failed issues. So I couldn't do so much to revert this situation. I already bought a new phone, not Samsung of course. I have read that some people had the same problem as me just because they let the battery reach a very low level in one opportunity, and something in the internal memory went broke. So it was a great phone, for three years and half, but it's so bad that it fails this way unexpectedly and without any apparent reason...
Yeh... There's no much support here, especially with old flagship cellphones...

fjpp81 said:
Thank you. But unfortunately for me too... Today my phone went black screened suddenly, when booting only got to Samsung GTI9305 logo... I tried to restart through secure mode and the other one you get pressing power plus home plus volume high, and when tried to do a cache cleaning and rebooting it showed some mmcblk failed issues. So I couldn't do so much to revert this situation. I already bought a new phone, not Samsung of course. I have read that some people had the same problem as me just because they let the battery reach a very low level in one opportunity, and something in the internal memory went broke. So it was a great phone, for three years and half, but it's so bad that it fails this way unexpectedly and without any apparent reason...
Yeh... There's no much support here, especially with old flagship cellphones...
Click to expand...
Click to collapse
Sorry for bothering this thread also... I got success by replacing the display!

Need help, anyone encounter this?

So, my Amazon subsidized R1 HD is rooted with systemless Xposed installed. I did take the OTA update last week. It had been working fine for two days. I powered the phone off and placed on the charger, at which point it keeps continuously attempting to boot, just flashing the White Blu screen every 4-5 seconds. No combination of button presses, or holding of power seems to be able to stop it, so can't power the phone down, or get into TWRP. Ideas? It does not have a SIM in it at the moment, or when this occurred if that might matter.
While I have rebooted the phone many times, this may have been the first time that I have completely powered it down since rooting and installing TWRP this weekend. I had not made any changes to anything for a day or so, and it had survived many reboots. The only thing I can think of is that I did freeze the Amazon Offers App in TiBu to see what would happen, however, not sure that is in anyway related since it is not even getting to a point in the startup where it would check.

Disregard the issue, after rebooting every 3 seconds for 7 hours, the battery died and the phone then properly booted on the first attempt. Not sure what happened, but all seems to work.

i dont think your the only one to have this happen to.
http://forum.xda-developers.com/member.php?u=2645880
that one got fixed same way. just letting it die. unfortunately that may take some time on full change.
edited.
oh i didnt realize that was both you.

This is the second reported instance with this behavior: http://forum.xda-developers.com/showpost.php?p=68027804&postcount=926
Wondering if we should start a thread for reports and the circumstances under which it occurs? In my case it occurred when using a 1st Gen Nexus base and a 3rd Party cable...... wondering if the behavior is charger related? Would be interested to hear if it happens to anyone else when using a BLU supplied charger and cable.

Random black screen issues?

Hey guys, I've been having some issues with my RP2 since fresh out of the box. Randomly, my phone screen will not turn on and will stay black. The phone itself isn't shutting down, as when I attempt to turn on the screen, I can feel the haptic feedback from an attempt to unlock via fingerprint.
It's really touch and go, sometimes its good for a day or two, sometimes it'll do this two or three times a day. A hard reset (Pwr+Vol Up) gets it back running again, but it's getting really annoying and interfering heavily with just everyday use.
Anyone else having the same issue? Anything I've read around the web hasn't helped or isn't pertinent. This happens on complete stock and running Arter97's kernel, so I'm left to believe it's a hardware issue (please no) or a ROM issue, i.e. Razer did a crap job.
Any thoughts? Thank you in advance!

Screen issue

Im facing an issue with my device, probably software but i'm not sure.
Sometimes, when i click on each application, device will behave oddly. Display freezes at same position where i click, nothing happens but after a moment is device confused. It starts clicking randomly, f.e i click on Facebook Messanger, it will pop up application, then i click on some message but it start to open other mesaages, doing random calls etc. If i tried get back with back arrow or home button, it get me to the launcher or back to messanger. Then i try restart phone obviously, but restart button does not work, i feel like it register click somewhere else.
Anyone got the same? I did factory reset, update to 10.0 but nothing changed. I've never did any software intervention like unlocking bootloader or flashing any custom rom.
Thanks

Haven't experienced any of these on my mi9 lite, might be hardware issue. Does it happen only when charging? Asking because back when I had the mi5 it behaved like that when I was using it while charging with a particular charger from ali if the phone had a case on.

Those symptoms you mentioned are more akin to a hardware problem. You might want to consider resetting your phone and locking the bootloader. Then you should RMA your device by sending it back. If is still under warranty then you should be able to get it fixed or replaced.