yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] GreatDayChap:
That's how it is supposed to work. Dubbsy stated previously that it is intentionally set up to not flash on ME7.
[Verizon Samsung Galaxy S 4] Alxoom33:
Although I am on MDK I have the me7 radio modem that I downloaded. Could that be the reason it said failed after flashing in TWRP even though Oct booted up OK?
[Verizon Samsung Galaxy S 4] GreatDayChap:
The latest build seems to be saying it failed for everyone in TWRP but it boots up just fine.
[Verizon Samsung Galaxy S 4] hlxanthus:
Excellent!! Thanks for confirming that for us :cyclops:

---------- Post added at 03:04 PM ---------- Previous post was at 03:02 PM ----------

No, it does not check the radios. It check device and bootloader. We are working on an another build to replace yesterdays quasi failure.
[Verizon Samsung Galaxy S 4] MichaelMcEntire:
Everything is working great for me, besides a lot of random reboots. I've tried stock kernel and a few others with no improvement. I've also tried a fresh install and a dirty flash with the same results. Bad download?
[Verizon Samsung Galaxy S 4] markwebb:
Worked beautifully"
[Verizon Samsung Galaxy S 4] Dubbsy:
new build up.
[Verizon Samsung Galaxy S 4] Chuckleb0ne:
Another?
[Verizon Samsung Galaxy S 4] hlxanthus:
This build is largely to address the issues people were having. The core rom is exactly the same. If you are happy with what you have, no reason to move to the next one. The biggest difference is more flexability and stability with using our installer under the Apps and Kernels aroma install path. You can now successfully use it to switch to one of our other kernels, or enable or disable the navbar for example. The exception to this is it will NOT delete anything unless the installer specifically states that it will, so for instance installing apex launcher will NOT delete nova or stock launcher.

That and over all greater stability within the aroma installer.
[Verizon Samsung Galaxy S 4] fafaffy:
Which kernel included in the aroma is best for overall battery life?

I'm not familiar at all with the kernel scene.
[Verizon Samsung Galaxy S 4] Grommish:
Asking about battery life is like asking which car is best for you. Battery life, for the most part, will depend on how you use your device. We typically won't include something for release that isn't something we'd run ourselves.

The screenshot here is from the stock Sprint kernel.
[Verizon Samsung Galaxy S 4] Dubbsy:
Just run stock until you've read about the pros and cons of each one's settings. Or do trial and error

sent from my Verizon Galaxy sIV
[Verizon Samsung Galaxy S 4] MichaelMcEntire:
Reinstalled with newest build, perfection.
[Verizon Samsung Galaxy S 4] Chuckleb0ne:
Where do I download or flash xposed?
[Verizon Samsung Galaxy S 4] Grommish:
Asking about battery life is like asking which car is best for you. Battery life, for the most part, will depend on how you use your device. We typically won't include something for release that isn't something we'd run ourselves.

The screenshot here is from the stock Sprint kernel.

View attachment 2321307
[Verizon Samsung Galaxy S 4] Treken:
Theme engine has been added and will be coming soon. ;)
[Verizon Samsung Galaxy S 4] daniel4653:
Google will tell you.
[Verizon Samsung Galaxy S 4] Grommish:
Not only that, but it is clearly an option to install when installing the ROM.
[Verizon Samsung Galaxy S 4] daniel4653:
I thought so too. But its been awhile since I ran the ROM.
[Verizon Samsung Galaxy S 4] markwebb:
OK guys. I have been on this ROM for approximately 16 hours and intentionally depleted the battery down to zero last night watching vids, surfing, etc: definitely a daily driver! However, am observing this am after having phone fully charged overnight, it seems a bit laggy and slightly slower. Just an observation. Of course it could be what I have installed, etc. I did the custom install with stock kernel.

But I love it.
[Verizon Samsung Galaxy S 4] brizey:
I'm running the original release pretty much as vanilla as possible except for kernel and xposed. Any reason to update? I am having no issues, but you never know if there are some less obvious tweaks, etc. (My favorite aspect of the aroma installer is all the stuff I can leave out!)
[Verizon Samsung Galaxy S 4] alleyboy727:
First off I love this rom great work devs the only issue I am having is the call s.o.d is there a fix or work around for it
[Verizon Samsung Galaxy S 4] hlxanthus:
No idea what you are referring to. I have had no issues with calls. Grab a log for us please.

---------- Post added at 11:36 AM ---------- Previous post was at 11:34 AM ----------

