yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] Cruiserdude:
I tried ME7 modem and went back to MDK, as I had the same results as Dubbsy. Though I'm highly suspect of any changes related to the modem on most version upgrades. Do they seriously make significant RIL changes with each update, or push newer PRLs only to those with the latest modem? Seems like they could change nothing but the signature and build stamp and people would still debate back and forth as to whether it improves or hurts signal.

But it isn't my area of expertise AT ALL, and I'm sure they DO make changes from time to time. I'm just saying I doubt it's every build. That being said, they did at one time say the jfltevzw would support AWS-LTE after a future software update. They just turned that on the same day the update was pushed, so there's a good chance that this modem/firmware combo may indeed have a MAJOR impact on data speeds, depending on where you live. The only question is, Are there separate kernel modules required for AWS to work, or would we be able to get it working with just the modem and firmware.
[Verizon Samsung Galaxy S 4] markwebb:
The new MI1 modem is slow as hell for me. Go figure. I even went back to rooted stock... Heavens!!!!... And it was slow.
[Verizon Samsung Galaxy S 4] Dubbsy:
As a heads up nothing Verizon will add to the modem will be substantial until they unleash their new LTE band. THAT modem will be worth the upgrade.

Besides that mdk has had Zero Major Flaws. Upgrading Now just causes variations in builds and makes anything RIL related impossible to diagnose for any Dev at the ROM level to deal with. I know it's a shocker.... Verizon sticking it to the non paid developers. Lol.

I will personally be on mdk until the new LTE is made available regardless of how many modems they push as updates.... The fallout from those updates is simply not worth it. Take it with a grain of salt of course. I don't blame anyone for using the latest modem. Any one who flashes the full ota is a total tool though. :)

The ota idiots are about the most annoying thing Dev wise. Sure we have to track down errors and why things are acting up. But hearing the same old sob story from someone who took the ota and can no longer root or flash is 10x more annoying than bug tracking. Those people clearly don't realise that the OTA release is at least 4 android revisions behind anything my fingers are touching.

My advice to those people... Stick to TW

sent from my Verizon Galaxy sIV
[Verizon Samsung Galaxy S 4] snael:
Man this is definitely bare bones AOSP at the moment but it is so smooth I love it. Very nicely done. If I can get past the camera compared to TW I will certainly be using this as my daily.
[Verizon Samsung Galaxy S 4] mkglitzman:
Does this rom work with safestrap?
[Verizon Samsung Galaxy S 4] hlxanthus:
No.

Sent from my Galaxy S4
[Verizon Samsung Galaxy S 4] Dubbsy:
Uploading

T-Mobile Theme Engine is included. And the beginning of our alternate UI has been introduced. The rom will remain AOSP styled, unless you enable Oct Settings like you would Dev Settings. But instead of 7 taps to build number it is 8. And if you don't understand why that is, you really shouldn't ask... I'm not THAT nice of a guy.

Enjoy once it's done uploading.
[Verizon Samsung Galaxy S 4] Dubbsy:
So apparently, when you upload and walk some filthy gremlin kills the upload.

So uploading again.
[Verizon Samsung Galaxy S 4] :
Just to verify, this rom has no CM or PA settings included? I am on the PAC rom now and I like that its all in one because it offers to much customization. Does this rom offer similar customization? I want to try somthign other than PAC because current builds of PAC do not support custom Kernels.
[Verizon Samsung Galaxy S 4] Dubbsy:
Did you read the OP and not get that it's real aosp? real vanilla aosp? We are adding some hidden options but we will not be adding even close to as many options as pac or any of them.

I'd strongly suggest reading the OP again.
[Verizon Samsung Galaxy S 4] Dubbsy:
New ROM is uploaded.

Time to get back to adding shhhtuff
[Verizon Samsung Galaxy S 4] :
Yes I read the OP but the last 2 lines were a bit misleading so I figured it wouldn't hurt to ask.

