yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 3 Q&A, Help & Troubleshooting] lare:
What would be the best file manager for Note 3?
[Galaxy Note 3 Q&A, Help & Troubleshooting] danieljamie:
It is subjective but I like ES File Explorer. Free and has root options.
[Galaxy Note 3 Q&A, Help & Troubleshooting] congusto:
+1, it can connect to cloud services, has extensive LAN support, to name another few
[Galaxy Note 3 Q&A, Help & Troubleshooting] MohJee:
Best explorer is by far Solid Explorer.
[Galaxy Note 3 Q&A, Help & Troubleshooting] htc6500uk:
It's personal taste but I find ES is the one I use the most, next Solid Explorer and finally Astro File Manager. Try 'em and pick your fave - or have all three!
[Galaxy Note 3 Q&A, Help & Troubleshooting] mouse100:
Solid explorer on first place

Galaxy Note 3 | SM-9005 | Tapatalk
[Galaxy Note 3 Q&A, Help & Troubleshooting] Mad383Max:
+1
[Galaxy Note 3 Q&A, Help & Troubleshooting] Deleted member 1009733:
I would go for ES too.
[Verizon Samsung Galaxy S 4] Dubbsy:
Reserved

About OctOS:

Treken (Co-Founder) – Coding, Scripting, Github, Troubleshooting

Dubbsy (Co-Founder) - Coding, Scripting, Github, Troubleshooting

HLXanthus - Graphic Design, Aroma Packaging

CJKacz – Lead Tester / Tester Oversight

Grommish - Server, Tools, Social Media

Agat63 – Custom Kernel

Cruiserdude – Testing and Networking

Red3razor – Graphic Design and Themes

SimonTuffGuy – Website and Hosting

Facebook

Twitter

Official Website

Our mission statement is simple. REAL AOSP base. Google Play Edition Layout if so desired by using the GPE GApps. AOSP GApps also available for the purists. With the settings you all know and love hidden away in our own setup called OctSettings under Development Settings hidden to keep the look of AOSP. We call this

REAL AOSP+GPE+OctSettings=OctOS

Enjoy Friends!
[Verizon Samsung Galaxy S 4] Dubbsy:
Reserved

Aroma has been put on hold until we get the ROM exactly how we want it and start getting it ported to all the other devices.
[Verizon Samsung Galaxy S 4] hlxanthus:
The aroma interface is my major part here. If you have aroma specific questions direct them at me like this

Thanks all and enjoy!!
[Verizon Samsung Galaxy S 4] Grommish:
Whee!

Follow us on Facebook and Twitter at the following address:

https://www.facebook.com/TeamOctOs

and

https://www.twitter.com/teamoctos
[Verizon Samsung Galaxy S 4] B-Nice_88:
Awesome

Mines!
[Verizon Samsung Galaxy S 4] cjkacz:
Me
[Verizon Samsung Galaxy S 4] an21281:
Yes!!!!

Sent from SGS4 PAC4.3
[Verizon Samsung Galaxy S 4] GreatDayChap:
Been waiting for this, can't wait to try it out. Thanks, team OctOS!
[Verizon Samsung Galaxy S 4] daniel4653:
Glad to see this

---------- Post added at 11:55 AM ---------- Previous post was at 11:54 AM ----------

And for sprint users, we download the same zip. As its multi carrier ?
[Verizon Samsung Galaxy S 4] Dubbsy:
Yep, all carriers will be built in one zip. Sprint and Verizon are the only ones fully setup right now. [MENTION=1975745]Grommish[/MENTION] & [MENTION=2953465]agat63[/MENTION] are on Sprint. The rest of us are Verizon users.

And a version of this has been on all our phones for awhile. It's stable for us. :good:
[Verizon Samsung Galaxy S 4] Pixelation:
Thanks Dubs, and the others that made this possible!!! :) Dling now!
[Verizon Samsung Galaxy S 4] paulg1981:
what seperates this ROM from the other AOSP roms? Is it AOSP or CM source? What features are included if any? Linaro -03 compiled?