Only if you want to. Not a lot different in the core ROM except the advanced power menu, which you can get with exposed and gravity box
[Verizon Samsung Galaxy S 4] thadialeckt:
I think he is referring to making back to back calls and the call ends right away
[Verizon Samsung Galaxy S 4] lortay78:
Works great on Developer Edition phone. Thank you!
[Verizon Samsung Galaxy S 4] rockingrubberducky:
im not rooted yet and im on me7.

can i flash this rom or any 4.3 AOSP roms?

or do i have to settle for AOSP 4.2?
[Verizon Samsung Galaxy S 4] markwebb:
Absolutely! Still putting it through its paces. Haven't tried Bluetooth yet.
[Verizon Samsung Galaxy S 4] Chuckleb0ne:
Camera force closes when you try to select the picture size. Also the pictures seem a little fuzzy.
[Verizon Samsung Galaxy S 4] markwebb:
No FC's here and pics look fine at least to me.

Just tried it again and yes force closes on pic size.... Sorry good catch!
[Verizon Samsung Galaxy S 4] mchief298:
I found a different apk and installed that instead, works fine.
[Verizon Samsung Galaxy S 4] markwebb:
Can you share which one?
[Verizon Samsung Galaxy S 4] mchief298:
http://xdaforums.com/showthread.php?t=2341554

I used this one... Don't know about updates but as is it works fine.
[Verizon Samsung Galaxy S 4] schwartz.matthew.e:
This is awesome! Thanks for making this!
[Verizon Samsung Galaxy S 4] Cruiserdude:
Thank you, thank you, thank you!! That one works great, and fixes Photosphere finally, really been missing that! For those who have odexed their phones again, you'll need to delete the old Gallery2.apk file after flashing, then go back to recovery and fix permissions. But after that it works great!
[Verizon Samsung Galaxy S 4] Tsukasa Buddha:
So when is 4.4 coming out?

:p
[Verizon Samsung Galaxy S 4] Treken:
2 weeks :p

---------- Post added at 07:15 AM ---------- Previous post was at 07:09 AM ----------

Look at the OP under "Features" section line #4.

All others: Please read OP fully as it may answer your questions, thanks! ;)

Edit: OP has been updated. Please take the time to read it. :)
[Verizon Samsung Galaxy S 4] Dubbsy:
Not as soon as you may read from treken. Basically we have a lot of "neat things" planned and none will be released until the "neat" part is finished...Again, another "this rom only feature" that we brained up ourselves. Only posting because I just don't want to see 5000 posts "where's theme engine", just like I'd rather not see posts "Game work yet" "How bout now" "Cant wait for game" ....trust us when it's fixed, we will know and it will be a big highlight in the Changelog.

Every update we release, since this project is so new, there are a lot of things that change. Bug fixes, additional "neccesary features", more file support.

But if you are happy with what you got, run it.

Just don't report errors or logs for old releases...the log reader-bug tracker(me) won't open them.
[Verizon Samsung Galaxy S 4] Diversion:
Resolved, make sure you're on a newer Loki'd Recovery or just use TWRP Loki'd

Latest build's boot animation doesn't work but otherwise rom seems fine.. nope no signal either.

Edit: No cell service on stock kernel and Verizon this is 10-12RC2, upon reboot, the rom seems to reinstall itself everytime or hang.. Not sure since there's no boot anim. Still no cell service after rebooting. I'll download Oct 11 and see what happens.

Edit2: Same exact problems on the 10-11 build.. weird.

Edit3: I do have a Loki'd recovery but Baseband says "Unknown" . .I can flash other TW roms like JellyBeans without any problems. Maybe this rom isn't compatible with PhilZ Touch 5 recovery?
[Verizon Samsung Galaxy S 4] hlxanthus:
We only ever test with twrp.

Sent from my Galaxy S4
[Verizon Samsung Galaxy S 4] Diversion:
I upgraded to a newer Loki'd recovery and it fixed everything :P Thanks.
[Verizon Samsung Galaxy S 4] asaberan:
I can't receive MMS messages and my 3G isn't working in the Play Store, Google Now, etc. I had the same issues with the Google Edition ported ROM.
[Verizon Samsung Galaxy S 4] jpcalhoun:
No Luck