"7. You want 100% untouched/unmodified AOSP. This isn't the ROM for you. And P.S. the source is openly available go make it yourself.

8. You want features. They are coming. No ETAs and no updates unless one of us is excited about getting something working."

Number 7 makes it seem as if its not vanilla aosp and with all the features you guys listed including "oct settings" I wasn't sure what type of customization was included. I really dig the aroma installer though, it makes it very simple to use. I will help my girlfriend install on her phone. I'm too OCD about my customizing.
[Verizon Samsung Galaxy S 4] hlxanthus:
Our goal is to remain very close to a true aosp experience, while offering a method for those few options we feel mesh well with that experience.

It is largely the OctOS branding the OP refers to as not vanilla aosp.
[Verizon Samsung Galaxy S 4] markwebb:
Some issues on new upload RC3 with Dev Edition:

1. I chose custom install and it hanged on the Samsung Unlock Screen upon reboot

2. I chose Google Default install and it loaded up

3. Reboots take VERY long on the Google Default install and as I type this, it is still rebooting. 1-2 minutes

4. No LTE data :(

I always fully wipe.

Thanks, nevertheless! Love the work.
[Verizon Samsung Galaxy S 4] cjkacz:
Bump :)
[Verizon Samsung Galaxy S 4] mkglitzman:
It has to do with the 4.2 kernel modules not being supported by 4.3 I'm guessing.

Thanks for the heads up. [MENTION=2519996]teamo[/MENTION]ctos This project looks like it has a lot of promise. Loved GE. Keep up the good work!
[Verizon Samsung Galaxy S 4] Cruiserdude:
Does the recent release of 4.3 TW (and subsequent source) for the GT-i9505 help out at all, or does it not contain anything that you didn't already have from GPe source?
[Verizon Samsung Galaxy S 4] Dubbsy:
We'll pull from it but we aren't going to rebase from it. This is still our ROM and nor pure GPE.

we have a very different idea of what we want. Stay true to a lot of aosp. Hide a butt-ton of options that handle all the extras. And patch in as much functionality from tw as possible.

sent from my Verizon Galaxy sIV
[Verizon Samsung Galaxy S 4] Dubbsy:
So no comments on release? We are working on adding more and cleaning up more now.

sent from my Verizon Galaxy sIV
[Verizon Samsung Galaxy S 4] Grommish:
What recovery are you using?

First reboot after install will take longer than normal. We force remove dalvik and cache, so it has to rebuild them.

I'm on Sprint with limited LTE around me, but I was able to grab LTE. Log the attempt to toggle 4g and send it in?
[Verizon Samsung Galaxy S 4] Sidewind75:
Great rom. Running awesome only problem i have is that i use my phone at work to stream pandora and my work place is very loud. The audio out of the headphone jack is so low even the V4 audio does not boost it up enough.I use A 150 watt stereo to amplify the sound and it is still very low. Is there anyway to increase it more..like what Hyperdrive does with the audio hack?.also is there any other fix for google services besides turning location services off? Every rom I try it kills the battery so damn quick.
[Verizon Samsung Galaxy S 4] lukelee83:
Well... Working very well so far. Theme engine works. Only problem is that some google services such as play store doesn't work on eHRPD for me. But that seems to plague all AOSP ROMs on sprint gs4 so that was kinda expected.
[Verizon Samsung Galaxy S 4] Grommish:
I'm on Sprint and have no issue with any of the Google services, including Play Store, on 3G eHRPD. What kind of issues are you having? Just connection, latency, etc?
[Verizon Samsung Galaxy S 4] thadialeckt:
I don't see theme engine

Nevermind
[Verizon Samsung Galaxy S 4] lukelee83:
It seems that number of us are having problems where the play store would always time out on eHRPD. On lte or evdo it would work fine. Also among those of us having the play store issue, there are some of us for whom google search wouldn't reliably work.