Not trying to be disrespectful just curious about the differences?
[Verizon Samsung Galaxy S 4] hlxanthus:
The goal is to remain as true to AOSP as possible. Right now the stock rom is just AOSP made to run on the GS4 varients. Right now, features are only what is added via aroma; apps, xPosed, different cameras, etc. We are striving to duplicate the Google Edition from an AOSP source. Later a modified AOSP will become available, and become an alternate aroma option
[Verizon Samsung Galaxy S 4] Dubbsy:
It's built from mostly the latest (4.3_r3.1) AOSP source. The source that isn't AOSP is because AOSP doesn't support the gs4 or its chipset. Those components are pulled from CM. We've been working on integrating Google/Samsung released Google Play Edition source also. Some has been fully integrated and some haven't. [MENTION=3236955]Treken[/MENTION] could answer the question about linaro better than I can.

Other reasons it's different are already posted...

sent from my Verizon Galaxy sIV
[Verizon Samsung Galaxy S 4] Tsukasa Buddha:
Yay, downloading!

So what is the OctOS kernel vs the stock 4.3?
[Verizon Samsung Galaxy S 4] Grommish:
OctOs comes with 3 kernel options.

1) Stock 4.3

2) Elite Kernel

3) AOSP Kernel from Agat63

Elite and Agat's Kernel are OC/UV'able and other tweaks (hotplug'ing CPU cores, etc)
[Verizon Samsung Galaxy S 4] GreatDayChap:
Just booted this ROM for the first time, nice touch with the boot animation! I'll be sure to report any bugs I come across.

EDIT: During setup, instead of displaying networks, it says "to see available networks, turn Wi-Fi on."

EDIT2: After skipping most of the setup I'm unable to enable Wi-Fi.
[Verizon Samsung Galaxy S 4] Grommish:
Got log?

Did you Factory Reset? Which Kernel did you pick.
[Verizon Samsung Galaxy S 4] hlxanthus:
We really need more information . . You on Sprint or Verizon . . Factory Reset? kernel installed?

LOL Gromm, great minds think alike!!
[Verizon Samsung Galaxy S 4] scarmon25:
If you need a tester let me know. I am very thorough as I beta many apps for android.
[Verizon Samsung Galaxy S 4] gwallers:
Anyone having trouble with getting stuck at Samsung boot screen on reboots? I thought maybe it was my recovery so I switched to CWM from TWRP and still getting same results. Its not everytime but a lot of the reboots I have to pull battery.

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

May have already been mentioned. Two glitches i noticed both are camera related.

if you use the aosp camera and gallery and try to change the size the camera takes pics it force closes...

if you use the GPe Camera and use the front facing camera you get the green lines in your pics..

don't know that these are really rom related but just letting it be known...
[Verizon Samsung Galaxy S 4] scarmon25:
Shadowgun deadzone got updated today. Makes me wonder if anything was done that would make it work on current builds. If I wasn't expecting phone calls right now then I would flash and see.
[Verizon Samsung Galaxy S 4] hlxanthus:
My current setup is via the Google edition preset option and front facing camera doesn't have the green lines on my end. Hopefully that means it will be fixed on the next release for you. I will have to check for the aosp camera bit

Sent from my Galaxy S4
[Verizon Samsung Galaxy S 4] scarmon25:
Is the GPE 4.2 or 4.3
[Verizon Samsung Galaxy S 4] hlxanthus:
The apk in the build is pulled from the 4.3 system dump if I remember correctly
[Verizon Samsung Galaxy S 4] scarmon25:
So the entire GPE build is 4.3?

---------- Post added at 10:02 PM ---------- Previous post was at 10:01 PM ----------

Cause j know shadowgun runs on that one?
[Verizon Samsung Galaxy S 4] GreatDayChap:
Are you talking about Dubbsy's GPE ROM? That is a different project, it is 4.2.2
[Verizon Samsung Galaxy S 4] scarmon25:
Nah. I though I saw a option in the aroma installer to install AOSP or gpe but looking back it was the gpe camera. My mistake.
[Verizon Samsung Galaxy S 4] red3razor:
@ team OctOs: mentioned possibly adding theme engine in future... Would this be compatible with the the cm/aokp themes then?
[Verizon Samsung Galaxy S 4] Treken:
Let me clarify...This project is compiled entirely from AOSP source minus device specific files that aren't supported by AOSP. We have modified things a bit so that it mimics GE as closely as possible. GE is not open source so we can't compile directly from their files which is why we chose the route we did. It is currently at branch 4.3_r3.1. The reason we are having trouble with Shadow Gun is because there is an issue with one if not more of our AOSP repos we pull from. We are working hard to find a solution and will post news of it running on OctOS when we find out what it is.
[Verizon Samsung Galaxy S 4] scarmon25:
Shadowgun had an update today. Not sure if that would help in anyway but figured I'd mention it. I'm patient so no worries.
[Verizon Samsung Galaxy S 4] conflikt:
Where to get the gapps for this as they arent in op. Link is messed up??
[Verizon Samsung Galaxy S 4] scarmon25:
Gapps are in the aroma installer. You choose them as you install.
[Verizon Samsung Galaxy S 4] elude79:
A fews issues

Hi Dev,

So far, ROM run very smooth.

A fews incident maybe Dev can help.

1. Randomly i can't call out. (Phone must be reboot before i can make a call).

2. No Reboot option when pressed n hold Power.

3. Can't pick ringtones from External SD.

4. Any change of Volume/speaker hack? Speaker and ear piece seem to be very low. ;)