Tried three times to get a successful flash with no luck. The ROM would boot, although very slow, but no data. WiFi worked great as did everything else, I think. I have a Verizon Dev edition running MKD, ktoonsez kernel and PHilZ Touch 5 recovery.
[Verizon Samsung Galaxy S 4] Dubbsy:
The nicest way I can say it is...Currently I blame your entire issue on CWM and KT(even though I like KT's kernel)

A. KToonsez kernel - Not supported by this project at this time.

B. CWM based recovery - Will

never

be supported by this project.

Ktoonsez kernel( and all others)may be added at some point once all devices are supported.

CWM and it's derivatives will never be, unless they drastically change the layout to make it more newbie proof.

Try it with things we support, and if you still get issues, log it, post it, and we'll do what we can.
[Verizon Samsung Galaxy S 4] markwebb:
I have a dev edition as well: the kernel might be your issue. I always use stock and I believe this ROM only should use stock...

EDIT::eek:eek:PS! See Dubbsy's response as validation. Cross posted :)
[Verizon Samsung Galaxy S 4] jpcalhoun:
Thanks for your suggestions. I didn't understand that you don't support CWM/deliverables. I thought with an unlocked bootloader that it wouldn't make a difference...guess I was wrong.

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

Yeah, I selected "stock kernel" in Auroma, but I guess that means if the stock kernel is already present use it, it won't flash a stock kernel if you have something different on the phone.
[Verizon Samsung Galaxy S 4] Alxoom33:
Surprised, been running Ktoonsz kernel since inception with no problemz ;)

Didn't know not supported, is there an issue with compatibility?:confused:
[Verizon Samsung Galaxy S 4] Dubbsy:
Sprint is unlocked, Verizon side steps the lock but doesn't remove it.

Since you "asked"... I dislike, and never recommend to anyone, CWM or any of the derivatives. Why? I'm glad you asked. I've had no less than10 people try to flash a rom using online instructions with CWM. 3 gave up and stayed fully stock. The others I either had to come over and do it for them or was able to talk through doing it on the phone. My first step to every one of these people was Download TWRP. Hell, even [MENTION=3236955]Treken[/MENTION] was running a CWM until he was having a issue I couldn't duplicate, I had him run TWRP and it fixed itself.

I'm not going to say that CWM can't work where TWRP can. I strongly believe many errors that are recovery related are user errors at their root. That being said, why the hell would anyone suggest the less tech-newb friendly recovery to ANYONE?

Preparing to install a new rom 101:

Make a freaking backup

Wipe the device, system, data(not media/internal sd), wipe cache, wipe dalvik, wipe preload(all in one menu for TWRP)

Go to install.

Find your zip files you want to install and follow the prompts until it says reboot.

Don't reboot.

If using TWRP, simple hit the wipe dalvik/cache button, then hit back, and hit reboot....done.(All same screen)

If using CWM, back out to main menu, go to wipe cache, tell it you really want to wipe cache, go back to home, go to advanced, wipe dalvik, approve your choice to wipe dalvik, go to main menu, reboot.(Not all the same screen... >.>)

Now, if walking a friend who knows nothing about any of it and wants to learn...don't you think he'll get more frustrated with the convoluted instructions and steps of CWM?

I won't pretend I've actually looked into the script aspects in the backend of the recoveries. I'd rank them at least equal until I compared them. I do know the wipe procedure on the 2.6+ TWRP is superior to 2.5. But I haven't cared enough to dig into the CWM wipe functions to see what all they wipe.

As an added newb-proofing me and [MENTION=4129069]hlxanthus[/MENTION] have been wiping dalvik and cache for the user within our installer script after the kernel is installed since we joined up on 4.2.2. In the aroma we include an optional script that will wipe data without touching media. And we format system at the beginning of the rom install. We try to make it as friendly as possible because I know how frustrating it can be sometimes.

If it's a prettiness thing that makes you prefer CWM, I'd suggest looking at some TWRP themes. I did one back in my 4.2.2 thread linked in my sig. And there are 5 more done by the guy who I based mine off of. For the future once the rom settles out a bit I had planned on building a custom recovery altogether based off of the latest at the time TWRP. Designed with the nightly user in mind. As a person who flashes roms sometimes 5 times in a single day...I know what needs changed desperate. More so in CWM than TWRP, but TWRP could use some tweaks too.
[Verizon Samsung Galaxy S 4] Dubbsy:
No issue, i've ran it also. Just because we don't officially support it, doesn't mean it won't work. But us not supporting it means, if stuff starts messing up, it's on you.

We are working on a 9 device supported installer, 3 kernels per device, and 2 full different UIs for each device. We aren't going to support everything...we've got enough to support as it is. :good:

Any AOSP 4.3.x kernel SHOULD work with minimal to no problems. But if it doesn't and it's not one of our 3...we won't troubleshoot.
[Verizon Samsung Galaxy S 4] jpcalhoun:
Dubbsy, first I'd like to make two things clear: 1) I appreciate and respect the work you and your team has put into, and continues to put into, this ROM and 2) I appreciate your response and time you've taken to help all of us. I hope there is nothing I've posted here that infers that I am criticizing your work, because I'm not!

