Bluetooth will not turn off - HTC Aria General

I recently started Bluetooth to transfer some files to another phone and could not get the file to transfer. Since doing this I have not been able to turn off Bluetooth on my Aria (the sending phone). I am running stock 2.1, rooted.
Could Bluetooth be still trying to send the file and therefore not shutting off? Is there any way of fixing this or has anyone ever heard of this problem before? Would clearing the dalvik cache fix this w/o loosing all of my data and settings? What would clearing the cache partition do anyway?
I have tried rebooting several time with no luck. Any suggestions are welcome.
-Gary

BatteriesIncluded said:
I recently started Bluetooth to transfer some files to another phone and could not get the file to transfer. Since doing this I have not been able to turn off Bluetooth on my Aria (the sending phone). I am running stock 2.1, rooted.
Could Bluetooth be still trying to send the file and therefore not shutting off? Is there any way of fixing this or has anyone ever heard of this problem before? Would clearing the dalvik cache fix this w/o loosing all of my data and settings? What would clearing the cache partition do anyway?
I have tried rebooting several time with no luck. Any suggestions are welcome.
-Gary
Click to expand...
Click to collapse
You can try clearing the cache and dalvik cache, you won't lose any settings or data or anything like that. It also may be worth your while to look at what services are running (settings > applications > services (<- that was off the top of my head, could be a little different)) and see if you can stop the bluetooth service.
That's what I would do if i were in your situation.

Well, still no solution. I've tried clearing the dalvik and cache partitions, tried killing all of the processes related to bluetooth. When I try to uncheck the Bluetooth setting in wireless and networks it says "turning off..." removes the icon from the notification bar and then stops but never updates the menu item to "Turn on...". It is stuck at "turning off...". I'll have to scan for it with another phone to see if it is indeed off. Very odd. It may be time for 2.2 liberated.

BatteriesIncluded said:
Well, still no solution. I've tried clearing the dalvik and cache partitions, tried killing all of the processes related to bluetooth. When I try to uncheck the Bluetooth setting in wireless and networks it says "turning off..." removes the icon from the notification bar and then stops but never updates the menu item to "Turn on...". It is stuck at "turning off...". I'll have to scan for it with another phone to see if it is indeed off. Very odd. It may be time for 2.2 liberated.
Click to expand...
Click to collapse
I didn't say process, i said service

bump
I'm having the same issue here on my HTC Desire running froyo. Any solutions?

Here is what worked for me. I am rooted. I have bloat freezer installed. Had bluetooth share frozen. This morning I accidentally hit bluetooth widget instead of wifi. Bluetooth would not turn off just as OP described. I defrosted bluetooth share, powered off and back on, turned off bluetooth thru settings instead of trhu widget. And it worked. Off now. My theory is freezing bluetooth share had something to do with it but I'm no expert.

Related

[cm7] Wifi stuck on connecting..

