Moto 360 loses bluetooth connectivity on lollipop leak - Galaxy Note 3 Q&A, Help & Troubleshooting

Hi - downloaded the lollipop update on my N9005 (ver details below) and all works well except my moto 360 android wear device appears to lose connectivity.
The Android Wear app shows connected, the running notification says connected, but when I launch a voice command from the watch, very ocassionally i see 'Offline.'
Any ideas?
I have seen 'bluetooth fixes' that people have had to do after the Hong Kong update - not sure if I should do that anyway as bluetooth and wifi work, just that bluetooth is not as reliable as it used to be!!
ver details:
baseband : n005xxegbnl8
build number: LRX21.v.n9005xxugbnl8

bump
can someone please respond?

up
as above

My bluetooth to LG G watch also fails after about a day of connection, but a phone reboot always fixes it. Havent figured it out how to fix it other than that daily reboot

same issue
Same issue here. Would you happen to find a fix for it? I'm also googling.

khanbaloch said:
Hi - downloaded the lollipop update on my N9005 (ver details below) and all works well except my moto 360 android wear device appears to lose connectivity.
The Android Wear app shows connected, the running notification says connected, but when I launch a voice command from the watch, very ocassionally i see 'Offline.'
Any ideas?
I have seen 'bluetooth fixes' that people have had to do after the Hong Kong update - not sure if I should do that anyway as bluetooth and wifi work, just that bluetooth is not as reliable as it used to be!!
ver details:
baseband : n005xxegbnl8
build number: LRX21.v.n9005xxugbnl8
Click to expand...
Click to collapse
Hi I am having same issue! have you find solution?
Thanks!

I was on CM11 (snapshot) and I had connectivity drops between my 360 and N9005.
So I installed the Official Poland Lollipop ROM and thinks are good after that....

nijom said:
I was on CM11 (snapshot) and I had connectivity drops between my 360 and N9005.
So I installed the Official Poland Lollipop ROM and thinks are good after that....
Click to expand...
Click to collapse
Thanks will do the same!

On UK note 3 unbranded official lollipop and I have the same problem. Constant disconnects and the 360 telling me I am offline when in actual fact I am connected.. Even after a full factory reset of both devices the problem persists.. Not happy!

CONTACTMC said:
On UK note 3 unbranded official lollipop and I have the same problem. Constant disconnects and the 360 telling me I am offline when in actual fact I am connected.. Even after a full factory reset of both devices the problem persists.. Not happy!
Click to expand...
Click to collapse
I had same problem again and again. But now I gave my note 3 to my wife, I am using moto g2 with cm.

Am downloading the last kitkat rom I was on and reverting back.... Samsung suck atm... This update is 7 months late and is faulty.

Back on kit kat 4.4.2 and all works perfect again!

Related

Moto G KitKat OTA - Canada - Koodo

