Database Develop

[Fix] Rebooting and Crashing

For those with Droid 3s that love to randomly reboot. and crash/lag
and also crash on camera, here is a fix
1) FACTORY RESET PHONE (Erase all data)
2) When its back up and your signing back in, DO NOT CHECK 'Restore Data' or 'Keep Device Backed up'
3) Open settings later, and ensure they're both unchecked under Privacy
NEVER enable them
4) For safety incase wifi settings were restored:
Go to Wireless and Networks, Wifi Settings, Manage Network Settings, tap first option and itll say 'forget or erase wifi settings' , choose Yes
5) Reboot Phone
*If camera is still not up to your standards, use Camera360 from market.
Should be all fixed up, no more reboots or crashes, and fast.
I guess its a temporary fix until Moto serves an update.
Sucks if you rely on backup to get your apps back, but Titanium Backup is a nice app to backup settings/apps

I have random reboots also, but the strangest thing is that when I shut the phone off I can put it in my pocket or on a table and it will turn itself back on. Was wondering if this would help this as well?

Is it being charged when it turns back on?
Nothing is pressing the power button right
Not sure of your issue would be fixed by this you can try
Sent from my MB860 using XDA Premium App

not being charged when it turns back on,
nothing pressing power button. will try and let u now what happens.

Hey Guys,
I know this thread is ancient, but I couldn't find anything newer on that topic.
I'm having the random reboot issue since a while now and wondered if you could help me piece together what I've got.
I managed to find a way to provoke the reboots and that is by flooding the RAM. I opened up some random apps (doesn't seem to matter which ones, as long as they consume a lot of RAM) and it crashed rather quickly. I also managed to get a Logcat of that, but it seems pretty normal.
I attached the Logcat-Log of the last 15 sec before the crash.
But sometimes there are reboots that happen when I don't have anything intense running.
Also sometimes (often when I am using rather intense apps) the phone gets stuck with the screen turned off and it essentially acts like dead until I do a battery pull. Sometimes when it does that, it just reboots on its own after a minute or two. That could be what Cglocke might have been experiencing.
I am running an XT860 with System version 5.2.476.XT860.BellMobility.en.CA and Android Version 2.3.6
Does anybody have any ideas on that topic?

Try using rom toolbox to increase the memory management to aggressive
Sent from my DROID3 using xda premium

[Q] overall slowing of OS responsiveness over time

Has anyone else noticed that their Moto X doesn't seem as "snappy" as it used to? It feels like I'm waiting a lot longer for the camera to open and take a picture, it takes several seconds to attach a photo to a message using Hangouts, SwiftKey doesn't pop up as quickly, etc. I've been running 4.4 since AT&T pushed it out. I'm considering doing a factory data reset to see if it helps speed things up, but that's a bit of a hassle so I've been holding off. Just wondering if anyone else has noticed this.

Nope. Has never slowed down here.
Sent from my Moto X cellular telephone...

Wipe dalvik and cache and see if that helps.
Sent from my Dev Edition Moto X

lifetechnician said:
Has anyone else noticed that their Moto X doesn't seem as "snappy" as it used to? It feels like I'm waiting a lot longer for the camera to open and take a picture, it takes several seconds to attach a photo to a message using Hangouts, SwiftKey doesn't pop up as quickly, etc. I've been running 4.4 since AT&T pushed it out. I'm considering doing a factory data reset to see if it helps speed things up, but that's a bit of a hassle so I've been holding off. Just wondering if anyone else has noticed this.
Click to expand...
Click to collapse
Wow! I almost made a thread about having this same issue recently. My x keep lagging and home screen scrolling was choppy and opening apps was very choppy also. I did clear cache partition and it has fixed it so far.
Sent from my XT1060 using Tapatalk

Schaweet said:
Wipe dalvik and cache and see if that helps.
Click to expand...
Click to collapse
I reset the cache, will update with results.

I've been using this.
http://forum.xda-developers.com/showthread.php?t=2132878
I think it helps out but not too sure if anyone wants to test it out. Just flash through recovery I have safestrap.

Schaweet said:
Wipe dalvik and cache and see if that helps.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
Forgive the noob question, but can this be done if I'm not rooted? If so how? Thanks for any help.
Sent from my XT1060 using XDA Premium 4 mobile app

Ryano89 said:
Forgive the noob question, but can this be done if I'm not rooted? If so how? Thanks for any help.
Sent from my XT1060 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Good question. I haven't had stock recovery on a device for longer than about 20 seconds so I'm not sure. Maybe someone else can answer that question.
Sent from my Dev Edition Moto X

Schaweet said:
Good question. I haven't had stock recovery on a device for longer than about 20 seconds so I'm not sure. Maybe someone else can answer that question.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
I don't remember where I found these instructions but they work for me.
To wipe the cache partition, follow these steps:
With the phone powered off, press and hold the Volume down key and Power key for 2-3 seconds until the the Boot options screen appears.
Release the keys.
Use the Volume down key to scroll to highlight Recovery.
Press the Volume up key to select.
The phone will display the Motorola logo then the Android recovery screen.
Once the Android recovery screen displays, press and hold the Volume up key for 10-15 seconds.
Quickly tap and release the Power key.
The Android recovery screen will appear.
Scroll down using the Volume down key to highlight wipe cache partition.
Use the Power key to select.
The phone will power-cycle.

Wife's Note4 screen stays on.

Hello and Happy Turkeyday to all. I have an issue with my wife's note. When she gets any notifications they turn the screen on and it doesn't turn off. I feel pretty knowledgeable about the android O.S. in a whole, I have my S5 rooted and running AICP. I just can't figure out why the notifications cause the screen to stay on. Has anyone else had this problem maybe you could help shed some light on my issue. Thanks in advance.

Is the phone rooted?
Sent from my SM-N910T using Xparent Pink Tapatalk 2

No she won't let me root her phone.

Same problem
I have the exact same problem on my Note 4 (N910F).
My phone is rooted and I have had the problem from the start.
I am also running a custom kernel now but the problem persists.

Any ideas on why this is happening anyone? I've got it to not turn the screen on for a notification but now it won't turn off when plugged in.

Turn off the lock screen notifications, or everything you can on the lock screen settings, most likely something is causing the screen to wake lock. My bet is the weather widget.
Sent from my SM-N910T using XDA Free mobile app

I just searched for the same problem on the Galaxy s5 and someone said to download wakelock-detector to see if it's an app.
Will keep you updated if it helps.

Bullet_King1996 said:
I just searched for the same problem on the Galaxy s5 and someone said to download wakelock-detector to see if it's an app.
Will keep you updated if it helps.
Click to expand...
Click to collapse
So a little update, so far, my problem seems to be fixed.
After the app told me that Dsploit was causing a lot of screen-on time, I disabled the app.
Haven't had it happen so far today so I hope this helps you too.

Bullet_King1996 said:
So a little update, so far, my problem seems to be fixed.
After the app told me that Dsploit was causing a lot of screen-on time, I disabled the app.
Haven't had it happen so far today so I hope this helps you too.
Click to expand...
Click to collapse
Can anyone else have other fix? I have new note 4 with rom stock and very few apps (5-8 apps)
the "Wakelock Detector-Save Battery" app requird root this not my phone so I can't root for now.

If you have very few apps installed, uninstall those apps one by one to see which one is potentially keeping the screen on. Otherwise, do a factory reset, clear cache; also ensure power button is sticky and is fully functional.
u1988 said:
Can anyone else have other fix? I have new note 4 with rom stock and very few apps (5-8 apps)
the "Wakelock Detector-Save Battery" app requird root this not my phone so I can't root for now.
Click to expand...
Click to collapse

arjun90 said:
If you have very few apps installed, uninstall those apps one by one to see which one is potentially keeping the screen on. Otherwise, do a factory reset, clear cache; also ensure power button is sticky and is fully functional.
Click to expand...
Click to collapse
Thx, What I did in the end is disble a few stock apps (I add a pic)
And set the Screen time to 30 sec and shut down the deivce got the battery out turn on, set the Screen time to 1 min and shut down...
a few times in the end got it back to the time I want, all of this fore "soft" reset the database of the settings
..now for about a week+ the problems won't show again :highfive:

Boot into recovery and clear cache
or factory reset like everyone said

Great to hear all is well. Please tell me that you're going to root.
u1988 said:
Thx, What I did in the end is disble a few stock apps (I add a pic)
And set the Screen time to 30 sec and shut down the deivce got the battery out turn on, set the Screen time to 1 min and shut down...
a few times in the end got it back to the time I want, all of this fore "soft" reset the database of the settings
..now for about a week+ the problems won't show again :highfive:
Click to expand...
Click to collapse

arjun90 said:
Great to hear all is well. Please tell me that you're going to root.
Click to expand...
Click to collapse
It's not my phone, so for now no need to root .
btort1 said:
Boot into recovery and clear cache
or factory reset like everyone said
Click to expand...
Click to collapse
I gave you Another solution.

Issues with my nexus 6

I brought nexus 6 few weeks back and I am facing below issues. Are these known issues and something to do with settings
1. Apps randomly hangs and doesn't close cleanly
2. Lag in display in caller while dialing through caller history
3. Incoming call doesn't display automatically when in battery saver mode
4. While on speaker at high volume some blur kind of noise
5. At times notifications on lock screen doesn't respond even after double click
6. Overall OS sluggishness at times randomly.

Yes, most of them are common.
Capri72 said:
I brought nexus 6 few weeks back and I am facing below issues. Are these known issues and something to do with settings
1. Apps randomly hangs and doesn't close cleanly
2. Lag in display in caller while dialing through caller history
3. Incoming call doesn't display automatically when in battery saver mode
4. While on speaker at high volume some blur kind of noise
5. At times notifications on lock screen doesn't respond even after double click
6. Overall OS sluggishness at times randomly.
Click to expand...
Click to collapse
Most of these are common gripes, none can be corrected natively, but some can be corrected through different Rom's and such.

so basically all these problens could be fixed by the android 5.1 upgrade right? cause i have most of them issues... freezing apps is the worst.

ripped85 said:
so basically all these problens could be fixed by the android 5.1 upgrade right? cause i have most of them issues... freezing apps is the worst.
Click to expand...
Click to collapse
nobody knows that, since android 5.1 is not released, and nobody knows what is included with it. but most of these issues that are reported here are user types of issues. meaning its your setup that will fix or break these things. like freezing apps you said.. that doesnt happen over here. usually its your setup or types of apps used that will cause that(apps not ready for lollipop).

That opens a big can of worms.
simms22 said:
nobody knows that, since android 5.1 is not released, and nobody knows what is included with it. but most of these issues that are reported here are user types of issues. meaning its your setup that will fix or break these things. like freezing apps you said.. that doesnt happen over here. usually its your setup or types of apps used that will cause that(apps not ready for lollipop).
Click to expand...
Click to collapse
MMV, but the update should make things more definable. What apps a user may have and whether or not they are updated to work on lollipop should not be such a drastic issue, In a perfect world, Google should provide for backward compatibility or come out with a whole new version of their operating system; I.E. Windows 7 as opposed to Windows 8.

I recently put a different ROM in and used open minded Gapps for some idotic reason and now Nexus just reboots to password needed which I don't remember and it won't go into recovery at all so I can't factory reset it.

[email protected] said:
I recently put a different ROM in and used open minded Gapps for some idotic reason and now Nexus just reboots to password needed which I don't remember and it won't go into recovery at all so I can't factory reset it.
Click to expand...
Click to collapse
You should still be able to enter recovery using the key combination:
- power off the phone; can usually be done by pressing the power button a very long time.
- hold volume down and power button to power up. This should get you to the bootloader screen.
- here, select recovery using volume + power keys.
PS: it's better to start a new thread rather than reuse an old one that doesn't exactly match your problem.

runekock said:
You should still be able to enter recovery using the key combination:
- power off the phone; can usually be done by pressing the power button a very long time.
- hold volume down and power button to power up. This should get you to the bootloader screen.
- here, select recovery using volume + power keys.
PS: it's better to start a new thread rather than reuse an old one that doesn't exactly match your problem.
Click to expand...
Click to collapse
Sorry lol had to hook it to laptop and run Nexus toolkit

phone kills scheduled events

I'm having issues with several apps not triggering at specific times/notifications. Tried to whitelist Duolingo and that worked for two days and then it stopped. Podcast addict is doing the same thing. It should update every 4 hours but nothing happens. Tried to whitelist it but didn't work. The developer thinks it is the phone that kills the wake-up trigger/alarm. Anything else that I can try as it is rather annoying that various apps only work if I actually open the.
Running nougat and 4.0.2

Disable Doze Mode from Settings->Developer options. Reboot to wipe caches and check if problem is solved.

TweaknFreak said:
Disable Doze Mode from Settings->Developer options. Reboot to wipe caches and check if problem is solved.
Click to expand...
Click to collapse
I'll test that. Didn't know the reboot did that.

Eggstones said:
I'll test that. Didn't know the reboot did that.
Click to expand...
Click to collapse
What I meant by reboot was to boot into recovery mode and wipe caches.

Sorry not sure how to do that. Just going into memory clearing it from there doesn't do the trick?

Press the POWER+VOLUME DOWN keys simultaneously until the device restarts and oneplus splash screen appears. Then recovery mode will start and language selection menu will appear. Wipe caches from there. Be careful not to wipe anything else. Then restart your device. Most issues albeit small ones get resolved by doing this.

Seems like doze kills the check. If I switch doze off, podcast addict runs the check for new episodes. With it on it doesn't, even if I whitelist the app. It also seems like when it runs the new episode check , the phone kills the app as it showed up under power hungry apps. I'll see if the cache clean dies anything.