HI, i had no problem with Wifi. Since last time I got to the hostel and have a weak access point I have a bug with Wifi : when I activate it, it says "connecting... ". But nothing happens, it doesn't list access point around me too.
I found a way to make it work: I uncheck Wifi, check airplane mode then check wifi again. It works but I have to do it every each boot or wifi deactivation..
Is there a parameters or cache file stocking the weak ap I was trying to connect when the bug appears at first?
Thank you
Problem not solved but changer: now it work but wifi is never activated at startup.. can't force it to auto activate. Strange...
Anyone else have this problem? I just started having it, first on Phiremod 6 and now just updated to 6.3 hoping for a fix, but no dice.
I have sent back 2 nooks to BN for exchange because of this issue. I didn't know doing the airplane mode thing would temporarily fix the issue. I even did the 8 hard reset and restore and the nook would get stuck on finding wifi window - turning on wifi but nothing would happen. My nook was manualnooted 1.2. Strange?
I'm on nightly-87, Dal's 1.2GHz OC Kernel 5/23, and I'm experiencing something very similar. I went from 7.0.2 to N87 without a hitch, but I immediately started to see the WiFi icon go gray and lose it's connection. I was forced to restart WiFi as a remedy. As of today I'm getting something closer to what you're talking about; when WiFi turns on, the nook will infinity cycle through: disconnected->connecting->disconnecting->scanning. I've wiped Cache, Delvik-cache many times to no avail. Also tried re-flashing N87 and the OC Kernel, which did not work. I'm still not able to connect to my home network(netgear, WPA). But, after enabling/disabling airplane mode, I was able to connect to my LG vortex and obtain the interbuttz.
The last time I did a fresh install was around N20 something. As far as possible causes to this erratic and ethereal bug, my money is on certain update paths for both the OS and Kernel having different remnants. Example: with 87 different experimental OS installs and, to a lesser degree, the three different stable OS installs. There are technically !90 different upgrade paths. Compounded by being paralleled by kernel installs, but I believe when a kernel is updated the former is completely replaced instead of merged. I'm not calling out the Dev's, it would be nearly impossible to foresee and head-off all of the permutations of merging 87+ releases.
I'm no expert, just my two-cents. I'm not really concerned about this as a long term bug. There are fine people hard at work, and unfortunately have far more pressing issues to contend with. It's a sad reality that community driven projects, notably the nook Color, rarely reach maturity or complete/efficient hardware-software integration before the allure and newness of a product wares off.
As a consumer of .rockbox, a Linux based OS for G5.5 ipods and below, Of which I've been using for years and years. And, I would say it's just now becoming 'perfect', even with it's lack of support for many peripheral devices. I'm long term with my gadgets.
I'm rambling now.
Hope this helps to narrow down symptoms and possible causes.
It seems that my problem is a known issue of cm7 (when you click airplane it stay on forever but the checkbox remains unchecked). Try a tool from market that shown me the airplane mode and unchecked it from here. Since I didn't reboot from that test I don't know if it's solved for now.
my NC on CM7 just stopped connecting too
I turned on my NC this morning and my WiFi no longer works either.
All of my hotspots say 'not in range'.
I tried all of the tools I have to turn off 'airplane' mode (just in case it was on)
but, nothing seems to get me 'out of the mode.
What can I try next?
Wifi miraculously auto-fixed itself, and then broke itself again
fulko said:
I turned on my NC this morning and my WiFi no longer works either.
All of my hotspots say 'not in range'.
I tried all of the tools I have to turn off 'airplane' mode (just in case it was on)
but, nothing seems to get me 'out of the mode.
What can I try next?
Click to expand...
Click to collapse
While researching potential solutions... CM7 auto-fixed itself after about 15 minutes.
I didn't touch it.
All of a sudden I heard the Gmail tool beep at me with new messages and the market with a few apps updates that were available.
Now it seems to be working fine.
I spoke too soon, I just powered off and on again to see if the problem was fixed
permanently, and its not... its back to the 'not working' state.
(I hate when that happens, because I don't know what caused it, and I don't know what fixed it!)
This happened (WiFi not hearing any APs) to me a few times with nightly 87, but hasn't happened since I upgraded to n94.
fulko said:
While researching potential solutions... CM7 auto-fixed itself after about 15 minutes.
I didn't touch it.
All of a sudden I heard the Gmail tool beep at me with new messages and the market with a few apps updates that were available.
Now it seems to be working fine.
I spoke too soon, I just powered off and on again to see if the problem was fixed
permanently, and its not... its back to the 'not working' state.
(I hate when that happens, because I don't know what caused it, and I don't know what fixed it!)
Click to expand...
Click to collapse
SAME! Bump.
Same issue.....latest nightly on VG SDcard solution. Never had a problem until recently. Was runnning 7.03(flawlessly) then suddenly started experiencing the issue, flashed the latest nightly (113)...worked for a bit, rebooted and now nada..... just sits at connecting..... then goes to disconnected. Cycles every couple of minutes.....
Any suggestions on what to look at?
**** Note ; WIFI works fine when I boot to EMMC (Nook 1.2) . So I do not believe this to be a hardware problem.
I was just looking for this issue also.
I was doing great with nightlies and the OC 6/18 kernal, this morning I updated to the Nightly 114, and I received no wifi connection on booting up.
So I did all the normal things (1. turn on/off the airplane mode - No change, 2. fixed permissions - no change, 3. restarted multiple time (aft all the prior changes) - no change) Ok I thought, I will go back to my previous nights backup (Nightly 113). But I still get no wifi. The widget says trying to connect, but none of my networks are showing up within range. I run wifi analyzer and I see NO networks (normally I would see about 5 to 7 of them).
So I begin stepping back, I reinstall the Nightly 113, with No OC, and while the wifi is off on bootup, once I 'turn it on' now I see my networks.
I'm cooking with gas now, so I install the OC 6/18 - No Wifi
So I install the OC 6/13 - Still no Wifi
Both times, the Nook boots up with the wifi 'off' so I turn it on, but no connection or sensitivity.
I again reflash the Nightly 113 only and while it again boots up with wifi 'off', I am able to turn it on and it actually sees my networks.
So strange, I am stuck without my OC kernal, but as least the nook works again.
Does anyone have an idea why this is happening to people?
Thanks
onclebob said:
It seems that my problem is a known issue of cm7 (when you click airplane it stay on forever but the checkbox remains unchecked). Try a tool from market that shown me the airplane mode and unchecked it from here. Since I didn't reboot from that test I don't know if it's solved for now.
Click to expand...
Click to collapse
The issue in the OP isn't related to the one you're talking about. Try deleting one or more of your remembered wifi access points with wifi on. Let it rescan and, if it's not some other issue, it should find your access points and connect.
Suffering this same issue as well on my Nook Color. I believe the problem lies under /data, and here's why. First, I made a backup of /data, and then wiped everything:
* I restored my device to factory 1.2: Wifi works
* I flashed CM7 nightly 113: Wifi works
* I flashed dalingrin's OC'd 6/18 kernel: Wifi works
* I restored /data from my backup: Wifi is stuck at "Connecting..."
I thought it might have something to do with the settings.db file under /data/data/com.android.providers.settings/databases/, but when I deleted that file and rebooted, it made no difference with the Wifi problem.
Something under /data might have a problem with the latest CM7 builds, but I couldn't say what exactly. I'm not an expert at this stuff, so I can only share what I've observed and tried for myself.
Hi. I have the same problems with Wifi since this morning. Is there any other solution then turning on and off airplane mode? thx
Formatted /system and /cache, and wiped the Dalvick cache, then flashed only CM7 nightly 143.
The problem still exists. Wifi is stuck at "Connecting..." Has anyone found a solution to this? It's obviously something to do with a setting/file under /data, because if I format /data, Wifi works like normal. But when I restore my backed up /data, Wifi is stuck at "Connecting..."
I think I found a solution. This worked for me, so I hope it works for others.
Shortly after writing my previous post above, I decided to play around with my NookColor, to see if I could get the Wifi to work normally again. Here's what I did, which fixed the "stuck at connecting" problem for me:
1) Go to Settings > Wireless & networks > Wi-Fi settings
2) Check to enable Wi-Fi, if it's not already enabled
3) Click every wireless network in your list and choose "Forget"
4) Make sure every wireless network is forgotten
5) Check to disable Wi-Fi
6) Check to re-enable Wi-Fi
Instead of "Connecting..." I now see "Scanning" and it picks up the routers around me! I selected my router, and it connected! I am now able to browse the web, update my apps, and all seems to be working normally now!
You can also watch if airplane mode is really off using Android assistant:
https://market.android.com/details?id=com.advancedprocessmanager&feature=search_result
it helped me with this problem
flansuse said:
I think I found a solution. This worked for me, so I hope it works for others.
Shortly after writing my previous post above, I decided to play around with my NookColor, to see if I could get the Wifi to work normally again. Here's what I did, which fixed the "stuck at connecting" problem for me:
1) Go to Settings > Wireless & networks > Wi-Fi settings
2) Check to enable Wi-Fi, if it's not already enabled
3) Click every wireless network in your list and choose "Forget"
4) Make sure every wireless network is forgotten
5) Check to disable Wi-Fi
6) Check to re-enable Wi-Fi
Instead of "Connecting..." I now see "Scanning" and it picks up the routers around me! I selected my router, and it connected! I am now able to browse the web, update my apps, and all seems to be working normally now!
Click to expand...
Click to collapse
That worked for me, thanks a ton!
flansuse said:
I think I found a solution. This worked for me, so I hope it works for others.
Shortly after writing my previous post above, I decided to play around with my NookColor, to see if I could get the Wifi to work normally again. Here's what I did, which fixed the "stuck at connecting" problem for me:
1) Go to Settings > Wireless & networks > Wi-Fi settings
2) Check to enable Wi-Fi, if it's not already enabled
3) Click every wireless network in your list and choose "Forget"
4) Make sure every wireless network is forgotten
5) Check to disable Wi-Fi
6) Check to re-enable Wi-Fi
Instead of "Connecting..." I now see "Scanning" and it picks up the routers around me! I selected my router, and it connected! I am now able to browse the web, update my apps, and all seems to be working normally now!
Click to expand...
Click to collapse
Man, you really had my hopes up with this one. You're the first person I've seen say every remembered network needs to be forgotten. But I followed your steps exactly, and my NC still will not connect. It sees all wireless networks available. It knows which ones are open and which ones are secured. I can go so far as to enter the password and click Connect. It says "Obtaining IP address from...", then quickly flashes "Unsuccessful", then "Scanning...", then loops indefinitely. I even took your steps one step further and rebooted before turning WiFi back on. Still doesn't work.
This is the fourth time this has happened to me. And every time, the only way I've been able to fix it is to completely reinstall CM7. That's not a fix, that's a wrecking ball. I'm pretty desperate to find a fix because my NookColor has become a joke, almost unusable. Right when I get it to the point of enjoying it and getting it set up just the way I want it, this happens. And the damn thing is useless without WiFi.
I also installed the latest nightly build, which was from last night. Nothing.

