Develop Bugs

Opening different apps than the one selected. Bug?

Okay I don't know if this is a bug in every Android version that still hasn't been fixed or is it an app that's causing it.
What happens is when I would be using an app like for example Google talk. I would try opening YouTube it would open calculator. And if I try opening messaging it would still open calculator. No matter which app I'd open it would open the wrong app. And I either have to kill all apps or restart my phone
I had this issue only my G2, my Nexus S, Anyone else having this?
Can't recall if I had it on my Sensation or not...
Sent from my Galaxy Nexus using xda premium

This has never happened to me. Are you completely stock?
Sent from my SGH-T989 using xda premium

I have had a similar error on multiple versions of android where you hit the back button and it starts to cycle through several different apps.

Yup happens to me on a few occasions. It just cycles like axion said

If you open apps continually without closing them or going back to the homescreen then pushing back will cycle through them.. that's how it has always been. That's also how it is on WP7
Sent from my Galaxy Nexus using xda premium

I've seen this once on my Galaxy Nexus only, never on a Nexus S, of GS2. A reboot seemed to resolve the issue. I've not seen it again since.

joshnichols189 said:
If you open apps continually without closing them or going back to the homescreen then pushing back will cycle through them.. that's how it has always been. That's also how it is on WP7
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
This is something i have encountered plenty of times. I certainly do not feel the need to come on this board and complain about my phone multitasking.
Sent from my SGH-T989 using xda premium

jonathan3579 said:
This is something i have encountered plenty of times. I certainly do not feel the need to come on this board and complain about my phone multitasking.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
You're missing the point. It has nothing to do with the back button or cycling through programs. The problem is icons launching the wrong apps.
I'm on 4.0.2 stock and if had this happen once since I got my SGN. Never on any other of my Androids. A restart fixed it.

thequinox said:
You're missing the point. It has nothing to do with the back button or cycling through programs. The problem is icons launching the wrong apps.
I'm on 4.0.2 stock and if had this happen once since I got my SGN. Never on any other of my Androids. A restart fixed it.
Click to expand...
Click to collapse
Then you guys have defective phones. Simple as that. Return it or stop complaing because most of us do not have these issues.
Sent from my SGH-T989 using xda premium

Happened to me too. Usually helps to get rid of all alps in multitasking menu.

jonathan3579 said:
Then you guys have defective phones. Simple as that. Return it or stop complaing because most of us do not have these issues.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
This is an absolutely absurd and incorrect statement. There is nothing "defective" about the phone. It's a software issue that occurs under a fairly specific set of circumstances.
I've had this happen starting with 4.0 builds on the Nexus S as well as on the GN. It didn't happen pre-ICS. What it does occur hitting back actually will back through the entire stack of activities oddly enough.
When this occurs you can back through the stack to a point, hit home and then hit the offending icon again and it will resume in the stack at the point in which you hit home. If you actually back entirely down the stack you'll get to the home screen and the expected app will finally launch. Depending on what's been opened since the last reboot though this can be a huge pain.
From looking in to this the only real thing I found reported was an issue with activity re-parenting. This was causing activities that allowed re-parenting to be launched in the wrong context and causing a similar behavior.
So far I've only noticed it occurring with the gapps (Messaging, Music) launching the wrong activity, but this is merely an observation.
If you can isolate a manner in which to recreate this scenario it would be helpful to report it, as this is definitely not the intended behavior. If you don't want to report it, but believe you can recreate it I can test it on a few devices / builds and submit it.
So far I haven't been able to purposefully recreate the issue, although I've spent minimal time trying as it is only a minor annoyance. If it occurred more frequently it would be another story.

krohnjw said:
When this occurs you can back through the stack to a point, hit home and then hit the offending icon again and it will resume in the stack at the point in which you hit home. If you actually back entirely down the stack you'll get to the home screen and the expected app will finally launch. Depending on what's been opened since the last reboot though this can be a huge pain.
Click to expand...
Click to collapse
Have you tried what I wrote? To just swipe away the apps in the multitasking menu/button? I've had it twice and both times that have been enough for me to sort it out.
Sent from my Nokia 3210

Lowtrash said:
Have you tried what I wrote? To just swipe away the apps in the multitasking menu/button? I've had it twice and both times that have been enough for me to sort it out.
Sent from my Nokia 3210
Click to expand...
Click to collapse
No, I've just backed down the stack. I am curious as to the trigger for the behavior though as it is a rather uncommon occurrence.

