yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] dodgem2012:
I'm also waiting for it to settle down been running for two days, yesterday it was downloading all my apps from google, but I have a question for exchange users. I have to have exchange email for work and I've used one of the pin bypass on Hyperdrive and it worked but tried it on Wicked and did not, I need to know before I try it has anyone else been able to successfully bypass the annoying pin to unlock using an exchange account???

This would be a deal breaker for the ROM if it did not, also at a later date can it be baked in? I love the ROM so far and would like to stay with it.
[Verizon Samsung Galaxy S III] AZNair:
How did you get google keyboard to work? I've had to switch to Swype but prefer the stock...

Also do you guys overclock all the way? Im looking for help with d2vwz cpu configuration if anyone has a link to share. Thanks
[Verizon Samsung Galaxy S III] johnnytraveler:
Your best source is with the op. GideonX has a kitkat kernel called bms, Its here on xda. There are lots of discussion on cpu and voltage tweaking. I believe there are even governors you can download.

Sent from my KitKat Galaxy S3.
[Verizon Samsung Galaxy S III] bshpmark:
Thanks

Thanks for the tips. I switched back to CM 11.0 and after flashing it I still had the problem. With Omni I ran both the kernal that came with the latest build and then switched to the BMS kernal. I still did not have gesture typing. I played with the setting and now I have gestures. I am going to go back to Omni in a day or two and see what happens this time. Omni seems to be a great ROM. Kudos to everyone that had a hand in it.
[Verizon Samsung Galaxy S III] dodgem2012:
I can't find Developer Options...

Nevermind, found DevTools.
[Verizon Samsung Galaxy S III] jlokos:
It has always worked for me on this rom. Have you tried deleting it and DLing it from the playstore?
[Verizon Samsung Galaxy S III] AZNair:
Replaced with official Google keyboard from the play store & gestures are working! Cheers!
[Verizon Samsung Galaxy S III] yamaha_wins:
Would it be possible for me to add extra notification toggles? A few other kk roms have 1 or 2 toggles that I'd like to add. But the ROM runs smooth as if not smoother than any other KK ROM I've tried. I did have a issue trying to get superuser working at first. Wasn't able to just download from play store and install. Had to actually download and flash in recovery.
[Verizon Samsung Galaxy S III] toosurreal01:
Is there a build in the works with a bluetooth fix?

I heard it was in the gerrit.
[Verizon Samsung Galaxy S III] Reborn627:
I haven't had a bluetooth issue yet. Runing the 1/18 build with the stock kernel and it's running brilliantly. Bluetooth connects to my car every time and stays connected. Streaming is flawless. What issues with bluetooth are you having?

Ray
[Verizon Samsung Galaxy S III] toosurreal01:
It wouldn't pair for me in my Ford. I'll try to flash the 1/22 build that was just uploaded and report back :D
[Verizon Samsung Galaxy S III] Reborn627:
My daily driver is a 2011 Fiesta with sync.

Ray
[Verizon Samsung Galaxy S III] samsgun357:
If you go to settings>about device>build number and tap it quickly 7-8 times it will unlock dev options.

Its only weird if it doesn't work!
[Verizon Samsung Galaxy S III] GideonX:
heh, you're quick.
[Verizon Samsung Galaxy S III] gadgetguy08:
I got the 1/22 version yesterday and see today that it is gone and there is a 1/23 version.

Was there an issue with 1/22?
[Verizon Samsung Galaxy S III] GideonX:
No issue, I just built a new one right after 1/22, didn't want to confuse people. I guess I failed :(
[Verizon Samsung Galaxy S III] gadgetguy08:
No worries. I really appreciate all you build for us.

I just didn't know if I needed to reflash with 1/23 immediately or if it could wait a few minutes. :p
[Verizon Samsung Galaxy S III] d1ez3:
Does this ROM have features like 'TDRS' from slimroms where the system apps are blacked out?
[Verizon Samsung Galaxy S III] HeathicusF:
Really enjoying this ROM so far. I came from Hyperdrive and think I'll stick with Omni for a while. I started with the 1/14 build (clean flash) and got a few forced reboots when using the camera. I dirty flashed the 1/18 build a couple days ago and so far so good. No crashes. Great battery life. Very stable, reliable, and fast. The only Touchwiz feature I miss is the quick toggles. I much prefer the Touchwiz functionality of the toggles over AOSP. Although I think both are ugly, the Touchwiz implementation seems more usable.
[Verizon Samsung Galaxy S III] gadgetguy08:
I am glad it works for you. I still have issues on the 1/22 and the 1/23 builds.