5. Camera also randomly stuck. (Must reboot):crying:

Will reports more when issue(s) occur.

Thanks:cool:
[Verizon Samsung Galaxy S 4] Dubbsy:
1. That's strange

2. That's not a bug... It's a lack of features included in real GE and AOSP. called vanilla...

3. No idea I'll have to see what's up with that

4. The hacks posted in the forums should work fine

5. Camera is an ongoing PITA

sent from my Verizon Galaxy sIV
[Verizon Samsung Galaxy S 4] Alxoom33:
Hi, noticed there was a 10/7 update. What has changed since origional 10/2 release. I know there was a kernel fix early on....
[Verizon Samsung Galaxy S 4] markwebb:
cool! I hope these are some of the dev edition fixes. But download link says 10/2??? Probably hasn't updated yet. Last minute fixes. :)
[Verizon Samsung Galaxy S 4] uribees:
Is there a changelog for the newest release?
[Verizon Samsung Galaxy S 4] Grommish:
As stated elsewhere, we need the system logs from the time these issues are occurring. We can't guess as to what the issue might be. This is especially important for bug reports like your first and fifth issues.

As for number three, we include ViperFX. The included APK in the released Package I would avoid in lieu of downloading it directly from the thread, as that release had it as a system APK and updating it can cause issues. The ViperFX update corrected driver installation issues with the S4.

You can find the ViperFX thread at:

http://xdaforums.com/showthread.php?p=39156703

The ViperFX issues have been fixed in the upcoming Aroma release (if it hasn't been pushed already).
[Verizon Samsung Galaxy S 4] elude79:
Thanks for your quick respond. :)

---------- Post added at 03:17 PM ---------- Previous post was at 03:09 PM ----------

DL it now..thanks
[Verizon Samsung Galaxy S 4] Dubbsy:
That wasn't a ROM update. Just a general thread layout update. [MENTION=3236955]Treken[/MENTION] was working on it with [MENTION=4129069]hlxanthus[/MENTION] for graphics. [MENTION=1975745]Grommish[/MENTION] and [MENTION=4129069]hlxanthus[/MENTION] have been working on automating the aroma build. I've been working on tracking down bugs and potential fixes. To piggy back grom's aroma work I've also been trying to find a quicker way to build all 9 carriers in one step.

We do have a few newer aroma packages but we are trying to get it cleaned up and I need to get a functioning USC build.

sent from my Verizon Galaxy sIV
[Verizon Samsung Galaxy S 4] lightiv:
Awesome ROM

I just want to drop in and what an awesome rom this is. Simply the bare necessities, clean and fast performance.

The only delta I can find is MMS doesn't work for me on the 3G network. It is fine of the 4G network.

