i know the title looks pretty weird but i was on Android Nougat Until yesterday
i flashed the latest official firmware for my J7 2016 (J710F) which is based on Oreo 8.1
the funny thing is since i flashed the rom the WIFI never take a break its like keep connecting to something
can anyone confirm that?>
i didn't attach any screen shots because i think it doesn't worth it.
by the way this is the first time i encounter something like this in phones
is there anyway to prevent it?or at least to monitor the wifi traffic so i can block it with hosts file or something i didn't root yet but i found working method
randomexpert said:
i know the title looks pretty weird but i was on Android Nougat Until yesterday
i flashed the latest official firmware for my J7 2016 (J710F) which is based on Oreo 8.1
the funny thing is since i flashed the rom the WIFI never take a break its like keep connecting to something
can anyone confirm that?>
i didn't attach any screen shots because i think it doesn't worth it.
by the way this is the first time i encounter something like this in phones
is there anyway to prevent it?or at least to monitor the wifi traffic so i can block it with hosts file or something i didn't root yet but i found working method
Click to expand...
Click to collapse
Did you disable the option in wifi settings to turn wifi ON automatically?
finac94 said:
Did you disable the option in wifi settings to turn wifi ON automatically?
Click to expand...
Click to collapse
i guess i was just paranoid nothing is weird looks like after flashing latest stock firmware Oreo 8.1 it tries to download additional stuff in the background
Related
The Wi-Fi on my wife's unrooted Nexus 5 (Sprint version) which was upgraded (via OTA) to Marshmallow last month suddenly stopped working last week. The slider would get hung while moving from Off to On (like it was trying to turn on) and therefore was not detecting any available Wi-Fi signals.
After trying many things, I eventually did the extreme and did a full factory data reset. No dice. Still not detecting anything.
Figuring it might be an OS issue with Marshmallow (given we're seeing a lot of forums indicating Nexus 5 issues based on Wi-Fi with both Marshmallow and Lollipop), we downgraded the OS first to Lollipop and then all the way back to KitKat (4.4). Still not working. At initial phone setup, the phone is not detecting any available WiFi signals and gets hungup trying to find networks for me to choose from - so I end up having to skip this step.
Any other tips out there on what I can try? Is this a sure sign of hardware problems? Don't think my wife's phone is under warranty any longer (have had it slightly over a year, I think).
PS - Now I can no longer even upgrade the phone (OTA, at least) from 4.4.4 because my phone is saying it needs Wi-Fi to download the update - with no option to do it over my data plan.
I'm in the same situation and it appears to be a hardware failure. The wifi chip can't be replaced so a motherboard swap is required.
You can upgrade to the latest stock ROM by flashing the entire ROM from a command prompt in Win7.
Plot thickens
So, I figured out a way to get the OTA's over LTE (by manually changing my phone's date up a week). While going through each OS update from 4.4 KitKat to 6.0 Marshmallow (about 5 or 6 rounds of them) my phone briefly was able to detect WI-FI, I believe during set up at 5.1.1 Lollipop - and I was able to get on my home network.
Probably should have just stopped updating after that, but definitely was not detecting anything after that. I lost it during one of the Lollipop updates - well before getting to 6.0. Not sure if WiFi was actually working well or not.
Maybe the chip is in the process of failing? Not sure but it seems like you are having better luck than me.
audit13 said:
Maybe the chip is in the process of failing? Not sure but it seems like you are having better luck than me.
Click to expand...
Click to collapse
I wish. Don't want to go through all those steps again after doing a clean wipe to have a fleeting glimpse of Wi-Fi.
pagalbengal said:
So, I figured out a way to get the OTA's over LTE (by manually changing my phone's date up a week). While going through each OS update from 4.4 KitKat to 6.0 Marshmallow (about 5 or 6 rounds of them) my phone briefly was able to detect WI-FI, I believe during set up at 5.1.1 Lollipop - and I was able to get on my home network.
Probably should have just stopped updating after that, but definitely was not detecting anything after that. I lost it during one of the Lollipop updates - well before getting to 6.0. Not sure if WiFi was actually working well or not.
Click to expand...
Click to collapse
Hi, pagalbengal. I'm having the same problems right now, and I wanted to check with you to see if there have been any developments with your situation over the past month. Still hopeless? Have you contacted Google tech support? Do they still even support this phone? Thanks for any info.
You guys might want to try reflash the modem firmware.
Couldn't get my wi-fi to work so I replaced the motherboard. Every stock and custom ROM I tried could not enable wi-fi.
Hi guys, just installed the proper Nougat clean install via Flashtool and rooted the device. I noticed that Bluetooth turns itself off every now and then and doesn't turn back on. Is this happening to anybody else ? I usually use the Moto 360 v2 with the Z5 and on MM, it doesn't happen that way.
LunatikBunnie said:
Hi guys, just installed the proper Nougat clean install via Flashtool and rooted the device. I noticed that Bluetooth turns itself off every now and then and doesn't turn back on. Is this happening to anybody else ? I usually use the Moto 360 v2 with the Z5 and on MM, it doesn't happen that way.
Click to expand...
Click to collapse
Im using the smartwatch via bluetooth and everything's fine
I think I found out why. Greenify's aggressive doze seems to be the culprit. Once I got that turned off Bluetooth stays on
Seems like even uninstalling greenify didn't work for me, Bluetooth still turned off after a while. Will continue to look for the root cause and solutions and post if there's a solution.
Feel free to chime in if anybody has answers
What is your kernel, ROM, etc.. ? I think if you have LineageOs 7.1.1 it's a bug caused by the ROM, I had this bug previously. So, try to return to 6.0.1 Marshmallow and retry with your Android watch.
Just got the official Nougat update (32.3.A.0.376) a few days ago, and I'm also getting the same issue on my Huawei Watch. Can't find any setting to keep it from turning off Bluetooth. It's starting to annoy me, honestly. But the rest of the phone is largely improved since the update, so overall, I'm OK with staying with the Nougat build.
SW3 here no problems. .372.
stock .376 rom doesnt have any issues with bluetooth and SW3
Hey guys, I was wondering if anyone else has this problem. When using the official COS 13 rom everything works but GPS is slow to get a fix and when it does, it is out of sync i.e. position is further back or forward from my real location.
When I flash to Nougat, GPS works as it should, locks pretty quickly and is accurate. I've tried changing modem firmwares, using TopNTP to patch the gps.conf file and nothing seems to work in COS 13, which is the OS I prefer since Kali Nethunter works on it with no hitches.
I would really like to go back to COS13 but I use GPS occasionally and as the old saying goes, you only wish you had it when you need it the most. Any help or thoughts would be appreciated. Thanks.
Guess no one else ever heard about this.
It's not that nobody has heard of it, but you're asking about an issue with an older version of Android that is no longer being actively developed, and due to security flaws is no longer safe to run on your handset. As with all versions of Android, the code is open sourced, so you are more than welcome to dig into the source code, get your hands dirty, and fix anything you want, but expecting anyone else to fix an issue on a deprecated OS is a bit much, IMHO.
Never asked if anyone can fix it, I won't be so bold since I never did any Android development myself, hence is stated I flashed different firmware and used GPS.conf apps etc just asked if anyone else came across this issue since at one point in time we were all on cos13 and if it could be solved by flashing a zip or editing a conf file.
Hey guys,
I'm living and working with my Z5 Dual since years and I have the latest Lineage OS with the updates it brings (old Android 7.1.2, latest and last update as of 5 February). But I am getting more and more annoyed by two things which drives me into severe considerations what to do next: changing the phone? changing the custom rom?
The issues I face with the latest Lineage Os are the following:
I cannot connect--although trying everything--my electronic scooter via bluetooth with the app of the provider (it's name is SoFlow). The app on all other Android devices I have, stock Samsung and custom roms all see and connect to the scooter.
My Wifi connection drops always after a couple of minutes when the Z5 screen is not used and the display turns off. That is super annoying and it only re-connects as soon as Ihit the power button to turn on the screen.
So my questions are now: Can anyone provide me with useful help regarding issues 1 or 2 on the latest Lineage OS? And if not: what can I do, should I switch to a different custom rom (which one, maybe Carbon Rom, maybe another One?) or should I go back to a rooted stock rom? Any help is appreciated. i know the devices is old and Android 8 or 9 is as unlikely as nothing else at the moment, but at least the issues mentioned should not be there in Android 7...
So I did a factory reset from 11 and upgraded to 13. Been on the fence about downgrading until I tired it on my work vans Uconnect Bluetooth and it wasn't crashing it (Was a known issue) and was like ok maybe i can live with the other stupid issues like it not auto playing Pandora when a Bluetooth device connected.
Well when I try to enable hotspot it says "to use personal host spot you need to subscribe to Personal Hotspot Services". Worked just fine on 11. I got Verizon in the US. I am Rooted and on latest security updates on stock OOS13. When I go online or use the stupid automated service it just says my device doesn't support it.
Willing to go back to 11 (Honestly feature wise it just seemed the best overall with the exception of my work van which I can live without) or use a different tethering app if out there.
drtweak said:
So I did a factory reset from 11 and upgraded to 13. Been on the fence about downgrading until I tired it on my work vans Uconnect Bluetooth and it wasn't crashing it (Was a known issue) and was like ok maybe i can live with the other stupid issues like it not auto playing Pandora when a Bluetooth device connected.
Well when I try to enable hotspot it says "to use personal host spot you need to subscribe to Personal Hotspot Services". Worked just fine on 11. I got Verizon in the US. I am Rooted and on latest security updates on stock OOS13. When I go online or use the stupid automated service it just says my device doesn't support it.
Willing to go back to 11 (Honestly feature wise it just seemed the best overall with the exception of my work van which I can live without) or use a different tethering app if out there.
Click to expand...
Click to collapse
You can try updating to the latest OOS13.1 (and check if it fixed this issue) or revert to OOS11.
Rootk1t said:
You can try updating to the latest OOS13.1 (and check if it fixed this issue) or revert to OOS11.
Click to expand...
Click to collapse
Already On 13.1 April 5 security