yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] Reborn627:
I'm going to bring this up again because I haven't seen it addressed and am unable to find any solution in all of my Google searches. Google Now is no longer "listening" for the "okay google" hot word. I have factory reset as well as completely wiped the phone with a fresh updated Omni with PA gapps. I've used the stock kernel and BMS. Ive installed alternative tts apps thinking maybe PicoTTS was the problem. I've changed languages, turned Google now off and turned off hot word detection. I've done all that I can think of to solve this and have seen no change. I find it hard to believe that there are only 2 of us with this issue. I'm currently running the 6-7 build with the most recent full stock PA Gapps with the Google Experience Launcher. Please, somebody help a brother out. I realize that "okay google" is not a necessary feature but it is one that I have found quite useful. Thanks in advance for your input.

Peace,

Ray
[Verizon Samsung Galaxy S III] Notorious:
I saw someone mention it on g+ page but no response about it. If you really need that feature try using the Xposed module for it. It let's you use the Okay Google hotword on 3rd party launchers to activate Google now
[Verizon Samsung Galaxy S III] Reborn627:
Thanks for the tip but unfortunately xposed doesn't help. Google search is not "listening". It appears as if the microphone attempts to initialize but fails. The mic icon in the search bar flickers solid a few times before ultimately going to "not listening" mode. I'm stumped.

Peace,

Ray
[Verizon Samsung Galaxy S III] RRF12:
Google now works fine on omni with nova launcher for me.
[Verizon Samsung Galaxy S III] MrBrady:
I had that issue with Maps, actually any GPS tracking app, as well. I noticed it came from installing the 6/8 Gapps PA Gapps package. I went back and installed the 6/3 Gapps package and it seemed to help the issue. Navigation now works, but sometimes I have to toggle "Location" first.

On the PA thread they said it's not Gapps related, it's ROM related, but I only noticed a fix after going to an older Gapps. Go figure.
[Verizon Samsung Galaxy S III] Reborn627:
Thanks, but I'm pleased enough with the Google Now Launcher and it doesn't matter what launcher that I use, it has the same problem. It seems the issue is with the ROM. I've attempted to use both the 6/03 and 6/08 PA Gapps packages and had the same troubles. I've wiped my phone and installed mastamoon's CM11 ROM with the 6/08 PA Gapps and "Okay Google" works just fine. I don't know why it's an issue with my phone with Omni but it is. I suppose I'll go back to CM.

Peace,

Ray
[Verizon Samsung Galaxy S III] kenbrownstone:
Nice work
[Verizon Samsung Galaxy S III] RyanJKremer:
Holy Hannah! Working screen record in the power menu! Wicked sweet!
[Verizon Samsung Galaxy S III] mbarry55:
Good question. To be honest hadn't even realized it wasn't there.
[Verizon Samsung Galaxy S III] GideonX:
No theme manager with omni.
[Verizon Samsung Galaxy S III] mbarry55:
[MENTION=2645480]GideonX[/MENTION], what kind of update schedule does/will this ROM have? Nightlies, weekly, whenever you get around to it? The crack flasher in me would like to know what I'm getting into. I like this ROM a lot so far.
[Verizon Samsung Galaxy S III] GideonX:
I'll try and nightly it. They're working on this pretty hard, so there's lots of changes going on.

