yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] jwattt:
Make sure there isnt any junk in the Netflix storage locations. Maybe a previous flash or install didn't complete properly. If you wipe system data that doesn't necessarily mean you got all of the app data. My Netflix works fine on OctOS.
[Verizon Samsung Galaxy S 4] Highway 55:
Because you and one other person are having problems does not mean the ROM is causing the problem. There is some other variable causing this to happen to the Netflix app. I have had zero problems with Netflix on every iteration of OctOS.

I just remembered when I was using a stock ROM I had issues with the Netflix app after authorizing Watch On to access my Netflix account. So that is something to think about if you are using both Netflix and Watch On to access your account.

Sent from my hand phone.
[Verizon Samsung Galaxy S 4] Dubbsy:
It comes down to...

Log or it didn't happen.

But we won't be doing any more work on 4.3.1 just because of the amount to do on 4.4. It's gone up 3 revisions since we started.

sent from my Verizon Galaxy sIV
[Verizon Samsung Galaxy S 4] Highway 55:
I can't wait! Every version has ran well. I have gone back to 10/22 mainly because I prefer Agat's kernel. I will likely stay there until you guys release 4.4. Keep up the good work guys!

Sent from my hand phone.
[Verizon Samsung Galaxy S 4] Tsukasa Buddha:
So Samsung released some code today.

http://www.androidpolice.com/2013/1...-edition-is-it-about-to-start-raining-kitkat/

Do you guys pull anything from this?
[Verizon Samsung Galaxy S 4] Treken:
Agat is popular among kernel devs. Maybe we can get him to do a kk kernel when we finally get our kk build published. We basically had to rebase everything to aosp 4.4 so it's like starting from square one again. We don't want to release anything publicly until we have our source straightened out. With that being said, anyone is welcome to join our testers chat group on hangouts. Just post your gmail here or if you would rather it be kept private then P.M. it to either dubbsy, hlxanthus grommish, or myself.

---------- Post added at 02:19 PM ---------- Previous post was at 02:17 PM ----------

Not yet. We won't be touching that until our source is solid. We have enough to work on w/o having to port a kernel into our source. We will look at it but will hold off on introducing it into our ROM until we get done with top priorities.
[Verizon Samsung Galaxy S 4] thadialeckt:
Count me in would love to help where I can
[Verizon Samsung Galaxy S 4] Treken:
added. check your hangouts
[Verizon Samsung Galaxy S 4] Chuckleb0ne:
Here's mine. XXXXXXXXXXX
[Verizon Samsung Galaxy S 4] hlxanthus:
Added you

Sent from my Galaxy S4
[Verizon Samsung Galaxy S 4] theHoleK:
Horrible idea to post your email address on a public forum...
[Verizon Samsung Galaxy S 4] daventodd123:
I just clean flashed the newest version of this ROM and everything works but WiFi. I thought it was just a goof, but after several wipes-then-reflashing, WiFi still does not work. On my previous ROM, Cyanogen Mod 10.1, WiFi worked fine so I don't know what the problem could be here.
[Verizon Samsung Galaxy S 4] cjkacz:
Did you try a different kernel?
[Verizon Samsung Galaxy S 4] daventodd123:
I didn't see any different kernels in

the Aroma installer
[Verizon Samsung Galaxy S 4] cjkacz:
My thought was to install one after rom installation. Boot back into recovery, wipe dalvik and cache and flash kernel. Not sure what device you are on but there are many kernels that would flash
[Verizon Samsung Galaxy S 4] Tsukasa Buddha:
You must have used the borked build. I flashed the Elite kernel and it worked.
[Verizon Samsung Galaxy S 4] Cruiserdude:
Flash Elite kernel from the link below and see if that fixes your issues. Aroma has posed a few problems, and it doesn't work properly on some of the builds. So it's wise to keep at least one compatible kernel around, so you can flash it in case you have an issue and the Aroma package doesn't give you options.