EDIT: This is for AOSP in general. For tw ROMs everything works fine. Unfortunately I prefer AOSP by far
[Verizon Samsung Galaxy S 4] Grommish:
I've not used other AOSP ROMs. TW stock with kernel prior, and CM10.1 before I picked up the S4 (OG Epic). Right now I'm the only one with Sprint, so I'm testing for it as it gets reported. Also means I can only attest to my device, so logs of the event, when it's happening, are crucial. If I can't get it to happen, and no logs are sent, we have to assume it's a user error. So, make it happen and log it out. [MENTION=3236955]Treken[/MENTION] and [MENTION=5168775]Dubbsy[/MENTION] are pretty good at fixing issues. If it's a true AOSP bug, we can keep an eye on the upstream for a fix and update the OP.
[Verizon Samsung Galaxy S 4] lukelee83:
Just to let you know, I already updated profile so that's not it. Also evidently not everyone gets it but I'm definitely not the only person.

Anyhow, just to make sure I understand correctly, to use syslog, I first replicate the problem, go into the app then tap on "take log" button. Is this correct?
[Verizon Samsung Galaxy S 4] Grommish:
Correct. Thank you!
[Verizon Samsung Galaxy S 4] lukelee83:
Here is my attempt at the log

https://dl.dropboxusercontent.com/u/22294515/2013-10-19_22.09.zip

Thanks you and hope it helps.
[Verizon Samsung Galaxy S 4] Tsukasa Buddha:
Just posting to say everything is running just fine over here :good: . The theming is a nice nice option, but I prefer the standard AOSP for now.
[Verizon Samsung Galaxy S 4] Dubbsy:
You didn't activate the alternate options. Go get your developer settings...

sent from my Verizon Galaxy sIV
[Verizon Samsung Galaxy S 4] Dubbsy:
I too am running stock holo anyway. But with added tiles and status bar layout. But I stay on themes for maybe a day anyway.

sent from my Verizon Galaxy sIV
[Verizon Samsung Galaxy S 4] markwebb:
I had already uninstalled by the time you had responded because no data is the main issue and I can't live w/o that. LOL

Yes, I know about first reboots.

What I was trying to say and perhaps it wasn't worded correctly on my part any subsequent reboots, the phone would reboot but any kind of activity/interfacing would take forever to engage For example, Android upgrading message would take at least 2+ minutes though there wasn't the typical listing of apps upgrading, logging in with user name and profile where it says "just a sec" took forever, and any at randoom reboot would take forever for the home page to let you perform any activity, etc. It did reboot instantly but any kind of interfacing you had to wait a very long time.

Otherwise, it runs fast and smooth.

I can re-install again today and post a log: how do I do that again?

Just an FYI: this zip from last week https://www.copy.com/s/TipmU/OctOS_Aroma_10.12.RC2.zip runs beautifully. Perhaps you can compare it to the currently posted zip for the data/lte settings?

Good work nonetheless and I am VERY excited about this project!
[Verizon Samsung Galaxy S 4] red3razor:
I tried xposed+xblast tools module = statusbar mods and such, but didn't see more tiles option. Is this on a private build or xposed module? BTW excellent work on this :) running smooth, great battery, no issues or FC's here. In aroma I chose boot animation- stock with OctOS twist, well done, very clean. Theme engine works nicely. Thanks to the whole team!
[Verizon Samsung Galaxy S 4] hlxanthus:
GravityBox has the quick tiles options

Sent from my Galaxy S4
[Verizon Samsung Galaxy S 4] Grommish:
I saw that happen under an old kernel early on. Once you get it reinstalled, post/pm me the kernel info? Did you install stock or one of the others?
[Verizon Samsung Galaxy S 4] markwebb:
Yes, I always install the stock kernel. Let me try a bit later and I will report back. How do i perform that kernel info again? I know i have it somewhere.

EDIT: I now see during install when I can save the log. I just did it. On first boot up which as we know takes longer. I did choose custom install but stock kernel.