Speaking of which...12/30 is up on the server...
[Verizon Samsung Galaxy S III] hallstevenson:
What's special about this group's ROMs (I don't mean that in a smartass way) ? Their website doesn't list what sort of features they have and their XDA threads are pretty minimal.

I'm following you on Google+ and I thought I remembered a post from you saying you're going to bake in your BMS kernel. Is this the same ROM ? Saw another posting from someone saying it was very sluggish with the stock kernel and they flashed BMS and it made a big improvement.
[Verizon Samsung Galaxy S III] mbarry55:
One other thing, if you do nightlies, will we have to install SuperSU each time? What's the reason it is not baked in?
[Verizon Samsung Galaxy S III] GideonX:
It's a new rom started by some really smart devs. So far it's probably the smoothest KK rom I've ran.

I'm not baking BMS into any roms I build. I don't believe in force feeding anyone my work. However, it is highly suggested to flash BMS after you flash Omni.

It may be in later on, but for now you will need to flash the SuperSU zip every time.
[Verizon Samsung Galaxy S III] androidsftw:
As gideonx has said, there's a lot of work being done with omni since it is a very young project. I'm not really sure what their plans are for certain in relation to qualcomm/caf items, since I've been told different things. (I've manually picked necessary caf stuff for a functional build, credits go to omni's gerrit and slim) For customization, there's stuff in omni's gerrit that look like they are very close to being merged so I really hope they do.
[Verizon Samsung Galaxy S III] hallstevenson:
Just found something missing that's unusual for custom ROMs.... The secondary power menu when you select "Reboot" (the one that gives you restart, recovery, bootloader, etc choices). Oh well - just downloaded an old favorite: Quick Reboot
[Verizon Samsung Galaxy S III] dandydon414:
Look for Advanced reboot in developer settings. Needs to be checked
[Verizon Samsung Galaxy S III] hallstevenson:
Hmmm, they moved Developer options, but I found it. Also found the setting and it is checked already... Let me try to un-check it then re-check it and see if that kicks it into place !

And.... that did it ;)
[Verizon Samsung Galaxy S III] omair2005:
[MENTION=2645480]GideonX[/MENTION] great work man! You need a

recognized contributo

r title!
[Verizon Samsung Galaxy S III] RRF12:
Tried this just get phone process stopped. Flashed three times with different gapps no go for me. Back to beanstalk it has cured my crack flashing.
[Verizon Samsung Galaxy S III] hallstevenson:
He has to "apply" for the title.... Or, a senior moderator can give him that title. The only one I see that frequents the VZW S3 area is kennyglass123 -- why not PM him on behalf of everyone here (since you brought it up) ? :fingers-crossed:
[Verizon Samsung Galaxy S III] GideonX:
Lol, hi [MENTION=3125148]kennyglass123[/MENTION].
[Verizon Samsung Galaxy S III] mav3rick478:
Ugh, just tried to install this and SuperSU errored out, can I just restart the phone and install it later after I redownload it? TIA
[Verizon Samsung Galaxy S III] GideonX:
Yes, you dont necessarily *need* superuser to boot the rom.
[Verizon Samsung Galaxy S III] mav3rick478:
Thanks [MENTION=2645480]GideonX[/MENTION], I just restored my nandroid and downloaded SuperSU again, hopefully it goes smoother this time but if not now I know I can just reboot and carry on.
[Verizon Samsung Galaxy S III] theyurtingyeti:
I've had a few back to back reboots, this is from the last one: https://www.dropbox.com/s/2gezsoomw8uj4j0/2014-06-13_22.29.zip

Thoughts?
[Verizon Samsung Galaxy S III] GideonX:
Can you pastebin the log?
[Verizon Samsung Galaxy S III] draexo:
Is there a list of specs for Omni?
[Verizon Samsung Galaxy S III] theyurtingyeti:
I suppose i could. what does that mean :)
[Verizon Samsung Galaxy S III] GideonX:
You can probably get a good feel of what the rom offers here:

http://xdaforums.com/omni
[Verizon Samsung Galaxy S III] GideonX:
Copy log into pastebin.com
[Verizon Samsung Galaxy S III] theyurtingyeti:
I copied the last_kmsg: http://pastebin.com/5z1npfuF

Let me know if you need more
[Verizon Samsung Galaxy S III] GideonX:
Doesn't look like this log has any info on the reboot.
[Verizon Samsung Galaxy S III] theyurtingyeti:
huh, that wouldn't be to helpful, then... I'll post the other logs from the zip. perhaps they'll have the relevant information.
[Verizon Samsung Galaxy S III] theyurtingyeti:
http://pastebin.com/sLJJLkPq -- dmesg.log

http://pastebin.com/m48HHXmn -- last_kmsg.log

http://pastebin.com/F35qvTq2 -- logcat.log

http://pastebin.com/HjGR0X33 -- modem.log

Those are all the logs I got after that reboot. Hopefully they have at least some useful information.

