yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] infamousxsniper:
Loving the ROM so far just two questions. Was aroma removed? And is there a way to change the phones DPi besides build.prop? Thanks.
[Verizon Samsung Galaxy S 4] Treken:
Currently there's no custom setting in Tentacles to change DPI. It may be added later. Aroma isn't our focus at this time. We have plans for it later on.
[Verizon Samsung Galaxy S 4] infamousxsniper:
Okay, no problem. I just read on the first few pages about Aroma so i thought it was in but wasn't. Thanks for answering tho.
[Verizon Samsung Galaxy S 4] Treken:
In case no one has checked, we have a new build up.
[Verizon Samsung Galaxy S 4] Aspesi4:
Treken, just installed it. So far so good. Quick question though. When installing the OTA updates, what's the best way to install? Is a wipe required? Just a dirty flash? I've tried flashing just the update and it seems like I lose apps particularly the play store. Any advice?
[Verizon Samsung Galaxy S 4] Treken:
Because we're still in beta, a clean install is recommended. Use titanium backup or a similar app to backup your apps.
[Verizon Samsung Galaxy S 4] igacek:
Great work with the ROM. I searched the thread, but couldn't find any info: Is there a way to make the "Preferred Network Type" stick with CDMA+LTE/EvDo? I am assuming that's the one we want to use on Verizon, correct? When I select it, it keeps saying GSM/WCDMA/LTE as the preferred network type, and when I reboot, I don't have the "LTE" letters near my signal bars - only the letter R.

Maybe I'm doing something wrong, but would appreciate any help. This ROM looks great.
[Verizon Samsung Galaxy S 4] Treken:
"R" means your on roaming. Do you have data when you first installed the ROM? Also, look in Settings>About phone and see what the build date and time is.
[Verizon Samsung Galaxy S 4] igacek:
Build date and time are Mon Feb 3rd, 02:40:49 EST 2014. If I switch the preferred network type to LTE/WCDMA, it shows the LTE symbol, but when I switch back to CDMA+LTE/EvDo, it brings back the R, even though I unchecked "Data roaming". I am in a large city and on TouchWiz ROMs, have zero problems with LTE or roaming. Just to double-check, the preferred network should be CDMA+LTE/EvDo for Verizon, right? As a side-note, this issue was happening with the 1-11-14 and 1-31-14 ROM build as well, if that helps. Not using SafeStrap or anything, as I flashed through TWRP.

Any help is appreciated. Thank you, Treken.
[Verizon Samsung Galaxy S 4] Dubbsy:
Verify that your CDMA subscription is set to ruim/sim instead of nv. Then set it to cdma/evdo/lte.