krohnjw said:
This is an absolutely absurd and incorrect statement. There is nothing "defective" about the phone. It's a software issue that occurs under a fairly specific set of circumstances.
I've had this happen starting with 4.0 builds on the Nexus S as well as on the GN. It didn't happen pre-ICS. What it does occur hitting back actually will back through the entire stack of activities oddly enough.
When this occurs you can back through the stack to a point, hit home and then hit the offending icon again and it will resume in the stack at the point in which you hit home. If you actually back entirely down the stack you'll get to the home screen and the expected app will finally launch. Depending on what's been opened since the last reboot though this can be a huge pain.
From looking in to this the only real thing I found reported was an issue with activity re-parenting. This was causing activities that allowed re-parenting to be launched in the wrong context and causing a similar behavior.
So far I've only noticed it occurring with the gapps (Messaging, Music) launching the wrong activity, but this is merely an observation.
If you can isolate a manner in which to recreate this scenario it would be helpful to report it, as this is definitely not the intended behavior. If you don't want to report it, but believe you can recreate it I can test it on a few devices / builds and submit it.
So far I haven't been able to purposefully recreate the issue, although I've spent minimal time trying as it is only a minor annoyance. If it occurred more frequently it would be another story.
Click to expand...
Click to collapse
But the OP clearly destroys your theory seeing as how this has happened on other handsets (pre-ICS as a matter of fact) as well. What's your rebuttal for that? To add to that, if a device pre-ICS did have this problem... Would it not be considered defective? *Keeping in mind that most people don't have the problem.* I have absolutely no issues no matter the number of apps I have open. So is my device defective because everything opens as it should? As I said before, this is a very small group of people who are experiencing this so I think that negates that something isn't defective. There are plenty of "defective" products that function generally as intended but have small quirks. Your turn...

jonathan3579 said:
But the OP clearly destroys your theory seeing as how this has happened on other handsets (pre-ICS as a matter of fact) as well. What's your rebuttal for that?
Click to expand...
Click to collapse
Where do you see this claimed to have happened on any pre 4.0 rom?
I had this issue only my G2, my Nexus S, Anyone else having this?
Click to expand...
Click to collapse
jonathan3579 said:
I have absolutely no issues no matter the number of apps. As I said before, this is a very small group of people who are experiencing this so I think that negates that something isn't defective. There are plenty of "defective" products that function generally as intended but have small quirks. Your turn...
Click to expand...
Click to collapse
I don't see how anything is "destroyed". The fact remains that you have an app launching an activity that does not belong to its package. The back button then proceeds to back down the activity stack rather than properly exit the app when the main activity is exited.
The fact that it is only noticed by a small subset of users is not indicative in any way of a "defective" handset - its far more likely that it's a very specific software issue triggering the problem.
The fact that the sub system is allowing the user to back down the ENTIRE activity stack with the back button rather than exiting properly when the main activity of *each* package is exited doesn't exactly scream bad hardware....

krohnjw said:
Where do you see this claimed to have happened on any pre 4.0 rom?
I don't see how anything is "destroyed". The fact remains that you have an app launching an activity that does not belong to its package. The back button then proceeds to back down the activity stack rather than properly exit the app when the main activity is exited.
The fact that it is only noticed by a small subset of users is not indicative in any way of a "defective" handset - its far more likely that it's a very specific software issue triggering the problem.
The fact that the sub system is allowing the user to back down the ENTIRE activity stack with the back button rather than exiting properly when the main activity of *each* package is exited doesn't exactly scream bad hardware....
Click to expand...
Click to collapse
I get your point but something being defective doesn't always dictate that it's a hardware problem, wouldn't you agree? I never specifically said it was a hardware issue. Either way, it's hard to say what the REAL issue is until someone takes time to reproduce this. Just for reference though: If a hardware/software manufacturer cannot reproduce said issue, they'd deem said products experiencing it defective.

Yep I know what you mean, happens to me on Google Music.
Th easiest solution I found was to force stop the app that's bugged out.

I've had this too. Swiping away the app I'm trying to open and the one it is opening instead has fixed it for me.