On question, can I tether with this rom and what tethering app should I use (when ever Spint gets 4G to my building)?
[Verizon Samsung Galaxy S 4] Dubbsy:
I tether daily. But I am on verizon. And I use the built in wifi tether, usb tether, and bluetooth tether depending on situation.

I know MMS with the stock-non-quickreply Mms works on 3g for Grommish. He is on sprint and sends me pics on each new build, and where he is, he only has 3g. Maybe it's locale based. I haven't ran across an issue like that before
[Verizon Samsung Galaxy S 4] lightiv:
Thanks, network wise things are rather strange. If you are close to major roadways and airports you get 4G on Sprint. They haven't upgraded our closest tower yet so I had to give up tethering when I got my new phone.

I don't see any tethering app and I assume that is because I chose the OctOS install instead of the Customized install?
[Verizon Samsung Galaxy S 4] hlxanthus:
You are not seeing an app because it is a native android feature.

Dubbsy is referring to the native tethering option. Found in settings > wireless & networks > more

Sent from my Galaxy S4
[Verizon Samsung Galaxy S 4] jwattt:
So the only thing I see that happens that strange is typically on all of the other roms I've been on when data is connected it has a blue symbol and Grey would mean a bad connection. I seem to be having Grey signals most of the time and randomly they seem to change to blue. However my data works fine even if it's Grey. Is this an issue or am I miss understanding the color sequence?
[Verizon Samsung Galaxy S 4] hlxanthus:
The grey to blue difference is your connection to Google services. This has nothing to do with your actual cellular data connection. The fluctuation is likely some quirks Google has been having on their end lately.

Sent from my Galaxy S4
[Verizon Samsung Galaxy S 4] lightiv:
Got it thanks!
[Verizon Samsung Galaxy S 4] brizey:
This ROM is sweet. Spent some time with my 2012 N7 today (playing star command...holy addictive batman!). Came back to this and was like woah.
[Verizon Samsung Galaxy S 4] royredman:
Is there a way you can install the Samsung voice recorder app on this ROM?
[Verizon Samsung Galaxy S 4] Dubbsy:
As a quick update. I fouled up the camera in an effort to fix the game. A series of reverts later... then android updated to 4.3.1_r1(JLS36I). So I updated everything today for that with some additional fixes and now she's building again.

Because of all of this, I found why some of the other variants won't work as built. So I'll be able to fix that tonight. It's specifically related to AT&T and U.S.Cellular not Sprint or Verizon which are currently released and do work.
[Verizon Samsung Galaxy S 4] Dubbsy:
If you can install the Samsung voice recorder app on other AOSP roms then sure it should install just fine.

The only reasons that it might not work is the fact that the app was designed and built using 4.2.2's api which sometimes causes and issue and many times does not. OR samsung could have made some special lib files specific to the noise-capturing app, which would be about half stupid IMO because what is there to hide in a noise recording app? Does it do some crazy audio auto-tuning on the fly?
[Verizon Samsung Galaxy S 4] Grommish:
Samsung.. Being stupid about code? Wha...? :rolleyes::p
[Verizon Samsung Galaxy S 4] red3razor:
I'm curious to know if the theme engine that may be built into this rom will be compatible with the cm/aokp themes (theme chooser)?
[Verizon Samsung Galaxy S 4] ioos:
Is the lack of proper vendor files the reason that AOSP roms typically have signal issues when compared to TW?
[Verizon Samsung Galaxy S 4] Cruiserdude:
And camera issues, and GPS issues, and graphics issues, and IR issues, so on and so forth. It's why any device has a bunch of issues when it first gets an AOSP or CM build, and why many of them continue. Using CAF libraries allows the SoC to work, so the device boots and runs, and many other basic functions are fairly easy to get working. But device specific hardware will pose more of a challenge, and often won't ever be as good as the manufacturer's base, due to not having the proper device files or the source to build them.