This is one of those issues that can be caused by either APNs OR by your last ROM. If the later you need to manually set everything above and then wipe and clean install a ROM.
[Verizon Samsung Galaxy S 4] igacek:
I've verified all of the above, still stuck with the roaming symbol. On my TouchWiz-based ROM (Hyperdrive, to be precise) I manually selected CDMA/LTE/EvDo as my preferred network, then wiped Dalvik/Data/Cache, and installed the Octo_Kat ROM per instructions, and still stuck with the Roaming symbol. If I wipe the System in TWRP then try to flash this ROM, it fails every time, so I don't wipe that. Any other ideas, or am I stuck with a TouchWiz-based 4.3 ROM until 4.4 is released? :(

Thanks!
[Verizon Samsung Galaxy S 4] KBizzle:
NVM
[Verizon Samsung Galaxy S 4] hawkxcore:
Can someone tell me if this ROM has aptx? I'm looking for an AOSP-ish ROM that still has it baked in.
[Verizon Samsung Galaxy S 4] thadialeckt:
Tell me what aptx is and then I can tell you
[Verizon Samsung Galaxy S 4] hawkxcore:
Bluetooth audio codec. Increases streaming audio quality over Bluetooth between two devices that both have aptx built in.
[Verizon Samsung Galaxy S 4] thadialeckt:
What ROM have you used this on before? And how does it work
[Verizon Samsung Galaxy S 4] hawkxcore:
All Touchwiz ROMs use it. It's a feature of the phone. It's not something that you see in the app drawer or settings.

Normally your phone pairs to the bluetooth received, compresses your audio, and sends it to the receiver. The receiver decompresses, and sends it out.

AptX is just a codec that compresses the audio differently. The only thing about it is, the source and receive both need to have the codec built in. From what I've found, AOSP based ROMs do NOT have AptX, and CAN not have AptX built in. BUT, this ROM has bits of Google Edition in it, and the Google Edition does indeed include AptX.

More reading - http://en.wikipedia.org/wiki/AptX
[Verizon Samsung Galaxy S 4] macravin:
What radio/modem do you guys use/support for this build?
[Verizon Samsung Galaxy S 4] theineffablebob:
Where do I find Oct Settings?

I just did a clean install of the latest version but I don't see Oct Settings anywhere. I see OmniSwitch in my app drawer, though.
[Verizon Samsung Galaxy S 4] Treken:
Settings>About phone>Build date
[Verizon Samsung Galaxy S 4] brandonair95:
Honestly if you're on MDK you should prolly just Odin yourself back to stock if you haven't fixed it yet
[Verizon Samsung Galaxy S 4] markwebb:
The latest build 0204 camera fc's.

Edit: installed 02/07 build and running well!
[Verizon Samsung Galaxy S 4] whozamazinka:
The Best!

First, I have to say, I love this ROM. Thank you to the whole OctOS team for putting out a fantastic ROM. I'm always looking for a stock looking ROM with minimal extras that are out of the way, and I love that this is part of the mission for OctOS. Top notch fellas...keep up the great work!

Whenever I get a new phone, my MO is to crack flash for a few months until I find the perfect ROM. Then I sit on that ROM for the rest of my phone's life, only updating if a newer code base, or a 'must have' feature comes out. But even then I may not move to newer versions as the dev/dev team releases new stuff.

So Oct is that ROM for me on my S4. I had been watching it for months, and early January finally pulled the trigger. I've been running the build from Jan 4th, and I just updated to Feb 5th for the Hangouts audio fix.

SO, all that long windedness to say, I notice from OctOTA that a new version came out yesterday, and then again today. I guess my question is this: are we at a stable place with the ROM, and now its just extras that are being added? Or should I just watch the changelogs for major changes?

Thanks again for the fantastic ROM Oct gang.
[Verizon Samsung Galaxy S 4] Treken:
We've added an about us app tonight and everything is running perfectly. You should update when we push another update.
[Verizon Samsung Galaxy S 4] igacek:
Please don't hurt me for this. Remember my "Roaming" icon issue? So yeah, any non-TouchWiz ROM apparently reports a Verizon Range Extender as "roaming" instead of LTE. I unplugged mine, and I see LTE now.

Edit: Also, if you wipe System in TWRP 2.6.3.x then try to flash the ROM, it will fail. Not sure if this is a bug with TWRP or with the ROM, though.

Edit 2: My camera is also force-closing after a second or two on the 2-7-14 ROM. Seems to do it the moment it starts to focus.
[Verizon Samsung Galaxy S 4] whozamazinka:
Treken,

Is that the Feb 7, 0724 build, or are you saying as soon as something new is posted? (I wasn't sure when the ROM was posted as compared to when you posted here.)

Thanks again, too. This really is a fantastic ROM.
[Verizon Samsung Galaxy S 4] cjkacz:
As soon as a new build is posted.

Sent from my Octo_Kat fueled Verizon S4
[Verizon Samsung Galaxy S 4] s44:
Flashed a new one as of this morning. Very nice: the little notification toggle ribbon adds a lot to the plain-Google base. But

(1) why do I have both AOSP and Google dialers? (With the GPE-Dalvik Gapps)

(2) how is there yet another build tonight? do I need to clean flash again?
[Verizon Samsung Galaxy S 4] Grommish:
GPe Gapps adds the GPe dialer. You can't ditch the stock dialer because it still uses it, so both hang out on app drawer.

As far builds, you can certainly dirty flash; HOWEVER, if you run into problems you can't report them if you didn't clean wipe. If you run into problems, clean flash and see if it still exists. As always, don't restore system apps
[Verizon Samsung Galaxy S 4] Dubbsy:
You don't NEED to do anything. :good: We build all day long. We don't always push them to the site. We built about 10 verizon builds between [MENTION=3236955]Treken[/MENTION] and I yesterday. The first build pushed to the OTA site was around lunch when I was testing. The last was around 8 and I was building out all the JF series devices and a few d2s as well. The later build has Google Dialer open source features added to the stock dialer.

The new GPE GApps on the site as of yesterday remove the Google Dialer for the time and update all the GApps to current. The changes to the AOSP dialer aren't the same as Google's but we are still looking at it and other options. I needed to remove the Google Dialer in order to test the hotseat locations for the new dialer though. But you can use whichever GApps you want. The new ones, the old ones, or whichever ones you want to use. :good:
[Verizon Samsung Galaxy S 4] ikn0wagh0st:
After flashing the latest build 2/13, my settings are FCing immediately on boot. I am redownloading in the event of a bad download, and will report back if this remedies the issue.

EDIT: Did not remedy the issue.
[Verizon Samsung Galaxy S 4] Treken:
Are you guys sending us Log cats of these events?
[Verizon Samsung Galaxy S 4] ikn0wagh0st:
I'm not sure how to, but I will look into it and send it ASAP.
[Verizon Samsung Galaxy S 4] Grommish:
In the OP, it outlines logcats.

Easiest way, get syslog from the play store
[Verizon Samsung Galaxy S 4] ikn0wagh0st:
Perfect, thank you. Logcat has been sent. Also, I am noticing that I also cannot access the Octos custom settings. Not sure if this option is disabled or broken.
[Verizon Samsung Galaxy S 4] Treken:
I believe we tell you how to access our settings in OP as well. Settings>About phone>Build date
[Verizon Samsung Galaxy S 4] ikn0wagh0st:
I know how to access the settings.. Just when I click on octos advanced settings nothing happens.
[Verizon Samsung Galaxy S 4] Chuckleb0ne:
Camera and Bluetooth should be working perfectly.
[Verizon Samsung Galaxy S 4] Treken:
We are using Samsung proprietary files released from Samsung. Should be the same as what GPE uses.
[Verizon Samsung Galaxy S 4] Treken:
These are the only ones available that I know of. If you care to lend a hand that would be great.

https://github.com/TheMuppets/proprietary_vendor_samsung
[Verizon Samsung Galaxy S 4] cjkacz:
That's not an Aosp ROM. It says it has "the features of an aosp ROM"

Sent from my Octo_Kat fueled Verizon S4
[Verizon Samsung Galaxy S 4] Treken:
To my knowledge we are using native divers that were pulled directly from the device
[Verizon Samsung Galaxy S 4] MassStash:
Gooooot cha, koo kool. No issues = no need for drivers I don't think. But if it's just curiosity, what the deal is that this is not GPe rom port from the GPe device, there are many issues porting roms that are meant for one carrier device, or international, to another carrier device, non-international. Even if the phone's are ridiculously similar. If this is true however, they may be a looooot less issues, seemingly none. Alternativly, it would seem the way the devs here decided to go was with AOSP base, meaning NOT GPe, NOT a port, and built straight from android AOSP source. This way, the issues involded are fewer, and more workable because they ARE NOT PROPRIETARY drivers to work with. Fixing proprietary stuff is next to impossible. Sometimes doable, but so tough most people are like, "eh".

Also, it would seem that a deal about this rom, seen in how smooth and awesome it is, is that it is about 2-3% based on cm, and more based around AOSP. That means it's like some almost pure Columbian if ya know what I'm sayin haha. Really good stuff.

All in all, this is not GPe port, so it does not have the drivers necessarily from GPe rom, it has the drivers treken linked, which are what all AOSP roms use pretty sure. And most the things in question seem to be functioning pretty well, so unless you can find us some drivers we can try to work to enhance the experience, I think things are doing well thus far.
[Verizon Samsung Galaxy S 4] whozamazinka:
Nice theming!

Guys,

Gotta say, I love the new 'true' kitkat themed dialer, and settings and such. It looks really sharp. Keep up the good work!
[Verizon Samsung Galaxy S 4] cjkacz:
Not a gpe port :) But glad you are enjoying it!

Sent from my Octo_Kat fueled Verizon S4
[Verizon Samsung Galaxy S 4] arlissnd:
In the op it says rooted s4 not using SS. I have the Verizon SCH-I545 on MDK. Can I flash this rom? Just wondering because I got the impression that this rom was for dev edition phones only. Thanks
[Verizon Samsung Galaxy S 4] Grommish:
Safe strapped phone lock the kernel. You cannot run OctOs on a TW kernel.
[Verizon Samsung Galaxy S 4] arlissnd:
I should have given more details. I am not on SS. I have twrp and I'm LOKI'd.
[Verizon Samsung Galaxy S 4] Smeagol1375:
I would say you are good to go, one thing to realize if you are not using TWRP 2.5.0.2 you may have issues flashing the ROM.
[Verizon Samsung Galaxy S 4] arlissnd:
Thanks so much! I appreciate the help.
[Verizon Samsung Galaxy S 4] jdegroot:
Known Issues: Compass? Chromecast?

Hey There,

Just checking in about some past known issues to see if they're still problems. Has the Google Play Chromecast crashing bug been fixed? How about the known issue listed on the website that "Compass and 3-Axis sensor does not function". Is that still an issue in the 0215 build for the S4? I have seen a few of the devs say here that everything should be working, but I don't see fixes for either of those issues listed on the changelog...
[Verizon Samsung Galaxy S 4] Naddict:
Thread lightly cleaned.

This ROM is a good one, please do not use this thread to compare to any other ROM, that is generally not good form and not very respectful of the members (in here) who are trying to make this build even better.
[Verizon Samsung Galaxy S 4] macravin:
Is there a way to get the stock lock screen slider. I liked the octopus at first, but now I'd rather it be stock.

Thank you for the ROM btw. It runs pretty much bug free and has the extra features (like ext4 extsd support) that the GE and other stock Roms can't provide.

Sent from my SCH-I545
[Verizon Samsung Galaxy S 4] s0m3f00l:
Got 2 potential bugs

The rom on the Octos website directed to from octota is incorrect. It's an old version as of this morning. And as soon as you flash it. It asks you to download a new version. The download ends in 2111 while update points to 0716. Also Oct ota spams every hour even if it's set to never or weekly. I am on vzw version of the rom.
[Verizon Samsung Galaxy S 4] Treken:
We're getting this fixed. On a side note, I'm working with dubbsy on getting a unified build working. Thanks to cm we might be able to consolidate d2 and jf devices.
[Verizon Samsung Galaxy S 4] s44:
I swap battery a lot, and about 50% of the time after powering back on the phone sticks on the Samsung/Custom screen and requires a battery pull to retry before it gets to the OctOS screen and actual boot. This can happen twice in a row, and has only been an issue since I flashed 2/11 OctOS (was on a TW ROM before).
[Verizon Samsung Galaxy S 4] Treken:
Then you've been lucky because it happens quite often for me on the S4.
[Verizon Samsung Galaxy S 4] markwebb:
Likewise for me but I notice it never occurs on tw Roms.
[Verizon Samsung Galaxy S 4] Treken:
When you think about it, TW was made specially for our phone. The fact that we've gotten aosp to run on it is a feat in and of itself. :)
[Verizon Samsung Galaxy S 4] Smeagol1375:
I have seen the same thing myself. As strange as it might sound, I have found that if I boot into recovery first. Then restart the system, it seems to boot right up most of the time.

Not sure if that will help or not. Thought I would share.
[Verizon Samsung Galaxy S 4] s44:
True. But the GPE software is specially for our phone too, which may be why people were hoping it would be the base for this ROM.

Interesting idea! Might try that.
[Verizon Samsung Galaxy S 4] gandhidog:
I get a fc when clicking notification led in octos settings. Let me know if you'd like a log. On 2/21 build.
[Verizon Samsung Galaxy S 4] Dubbsy:
I believe this was taken care of in testing already. I am on the OTA also. I built out all the devices last night into this morning. They should be pushed live as soon as our web/server guy gets a moment.

We build every day, not always getting pushed to the site. The testers try to break it, and we try to fix it. :good:

I need to update the thread. We have been on KVT49L for awhile now. and the hidden features include:

OctPapers

OctOTA

Tapping the Build Date will bring up:

T-Mobile theme manager support

Quick Tiles

Notification drawer ribbon

Notification LED

Status Bar modifications

Nav Bar

Lockscreen Shortcuts

Custom progress bar options

SuperSU is baked in now

Power Menu options

ChaOS's active display

-Battery ring around the lock handle under these settings also

Screen Recorder

Quiet Hours

Clear All button and Memory Indicator options

And OmniSwitch option(if you want it vs default)

And if you tap the Kernel version like a mad man you'll get our CandyPuss :victory:

We've also been building jflte(unified) but it's not ready in our eyes to replace the good working individual builds(or at least mostly working as it seems when we add features things get goofy)

It can't be the base for a built from source rom. Bits can be added in. Parts can be patched. But it can never be the base unless samsung and google pony up the entire source.

I've been lucky, I don't have hang at boot screen issues. I also don't ever get the Samsung custom screen unless I flash a bad kernel or recovery. I turn off my phone fairly frequently. I'm not sure if it's a kernel issue, recovery issue, or what that causes the hang. I did get boot hang when I was on TWRP 2.6.3.1 but I am on 2.5.0.2 now.
[Verizon Samsung Galaxy S 4] Grommish:
Come Chat with Team OctOs!

On March 6, 2014, Team OctOs will be holding a Google Hangout Meet and Greet/Q&A session beginning at 9AM Eastern time. This will continue until we get bored with it.

Send an email to: chat@teamoctos.com with your Google Hangout email (if different) and we'll send the invite as the time comes closer.

Bring questions, comments, or just come to hangout.
[Verizon Samsung Galaxy S 4] Grommish:
Translators Needed!

We are currently looking for translators to help localize OctOs into other languages.

Many of the main ROM components are already translated (built-in), but anything that we've changed or added won't be. Currently, we are "English predominate" speakering team, but many of the users may not be!

If you would like to help bring OctOs to your language, check out: https://crowdin.net/project/team-octos-octo-kat-android-ro

You can sign up as a Translator and then start translating the OctOs project. This makes it easy to identify and translate the individual strings.
[Verizon Samsung Galaxy S 4] s44:
Is this a known issue? On 0226-1551, when I take/make a call through earphones, the sound only comes out of the left side. All other earphone sound is fine.
[Verizon Samsung Galaxy S 4] Dubbsy:
I can test this tomorrow when I get to work. I don't have any stereo headsets here right now. It hasn't been reported before this that I've noticed though.

My right sided headset works fine, but that doesn't mean anything to stereo sound.

Edit* I tested this with my work headset and both sides worked. Ive not heard anyone else say anything yet. I'll keep an eye out for others.
[Verizon Samsung Galaxy S 4] cjkacz:
Anyone check out our new Google Plus community??

https://plus.google.com/communities/102188586220747781076?partnerid=gplp
[Verizon Samsung Galaxy S 4] s44:
Any verdict?

Neat.

Anyone dirty flashed 3/04 yet?
[Verizon Samsung Galaxy S 4] macravin:
I heard CM finally fixed the boot problem. Have these fixes been merged yet?

Sent from my SCH-I545
[Verizon Samsung Galaxy S 4] Treken:
I'm not aware of the fix. If you would like to contribute and find the commit I'll add it. I'm bogged down with rebuilding our Tentacles app for custom settings.
[Verizon Samsung Galaxy S 4] Naddict:
[MENTION=5168775]Dubbsy[/MENTION]

Please check your pm
[Verizon Samsung Galaxy S 4] Dubbsy:
You got it :)
[Verizon Samsung Galaxy S 4] red3razor:
Signatures for all