Thanks!
[Verizon Samsung Galaxy S III] GideonX:
Reboots are usually in the last_kmsg. However, sometimes it won't contain any useful info if it wasn't captured in time or if the log wasn't written somehow. If it happens again, try to capture it as soon as it reboots.
[Verizon Samsung Galaxy S III] theyurtingyeti:
Thanks! I'll send along the log next time... although, I saw a new version up too... May give that a go also.
[Verizon Samsung Galaxy S III] jpmaniac87:
I've been running the 5/30 version with 4.2.2 gapps, no problem. Took the Omni ota update and was getting reboots. I downloaded the 6/20 version of Omni and gapps and now I can't boot.... I'm on mf1 firmware and radio. Is there a good reason for this of the top of anyone's head? Thanks!

Update, I flashed the ml1 modem and got it to boot on the 6/20 build
[Verizon Samsung Galaxy S III] MrBrady:
I can only get the 6/20 build to boot once. Trying to boot a second time winds up in a bootloop. Wiping data and cache gets it to boot again, but only once. Then bootloop again.

VZW SGSIII
[Verizon Samsung Galaxy S III] Wh1t3Rose:
the 6/24 build is doing the same thing
[Verizon Samsung Galaxy S III] MrBrady:
I'll stick with 6/15 for now then. It seems to be working pretty well.

I'm having issues with GPS on all 4.4.2+ AOSP ROMs I've tried where I have to toggle location on and off for it to activate GPS. Otherwise it bases my location on the tower I'm connected to. Flashing a 4.3 TW ROM doesn't seem to help the situation either.
[Verizon Samsung Galaxy S III] jlokos:
It took a good 10 minutes for me but the 6/24 build finally booted and updated (dirty flash). Everything seems to be working.
[Verizon Samsung Galaxy S III] pyrite123:
I've tried 2 KitKat ROMs today and downloaded everything using my data... I've already used half my data allowance in the first 3 days of my billing cycle. So I'd very much like to get this issue solved ASAP.

In both ROMs my WiFi is COMPLETELY broken. It won't even detect WiFi networks. I've reflashed everything multiple times and in different orders. I've wiped everything several times. I don't know what else I can do. Is there a aosp modem I should install or something?? Please help, I'm panicking over here!!

I forgot to mention the first KitKat ROM I flashed was the latest resurrection ROM with a completely clean install.

Edit

I got the WiFi to work finally however having the same problem as everyone else with the booting up after first reboot.

Edit2

Also I can't get SuperSU to install. I even tried flashing the zip in recovery and it just causes endless boots.
[Verizon Samsung Galaxy S III] Wh1t3Rose:
But did you try to boot a 2nd time with the new build?

I tried the 15th build but kept having root problems and SuperSU wouldn't update the binary for some reason.

---------- Post added at 07:11 AM ---------- Previous post was at 07:08 AM ----------

you need to download TiBU. Use that to restore your apps after a ROM flash.
[Verizon Samsung Galaxy S III] jlokos:
Yes I did and it booted up fine after that.
[Verizon Samsung Galaxy S III] jpmaniac87:
I too am having boot issues with the updates... The boot now takes about 10min. Thinking of trying a clean flash if noone knows what else could fix it...
[Verizon Samsung Galaxy S III] GideonX:
Tried 6/27 build yet?
[Verizon Samsung Galaxy S III] jpmaniac87:
Just tried on a fresh flash and I'm hanging with the sluggish boot again. I rebooted before adding my account and am just sitting on the omni logo...
[Verizon Samsung Galaxy S III] GideonX:
What radio etc. are you on?
[Verizon Samsung Galaxy S III] jpmaniac87:
ML1 Radio

Flashed the 6/27 build with the 4.4.4 gapps from PA