But if we can get Samsung to release these files to us, we can theoretically build a rom that's as solid as TW with the performance of AOSP. It's been done before for other devices, with predictably awesome results. This rom has the advantage of being AOSP instead of CM/CAF code on top of the CAR libraries, which is why it already runs better and likely will be more stable than most once the team has this where they want it. The CAF codebase changes constantly, which introduces it's own instabilities, incompatibilities, bugs, errors, etc (aka broken ****). So building a CAF rom on top of incomplete CAF libraries will tend to break more things more often than an AOSP rom atop the same libraries.

Ironically, CM now even builds CAF on actual Nexus devices, which makes no sense on a device that already has full AOSP source and vendor files. But many Nexus roms are built off of CM, and so a lot of work out there for Nexii is now no more stable than for devices like our own. Only CM seems to know why they do that, and they're not talking.

You can of course avoid all this nonsense by sticking with stock or roms based off it. But there are plenty of people out there that seem to enjoy buying a fully AOSP-supported device, and then putting it on the same unstable crap the rest of the devices are forced to use. My hope is that Samsung will release AOSP device files, at least for the GPe devices, so we can have pure and complete AOSP (plus whatever methods used to obtain CDMA functionality). Maybe someday everyone will be like Sony and release AOSP device files for everything they make. But that would take strong encouragement from Google, and I just don't see that happening anytime soon.

Looking forward to the new build!

:thumbup:
[Verizon Samsung Galaxy S 4] Dubbsy:
What he said.

Well done...

sent from my Verizon Galaxy sIV
[Verizon Samsung Galaxy S 4] Dubbsy:
Yeah we are going to use T-Mobile theme engine. The reason for that is I own a lot of cm10+ themes. And I personally like convenience ;)

That and it's the most wildly used theme engine... Meaning tons of options.

sent from my Verizon Galaxy sIV
[Verizon Samsung Galaxy S 4] xM Minton Mx:
I see you finally got this up and running... Awesome work. Still going to sit in the car and wait it out a little longer. Lol

If I helped don't forget to hit that thanks button.

Sent from my Hyperdrive S4
[Verizon Samsung Galaxy S 4] joshm.1219:
I figured out in the passcode in aroma easy enough lol but how do I know what the extra goodies are? Do I have to flash again and see what I'm missing? :p

This is SICK btw. Admittedly, this is my first GPe ROM, but it's easy to see the potential of this ROM when it's fully fleshed-out.

Also is there a way to re enable the capacitive keys if you selected the navbar in aroma? There's no menu button if you pick the navbar.

Finally, is there options for editing the statusbar etc. yet? Am I just missing something...
[Verizon Samsung Galaxy S 4] GreatDayChap:
Use xposed for your nav bar and status bar modifying needs, GravityBox works nicely.
[Verizon Samsung Galaxy S 4] hlxanthus:
There would be no doubt if you did it correctly . .

As for menu, you access it via the 3 dot menus in apps or sometimes the navbar.

