Database Users

HELP REQ - Stock Lollipop Note 3 N9005 - Random Reboots/Wifi-BT Clashes

Hi all,
Having a problem here.
Had my N9005 for about 18 months, never really had any problems with it - or rather, never really required anything of it which might manifest any problems.
I've always used Stock ROM's, soft-rooted.
Never triggered KNOX.
I'm currently running Stock Lollipop (latest Switzerland Open). Everything I'm about to elaborate is also the same using Stock Lollipop (latest UK Open).
I'm rooted on Lollipop using the method compiled by The TAMAS on XDADEV.
I root because my phone is work-critical, and so I use Titanium Backup to keep my data/calls/APN/SMS backed up and to make restoring easy, as well as to disable stock bloatware etc.
The problem may have pre-existed in pre-Lollipop ROM's, but the sequence of changes which caused it to be manifested included my need to update to Lollipop, about 5/6 months back.
THE PROBLEM - First and foremost, the damn phone reboots randomly. I become aware of it because it will vibrate for startup and play the Samsung startup tone and splash screen before booting to normal functionality. It can do this day or night, maybe 3-4 times a day. I have no error messages or warnings, it's done it while in my hand, while plugged in charging, while out and about, in the car, on wifi, on data. MOST times it reboots. SOME times it just shuts off and I don't realise it's off until I go to use it, or get a call on a second phone to ask why I'm not responding to calls or messages.
When it reboots itself, if I go to the Samsung Battery control panel pane and take a look at the battery chart it will show a gap which is longer than the time it took to reboot, and a shift in the battery meter level.
But, that's not the only possible symptom or problem with the phone.
I've noticed also that my WIFI does a lot of crapping out, or slowing to a crawl, even on my home AP. I've reset AP's, reset networks, reset the phone, forgotten and then reattached the AP in WiFi Settings. So I downloaded the Ookla Speedtest App, to see this issue in black and white, and sure enough, even though any other Android or iOS or Windows or OSX device in my place can connect via Wireless AP to my fibre connection and get great consistent throughput, the Note 3 can often appear crippled...
At it's best, it responds to ping quickly on the Speedtest app, and leaps up to the 30-40Mbps range with consistency for download, and up to 17-20Mbps for upload. This is the least I would expect it to do, my target standard.
At it's worst (which can be 'most of the time') it responds slowly to ping, and either struggles to get over 250Kbps download and maybe a crazy Meg or two for upload, consistently, a slow grind; or it may oscillate extremely wildly between slow and high speeds before eventually settling to unacceptably low transfer rates.
Up to press, I've been trying to chase these problems in isolation, believing them to be unconnected.
No success.
I've reflashed several times. I've Factory Reset. I've wiped data and cache. I've reinstalled and restored from Titanium. I've reinstalled and restored nothing but my SMS's and Call Logs. I've reduced my installed apps to bare minimums. I've tried it with a MicroSD installed, and without. I've bought another battery and replaced it. I've tried it in its case and without its case.
Then I started thinking that the problems were all the same thing, and stemming from the same root.
It suddenly occurred to me that my use of the phone changed significantly at the same time as I moved to Lollipop.
I need to be on Lollipop because apps and hardware that are critical to me are Lollipop dependent.
All at the same time, I began using a Moto360, a Bluetooth Receipt Printer and a Bluetooth Credit Card Reader, all of which are deficient in functionality or in some way hamstrung by not using Lollipop.
So I had gone from occasional BT user (maybe PlayerPro plus a BT link to headphones or my stereo occasionally; when needed, BT speakerphone in car) who usually turned BT off manually to preserve battery life, to a constantly connected BT user...
So I went back to Speedtest app, and tried to test the WIFI connection again. Sure enough, it was pitiful. Then I simply disabled BT on the N9005 and ran the test again, and had full 'through the roof' speed ratings.
I've tried this back and forth hundreds of times now, and it is predictable and established. BT is somehow crippling WIFI on my N9005.
I've tried running the phone on either wifi or data only, with BT off, and had a couple of days use at a time without any restarts. Put BT back on permanently, and the restarts resume within hours.
I'll be honest, I've even been cursing and swearing at my BT devices, because BT sometimes struggles to even maintain a continuous connection. I get vibrations all the time on my Moto360 indicating that the phone, which is on my person, has disconnected from the watch again, perhaps just for moments, sometimes for minutes, resulting in the watch eating battery life, trying to get reconnected.
I'm convinced now that all these things are related, and the problem lies somewhere in the interaction between BT and WIFI in my N9005.
It seems likely that I never noticed the problem before because I never required continuous BT connection before the point where I installed Lollipop.
Downgrading the ROM isn't an option. Leaving BT off isn't an option (nor should they have to be, on an 18 month old £600 smartphone).
Does anyone else have experience of this? Has anyone else had problems that they now suspect might be this same problem? Does anyone understand what's going on hardware/software wise, or have experience of a solution to these issues?
I'd appreciate your input urgently, even if only to affirm that I need to go to the inconvenience of temporarily buying another phone to replace this, while I send this away for a warranty repair.
Is this even a recognised hardware fault, or would I just get back an identical unit which is crippled from being able to perform as I expect it?
Please help.