Wifi Not connecting

I have an interesting problem that is driving me crazy. I am running a rooted 2.3 version. If I reboot the phone with the wifi enabled it will connect to the network within range, and it will stay connected until out of range or wifi turned off.
HOWEVER, the second I disable wifi or try to do anything it will go through the motions, even say connected and show the icon in the notification bar (with no signal) then it immediately disconnects and starts popping up "unable to scan for networks" If i disable wifi and reenable it will do the same thing say connected, immediately disconnect and start erroring out again. I can see in logcat it gets an IP etc. assigned but it will not stay connected. Any ideas?
Oh and just in case someone suggests it, I have wiped the .conf file in the data/etc/wifi folder to no avail.
Who's version are you running? Did you do a Full wipe ( Data/ Cache ) before install, several times? Have you already tried booting into recovery wiping cache a few times and rebooting? Is there anything else weird going on? Did this just start or was it always an issue?

BT keeps turning off

For the past few days, my BT setting keeps turning itself off every few hours. Once it happens, it then continues to turn itself off immediately each time I re-enable it. After an hour or so, it recovers and lets me turn it back on (until the next time a few hours later).
The phone is completely stock (APK1), never rooted, no 3rd-party power-saving, task-managing, or security apps ever installed, no power-saving modes turned on. It does not help to clear the system cache or the Bluetooth Share cache. Closing all open apps does not help. Rebooting sometimes helps temporarily, sometimes not even temporarily. I haven't seen the problem when I reboot in Safe Mode, so either it's caused by an app (I have hundreds), or else I just didn't leave it in Safe Mode for long enough for the problem to reappear. I have not recently installed any apps or made any settings changes. I've searched online and come across many suggestions but none are applicable and successful here.
Is there a system log somewhere that would tell me what is turning off the BT setting?
Gary02468 said:
For the past few days, by BT setting keeps turning itself off every few hours. Once it happens, it then continues to turn itself off immediately each time I re-enable it. After an hour or so, it recovers and lets me turn it back on (until the next time a few hours later).
The phone is completely stock (APK1), never rooted, no 3rd-party power-saving, task-managing, or security apps ever installed, no power-saving modes turned on. It does not help to clear the system cache or the Bluetooth Share cache. Closing all open apps does not help. Rebooting sometimes helps temporarily, sometimes not even temporarily. I haven't seen the problem when I reboot in Safe Mode, so either it's caused by an app (I have hundreds), or else I just didn't leave it in Safe Mode for long enough for the problem to reappear. I have not recently installed any apps or made any settings changes. I've searched online and come across many suggestions but none are applicable and successful here.
Is there a system log somewhere that would tell me what is turning off the BT setting?
Click to expand...
Click to collapse
Try this my help.
Settings-> connections->more connection setting -> reset networks
Clicking from Edge of Galaxy.
norbarb said:
Try this my help.
Settings-> connections->more connection setting -> reset networks
Click to expand...
Click to collapse
Wouldn't that delete all my WiFi passwords? I find several online mentions of people who unsuccessfully tried Reset Networks to solve BT problems, and no mentions of it being successful.
Gary02468 said:
Wouldn't that delete all my WiFi passwords? I find several online mentions of people who unsuccessfully tried Reset Networks to solve BT problems, and no mentions of it being successful.
Click to expand...
Click to collapse
Yes, it will delete all your passwords. It help eith problem on my wife's s7 edge bluetooth.
Clicking from Edge of Galaxy.
norbarb said:
Yes, it will delete all your passwords. It help eith problem on my wife's s7 edge bluetooth.
Click to expand...
Click to collapse
Thanks, that's good to know. I'll consider it next.
UPDATE: Didn't help (but thanks for the suggestion).
Gary02468 said:
Thanks, that's good to know. I'll consider it next.
UPDATE: Didn't help (but thanks for the suggestion).
Click to expand...
Click to collapse
Try one more thing : Settings-> Applications-> in right top corner you have 3 dots, press and choose Show System Apps
scroll to Bluetooth share , click on it then click on Storage and Clear Data. go back and do same with Bluetooth Test.
Thanks, but that didn't help either. I found the culprit, though: the Walgreens app. When I force-stop it and then turn on BT, BT stays on. As soon as I start the app again, BT turns off. And I now see many other user reports of this problem, going back a couple of months.
It's annoying that without the user's knowledge or consent, Android gives an app unnecessary permission to turn BT off. What's worse is that there's no easy way to identify who turned it off.
Gary02468 said:
Thanks, but that didn't help either. I found the culprit, though: the Walgreens app. When I force-stop it and then turn on BT, BT stays on. As soon as I start the app again, BT turns off. And I now see many other user reports of this problem, going back a couple of months.
It's annoying that without the user's knowledge or consent, Android gives an app unnecessary permission to turn BT off. What's worse is that there's no easy way to identify who turned it off.
Click to expand...
Click to collapse
Very interesting info.
Gary02468 said:
Thanks, but that didn't help either. I found the culprit, though: the Walgreens app. When I force-stop it and then turn on BT, BT stays on. As soon as I start the app again, BT turns off. And I now see many other user reports of this problem, going back a couple of months.
It's annoying that without the user's knowledge or consent, Android gives an app unnecessary permission to turn BT off. What's worse is that there's no easy way to identify who turned it off.
Click to expand...
Click to collapse
There is an app in the store called App Brain Ad Detector.
After you install it you can scan all your installed apps and it will break down all permissions given to each app, show which ad network, etc. It is very useful!
Also after it is installed when you install a new app it will report if it does things not normal.. IE it would probably have caught that BT permission!