http://www.projectelite.net/actngrezy/jb-mr1/JF/kernels/aosp/
[Verizon Samsung Galaxy S 4] red3razor:
OctOS team, could I please get in on the test group? I'll pm my gmail to treken and dubbsy.
[Verizon Samsung Galaxy S 4] Chuckleb0ne:
I don't even know how the test group works... All I know is that I sent then my email
[Verizon Samsung Galaxy S 4] schwartz.matthew.e:
Message Dubbsy then.

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

Look at my response to the question above you.
[Verizon Samsung Galaxy S 4] SimonTuffGuy:
You'll have to check in on Hangouts. The team will post the latest test builds there to run and post feedback on. Current release is a 4.4 with built in OctOS settings.
[Verizon Samsung Galaxy S 4] Chuckleb0ne:
I checked hangouts since I am running CM11 and I don't see the test group in the contacts page.

EDIT: Nevermind, I look it up in the invite section.
[Verizon Samsung Galaxy S 4] edif30:
How are you running CM11? I don't see it posted anywhere.
[Verizon Samsung Galaxy S 4] cjkacz:
That's cause this is OctOs' thread and not CM! ?
[Verizon Samsung Galaxy S 4] MassStash:
Ah snap! Just started tweaking and looking for hope of the GE kitkat being ported over to usc version, and I find this teaser.... Awwwwwesome

~Jflteusc runnin' latest Carbon Nightly

Latest KToonsez Kernel 2.1;189;480

Pegasusq

Row

Thermald:

Mpdecision:
[Verizon Samsung Galaxy S 4] Treken:
A release is expected this week. We're still working out some bugs
[Verizon Samsung Galaxy S 4] dogg94:
Excellent looking forward to it! Thank you.
[Verizon Samsung Galaxy S 4] PSBJ:
Looking forward to this! Keep up the great work guys.
[Verizon Samsung Galaxy S 4] MassStash:
So is this rom weird with bootloader too? Reading around on some GPE rom for tmo and they say that it can't charge while phone is off due to bootloader being different for the GPE edition. Is that just an issue with that tmo version/rom?

~ TF101 on K900's AOKP

Currently OC'ed to 1.4, KatKernel 70
[Verizon Samsung Galaxy S 4] Treken:
No. This ROM has no issue charging while off. Why would you charge with the phone off anyway? The only time my phone turns off is when I flash ROMs
[Verizon Samsung Galaxy S 4] s0m3f00l:
Anybody think the S-View Cover will be supported any time soon on this the Premiere S4 ROM? I would donate to further this cause if I could find your donate button on the FB or paypals, if such a thing would be helpful....

ALSO, I been using dubs' rom's since the first release of GPE1 and they are the greatest for support and reliability. A big thanks to you guys and your work on this epic undertaking. keep on keeping on.
[Verizon Samsung Galaxy S 4] Treken:
We have no plans as of now for the S-View feature but that's not to say it will never be. Our primary focus is to publish a pure aosp ROM GE style and have hidden features for customization if one so chooses to do so. We have been re-basing our project to have a base to build off of and after we get that finished then things will move along rather quickly.
[Verizon Samsung Galaxy S 4] ChoctawT:
How do I go about getting the multi window feature on this rom?

Sent from my SPH-L720
[Verizon Samsung Galaxy S 4] MassStash:
Oh wow, awesome! Really can't wait to try this out... for me, bout only time is playing ingress, phone dies, need to get it to charge while off to even turn it back on again
[Verizon Samsung Galaxy S 4] ROMANTiC KiD:
Multi window feature is a tw feauture. The dev's priority is to make a stable build first than maybe add some s4 features.
[Verizon Samsung Galaxy S 4] MassStash:
Wonder if which would be easier to add, tw multi window or Omni rom. I guess tw cuz its actually based on to kernel perhaps

~Jflteusc runnin' latest Carbon Nightly

Latest KToonsez Kernel 2.1;189;480

Pegasusq

Row

Thermald:

Mpdecision:
[Verizon Samsung Galaxy S 4] Dubbsy:
Sorry guys. Been away. M grandpa passed away and for a week been getting everything from his house in kc,mo that we wanted. I live in pa. I've been busy. We are working on fully linaro optimizing and building the setup for 4.4. We've had dozens of builds but not which are ready.

I've got sprint and vzw builds made but I need to make sure they install first. and I'm not entirely sure it's not b recovery related. So I'm looking into it. I'll be do swing again in a couple of days. Kevin has been soloing the whole thing so it's been kind of rough on him. Hopefully something new soon.

sent from my Verizon Galaxy sIV
[Verizon Samsung Galaxy S 4] ckelly33:
Sorry about your grandpa.
[Verizon Samsung Galaxy S 4] Alxoom33:
Hey Dubbsy, that must be rough! We're in no rush, so take the time that you need. This is just fun and games not real life.:rolleyes::beer:
[Verizon Samsung Galaxy S 4] Chuckleb0ne:
Sorry about your loss... I'll be waiting patiently for the next build.
[Verizon Samsung Galaxy S 4] jvinga1:
I installed 4.2.2 with safestrap, but I read that 4.3 would not work with it. Is 4.4 expected to work with safestrap or no?
[Verizon Samsung Galaxy S 4] Tsukasa Buddha:
I notice SELinux is set to permissive. I think I read it defaults to enforcing or something.

Also, there was a headline story a while back about updated recoveries for KitKat. Have you guys experienced problems with that?
[Verizon Samsung Galaxy S 4] Cruiserdude:
Again, any TW features will be coming later, if at all. Features like multi window seemingly require the full TouchWiz framework. Considering no one ever got them working on GoogleEdition, which was built atop a TouchWiz base, it's even less likely on a true AOSP base, which this has been since it's inception.

Bottom line, it's a distant possibility, but if multi window or other defining TW features are important to you, you may wanna stick with TW roms. This is primarily focused on a pure AOSP experience, with what tweaks can be made to work without ruining that.

I would not expect that to happen unless SafeStrap gets kexec or some other method of supporting custom kernels. 4.2.2 GoogleEdition, a different rom, was built on a TW base, and Dubbsy ported it over. It uses a TW kernel, and so it will apparently work just fine using SafeStrap atop a TW kernel.

4.3 and up are actual AOSP, just like the real GPe that it's based on/inspired by. Therefore this rom will not boot without an AOSP kernel, which you can't currently flash or load on any Verizon S4 unless you're MDK. This ROM is multi carrier, but only works with an (effectively) unlocked bootloader. Locked bootloaders that cannot load a custom kernel are not supported, and no method is yet known to make this work. There's nothing that can be done on this end, I'd focus on helping with SafeStrap development or bootloader unlocking methods if you wish to see this happen.

Everyone running this ROM on a Verizon phone still has an MDK bootloader and never took an official update. Newer official kernels installed a new bootloader that has yet to be exploited, and set SELinux from Permissive to Enforcing. MDK was still set to Permissive, and so it still is for those of us who had MDK and still do.

See the answer above yours for more details.
[Verizon Samsung Galaxy S 4] jvinga1:
Ah, thanks for explaining. I'm starting to understand some of the details. Some if it's starting to gel. So 4.2.2 GoogleEdition is inspired by the GoogleEdition and not really built on it, but rather, built on TW, and probably why there's still a bit of lag here and there (just like Hyperdrive, the only other ROM I've tried under SafeStrap)?

