Search results

I am in the process of flashing and setting up OB 20 itself (full install, user data wipe, the whole bit). The issues seem to be gone while that's running. Once I get that to the point where it's usable, I will make a nandroid of that and see about getting OMNI back on this thing. Hopefully...

I can confirm the no sms issue. I wonder if it's modem / radio / rild issue? I'm thinking about grabbing the OOS pie beta and letting that load before coming back to omni pie. Sidebar, my gravity / orientation sensor seems to have gotten screwed up, such that the x and y axies appear to have...

Even if I'm all the way back on your last Oreo build? That stuff is pretty ancient... Cool, thanks.

Ok, I will give it a shot and see what happens. I see 3 files to download .. I presume we flash firmware, rom, and (optional) gapps in one recovery session and in that order .. I searched the thread and didn't find what to do with vnd.img, though. fastboot flash vendor vnd.img or something...

Anyone know if WiFi calling on T-Mobile USA works with the latest build? That's the only thing holding me back...

Well, shoot. I had to revert back to 8.1. Wifi calling on t-mobile doesn't seem to work. Can anyone else confirm or suggest a way to get it going? I need it for work, so it's a deal - breaker for me, unfortunately.

This new build seems to be the thing! I now have a nicely working PIE build on my phone - thanks Darkobas! FYI, I had tried an earlier build and had flashed OOS 5.1.5, so I had the vendor partition and all that pre-existing. When wifi wouldn't work, I restored my 8.1 nandroid backup, which I...

Looks like I am having the WiFi problem with the latest build. Hoping I can easily revert back to 8.1 until it's fixed...

Has anyone tried this under either or both of the following conditions: 1. with codeworkx's 3.2.3-0 recovery (with /vendor partition support)? 2. coming from the 8.1 version of Omni encrypted with a PIN? Any pitfalls to watch out for?

Maybe he's uploading a new one?

So, are there any complete instructions for upgrading from the last official nightly to the unofficial Treble build? It seems like there are some more complex steps involved than wipe, flash, enjoy ... but, I've been over the bits of this thread since the Treble build was posted and not found...

Just wanted to let everyone know my Bluetooth issue seems to have resolved. I think what did it was finding the Bluetooth system app and clearing its data, along with the Bluetooth midi app. I was able to pair with my Focus and it survived a power cycle or two. Sent from my ONEPLUS A5010 using...

Here I go again... I'm having some pretty serious Bluetooth pairing issues. I pair my device with my 2009 ford focus with Sync, and it at first seems to work. However, after I disconnect from the device (like by turning my car off), the phone seems to forget that it's paired. Subsequent...

BTW, if anyone cares: Settings -> System -> About Phone -> Baseband version OB3 = MPSS.AT.2.0c4.7-00070-8998_GEN_PACK-2.130961.1.131284.2 OB4 = MPSS.AT.2.0c4.7-00070-8998_GEN_PACK-2.131284.1.132073.1

First, thanks for answering at least some of my questions about the firmware. I'm still learning the ins and outs of this device, and I'm not really used to needing to care much at all about firmware in addition to the ROM itself and occasionally the kernel. Yes, I understand the things you...

OK I'm so I just spotted the thing about OB4 existing. I'm pretty sure I'm not in it, even though I did flash the last weekly that came out. OP is not updated yet to include a link to OB4, even though someone said it is already required. Yes, I searched the thread before posting. 1. How do I...

OK, I feel really stupid for asking this, but I can't find it... How the heck do you take a screen shot with this ROM? I'm used to it being an option on the power button menu, but it's not there. I searched settings for it, and nothing other than saying "OK, Google, take a screen shot," which...

Aha! I found what I was looking for - thank you again! I've been an Omni-ROM virgin up until today, so please pardon my ignorance.

Just wanted to thank the dev for this. So far, this is the only 8.1 ROM for the OP5t I've found where the headset microphone seems to be working properly (I'm on the latest weekly as of today's date). STRONG candidate here for my daily driver to replace stock OOS. Now I just need to find a...

Thanks - Just wanted to see if I could confirm that it was a software issue and not a hardware problem. I bought my 5t used over the weekend and am trying out different ROMs.

Is anyone else having an issue where a wired headset mic will not work at all? I can hear system sounds, etc., through the earphones, but no audio is passed from the mic. Interestingly, if I load the app called Spectroid (audio spectrum analysis) and set the audio source to "unprocessed," then...

FYI, my symantec anti-virus is flagging this as malicious. It did not do this with previous versions.

Feature request: I went back deceased pages and didn't see this, so here it goes. With the latest update, Google has removed the option to make a call using your carrier network and number, and instead insists on placing the call through Google voice when you hit the phone icon in a hangout...

Holy crap, thank you for this!! I've had this issue pop up over the last few days and couldn't for the life of me figure out what was wrong. It seems that un-blocking the proxy did the trick for me, too. I took it one step further, though, and whitelisted the whole att.net domain. Oddly...