"Settings has stopped" and "Settings keeps stopping"

Hi, its my first time writing here, but not using this forum.
First of all, sorry if my english is not good enough.
I have a Nexus 6P stock, without root or anything. This week I installed Android 7.1.2 from google beta program, after that, I was having draining battery issue, so, I checked the battery usage and discover that the Wi-Fi never stop, then, after reading on some blogs about this problem and found that I should go to WiFi setting and disable some option in "keep wifi on sleep", however, when i click on setting key, always appear this messages "Settings has stopped" and "Settings keeps stopping". Things I did:
1) Disable Wi-Fi, try clicking on setting key - still the problem
2) Restart on safe mode - still the problem
3) clean the cache from recovery mode - still the problem
Any other suggestions without restoring the cell phone?
Thanks in advance
frax2050 said:
Hi, its my first time writing here, but not using this forum.
First of all, sorry if my english is not good enough.
I have a Nexus 6P stock, without root or anything. This week I installed Android 7.1.2 from google beta program, after that, I was having draining battery issue, so, I checked the battery usage and discover that the Wi-Fi never stop, then, after reading on some blogs about this problem and found that I should go to WiFi setting and disable some option in "keep wifi on sleep", however, when i click on setting key, always appear this messages "Settings has stopped" and "Settings keeps stopping". Things I did:
1) Disable Wi-Fi, try clicking on setting key - still the problem
2) Restart on safe mode - still the problem
3) clean the cache from recovery mode - still the problem
Any other suggestions without restoring the cell phone?
Thanks in advance
Click to expand...
Click to collapse
Hi... The gear icon force close... It's a bug in this beta version, nothing you should worry about.
However, I have no idea for your battery drain...
5.1 said:
Hi... The gear icon force close... It's a bug in this beta version, nothing you should worry about.
However, I have no idea for your battery drain...
Click to expand...
Click to collapse
Thanks for your anwser!
I'm very upset with the battery drain, I hope the next update come soon and fix my problem.
frax2050 said:
Thanks for your anwser!
I'm very upset with the battery drain, I hope the next update come soon and fix my problem.
Click to expand...
Click to collapse
Have You tried with - Settings - Location - press the 3 dots - Scanning - And disableing everything there ?
So...if I can't access the wifi settings is there any way to disable the wifi optimization or otherwise prevent it from dropping a wifi connection that it detects has no internet?
frax2050 said:
Hi, its my first time writing here, but not using this forum.
First of all, sorry if my english is not good enough.
I have a Nexus 6P stock, without root or anything. This week I installed Android 7.1.2 from google beta program, after that, I was having draining battery issue, so, I checked the battery usage and discover that the Wi-Fi never stop, then, after reading on some blogs about this problem and found that I should go to WiFi setting and disable some option in "keep wifi on sleep", however, when i click on setting key, always appear this messages "Settings has stopped" and "Settings keeps stopping". Things I did:
1) Disable Wi-Fi, try clicking on setting key - still the problem
2) Restart on safe mode - still the problem
3) clean the cache from recovery mode - still the problem
Any other suggestions without restoring the cell phone?
Thanks in advance
Click to expand...
Click to collapse
Unfortunately the only thing that usually fixes that is a factory reset. And if that doesn't work it's a ROM issue. Even though it's a stock ROM it happens.
Your best bet is probably a factory reset at this point. Usually if Settings or another system app is crashing on Stock, something is pretty messed up. You could either opt out of the beta and it will wipe/downgrade for you, or you can download a factory image from Google and install it manually if you're so inclined.
I have the same issue on my s6 after it updated to Nougat. Settings crashes every time if I try to open wifi, no matter what. Already wiped system cache and started in safe mode, but the problem is still there. Has anybody figured out a solution to this?
Did you try what was suggested..... ?
rchtk said:
Did you try what was suggested..... ?
Click to expand...
Click to collapse
I tried everything except factory reset, which I don't want to do yet.
I have this problem but I'm running Nougat on a stock "International" Samsung Galaxy S7.
I've tried factory resetting which fixed the issue for a while, but now it's come back.
Possible Fix Found!
frax2050 said:
Any other suggestions without restoring the cell phone?
Click to expand...
Click to collapse
I may have found a possible fix for this issue. Head over to this Android Central Thread where I've been discussing the issue with some other people.
Good luck!