I have used TWRP for a couple of years, and loved it. However, when I first got my dev ed S4 a couple of weeks ago I asked, in a different forum, of the dev owners what recovery they recommended. Of the 7 or 8 owners who responded at least 6 of them recommended PhilZ...so I went with that. I also asked about kernel they recommended, and again the recommendations were almost unanimously ktoonsez, so I went with that. I agree, PhilZ is much more "complicated" to use than TWRP, but I've learned to be careful, read before selecting and have taken the time to "find my way around" the recovery. That's not to say I'm happy with it. I miss the simplicity of TWRP. And looks, particularly in a recovery, don't mean crap to me, it just needs to work right every time. I'll most likely flash a different recovery and kernel so I can successfully flash your ROM. Thanks for you help.
[Verizon Samsung Galaxy S 4] Dubbsy:
I didn't take it as any criticism, just giving long drawn out answers to remove any context follow up questions that I don't like to answer lol. If anything I am sick of seeing newb-instructional-walk-throughs using the most complicated recovery for nearly every device. And like I said, I'm fairly certain all recoveries do the same thing( assuming the recovery's scripts aren't messed up.) A format command is the same so long as it actually executes. Same with delete and rm -rf. That's why I think any recovery issue(unless it is really just THAT BAD) is just a simple user error, missing a step, or selecting the wrong thing. But that's why TWRP is a better option, less chance of messing up with nicely organized buttons vs totally unrelated submenus. For example there is nothing advanced about wiping dalvik....:laugh:
[Verizon Samsung Galaxy S 4] markwebb:
For what it's worth I have been using philz recovery since day one with the most recent update and have never had one rom to fail either upon install, backup or restore so take that with a grain of salt though it is not officially sanctioned. ;)
[Verizon Samsung Galaxy S 4] Dubbsy:
Yep. Like I said I really think recovery related errors are just user error. Sounds mean... But it's how it is.

You really just can't F up a script without it being blatantly obvious. Especially the scripts ran to do the simple commands that recovery does.

I've been looking into the back end of recoveries more lately because we are working it into our project goals.

sent from my Verizon Galaxy sIV
[Verizon Samsung Galaxy S 4] Bait-Fish:
Thanks for the great ROM. Being new to Samsung, I stayed STOCK for months and got a good feel for TW :eek:

This afternoon I took the plunge. Very nice. Just getting settled in. Looking forward to OctOS' continued development.

BIG thanks!
[Verizon Samsung Galaxy S 4] rosser725:
Love the ROM but I keep getting dialer force closes when I go to use the phone. Any known fixes?
[Verizon Samsung Galaxy S 4] Cruiserdude:
No issues here, but try clearing that app's data, and fixing permissions again.

If that still doesn't work, you can just go in /system/app and replace it with any 4.3 AOSP Dialer.apk. I'd copy mine for you, but I'm odexed. Anyone else's with this rom should work, or you can pull it out of the zip by looking in the same place you'd look on your phone.
[Verizon Samsung Galaxy S 4] hlxanthus:
This is a known aosp bug that we are working on. In every case we have seen it is fixed by a reboot. It begins when you start a call and cancel before it connects. All further calls then fail until a reboot.

Sent from my Galaxy S4
[Verizon Samsung Galaxy S 4] thadialeckt:
Will xposed framework still work. If you reodex the phone.
[Verizon Samsung Galaxy S 4] Dubbsy:
Yes.

If people desire I can put in an odex script by default in /bin and the user would then just have to open a command line and type odex and follow prompts. Me and hlx had played with this idea on 4.2.2

sent from my Verizon Galaxy sIV
[Verizon Samsung Galaxy S 4] thadialeckt:
I would like this
[Verizon Samsung Galaxy S 4] Dubbsy:
Alright. I'll make it happen once we get the settings locked down. It needs done before we can release again. Even though we have working builds lol

