Hello guys,
This issue has been haunting me. Whenever i try and pair my device it freezes the phone and after about 5 seconds, it restarts the device. The weird thing is, it doesn't ask me for my SIM pin which is enabled. So i'm thinking it's a soft-boot (is that even a thing?).
The watch is useless at the moment.
It's worth noting that it works fine with CyanogenMod 12.1.
Logcat logs can be provided (can't post because it's too long).
Things i've tried:
-Install older version of android wear.
-Clear cache.
-Manually pair watch via Bluetooth settings.
Device: Moto X 2014 victara.
OS: CyanogenMod cm-13.0-20160508-NIGHTLY
Watch: Moto 360 2n Gen.
Android Wear version: 1.5.0.2714488.gms
Any help is greatly appreciated. Thank you.
I am having this exact same issue. Yesterday I flashed the latest nightly of CM13 for my device. I flashed it clean coming from the last CM12.1
Right now I have the watch connected to my phone manually via bluetooth.
I've tried the same things you have without any success.
Device: Nexus 6 shamu
OS: Cyanogenmod CM13.0-20160605-nightly-shamu
Watch:LG G watch
Wear version: 1.4.0.2576000
Same issue
Guys, did you manage to fix this issue?
On a OPO CM13.1 and on restored backup to 13, I too having this issue with a moto 360 g2. Factory reset watch and still android wear crashes the phone on pairing. Worked great for 6 months until I down graded Google services due to battery drain issues, and now can't get wear working again.
Any suggestions on fixing it would be gratefully received.
Related
Hi there,
I am very happy with my Moto Z, but since about 8 weeks the phone keeps randomly rebooting, even over night when I don't interact with the phone. I did already a factory reset, installed less applications as before, but after about one week the random reboots returned. Does someone else also have this issue, and has probably a solution?
Some system details:
- Moto Z, Andoird 7.0 (stock), reteu
- Build NPLS25.86-31-5
- Baseband M8996_1239.53.01.12R SRS
- Kernel [email protected] #1 from 30/03
I fear everything started with the first 7.0 update installed via OTA. I know that safe mode is often suggested, but then I can't install any application for about one or two weeks to check stability. That's actually a no-go for me.
Best
subwayne
Now this is the weirdest thing I've ever encountered! I have a Samsung Galaxy Note 8.0 tablet (n5110) which runs TWRP recovery and Resurrection-Remix-5.7.4 (CM13 based). Everything used to work beautifully until the end of July when an app called “EPB DVR Manager” (in the Play store) received an update. My tablet had to do a whole bunch of updates, so I gave it the “go” and Play Store started doing its thing, updating one app after the other.
At some point the tablet froze. Dead. Even the clock in the status bar stopped. I had to reset the device by pressing and holding power until it rebooted. The next thing was ... boot loop. It seemed to finish the boot animation and at the point when the main screen is supposed to show up it rebooted!
Tried to wipe dalvik & cache. No go, still boot loop. Had to format data to get the device back to life. From there it took me quite some hours of repeated tries of restoring 100+ apps and crashing the device all over until I figured out that it was this specific app - the “EPB DVR Manager”. After figuring out that this app causes the problem, I did two more attempts to confirm what is going on:
First, I did a wipe of dalvik, cache & data, reboot, android setup wizard (setup Google account). Then, as the first action at all, I tried to install the “EPB DVR Manager”. Boom - device messed up again.
Second, I reverted back to stock firmware (kitkat) and installed the “EPB DVR Manager” - no problem at all. So it has something to do with the Resurrection-Remix ROM, but here's the thing:
I have 3 different devices (a Moto G 3rd Gen, a LG GPAD 7.0 and that Samsung Note 8.0) and all three of them run Resurrection-Remix 5.7.4 and the Samsung is the only device which all in a sudden has these catastrophic problems with the latest version of this app (earlier versions installed/updated fine).
Now I understand that my devices run different kernels with different hardware drivers despite all of them running RR-5.7.4.
I would really like to get a clue about what the heck is going on here. Now before y'all are telling me that RR-5.7.4 is dead because it is based on CM13 - I know that. Still, RR-5.7.4 is a way better daily driver than the newer Nougat builds. So how should I try to get “live logs” because the problem always ends in a crashed installation and Android needs a full wipe to recover. I would like to find out what is going on to be able to let the app developer know about the problem (if the app's apk is at least partially to blame).
Even if it turns out that it is RR's fault (and therefore the bug will not be fixed because RR-5.7.4 is dead) I would still want to learn how such a simple transaction like installing an app can cause such a dramatic (and 100% reproducible) crash of Android's data partition.
Thanks for any suggestions on how to catch logging information for this kind of mystery.
Markus.
Today I had to resync three times. At first I thought it was my custom watch face but I have everything factory reset and just running default.p. I am running the latest build of Lineage but it is the same thing happening on my wife's phone with her stock LG G5.
Hello, i have a problem with samsung alpha on 4.4.4. kitkat. When i try to use google maps, if i click on directions and select car, application will crash. If i select bus, it will sometimes crash. If i select walking, it will never crash and normaly show path. If i upgrade application, it doesnt crash but instead locks up and heats the mobile phone a lot.
What i tried so far:
1) gps on/off, tried using only wifi/mobile data
2) tried all 4 versions of 4.4.4 for my country, first and latest update
3) it works fine on 5.0.2, though i want to remain on 4.4.4
4) tried resetting gps
5) tried rooting phone, uninstalling app completely and reinstalling it, doesnt help
6) tried like a 100 different stock roms from different countries and couldnt get a single 1 to work, they all fail or go into infinite boot loop
Please help me with my problem. I really like this phone and would hate it to leave a bad taste because if this 1 problem. Btw, the only roms that work for my phone are on the link below. I tried other links from my country (branded ones, not opened ones) and nothing works. I want to remain on stock rom btw.
https://samfrew.com/model/SM-G850F/region/SIO/
Google maps does the same for me. It hangs when I click on 'directions'. I have a Samsung Galaxy ACE4 SM-G357FZ with Android 4.4.4. It started happening to me a few months ago. I thought it was because my phone has only 1GB RAM, and I removed or disabled every app that I don't use regularly, but it didn't help. I switched to Sygic GPS. It is better than google for walking, and it works OK for driving, but I miss not having the bus and subway schedules on google maps. I don't have the option of updating to 5. As far as I know, the last update was a Jan 2017 security update of 4.4.4. I have a Nexus 7 tablet. Updating it from Android 4.4 to 5 made it so slow it is useless.
" though i want to remain on 4.4.4"
why?
Try the workaround posted 7/6/19 here: support.google.com/maps/thread/9075511
Or reverting to previous version of the app posted 2/17/20 here: support.google.com/maps/thread/3592231
Hi, since 2 months, this app never again works in my g watch, are anyone that use it can confirm if works in your device?
I tried to reset watch, reinstall app, all without success.
Regards
Update: I update google play services 8.X to 9.X using a downgrade of wear OS apk 1.5, but sending apk from phone to watch continiue unresponsive.