Is it correct then, that only a Touchwiz-based ROM can work from Safestrap? I'm a little unclear as to what's different when run from Safestrap or not and which file is the kernel and what it's tied to. For example, I thought I heard of someone choosing to switch from ME7 to MDK, but I'm not sure exactly what that means. I had thought this referred to the 4G radio. I also assume this can't be done when using Safestrap. What does it do when I flash jfltevze-ME7-modules.zip after I flash a ROM with SafeStrap? Maybe someone could clear up the basics for me?
[Verizon Samsung Galaxy S 4] Tortuga:
Regarding the first bolded item, no. The 4.2.2 Google Edition was built by Samsung/Google heavily on TouchWiz. This changed with 4.3+ to mostly AOSP. I recall Dubbsy commenting about how hacked together the system files were with both TW and AOSP elements. Dubbsy's (and Nitro's) 4.2.2 GE ROMs were ported from the international GS4's Google Edition system dump, because there is no Google Edition phone for Verizon. Rather than continue porting these ROMs (resulting in strange issues - i.e. carrier banner - and instability) Dubbsy and the other OctOS devs decided to create a fully AOSP ROM with a version as close to the Google Edition ROM as possible, while allowing for customization and multi-carrier functionality.

Your second bolded item is currently correct, until an exploit is found to allow AOSP kernels. In fact, from what I gather it is currently not possible to run 4.3 TW ROMs via SafeStrap since they require a different kernel as well.
[Verizon Samsung Galaxy S 4] theHoleK:
I seem to have lost the ability to send MMS messages. While connected to WiFi, in the past few days, I've had 6 MMS messages fail. The messages are just pictures which are around 600K. Logs available which I will PM to the devs upon request.
[Verizon Samsung Galaxy S 4] WrenchingPilot:
Dock Sound Redirector

Has anyone gotten this ROM (which is fantastic, thanks Dubsy & team), to work with the audio routed out a USB cable?

I have the iBolt "dock" cable, that worked properly when running stock TW.

When connected to the micro-USB port on the phone, using the "Dock Sound Redirector" app, the audio routed out the micro-USB port and through the 3.5mm jack on the iBolt cable.

It was convenient in my car to plug into the micro-USB port and listen to music while simultaneously charging the phone, all from one connector on the phone.

Anyhow, I can't seem to get it to function now. When I run the cable & app, it kills the sound.

The app dev states that this app may not work with CM, and the mapping needs verified:

"Please have the CM dev supporting your model verify the correct mapping exists between the ROM audio device and the kernel audio path (commonly set in libaudio).

Example: DEVICE_OUT_ANLG_DOCK_HEADSET in ROM should map to the path PLAYBACK_EXTRA_DOCK in the kernel."

I'm a newb. Does this apply to this ROM? Any ideas on how to make this work?

Thanks
[Verizon Samsung Galaxy S 4] schwartz.matthew.e:
[/COLOR]

Wait for the KitKat build to be released. It's working with MMS :)

Verizon SCH-I545

OctOS Tester

Verizon Wireless Retail Manager

---------- Post added at 04:56 AM ---------- Previous post was at 04:53 AM ----------

Good question. I'm not sure. If one of the devs doesn't respond soon, just message them.

Verizon SCH-I545

OctOS Tester

Verizon Wireless Retail Manager
[Verizon Samsung Galaxy S 4] Tsukasa Buddha:
Try: Oct Settings (tap "Build number" in "About Phone" 8 times to reveal) -> Advanced -> Sound -> Use Dock USB Audio

I don't have any experience with it, but it sounds close :p .
[Verizon Samsung Galaxy S 4] Grommish:
It'll be on by default in next release.
[Verizon Samsung Galaxy S 4] Dubbsy:
Compiling 4.4 takes like twice as long as 4.3. :silly:
[Verizon Samsung Galaxy S 4] Prindle19:
Can't wait for OctoKAT, hoping my Bluetooth issues from the first OctOS image will be resolved with it. Also sorry to hear about your loss, Dubsy.
[Verizon Samsung Galaxy S 4] Alxoom33:
Awesome Dubbsy!

:cool:
[Verizon Samsung Galaxy S 4] Tsukasa Buddha:
So will you guys be focused on what you have first, or integrating 4.4.1 right away?

