Search results

Any plans for another build for July? I've got a couple bugs, like it always asks me if I want to use Action Launcher as my homescreen despite me already setting it every time, and when I try to change notification sound in settings, it crashes.

The fingerprint vibration is especially annoying when using one button nav :/ wish it would turn off when that is enabled

yeah, same here! luckily I haven't needed to remove the battery yet.

I guess it's nice to know for sure, but June seems like a long time to wait ?

sounds like good news! The Moto_GER Twitter account has also said they're working on Nougat for the Play. Hopefully we all won't have to wait long :D

Doesn't look like the Okay Google hotword from every screen is working

Coming from an M7, this is really annoying, especially when scrolling through Twitter.

Chrome tried to block the ROM file download as being 'malicious' :o I'm still flashing it ;D if the dt2w kernel works as well, this will be awesome! I get the E: unknown command when installing, just like with Candy7 EDIT: I just get reboots all the time :c only when wifi is on, I think

Was eager to flash this after reading the positive comments posted so far, however it reboots on me every thirty seconds or so. It took me a while to get through the set-up screen, and I was hoping it'd quit, but it's still rebooting as it tries to complete the set-up by restoring apps. EDIT...

I would greatly appreciate it!

is the OP not responding anymore? :/

does anyone know if this kernel would work using a Marshmallow ROM?

Are there any good custom kernels for the M7 on Marshmallow? (Preferably one with dt2w!) I've heard good things about ElementalX, but it seems they don't have an M7 kernel for Marshmallow. (And if I'm running a Marshmallow ROM, I need a Marshmallow kernel, correct?)

maybe this has already been reported, but there is no option in the settings to disable the backlight of the physical navigation keys (home and back buttons). I usually prefer to keep these off. oh, also for some reason when calling people on Duo, they cannot hear me; the mic doesn't work

does this work on the Sprint version?

this doesn't seem to work on the Sprint variant anymore :c

well, damn. seeing IG posts in Blinkfeed was super nice. wonder if HTC can pull some strings and get it back?

I'm interested in trying this out...

still seeing the double space bar issue. guess development has stopped? that's a shame, because auto-tinting based on what app is awesome. almost makes me want to go back to Fleksy, whose Chameleon theme is incredible. hopefully Google decides to add auto-tinting to their keyboard sometime...

working well for me, but I wish the built-in browser had the ability to sign into Google, and use Chrome Custom Tabs. they don't seem to be working in Twitter. also, like others have mentioned, the Settings crash when trying to change Lock Screen settings. do you plan to update this ROM on a...

I guess if obtaining root was possible, someone would have done it by now. I would've liked to install a Marshmallow ROM, but 5.1 works great, so that's something.

No, I am not.

I've just switched to Vanir from Candy6, and am very pleased. Everything seems to be working great. The only thing I miss is tap to wake, which must have been included in the kernel with Candy6. Has anyone tried anything to get tap to wake running on Vanir?

Okay, maybe I'll do that

My M7 is the Sprint variant, though I don't use it with a service plan. And no, I haven't tried either of those... Should I?

The microphone still doesn't work on this newest build. Also, I still can't seem to enable Now-on-Tap, even though the hardware buttons have configurable actions. But...it does complete the boot process! xD

I'm also stuck on the boot animation. Newest 2.1 Spr build.

Whenever I unlock the phone after installing the update, it just shows a black screen. The lock screen is normal (though a bit laggy), but once the device is unlocked, it's just the black screen :/ EDIT: I've tried doing a completely fresh install, and it seems to be working better for now...

Great ROM! Running well, except for auto-rotate seems to be broken.

Flashing now; I've been on Candy5 for the past few months and loved it :D thanks a bunch!

Has anyone tried the newest 6.0 beta build? It looks like all the previous builds have been removed. https://www.androidfilehost.com/?w=files&flid=44301

GPS is working fine for me on the final release 5.0 build...is that the 'test build' you're referencing?

There's someone reporting on Reddit that he got past it by deleting the cache repeatedly in recovery mode. I might go ahead and update, just for the heck of it. http://www.reddit.com/r/motog/comments/3sos0y/just_got_the_update_notification_on_xt1028verizon/cx03pe5 UPDATE: I updated, and...

Hoping for a solution as well, as I only use the device on WiFi. I suppose I'll hold off on installing the update, for now.

still holding out hope that Verizon will push out an update. they just updated the first gen Moto X to Lollipop, so perhaps the Moto G is next in line...

I've not experienced this on either release... working great for me! (This is probably because I don't use a network with my M7, just WiFi.)

Sweet! Had heard about this, but didn't really understand how it was different than any other gapps package. I don't wanna go through the process of replacing all Google apps now, but next time I flash an update to Candy, I will! :D

It'd be nice if the Camera app was able to be uninstalled or disabled. It looks like an older version of Google Camera, and I'd prefer to just install the actual Google Camera app and receive OTA updates for it.

Yeah, you have to reset Android Wear watches when pairing with a new phone/ROM so that isn't the issue. It's with Bluetooth in general, nothing to do with my 360 I don't think.

I've encountered an odd issue several times now where Bluetooth can't be turned on. If the phone has been on for about a day, and I've been toggling Bluetooth on and off throughout the day, it will stop being able to turn back on. Doing it from quick settings does nothing, and going into...

I tried to use the CandyOTA app to install. It booted into recovery, but nothing happened. Eventually I located the zip it had downloaded and installed it myself, then rebooted and everything seems fine.

This fixes most of the audio problems, but not the issue where, when wakening the screen during music, it causes the music to skip momentarily.

Can I flash this onto a Sprint M7? It doesn't say anywhere in the post about specific carriers...

I've been wondering if I should just go ahead and install Xposed simply to fix the sim issue, or just hold out for a fix later on. It seems kinda silly to install an entire framework just to hide a harmless message. Doesn't installing Xposed cause issues with updating via OTA? Like, you'd have...

5.1 I guess I should've said 'was', since you aren't running it anymore.

Is it stable enough to use as a daily driver?

is this still being maintained/updated? the build linked on the front page is from last month...

Why isn't this fix listed as the latest build on the front page? And why wouldn't it be available in the OTA downloader? Just curious. EDIT: Also, I think this is a bug with 5.1 in general and not Candy5, but when I'm in airplane mode and reboot, the no sim error message shows on the lock...

So... will the fix be pushed out to the Candy OTA app? Or will we need to flash the build you linked over the current one? Because I just flashed the latest zip from the first page of this thread, and I get the weird popping audio.

Currently, CyanogenMod is sitting at 12.0 for the Sprint M7, with no hope for reaching 12.1. The Verizon M7 IS at 12.1! I only use my phone on Wifi, no data, so would flashing the Verizon version of CM work on my M7? Would data be the only thing broken? Thanks!