Log attached!
[Verizon Samsung Galaxy S 4] JamesPumaEnjoi:
How do you do it Dubbsy? Every time its just magnificent
[Verizon Samsung Galaxy S 4] :
I am on vzw I installed using cwm touch recovery v6.0.4.4. and have no data. I first came from another rom and it worked great installed from twrp recovery. then It got stuck on s4 logo after rebooting. I odin back to complete stock re-rooted and I decided to use cwm recovery thinking twrp recovery was giving me the issues. This is the first rom I installed after coming from stock but now im not getting data at all? I reinstalled it again using custom - (stock kernel and still no data)
[Verizon Samsung Galaxy S 4] Grommish:
Can you screen shot and post your About screen?
[Verizon Samsung Galaxy S 4] :
here is mine
[Verizon Samsung Galaxy S 4] :
baseband version is unkown? should I try a new kernel?

EDIT: Tried with elite kernel and is working great now
[Verizon Samsung Galaxy S 4] hlxanthus:
We will take a look

Sent from my Galaxy S4

---------- Post added at 07:21 PM ---------- Previous post was at 07:18 PM ----------

We only verify thru twrp and version 2.5.0.2 to be exact. Now I understand twrp failed to boot for you but I am curious what version it was. We have had issues with cwm based recoveries which is why don't use them anymore and don't recommend or support them.

Also what wipes did you all do? Did you come from aosp previously or aosp?
[Verizon Samsung Galaxy S 4] :
I always do a full wipe factory/data reset, delvik, cache and format system and data.

I used the latest twrp from goo manager. do not know what version it was but was possibly a newer one than the supported one.

Looks like I will be set for now, using the elite kernel, but thanks for the clarification.

and also thanks for all the hard work you all put into this rom. :good:
[Verizon Samsung Galaxy S 4] hlxanthus:
The most recent twrp would be 2.6.3.0. Now, are you saying elite kernel fixed the issue?
[Verizon Samsung Galaxy S 4] :
Yes it did.

I always choose stock (tried stock several times with no luck)

finally I tried the elite kernel and my data is now working on this rom.
[Verizon Samsung Galaxy S 4] markwebb:
Interesting. So I wonder what changed in this latest update from the prior update regarding the stock kernel?
[Verizon Samsung Galaxy S 4] mchief298:
Is yours a loki'd recovery?
[Verizon Samsung Galaxy S 4] Dubbsy:
Not to sound mushy or cliché.... But

By having a great group of team members who all either 100% agree or can be convinced of the general idea and goals of this ROM.

We've changed things throughout but it's always been unanimous decision of all of us.

Just because I posted the ROM doesn't mean it's all me. In fact [MENTION=3236955]Treken[/MENTION] and I decided to start this equally. I brought in [MENTION=4129069]hlxanthus[/MENTION] because he was a part of my GE project. [MENTION=1975745]Grommish[/MENTION] is an old friend with wicked server talent and a strong unfastening of Linux. Agat was brought in to build us a custom octos kernel by grom. [MENTION=333331]cjk[/MENTION]awz has been then best tester a person can ask for with practical ideas and suggestions and he's learning the ropes of development also. [MENTION=2967322]buckmarble[/MENTION] while not a member of the team (he's with team elite)might as well be because he's helped us a lot and gave us permission to use his kernel in our builds. He even built the sprint version because we asked.

This wouldn't happen if it was just me. I'm a make something broke work kind of guy... Not a build from nothing kind of guy. The whole project has been the biggest learning experience I've ever had. Knowing how to read code is nothing....knowing how to diagnose build errors was tough.

But really this isn't me... It's Team-OctOS's doing. Some days I'll push 20 changes. Some days I won't even login to git.... The project moves forward regardless because we all know what we are doing next. :good:

sent from my Verizon Galaxy sIV
[Verizon Samsung Galaxy S 4] Treken:
A screenshot of the kernel version would be helpful.
[Verizon Samsung Galaxy S 4] dogg94:
Making a Nandroid and downloading excited for new flavor
[Verizon Samsung Galaxy S 4] fallingd0wn:
I had the same problem. Verizon. Wiped system and data before install. Picked Elite kernel in Aroma but ended up with an older Faux kernel after install and no wifi. I flashed the latest Faux kernel from his thread to fix. Haven't found any other issues yet.
[Verizon Samsung Galaxy S 4] GreatDayChap:
Sorry for the delay - I hadn't installed syslog and had next to no idea what to do to grab a log. Here:

https://www.dropbox.com/s/htcr87x3cv3v8gx/2013-10-02_16.26.zip

jfltevzw, yes I did a factory reset, and I installed Elite Kernel.

EDIT: Flashing Chronic Kernel seemed to fix my issue.
[Verizon Samsung Galaxy S 4] hlxanthus:
Okay, I have an idea what going on.
[Verizon Samsung Galaxy S 4] jwattt:
coming over from your G.E. rom. doing a full wipe and clean install. let the fun begin!
[Verizon Samsung Galaxy S 4] Dubbsy:
Fix for elite until we get the updated build uploaded

https://copy.com/NeiHh

sent from my Verizon Galaxy sIV
[Verizon Samsung Galaxy S 4] hlxanthus:
Just to clarify. There was a spelling error when calling to install selected kernel ONLY if installing Elite Kernel, and only on verizon. It has been fixed and will be upload this evening. Thanks for finding this guys!!

And another option for you guys is you can flash the rom again, choose no factory reset, apps and kernel options, then go thru and simply select either agat or stock kernel.
[Verizon Samsung Galaxy S 4] alleyboy727:
Just installed this rom everything booted just fine on sprint with stock kernal but I can't download from the play store it just says download error
[Verizon Samsung Galaxy S 4] hlxanthus:
How long did you let it settle? You usually have to let everything sync before you can download from the play store. Try rebooting and/or doing a cache/dalvik cache wipe.

Sent from my Galaxy S4
[Verizon Samsung Galaxy S 4] Nugg14:
Quick and easy question. Can we use any 4.3 vzw loki kernal with this build?
[Verizon Samsung Galaxy S 4] an21281:
Also try to clear cache, clear data and force stop play store by long pressing/app info, then reboot and see if that helps.

---------- Post added at 05:48 PM ---------- Previous post was at 05:47 PM ----------

I think it has to be AOSP, not TW.
[Verizon Samsung Galaxy S 4] Ryno77:
Play store problems are likely not related to the rom. I just read a tweet from Droid Life about the Play store not working properly.
[Verizon Samsung Galaxy S 4] Tsukasa Buddha:
Hm, didn't fix it with me.
[Verizon Samsung Galaxy S 4] an21281:
Maybe try a factory reset, not sure whats up... Or like stated above, it may be just a problem with the Play Store itself that google will have to fix...?
[Verizon Samsung Galaxy S 4] hlxanthus:
It is android wide . . so not ROM related

http://www.droid-life.com/2013/10/02/google-play-currently-experiencing-issues/

Sent from my Galaxy S4

---------- Post added at 06:16 PM ---------- Previous post was at 06:12 PM ----------

Compass is a known issue for all aosp builds for the gs4 I believe. As of yesterday we still couldn't find a fix.

Sent from my Galaxy S4
[Verizon Samsung Galaxy S 4] Treken:
@ Everyone,

If you are having issues, please capture a logcat while trying to replicate the issue. This means using your pc and adb logcat command with your data transfer cable connecting phone to pc, or using a market app that allows you to run it in the background. I can not stress enough that we must have a log so the issue can be pin pointed. Thanks ;)

Play issues are reported from Droid Life forum so check the details there.
[Verizon Samsung Galaxy S 4] d11dog11:
Does this have the Samsung camera like gpe version?
[Verizon Samsung Galaxy S 4] hlxanthus:
That is an aroma option

