I have a Sprint Note 4 and until I rooted it my watch connected fine, worked great, looked great with the Pebble Steel band. Now it fails to connect no matter what I do. I have done everything I know to do as a fairly experienced phone geek. Outside of unrooting and reinstalling the stock ROM I cannot get it to connect.
My question is: Do I now need to root my watch so I it will connect to my phone?
EdHicks said:
I have a Sprint Note 4 and until I rooted it my watch connected fine, worked great, looked great with the Pebble Steel band. Now it fails to connect no matter what I do. I have done everything I know to do as a fairly experienced phone geek. Outside of unrooting and reinstalling the stock ROM I cannot get it to connect.
My question is: Do I now need to root my watch so I it will connect to my phone?
Click to expand...
Click to collapse
I'm using my unrooted Moto360 with my rooted Sprint Galaxy S5 running a custom Tom. No problems connecting.
EdHicks said:
I have a Sprint Note 4 and until I rooted it my watch connected fine, worked great, looked great with the Pebble Steel band. Now it fails to connect no matter what I do. I have done everything I know to do as a fairly experienced phone geek. Outside of unrooting and reinstalling the stock ROM I cannot get it to connect.
My question is: Do I now need to root my watch so I it will connect to my phone?
Click to expand...
Click to collapse
Did you reset the watch and reinstall on android wear on your device?
Ramer said:
I'm using my unrooted Moto360 with my rooted Sprint Galaxy S5 running a custom Tom. No problems connecting.
Click to expand...
Click to collapse
Where did you get a custom Tom? [emoji12]
No problems connecting my stock 360 with my xperia ultra running slimkat
joshm.1219 said:
Did you reset the watch and reinstall on android wear on your device?
Where did you get a custom Tom? [emoji12]
Click to expand...
Click to collapse
Darn auto-correct. lol
joshm.1219 said:
Did you reset the watch and reinstall on android wear on your device?
Where did you get a custom Tom? [emoji12]
Click to expand...
Click to collapse
I reset the watch, reinstalled Android Wear and tried to re-pair, no success. Even Factory reset phone and installed Android wear and then try to re-pair. No success.
The only time I was able to re-pair was by unrooting.
We'll see what happens when I upgrade to 5.0.1. In the process of upgrading, re-rooting, re-installing TWRP and then VisionX Rom.
If I have to I will root the watch. I was just curious if my problems were root related.
EdHicks said:
I reset the watch, reinstalled Android Wear and tried to re-pair, no success. Even Factory reset phone and installed Android wear and then try to re-pair. No success.
The only time I was able to re-pair was by unrooting.
We'll see what happens when I upgrade to 5.0.1. In the process of upgrading, re-rooting, re-installing TWRP and then VisionX Rom.
If I have to I will root the watch. I was just curious if my problems were root related.
Click to expand...
Click to collapse
Could you link me to the root method you used? Root access is simply enabling you control of the /system partition and if done properly shouldn't be affecting anything like your Android Wear connection.
I am using my Moto 360 on rooted Sprint Note 4 without issue. I actually had issues with the watch staying connected until I rooted my Note and flashed a custom rom. Uninstalling Android Wear and Moto Connect then factory resetting the 360 to go through the whole pairing process again resolved all issues I had.
joshm.1219 said:
Could you link me to the root method you used? Root access is simply enabling you control of the /system partition and if done properly shouldn't be affecting anything like your Android Wear connection.
Click to expand...
Click to collapse
The latest CF Auto Root at the time.
My (unrooted) Moto 360 connects just fine with my rooted YotaPhone 2...
I suspect that rooting isn't the culprit, but installing a custom ROM.
Custom ROMs usually involve removing/adding/replacing files, and you can't always be sure that the required files for Android Wear connection are still present in the custom ROM you're using...
Things you might want to try, if not already done, are installing another custom or vanilla ROM,
and/or connecting another Android Wear watch to your phone with the initial custom ROM.
Good luck, anyway! I hope you can find a way out of this situation...
Update
Thanks to everyone for all the help.
Since the Lollipop update all is functioning properly. I'm still curious as to why I rooted the phone and it wouldn't connect just to learn why...
it has always worked fine with my Rooted Nexus 6, glad you where able to get it working again!
Related
Greetings, I wonder if somebody can solve the following problem. I'm from Venezuela and I bought this model GT-I9192 in December 2013 when the update came out this year it was updated from 4.2.2 (JellyBean) to 4.4.2 (KitKat). I almost never use the camera of this phone and then I noticed that every time I opened the camera app I would get "Warning: Camera Failed". Thinking it was the update I proceeded to install the Cyanogenmod rom 11 for this model, but continued with the same problem. The flash works every time I turn the flashlight application. I took it to a technician telling me that the problem was not hardware but software. This is where my troubles began. I do not remember which firmware was installed. I tried to install several firmwares 4.2.2. but without success all with flashing failures. However, I could install version 4.4.2 of Trinidad and Tobago but with the same camera error. Hopefully someone can help me with this problem. I would like to know exactly what firmware should download to install? Thank you very much.
nelson2006 said:
Greetings, I wonder if somebody can solve the following problem. I'm from Venezuela and I bought this model GT-I9192 in December 2013 when the update came out this year it was updated from 4.2.2 (JellyBean) to 4.4.2 (KitKat). I almost never use the camera of this phone and then I noticed that every time I opened the camera app I would get "Warning: Camera Failed". Thinking it was the update I proceeded to install the Cyanogenmod rom 11 for this model, but continued with the same problem. The flash works every time I turn the flashlight application. I took it to a technician telling me that the problem was not hardware but software. This is where my troubles began. I do not remember which firmware was installed. I tried to install several firmwares 4.2.2. but without success all with flashing failures. However, I could install version 4.4.2 of Trinidad and Tobago but with the same camera error. Hopefully someone can help me with this problem. I would like to know exactly what firmware should download to install? Thank you very much.
Click to expand...
Click to collapse
I registered here just to answer your question.
My Android expertise is very limited but I try to learn from past experience. If I understand correctly, your want:
1. the camera should work.
2. the phone should function properly.
If you do not remember your original firmware, do not worry as it does not matter. Once your upgraded to KK, Knox (google it) kicked in to prevent you from downgrading to JB. That's why all flashing efforts to downgrade failed. So, you can keep your phone with KK if the phone works except camera. In case you want to downgrade to JB, I am sure that able XDA members can help you with that. I am unaware if such methods exist.
Now, to see if the camera works there are several methods. I encountered the same problem with my wives i727 Skyrocket which has JB 4.1.2 installed. One day the camera suddenly failed with the error "Warning: Camera Failed". The flash-light worked flawlessly so I was a bit perplexed. I researched and found several remedies:
1. From application manager, clear cache/data of the camera app and restart phone - Tried this several times, did not work.
2. Perform factory reset- Thought I'd use it as a last resort as the phone had gigs of data in it.
3. Uninstall apps (last installed app uninstalled first and so on) - I uninstalled the last installed app and restarted the phone. Voila! The camera was back. I have no explanations why but it just worked.
Let us know how it goes, good luck!
On the i9195, it is possible and easy to downgrade to JB since there's a 4.2.2 firmware which is similar to the 4.4.2 firmwares, but I don't know about the i9192.
Be careful with this;
If you know what you are doing, get the CWM recovery, format system/data and flash a 4.4.2 firmware again. If that didn't fix it, I suspect that it's a hardware problem and it's having problems with the software, but there should be something wrong with the hardware, for sure.
Good Luck.
snipar said:
I registered here just to answer your question.
My Android expertise is very limited but I try to learn from past experience. If I understand correctly, your want:
1. the camera should work.
2. the phone should function properly.
If you do not remember your original firmware, do not worry as it does not matter. Once your upgraded to KK, Knox (google it) kicked in to prevent you from downgrading to JB. That's why all flashing efforts to downgrade failed. So, you can keep your phone with KK if the phone works except camera. In case you want to downgrade to JB, I am sure that able XDA members can help you with that. I am unaware if such methods exist.
Now, to see if the camera works there are several methods. I encountered the same problem with my wives i727 Skyrocket which has JB 4.1.2 installed. One day the camera suddenly failed with the error "Warning: Camera Failed". The flash-light worked flawlessly so I was a bit perplexed. I researched and found several remedies:
1. From application manager, clear cache/data of the camera app and restart phone - Tried this several times, did not work.
2. Perform factory reset- Thought I'd use it as a last resort as the phone had gigs of data in it.
3. Uninstall apps (last installed app uninstalled first and so on) - I uninstalled the last installed app and restarted the phone. Voila! The camera was back. I have no explanations why but it just worked.
Let us know how it goes, good luck!
Click to expand...
Click to collapse
I haved tried the first two steps and no luck at all. Maybe this weekend I'll try the third one. Thank you for the reply.
snipar said:
I registered here just to answer your question.
My Android expertise is very limited but I try to learn from past experience. If I understand correctly, your want:
1. the camera should work.
2. the phone should function properly.
If you do not remember your original firmware, do not worry as it does not matter. Once your upgraded to KK, Knox (google it) kicked in to prevent you from downgrading to JB. That's why all flashing efforts to downgrade failed. So, you can keep your phone with KK if the phone works except camera. In case you want to downgrade to JB, I am sure that able XDA members can help you with that. I am unaware if such methods exist.
Now, to see if the camera works there are several methods. I encountered the same problem with my wives i727 Skyrocket which has JB 4.1.2 installed. One day the camera suddenly failed with the error "Warning: Camera Failed". The flash-light worked flawlessly so I was a bit perplexed. I researched and found several remedies:
1. From application manager, clear cache/data of the camera app and restart phone - Tried this several times, did not work.
2. Perform factory reset- Thought I'd use it as a last resort as the phone had gigs of data in it.
3. Uninstall apps (last installed app uninstalled first and so on) - I uninstalled the last installed app and restarted the phone. Voila! The camera was back. I have no explanations why but it just worked.
Let us know how it goes, good luck!
Click to expand...
Click to collapse
RoyaLKurTx3 said:
On the i9195, it is possible and easy to downgrade to JB since there's a 4.2.2 firmware which is similar to the 4.4.2 firmwares, but I don't know about the i9192.
Be careful with this;
If you know what you are doing, get the CWM recovery, format system/data and flash a 4.4.2 firmware again. If that didn't fix it, I suspect that it's a hardware problem and it's having problems with the software, but there should be something wrong with the hardware, for sure.
Good Luck.
Click to expand...
Click to collapse
Tried that too and nothing. I also suspect that the problem is a hardware issue. Thank you for the reply.
nelson2006 said:
Tried that too and nothing. I also suspect that the problem is a hardware issue. Thank you for the reply.
Click to expand...
Click to collapse
The problem, in fact is a fault in the hardware problem. If it's still under warranty, request a new phone.
Can anyone help with this. I have a sprint note 4 that I rooted and was working great, but wanted the stock 5.0.2 upgrade. Used odin to install stock 4.4.4 and remove root. Worked fine phone took the 5.0.2 upgrade. Rerooted and installed wifi tether router but could not get it to work, found it is not working on 5.0.2, dam. Used odin once again to return to stock 4.4.4, rooted, installed wifi tether, everything works with one problem. When turning the screen on I now have a severe lag between the button push and the screen light up.
I odined back for other issues and still had problems. .even a backup was not working... i wiped everything, all data etc, 2 times then went back to nie....then took the otas back to lollipop. .now everything works fine except i still hate the colors
Sent from my SM-N910P using Tapatalk
Fixed, it was a bad sd card had nothing to do with the dowgrade.
Good to hear you found your problem. However if it's tethering that's keeping you away from Lollipop then you can put that to rest because you can easily enable wifi/usb tethering without the need for a third part app like tether router (which i have payed for as well). If you expect to stay on the factory rom/firmware then Lollipop would be a wise choice due to the new ART (android runtime) and it's overall effeciency compared to KK . It has a lot of benefits and other than the stock colors, there's no reason you shouldn't update to Lollipop. Do a little searching here in the Sprint Note 4 forum and you'll find a few easy ways to enable the built-in tethering.
Thanks for the info, did exactly that, found galaxy tools would provide the tether
Downgrade help
Hey
I need some help downgrading my phone from LP 5.02 OE1 update
I have no service and need to re unlock
What files did you use?
Can you send me a link. Odin fail with everything
badgal said:
Hey
I need some help downgrading my phone from LP 5.02 OE1 update
I have no service and need to re unlock
What files did you use?
Can you send me a link. Odin fail with everything
Click to expand...
Click to collapse
You are SOL for now. Cant downgrade rom OE1, but a new OTA is about to come out, I'd sit tight until then. or...Many people flash Noterized Rom. Try flashing that and continue your troubleshooting.
Stuck
Here is my screen
I have the T-Mobile SGH-T889 running stock Android 4.3. I'm interested in learning how to flash custom ROMs—most recently because Pokémon GO is only compatible with Android 4.4 and up, but it always seemed like something cool to do and I can push my old phone to do new tricks.
However, I also have a Samsung Gear 2 Neo watch. I'm afraid that flashing a custom ROM might affect compatibility with the watch, and I'd rather not go through the hassle of backing everything up, installing the ROM, and reinstalling everything only to find out that my watch can no longer connect. Can anyone shed some light on my situation?
I have searched all over and couldn't find any answers, so hopefully this isn't a repeat thread.
I just purchased the HTC desire 816 and upgraded to it. I activated it, and set everything up, Saturday. Sunday after trying to load xposed onto it, it froze on the boot screen.
I managed to restore it from fastboot, and got it updated to lollipop.
Now for the problem, and what I have tried:
The phone will not see bluetooth devices at all.
First I tried simply a factory reset, which allowed it to see my smart watch and start to connect to it. Part way through the setup of my watch, it lost it's connection.
Next I tried a wipe and restore to full stock, this did not allow me to see any bluetooth devices.
Then I tried rooting, cwm, and putting kitkat back on the phone. I still couldn't see bluetooth, and now I am trying to upgrade back to lollipop.
I am at a loss as to what may be the problem, but I need it to work with bluetooth.
I have tested it with both my LG G smartwatch, and a gemline bluetooth speaker.
OK, so a little update here. I did a full stock & root flash last night.
The wifi began working, and Bluetooth was connected to my smartwatch.
This morning, wifi is still working and bluetooth can't see any devices.
On a side note, I am trying to figure out what version of xposed to install on my phone.
tenchu98 said:
OK, so a little update here. I did a full stock & root flash last night.
The wifi began working, and Bluetooth was connected to my smartwatch.
This morning, wifi is still working and bluetooth can't see any devices.
On a side note, I am trying to figure out what version of xposed to install on my phone.
Click to expand...
Click to collapse
If you're on 5.0 lollipop then 21. If you're on CM 12.1 (5.1) then 22. I have this same device and carrier and haven't had any issues like you're describing other than a few Bluetooth dropouts every once in a while. Good luck.
http://forum.xda-developers.com/showthread.php?t=3034811
thoctor said:
If you're on 5.0 lollipop then 21. If you're on CM 12.1 (5.1) then 22. I have this same device and carrier and haven't had any issues like you're describing other than a few Bluetooth dropouts every once in a while. Good luck.
http://forum.xda-developers.com/showthread.php?t=3034811
Click to expand...
Click to collapse
I went back to full stock, and relocked the bootloader, because HTC said that it was an issue with the bootloader being unlocked. I doubted them, and it turns out I was right to doubt. The issue isn't fixed, and I seem to have narrowed it down to the searching function. My HTC can't see any discoverable items.
I have a gemline speaker, which has NFC to pair Bluetooth built-in, and my phone is unable to see it when I try to use NFC enabled pairing.
I am suspicious that somewhere along the lines the bluetooth files became corrupted in system. I have been trying to find a way to put the original ones back on, but haven't been able to find a way. I really want to get this working, and remove root.
Why do I not want root, because my kids enjoy pokemon go and it won't run on root anymore.
tenchu98 said:
I went back to full stock, and relocked the bootloader, because HTC said that it was an issue with the bootloader being unlocked. I doubted them, and it turns out I was right to doubt. The issue isn't fixed, and I seem to have narrowed it down to the searching function. My HTC can't see any discoverable items.
I have a gemline speaker, which has NFC to pair Bluetooth built-in, and my phone is unable to see it when I try to use NFC enabled pairing.
Click to expand...
Click to collapse
Yeah, that's a load of crap so you were right to question that. My bootloader stays unlocked and I don't have any Bluetooth issues other than the ones noted for running CM custom roms and the headset dropouts. I have 3 different Bluetooth devices linked to my phone and no issues pairing any others either.
I am suspicious that somewhere along the lines the bluetooth files became corrupted in system. I have been trying to find a way to put the original ones back on, but haven't been able to find a way. I really want to get this working, and remove root.
Why do I not want root, because my kids enjoy pokemon go and it won't run on root anymore.
Click to expand...
Click to collapse
You could find and flash back your stock recovery and then find either the stock RUU file or the stock Rom.zip file and flash back to stock. I understand about root. It's getting to the point my next device will probably stay stock but I'm having my fun now.
thoctor said:
Yeah, that's a load of crap so you were right to question that. My bootloader stays unlocked and I don't have any Bluetooth issues other than the ones noted for running CM custom roms and the headset dropouts. I have 3 different Bluetooth devices linked to my phone and no issues pairing any others either.
You could find and flash back your stock recovery and then find either the stock RUU file or the stock Rom.zip file and flash back to stock. I understand about root. It's getting to the point my next device will probably stay stock but I'm having my fun now.
Click to expand...
Click to collapse
I did this once already, I am thinking that my next step will be to manually copy the bluetooth related files from the system image into system using root
then flash unsupersu.zip
So I hav replace every bluetooth related file I can think of, and even deleted some file suggested online, and my phone still doesn't see other devices. When I put my phone on my NFc enabled speaker it acts like it is going to pair, but then says "unable to pair gemline speaker".
I am beginning to become frustrated.
I have been using the LG v495 on 5.0.1 with some healthcare related Bluetooth devices without any problems. ATT forced the 6.0 update and it caused the BT devices no to work (or spotty at best) and also have problems paring these devices. Is there a way I can go back to 5.0.1 with these tablets? I still have a few that have not yet updated to 6.0 Possibly a way to back up the 5.0.1 from one tablet and restore it to a 6.0 tablet. Not sure why the 6.0 BT is buggy with BT devices that worked fine on 5.0.1
Any help would be appreciated.
Bump? No one has done this?
I don't have the V495 bit did you try a factory reset (which will wipe everything including all user apps, data and internal storage)?
Factory wipe does not change the firmware..
jaingram said:
Factory wipe does not change the firmware..
Click to expand...
Click to collapse
I know it doesn't change your firmware, I mean did you try one to see if Bluetooth improves?
Yep, several times, unfortunately, it didn't help the pairing issues.