The only new thing I've read about is the camera, but I don't even know if the Nexus 5 has the same camera.
[Verizon Samsung Galaxy S 4] Cruiserdude:
Well I don't wanna speak for them, but they are rebasing to 4.4.1. Their philosophy, and it's a smart one, is to get a solid, stable base before adding anything. Get everything working, all the kinks out, etc, before rolling the modifications in. Google just dropped 4.4.1, so it makes the most sense to get the base synced up with that first. Then further point releases of this rom can be focused on adding or improving special features, rather than doing that at the same time they are moving to a new base and trying to get a stable foundation.

Long story short, it makes a lot more sense to move to 4.4.1 now and get everything solid before adding a bunch of features that may break things. Considering the amount of changes in Kit Kat, it would be a waste of time to NOT do it this way.

Progress is going well, the base is looking great. A little patience now will pay off when it's released.
[Verizon Samsung Galaxy S 4] theHoleK:
I've been patiently waiting! I don't think I can go much longer without sending MMS and might have to move on to another ROM in lieu of a fix for this.
[Verizon Samsung Galaxy S 4] Cruiserdude:
Nothing wrong with that, gotta have the features you need when you need them. Just keep an eye on this thread, shouldn't be long now. I can assure you this is the best Kit Kat rom out there, so it's gonna be worth the wait.

Sent from my VZW Galaxy S4 Google Play Edition :)
[Verizon Samsung Galaxy S 4] pingpong1109:
I understand Android development a little and kinda want to get into the ROM making scene. Can I help with beta testing? I am not a master at C but if there is something you need help with I may be able to help.
[Verizon Samsung Galaxy S 4] cjkacz:
What device are you on?
[Verizon Samsung Galaxy S 4] Ropeguru:
Has anyone had any issues with autobackup to Google+ not turning off? I have the Verizon S4 and have turned off Autobackup in the setting, however when I take a picture with the camera, it is still auto uploading to Google.
[Verizon Samsung Galaxy S 4] Treken:
I believe you can turn it off in camera settings
[Verizon Samsung Galaxy S 4] cjkacz:
OK telling a Dev what to do or not do is really never a good idea. Especially since the first person you quoted has nothing to do with the development of this ROM.

With that said, the team is working very hard to get out a new build. We ran into some issues that are being sorted out and I assure you a build will come and it will be good. A lot of people think that because Google is pumping out updates at a fast rate lately that we should too. This team has a policy of quality not quantity. We refuse to push out an update that is half baked or incomplete just to keep up. Thanks for your patience. :)
[Verizon Samsung Galaxy S 4] Grommish:
Besides, anyone who "wants it now" can build (or try) their own. The repos are public for a reason. Have at it; but, if you expect it to build out without issue keep in mind there's a reason you already don't have a zip to flash :)
[Verizon Samsung Galaxy S 4] Treken:
Dude, if I want to give an ETA then that should be considered a courtesy not a reason to break our rules. Look at the attached pic and you'll see what I'm talking about
[Verizon Samsung Galaxy S 4] Grommish:
Enough. We understand that the compulsive flasher are chomping at the bit.

Treken is the person digging through the code. Your first quote was from Mass, second from Treken.

The issue comes from if I say "New build tomorrow!!1!!11" and it doesn't happen, the world ends for some of the XDA posters, and we have to listen to it, sift through it, or ask the FNM to come clean up the mess. We all have better things to do then that.

We promise, sincerely, to post an update for anyone to use once we have something safe and worth while to provide. If you want bleeding edge, look for when we post request for testers, or find another ROM for the mean time.

For every person that screams undying love for OctOs, consider there is a reason it working like it's does: time and pixie dust.
[Verizon Samsung Galaxy S 4] cjkacz:
For the sake of going round and round here let me clarify. Your first quote was from masstash. He was the one who had an issue with the post. He is who I was referring to. He is not a team member.

Treken is a team member as am I and Grommish. Got it? Good. Let's move on
[Verizon Samsung Galaxy S 4] theHoleK:
Does wanting to have the ability to send MMS make me a "compulsive flasher?"
[Verizon Samsung Galaxy S 4] Naddict:
Thread cleaned...

