Database Info

[Q] Restarting

So I've had the phone for about 3 weeks now and never had the restarting problem but now it's done it twice in the past 24 hours. Anyone know why it's doing it and how to fix it?

no one???? it's done it more again

hockeybpr25 said:
no one???? it's done it more again
Click to expand...
Click to collapse
need details what rom/kernel are you using? or is it completely stock? whats running when it restarts if anything? check new apps maybe one is being screwy
blazing through on my VZ Droid Charge

Completely stock, haven't rooted my phone yet. The phone every time has just been sitting on my desk or I'll be holding it doing nothing. I always close everything after I use it using the task manager. Let me know if you need any other info, and thanks.

hockeybpr25 said:
Completely stock, haven't rooted my phone yet. The phone every time has just been sitting on my desk or I'll be holding it doing nothing. I always close everything after I use it using the task manager. Let me know if you need any other info, and thanks.
Click to expand...
Click to collapse
hmm if its completely stock I couldn't say why, but maybe someone with more experience than me could chime in... as for a fix, perhaps if you backed everything up first, then a factory reset might do the trick
blazing through on my VZ Droid Charge

hockeybpr25 said:
Completely stock, haven't rooted my phone yet. The phone every time has just been sitting on my desk or I'll be holding it doing nothing. I always close everything after I use it using the task manager. Let me know if you need any other info, and thanks.
Click to expand...
Click to collapse
I'd look at any apps you recently installed. My Fascinate would reboot quite a bit at times for no reason, it could be a Samsung glitch.