Sent from my Galaxy S4
[Verizon Samsung Galaxy S 4] Chuckleb0ne:
Can't wait for the update! Cyanogenmod is just not cutting it.
[Verizon Samsung Galaxy S 4] red3razor:
I was hoping :) I also use often. Thanks! (Your AOSP source roms are the only ones I've been willing to sacrifice themes for)
[Verizon Samsung Galaxy S 4] Dubbsy:
Even then I didn't... plain is boring. I used xposed theme engine, xblast, and gravitybox on those builds.

I'm uploading a new verizon and sprint build that we put together last night. Usc is going to have to wait until I relink all the repos properly. Whoever initially made the device repos also made the proprietary files repos. And named the ATT and USC models 2 totally separate things. So when you build using jflteusc or jflteatt it logically looks for the same from proprietary...Well, those are named jflter970 and jfltei337. Brilliance right? :good:
[Verizon Samsung Galaxy S 4] red3razor:
I tried xposed themes, but could not find any complete 4.3 ones in red. Does your last night build include the TMO theme engine?
[Verizon Samsung Galaxy S 4] Dubbsy:
No and it likely won't be included for a few updates.

All of the alternate ui options are being released at the same time. Not individually.

And getting all carriers supported is currently ahead of that in the wicked long to do list.

PS, OP updated and build is about 15% uploaded.
[Verizon Samsung Galaxy S 4] Dubbsy:
And uploaded.

We are working on the updater. If it fails, get a log, and try to boot it anyway. I think it's something at the end. We'll have another update shortly anyway
[Verizon Samsung Galaxy S 4] markwebb:
Wow.. total fail on Dev edition both custom and default aroma install. Was expecting 3 sigs but found 6 was the error?
[Verizon Samsung Galaxy S 4] kent9272:
I don't have the option to restart or go into recovery unless I turn off the phone. What step did I miss?
[Verizon Samsung Galaxy S 4] Cheater912:
That's not a feature of AOSP. Install GravityBox for the option.
[Verizon Samsung Galaxy S 4] kent9272:
I checked Google play and I couldn't find it and another question, sorry, I've only been getting one bar for my signal.
[Verizon Samsung Galaxy S 4] mchief298:
Have to install xposed framework and then install gravitybox inside that.
[Verizon Samsung Galaxy S 4] Alxoom33:
Dubbsy, dl 10/11 build, made sure MD5 matched, did full wipe and individually wiped partitions and got a big fail, twice. Flashed the build from 10/2 and booted up fine. What is the difference between the two recent builds and the prior build? I'm on vzw S4 running MDK.

Thanks,

PS about phone says my build is 4.3 JLS36G end.treken 20130927.164018 test-keys.Thanks

Edit: It said Failed in TWRP but Oct booted up fine. Weird now I'm on 4.3.1:cool:
[Verizon Samsung Galaxy S 4] joshm.1219:
I know i did it correctly lol and specifically the watch on app doesn't have an option to get to the menu within the app. I had to install pie to get to to the menu.
[Verizon Samsung Galaxy S 4] Chuckleb0ne:
Yea I was unsure it would boot up after the error but It booted up fine. I think the error was for the way there aroma installer tried to tell TWRP to reboot but it didn't like the installer. That's just my thought.
[Verizon Samsung Galaxy S 4] jpcalhoun:
Sorry to hear that. I'm really looking forward to flashing this ROM when they get the Verizon Dev included in the supported devices.
[Verizon Samsung Galaxy S 4] markwebb:
Yeah, was bummed but am posting the log for the devs to look at per OP instructions. I also tried again this AM thiking it might have been a bad DL but alas it wasn't.
[Verizon Samsung Galaxy S 4] jpcalhoun:
For all the Dev owners following this thread, thanks for taking the time and trouble for working with the developers in getting this ROM supported.
[Verizon Samsung Galaxy S 4] markwebb:
Ok this is strange: log results says successful but Recovery aborted install saying it found 6 args and not 3.
[Verizon Samsung Galaxy S 4] Alxoom33:
Did you try to reboot system. I got a fail in TWRP and Oct reebooted just fine. :cool::cool:
[Verizon Samsung Galaxy S 4] markwebb:
No let me try again. Be back in a few.
[Verizon Samsung Galaxy S 4] Alxoom33:
Weird, but the flash was successful. Would be curious what Dubbsy and the other Oct developers have to say. Btw, the new Oct 4.3.1 is running great!
[Verizon Samsung Galaxy S 4] hlxanthus:
PM sent
[Verizon Samsung Galaxy S 4] mikepers:
ME7 check does seem to work

Didn't see anyone else confirm it in the thread so just wanted to mention that I tried to flash last nights build on ME7 (using safestrap). The check worked and it did not flash.
[Verizon Samsung Galaxy S 4] markwebb:
OK it worked by just rebooting and ignoring the failure. Working well so far. LTE signal is stronger than the other431 builds. WiFi worked immediately. Great job and I anticipate greater improvements with each iteration!
[Verizon Samsung Galaxy S 4] mbwsutherland:
Great work first gpe experience. Love this. Just trying to feel out this exposed framework **** lol. Got gravity box and xblast. Any other module suggestions. For some odd reason I can't make nav bar transparent. I believe it's because I choose enable navbar in aroma and it's blocking it from changing for some reason.

Thanks for this is an experience for sure;)