[ROM][4.4.2][KOT49H][AOSP][TMO] Octo-Kat

Disclaimer: OctOS is a WIP. It has been evaluated as being stable, and is suitable for daily use in most cases. While it may be considered stable, there may be unknown bugs. The development team is not responsible for any damage to your device or your information.

Click to expand...

Click to collapse

Rules for inquiring a subject matter concerning this project are:
1. Read the OP fully.
2. For bug reports, we need a log to assess the issue. Capture a log while replicating the issue.
3. Do not ask ETA's on updates; you will be ignored.
4. Use the "search this thread" feature to make sure your question wasn't already answered by using key words.
5. Only ask a question about this project. Any questions about another ROM or project will be disregarded.
6. You don't like our OctOS symbol. Too bad.
7. You want 100% untouched/unmodified AOSP. This isn't the ROM for you.
8. Team OctOs/Octo-Kat is open source. You can always build it yourself.


AOSP Android 4.4.2 KOT49H


OctOs Settings - These features are included and can be enabled at the user's preference

• Navigation Bar (On-Screen Buttons)
• Notification LED control
• Status Bar control
• Active Display
• Application Side-Bar
• Battery Bar
• Quick-Tiles
• Theme Engine
• Power Menu Options
• Apps Ops preserved

Frequently Asked Questions
Q: Why isn't there XXXXXXX feature.
A: Shoot us a Suggestion if you want to see something added. While we are not going to promise to implement, we will always look into it

Q: But CM and all the others have..
A: ROM developers, including CM, build something they want to use. The ROM dev that includes something they won't run implies less than 100% effort to ensure it does work. As a team, we have similar goals and objectives. If XYZ ROM has a feature you want, and we don't (or don't want), feel free to use XYZ ROM, or build your own custom version of Octo-Kat

ADB Logcat tutorial here: http://xdaforums.com/showthread.php?t=1726238How to create a logcat log

Bugs:

Let us know if you run into bugs. Get Syslog from the Android Market, if you don't already have it. No logs and we can only try to recreate the event off of vague descriptions. Please also include what you were doing when it FCed or failed. Logs can be emailed to: teamoctos@gmail.com

• App-Sidebar Refresh - App-Sidebar tends to disappear
• Carrier-Option Menu choice FC
• Bluetooth when connected to Automotive Headunits
  - This is a known Android Issue and has been reported to Google here and here

Click to expand...

Click to collapse

Basic Instructions:

1. Download ROM .zip file
2. Download KitKat GApps - * See Note Below! *
3. Download latest SuperSU flashable
4. Reboot to Recovery (Note: Use Three-Finger or adb reboot recovery - ROM Manager or similar software is NOT supported)
   --- TWRP is the ONLY recovery Team OctOs uses - We do not support flashing on CWM ---
5. Flash ROM, GApps, SuperSU .zip files
6. Clear Dalvik/Cache
7. Reboot

A Note about the Team OctOs GApps
We in Team OctOs believe in choices. We believe in leaving the fundamental decisions about your phone to you.

In that spirit, Team OctOs gives you options for your GApps experiences. While any ODEX'ed GApps package should work, we offer you the choice of using some of the same GApps packages that we use ourselves, and leave the choice up to you.

You can find our Team OctOs GApps packages here, and break down into the following types:

• GPe - Google Experience
  
  • Regular GPe GApps
  • Dalvik-Enhanced GPe GApps
• AOSP
  
  • AOSP GApps
  • Dalvik-Enhanced AOSP GApps

The Dalvik-Enhanced packages are NOT ART compatible. If you plan to run ART, don't use those.

Special thanks to

• @broodplank1337 for the great aosp source to start
• @buckmarble for helping on a lot of random issues. :good:
  
  We would also like to thank
• CyanogenMod for their device specific files and drivers
• ChameleonOS
• SlimROM
• Anyone else who has ever submitted Open-Source code

Click to expand...

Click to collapse

We will only update the DevDB with Stable Releases, whenever possible. This means that the DevDB may be behind non-milestone releases. If you have an issue with compulsive flashing, or feel the need to live 'life on the edge of brick', we invite you to follow us on Facebook and/or Twitter. Any dailies that can be released, we will release there. Please note, we pull these releases after a day or two, so if the latest link posted there is empty, simply wait until the next one.

- Follow Team OctOs on Facebook


XDA:DevDB Information
OctOS-Galaxy S 4 variants, a ROM for the T-Mobile Samsung Galaxy S 4

Contributors
Grommish, Dubbsy, hlxanthus, treken, agat63, cjkacz, buckmarble, winner00, wizard0f0s
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Galaxy S 4 rooted with NON-SS recovery
Based On: AOSP

Version Information
Status: Testing
Beta Release Date: 2013-12-27

Created 2013-12-12
Last Updated 2014-01-12

Latest 4.4.2 Builds from tonight:
https://copy.com/2N0Ww

Vzw, spr, xx, usc, and tmo.

Use pa gapps. And the latest supersu.

As for it not installing or working. Is need logs to do anything. Abs frankly it should be fine because we didn't invent the device repos.... We just modded them.

sent from my Oct_jfltevzw

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.

DylanTheVillian said:

OK I'll bite! Downloading and opening another beer! Thanks!

Sent from my SGH-M919 using Tapatalk

Edit: Ouch, 4 hours left on my download, and I have 12mbps down....

Click to expand...

Click to collapse

Its being hosted by XDA. Its ~170MB file. Cancel and try again.

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.