What I tell my customers to do is;
-check that there isn't any software updates
-pull the battery and wait 30 sec. I know it is the generic answer but it fixes most problems, it just like a computer if it not working right, restart. (Laptops mainly in pulling the battery.)
-or factory/data reset. It often will fix the issue but there are the few cases where it will not solve the problem. (and you will lose all of your stuff on your phone, contacts are backed up by Google or backup asst.)
-lastly, root it!!! no problems on my GummyCharged, v1.5, 2.3.4 (I don't tell my customer this choice)

Yeah I'm going to root soon. I just keep on reading these forums everyday so I can hopefully prepare for rooting with no issues.
Sent from my SCH-I510 using XDA Premium App

Atrix 2 - Official ICS - running very very slow these days - Help!

Hello Guys!
I own an Atrix 2 and am currently on Official ICS. My phone was working fine all along.
Recently I've noticed that the phone runs extremely slow many times. I have to power off & on many times a day to keep it functioning properly.
It is mostly sluggish these days and I don't understand why. I tried uninstalling recently installed apps but, nothing seems to be helping.
This is my first Android phone and am lost!
Any help would be appreciated.
Thx.

The Sicilian said:
Hello Guys!
I own an Atrix 2 and am currently on Official ICS. My phone was working fine all along.
Recently I've noticed that the phone runs extremely slow many times. I have to power off & on many times a day to keep it functioning properly.
It is mostly sluggish these days and I don't understand why. I tried uninstalling recently installed apps but, nothing seems to be helping.
This is my first Android phone and am lost!
Any help would be appreciated.
Thx.
Click to expand...
Click to collapse
IF you think you phone is giving poor performance on official ICS then why don't you try custom roms . Read/Research on MIUI and I think you will get best performance. BUT READ TILL YOU UNDERSTAND EVERY ABOUT COUSTOM ROMS.

shashankxda said:
IF you think you phone is giving poor performance on official ICS then why don't you try custom roms . Read/Research on MIUI and I think you will get best performance. BUT READ TILL YOU UNDERSTAND EVERY ABOUT COUSTOM ROMS.
Click to expand...
Click to collapse
Hi,
What you are saying may be correct however, the same phone was performing superbly on Official ICS for around 6 months. It's been a few weeks that the phone has become sluggish.
I need to find out the root cause for this and rectify that.

The Sicilian said:
Hi,
What you are saying may be correct however, the same phone was performing superbly on Official ICS for around 6 months. It's been a few weeks that the phone has become sluggish.
I need to find out the root cause for this and rectify that.
Click to expand...
Click to collapse
You could try wipe cache...
Turn off the phone and then press and hold at the same time: the Power button, Vol up and Down Key until the bootloader screen comes up
Volume down to recovery and than hit Volume up to select
When the Android with the the Red Triangle appears push the vol up and down button together
Scroll to clear cache partition and push the power button
Wait for it to clear and than choose reboot once complete by pushing the power button.

It might be some rogue app.. Try uninstalling any app you installed recently.. Worst case, backup all apps and data, try a factory reset.. After that, restore only the apps you really need.. One by one when you get time and find out what was causing the problem..
Sent from my MB865 using Tapatalk 2

Try downloading a Cache Cleaner like https://play.google.com/store/apps/details?id=com.jrummy.cache.cleaner. You could also make a titanium backup of all your apps and do a factory reset.

You might also try and do a FXZ and start over. It seems odd, sometimes that fixes all of the little oddities that pop up including slowness that shows up out of nowhere.

I faced the same problem a month ago. Opening Messages, Settings, EVEN PICKING CALLS, took 7-15 secs.
Turned out it was Android OS/ the Kernel. Whenever the WiFi status changed and some other reasons, the Android OS seemed to take 100% CPU usage for about 1-3 min. Also sometimes I had other processes such as kworker2, kworker3 and others. It took me many apps such as Watchdog, Systempanel, etc to find it out.
Even still I got tired and did a Factory Reset, Rooted it and installed Another ROM. Now its Working fine.
My suggestion would be a Factory Reset (Dont forget Backup if you need to). :good:

Tried the clear Cache Thing as well as uninstalled most of the apps which I never use. Phone started functioning good for some time.
But, now again the same thing.
Thinking about FXZ now. What is FXZ and how do you do it?
Factory reset I can consider but, does it really help?
I notice that the sluggishness starts when WIFI is on and the phone is connected to my home WIFI.

Redicus said:
I faced the same problem a month ago. Opening Messages, Settings, EVEN PICKING CALLS, took 7-15 secs.
Turned out it was Android OS/ the Kernel. Whenever the WiFi status changed and some other reasons, the Android OS seemed to take 100% CPU usage for about 1-3 min. Also sometimes I had other processes such as kworker2, kworker3 and others. It took me many apps such as Watchdog, Systempanel, etc to find it out.
Even still I got tired and did a Factory Reset, Rooted it and installed Another ROM. Now its Working fine.
My suggestion would be a Factory Reset (Dont forget Backup if you need to). :good:
Click to expand...
Click to collapse
Out of curiosity - which rom are you now using? Do all features of the phone work?

The Sicilian said:
Tried the clear Cache Thing as well as uninstalled most of the apps which I never use. Phone started functioning good for some time.
But, now again the same thing.
Thinking about FXZ now. What is FXZ and how do you do it?
Factory reset I can consider but, does it really help?
I notice that the sluggishness starts when WIFI is on and the phone is connected to my home WIFI.
Click to expand...
Click to collapse
Go to your wireless settings and "Forget" the home wifi connection. Reboot your router and phone, then sign back in to your WIFI.
If you are thinking about FXZ, then you might as well try the FDR first.
Start here and read and read again:
http://forum.xda-developers.com/showthread.php?p=20389449
If you decide to go the FXZ route, please ask and confirm which firmware to use with your Atrix2. Many BRICKED their phones flashing the WRONG FXZ!
Sent from my MB865

The Sicilian said:
Out of curiosity - which rom are you now using? Do all features of the phone work?
Click to expand...
Click to collapse
Presently on Numa 3.0. Now bored and changing it.
Everything works. There are few FC now and then.

Redicus said:
Presently on Numa 3.0. Now bored and changing it.
Everything works. There are few FC now and then.
Click to expand...
Click to collapse
I think you should try MIUI
http://forum.xda-developers.com/showthread.php?t=2093882
Its the best rom i think and you will be very happy while using it.
I am using it from last 3-4 months.

shashankxda said:
I think you should try MIUI
http://forum.xda-developers.com/showthread.php?t=2093882
Its the best rom i think and you will be very happy while using it.
I am using it from last 3-4 months.
Click to expand...
Click to collapse
Using Pacman since 2 weeks, but there is too much UI Tearing.
Thanks for the suggestion. Installing Miui now.

Redicus said:
Using Pacman since 2 weeks, but there is too much UI Tearing.
Thanks for the suggestion. Installing Miui now.
Click to expand...
Click to collapse
after you have installed
set your language english (united states)
other wise you will have FC issue
and read all MIUI threath

shashankxda said:
after you have installed
set your language english (united states)
other wise you will have FC issue
and read all MIUI threath
Click to expand...
Click to collapse
Ok, thanks :good:

slow atrix2 - email trash folder
I was having the same issue - tried wiping the cache (both via the system and with various cache wiping apps). Eventually I would get a slow atrix2 again. I noticed that the trash folder for my pop3 email accounts did not clean itself up, so I did a select all and deleted the messages from the trash folder. This was thousands of trash emails. Three days later and my atrix2 is still snappy. I'm hopeful that this was the issue.
jhelion

{Q}to follow the cm 10.2 updates

Hi,
I m very interested in install the official 10.2 CyanogenMod based in android 4.3, but is in Nightly phase, i am wondering how much time can take to reach a more stable version, and if is posible to follow the changes, issues and fixes in the daily releases.
I hope someone can give me orientation, thx in advance.

Of course you can. Head over to the thread Nardholio started in the Development section.
http://forum.xda-developers.com/showthread.php?t=2405310
The first post has links to: the official CM site and to the Apex Github. The CM site has a changelog for nightlies. On the Apex Github, they maintain a list of known issues.
It's all there.
I caution you on expectations here. Android 4.4 was just announced with a very unfortunate name. I think Jelly Bean 4.3 has about 60 days to live. It would be silly to expect 10.2 to be stable by then. After 4.4 hits Nexus devices, I bet the Apex guys will shift their focus to 4.4 and we will repeat some of this process...

NavarroCol said:
Hi,
I m very interested in install the official 10.2 CyanogenMod based in android 4.3, but is in Nightly phase, i am wondering how much time can take to reach a more stable version, and if is posible to follow the changes, issues and fixes in the daily releases.
I hope someone can give me orientation, thx in advance.
Click to expand...
Click to collapse
it will probably never happen.
android 4.4 is just around the corner, so i guess the focus will be swapped on that, as it was for 4.3 and 4.2 before

CyanogenMod will do a final "release" build when 10.2 is EOL which will be the most stable we can make it. We also have a last 10.1 build we consider mostly stable, although it is unofficial. Right now 10.2 does have some stability issues, but most of these will be worked out (there are some bugs in our firmware we will not be able to fix until/if Samsung updates the firmware)

Nardholio said:
Right now 10.2 does have some stability issues, but most of these will be worked out (there are some bugs in our firmware we will not be able to fix until/if Samsung updates the firmware)
Click to expand...
Click to collapse
I have random freezes/reboots all the time on the official nightlies -- even the ones people claim are stable. The lockscreen freezes quite often too. Are these known issues or am I just a lucky one? I am running CWM and followed the installation instructions on the Cyanogenmod wiki.
I just installed alogerec and hopefully something will show up to troubleshoot my issue.

Problem with 10.2 nightly as well
I have a problem with the 10.2 nightlies I have tried (all from this week) that I emailed Narholio as he requested.
But since I am a n00b and cannot post to development threads yet I could not post details there. I have not done extensive testing because the screen stays black even though the buttons light up when I try to unlock the phone. I can usually get it to display by pressing the lock button again to lock it, then pressing it again to unlock it right away. This also seems to happen only after the phone has been locked for greater than 20 seconds. If the screen timeout happens, or if press the lock button to lock it, the display almost always works if I unlock it again before 20 seconds is up.
I have not noticed any reboots or other problems, but have not used it extensively because of the black screen problem.

Try http://ls.infernix.net/jenkins/job/apexq-staging/ build 336
Sent from my SGH-T699 using XDA Premium 4 mobile app

I flashed build 336 last night and still have my phone lock up when trying to unlock it. This doesn't happen every time but when it does it either shows the back and menu buttons illuminated with a black screen or an unresponsive lock screen. In either case it will eventually reboot.
Sent from my SGH-T699 using xda app-developers app

Same problem
Nardholio said:
Try build 336
Sent from my SGH-T699 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I also still have the same problem with 336 you linked. I'm running it right now and posting this using it. I have had no reboots or other problems yet, but the black screen while trying to unlock it still plagues an otherwise really great experience. I love the speed and feel of it

I've seen that problem w/ the freezing while trying to unlock when the phone is OOM. If you can actually get it to unlock after that, check your apps memory usage.

Good idea
DOMF said:
I've seen that problem w/ the freezing while trying to unlock when the phone is OOM. If you can actually get it to unlock after that, check your apps memory usage.
Click to expand...
Click to collapse
Thanks for the suggestion. Checking memory is a good idea, although I really don't have any apps at all installed. Didn't even install gapps when I flashed this time.
Is there a preferred way to check for free memory? Terminal command?

computerinfo21 said:
I also still have the same problem with 336 you linked. I'm running it right now and posting this using it. I have had no reboots or other problems yet, but the black screen while trying to unlock it still plagues an otherwise really great experience. I love the speed and feel of it
Click to expand...
Click to collapse
Have you tried a clean install? Wipe system,data,cache then install I have not had wake-lock since early 10.1

computerinfo21 said:
Thanks for the suggestion. Checking memory is a good idea, although I really don't have any apps at all installed. Didn't even install gapps when I flashed this time.
Is there a preferred way to check for free memory? Terminal command?
Click to expand...
Click to collapse
Personally, I always forget to close browser tabs and OOM that way. Check in Settings -> Apps -> Running

Look at the apps you use as well.
When Android was introduced, they rolled it out with a set of guidelines called the application life cycle.
In the document, Google specified how to develop applications and what was available. One option for devs that is powerful is running a thread as a service. It was a feature that was supposed to be used sparingly... (A service is a program that runs all the time--unless the kernel panics and shuts down everything.)
Unfortunately, developers know that Google isn't going to do anything to push them to make quality software. The market is supposed to sort it out.
In many cases, this is not working. People are taking advantage of the lack of QA.
Bottom line: App devs are building software that leaves services running in the background all the time--for no good reason, whatsoever. Many of these services are just there to slurp up your data and send it to their servers so they can sell it.
Holding the back button to fix it? That rarely works. The devs have intentionally built their memory wasting crapware to restart the service if it gets shut down.

Plenty of free memory
croogrog said:
Have you tried a clean install? Wipe system,data,cache then install I have not had wake-lock since early 10.1
Click to expand...
Click to collapse
Yep, did wipe each time I tried multiple recent nightly versions which all do the same thing. The only one I've tried that works correctly is the 20130309 version.
DOMF said:
Personally, I always forget to close browser tabs and OOM that way. Check in Settings -> Apps -> Running
Click to expand...
Click to collapse
I generally keep a tab open to this Relay forum so I can watch what's happening, but not many tabs. Also happens immediately after flashing, without even running any apps, much less installing any.
orange808 said:
Look at the apps you use as well.
When Android was introduced, they rolled it out with a set of guidelines called the application life cycle.
In the document, Google specified how to develop applications and what was available. One option for devs that is powerful is running a thread as a service. It was a feature that was supposed to be used sparingly... (A service is a program that runs all the time--unless the kernel panics and shuts down everything.)
Unfortunately, developers know that Google isn't going to do anything to push them to make quality software. The market is supposed to sort it out.
In many cases, this is not working. People are taking advantage of the lack of QA.
Bottom line: App devs are building software that leaves services running in the background all the time--for no good reason, whatsoever. Many of these services are just there to slurp up your data and send it to their servers so they can sell it.
Holding the back button to fix it? That rarely works. The devs have intentionally built their memory wasting crapware to restart the service if it gets shut down.
Click to expand...
Click to collapse
I really haven't installed any. And when testing different nightlies I just flashed and it happens right away, didn't install a thing on them.
I decided to stay on a version for a while, so have had 20130920 since Friday, and I've used it long enough to know it is consistent. I have found another way to make it happen: incoming phone calls. When phone wakes that way it almost always happens as well. Today it finally showed the screen when I received a call, but 3 or 4 other calls the screen has just been black so I can't tell who's calling.
I discovered another thing since using this ROM for 6 days. Sometimes I get lines/bars/tearing on screen that won't go away until I lock and unlock the phone again.
I have some other phones that are broken, if I can fix one of them I might consider sending this one to a dev to temporarily play with since it seems to be the perfect test case for this problem. The screen is cracked (I got it used in this condition), which I would normally suspect to be the cause of the problem, however since it does not have either problem with stock ICS, stock JB, or the 20130309 CM I'm pretty sure it's related to something in CM10.2. Just new enough to Android I'm not sure how to track it down.
Thank you all for your help!

I have one of these "rev0 cpu" phones and just recently went back to the stock firmware (ugh) because of the lockscreen wakeup lockups. I have gone 3 days so far with no issues. Until this issue is troubleshot, this is an option for anybody who needs stability with one of these phones. I miss CM very much though.
Sent from my SGH-T699 using xda app-developers app

I also have a rev0 cpu phone, and I had a few lockup/reboots since I finally dove in last Monday (9/30) with Staging build 341. However, without me changing anything (still on the same build), they seem to have stopped. Last one I got was 10/2.
Edit: until just now. *facepalm*
TheMaskedMan said:
I have one of these "rev0 cpu" phones and just recently went back to the stock firmware (ugh) because of the lockscreen wakeup lockups. I have gone 3 days so far with no issues. Until this issue is troubleshot, this is an option for anybody who needs stability with one of these phones. I miss CM very much though.
Sent from my SGH-T699 using xda app-developers app
Click to expand...
Click to collapse

I got sick of stock so I tried CM again. After flashing the 10.2-20131014-NIGHTLY-apexqtmo nightly I have not had one reboot or lockup in days. YMMV
Edit: Still haven't had a lockup on wake or reboot.
TheMaskedMan said:
I have one of these "rev0 cpu" phones and just recently went back to the stock firmware (ugh) because of the lockscreen wakeup lockups. I have gone 3 days so far with no issues. Until this issue is troubleshot, this is an option for anybody who needs stability with one of these phones. I miss CM very much though.
Sent from my SGH-T699 using xda app-developers app
Click to expand...
Click to collapse

Hmm... I'll have to try again
Hmm... Sounds like I need to try again then. I tried one released after that and still had issues, but I will try to make some time later to try it. It is fantastic other than that problem.

newer nightlies
Anyone else having issues with the newer nightlies? I have been flashing one a week for a while now and I'm coming from the 14th. tried flashing the 21,22,and 23 all of them are giving me a boot loop at the samsung screen. I have dirty flashed, cleared cache and dalvik, updated recovery. none of them are working for me. Am I missing something? they don't work so i reflash the 14th and everything is good again.
tried in
CWM 6.0.3.7
CWM 6.0.3.8
CWM Touch 6.0.3.8
all with the same errors any help would be appreciated

[Q] Phone booting on it's own Fastboot Overnight

This has been a pain in the butt because I've missed morning alarms just to find our my phone is sitting in the bright white screen of derp. This time I need to know, is this an issue for people in general or could this be a ROM issue?
HTC M8 used the $25 unlocking tool and slapped CM 12.1 on this beast. My advanced reboot menu is OFF in developer options. There is no fastboot or whatever from the stock ROM as far as I can tell. Nothing is pressing on the screen as its just face up on the ground. What can I do, what should I try?
EDIT (8/28/15): After trying a sense based rom the issue went away. Just followed the advice given below

Gevork Gevorkyan said:
This has been a pain in the butt because I've missed morning alarms just to find our my phone is sitting in the bright white screen of derp. This time I need to know, is this an issue for people in general or could this be a ROM issue?
HTC M8 used the $25 unlocking tool and slapped CM 12.1 on this beast. My advanced reboot menu is OFF in developer options. There is no fastboot or whatever from the stock ROM as far as I can tell. Nothing is pressing on the screen as its just face up on the ground. What can I do, what should I try?
Click to expand...
Click to collapse
Does this happen every night?
If it occurs often.. I would honestly just try flashing a Sense ROM for a few days and see what happens. At least you will know in a few days instead of pulling your hair out.
If it still reboots in Sense, probably a hardware problem
If it doesn't reboot anymore, probably a software glitch in CM

So after wondering "maybe the USB cable plugged into my wall charger causes it to somehow go to fastboot mode"... I just had a reboot at work. Had a youtube video open, I hit pause and turned off the screen, and slid the phone into my pocket. No sound, no vib no indications, 5 minutes later I check and find out that its in fastboot mode. So its not from the USB.
I'll try to install a Sense 7 ROM and see how that goes. Very frustrating.
The only other issue I have is GPS not updating quickly enough, it only catches my location approximately and only if WiFi is enabled even if its not connected...

I've only had issues with a bad boot.img, but i couldn't boot the ROM at all. I would try a different ROM & see if that is the issue
---------- Post added at 09:50 PM ---------- Previous post was at 09:49 PM ----------
What ROM are you on? Just plan CM

Same issue here, running Candy ROM. Never see this before, it's almost made me miss my alarms.
Gevork Gevorkyan said:
So after wondering "maybe the USB cable plugged into my wall charger causes it to somehow go to fastboot mode"... I just had a reboot at work. Had a youtube video open, I hit pause and turned off the screen, and slid the phone into my pocket. No sound, no vib no indications, 5 minutes later I check and find out that its in fastboot mode. So its not from the USB.
I'll try to install a Sense 7 ROM and see how that goes. Very frustrating.
The only other issue I have is GPS not updating quickly enough, it only catches my location approximately and only if WiFi is enabled even if its not connected...
Click to expand...
Click to collapse
Any luck with Sense ROMs?

It happened to Me while on BlissPop,and Sonic Open Kang when I had root,it would take two reboots to get my phone back running
Sent from my HTC6525LVW using XDA Premium 4 mobile app

I have the same problem. I seems to be completely random. It only happens when plugged in overnight. Also, I have to select reboot twice to get the phone to reboot. The first try doesn't work.
HTC M8 running The latest Candy ROM.

gmoe65 said:
It happened to Me while on BlissPop,and Sonic Open Kang when I had root,it would take two reboots to get my phone back running
Sent from my HTC6525LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You say when you had root. Did it stop when you turned root off?

I had to get a replacement phone,and it came back with lollipop 5.0.1
Sent from my HTC6525LVW using XDA Premium 4 mobile app

Gevork Gevorkyan said:
This has been a pain in the butt because I've missed morning alarms just to find our my phone is sitting in the bright white screen of derp. This time I need to know, is this an issue for people in general or could this be a ROM issue?
HTC M8 used the $25 unlocking tool and slapped CM 12.1 on this beast. My advanced reboot menu is OFF in developer options. There is no fastboot or whatever from the stock ROM as far as I can tell. Nothing is pressing on the screen as its just face up on the ground. What can I do, what should I try?
Click to expand...
Click to collapse
Did you install the right GAPPS package for that CM?
Did you fac reset before new OS install?
Fastboot was an option with KK, it is not an option with lollipop.
I use CleanRom 4.0 which is 5.0.1 based, no issues. Sense 6 based. Does not need GAPPS. If your gonna tryout other ROMs, I would try CR 4 for the M8. If it does not reboot auto like then maybe its the CM ver you used or maybe it did not load right. I like CR because it has been cleaned of all carrier software. Has only what you need to function as a phone and mini surf machine, lets you do the customization.
Hope you solve it.
luck

spyknee said:
Did you install the right GAPPS package for that CM?
Did you fac reset before new OS install?
Fastboot was an option with KK, it is not an option with lollipop.
I use CleanRom 4.0 which is 5.0.1 based, no issues. Sense 6 based. Does not need GAPPS. If your gonna tryout other ROMs, I would try CR 4 for the M8. If it does not reboot auto like then maybe its the CM ver you used or maybe it did not load right. I like CR because it has been cleaned of all carrier software. Has only what you need to function as a phone and mini surf machine, lets you do the customization.
Hope you solve it.
luck
Click to expand...
Click to collapse
I'm on Candy ROM which I believe is based off 5.1.1 CM12.1. I flashed GAPPS only after the installation and did a full wipe beforehand. After sticking with a N6 so long I don't really like the Sense layout anymore.

The method I used as per CleanRom guide.
Get 2.8.5 TWRP installed, a must for lollipop.
Make a nandroid backup.
Get firmware for Android 5 installed, carrier dependent!
Factory reset from bootloader
Install Sense or AOSP rom android 5.x.x.
if Sense based your done, if AOSP based install GAPPS ver for your OS/rom
Installing lollipop without right FW could cause issues.
Installing FW can brick your device! so be sure its right one, and make sure you get a nandroid backup stored on your added sd card. More importantly do not just take my word, double and triple check all steps before you leap.

I'll be honest I haven't really tried anything because I don't want to go through the hassle of installing and using other ROMs. Mainly because I think it's hard, even though I know it isn't :silly:
I've been just kinda dealing with the occasional random fastboot reboots. Same thing I have to press reboot twice to reboot the phone, and it happens both when plugged in and charging and when just sitting idle in my pocket. But it's never happened while I was using the phone.

Gevork Gevorkyan said:
I'll be honest I haven't really tried anything because I don't want to go through the hassle of installing and using other ROMs. Mainly because I think it's hard, even though I know it isn't :silly:
I've been just kinda dealing with the occasional random fastboot reboots. Same thing I have to press reboot twice to reboot the phone, and it happens both when plugged in and charging and when just sitting idle in my pocket. But it's never happened while I was using the phone.
Click to expand...
Click to collapse
I've been rebooting the phone every night. So far I haven't run into the issue, and I've never had my phone reboot in my pocket.

Gevork Gevorkyan said:
I'll be honest I haven't really tried anything because I don't want to go through the hassle of installing and using other ROMs. Mainly because I think it's hard, even though I know it isn't :silly:
I've been just kinda dealing with the occasional random fastboot reboots. Same thing I have to press reboot twice to reboot the phone, and it happens both when plugged in and charging and when just sitting idle in my pocket. But it's never happened while I was using the phone.
Click to expand...
Click to collapse
Flash another ROM, or reflash CM. Make sure you wipe first. It was probably a bad flash and something is bonked. It'll take you less than 30 mins. I bet that'll take care of your issue. Good luck.

After many months now of using a sense based rom I've yet to run into the fastboot reset problem. I'm going to switch back to CM this weekend and see where it takes me.

New update

There was a new update today. The new version is N920VVRS2BPF2. Not sure what changed though.

I wouldn't download this yet guys/girls because it's looking like this is a security patch to stop us from downgrading from MM to Lollipop!! Once this has been accepted you can't even factory reset or it will render the phone useless!!

I don't know why people have an issue with Marshmallow. Runs flawlessly, I'm usually sitting at 1880MB of free space of RAM, no stuttering, looks and feels cleaner.
Sent from my SM-N920V using Tapatalk

ukemochi said:
I don't know why people have an issue with Marshmallow. Runs flawlessly, I'm usually sitting at 1880MB of free space of RAM, no stuttering, looks and feels cleaner.
Sent from my SM-N920V using Tapatalk
Click to expand...
Click to collapse
Not everyone's phone is the same that's why. Some people like Lollipop over Marshmallow and depending on how you use it and what apps you have on there are also a determining factor in how the rom runs.

Took this update earlier this morning, phone runs like a dream on mm. Starting to notice some slight slowdown with battery saver on. Might be time for a full wipe and reinstall. I did one with the first mm update but there's been like three now since then.
Sent from my SM-N920V using Tapatalk

udis said:
Took this update earlier this morning, phone runs like a dream on mm. Starting to notice some slight slowdown with battery saver on. Might be time for a full wipe and reinstall. I did one with the first mm update but there's been like three now since then.
Sent from my SM-N920V using Tapatalk
Click to expand...
Click to collapse
Good luck! Someone else who tried to do a factory reset and wipe caused the phone to get stuck and so far he hasn't been able to do anything at all to fix it!!

Yikes guess I'll be holding off then
Sent from my SM-N920V using Tapatalk

I accidently hit the install for this update. Ever since MM my battery life, screen on time, has been horrible (2.5-3.5 hours MAX). I've factory reset, wiped cache, tried the package disabler with extreme settings and it still is not right. I was thinking about going back to lollipop but if this update froze that I may dump this phone and look for another. that I can root.

b4u2 said:
I accidently hit the install for this update. Ever since MM my battery life, screen on time, has been horrible (2.5-3.5 hours MAX). I've factory reset, wiped cache, tried the package disabler with extreme settings and it still is not right. I was thinking about going back to lollipop but if this update froze that I may dump this phone and look for another. that I can root.
Click to expand...
Click to collapse
That sucks dude!! I've figured out that if you factory reset *before* you accept any updates, the battery and phone will work much better! I'm not sure what you can do at this point except maybe try to Odin the stock Lollipop rom and see if it works cause maybe the other guy's phone was just a fluke! You have to enable OEM unlock first and enable adb in developer settings.

MrMike2182 said:
Good luck! Someone else who tried to do a factory reset and wipe caused the phone to get stuck and so far he hasn't been able to do anything at all to fix it!!
Click to expand...
Click to collapse
I'm on MM and did a reset last week. I could not sign in to the phone using my Google account for 24 hrs.
If you do a Google search you can find out about this new "security feature".
Also you can reboot the phone by holding down the volume down, then home, then power in that sequence for 10 seconds.

lnjryan said:
I'm on MM and did a reset last week. I could not sign in to the phone using my Google account for 24 hrs.
If you do a Google search you can find out about this new "security feature".
Also you can reboot the phone by holding down the volume down, then home, then power in that sequence for 10 seconds.
Click to expand...
Click to collapse
You're trying to help the wrong person buddy, lol.

MrMike2182 said:
You're trying to help the wrong person buddy, lol.
Click to expand...
Click to collapse
When did they start doing that 24 hour hold?

jaydizman said:
When did they start doing that 24 hour hold?
Click to expand...
Click to collapse
They've been doing it for quite a while.. It's supposed to be a security guard against people stealing your phone and factory resetting it immediately so they can use it. The simple way to stop this is to activate developer mode and enable OEM unlock and USB debugging! Most people who don't bother to read nothing should be happy that it's only 24 hours instead of the 72 (3 days) that it used to be! All they need to do is research before doing anything to their phones.

MrMike2182 said:
They've been doing it for quite a while.. It's supposed to be a security guard against people stealing your phone and factory resetting it immediately so they can use it. The simple way to stop this is to activate developer mode and enable OEM unlock and USB debugging! Most people who don't bother to read nothing should be happy that it's only 24 hours instead of the 72 (3 days) that it used to be! All they need to do is research before doing anything to their phones.
Click to expand...
Click to collapse
So it just buys you time if your phone is stolen. Fine right do what exactly I would track it.. Or remote wipe it.. Just not seeing the benefit

jaydizman said:
So it just buys you time if your phone is stolen. Fine right do what exactly I would track it.. Or remote wipe it.. Just not seeing the benefit
Click to expand...
Click to collapse
Yeah it basically buys you time to track it or wipe the phone and lock it down. It also gives you time to change your password just in case. If people don't want it they can disable it as I said and you can enable it again later if you choose to. I don't see how it's going to hurt anyone so long as they read and learn about their phone before doing anything to it.

MrMike2182 said:
They've been doing it for quite a while.. It's supposed to be a security guard against people stealing your phone and factory resetting it immediately so they can use it. The simple way to stop this is to activate developer mode and enable OEM unlock and USB debugging! Most people who don't bother to read nothing should be happy that it's only 24 hours instead of the 72 (3 days) that it used to be! All they need to do is research before doing anything to their phones.
Click to expand...
Click to collapse
What? I've been using Android phones with Verizon for as long as there has been such a thing...and I've never waited three days after a reset or one day either. Personal experience here or rumor?

ratman6161 said:
What? I've been using Android phones with Verizon for as long as there has been such a thing...and I've never waited three days after a reset or one day either. Personal experience here or rumor?
Click to expand...
Click to collapse
Personal experience several times! Either it's on or off and the carrier can even hide the option so you don't even know it's there. Personally I think it doesn't happen when you're somewhere you normally use your phone but if you go to say another state it's going to know and activate it.

I've reset an lg g2 tons of times flashing it, s4 multiple times and my note 5 twice and I've never had to wait ever. Could it be because I use 2 step authentication?
Sent from my SM-N920V using Tapatalk

Stupid update has screen time like 6th on my list of battery consumption. Thanks for the security update Verizon. Google services seems to be my main drain. Then media server. Nothing like ruining my great battery life.
Sent from my SM-N920V using XDA-Developers mobile app

MrMike2182 said:
I wouldn't download this yet guys/girls because it's looking like this is a security patch to stop us from downgrading from MM to Lollipop!! Once this has been accepted you can't even factory reset or it will render the phone useless!!
Click to expand...
Click to collapse
This is totally false. I just upgraded my wife's Note 5 and then downgraded back to KK. All that is required is a factory data reset after the downgrade. You can do this by holding down the volume up, home and power buttons for 10 seconds. The phone will reboot into recovery and then you can reset and be on your way. Just keep your Google account and password handy if needed.