[RETLA] Crash reboots after updating to Pie

Before updating I had the dolby app disabled. After the update it was still disabled but the service seemed to be running because it was affecting the audio quality, so I re-enabled it, turned off the dolby processing, and when I was about to disable the app back I got my first reboot. After it went on again I was able to disable it. Started playing some music to check if it was disabled and got another reboot. Now every once in a while happens. Has anyone else had the same problem?
m0ndul said:
Before updating I had the dolby app disabled. After the update it was still disabled but the service seemed to be running because it was affecting the audio quality, so I re-enabled it, turned off the dolby processing, and when I was about to disable the app back I got my first reboot. After it went on again I was able to disable it. Started playing some music to check if it was disabled and got another reboot. Now every once in a while happens. Has anyone else had the same problem?
Click to expand...
Click to collapse
Maybe try to force stop Dolby app then erase data and try again.
For now seems you're the only with this problem
Sent from my Motorola moto g(6) plus using XDA Labs
Made a factory reset, didn't disable anything and I have got at least two random reboots. How can I get a logcat of what happened before the reboot?
[EDIT] Found that the random reboots only happens when I'm at the office, connected to a hidden unmetered WPA2-protected Wi-Fi network.
m0ndul said:
Made a factory reset, didn't disable anything and I have got at least two random reboots. How can I get a logcat of what happened before the reboot?
[EDIT] Found that the random reboots only happens when I'm at the office, connected to a hidden unmetered WPA2-protected Wi-Fi network.
Click to expand...
Click to collapse
You run Catlog app (for example) and wait for the reboot. If it's plain that it only happens with that Wi-Fi connection, then just run Catlog, connect to WiFi, boom. Check logs afterwards
Has anyone found a solution?
I'm having the same issue. Has anyone found a solution? I already factory reset the phone, but the random reboots persists, and it's only when connected to my home router, it never occurs when wifi is off, and hardly when connected to other APs, wich is very strange.
My device is RETBR, I'm not rooted and never unlocked my bootloader.
Thought about reflash the rom, but i don't see how it would help.
Workaround
Hi, just updating this thread because I maybe have found a workaround. After I installed Blokada, witch uses a VPN, the phone stoped rebooting when connected to my home WiFi. Probably the VPN changes the way Android connects to the internet thus solving the problem. Blokada isn't a real VPN service, it only uses the API to creat a way to block adds, so other apps that uses VPN like that (1.1.1.1, intra, etc) should work as well.
This is a really weird bug, that onky happens in some specific conditions. I didn't found to much people reporting this, but if someone is having the same issue, I hope this "solution" could help.
Have you tried reflash to Oreo Stock?
Maybe after flash Oreo Stock your cellphone working fine.

Categories

Resources