So, it's been a long time, and I've upgraded my Note 2 to a KitKat ROM. And .. gsiff_daemon still goes run-away after a soft-reboot. I did find a way to reliably reproduce the behavior, too. I installed the XPosed framework, and using its "soft reboot" option will make gsiff_daemon lose its...

While I'm sure you're right that those things don't help, please do remember that DerTeufel1980 has been really busy with his Real Job lately, and has been on travel assignments for weeks at a time where he has been unable to work on the kernel or even check on XDA. That is why not much has been...

Hmm .. trying to bootleg some Nightwish / Within Temptation / Tarja, are we?

I checked that post out and it intrigued me, to say the least, but let me explain what it's doing a little bit. First off, the source file that's changed isn't part of the DevilKernel source. It's from the device-specific files built into most ROMs. In PAC's case, it's under...

Did you guys use the very latest kernel from a few posts back? Phone.APK FCs might be the result of telephony-msim.jar not being present in BOOTCLASSPATH, and that issue wasn't fixed in the devil kernel until very recently. Specifically, I'm pretty sure the kernel in the OP of this thread...

If it's a CM-11 based ROM, then this kernel looks for framework2.jar. I honestly didn't look at the others. That's why I made symlinks for both.

That ZIP is only compatible with PAC, unless you edit the script to use whatever name your other ROM uses - just be aware of that. So what you'll want to do is flash the ROM and Gapps only (no custom kernels yet), then adb shell into it. From there, go to /system/framework and ls framework*...

Just to let everyone know, I think this is basically the same as the custom build I've been running for the last couple weeks. It's solid as a brick on my note 2 with the PAC 4.4 nightly builds. Try it. You'll like it.

It is. I'm running it. Also, there is a 3/7 nightly for t0lteatt now. Upgrades!

Running this on a AT&T Note 2 with the latest PAC nightly build. I've observed the same behavior on older, more stable ROMs as well. 1. Most of the time, the random MAC appears to try and preserve the upper 2 bytes or so of my original MAC address. Since this is where the chip manufacturer is...

I learned my lesson a long time ago about taking another developer's work, putting a fix or two into it, and releasing it myself. Last time I did that, it caused a sh!tstorm, so I won't do that again -- at least not without permission from DT himself. So, I'm sorry, but no, I can't. The other...

I hear rumors that it's the "non-intrusive call" thing. If you disable it, it should be ok. Of course, that sucks, because that was a big reason I wanted KK in the first place...

I can tell you right now that it won't. The issue is that there's a new file that needs to be added to the BOOTCLASSPATH in the kernel's initramfs. Other kernels probably don't suffer from this because they don't use their own baked-in initramfs (and they don't give you dual boot functionality...

Think you could point me to those threads? The odin idea is intriguing to me, but I'm lazy ;) Maybe I could set this one up: Edit: Never mind - I found the threads. It looks like he's setting up the boot splash image, which appears BEFORE the kernel's boot logo. It's the raw "galaxy note...

Well, a little bit of both. I managed to download the generic bootloader image from my phone and render it in GIMP, and save it as a .png graphic. Then I searched the web for cartoon-ish devil images and found the little guy with the kettle. I downloaded him and pasted him into the file...

At one point, I replaced it with this in my custom builds: >;)

Ok, I found it. Bad news is that it's still looking in the root directory, so any modifications would still have to be done in initramfs, which means re-building the kernel. I also am not sure how it will interact with the stuff the kernel is doing in the video drivers - setting the image from...

I apparently don't know where to look for that. I'll keep searching.

I've done this before - it's a little tricky, and you need to compile the kernel from source, and you need to have the image sized and formatted just-so. I'd love to figure out a way to have it read an arbitrary image from a config file or something, but there doesn't seem to be a "good" way of...

Oh, jeeze .. I guess it helps if I subscribe to the right thread, huh? Thanks, man!

Ok, seriously dumb question, but .. Are there any significant differences between "t0lte" and "t0lteatt" that would prevent me from using the t0lte test recovery on my t0lteatt device? I'm going to assume yes, just to be safe, but I'd love to be wrong.

FYI, the latest kernel for t0lte (at&t) works great with /data/.selinux_disable not present. Now I just have to work up the courage to try the f2fs migration ...

Thanks, man! Let me know if I can help.

Apparently the new devil kernel and recovery allow any 4.4 ROM to migrate and use it, yes. I'd like to try it out, but once you twrp, you never go back, lol, so I'll wait.

Any plans on f2fs support for other (non-moto-x) devices, like t0lteatt?

Ok .. so I just flashed the test kernel on my t0lte note 2. I am not using dual boot. The ROM is 4.4-based, Temasek version 40 (same ROM I had working fine with the latest stable devil kernel). Before flashing I ran (as root): # touch /data/.selinux_disable # chmod 644 /data/.selinux_disable...