Sent from my Galaxy S4
[Verizon Samsung Galaxy S 4] JamesPumaEnjoi:
Love it...love the commradarie within the team and it shows in the work you guys produce. Keep up the great work guys we all appreciate it very much. I'm out of thanks today but I'll be back.....oh I'll be back!
[Verizon Samsung Galaxy S 4] markwebb:
Yes it does work. Any luck on the stock kernel issue?
[Verizon Samsung Galaxy S 4] Dubbsy:
We'll be working in kernel this week. Likely with buck and agat. We'll get it fixed.

I'm still not positive that it's not a bad upload because I'm running stock kernel now

sent from my Verizon Galaxy sIV
[Verizon Samsung Galaxy S 4] markwebb:
Wonderful and thanks! No rush as the Elite kernel is working fine. This is my "other daily driver" when I tire of the TW bloated interface. Nice change of pace and small file sizes and fast!

EDIT: Actually, another issue. Though indicator says I get data, it has been weak (VZW issue??), and then incoming caller could not hear me nor could I hear them. I then called them and had the same issue. Phone then rebooted. Not sure if Elite kernel related. Anyways, I went back to your prior release as that one is working well. I can wait till the next fix.
[Verizon Samsung Galaxy S 4] Persianhawkes:
Can anyone confirm that ir blaster works. I saw that watchon is bundled but just want to confirm if it works. Thanks.
[Verizon Samsung Galaxy S 4] cjkacz:
Mine works in VZW
[Verizon Samsung Galaxy S 4] Dubbsy:
That was literally the very first thing we added to AOSP's code. lol

I can't use watchon because I've been spoiled with better remote options. So Ive never personally tested watchon, but I know the ir blaster works perfectly.
[Verizon Samsung Galaxy S 4] lightiv:
Lovin' It 10/18 Build

Just wanted to drop in and say how I am loving the latest build and as an added bonus I discovered that I can get a 4G signal if my phone is placed in the right position and location in my office. Tethering is most important to me and the native app is working great.
[Verizon Samsung Galaxy S 4] Persianhawkes:
Thanks its for my ole lady. She loves watchon. Havent told her about smart remote yet lol.
[Verizon Samsung Galaxy S 4] thadialeckt:
I don't like watchon much. Smart remote is better. Which app do you use dubbsy
[Verizon Samsung Galaxy S 4] Dubbsy:
I use whatever that remote is that cost 15 bucks. Not sure if it was worth it... But it's 10000000% better than watchon

sent from my Verizon Galaxy sIV
[Verizon Samsung Galaxy S 4] pastert33:
Great job on this! Really appreciate it. I have read through the thread and noticed a few ppl mention the TW cam and that is was an aroma option. What option do I select to have this BC I cannot find it. Thanks in advance
[Verizon Samsung Galaxy S 4] Dubbsy:
No the GE4.3 is an option. We arent even remotely close to adding the tw yet. It's planned but way down the list.

sent from my Verizon Galaxy sIV
[Verizon Samsung Galaxy S 4] reznaur:
I've got a Samsung Dev edition and still for the life of me can't get this to work. I've tried every RC build (one, two and three), tried Philz recovery (recommended for the Dev device) and the latest version of TWRP flashed via Goomanager all to no avail.

When I used TWRP I got a "set-perm failed" at the very end of the install and then the ROM just wouldn't boot at all. TWRP also took a crazy long time to load so something seemed off there (I went back to Philz). Also Aroma couldn't detect my phone which seemed wrong (worked fine with Philz). I emailed the TWRP guys to see if they have a non-loki'd build for the Dev phone but haven't heard back yet.

When I tried Philz with RC3 again last night I got the ROM to boot but it took about three minutes and then couldn't connect to VZW. Rebooting still took about three minutes and nothing could make the data work (WiFi worked).

Anyway I REALLY want to get this working but am somewhat at a loss of what to try next.

Any help greatly appreciated, thanks for all your work on this!

Dan
[Verizon Samsung Galaxy S 4] Dubbsy:
The entire team ONLY uses TWRP 2.5.0.2

Hlx was working directly with a Dev edition person to figure things out. Last I had heard it was fully working

sent from my Verizon Galaxy sIV