Database Develop

[Q] Reboot using Airplane mode

Sometimes I'm in areas where I don't get the best reception (i.e. some lecture halls during school hours) and I choose to put my phone in airplane mode so as to conserve battery when the class is over. However I find after trying to come out of Airplane Mode my Revo always reboots. As far as I can remember this issue has also happened in Decrapped 1.0. The same thing happens when I turn on GPS and choose to go to Google Navigation I get rebooted. After the reboot occurs I can turn on the gps/airplane mode etc without any problems. But does this issue happen to anyone else or is it perhaps just my phone? Thanks!!

I find that my revo does the same thing with google nav beta, it will sometimes hang and reboot too. I am running stock rom with a root. When I rotate phone the landscape view is sometimes corrupted with tiny blocks instead of the maps drawn correctly. I have to exit nav app and reload

I've had the same thing happen with airplane mode. I don't really use it often so I figure I can live with it.

Same here. The Revo doesn't seem to like hardware mode changes at times. I get reboots when switching into Bluetooth occasionally.
[I'm Revolting -- are you? Beamed directly into your brain by Revolt 1.3]

I'm happy to hear I'm not the only one this happens to. Do you think LG will possibly release a fix? (or more people will have to raise concern about it) or possible for a dev to take a crack at it in their free time? Thanks for the feedback guys!

Cryofalcon said:
I'm happy to hear I'm not the only one this happens to. Do you think LG will possibly release a fix? (or more people will have to raise concern about it) or possible for a dev to take a crack at it in their free time? Thanks for the feedback guys!
Click to expand...
Click to collapse
I'm only adding this due to the fact that I was constantly having issues when tethering with the Verizon 4g Hot Spot app. When running it, I found myself needing to reboot because the data connection would get lost and sometimes go into 3g, causing all sorts of headaches with doing things on my computer, such as redesigning websites, including my own.
What I found, though, related to this post, is using the airplane mode to kill the data connection and restart it, was getting me 4g and a few minutes to a few hours of Internet again until the next glitch.
Overall, modded, ota updated, downgraded, whatever, using that method never rebooted my phone. My thoughts are that it's possible some app might be causing that. I don't use Nav anymore, except as a last resort because it is so buggy, it would cause my phone to crash over and over, and rebooting. So, as for LG or Verizon coming up with a fix for this issue, I don't know if they would see it as one because it's not something everyone is experiencing and with as much as I use(d) that method, it never once happened to me. Please don't take that wrongly, just wanted to point out that it might be a certain app and allow those having this issue to seek another solution, maybe comparing apps installed to see a common denominator.
And, because I see a lot of posts relating to tethering issues with Internet freezing or dropping out, I found, on my LINUX machine (so far), that setting the MTU to 1300 seems to have solved that issue. I know this last part isn't directly related to the original post, but is the reason I kept using the airplane mode method and thought this added information might help someone doing what I was...
-Cybie

Sorry for the bump, but as of flashing Revolt 1.5, the issue in my original post seems to have been corrected as I was able to go from airplane mode to google nav multiple times and didn't reboot at all. so whatever the issue was seems to have been corrected. Thanks MT!!

Overheating to the point of possible injury

So I will preface with the fact that I'm on my second s6 edge 64GB. The first one had same issues.
Essentially 80% of the time this phone functions and works with no problem still the best phone I've ever used. However, it will heat up randomly, or so I thought, to the point of the first one burning me and leaving red marks on my hands. This is what prompted the first exchange.
Now this one is doing the same. It seems to be triggered when I enable wifi but I haven't been able to pin point exactly what it is. It also seems to get really bad when I have it on the charger.
Attached you can see the result of the worst it's gotten.
Anyone else having overheating issues like this?

h3ck said:
So I will preface with the fact that I'm on my second s6 edge 64GB. The first one had same issues.
Essentially 80% of the time this phone functions and works with no problem still the best phone I've ever used. However, it will heat up randomly, or so I thought, to the point of the first one burning me and leaving red marks on my hands. This is what prompted the first exchange.
Now this one is doing the same. It seems to be triggered when I enable wifi but I haven't been able to pin point exactly what it is. It also seems to get really bad when I have it on the charger.
Attached you can see the result of the worst it's gotten.
Anyone else having overheating issues like this?
Click to expand...
Click to collapse
I use wifi all the time and actually leave wifi on all day long. Never had this issue. If you are having the same issue with two phones, you should check out apps you installed.

Definitely get it back to stock even if you have to reset and see if the same issue exists. if it does then I would get with Samsung again for another replacement

As someone who is on their 3rd phone for factory defects, I can tell you my 2nd one was MUCH hotter than any of the other ones. I'm not sure what causes it, but it seemed hardware related.

compywiz said:
As someone who is on their 3rd phone for factory defects, I can tell you my 2nd one was MUCH hotter than any of the other ones. I'm not sure what causes it, but it seemed hardware related.
Click to expand...
Click to collapse
The only time mine gets THAT hot (to the point of triggering the cool down mode even), is if I'm tethered, and charging, and even then it's hit or miss. If I start doing stuff on the phone at the same time though, then it'll ramp up quickly. It actually shut down skype on me yesterday doing that, but I was pushing it pretty hard. Skype on the phone, charging, and hotspot to the PC downloading a 2 gig file. Normal wifi tho, no issues on my end.

Might be go to do with the kernel for WiFi. Maybe you can get a replacement with a different variant?
Sent from my Moto G using XDA Free mobile app

You could always download CM Security off the market and it will analyze what's causing your phone to heat up. Sorry if that wasn't helpful. I use that app daily to keep my phone freed up and secured.
Sent from my SM-G925V using Xparent Red Tapatalk 2

The edge was designed and intended to be used as a clothes iron.
(Disclaimer: I take no responsibility if you use it as one and it causes a fire)

After tons of trial and error I don't have it happen almost all all now that I use smart wifi toggle app. Think wifi in a weak signal area also was to blame. It was constantly trying to connect and reconnect. Also, most recently it got hot, but not to the extreme, when I started looking at theme store again. So wifi issues and or theme store are contributors.
Sent from my tablet

[Bugcollection] Which bugs did you encounter in Lollipop?

Hey guys,
I am using my Moto X (XT1052) for almost 2 years now. It is/was the best android phone I've had so far. It was smooth, had no hangs and just did what it was supposed to do. Since I received the Update to 5.1 I keep on having real strange issues and it really bothers me because it really renders the phone useless at times. And since I couldnt find another thread with all bugs collected in one place, I am going to start my own thread.
So which bugs did I find so far?
1.Youtube and other video services don't work all the time
(They work sometimes, but the the video stops, tries to resume and ends up in a loop trying to load the video. Often only a reboot helps.)
2. Battery consumption in general has become way worse (cell-standby)
3. Random "Optimizing apps" after a reboot
4. No Active Display with handsover (I know this isn't a feature anymore, but to me this is a bug as well)
5. Missing energy widget
6. Wifi range has reduced significantly and seems to be buggy at times (can't always tell if it's my router or the phone, but mostly it's the phone)
7. Sometimes the phone uses mobile data instead of wifi, even if connected
8. Vibration mode (important notifications only) doesnt always end properly and the phone doesn't start vibrating again after the set time or alarm
I think that's it for now. But this clearly is enough for me.
So please Moto guys do something! If you need logcats or anything else, let me know and I ll help out as good as I can. I was one of those who patiently waited for an update instead of crying for one, because I wanted a stable one rather than a fast and unstable one. So either fix it, or I ll have to return my Moto X. The phone in its' current state is useless for me. Especially as I can't even downgrade without having to risk a full brick. So please do something and push an update to either allow downgrading, or fix the existing bugs!
Sent from my XT1052 using XDA Free mobile app

N00BY0815 said:
Hey guys,
Sent from my XT1052 using XDA Free mobile app
Click to expand...
Click to collapse
I miss this very badly
"No Active Display with handsover"
Now I have to tap or take my phone to see notifications... :crying:

I switched over to CM and all is going great of course at a small cost of losing Moto voice feature but I can most certainly live without it. I've got very decent battery life of 5-6hours of screen time over a span of 13hours. No over heating issues and usually cell standby sits at 2% usage which is absolutely fine for me.. Even the hand wave gesture works with active display. I'm so happy with how stable it is with CM. Living with a bug free phone for now.
Sent from my Moto X

Random Crashes followed by optimization boot
I have been getting random crashes that lead to the phone shutting off. When I turn it back on, it takes FOREVER to optimize 92 apps. I don't have even 30 apps on the phone!
I did a factory reset and still have this problem. It's happening every couple of days. It's making my experience with this phone very frustrating!

Some more issues I've found:
Soundproblem, sometimes when I switch e.g. from twitch to spotify and then try to increase or decrease the volume, I get a crackling sound every time I push the button. Sometimes it disappears after a certain time of not playing anything, but mostly again only a reboot helps.
The phone unlocks itself more often in my pockets for no obvious reason.
The unlock on the ActiveDisplay unlockscreen often only leads to the normal unlocking screen instead of the homescreen. Same thing when I try to open notifications. Mostly those apps run, but I get to see the normal lockscreen, instead of the app with the notification.
Sent from my XT1052 using XDA Free mobile app

I think I found a fix for the YouTube problem.
Press the power button and keep it pressed till you feel another vibrate ie. After the power menu pops up.
That seems to solve it
Sent from my XT1052 using Tapatalk

adity said:
I think I found a fix for the YouTube problem.
Press the power button and keep it pressed till you feel another vibrate ie. After the power menu pops up.
That seems to solve it
Sent from my XT1052 using Tapatalk
Click to expand...
Click to collapse
Well that's not exactly what I would call a fix it appears to work sometimes though. I also noticed that simply changing the video quality from let's say 720p to 480p often resolves the issues. I mostly get the video bug, when I am trying to watch things in 720p or above. Maybe it is a codec problem? A broken lib?
Sent from my XT1052 using XDA Free mobile app

For YouTube, you could get another app. I stopped the cell standby issue by turning off carrier internet when not needed. Install greenify, servicely, battery saver, and power nap. 1 I too have random optimizing of apps. 2 pocket dials have increased, 3 if I tap on the phone icon from messaging app to make call to that person, I have to exit out of the SMS app before I see the call screen. 4 sometimes when I'm multi tasking I go back to another app but the app reloads and doesn't take me to where I was. 5 Google now voice only responds 30% of the time when i say hello google. Some other problems I have noticed but can't think of right now
---------- Post added at 12:41 PM ---------- Previous post was at 12:38 PM ----------
Good thing I waited for a version that I could go back to kit kat because it didn't update the bootloader to lollipop. This is the thread if anyone is interested. I flashed this rom for xt1053 on my Rogers xt 1058, with only speaker phone not working away from WiFi for some reason, but that's if you flash on another moto x besides xt1053. http://forum.xda-developers.com/showthread.php?t=3155843

1. Battery drain (cell standby) makes the phone unusable.
2. WiFi does not connect or only works rarely now.

- download two times on whatsapp
- dialler doesnt dial a call
Sent from my XT1052

Cell Standby Battery drain is the worst..
Randomly restarting and optimizing apps has been a huge problem as well.

I miss the wave to wake for active notifications...
But what I really hate about 5.1, is that when using wifi my mobile radio keeps active all the time...
This drains the battery while being on wifi...
Funny enough, when I'm on mobile data, everything is ok and mobile radio is active only when needed by the apps...
On wifi on the other hand, oh man... it's active all the time...

Signal problem. Update: Info for others with issue and solutions.

After searching extensively on the whole Nexus 6 signal debacle. I've gotten some observations and studies to share and a couple questions.
I recently obtained a Nexus 6, which I already knew had the ! no data connection problem. (I tried to help the previous owner with the issue before, calls/texts would work, but data wouldn't) They were naturally on T-Mobile, so I assume it was related to the project Fi launch. Googling the issue recently states mostly T-Mobile and Sprint users having the issue, so I decided eh can't pass up a good deal! A like-new Nexus 6 for only $70, who can resist? I figured even if I get the no data issue, I can just turn on airplane mode, use as a mini-tab.
Here's where it gets interesting: I use Cricket (which is AT&T of course), popping the sim in results in good signal, LTE, etc as expected. Randomly (sometimes within 2 minutes) instead of the "!" on service problem, it drops to No Service completely. A reboot and it comes back fine, this wouldn't be too much of an issue except it happens EVERY 2-10 minutes. The only way to get it back is a reboot, airplane mode toggle doesn't help.
Which leads into the second part of the conundrum: Airplane mode doesn't help.
I figured I might just keep it in airplane mode and use as a tablet... The phone said no, Was fully charged before going to bed, by morning 17%. In airplane mode no less, which is of course is abnormal. Looking into it, it seems the phone never went into Deep Sleep, which I immediately delved into the cause. At this time I was running CM13 latest nightly, naturally I went for a fresh stock flash... Same issue. I even stock flashed to 5.0.0 and the same issue... Looks like hardware, but the randomness is the confusing part and you'd think if it was hardware a simple reboot wouldn't fix.
The phone never slept because when it would "No service" on me, I'd get wakelocks for "msm_hsic_host" which would keep the phone awake EVEN IN AIRPLANE MODE, which also in the battery settings showed the red bar for "bad" signal. This happens with AND without a sim, airplane mode or not. I'm currently on Pure Nexus and Franco's kernel to disable hsic wakelocks, and I'm seeing another one for "qcril_pre_client_init" when the issue happens. Which would be the Qualcomm radio interface layer, by the name, I'm assuming android is trying to turn on the radio and keeping the phone awake. This shouldn't happen in airplane mode, I've also tried "Toggle Cell Radio 5.0" to directly turn off the cell radio; Issue remains.
The randomness of when it happens, how it's "resolved" by a simple reboot, and the fact that airplane mode has zero effect on when it happens basically cripples it as a tablet as well, it never sleeps so the battery life is pretty crap (about 18%/hour screen off). After a reboot the thing is great as long as the thing has signal, runs cold, great life, charges fast, sleeps deep. Befuddled that it still does it without a sim card and airplane mode...
My question to the users here: If anyone else has any insight on this, and if anyone knows how to completely disable the cellular interface and literally turn it into a tablet. Is there any rom or such that doesn't try to wake/use the cellular radio and keep the thing awake.
EDIT: Yes, I've run the factory images from google, 5.0.0, 6.0, and 6.0.1 during testing.
The sim card is new, I've already changed it.
Yes the device is actually an XT1103, not a knockoff.
Sorry if any of this information wasn't clear enough.
Further Observations:
During the night I had zero reboots (It's setup to reboot on signal loss, so from here reboot == signal loss), then after taking it off of charge and turning the screen off, then back on after about 5 seconds the signal was lost and it rebooted.
This got me thinking, so on the way to work, I streamed music and had zero problems, not on the charger. After reaching work, I moved some offline music onto my phone and it acted fine as well. The phone never reboots if the screen is kept on as well.
This tells me it's something about how android switches to low-power on the cellular radio. Perhaps the radio cannot wake up properly from the low-voltage sleep state.
tl;dr
When phone is 'active' and not sleeping, problem doesn't arise.
Acts normal with screen off: Streaming music, Regular music, Plugged in.
Acts normal with screen on always.
If doing nothing and phone sleeps: reboots, usually on wake up (i.e. turning screen on to check time)
Likely issue with sleeping/low-power to the cellular radio.
Current bad "solution" play music with phone muted.
However, this doesn't seem to be too bad an impact on battery life, music player has used a total of 1% in the last two hours, screen is top again, where it was android os.
EDIT: Went all day without dropping signal by keeping music playing muted. At 52% after about 12 hours, 3 hours screen on, an hour VOIP call, wifi on the entire time. Not the best solution, but it's livable.
Further testing: I've tried a couple "keep awake" apps that set wakelocks and they do not seem to help, but this might be that they are not designed for marshmallow.
I've also "unoptimized" anything related to phone/cellular in the battery settings to prevent doze from sleeping them, no effect, double the apps directly hit the radio.

first off, first thing that I would do is fastboot flash the latest 6.0.1 factory image(then root it). as the issue sounds like a software problem. if it is, this would fix it. if it still is broken, then I'd root it for sure, then disable the cellular connectivity issue with my root access. without root, you are stuck with airplane mode, only.

simms22 said:
first off, first thing that I would do is fastboot flash the latest 6.0.1 factory image(then root it). as the issue sounds like a software problem. if it is, this would fix it. if it still is broken, then I'd root it for sure, then disable the cellular connectivity issue with my root access. without root, you are stuck with airplane mode, only.
Click to expand...
Click to collapse
I mentioned that I stock flashed... I tried 6.0.1 and even 5.0.0... Also I'm on a custom rom + kernel, so I kiiiinda have root access as well. I don't mean to sound uppity or anything, but did you even read my entire post? If you have a way to completely disable the cellular radio, by all means share. Only other thing I can think of to try tomorrow when I get time is to flash an incompatible baseband, but I can see it causing the same issue with I/O problems.

Skreelink said:
I mentioned that I stock flashed... I tried 6.0.1 and even 5.0.0... Also I'm on a custom rom + kernel, so I kiiiinda have root access as well. I don't mean to sound uppity or anything, but did you even read my entire post? If you have a way to completely disable the cellular radio, by all means share. Only other thing I can think of to try tomorrow when I get time is to flash an incompatible baseband, but I can see it causing the same issue with I/O problems.
Click to expand...
Click to collapse
By saying what you did that doesnt say if you went completely stock with the google images or some of the roms floating around. There is something in the background trying to force the device to connect to cell netowork. I would completely erase the device and make sure to format everything with the flash all bat file. You will ose everything on the device.
Also could be a lose connection in the hardware.

zelendel said:
By saying what you did that doesnt say if you went completely stock with the google images or some of the roms floating around. There is something in the background trying to force the device to connect to cell netowork. I would completely erase the device and make sure to format everything with the flash all bat file. You will ose everything on the device.
Also could be a lose connection in the hardware.
Click to expand...
Click to collapse
When I said stock, I meant the factory images from google... I've completely wiped the device several times. I'm not new to the entire process... That's why in my original post I stated possible hardware, but curious as to why it does it even in airplane mode when it shouldn't poll the cell radio at all. Further testing seems to say that disabling location access (I generally use battery saver, gps only for navigation), it holds signal longer. Potentially something wrong with how the system requests location.

Skreelink said:
I mentioned that I stock flashed... I tried 6.0.1 and even 5.0.0... Also I'm on a custom rom + kernel, so I kiiiinda have root access as well. I don't mean to sound uppity or anything, but did you even read my entire post? If you have a way to completely disable the cellular radio, by all means share. Only other thing I can think of to try tomorrow when I get time is to flash an incompatible baseband, but I can see it causing the same issue with I/O problems.
Click to expand...
Click to collapse
like was said, kinda sounded like you flashed a stockish kinda ROM. if not factory image, I recommend it.

Skreelink said:
When I said stock, I meant the factory images from google... I've completely wiped the device several times. I'm not new to the entire process... That's why in my original post I stated possible hardware, but curious as to why it does it even in airplane mode when it shouldn't poll the cell radio at all. Further testing seems to say that disabling location access (I generally use battery saver, gps only for navigation), it holds signal longer. Potentially something wrong with how the system requests location.
Click to expand...
Click to collapse
Are you sure it is a legit device? I have seen some knock offs have this issue.
You know we are all kinda dumb here. Myself included.
Run a logcat and see what is trying to connect.

zelendel said:
Are you sure it is a legit device? I have seen some knock offs have this issue.
You know we are all kinda dumb here. Myself included.
Run a logcat and see what is trying to connect.
Click to expand...
Click to collapse
Yes it is a legit device directly from tmobile. I'll do more testing tomorrow.

Maybe try a new sim card,only thing I can't think of

holeindalip said:
Maybe try a new sim card,only thing I can't think of
Click to expand...
Click to collapse
Already got a new sim, updated info in original post.

Attached a screen with battery info, from testing it's pretty accurate.

After implementing my "solution" for a couple days, it seems to sleep fine now without losing signal. Remember, I have tasker setup to reboot on signal loss so this is informative that it actually sleeps now...

Was the phone ever wet? The signal loss is common on my Nexus, as with my previous, always have missed calls etc, got a voicemail but no missed call notification. However it doesn't really describe the radio issue your describing. I'm almost certain the mother board is malfunctioning. The radio turns to low power mode in doze, but never returns to full power state. Seems to me that it's a communication issue from the motherboard. Neat idea for your "solution".
Sent from my Nexus 6 using Tapatalk

Jnewell05 said:
Was the phone ever wet? The signal loss is common on my Nexus, as with my previous, always have missed calls etc, got a voicemail but no missed call notification. However it doesn't really describe the radio issue your describing. I'm almost certain the mother board is malfunctioning. The radio turns to low power mode in doze, but never returns to full power state. Seems to me that it's a communication issue from the motherboard. Neat idea for your "solution".
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Phone has never been wet or suffered any trauma such as a drop or high temps. It's an odd little thing.

Try flashing a different modem?

dcrews said:
Try flashing a different modem?
Click to expand...
Click to collapse
I have, I think it's a hardware problem where the modem can't wake up from low power state similar to some cpus unable to wake if set too low.

Seemingly a breakthrough
Did a few more things and testing and I seem to have gotten onto something. I've attached screenshots showing just over 3 hours deep sleep and included battery info page. As a recap I couldn't get 10 seconds of deep sleep before tasker would wakeup the phone because it lost signal, then wait 30 seconds before rebooting it to get signal again, unless I was playing music (which kept the phone awake and thus never lost signal). You may notice on the upper left the carrier symbol, I'm on Project Fi and using Signal Spy to show which carrier I'm currently on. After doing my tests today it swaps carriers fine without ever completely dropping the radio and requiring a reboot to regain signal.
I'll do more tests and see how long, if it does to act up. If I seem to have actually found a real solution, I'll post what I did to resolve the issue just incase any other Nexus 6 users are experiencing problems.
Edit: Small note worth mentioning, wifi seems more stable as well. I'm able to keep AndroIRC connected with the screen off whereas I was having issues with it disconnecting randomly. This MAY just be due to something else, but still noting it here.

Strange behavior from Nexus 6 Display

My N6 is running Android 7.0, have not had problems until a couple of days ago.
The right half of my display started scrolling while, the left side of the display was normal. I powered it off and back on a couple of times and, the issue was still there; I panicked and did a factory reset from the "Settings" menu hoping that would solve the problem, it did not; I still had a jacked up display.
Is this a failure mode that anyone else has seen?
I powered the phone off and, turned it back on with the volume control button pressed and, it booted into safe mode(?) then, I toggled the mode to "Restart" and, upon restart, my display was normal. This was not the end as, it will occasionally be split screen when I unlock it. I have discovered that sometimes if I receive or make a call the display will return to normal, if not, I just power cycle it into the safe-recovery mode (but not do anything else) then toggle to restart and, it's all good until next time.
Is it possible that another device (blue-tooth) in close proximity could cause my phone display to act up?

queensgate555 said:
My N6 is running Android 7.0, have not had problems until a couple of days ago.
The right half of my display started scrolling while, the left side of the display was normal. I powered it off and back on a couple of times and, the issue was still there; I panicked and did a factory reset from the "Settings" menu hoping that would solve the problem, it did not; I still had a jacked up display.
Is this a failure mode that anyone else has seen?
I powered the phone off and, turned it back on with the volume control button pressed and, it booted into safe mode(?) then, I toggled the mode to "Restart" and, upon restart, my display was normal. This was not the end as, it will occasionally be split screen when I unlock it. I have discovered that sometimes if I receive or make a call the display will return to normal, if not, I just power cycle it into the safe-recovery mode (but not do anything else) then toggle to restart and, it's all good until next time.
Is it possible that another device (blue-tooth) in close proximity could cause my phone display to act up?
Click to expand...
Click to collapse
So weird, but same thing has been happening to me the past few days. But I have a justified cause. It started immediately after installing Franco Kernel.
Sent from my Nexus 6 using Tapatalk

queensgate555 said:
My N6 is running Android 7.0, have not had problems until a couple of days ago.
The right half of my display started scrolling while, the left side of the display was normal. I powered it off and back on a couple of times and, the issue was still there; I panicked and did a factory reset from the "Settings" menu hoping that would solve the problem, it did not; I still had a jacked up display.
Is this a failure mode that anyone else has seen?
I powered the phone off and, turned it back on with the volume control button pressed and, it booted into safe mode(?) then, I toggled the mode to "Restart" and, upon restart, my display was normal. This was not the end as, it will occasionally be split screen when I unlock it. I have discovered that sometimes if I receive or make a call the display will return to normal, if not, I just power cycle it into the safe-recovery mode (but not do anything else) then toggle to restart and, it's all good until next time.
Is it possible that another device (blue-tooth) in close proximity could cause my phone display to act up?
Click to expand...
Click to collapse
It is a known hardware issue in some N6 phones, some have it and it only shows up on certain rom / kernel combos, even stock. One thing that helps is to use the interactive kernel governor and/or the down sampling factor. Of course you will need a kernel manager app for that.
https://forum.xda-developers.com/showpost.php?p=63249802&postcount=4602

Pkt_Lnt said:
It is a known hardware issue in some N6 phones, some have it and it only shows up on certain rom / kernel combos, even stock. One thing that helps is to use the interactive kernel governor and/or the down sampling factor. Of course you will need a kernel manager app for that.
https://forum.xda-developers.com/showpost.php?p=63249802&postcount=4602
Click to expand...
Click to collapse
That's good to know.
I inserted the Bluetooth question because, coincidentally or not this issue presented when I acquired a wristwatch ($19.00 from China) that connected to my phone via Bluetooth, It had it's own fitness app which I installed (which did not work). To me, there seems to be more "connection" than expected as, the fault thing only seems to happen when the watch was powered on (but not even connected via Bluetooth). If there was a bug caused by the companion app, that should have been taken care of by the factory reset.
I'm going to do some "scientific testing" by, not powering on the watch for a week and see if the issue reoccurs. Meanwhile, I will read up on kernel manager apps.

I've since flashed stock pn, and now elementalx. It's not acted up yet. Seemes to be a better performance kernel. We'll see how battery is. Sorry to hijack your thread!
Sent from my Nexus 6 using Tapatalk

queensgate555 said:
That's good to know.
I inserted the Bluetooth question because, coincidentally or not this issue presented when I acquired a wristwatch ($19.00 from China) that connected to my phone via Bluetooth, It had it's own fitness app which I installed (which did not work). To me, there seems to be more "connection" than expected as, the fault thing only seems to happen when the watch was powered on (but not even connected via Bluetooth). If there was a bug caused by the companion app, that should have been taken care of by the factory reset.
I'm going to do some "scientific testing" by, not powering on the watch for a week and see if the issue reoccurs. Meanwhile, I will read up on kernel manager apps.
Click to expand...
Click to collapse
Well, so much for "scientific testing" and wishful thinking.....didn't take long to eliminate the wristwatch, now to fix the problem.
.