Folks,
I got an OTA update for the moto g. I'm on the Koodo network.
I downloaded the OTA update. Got the file from /cache.
Interesting the zip file i got has the name:
Blur_Version.173.44.9.falcon_umts.Telus.en.CA.zip
The OTA installer is telling me: 173.44.30.en.CA
The release notes had stated (can't find it now) that it has a fix for the OTG support and radio fixes like the UK and DE updates, PLUS a fix for Telus/Koodo customers that couldn't end their calls correctly.
Anyway i can't apply/update as i'm currently rooted. What are my options?
Be gentle, its my first android device.
------------------------------------------------------------------------------------------------------
Vector_Calculus said:
Folks,
I got an OTA update for the moto g. I'm on the Koodo network.
I downloaded the OTA update. Got the file from /cache.
Interesting the zip file i got has the name:
Blur_Version.173.44.9.falcon_umts.Telus.en.CA.zip
The OTA installer is telling me: 173.44.30.en.CA
The release notes had stated (can't find it now) that it has a fix for the OTG support and radio fixes like the UK and DE updates, PLUS a fix for Telus/Koodo customers that couldn't end their calls correctly.
Anyway i can't apply/update as i'm currently rooted. What are my options?
Be gentle, its my first android device.
------------------------------------------------------------------------------------------------------
Click to expand...
Click to collapse
I just updated although I'm rooted but Im using the original ROM
See this thread too: http://forum.xda-developers.com/showthread.php?t=2648590&page=13
you have to unroot
You can unroot quite easily and apply the OTA then root again.
You shouldn't loose anything: download the original ROM you are currently running (the telus 4.3) and extract the 3 parts of the system image, then flash them using fastboot.
Let me know if that's not clear enough, I'll find the Step by step instructions for you.
Just an update on the Koodo/telus patch (8.5mb)
I was originally running at 4.4.2 but after backup critical files i jumped in and rooted to get the fixed the update provided.
It worked! No issues. Root was preserved after the update.
My phone prior to update was at 4.4.2 (173.44.9) and after the update it went to 4.4.2 (173.44.30). Don't know why its not called 174.xxx like the other countries. It would nice if we all had the same patch naming schemes. Very confused tracking all the versions out there.
The fixes included:
"Fixed an issue which caused temporary cellular network loss for small number of moto G customers.
-Fixed wallpaper cropping issue
-Resolved USB OTG support issue with USB Drives
-Fixed low call volume by some users
-Fixed an issue with ending calls originated from a moto G on Telus/Koodo.
I actually the last item happened to me as both my wife and I have the motog and are on the same network.
Vector_Calculus said:
It would nice if we all had the same patch naming schemes. Very confused tracking all the versions out there.
Click to expand...
Click to collapse
Yes, the naming scheme is quite confusing, but despite the fact that my German version is 176, US version is 174 and yours is 173 after updates, obviously they got exactly the same patches as you listed. No worries.
Vector_Calculus said:
Just an update on the Koodo/telus patch (8.5mb)
I was originally running at 4.4.2 but after backup critical files i jumped in and rooted to get the fixed the update provided.
It worked! No issues. Root was preserved after the update.
My phone prior to update was at 4.4.2 (173.44.9) and after the update it went to 4.4.2 (173.44.30). Don't know why its not called 174.xxx like the other countries. It would nice if we all had the same patch naming schemes. Very confused tracking all the versions out there.
The fixes included:
"Fixed an issue which caused temporary cellular network loss for small number of moto G customers.
-Fixed wallpaper cropping issue
-Resolved USB OTG support issue with USB Drives
-Fixed low call volume by some users
-Fixed an issue with ending calls originated from a moto G on Telus/Koodo.
I actually the last item happened to me as both my wife and I have the motog and are on the same network.
Click to expand...
Click to collapse
I applied the update as well. However, my phone battery starts draining very fast, 50%+ overnight, with WiFi off. The phone seems not go to idle but running always.
xda127 said:
I applied the update as well. However, my phone battery starts draining very fast, 50%+ overnight, with WiFi off. The phone seems not go to idle but running always.
Click to expand...
Click to collapse
Battery drain is about the same as before. Maybe a factory data reset may help. I don't know if you lose root if you go this route..
xda127 said:
I applied the update as well. However, my phone battery starts draining very fast, 50%+ overnight, with WiFi off. The phone seems not go to idle but running always.
Click to expand...
Click to collapse
There is a camera bug on 4.4.2 that keeps the phone running after exiting the app. A fix is o the way...

Not receiving push notifications on Android when I'm connected to my Wifi

So, I'm facing a problem with my Samsung Galaxy s5 (sm-g900f). I can't receive push notifications for some apps (hangouts, whatsapp, gmail,..apparently all the apps using Google Cloud Messaging to push their notifications). I'm having this problem when I'm connected to my home Wifi only; when I turn off the wifi and switch to mobile data, all the delayed notifications arrive all at once. However, when I connect to other Wifis, everything seems to be working normal. Also note that, other phones work normally on my wifi (Samung galaxy s4 for instance). I've already done some troubleshooting:
1) I was using the stock android 5.0 (the Spain firmware) (I live in Lebanon) . I rooted my phone, the problem remained. I put a custom rom , didn't solve anything. Finally ,I unrooted the phone and I fully wiped it and installed the stock android kitkat (4.4.2) for Lebanon from sammobile.com, again with no luck.
2) I thought it was a router issue, so I changed my router.
3) I downloaded "push notification fixer".
4) I looked up the ports that GCM (google cloud messaging) uses, and I forwarded those ports to my phone's local IP.
Nothing of the steps mentioned made any difference. I'm sure there are still some troubleshooting I haven't tried; Can you help me? Thank you.
Same problem
I'm having a similar problem with a different phone, I have a Xperis E1
While running update with android 4.3 Jellybean it works fine
When i upgrade to android Kit kat 4.4.2 I get delays on my notifications, from a couple of minutes up to not receiving the notification until I unlock the phone manually.
So i've tried severral stock firmware and only when i use one based in 4.3 Jelly bean the problem never appears. My problem is this firmware has lots of bugs and misbehavior. So i Installed this one and hopped the best:
Xperia E1 D2004 official firmware Customized IL (Israel) 20.1.A.2.13 /R1B
Jellybean firmware with push notification working perfectly is:
Xperia E1 D2004 official firmware Customized GEL (Generic LAM) 20.0.A.1.21 / R3A

[Q] Has anyone had problems with Android Wear after upgrading to a 5.0 rom?