Hello everyone, I have made some custom signatures if you would like to use them as your signature in a forum or wherever :)

8 colors: https://copy.com/MXw9lbAww1lS
[Verizon Samsung Galaxy S 4] s44:
So what's changed in the two March builds? Not sure where the repository is...
[Verizon Samsung Galaxy S 4] cjkacz:
Now building with Sabermod for Rom and Linaro for kernel, Omnigears,fix d2mtro,fix auto collapse on notification drop down,added several new devices to the repo,fixed dialer and general AOSP updates.
[Verizon Samsung Galaxy S 4] ecsnead69:
Is this ROM plagued with the APN issues that the GPE ROMs are having?
[Verizon Samsung Galaxy S 4] Dubbsy:
This is not a GPE port. Or based on GPE. We try to bring a GPE experience to AOSP. But we also pull in mods from other Roms.

For vzw there aren't any APN issues that I've found. I use it everyday on VZW with no problem.
[Verizon Samsung Galaxy S 4] ecsnead69:
Great, I am on Evil Red too. I will give this a try then. So if you don't enable the octsettings thru build number, its a stock AOSP ROM?
[Verizon Samsung Galaxy S 4] Dubbsy:
It's a mostly stock AOSP experience until you go into the hidden settings.

I say mostly because progress bar defaults to on instead of off(for now), some of the tiles are backwards (long press vs short press), and we have expandable volume default(this is staying)