Bluetooth turning itself off

I've had a search, but cannot see anything recent or apparent to my issue. When I try to connect my bluetooth headphones, they stay connected for about 2 seconds and are then disconnected, and will not reconnect. It turns my headphones off. I don't seem to have the same problem with my activity tracker, and I do not have the same issue when I connect my headphones to another device.
I have to say that for a flagship model I've had nothing but problems with this phone and I'll be glad to get rid of it. The sound quality was awful on MM but at least the OS was stable and the battery life decent. However since the update to Nougat I have had numerous instability issues and I have done numerous factory resets and cache cleans.
I have not rooted the device or done anything else that may have caused these issues, I think it's just poor quality Samsung software, and we're still on 7.0! Anyway back to the reason for the post, has anyone else had bluetooth problems?

Random reboots when/after listening to music

Hello,
I'm experiencing some weird problems on my Nexus 6P.
Everything was fine until like a month ago, when I tried switching to F2FS. I didn't notice any improvement and so I reverted to EXT4.
That is when the phone began randomly rebooting itself, often freezing while I was listening to music. (I have a huge music collection, like 15 to 18 GB, but I've never had this problem on any other phone)
At first I thought it was caused by maybe one of the music files being corrupted and forcing reboots, but I have the same music files on another, older phone and they work flawlessly.
Moreover the phone seems to be randomly rebooting after I listen to music, not always while I'm doing it, and even with streaming services.
What's worse is that it doesn't always reboot properly and most times gets stuck at the Google logo, then reboots again and so on. Bootloop.
I can always access recovery though, and re-flashing the rom (I'm on the latest PureNexus) seems to temporarily fix it.
Do you think I can fix this? If so, how? I'm afraid this may be a hardware issue :/

Lock screen freezes

Hello XDA,
This is my very first community post so please don't judge if I do something wrong here
Let's cut to the chase. I am a happy owner of the OP6T 8/256gb phone and I am super happy with the device, however, I have been having an awkward issue. From time to time, couple of times a day, my phone would not recognize neither double tap nor the power button to wake the display up. Usually out of frustration I press the power button couple of more time, but nothing happens. Then after 3-4 seconds the display wakes up and even opens the camera (because I pressed the button couple of times, but not in a fast way...). Afterwards, the phone works without an issue until same thing happens hours later.
So my question is if anyone is experiencing anything similar and found the culprit of it?
If you need any additional info on my settings, please let me know!
It is not the worst thing that could be happening with a new phone, but you know, one expects the brand new phone to work 100% of the time
Looking forward to your replies and ideas!
Many thanks,
Donatas

It's happened to me only recently. I'm rooted with magisk 17.3 running a few modules such as dual speaker, Google dialer framework and viper. I was on stock kernel, but switched to Smurf kernel without any hiccups so far.

Well I am full stock, even with stock launcher... That's why it bothers me that it is happening:/ thanks for your reply

Donis.za said:
Hello XDA,
This is my very first community post so please don't judge if I do something wrong here
Let's cut to the chase. I am a happy owner of the OP6T 8/256gb phone and I am super happy with the device, however, I have been having an awkward issue. From time to time, couple of times a day, my phone would not recognize neither double tap nor the power button to wake the display up. Usually out of frustration I press the power button couple of more time, but nothing happens. Then after 3-4 seconds the display wakes up and even opens the camera (because I pressed the button couple of times, but not in a fast way...). Afterwards, the phone works without an issue until same thing happens hours later.
So my question is if anyone is experiencing anything similar and found the culprit of it?
If you need any additional info on my settings, please let me know!
It is not the worst thing that could be happening with a new phone, but you know, one expects the brand new phone to work 100% of the time
Looking forward to your replies and ideas!
Many thanks,
Donatas
Click to expand...
Click to collapse
Yes this has happened to me, glad to see I'm not alone.
It happeneds randomly, like few times a day, not too frequent to render the device unusable, but enough to be irritating - especially when it's a brand new device.
My setup;
*Rooted
*Magisk (viper & YouTube vanced module)
*Stock kernel
I'm at a loss as to what's the cause of this issue, it's very weird, it could just be an oxygen os bug that will be resolved by OnePlus. Who knows. Hopefully if more people comment about this here - we will eventually get to the bottom of it.

So far on 9.0.6 build the issue appears to have been fixed, I have not had any random temporary lock screen freeze.
Can anyone else confirm this?

krohme said:
So far on 9.0.6 build the issue appears to have been fixed, I have not had any random temporary lock screen freeze.
Can anyone else confirm this?
Click to expand...
Click to collapse
Glad to hear it is fixed for you!
Unfortunately, since the update, I already experienced it 4 times...
Even more so, sometimes now the phone would randomly stop playing music from Soundcloud (I dont know about other apps, i predominantly use Soundcloud).
I love the phone but it is a little shame that some of these features are failing
Hope 1+ will fix this and we all be happy!

Yeah, sometimes my device doesn't respond to double-tap. Usually I just have to double-tap again and it wakes up. I haven't noticed the issue with the power button, but I rarely use that to wake the device. I did have a situation recently where the device wouldn't wake from a screen tap no matter how many times I tried. I can't recall if using the power button woke it or if I had to force a reboot. But that's only happened that one time.
I just updated to 9.0.6 a day ago. I don't think I've experienced any non-wake issues since then. Really haven't been paying that close attention, I guess.

I believe I am having this issue. I just flashed 9.0.7 from TMO and I'm rooted with magisk v4a and vanced. I get random freezes where I can't tap anything on my screen. I have to turn it off and on with the power button.

I experience this as well. I thought it was just an isolated thing, and it's kinda annoying...

It's very irritating. I'm trying to pin point it and so far I notice it with Firefox and Spotify transitions.

Weird System Bugs/ Issues Stock

Hi, I have owned a One Plus 6T for a few years now, didn't have many issues, until the last few months. I used to be on Android 10. (something) can't remember and the issues I'm about to describe happened on that version too. I have recently updated to Android 11.1.1.1 and the problems still persisted. And I've run a factory reset a few days ago and that still hasn't solved the issues. My bootloader is unlocked and I am not rooted.
Issues:
1. Phone randomly rebooting (almost like there isn't any RAM but there's over a gig spare) eg Ill be listening to spotify and suddenly phone reboots
2. Extreme System UI delay/lag and screen lag. This is the weird one. Happens at completely random times. Phone will slow down extremely to the point where nothing will be responding. For example if I click the power button to look at the lock screen the screen will just stay black for ages. Apps will not open etc. Can barely even swipe or do anything, it happens multiple times a day too.
I was wondering if anybody knew why this might be occurring, considering I am running a fresh install, unless it comes down to just bad software.