Search results

GPS works fine. Waze navigation works fine. And I did migrate apps from my previous device, but it was from my Google account, which reinstalls all apps from the play store. Also, Maps is a system app, so it was not part of that restore process, it came pre-installed. I have also cleared all...

Has anyone else had the issue of Maps crashing when you press the start navigation button? This is the first device I've ever had this issue on, and have tried clearing app data / disable re-enabling / reboot.

Did all of those things. Same result. ---------- Post added at 10:38 AM ---------- Previous post was at 10:20 AM ---------- After formatting data and full wiping and installing 4 consecutive times, it worked. Go figure. On a side note, I don't recommend anyone use the built in Omni updater...

Tried again with the 1/21 build, this time without flashing gapps, and I get Launcher3 and Messaging force closing nonstop instead. Can anyone help me?

Just clean flashed the latest 1-22 build, and getting nonstop Google Services Framework errors on boot. This is after formatting data/internal, on the latest Codeworkx TWRP, stock kernel, no magisk.

Heehee :D

You, sir, are a ****. Fortunately the rest of the Omni community is not.

Magisk doesn't seem to pass safety net on latest build. API error in the manager app. Tried 14.0 and 14.5.

This is the only way I've found to fix this, found from another user on Android Central. Ihawki So I've been too lazy to post this but after moving to a note8 I realized the pain you all are feeling and that I would feel if I thought my $600-1000 phone couldn't do this. The solution is the...

Quite a bit later than I thought. I just got the notification too; not sure I want to wait that long. May just go get an Exynos S8+...

Pardon my ignorance, but when the carrier-unlocked version drops, where would we purchase it?

Has anyone else had issues with Titanium Backup not working on the latest build? Clean flash, with the nano gapps recommended in the OP, on the 3-07 build. No other apps installed, root enabled in dev options, TiBu spins forever when restoring any app or data.

Same here, clean flash of OOS 4.0.2, then r6, results in no mobile data. I'm on AT&T.

It's in the navigation bar settings. IME selector icon.

I have not found this to be true. I am seeing long wake locks and much less time in deep sleep when using any of the wake gestures. 5-6% per hour, without touching the phone for extended times. As soon as I disable them, the device sleeps normally, less than 1% drain per hour.

Did you even look at the thread before you posted?

I am still getting multiple sleep of death per day on the latest nightly. Is anyone else experiencing this? The Nexus Experience ROM did not have this issue for me in a full month of use.

No. Should I have? On an unrelated note, in the middle of playing a youtube video on the phone, the entire system crashed to the point that required me holding the power button to reboot. After a reboot, a screen appeared saying that Encryption had failed, and that a factory reset was...

Same thing here. System UI crashes on the 13th nightly. Flashed back to the 12th and all is good. Still getting consistent sleep of death. At least once per day now.

Just did a clean flash from stock yesterday. One sleep of death so far. I'll give it another day or two.

So are any of you guys running these nightlies without the sleep of death issues?

I hadn't seen any quark specific commits since the 2nd. Are you saying this was fixed with a regular commit?

Has anyone else had the "sleep of death" problems? Mine were so frequent that I had to go back to stock. Any insights?

I'm assuming this can't be flashed on a Moto Maxx? Not brave enough to try, figured there would be some major differences.

Fixed the GPS issue by flashing the modem again. But still getting lots of "sleep of death." At least 5 per day. May have to go back to stock until it's resolved ?

When it happens to me, I don't get wallpaper or anything. Just a black screen. No capacitive key lights. ---------- Post added at 08:23 PM ---------- Previous post was at 08:05 PM ---------- Anyone having issues with GPS on the more recent nightlies? I can't get a GPS lock even with flashing...

I have had several of these black screens of death, which require holding the power button to reboot. This is on the 5/1 nightly. 2 within the span of 5 minutes.

The nightly for 5/2 is hugely bigger than previous nightlies. Is this safe to flash?

I tried this buildprop change, and it did not fix my audio stuttering in Spotify. This is with stock kernel. Thoughts?

Tried that as well, no dice. Have clean flashed all the way back to 2.6, which worked with TiBu before, and now it doesn't?! It's weird. Same results regardless of stock kernel/AK kernel, different gapps, different SU binaries, namespace separation on/off. SuperSU does give a...

I had noticed that in the past, but in this case, rebooting did not help.

I'm also having issues restoring apps or data with TB, both in batch mode or individually, on a clean flash of 3.1, and again with a clean flash of 3.2. This is after installing SuperSU binary 2.37, and updating to the most recent via the Play store, and on the newest version of TB. The...

Has anyone else noticed that when you open the dialpad to enter numbers while in a call, it mutes the incoming audio? I have to turn speakerphone on and back off anytime I need to press a number while in a call. This has also happened when I receive a call while already in a call: the audio...

Any chance of v510 support for this? I have one available to test if that helps.

Sarcasmception.

Safe to use Franco aosp kernel on this?

Damn, you guys have NO sense of humor.

My big question is: Are most of the features & fixes included in the latest OTA coming from upstream CM, and as such, already present in CM nightlies, or will they be merged into the nightlies now that this release is out? Obviously stuff like the new lockscreen wouldn't be included in that...

So what's the word on TWRP 2.8.0.1 and these flashable zips? Do we just need to use an earlier version of TWRP, or does it fail because something didn't get wiped correctly first? I can't seem to get the flashable zips to flash on any version of TWRP that I've tried so far. This is for the 33R...

So 2.7.1.1 is the working version? I had tried 2.7.0.0, and it would fail flashing those zips as well.

The only recovery flashable 33R I ever found gave me lots of issues in TWRP 2.8.0.1: http://forum.xda-developers.com/oneplus-one/general/cm11s-official-untouched-image-t2857110 If I could get on 33R I'd be good from there, but the flashable image in that thread never would work for me.

So just to be clear, if coming from another rom like PA, we need to wipe, fastboot flash the 33R images, then we can install the OTA via custom recovery? Is there a simpler process when coming from a different rom?

Wow dude. Just wow. Anyway, to actually answer the question that was asked: there are no video issues on Beta3 for our device. The quick dialog issue is present though, but we have to wait for the new build to be pushed for us. If you dirty flash Beta3 and have already done the quick dialogs...

It's a 64 gb. Not sure how to answer the partition question. I haven't changed anything partition wise if that's what you're asking. The sd card is fat32

I cannot see the sdcard in storage under settings, or in Solid Explorer, ES File Explorer, or Sliding File Explorer. Using the mount sdcard option in storage settings does nothing. Can see it fine in TWRP recovery 2.8.0.1. Just flashed to ARHD 11.1 Sense, and it shows up fine there. This...

I still have no access to external sd card, even after running the SD card fix app. Ideas? This is on the 20th nightly, stock kernel.

I have no problems with battery life. 14 hours off the charger yesterday evening, I was at 50%. Better than my phone battery. Ambient mode off, moderate use.

Which of those zips can be flashed on Vanir? Would the CM zips work?

After flashing the rqstats with FauxSound and loading up the FauxSound app, mine shows the M8 - specific amp value at 100 by default. Is this normal?

Still rocking 5.6, still loving it. Thank you for your work.