Hey guys I'm loving the 360. Got a small problem. I'm a crack flasher on my Note 3. Is there any way to flash a ROM and re-pair my watch back to my phone without having to reset the watch and lose all my data?
I have tried using titanium backup and backing up Bluetooth pair setting and it didn't help. Thanks
yeah, I ran into the same issue. I had to reset the moto 360 inorder to get it up and running properly again.
I previously had a G watch and was in a similar situation. When updating from one nightly to the next (aka no data wipe) it'll be fine and just work. However, whenever you wipe data, you'll need to factory reset the watch. Luckily the only thing you'll really be losing is fitness data.
Related
Hey Everyone,
I am running the SGH-T989 with the latest Darkside (2.3) ROM and kernel. Though new to the forums I have been "trolling" here for years and rooting and moding every phone I have had since ... well I can't remember when.
Never had any serious troubles, but suddenly, about 2 days ago I stopped getting incoming calls. It acts as though the phone is off and all calls go straight to voice mail, this happens when I have full signal, and I can still make outgoing calls. I have done full wipes, charged fully, tried it plugged in, not plugged in, on WIFI calling, on cellular networks, different ROMs, and nothing seems to work.
Anyone have any suggestions?
check under settings --call--- call rejection---auto reject numbers---should be off or the ones you want rejected...may got switched to all calls
Thanks for the response Bobby. Unfortunately I checked that after posting and it is set to off.
However I retired again and I am receiving calls now over Wifi calling, just not over cellular networks.
This is herring frustrating and of course the missus blames me for routing and ROMing
Ok,actuakly I tried to type retried but you gotta love auto-correct.
Sent from my SGH-T989 using XDA App
What about call forwarding?
Just checked and Call forwarding is set to:
Always forward: Disabled
Forward when busy / unanswered / unreachable is all set to voicemail.
Could that be the culprit even if I show full signal and am able to make out going calls? Should I disable any of those?
A few weeks back I had flashed a new rom and did a full app restore from Titanium backup. I had the same thing happen with call going directly to VM. I did a full wipe and re-flashed and then restored only missing apps and the problem went away. I assume it may have been a conflict with the restore. Might be worth a try. Good luck.
myndsey said:
A few weeks back I had flashed a new rom and did a full app restore from Titanium backup. I had the same thing happen with call going directly to VM. I did a full wipe and re-flashed and then restored only missing apps and the problem went away. I assume it may have been a conflict with the restore. Might be worth a try. Good luck.
Click to expand...
Click to collapse
Yes if you restore system data that causes issues unless it's backed up and restored on the exact same rom.
Sent via Brain Drain
I am having the same exact problem on Jugs 5.0... very interesting. I did not do a Ti restore, but rather just upgraded from one iteration of Jugs (3.7) to the latest.
But what happens when you don't restore any apps / data? I tried a fresh ROM install and prior to installing any apps I was unable to get any incoming calls (except when on WIFI calling).
Thanks for the help everyone. I guess its time to break down and contact Tmo and see what's up.
You beat me by seconds Poser. I tried Jugs 5.0 too and the problem still didn't go away.
Mystic_ said:
But what happens when you don't restore any apps / data? I tried a fresh ROM install and prior to installing any apps I was unable to get any incoming calls (except when on WIFI calling).
Thanks for the help everyone. I guess its time to break down and contact Tmo and see what's up.
Click to expand...
Click to collapse
By fresh install did you go into recovery and:
1. wipe data/factory reset
2. wipe cache
3. wipe davlik
4. mnt /system and wipe
5. flash ROM
I only ask, because I am wondering if "ghosting" is leading to mine and your problem?
Well, with the Darkside ROM has its own script to do a wipe ..... But, I'm a little OCD so, especially after having the problem I went through and wipe / re-wiped / wiped dalvik / re-wiped and factor reset.
Then after the flash (no matter what ROM that I have tried since having this problem) I fix permissions and then leave it for some time after boot to let it "settle in".
Hopefully the "ghosting" is your problem and the full wipes will help.
Mystic_ said:
Well, with the Darkside ROM has its own script to do a wipe ..... But, I'm a little OCD so, especially after having the problem I went through and wipe / re-wiped / wiped dalvik / re-wiped and factor reset.
Then after the flash (no matter what ROM that I have tried since having this problem) I fix permissions and then leave it for some time after boot to let it "settle in".
Hopefully the "ghosting" is your problem and the full wipes will help.
Click to expand...
Click to collapse
No dice, same problem. Wonder if it is an /efs problem?
Don't know but it is odd. I can still make outgoing calls, get data and everything else.
I have the same exact symptoms...exactly. It also just began a couple of days ago. Have you restored to bone stock via ODIN (I can't, my usb port is shot)?
Get a new sim card. If factory reset doesn't do it and you think its not network related and you don't think you accidentally blacklisted all your friends its probably the sim card.
Sent from my HTC Vision using xda premium
Android_Monsters hit the nail on the head. I took it to a T-Mobile store, they replaced the sim and all is golden (except that my wife can now call me again )
And in case you are worried, my phone was still rooted / ROMed and the Tmobile rep working the store was simply stunned to see the custom boot screen. They didn't care in the slightest that the phone was rooted and ROMed. In fact he was upset because he couldn't do that because of company regulations.
Same here.... new Sim did the trick
Huh?
This happened to me b4 I called t-mobile and they fixed it without going anywhere.
Sent from my SGH-T989 using xda premium
Hello everybody,
I'm running the latest stock Android 4.3 on a rooted Note 2 with CWM installed. What happens is that when I use the phone to make or receive phone calls (streaming music is ok instead) in my car (but I experienced the same problem in another car) the Bluetooth all of a sudden goes off and I need to either turn the screen on or toggle the bluetooth button.
Any idea on how to fix it?
Thank you,
Davide
Hi! Have you tried a Factory Reset? It will wipe your phone clean, so back-up your stuff first. Come back after with the results, maybe this will fix the Bluetooth issue.
Ruwin said:
Hi! Have you tried a Factory Reset? It will wipe your phone clean, so back-up your stuff first. Come back after with the results, maybe this will fix the Bluetooth issue.
Click to expand...
Click to collapse
Actually I wanted to avoid that...
Okay, so let's try something else first and see where it leads: Go to CWM and make a Nand Backup. Then wipe your Cache and Dalvik Cache. Reboot and test. Most probably this will not solve, but it's worth trying. Get back in CWM and this time wipe Data + Dalvik + Cache (Factory Reset basically). Boot and test. If not working, you can restore the Nand Backup to get back your apps and data. If it is working, well, lucky you, you'll have a great time installing all your apps back
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!
Has anyone been able to do a clean ROM install on their phone and NOT have to factory reset their watch to get it to re-pair? It's not a huge deal, but it's kind of a pain, and I feel like hte pairing information should be able to be backed up and restored across a ROM install so the watch doesn't know the difference.
I hear ya brother i got to reset my watch to get it to connect after flashing new roms too. I've tried to connect without resetting but still haven't found a way
I recently rooted and flashed a recovery on my M8.
I was experimenting with the Fake GPS Free app, and mock locations. Worked great.
But when I turned it off (developer settings, mock location-->None), Actual GPS doesn't work right.
Turned it off, removed mock location setting, deleted app, re-installed app, made sure it was turned off, deleted again.
'High Accuracy' sorta works. It gives an approx position. But using something like google maps navigation gives the message 'Searching for GPS...' and never finds it.
I tried a couple of apps 'GPS Status' and 'GPS Reset Com' which reset A-GPS, but it hasn't worked.
'Device Only' fails completely.
Tried clearing cache.
I even flashed a new ROM (Android Revolution HD (6.0)) but no luck.
I do have a factory reset option - but I'd rather avoid it if possible.
Anyone have any ideas of what else I can try?
Restore the nandroid backup you made (you made one right?) before flashing a new ROM or playing with apps from /system
I actually did not make one. I've just been reading up what it is and what I should have done and now I feel a bit silly.
When it said 'backup your phone' I thought it was just the contents (messages, data, media, etc).
Oops!
It's still all a bit new to me..
Anything else I can try?
Backup your data and sdcard content then flash appropriate RUU, if it's not gonna work it's probably an hardware issue.
I have exactly the same problem with my M8. I tried exactly the same steps and still have the GPS issue. I also restored a previously made backup and did a clean flash of CM13... this couldn't solve the problem.
It can't be a hardware issue
UPDATE: I don't know if it would have worked before, but after reflashing I placed my phone on the ground outside, started GPS Status & Toolbox and waited for a GPS signal. after ~1 minute GPS signal was found and it works fine since then. Maybe I was just too impatient before.
jamesb457 said:
Tried clearing cache.
I even flashed a new ROM (Android Revolution HD (6.0)) but no luck.
I do have a factory reset option - but I'd rather avoid it if possible.
Click to expand...
Click to collapse
Looks like you are new to the modding world. But if you are modding the phone (root, custom ROMs), you should always be prepared to recover from a factory reset (have your data backed up).
And if fact, if you are flashing ROMs without doing a factory reset (within TWRP) you are inviting all sorts of random bugs. In other words, the default wipe in TWRP (data, cache, Dalvik) is always recommended when flashing a new ROM.