See OP, also, members need to be reminded that this is a site for developers and development, passers by and/or consumers of the products here are not entitled to anything.

If the OP/development team wants to drop a heads up about an ETA, that is their right, if you ask, and they choose to tell you to stop, then I suggest you do exactly that.

Don't like that? Then go seek membership somewhere else!

Enjoy what is offered, and take the rest of the stuff to (respectful) PM's.

Final warning in here folks.
[Verizon Samsung Galaxy S 4] Dubbsy:
No it does not.

But if you are not running one of our 4.4 builds then any bug reports at this point won't be helpful.

In general:

A lot of folks talk for us because they are in the testers group and know what is going on in the testing group and get the random updates we post there. There is a lot of work going into this. But we have working builds for almost every carrier in one format or another.

I'm booting up one from last night actually.

Love the toxic santa hat! I need one for my gangster dog for the season. I'll have to work on something later. :cool:
[Verizon Samsung Galaxy S 4] theHoleK:
Grommish contacted me and took care of my issue. Sorry for being snippy. :o
[Verizon Samsung Galaxy S 4] Grommish:
4.4.1 is up. Check the DevDB.

This is a BASE AOSP. No OctOs stuff yet.

MMS works. Wi-Fi, BT, GPS, etc.

Report any issues in the normal way.

SuperSU v1.80 - https://copy.com/3lAd7

Odex'ed GApps - https://copy.com/FSrSB
[Verizon Samsung Galaxy S 4] s0m3f00l:
Sview cover workaround!

An SVIEW cover fix by CM! Though its not perfect it does allow the hall sensor to work in conjunction with the proximity so it can be more accurate than other apps I have seen. Until SVIEW is fixed I guess this is what you can use.

http://forum.cyanogenmod.com/topic/76426-s-view-cover-x-cyanogenmod/

Thanks
[Verizon Samsung Galaxy S 4] brizey:
Is it OK to use the pa gapps that supposedly work with both odex and deodex ROMs? They are a good bit newer. I am willing to try them and see, but sometime gapps issues kind of lurk in the background then hit you when you least expect it, lol.
[Verizon Samsung Galaxy S 4] Dubbsy:
I use pa gapps currently...

sent from my Verizon Galaxy sIV
[Verizon Samsung Galaxy S 4] brizey:
Thanks!

FWIW, there are a bunch of updates for 4.4.2 today. The PA gapps have the updates. I'm going for it and will report back if I have issues.
[Verizon Samsung Galaxy S 4] Dubbsy:
We are already aware of the aosp updates. On every sync we see what revisions are available. Since we sync daily we see as soon as it's available in the readouts.

I haven't dl'd the latest pa gapps yet but I've been building out all carriers today.

sent from my Verizon Galaxy sIV
[Verizon Samsung Galaxy S 4] s0m3f00l:
I'm using the newest PA GAPPS on 4.4 and they worked fine on Dalvik... On ART TALKBACK is broken completely. As well as TEXT-to-SPEECH. This can cause periodic errors. GMAIL crashes on rare occasion as well

Also occasionally after restart there is a freeze @ SAMSUNG Galaxy S4 boot screen... All seem related to ART but The Boot screen issue happened once on Dalvik and never came back there, it still happens on ART occasionally...

Just some feedback so far for those wishing to Plunge into the cold waters of 4.4
[Verizon Samsung Galaxy S 4] Dubbsy:
Yeah as far as we are concerned anyone who turns on ART is on their own as it is known to still be in beta. Not that we aren't using it and playing with it here and there. We just aren't going to research things AOSP is still considering beta meaning tons of updates as they get it all worked out. Im syncing up 442 now.

P.S. last nights builds for all carriers. USC known to have issues right now because I found the error half way through the build.

>>>>> https://copy.com/cRR1L <<<<<

Still 4.4.1, as I said, syncing with 442 now.