Just to make sure I hadn't borked anything with the phone itself, flashed back to 5/30 4.4.2 version with the 4.4.2 gapps and all is back to normal. Any thoughts?
[Verizon Samsung Galaxy S III] GideonX:
Not sure at this point - I can't reproduce on my end. The latest build flashes and boots like normal for me. I've had a few other users who previously had slower boots say the new build has fixed it for them as well.
[Verizon Samsung Galaxy S III] Wh1t3Rose:
OK I'm coming back. May be getting an LG G2 in the next week or so. This may be my last S3 ROM
[Verizon Samsung Galaxy S III] griz.droidx:
Just to confirm I had no issues when testing the 06-27 build. I was just trying it out to see how things were coming and had no issues with slow boots or anything like that.

Thanks to GideonX for his continued support of this device with all the builds and kernel work. Thanks man. Oh, I used pa gapps for 4.4.4 from around the middle of June.
[Verizon Samsung Galaxy S III] Wh1t3Rose:
What gapps are u guys using again? That might be why some ppl r having boot issues and other r not. Some might be using Mini or Micro and others r using Full Modular
[Verizon Samsung Galaxy S III] pyrite123:
I tried several times with 3 different gapps with all the same outcomes
[Verizon Samsung Galaxy S III] Wh1t3Rose:
3 different types of Gapps or 3 different dated gapps?
[Verizon Samsung Galaxy S III] pyrite123:
Types. Lite, slim, and stock
[Verizon Samsung Galaxy S III] twistedillutions:
How i enable multi windows? Is it cuz i have Omni switch on?
[Verizon Samsung Galaxy S III] mav3rick478:
Am I missing something?! I recently came back to Omni and I can't get vibrate notifications to work, do I need to install a sound pack or something? I'm using Active Display also, does that have something to do with it?
[Verizon Samsung Galaxy S III] mav3rick478:
Nevermind, figured it out. I guess if you use the toggle for quiet time it's really for manual use and not to activate it. Turned it off and all my notifications came back.
[Verizon Samsung Galaxy S III] JT1510365:
can someone provide a new download link to this rom?
[Verizon Samsung Galaxy S III] Dcox28:
Is there not an option to center the clock? I am loving this ROM so far and that is the only thing that I can't find that I wish it had
[Verizon Samsung Galaxy S III] GideonX:
Not an option, but you can use xposed + gravitybox to achieve that I think.
[Verizon Samsung Galaxy S III] jlokos:
That is what I use for that purpose.
[Verizon Samsung Galaxy S III] Eyalkn:
Not with art. Love this rom. It will also be nice if omni will add features like transparent notification drawer and battery styles.
[Verizon Samsung Galaxy S III] RyanJKremer:
You can choose other battery icons under settings/battery/battery indicator.
[Verizon Samsung Galaxy S III] MrBrady:
**FINGERS CROSSED** does this mean no Cyanogenmod parts? I'd love a pure AOSP ROM.
[Verizon Samsung Galaxy S III] GideonX:
Almost, kernel and some vendor bits are cm. It's just about 99% omni.
[Verizon Samsung Galaxy S III] faehsemc:
Thank you. Can't wait for KK to catch up with Jelly bean when it comes to all the different mods. This ROM hasn't given me any issues at all. Been using it for over a day now, with your kernel. Thank you for your amazing work.
[Verizon Samsung Galaxy S III] GideonX:
Thanks for the RC title [MENTION=3125148]kennyglass123[/MENTION]!

:good::highfive:
[Verizon Samsung Galaxy S III] hallstevenson:
That was pretty easy, eh ? ;)
[Verizon Samsung Galaxy S III] GideonX:
He actually PM'd me before I even did anything. Best mod ever?
[Verizon Samsung Galaxy S III] sbattosai:
My impressions are very good with Omni. Once the kernel is replaced, the rom becomes smoother and I had no reboots. I was overseas with the 12/29 build and was having no signal issue on gsm but I couldn't get data when I was roaming (not the rom's fault). Wifi to no wifi area was Goodman and didn't create reboots like on other roms. I came back to California, put my Verizon sim card and was ready to roll data. Flashed the 12/30 build by dirty flashing the rom only and everything was fine, even the stock kernel seemed way better on that build.

Everything was great except for one thing, bluetooth. Bluetooth isn't good on the last build (didn't try the previous build) with weird slow downs in the music while streaming, like you would change the speed on a LP, some cracking issues. Reconnecting to the paired speaker was also a pain (basically only a reboot helped).