jonathan3579 said:
I get your point but something being defective doesn't always dictate that it's a hardware problem, wouldn't you agree? I never specifically said it was a hardware issue. Either way, it's hard to say what the REAL issue is until someone takes time to reproduce this. Just for reference though: If a hardware/software manufacturer cannot reproduce said issue, they'd deem said products experiencing it defective.
Click to expand...
Click to collapse
Defective software I have no issue with - that's a harsh classification for a bug, but not incorrect.
Your statement of "Return it" followed by "most of us do not have these issues" seemed to imply a belief that the physical unit must be defective (in comparison to a unit that did not experience this issue) rather than a behavior or set of behaviors causing as software issue as most users do not experience this. Thereby returning would resolve the issue.
Given the symptoms present when this occurs I can't imagine this to be true i any way, shape or form. Especially given that this bug has existed since 4.0 hit AOSP and on builds for the Nexus S as well (hence why it's absurd to blame this on a singular hardware fault of a single device).
I am interested in reproducing the issue, or capturing a logcat the next time it occurs (it only seems to happen when I am in the car unfortunately) to see if the WindowManager of ApplicationManager are supposedly starting the proper activities or the issue might lie with the package manager.

I've had this happen when i open a lot of apps without closing them and use the multitasking button to switch between apps.

Random Reboots - FF18

I'm running the stock ICS FF18, rooted. All seemed reasonably well for the first couple weeks, now the damn thing wants to randomly reboot.
I tried wiping, reinstalling the stock ICS, but the problem returned. Reboots happen maybe upwards of a dozen times a day. I've tried isolating the problem but unable to find a common variable...sometimes it happens when I'm in the middle of something, like web surfing or texting. Sometimes it happens when I press the power button, sometimes it happens when it's just sitting there not being touched, sometimes it happens when plugged it, sometimes when not plugged in.
I can't think I have a bad install twice and I'm not finding much on the forums here about others with a similar problem with the stock ICS. So I'm thinking either an app is being a b1tch and causing problems or perhaps something related to the battery? If there was one common theme, it does always happen later in the day or at night after the battery is down below 50%.
Does anyone have thoughts, ideas, suggestions on the likelihood of a bad battery or perhaps someone experienced something similar?