It would disconnect after 10-15 minutes from my car audio system and manual reconnection could not occur until after 1-2 minutes. Connection with some other devices was not always a smooth process either. :(
[Verizon Samsung Galaxy S III] Reborn627:
Hmm, clean ROM install? Full re-pair to vehicle after a master rest? These are two ways that I found mine to work. If I dirty flashed or didn't reset my vehicle I'd experience the same. Also, are you finding that you can stream as long as you want but if you're only connected, not using bluetooth streaming at all, that it quits after 15-20 min?

Ray
[Verizon Samsung Galaxy S III] gadgetguy08:
Yes, clean install, re-pair.

The 10-15 minute stop occurs while it is playing. I didn't get the Blue Tooth Stopped pop-up. Previous ROMs would throw that up and the streaming would continue until I clicked "OK" on the pop-up and then it would stop. What fun!
[Verizon Samsung Galaxy S III] HeathicusF:
Actually, I am having a minor issue I forgot to mention. Every now and then, I lose all notification sounds. The files are still there, the apps are still pointing to them, but they just won't play. The phone will only vibrate. I've checked volume settings. I'm not sure what triggers it. But a reboot will bring them back. For a while, anyway.
[Verizon Samsung Galaxy S III] eksoccer99:
updated a friends vzw GS3 to this b/c of good things, but running into a charging issue. Coming from Clean Rom 7: 4.1.2 & bootloader had no problems charging device no matter what cord or method. All of a sudden, updating/moving to this Rom; only certain charging cords, wall adapters or connecting to a PC work & charges. Their OEM samsung charger doesn't even work and it's never been used out of the box, but their daughters OEM samsung charger does work. Same device GS3. Is this a USB port issue? I've done some research and found blogs/articles from last year (2013). It's just all of a sudden since updating to 4.4.2 and/to this Rom. Charging is being finicky. Other than charging. Their loving the Rom.
[Verizon Samsung Galaxy S III] AZNair:
I use switchpro widget which let's you drop practically any toggle in the notification center, just like touchwiz but much neater.

---------- Post added at 09:12 PM ---------- Previous post was at 09:07 PM ----------

Maybe check if fast charge is enabled. I'm not sure if there's a toggle for it somewhere, or if it's even the issue...just a guess.

[MENTION=2950740]lso[/MENTION] quick shoutout to Omni devs for including an exceptionally nice boot-animation.
[Verizon Samsung Galaxy S III] 96NovaC:
Just flashed this and it's really nice. Only problem is I can't get the split view option to show up when I long press an app in recent apps like it's supposed to. Any ideas on how to make it work? Maybe an app or Xposed module like gravitybox is interfering?:confused:
[Verizon Samsung Galaxy S III] eksoccer99:
Only spot that I saw to enable it was in gravity box and its unchecked. Just odd. Never seen this before as my note 2 is rooted. Same routine that I do on flashing. Wiped clean install coming from a different rom.
[Verizon Samsung Galaxy S III] samsgun357:
Right now not even slim has this implemented fully. I'm not sure about omni but on slimkat and others I've tried with dark ui, it only does settings menu, calculator, calendar. It doesn't invert playstore, g+, hangouts etc.

If you really want all the gapps inverted grab a theme and use it. I can't wait for trds to be fully implemented again!

Its only weird if it doesn't work!
[Verizon Samsung Galaxy S III] AZNair:
Hmm getting half-dozen hotboots a day, usually when multitasking...had switched to art runtime a while back & didnt notice any real improvement over dalvik regd lagging or how fast apps loaded but didn't have this reboot problem before & also have 120+ user apps loaded on here really can't tell what the problem is...any thoughts?

Edit- turns out deleting apps may have solved the problem, well that or updated bms kernel...either way no more hotboots Air Omni cleared for liftoff!
[Verizon Samsung Galaxy S III] syst3merror:
does this have a reboot menu (reboot, reboot to recovery, etc)? Its the one thing I've missed in a lot of roms and wanted to check before I flash this.
[Verizon Samsung Galaxy S III] mav3rick478:
Yes
[Verizon Samsung Galaxy S III] johnnytraveler:
Actually, all the KitKat roms I've tried have advance power options. Often times you'll need to activate it in developer options.

Sent from my Cromix TF700T tablet.
[Verizon Samsung Galaxy S III] eksoccer99:
Try the bms kernel.
[Verizon Samsung Galaxy S III] HeathicusF:
I've tried a few apps that add toggles to the notification area, but none of them get it right. The big thing for me is the brightness slider. I can't find an app that has the brightness slider right there in the notification area below the toggles just like in Touchwiz. The closest any of them come is a toggle to bring up the slider. I tried the "Brightness control" option in the "Bars" settings menu, and that worked ok, but the setting never stuck. Whenever the screen would turn off and I turn it back on, the brightness was reset.
[Verizon Samsung Galaxy S III] elempoimen:
I'm having a heck of a time with the app switcher. It puts apps into multiwindow mode without having long-pressed them first. Then, I can't get them out of multiwindow ithout closing the app.

Is there a way to disable multiwindow?

I'm running the 1/23/14 build. Standard kernel, because things have been really unstable for me every time I've tried BMS (although I wish I could run it because the battery life is *insane*)...on an SCH-i535, of course.
[Verizon Samsung Galaxy S III] Azuma73:
Hey guys, weird action here!?!? Been running latest build for a few days and all was real nice.....until yesterday!!

My home WiFi started showing up as "out of range", out of the blue. Won't connect, won't let me forget network, won't scan?? And that's friggin' odd cuz my home WiFi is flawless & always 100% on all our other devices, but my phone all of a sudden!?!?

Haven't changed a thing since I set it up the other day either!! No big deal, I'll figure it out...always do eventually!! Probably just re-flash all nice & clean....again!!

Just thought I'd post my latest experience. Thanks for the RAD ROM!!
[Verizon Samsung Galaxy S III] elempoimen:
As a follow-up, I reflashed to the 1/18 build, and all is well. I actually decided to try BMS again as well, and that seems to be going well with this build. No issues yet...although I'm not quite getting the battery life I'd expected. :(

Still..quick and stable so far.
[Verizon Samsung Galaxy S III] cammykool:
Has this stabled out over the earlier builds of this?
[Verizon Samsung Galaxy S III] elempoimen:
This time around BMS killed my battery, and caused intermittent reboots. Rolling back to the default kernel solved that.
[Verizon Samsung Galaxy S III] xdreaper15:
hey there big guy, you should've been the one driving this hype-train! you had the first build!
[Verizon Samsung Galaxy S III] cammykool:
Im just pissed I couldn't figure the damn thing out. I messed up my build box and don't know how to fix it.
[Verizon Samsung Galaxy S III] GideonX:
Getting better ;)
[Verizon Samsung Galaxy S III] GideonX:
Want to give this test build a shot?
[Verizon Samsung Galaxy S III] johnnytraveler:
Been running it since last night. So far so good. Can't comment on battery life as I want it to bake in for a while.

Sent from my KitKat Galaxy S3.
[Verizon Samsung Galaxy S III] tyler.frost92:
Anyone get tap and pay to work successfully yet?
[Verizon Samsung Galaxy S III] elempoimen:
Trying it now. I will report back...so far so good, but I haven't used my phone much since I installed it.

Thank you for all your efforts!

---------- Post added at 09:54 PM ---------- Previous post was at 09:22 PM ----------

@GideonX, what governor settings do you recommend with BMS?
[Verizon Samsung Galaxy S III] dpeeps74:
I'm not GideonX but smartmax/row with stock max has not failed me. I consistently see about 10 hours with 4 on screen. I'm not doing anything else to try and save battery beyond I usually don't have sync on.
[Verizon Samsung Galaxy S III] GideonX:
I'm currently on smartmax/sioplus, so far so good but I change quite a bit.
[Verizon Samsung Galaxy S III] elempoimen:
using the settings, my battery life has been superb! Unfortunately, I did just have my first hot boot with the new kernel. It came shortly after I used the camera. Does anybody else seem to have problems with the camera and custom roms for this phone? I've had ongoing issues with this, no matter which rom I have used.

GideonX, I did try those settings but didn't seem to get as good of battery life. How is your stability?

FYI, I'm still running 1/18, due to the task switcher issue.

---------- Post added at 01:25 PM ---------- Previous post was at 01:12 PM ----------

I just had my second hot boot now with this setup. This time I only was using chomp sms. I went ahead and fully restarted the phone after this hot boot, thinking that it might still be an issue with the camera that was hanging things up.

Could it be a governor issue? Should I look at overvolting as mentioned earlier? I'm concerned about battery life if I do that, though.
[Verizon Samsung Galaxy S III] GideonX:
You can try upping the voltage a bit. BMS comes undervolted so your phone may actually not be playing well at the defaults. Raising it a bit should be fine.
[Verizon Samsung Galaxy S III] sbattosai:
I also did experience a hot boot today after flashing the new kernel and using GideonX settings. On the beta kernel, I didn't have any hot boot, but I was also using dance dance as CPU governor... On Omni rom of course.
[Verizon Samsung Galaxy S III] elempoimen:
What governor do you recommend? I've just been using the one baked into Omni...but it doesn't look like I can change voltages there? Does anyone know the stock voltages?
[Verizon Samsung Galaxy S III] GideonX:
Stock doesn't have any of those options.

Try a few combinations for gov, every phone is different so what works for me may not work as well for you.
[Verizon Samsung Galaxy S III] Reborn627:
Hey X, any idea what might have changed from the 1/18 build to the 1/23 or the latest kernel update you've done when it comes to bluetooth? I've had little to no issues connecting and staying connected to my car's sync system with the 1/18 build. Unfortunately if I upgrade to the 1/23 build or use the 1/27 BMS kernel I'm unable to pair my phone at all. For the time being I'm very pleased with the performance of the 1/18 build but I know for certain I can get even better battery like out of your BMS kernel. Just thought I'd ask. Thanks for all the work that you've been doing compiling ROMs and updating BMS. Yur da man!

Peace,

Ray
[Verizon Samsung Galaxy S III] jlokos:
Ray, I would try the 1/28 build. BT connection and voice dialing working for me.
[Verizon Samsung Galaxy S III] elempoimen:
What is the situation with multiwindow in the 1/28 build? I saw on the omni blog that they're working on new code...I assume that's what the strangeness was in 1/23. I'm wondering how far along that is. I don't really use multiwindow...but the 1/23 implementation was messing up my task switching.
[Verizon Samsung Galaxy S III] jlokos:
I don't use it much. I tried it the way I used to: hold down app in app switcher, and pop up comes up but no item show in split view.
[Verizon Samsung Galaxy S III] GideonX:
Multiwindow is not ready yet and is currently being cherry pick into this build. You'll likely see some weirdness until they merge it in officially with all the fixes.

Not sure on the BT issue. I'm seeing connection problems on my end, but it works sometimes as well. :confused:
[Verizon Samsung Galaxy S III] iofthestorm:
Not sure which patch set you have in your builds, but patchset 21 was broken such that every time you tried to switch apps it would do multiwindow instead. Patchset 22 fixed that so you might wanna grab that if you haven't.
[Verizon Samsung Galaxy S III] GideonX:
I haven't built with 22 yet, I'll get it into the next one.
[Verizon Samsung Galaxy S III] elempoimen:
That was the issue. Exactly.
[Verizon Samsung Galaxy S III] Reborn627:
Unfortunately no luck here. I did a sudo clean install (system, cache & dalvik) but I still experience the loss of connection after 15-20. Strange, the 1/18 would sync and stay connected perfectly. Any others after that struggle to pair and loose connection after 15 minutes. Thank for the tip though.

Peace,

Ray

Edit: This may help. I paid attention to the connection while driving to work this morning. After exactly 15 minutes it appeared to disconnect (my Ford sync system has 2 indicators. One is a bluetooth led the other shows the battery and signal strength on the screen) The bluetooth indicator never went out although the battery and signal indicators did. Upon testing what was actually connected I was able to play music via bluetooth. I was not able to receive calls or use the app link features that are normally present when connected via bluetooth. This seems rather interesting, well to me it does. Let me know if any of you need more clarification in order to troubleshoot this.
[Verizon Samsung Galaxy S III] Reborn627:
One thing that it isn't doing is reconnecting after getting out of the car. That requires a reboot.

Ray

Edit: I flashed back to the 1/17 build and haven't had a problem with bluetooth, or anything else for that matter. I guess I'll just hang with 1/17 for now and see what the future holds.
[Verizon Samsung Galaxy S III] cammykool:
so nothing good out of this vs cm in stability? ive been stranded on 1/17 since it came out i dont have anty in car BT (i dont have a car) but i have a pebble
[Verizon Samsung Galaxy S III] GideonX:
You can try the 1/30 test build I have in the testing directory.

Speaking of pebble, how is it anyway? I thought about getting one.
[Verizon Samsung Galaxy S III] cammykool:
i like it its a if you have a need for one go crazy but you could live without it i hear the peble app store makes things better though but ill have to wait on the android release

how do i delete quicksettings tiles?
[Verizon Samsung Galaxy S III] johnnytraveler:
Pull down the tiles. Tap the 'marker' icon (upper right) then tap the tile you want to get rid of. It should shrink in size if you did it right. Hit back and it should disappear.
[Verizon Samsung Galaxy S III] gadgetguy08:
I have had a Pebble for about 6 months and really like it -- although it did have a fit with the BlueTooth connection the other day. Normally that hasn't been an issue.

I find it helpful getting email, notifications and the like on my wrist without having to pull out the phone. Also it is customizable enough so you can get the outdoor temperature or the phone battery strength at a glance. Music control is useful, for example, when mowing the lawn and wanting to skip a track. Alarms are recently improved to allowed them to remain and be turned on and off.

The battery lasts about 5 days for me and my only minor complaint is that you can sometimes get surprised when it dies. The low battery icon appears on a secondary screen.

I find Canvas for Pebble to be an good app for modding phone faces.
[Verizon Samsung Galaxy S III] cammykool:
I don't like how much the pebble kills my battery on this
[Verizon Samsung Galaxy S III] griz.droidx:
Just wanted to say thanks again to GideonX for building these. I saw the new feature for app switching and stuff and will be trying the latest build soon.

Again thanks man for all you're doing for the d2vzw community.

Sent from my bad ass small block. SGS3 pimped way out thanks to. All the deva and the community. Many thanks to everyone who's made it possible for me to have the coolest phone in my area. For real everyone always asks how I do this or that on my phone.
[Verizon Samsung Galaxy S III] johnnytraveler:
+1

The newest version (2-3) has Omni port, the app switching feature you were talking about. You can read about it here. http://omnirom.org/features/easily-switch-apps-omniswitch/

I found out about it from xda member Mitchwtn .

Sent from my KitKat Galaxy S3.
[Verizon Samsung Galaxy S III] gadgetguy08:
Interesting. I have never noticed battery issues with the Pebble. I use the BMS kernel which gives me good battery life.
[Verizon Samsung Galaxy S III] Reborn627:
I've flashed the test kernels from 2/5 and 2/6 and bluetooth is now working perfectly, Thanks Ed. Quick question though. Has anyone else found a complete loss of root? I've tried installing supersu from the play store, tried flashing supersu from the link in the OP. I've also tried the "fix permissions" option in TWRP. All with the same result. Root has failed. I tried flashing the 12/27 BMS kernel as well thinking that maybe something was missing from the test builds. I've tried to get root back with casual and with saferoot and have had no luck at all. I wiped the phone and restored a previous mastamoon CM build and root works just fine there. I'm stumped. Any ideas?

Peace,

Ray
[Verizon Samsung Galaxy S III] johnnytraveler:
Is supersu enabled? Check in developers options and make sure it is turned on. If not, turn it on and reboot. If that doesn't work, look around for the supersu update zip that was to be flashed in recovery.

Sent from my KitKat Galaxy S3.
[Verizon Samsung Galaxy S III] Reborn627:
Well, that seems to make sense. I don't have the supersu option in developer options with the Omni ROM. Odd

Ray
[Verizon Samsung Galaxy S III] johnnytraveler:
My bad, this rom already has su enabled. I'll look around for the su update zip.

Try this. Flash in recovery.

https://www.dropbox.com/s/p9i64hgpd3jhz28/SuperSu-update.zip

Sent from my KitKat Galaxy S3.
[Verizon Samsung Galaxy S III] Reborn627:
Failed in TWRP just like the 1.93 posted in Beans forum post did. I'd flash cwm in ez-recovery but without root I can't do that either. Not sure what's going on

Ray
[Verizon Samsung Galaxy S III] jlokos:
Ray, go into settings>developer options>root access and make sure it is checked for apps and ADB.
[Verizon Samsung Galaxy S III] Reborn627:
Thanks but there is no "root access" option in my developer options. I've made that change in the past on other ROMS but it just isn't there on the most recent Omni that I'm running, 2/3 I believe. I'm downloading 2/5 right now

Ray
[Verizon Samsung Galaxy S III] johnnytraveler:
I'm getting stumped too. I read through your first post and find it odd that you would have root and su in another rom, but not this one. Did you already wipe and do a clean install of Omni? Have you tried flashing a different rom just to check. I'd download a totally different rom and see it you get root and su. GideonX has several others you can try. I'm guessing it is something with your phone and not the rom. Would like to confirm by testing another rom.

Sent from my Cromix TF700T tablet.
[Verizon Samsung Galaxy S III] Reborn627:
Thanks for the suggestion. I tried doing a full wipe and reinstalling Omni 2/5 and still was not able to get root. After that I did another full wipe and installed mastamoon's unofficial from 1/31. Root is a go with mastamoon's build. I'm not sure what's going on here but it seems to me it's an Omni thing on my phone. Can't fathom what it could be though.

Ray
[Verizon Samsung Galaxy S III] GideonX:
Flash philz recovery within your current recovery. Then use the option in philz to fix root.