sent from my Verizon Galaxy sIV
[Verizon Samsung Galaxy S 4] joshm.1219:
It hasn't been that bad for me only once or twice a day I have to reboot.
[Verizon Samsung Galaxy S 4] Treken:
Please stay on topic with the OP
[Verizon Samsung Galaxy S 4] lukelee83:
I'm not sure if it means anything but figured I would throw this out just in case it helps with something. I'm on sprint, and when I first flashed this ROM, I would get low internal storage warning thing for every app I updated. Yet I could install new apps just fine. I rebooted and it no longer happens. I can update apps fine without a warning.
[Verizon Samsung Galaxy S 4] schwartz.matthew.e:
I'm using cwm but switched from chaos kernel to elite. Have had zero issues. Everything works perfectly. Thanks for your hard work on this ROM devs!
[Verizon Samsung Galaxy S 4] Alxoom33:
Sorry Treken, but I thought that the warning was important for all VZW S4 owners, many of whom, like me, use Oct as their DD.:cool:
[Verizon Samsung Galaxy S 4] Grommish:
A OTA update from Verizon has no point here. You have to violate you're ToS with Verizon to even load OctOS.. Besides, will an OTA even download on AOSP?
[Verizon Samsung Galaxy S 4] Alxoom33:
Of course not! But it will on stock! That's not the point, which was to warn vzw Oct users who may also flash to stock on occasion, say when they hear there's an OTA.

:cool:
[Verizon Samsung Galaxy S 4] Dubbsy:
Any idiot that takes an ota after taking me7 deserves to never gain root again. The first thing you learn in this world is not to trust your carrier. The second is only take the update if and when it's been proven safe and has been reposted by a reputable member that isn't Verizon. BASICALLY... Don't take the F'ing OTA.

NON-ISSUE

The storage reminder feature is new to android in general as of 4.3_r3. It's not a bug and it's not a warning. It's a simple " hey Buddy you have this much room left"

It can probably be removed... But I'm not doing it.... it's actually a nice feature on a device with limited storage.

sent from my Verizon Galaxy sIV
[Verizon Samsung Galaxy S 4] Dubbsy:
If someone is flashing to pure stock and they take the OTAs... They deserve it and I have no sympathy.

sent from my Verizon Galaxy sIV
[Verizon Samsung Galaxy S 4] Alxoom33:
There's a whole new thread of such sad souls on XDA.:(
[Verizon Samsung Galaxy S 4] Treken:
We appreciate your support. But please stay on topic and remember that you don't have to have the last word. ;)
[Verizon Samsung Galaxy S 4] lukelee83:
The thing about the storage thing is that it said I had 1.5 mb of internal storage when I actually had over 3gb. Then I downloaded and installed a 16 mb app just to test it and it installed fine. Also it doesnt happen any more. It only happens once right after clean install
[Verizon Samsung Galaxy S 4] hlxanthus:
It is related to the dalvik cache which is within data. When you download a lot of apps or update via the market it stores them there before installing then so it can kind of be misleading. Yes that space is taken but is temporary really.

Sent from my Galaxy S4
[Verizon Samsung Galaxy S 4] Dubbsy:
The newbs that take that OTA are the type that A. aren't going to post bugs correctly anyway B. are going to have mysterious issues that they blame on the rom after they install stuff known to EVERYBODY to cause wakelocks, like antivirus crap or battery savers and finally C. will report bugs on dirty flashes when we explicitly say not to.... We are better off without them.

See what I did there [MENTION=3236955]Treken[/MENTION]? I got the last word. :p
[Verizon Samsung Galaxy S 4] joshm.1219:
Besides the occasional dialer hiccup this has been flawless, thank you so much.
[Verizon Samsung Galaxy S 4] GramKrackr:
Does this ROM have support for the Galaxy Gear on the S4? Looking for a 4.3 ROM that has support.
[Verizon Samsung Galaxy S 4] ckelly33:
Op says camera choice via aroma. Does this have a tw camera option? If so, fully functional?
[Verizon Samsung Galaxy S 4] Alxoom33:
Yeah Dubbsy! You did get the last word!

Oops, well, now that I'm here, I found that the MI1 flashable modem has been extracted and a link posted in the MI1 thread to the flashable zip file. Have you looked at it? Would you recommend flashing the MI1 radio/modem?

;):D
[Verizon Samsung Galaxy S 4] Dubbsy:
I won't be flashing the modern until it's been proven to be an actual upgrade. The me7 modem was worse than mdk. Spottier reception for me. And I honestly think the people using it who think its better are toking on the placebo pipe....

sent from my Verizon Galaxy sIV
[Verizon Samsung Galaxy S 4] markwebb:
Interesting. :) I work in an area/building which has slim to zero chances of connecting via LTE. I did find the ME 7 does allow me to connect "more often" , albeit on a very weak signal and typically at 1x-3g for a short period of time or intermittently vs. NO connection on an MDK modem. So, mileage will vary as they say..and trust me, I am always testing these things out during the day and swap the modem whenever I change ROM's to see which work better. :) So, definitely not "placebo pipe" in my case though I am sure it may be with others.
[Verizon Samsung Galaxy S 4] brizey:
For me I just can't really tell the difference. So I left it on ME7 because the "number" is bigger, lol.