Finally I had some Poweramp issues with the regular settings, solved using the advice in the dedicated thread in this forum.

Overall solid build, lacks customization that you can partly compensate with xposed but I miss the quiet hours option for example.

The bluetooth issues are once again the biggest issue on cm and aosp right now, which was not a problem during my European tour but is a major one when I am back home.

Thank you GideonX so much for everything you have done for the d2vzw community, congrats on the RC title and don't forget to update your kernel in between 2 builds :)
[Verizon Samsung Galaxy S III] Blaiser47:
This rom is amazing! Has tether and camera working so dd for me. Thanks GideonX for this and all you build. Only tiny bug I found is messed up screen shot image (just black and white lines for me) flashes across screen when the shot is captured but the actual resulting image is fine so doesn't really matter. This and xposed and I'm set until slim catches up... Happy new year all!
[Verizon Samsung Galaxy S III] GideonX:
Yup, BT is hit or miss with all CM/AOSP right now. It'll hopefully get better over time.
[Verizon Samsung Galaxy S III] hallstevenson:
Hey, I think you got something brown on your nose there.... better wipe it off !! :highfive:
[Verizon Samsung Galaxy S III] mav3rick478:
Stupid question here, how do I get xposed running on this Rom? Sorry so used to having it already in Beans.
[Verizon Samsung Galaxy S III] Eyalkn:
http://xdaforums.com/showthread.php?t=1574401

Download and install the installer (It is the app that comes with beanstalk)
[Verizon Samsung Galaxy S III] mbarry55:
I can't get any notification LEDs to work with Hangouts no matter what I do. I tried using LightManager which is what I usually use, no dice. Tried the built in settings for LEDs, nothing. Any other ideas? Never ran into this before.
[Verizon Samsung Galaxy S III] GideonX:
I actually just had this problem from a Hangouts I restored.

A simple re-installed and then a reboot got everything back to normal.
[Verizon Samsung Galaxy S III] GlitchMob:
How is this rom compared to Gummy?
[Verizon Samsung Galaxy S III] GideonX:
Paging [MENTION=4642324]SlothlyDX[/MENTION] since he's tried both.
[Verizon Samsung Galaxy S III] SlothlyDX:
Uhhh I couldn't run gummy because Wi-Fi wouldn't work with a custom kernel soooooooo. Yea. I would say every phone is different and no over could really say. Gummy was nice on sick everything but omni is a change of site.

Crack-Flasher
[Verizon Samsung Galaxy S III] mightybryan:
Coming from Gummy, this ROM feels slightly less smooth. BMS helped a little from when I was using learnkernel at first.

But this build has TOO much potential. :thumbup:
[Verizon Samsung Galaxy S III] mbarry55:
Still not working. I reinstalled hangouts and light manager both and still no hangout led.
[Verizon Samsung Galaxy S III] GideonX:
Rebooted after re-installing?
[Verizon Samsung Galaxy S III] mbarry55:
I did yes. Not sure what's going on.
[Verizon Samsung Galaxy S III] GideonX:
Working ok over here now after I did that. Not sure then :(
[Verizon Samsung Galaxy S III] mbarry55:
Flashed a different kernel and now it kind of works. Although feels delayed by a second or two.

---------- Post added at 06:20 PM ---------- Previous post was at 06:19 PM ----------

I was on stock kernel I flashed dkp 12-26. Gonna try bms now and see what that brings

---------- Post added at 07:07 PM ---------- Previous post was at 06:20 PM ----------

I'm at a loss here. Reflashed rom, gapps, kernel. Still no hangout led. Next step I guess is a full wipe but I dont have time tonight to mess with that. Not sure what else to try.
[Verizon Samsung Galaxy S III] RRF12:
tried flashing this rom again today cannot get set up because unfortunately,phone has stopped popup will not go away. Any one else have this issue only rom I cannot get to work.
[Verizon Samsung Galaxy S III] cammykool:
What is your source? I was working on this.
[Verizon Samsung Galaxy S III] Blaiser47:
Spoke a little too soon, camera still causes reboots from time to time. Still, great rom and so much potential. Can't wait for updates... Maybe GideonX should be the US variants d2 maintainer for Omni ?? Got my vote if he is interested ;)
[Verizon Samsung Galaxy S III] GideonX:
Built from Omni source with CM d2 (device, kernel) and vendor from the Muppets.
[Verizon Samsung Galaxy S III] GideonX:
I'll need to pass. I don't have that kind of free time :)
[Verizon Samsung Galaxy S III] pastapie:
Same happened to me. What I did was wipe all three, format system & then just flash the ROM then boot. Let it settle then back to recovery wipe caches then flash gapps & supersu, boot.
[Verizon Samsung Galaxy S III] Blaiser47:
Fair enough, your kernel is plenty anyway. Thanks for all you do for our aging device!
[Verizon Samsung Galaxy S III] cammykool:
PM me. I need to ask you stuffs.
[Verizon Samsung Galaxy S III] Dcox28:
Just got a voicemail and went to check it but there is no phone number assigned to my v.m. I've never had this happen on a ROM so I'm not sure what the number is for a d2vzw??
[Verizon Samsung Galaxy S III] GideonX:
Hit me up on hangouts instead :)
[Verizon Samsung Galaxy S III] cammykool:
Working fine here.