waltcoleman said:
I'm running the stock ICS FF18, rooted. All seemed reasonably well for the first couple weeks, now the damn thing wants to randomly reboot.
I tried wiping, reinstalling the stock ICS, but the problem returned. Reboots happen maybe upwards of a dozen times a day. I've tried isolating the problem but unable to find a common variable...sometimes it happens when I'm in the middle of something, like web surfing or texting. Sometimes it happens when I press the power button, sometimes it happens when it's just sitting there not being touched, sometimes it happens when plugged it, sometimes when not plugged in.
I can't think I have a bad install twice and I'm not finding much on the forums here about others with a similar problem with the stock ICS. So I'm thinking either an app is being a b1tch and causing problems or perhaps something related to the battery? If there was one common theme, it does always happen later in the day or at night after the battery is down below 50%.
Does anyone have thoughts, ideas, suggestions on the likelihood of a bad battery or perhaps someone experienced something similar?
Click to expand...
Click to collapse
Any special wi-fi config? (That's the culprit in my case.)

garwynn said:
Any special wi-fi config? (That's the culprit in my case.)
Click to expand...
Click to collapse
No...never installed the hotspot hack, did have foxfi installed, but did not reinstall after reloading ff18.

im also having the same problem as well, and the problem has became worse and worse,what started off as once or twice a day,is now at least occurring every 10 min.I think im about to downgrade right now to stock gingerbread and see what happens

My phone has always had some amount of random "poweroffs" (not really reboots, I pick up the phone expecting it to be on and it boots from scratch instead). However its much more frequent on ICS (FF18/FH13).

rocket321 said:
My phone has always had some amount of random "poweroffs" (not really reboots, I pick up the phone expecting it to be on and it boots from scratch instead). However its much more frequent on ICS (FF18/FH13).
Click to expand...
Click to collapse
U can always unroot back to el29(gingerbread)i was having the same problems and now i can enjoy my phone
Sent from my SPH-D710 using xda premium

I had that issue on AOKP M6, then realized my power button was actually broken. It would reboot the phone because it was actually stuck down internally. Had to get a new phone.
Sent from my SPH-D710 using xda app-developers app

R0CKSTAR3N3RGY said:
I had that issue on AOKP M6, then realized my power button was actually broken. It would reboot the phone because it was actually stuck down internally. Had to get a new phone.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
The power button seems to be a common cause of random reboots and that's what I'm leaning towards now as no other software fix has resolved the problem. Supposedly Sprint ordered me a replacement to swap out phones. I'd definitely recommend trying a different Kernel if on FF18 and if that doesn't fix it, try rolling back to EL29.

"Ghost" Problems

That's what is being called now, where you get a momentary line across your screen, or the page jumps by itself for no reason.
At first, it was only just an annoyance, but now it has become a pain in the neck, starting today. What was a bit too often occurrence had today become a noticeable problem.
It is happening no matter what rom, Application or an page I'm on. I can be reading something, when the page will for no reason jump to where it was before for a moment, then come back to its previous position. I am even finding that if I am responding to a post and am quoting it, the cursor will jump up in the quote while I am typing, causing me to mess up the quote and having to back out of the response all together and start over. What's more what was happening infrequently is now becoming a few times an hour.
So I am wondering if anyone is experiencing this increase in the problem lately, and has anyone had any luck in finding a solution?
Sent from my SGH-T999 using XDA Premium HD app

Kamau54 said:
That's what is being called now, where you get a momentary line across your screen, or the page jumps by itself for no reason.
At first, it was only just an annoyance, but now it has become a pain in the neck, starting today. What was a bit too often occurrence had today become a noticeable problem.
It is happening no matter what rom, Application or an page I'm on. I can be reading something, when the page will for no reason jump to where it was before for a moment, then come back to its previous position. I am even finding that if I am responding to a post and am quoting it, the cursor will jump up in the quote while I am typing, causing me to mess up the quote and having to back out of the response all together and start over. What's more what was happening infrequently is now becoming a few times an hour.
So I am wondering if anyone is experiencing this increase in the problem lately, and has anyone had any luck in finding a solution?
Sent from my SGH-T999 using XDA Premium HD app
Click to expand...
Click to collapse
It is a well known CM 10.1 issue. Not sure which nightly this started occurring on but the fact is they are nightlies. Any known issues will be fixed. As far as the issue increasing is concerned, it's happened to others but for some not at all. Some occur with these 3.4 kernels so it can also depend on the kernel you're running. Keep track of your kernel thread. The fact is ALL devices even if it's the same model may handle things differently. You're just gonna have to stick it out as more nightlies come through, hopefully fixing this ghost screen increase for you and other users.
Sent from my Nexus 4 using xda premium

I was using reddit is fun for a couple hours today and did not encounter the issue (with nightly 4/14). Was terrible with previous nightlies. Terrible as in every damn time I scrolled the page. If you haven't tried 4/14, or the soon to be 4/16, that's your first step.

LuxigiBull23 said:
It is a well known CM 10.1 issue. Not sure which nightly this started occurring on but the fact is they are
. Any known issues will be fixed. As far as the issue increasing is concerned, it's happened to others but for some not at all. Some occur with these 3.4 kernels so it can also depend on the kernel you're running. Keep track of your kernel thread. The fact is ALL devices even if it's the same model may handle things differently. You're just gonna have to stick it out as more nightlies come through, hopefully fixing this ghost screen increase for you and other users.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I was thinking about trying a different kernel, but the last rom I flashed other day had a different one in it, and it did the same thing.
Thanks for the info though. I was just wondering about the increase because it seems to get worst each time I flash. Basically though I was just putting info out there in case it could be helpful.
Aerowinder said:
I was using reddit is fun for a couple hours today and did not encounter the issue (with nightly 4/14). Was terrible with previous nightlies. Terrible as in every damn time I scrolled the page. If you haven't tried 4/14, or the soon to be 4/16, that's your first step.
Click to expand...
Click to collapse
I'm not on a nightly. I'm running a stable Deviant Xone, but I am more than sure it's not the rim since I have heard of the same issue on other roms.
Thanks anyway. As I do flash other roms, I will keep that in mind.

Random sluggish performance that requires reboot?

Hello everyone. I've been experiencing a problem lately that has me scratching my head. The phone for no reason and at random times because super sluggish like the frame rate or something is super low.. It seems to be most apparent in the launcher.. It happens at random even if the phone is cool or hot. Happens on touchwiz launcher as well as nova launcher.. Clearing ram and open apps doesn't work... The only thing that makes the phone go back to normal is a reboot. This also happens on any custom ROM. With stock or custom kernel.. So.is this a CPU hardware problem? Has anyone else had this happen? It's already been happening quite often and its becoming annoying. Factory resets don't solve it either as it comes back randomly. If anyone can shed some light please do.
Sent from my GT-I9505 using xda app-developers app

pezlomd said:
Hello everyone. I've been experiencing a problem lately that has me scratching my head. The phone for no reason and at random times because super sluggish like the frame rate or something is super low.. It seems to be most apparent in the launcher.. It happens at random even if the phone is cool or hot. Happens on touchwiz launcher as well as nova launcher.. Clearing ram and open apps doesn't work... The only thing that makes the phone go back to normal is a reboot. This also happens on any custom ROM. With stock or custom kernel.. So.is this a CPU hardware problem? Has anyone else had this happen? It's already been happening quite often and its becoming annoying. Factory resets don't solve it either as it comes back randomly. If anyone can shed some light please do.
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
I would contact T-Mobile it could be a phone problem if you are seing it after an Odin back to stock. That would be my only suggestion is an Odin back but since you already did that I would see about getting the phone switched out
Sent from my GT-I9505G using Tapatalk 4

byron1985 said:
I would contact T-Mobile it could be a phone problem if you are seing it after an Odin back to stock. That would be my only suggestion is an Odin back but since you already did that I would see about getting the phone switched out
Sent from my GT-I9505G using Tapatalk 4
Click to expand...
Click to collapse
How could I prove to them that this is worthy of a warranty replacement? I can't seem to reproduce the problem.. It just happens..I thought Odin would solve the problem too but then it just randomly happened
Sent from my GT-I9505 using xda app-developers app

pezlomd said:
How could I prove to them that this is worthy of a warranty replacement? I can't seem to reproduce the problem.. It just happens..I thought Odin would solve the problem too but then it just randomly happened
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
Explain to tmobile what's happening and let them know you want a new device. they are very easy to work with and tmobile won't make you prove anything. Ive been with tmobile for ten years now. Trust me they are easy to work with if you explain the situation and let them know it clearly interferes with your ability to use the device as it should be used. You should have ZERO problems with returning the device. By the way sounds like your device DOES have serious problems so id call tmobile as soon as possible. They MIGHT try trouble shooting it FIRST as this is procedure they HAVE to follow simply let them know after trouble shooting that your issue IS STILL PRESENT and they will exchange your device for a new one without issue...so call them asap. You won't have any trouble. You will see. They are very EASY to work with so NO WORRIES. Call and get your device exchanged NOW. Hope this helps you out. I've had a LOT of expirence working with tmobile. It won't be a problem. Youll see. Best wishes to you and hope you get this matter resolved today.

realsis said:
Explain to tmobile what's happening and let them know you want a new device. they are very easy to work with and tmobile won't make you prove anything. Ive been with tmobile for ten years now. Trust me they are easy to work with if you explain the situation and let them know it clearly interferes with your ability to use the device as it should be used. You should have ZERO problems with returning the device. By the way sounds like your device DOES have serious problems so id call tmobile as soon as possible. They MIGHT try trouble shooting it FIRST as this is procedure they HAVE to follow simply let them know after trouble shooting that your issue IS STILL PRESENT and they will exchange your device for a new one without issue...so call them asap. You won't have any trouble. You will see. They are very EASY to work with so NO WORRIES. Call and get your device exchanged NOW. Hope this helps you out. I've had a LOT of expirence working with tmobile. It won't be a problem. Youll see. Best wishes to you and hope you get this matter resolved today.
Click to expand...
Click to collapse
I'll have to agree here. I've had many issues over the years (anyone remember the LG G2X?), and they will stand by you. Sometimes you have to squawk loudly, but they want you to be happy...
Unlike Sprint.....I hate Sprint
Edit: If you're not happy with their response, just escalate it to Customer retention...they have the real power.

I had bad lag when I was trying to text, send an email, or anything involving using the keyboard. I flashed a ROM thinking that would take care of the issue . It didnt, still had hang ups and lag. I flashed back to stock and received a new phone and havent had an issue yet.

Random reboots after Andorid 7.0 Nougat update

I took the plunge to Android 7.0 Nougat, however I am having some major problems. Initially I had everything stock, and every once in a while my phone would reboot when on WiFi. Sometimes it rebooted within 5 minutes of booting back up, sometimes it would reboot 1 hour after booting back up. There is a whole thread about it here (note: not the bootloop issue occasionally talked about in that thread, although it could be related I guess): https://productforums.google.com/forum/#!topic/nexus/kaMOvuf093Q
I was wondering if anyone else has run into this issue? It definitely seems to be linked to WiFi only. A bunch of users apparently narrowed down a few apps that triggered the reboots more frequently (Napster, for example), but the problem seems deeper than just a rogue app. Safe mode does seem to alleviate the issue, but this is not really an acceptable solutions to me. I tried another kernel (Franco's), but that didn't fix anything. I was wondering if anyone who had this problem had any success fixing it by changing ROMs or kernels? I also read that turning off WiFi scanning may also help--I will report back if this fixes anything.
Any suggestions welcome, thanks!

This could be part of the hardware issue that is happening, it talented to me and I finally have my phone back
Sent from my Nexus 5X using Tapatalk

Which Model of LG 5X?
Do you have H-790 or H-791 Model?
Cheesejam said:
I took the plunge to Android 7.0 Nougat, however I am having some major problems. Initially I had everything stock, and every once in a while my phone would reboot when on WiFi. Sometimes it rebooted within 5 minutes of booting back up, sometimes it would reboot 1 hour after booting back up. There is a whole thread about it here (note: not the bootloop issue occasionally talked about in that thread, although it could be related I guess): https://productforums.google.com/forum/#!topic/nexus/kaMOvuf093Q
I was wondering if anyone else has run into this issue? It definitely seems to be linked to WiFi only. A bunch of users apparently narrowed down a few apps that triggered the reboots more frequently (Napster, for example), but the problem seems deeper than just a rogue app. Safe mode does seem to alleviate the issue, but this is not really an acceptable solutions to me. I tried another kernel (Franco's), but that didn't fix anything. I was wondering if anyone who had this problem had any success fixing it by changing ROMs or kernels? I also read that turning off WiFi scanning may also help--I will report back if this fixes anything.
Any suggestions welcome, thanks!
Click to expand...
Click to collapse

sorry my bad, wrong thread

ashokabs said:
Do you have H-790 or H-791 Model?
Click to expand...
Click to collapse
I have a H-790 Nexus 5x on Verizon.

has been happening to me too -- reboots randomly about once or twice a day. (only realize it since fingerprint scanner does not work and i am forced to key my passcode at first login post reboot).

It seems that the H 790 production series are faulty

Nexus 5x reboot problems
Yes it would appear so. However, I have read one post in Google Forums that speaks of problems with H791. However, it could be related to the wifi problem. There are two problems - one is problem booting initially and finally phone does not boot into the ROM and cannot be recovered. This seems to be related to hardware problem in H-790 series. The other has been isolated to the WiFi scanning which causes a crash.
giannism13 said:
It seems that the H 790 production series are faulty
Click to expand...
Click to collapse

Yeah, I am definitely having a problem with the WiFi crash. Would a custom kernel fix this? A custom ROM would, right? Any ideas for a fix for this?

ashokabs said:
Yes it would appear so. However, I have read one post in Google Forums that speaks of problems with H791. However, it could be related to the wifi problem. There are two problems - one is problem booting initially and finally phone does not boot into the ROM and cannot be recovered. This seems to be related to hardware problem in H-790 series. The other has been isolated to the WiFi scanning which causes a crash.
Click to expand...
Click to collapse
I have read the same too, but he's the only one among the hundrends of h790 users who have the same problem.
Cheesejam said:
Yeah, I am definitely having a problem with the WiFi crash. Would a custom kernel fix this? A custom ROM would, right? Any ideas for a fix for this?
Click to expand...
Click to collapse
You could try too, but I doubt it will fix anything. Its a hardware problem

giannism13 said:
I have read the same too, but he's the only one among the hundrends of h790 users who have the same problem.
You could try too, but I doubt it will fix anything. Its a hardware problem
Click to expand...
Click to collapse
I thought the bootloop issue was hardware related, but not the random reboots issue? Ex: Safe mode fixes the problem for me.

ashokabs said:
There are two problems - one is problem booting initially and finally phone does not boot into the ROM and cannot be recovered. This seems to be related to hardware problem in H-790 series.
Click to expand...
Click to collapse
IMO opinion this is just the eMMC dying problem that people have reportedly sporadically over the past 12mo. That problem has affected both H790 and H791. It likely just became more likely to show up after the 7.0 update because that was a large update, but by no means is a large update going to cause the problem by itself. The core problem is eMMC that was waiting to fail and could have happened just when web browsing but a large update just pushed it over the edge. Some phones you can do many large updates and never see a problem, then boom, one day randomly it just reboots and bootloops, with no amount of flashing or resetting making any difference.

Cheesejam said:
I thought the bootloop issue was hardware related, but not the random reboots issue? Ex: Safe mode fixes the problem for me.
Click to expand...
Click to collapse
If safe mode fixes the problem, then I was wrong. Try to find which app conflicts with the system and uninstall it

giannism13 said:
If safe mode fixes the problem, then I was wrong. Try to find which app conflicts with the system and uninstall it
Click to expand...
Click to collapse
I really wish Google would fix this, this isn't really an acceptable solution to me. :/

I have a h790 nexus 5x and haven't seen this issue, knock on wood. However if it's linked to wifi scanning that was issued in another post you may try disabling wifi scanning to see if the issue is resolved. If not it's definitely the emmc in my opinion
Sent from my Nexus 5X using XDA-Developers mobile app

Cheesejam said:
I really wish Google would fix this, this isn't really an acceptable solution to me. :/
Click to expand...
Click to collapse
If it is indeed not a a hardware problem, then don't wait for Google to fix it overnight. Besides, it may be the case that there is no bug at all, and you flashed a corrupted firmware. Your Best bet right now is to try some custom Roms and kernels and see if it fixes the problem. If you don't want to mess with user made firmware then I would suggest you to reflash the latest stock image form Google. If both of the above fail, the you are forced to roll back to marshmallow

You can try to disable wifi scanner on sleep,.

After the Nougat upgrade, I was having random reboots on my 5X (LG-H791). It always happened when my 5X was sleeping (laying on my working desk or on my bedside table for some time). After the reboot it was working fine again for some hours, so it does not seem to be the bootloop issue. I remember that I had a few rare reboots after upgrading to Nougat 7.0, but after the last 7.1.1 upgrade the reboots occured at least every second day.
Last Friday I had enough of it. I downgraded to the last stock Marshmallow 6.0.1 (MTC20K), and it didn't crash a single time after that.
My wife's 5X is having the same random reboots. The reboots are less frequent (but still occur) when WLAN is turned off. I will downgrade her's too, if my 5X is still still stable after the next weekend.
I wonder if this is a different problem, or if this is just a first symptom of the bootloop issue. If it's a bug in Nougat, then shouldn't much more (if not all) 5X owners experience these random reboots?

Cheesejam said:
I took the plunge to Android 7.0 Nougat, however I am having some major problems. Initially I had everything stock, and every once in a while my phone would reboot when on WiFi. Sometimes it rebooted within 5 minutes of booting back up, sometimes it would reboot 1 hour after booting back up. There is a whole thread about it here (note: not the bootloop issue occasionally talked about in that thread, although it could be related I guess):
I was wondering if anyone else has run into this issue? It definitely seems to be linked to WiFi only. A bunch of users apparently narrowed down a few apps that triggered the reboots more frequently (Napster, for example), but the problem seems deeper than just a rogue app. Safe mode does seem to alleviate the issue, but this is not really an acceptable solutions to me. I tried another kernel (Franco's), but that didn't fix anything. I was wondering if anyone who had this problem had any success fixing it by changing ROMs or kernels? I also read that turning off WiFi scanning may also help--I will report back if this fixes anything.
Any suggestions welcome, thanks!
Click to expand...
Click to collapse
hi, i had the exact same problem with my nexus 5x from carphonewarehouse (uk), and when it was given in to repair i was promised money in return, however they ended up refusing to give money and gave a replacement phone instead, the only way to fix this issue is apparently to get a replacement, as it is most likely a hardware issue google haven't accounted for

I've had the random restart issue for a while now. I got a "new" replacement in November for a different issue and have been on 7.0 the whole time (until last week when I got 7.1.1 OTA). I'm going to call today about another replacement. I've just had two restarts in the last hour.