This has been mentioned somewhere else before but I haven't found a reliable solution .... after upgrading to stock 5.0 (SM-N9005, tried both saudi arabia and poland rom), my LG G Watch R keeps getting disconnected. More accurately, it disconnects when out of range and refuses to reconnect when back in range. Only rebooting the phone lets it connect again. This is extremely frustrating and it's a problem that seems to be localized to the Note 3. I'm considering downgrading back to kitkat (but I'm not even sure how to go about doing that). Anyone know of a solution?
HyperShad0w said:
This has been mentioned somewhere else before but I haven't found a reliable solution .... after upgrading to stock 5.0 (SM-N9005, tried both saudi arabia and poland rom), my LG G Watch R keeps getting disconnected. More accurately, it disconnects when out of range and refuses to reconnect when back in range. Only rebooting the phone lets it connect again. This is extremely frustrating and it's a problem that seems to be localized to the Note 3. I'm considering downgrading back to kitkat (but I'm not even sure how to go about doing that). Anyone know of a solution?
Click to expand...
Click to collapse
http://forum.xda-developers.com/galaxy-note-3/help/tw-lollipop-n9005-problem-bluetooth-t2990348
So solution yet, but workaround.
Thanks for replying. Sorry I didnt notice that thread before posting. The only workarounds seem to be using a BT autoconnect app which drains battery or else flashing a 16GB Hong Kong rom with pit file. I had tried doing that recently and ran into all sorts of problems and almost bricked my phone. I was lucky to recover from it. I may have perhaps used the wrong pit file or something, but in any case there's no way I'm trying that again. Can anyone point me towards a quick guide to downgrading back to kitkat? Is it a simple matter of flashing a stock kitkat rom, or will that cause problems?
had this issue on CM11
HyperShad0w said:
This has been mentioned somewhere else before but I haven't found a reliable solution .... after upgrading to stock 5.0 (SM-N9005, tried both saudi arabia and poland rom), my LG G Watch R keeps getting disconnected. More accurately, it disconnects when out of range and refuses to reconnect when back in range. Only rebooting the phone lets it connect again. This is extremely frustrating and it's a problem that seems to be localized to the Note 3. I'm considering downgrading back to kitkat (but I'm not even sure how to go about doing that). Anyone know of a solution?
Click to expand...
Click to collapse
I had this issue on CM11 kitkat and Moto 360.
After installing the Poland ROM it was great. I had no issue.

Gyroscope not working

Hi, after update my Huawei G7-01 from official Kitkat 4.4.4. to official Lolipop 5.1.1. build G7-L01C432B340 I have a problem with Gyroscope sensor and with app in googleplay store Google cardboard. Google plays says that i have not compatible phone. If I have Kitkat there isnt problem with this app. Can You help me? Sorry for my English
I think it's a known problem with Lollipop on the G7. I don't know if it is fixed in Marshmallow (as it hasn't been released for my country yet).
shweeney said:
I think it's a known problem with Lollipop on the G7. I don't know if it is fixed in Marshmallow (as it hasn't been released for my country yet).
Click to expand...
Click to collapse
OK, thanks for your answer. Im back on stock KITKAT 4.4.4 and gyro works perfectly.. But I do uprgrade to Lolipop, because bluetooth on my G7-L01 doesnt see bluetooth controler to th VR head set. In Lolipop mobile detected the bluetooth gamepad but G-sensor not work. Now on kitkat bluetooth doesnt see the gamepad and the G sensor works. Other Bluetooth phones on kitkat are detected, only gamepad no
Yeah, on all stock lollipop builds gyro not working. If you have root on your device and custom recovery, you can fix it by flashing this .zip file.

Slow speed wifi

Hi all,I have j500f model with marshmallow but when I download something from play store with wifi the speed of download is very slow,I reset the phone and router but the problem persist,with other phone the speed is good,is a problem with phone software,with 5.1.1 working fine.
Someone knows how to fix this issue?Thanks
Flash different 6.0.1 build from updato.com does the problem appear after flashing different 6.0.1 firmware?
Yes,I flashed many roms from updato without succes,the bug is still here,any ideas?
I flashed 5.1.1 from my country and I make all updates from ota and make reset but the bug is still there
aaddiy said:
Yes,I flashed many roms from updato without succes,the bug is still here,any ideas?
I flashed 5.1.1 from my country and I make all updates from ota and make reset but the bug is still there
Click to expand...
Click to collapse
Flash custom kernel...
I try hadeskernel but is not working...but with india latest mm is working fine is the only rom with no bugs for me,but not have my language.
I want to fix bug to working fine wifi with my country rom but I try everything for fixing..
I'm couriosly if this bug is only for me..
We recently got a new VM router and I've been having WiFi problems with my SM-J500FN (2015): Not exceeding download speeds more than 4 Mbps. I hear many others cant get no more than 4 mbps on their J5.
Nothing seemed to change the speed. Wipe cache partition only solved it just for about a minute. Keeping the phone in flight mode with Wi-Fi on does solve this problem but you won't be able to take/make any calls.
Fiddling around with the phone, I decided to turn Android Beam off to see if that would change anything. After that I did a speed test and got a stable 56 Mbps. This seemed to do the trick for me. It hasn't dropped back to 4 mbps since. I did the same thing on my gf's J5 (same model, same problem) and it fixed it as well.
Go to: Settings 》 NYC and payment 》 Android Beam
Now, if NYC is turned off turn it on just to switch Android Beam off.
I don't know what makes Android Beam interfere with Wi-Fi reception on the J5 but someone might be able to explain.
Not sure but this may help with the J5 (2016) too. It's worth a try.

Categories

Resources