We are slowly working through these discrepancies. We also just fully redid the Tentacles settings and are adding AOSPAL's lock screen notifications and few other tweaks.

Today I was working on adding Flo support, and the Dons were working on Grouper. Should get Flo don't tomorrow. I'll hop on grouper if that's not done. Then onto the transformer tabs. Then onto the HTC one-x and one.
[Verizon Samsung Galaxy S 4] ilinimud:
Did the lockscreen notifications get added in today?
[Verizon Samsung Galaxy S 4] Treken:
It has been added yes...but you won't see it until we officially swap to the new Tentacles. I'm working on finishing it up this week.
[Verizon Samsung Galaxy S 4] ecsnead69:
Just want to verify before flashing, SU is baked in now? The install instructions still say to flash the latest su zip... Thanks
[Verizon Samsung Galaxy S 4] hlxanthus:
Yes SuperSU and binaries are baked in now.

Sent from my Galaxy S4
[Verizon Samsung Galaxy S 4] Treken:
OP updated. Thanks
[Verizon Samsung Galaxy S 4] heath2805:
edit: deleted.
[Verizon Samsung Galaxy S 4] saul1991:
I flashed the 3/13 build and it failed. Anybody else have this issue?
[Verizon Samsung Galaxy S 4] Treken:
Can you be more specific? It failed..ok, but what was the message it gave you? There should be a message saying why it failed.
[Verizon Samsung Galaxy S 4] saul1991:
so i flashed with out wiping data or cache, i figured it, it was going to fail and i didnt want to restore lol and it flashed succesfully. thanks man im going to give the a rom a run
[Verizon Samsung Galaxy S 4] s44:
Dirty flashed from 2/26 to 3/13... no issues yet.
[Verizon Samsung Galaxy S 4] ilinimud:
How is the work on the new tentacles app coming along? Looking forward to the lock screen notification addition.
[Verizon Samsung Galaxy S 4] mrw1215:
I feel like I'm going to get yelled at for asking this, considering I saw the little note in the OP, but is there any way at all to turn off the Octo lock on the lock screen and just use the stock one?
[Verizon Samsung Galaxy S 4] urrgevo:
Most themes will replace that
[Verizon Samsung Galaxy S 4] ecsnead69:
Does the phone display work correctly on this ROM? I have tried several and none of them will turn the screen back on during a call???
[Verizon Samsung Galaxy S 4] thadialeckt:
Everything works for me