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
Related
So a couple of months ago this started happening. I was running 5.0.1 and now I´m on 5.1 and it is the same.
Wifi is set to "always on". If the phone is blocked for a short time wifi works fine but if I don´t keep unblocking the screen it just turns off. It turns on automatically when I unlock the phone. This happens in any wifi network.
I know it´s more energy efficient this way but this is really anoying when having a phonecall over the internet, when using spotify or just when receiving whatsapp messages.
I did not wait for the OTA updates. I rooted my Moto G XT1032 to update from kitkat using the brazilian rom. I also used the GPE method to update to 5.1
Did I do something wrong? Is this a known lollipop issue? Any pointers? So far I´ve only found a couple of solutions involving installing a 3rd party app.
Thanks!
Try to flash a new ROM,wifi set and installing a third party app are two usual ways causing this problem ,if you are sure you have set right ,I think it is a ROM problem. Sorry for my English.
Hey guys,
2 days ago I updated my German z5 due pcc to Android 6.0. Since that I'm facing issues with my smartwatch. Directly after the update, I didn't get any connection to my watch again. I tried do reset the watch and installed android wear app new. Luckily the first connection is always possible, but after first setup I´m not able to connect again. Does anyone has another hint, then reset my z5 like the support of Sony did? I don´t have the feeling, that a reset would, because it is obviously a Bluetooth issue. Thanks for any help and see the screenshot attached. The screenshot shows, how android wear is always stopping when trying to get a connection.
Update:
Yesterday something strange happened. I settled my watch the whole day in it's loading station and in the evening I saw, that my watch was muted like my phone was. When I opened up android wear, I saw my watch was connected, also every app was synced. So I started to install some new wear app and the all get synced. But when I pulled up my watch from the loading station, the connection immediately got lost and until now, I'm not able to connect again. Now I'm pretty sure it is an Bluetooth bug, coming with the android 6.0 update of my z5.
z0rn said:
Update:
Yesterday something strange happened. I settled my watch the whole day in it's loading station and in the evening I saw, that my watch was muted like my phone was. When I opened up android wear, I saw my watch was connected, also every app was synced. So I started to install some new wear app and the all get synced. But when I pulled up my watch from the loading station, the connection immediately got lost and until now, I'm not able to connect again. Now I'm pretty sure it is an Bluetooth bug, coming with the android 6.0 update of my z5.
Click to expand...
Click to collapse
Completely remove the device, then re-add it and set as trusted device
danw_oz said:
Completely remove the device, then re-add it and set as trusted device
Click to expand...
Click to collapse
No changes. Sometimes it randomly connects and sometimes it is loosing the connection. :/
z0rn said:
No changes. Sometimes it randomly connects and sometimes it is loosing the connection. :/
Click to expand...
Click to collapse
So I have been reading about and there are loads of bluetooth issues with Marshmallow even with googles own Nexus devices I know it's not going to help you... http://ausdroid.net/2015/11/17/google-working-fix-nexus-6p-bluetooth-issues/ so I think google need to understand what the problem is a provide a fix for the other manufacturers to include.
My best guess is bluetooth is not behaving nicely in the new google ART cache which is supposed to fully replace delvik in Marshmallow.
Ever since I upgraded to Marshmallow 6.0 it would seem my Wifi won't stay on when the phone sleeps. This has started to cause me data issues so I was wondering if anyone else had these issues or a possible fix?
My wifi is set to stay on at all times.
6.0 removed stamina mode, there is currently no battery saving modes turned on
I have done a factory reset through the companion tool, but the issue still seems to occur
Thanks for any help, insights or assistance!
Which mm version do you have?
Phone is completely stock, no unlocks, roms or bootloader has been touched.
Android version 6.0
Kernel Version 3.10.84-perf-g19d6d92
Build Number 32.1.A.1.185
Sorry unsure if I answered your question I'm not familiar with what "mm" means.
vincent-h said:
Ever since I upgraded to Marshmallow 6.0 it would seem my Wifi won't stay on when the phone sleeps. This has started to cause me data issues so I was wondering if anyone else had these issues or a possible fix?
My wifi is set to stay on at all times.
6.0 removed stamina mode, there is currently no battery saving modes turned on
I have done a factory reset through the companion tool, but the issue still seems to occur
Thanks for any help, insights or assistance!
Click to expand...
Click to collapse
Same issue for me...
When my phone sleeps, sometimes wifi stay on, sometime not. I think it's a Marshmallow 6.0 issue...
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...
Hi, All
So, I'm trying to run custom ROMs as I want to set my HID_DEV_MTU_SIZE to 512 for amiibos, but every time I boot up the phone or manually turn Bluetooth on, it just says "turning on" and then turns itself off again, then back on, then off, then back on, then off... I can't get it to see any nearby bluetooth devices and the about section doesn't even show a Bluetooth address. It isn't an issue when I have stock OTA Android 10 installed, though...
I've reinstalled both Lineage 17 and Bliss more times than I can count, tried adding qcom.bluetooth.soc=smd to build.prop, disabling A2DP hardware offload; nothing works.
I've done a logcat several times, and it always comes up with bluetooth has died, not sure if that's of any help, though.
I know there have been other threads about this, but none of the solutions on those have helped, so apologies for starting another one.
I'm really lost at this point, any input would be greatly appreciated!
Thanks!!
Update: I installed Pixel experience and bluetooth works fine on there!
trainingtoothpaste said:
Update: I installed Pixel experience and bluetooth works fine on there!
Click to expand...
Click to collapse
Well i have in installed and its still troubleshooting... My device is Huawei p20 lite and Pixel Experience v13 installed