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.
Related
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.
Hey Guys,
I just flashed the latest lineageOS nightly and decided it was a good time to encrypt my phone.
However, when I try and encrypt, it starts by going to the encrypt screen with the green outline of the android guy. Seconds later it goes to the lineage loading animation and goes right back into the OS and nothing happened (no errors or anything either) I've tried multiple times (unplugging and plugging the phone back in, turning off wifi, etc)
Has anyone else come across this?
Thanks!
Has no one tried encrypting their phone? I can't be the only one.
I tried to encrypt using lineage 13 for the zl1 (lepro3) March 25th weekly build, and see exactly this issue.
Can't remove data
I've tried encrypting my phone several times and never had this issue. My problem comes when app data for certain games are still saved on my phone, even if I do a factory reset right after encrypting. The specific apps I'm referring to are Mobile Strike and Game of War.
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.
Hi all!
I have already commented on a opened thread about this problem but, as it was a similar, not exactly the same problem, I decided to make a new one, and delete the comment. I tried to install AOKP osprey nougat on my Moto G 2015. It installed with no problem at all, I installed it with Magisk and OpenGapps micro. But, as soon as the phone turned on and I started to go through google registration stuff, I started get a "advanced settings has stopped" with a close button. It was happening forever. I could fast click close and do one click on the phone but the error message was popping up every second. It was unusable, forcing me to not use aokp custom rom. I'm waiting for a new release. U guys do an awesome job and I would love to be able to use it on my phone...
Ty.
:crying:
Hello again guys! A new aokp Osprey version has been released in 05/23. I tried it in my Moto G 2015 that was running LineageOs with no problems. Just like the older ones it installed fine with gapps. But the further problems that I had with the older versions happened again. In the first boot, after installation, the popup error, that I talked about in the previous post appeared, but, this time I managed to get rid of it by just closing it some times (approx. 20x), so then I could login to my google account. In this first boot the phone was working fine, I installed some apps, changed some configs, and it seemed to be working ok. I decided to reboot my phone for testing purposes and here is where stuff broke again. The same error popup that I talked about, but now even with me closing it for at least a hundred times the popup was showing everytime. So, saddly, I just had to return to LineageOS.
That's it, bugs are still happening... But keep up with ur good work and, hopefully we will have some amazing Osprey ROM in te future.
Same bugs...
New ROM (aokp_osprey_nougat_nightly_2019-06-06_ota.zip), same bugs...
I'm giving up on AOKP for now...