---------- Post added at 08:21 PM ---------- Previous post was at 08:21 PM ----------

How. Tapatalk won't let me tap your G+ id
[Verizon Samsung Galaxy S III] GideonX:
How's this link?
[Verizon Samsung Galaxy S III] cammykool:
Sent.
[Verizon Samsung Galaxy S III] hallstevenson:
It's likely dialing your own number (and not displaying it).
[Verizon Samsung Galaxy S III] Wh1t3Rose:
Hey SlothyDX! Long time no see! How'd you been? You working on Liberty ROM for DX still? Or moved on to bigger things?
[Verizon Samsung Galaxy S III] SlothlyDX:
Whoa dude how is it going? I have a d2att now so I stopped with the dx. I'm assisting gideonx in testing his kernel and roms. I don't have a computer or means to build any roms right now ?

Crack-Flasher
[Verizon Samsung Galaxy S III] Wh1t3Rose:
I have had issues with my voicemail as well ever since upgrading to KiKat. If I dial my # or *87 or hold down 1 I just get sent to my voicemail to send a message like I'm calling from another phone. I have had this issue for a while and can't figure it out.
[Verizon Samsung Galaxy S III] mav3rick478:
I just checked on my phone and all the normal ways to access voicemail work, *86 and long press 1. Which gapps did you use because I'm using the mini one.
[Verizon Samsung Galaxy S III] Wh1t3Rose:
I'm using the mini ones as well
[Verizon Samsung Galaxy S III] DBLOCKWOOD:
Any chance of getting this for d2usc?
[Verizon Samsung Galaxy S III] mav3rick478:
Well so much for that.

I'm guessing you have your voicemail (*86) saved in your contacts too right? I know I'm reaching for anything now.

---------- Post added at 12:36 PM ---------- Previous post was at 12:31 PM ----------

@GideonX thanks for this Rom, it's been running great for the 3 days it's been on my phone without a hitch. As a matter of fact, it fixed the issue I had with all access Play Music disconnecting after so many minutes to my Chromecast!
[Verizon Samsung Galaxy S III] Wh1t3Rose:
its not. But doing *86 does the same crap and it shows as voicemail in call log
[Verizon Samsung Galaxy S III] hallstevenson:
What exactly is the problem ? If you tap the voice mail item in your notifications, does nothing happen ? If you dial your own # or *86 (*86 is standard for ALL Verizon phones -- it's the same # I've dialed since I had a flip-phone with VZW -- it has nothing to do with the phone model), does it not call your voice mailbox ?
[Verizon Samsung Galaxy S III] gadgetguy08:
Yeah, I had the same problem after a couple of attempts required battery pulls.

Gave up for now.
[Verizon Samsung Galaxy S III] RRF12:
I got it all working by formatting system an internal SD. Just got everything set up an its really running good with BMS kernel an gravity box. Nice rom