yashsingh1/xdaforums huggingface dataset:
[Sprint Samsung Galaxy S III] TexasLTE:
I downloaded that test version = so far so good but I gotta hit the sack to get ready for work tomorrow :)
[Sprint Samsung Galaxy S III] morbidj:
I'll report back soon boss ?

---------- Post added at 10:22 PM ---------- Previous post was at 09:27 PM ----------

I dirty flashed the test build... Lost CDMA radio and details in settings.. I flashed a kernel we don't talk about on xda and radio is back and this build is flying...!

---------- Post added at 10:37 PM ---------- Previous post was at 10:22 PM ----------

BTW the white looks very clean opposed to holo blue..
[Sprint Samsung Galaxy S III] TheKenRob:
Dirty flashed lost NOTHING great find. Will report back tomorrow working night shift will run it throughout.
[Sprint Samsung Galaxy S III] morbidj:
Clean flashed and for the first time I didnt have the baseband / modem issue.. :)

I noticed with both dirty and clean flashing the new "test build" "Ok Google" is not listed on the home screen widget and although selected in the settings does not function..

Not a biggie just thought I would report... Thanks for your efforts this baby is really getting polished out..
[Sprint Samsung Galaxy S III] TheKenRob:
Ran throughout the night all is well! Keep the updates coming!
[Sprint Samsung Galaxy S III] tpike1296:
Using the test build with dkp kernel. Other than some minor complaints like buggy SMS (may be due to the network where I am), or not being used to the smaller feature set compared to CarbonROM, I am loving it. Multiwindow is definitely useful and I can't wait until it gets polished, and the build is running fine.
[Sprint Samsung Galaxy S III] androidsftw:
Do any of you that are using the test build use bluetooth? If so, can you tell me the status of that? Sorry I haven't posted a build in a few days.. school's started and it's really busy again so I shall post a build as soon as I can.
[Sprint Samsung Galaxy S III] huckl3b3rry:
I will test it out, but I won't be able to until this weekend most likely. Thanks for working on it.
[Sprint Samsung Galaxy S III] j00manji:
when/how did we get multiwindow working on AOSP? feels like I've been out of the game for a while
[Sprint Samsung Galaxy S III] das_webos_transformer:
Multi window (corner stone)is a open source feature, Samsung was just the first to utilize it in a large scale. Omni is the only open source ROM I know of that has this feature, because they developed it, I'm sure it highly tied to the framework. Here is the site http://www.onskreen.com/cornerstone/
[Sprint Samsung Galaxy S III] halodos:
Native WiFi tethering still working on the Jan04 build, which I also dirtyflashed and which has been working perfectly these past 5 days. I think I had a few random reboots the first day, but everything has been clear so far.

Awesome build, no problems so far!

2 experimental things that haven't yet worked for me, which is expected, are ART and multiwindow.

Multiwindow is kinda buggy and not clear as to which apps are open in the multi, but i don't really care about that since it is in the process.

For those that have used ART, have you checked after the fact to see whether ART is actually enabled? What happens to me is that I get an immediate reboot during the loading screen after enabling ART, after which it switches back to davlik if I look on the dev options. But again, no problem since it is in development.

Thanks for the build again!
[Sprint Samsung Galaxy S III] MassStash:
Just dirty flashed that test btw, booted up all good. Bout to try ART

~d2spr runnin' Carbon Latest Nightly;

Expletive Deleted Kernel

cpu0/1: 1.512ghz | 384mhz | sleep 486mhz

ondemand

row

mpdecision: Rom Based

thermald: Kernel Based

Tapatalk4
[Sprint Samsung Galaxy S III] MassStash:
ART booted up, no reboot, seems to be running well so far. (wouldn't let me edit last post sorry)

~d2spr runnin' Carbon Latest Nightly;

Expletive Deleted Kernel

cpu0/1: 1.512ghz | 384mhz | sleep 486mhz

ondemand

row

mpdecision: Rom Based

thermald: Kernel Based

Tapatalk4
[Sprint Samsung Galaxy S III] das_webos_transformer:
So when you selected ART, IT DID NOT REBOOT? That means its not working.
[Sprint Samsung Galaxy S III] MassStash:
Huh? Nah, it's working. You said it reboot after first reboot, and the setting was still set at Dalvik. Could you see my Screenshot with the setting on ART? That's after selecting ART, hitting ok to reboot and rebuild cache, 10mins of cache rebuilding, then the setting sticking correctly to ART. Running really snappy now

~Jflteusc runnin' latest Carbon Nightly

Latest KToonsez Kernel 2.1;189;480

Pegasusq

Row

Thermald:

Mpdecision:
[Sprint Samsung Galaxy S III] SOHKis:
ART is running fine for me on the 01/05 build, if you do continue to build i hope you leave the cherry-pick that removes the holo blue. looks so much cleaner as white/grey imo.

thanks for the builds! :good:
[Sprint Samsung Galaxy S III] das_webos_transformer:
I didn't say that, that was another user :P but thank you for the reply, I'm still on the first multiwindow build, my volume up key doesn't work, and when I flash ROMs, I have to be 100% its something I can stick with, I don't want to jimmy rig a connection with the phone open to get to recovery hahaha.

Also, is it safe to say that you SIG is outdated? :P
[Sprint Samsung Galaxy S III] halodos:
Lol yeah, I'm the one who gets the reboot reset to davlik after the auto reboot. Cache never rebuilds for me

What recovery do you use? I'm in the latest cwmr touch. Also do you use supersu?

Thanks yo
[Sprint Samsung Galaxy S III] androidsftw:
I always use ART and it works great for me. Sorry I haven't posted a build guys, I'm trying to test something and if it works, I'll put this up as my next build. I've decided to not to go pure omni yet because there's some loss in functionality.. so I'm still using some slim (and caf commits from omni's gerrit).

Edit: I figured out what is causing that issue with baseband. Problem is, I have no idea how that tweak is causing it.
[Sprint Samsung Galaxy S III] androidsftw:
Your volume up key doesn't work? Mine's working fine. :P
[Sprint Samsung Galaxy S III] das_webos_transformer:
Well, after your phones been in a pool, two broken screens and the wild Indiana summer months and over a year old, let me know how that volume key is doing!!! :P

Edit

And I mean all the way to the bottom of the pool, like fully submerged.
[Sprint Samsung Galaxy S III] androidsftw:
Time to test that ;)
[Sprint Samsung Galaxy S III] das_webos_transformer:
I mean, parts for this thing are pretty cheap, new volume rocker cone with like a new call speaker too, and another thing, they're all on the same ribbon. So when I upgrade, it'll be like new! Just I don't have $10 to order it, seems like everything cost $10 these days
[Sprint Samsung Galaxy S III] iofthestorm:
Hey, are you Ani Ravi on gerrit? I'm Ibrahim, was wondering how you're progressing with this. I am trying to do a bringup for d2vzw but I don't want to use repos from Slim and CM so that it can actually be merged eventually. It's actually pretty straightforward to get it booting, just RIL is broken so no network unfortunately. I guess right now I'm kind of busy but maybe next weekend I'll take a closer look and try to get a proper build working and then figure out which commits are actually needed from Slim and CM. Do you have a local manifest posted somewhere? Thanks!

Edit: Oh, I see you responded on gerrit, I'll check it out next weekend. Thanks!
[Sprint Samsung Galaxy S III] androidsftw:
By RIL being broken, do you mean that baseband and everything shows up unknown? That's not because the RIL is broken. It's because the init binary isn't properly generated, and the patch that I posted on gerrit that fixes that just got merged. My new instructions show how to build with just omni itself and get it working, so it's what you would want. Actually, if you have your device tree set up right, you can just do a plain build (only the android-4.4 branch) without any kernel modifications and just the necessary device tree modifications for build, and you will have a working build. I'm only using the qcom-4.4_2.7 branches for the newer caf stuff and (possibly?) better functionality. (only problem with using the qcom-4.4_2.7 branch is that a kernel revert is needed, and if you do end up using those branches, people can't use custom kernels because no custom kernels will have the commit reverted.)
[Sprint Samsung Galaxy S III] iofthestorm:
Oh neat, that's exactly what I meant. Will have to give it a try. Now that it got merged do you think they will be doing official support soon? Is anyone ready to maintain d2s? Lol I've been doing builds for my tablet for like 3 months and because of random stuff that never gets done) finalized I've still not gotten nightlies (even though the repos are forked and the blobs are there). But it seems like d2 should be good to go now?
[Sprint Samsung Galaxy S III] GideonX:
It'll likely never get official support. None of their devs have a D2.
[Sprint Samsung Galaxy S III] acoustikamusika:
How do you enable multi-window?
[Sprint Samsung Galaxy S III] androidsftw:
I guess d2's would be "good to go" if someone was willing to maintain them.. and also an issue is, I'm using cm for msm8960-common, qcom-common, hardware/samsung, and Muppets for vendor/samsung. The msm8960-common and qcom-common repositories are out of date on omni because no one is doing any work with those. I guess if those were synced or had all the new cm commits, it might be possible for someone to become a maintainer.
[Sprint Samsung Galaxy S III] androidsftw:
Hold home button to open recent apps, then tap & hold on an app and select "split view". It's a work in progress so it might not work that well for you.
[Sprint Samsung Galaxy S III] iofthestorm:
Uh, that's a weird thing to say. Anyone can become a maintainer.

Eh, you don't actually need to use cm repos for those things right? They may be out of date on Omni but that is probably just because not many devices are using those repos, and I just ran off a build which is working fine now thanks to your init stuff being merged. Can't you and GideonX and whoever else has been doing these ports maintain them? Usually I see people just pop into IRC and ask for repos to be forked and maintainer status and xplodwild just gives it to them.
[Sprint Samsung Galaxy S III] GideonX:
I don't want to maintain. I like not feeling obligated to focus on this in all my free time.

I nominate [MENTION=2105079]androidftw[/MENTION] :)
[Sprint Samsung Galaxy S III] EverDeathly:
[MENTION=5490820]androidsftw[/MENTION] xD
[Sprint Samsung Galaxy S III] GideonX:
Fat fingered it ;)
[Sprint Samsung Galaxy S III] androidsftw:
I don't want to be a maintainer. And yeah I know they're out of date because no devices use them. Besides the jf devices.. which I'm not really even sure if they're being worked on at all anymore.
[Sprint Samsung Galaxy S III] androidsftw:
Wait you made a build with omni's msm8960-common, qcom-common, and hardware/samsung? It shouldn't have worked. sepolicy is defined under msm8960-common for the d2 devices in cm but it's not commonly defined in omni (it's defined in the specific device tree, such as jf-common), meaning that you made a build without any of the device-specific sepolicy definitons.
[Sprint Samsung Galaxy S III] iofthestorm:
Err, granted I don't really know how sepolicy files are supposed to be set up, but do you mean https://github.com/omnirom/android_vendor_omni/tree/android-4.4/sepolicy ? That looks like a common definition for omni to me, but again I know nothing. I'm pretty sure the build I'm running on my phone works... I did try using CM repos for those earlier (and the other stuff you defined) but I must have missed something because my build was broken, so I went back to all omni repos.

Edit: I dunno what device specific sepolicy files are supposed to be needed, if any, but like I said, the build I did seems to work fine as far as I can tell. For the record I never set up sepolicy definitions when I did a bringup for my tablet either and I've never had issues.
[Sprint Samsung Galaxy S III] androidsftw:
https://github.com/CyanogenMod/android_device_samsung_msm8960-common/tree/cm-11.0/sepolicy
[Sprint Samsung Galaxy S III] iofthestorm:
Oh derp, I forgot that I had set selinux to permissive, that's probably why it works. I bet there's a bunch of selinux violations spamming logs or something.
[Sprint Samsung Galaxy S III] androidsftw:
Yeah don't set it to permissive.
[Sprint Samsung Galaxy S III] morbidj:
My favorite ROM bar none hands down.. Been quite as of late.. Have you moved on dev?
[Sprint Samsung Galaxy S III] androidsftw:
Nope just working on something that I'm hoping to implement before I post the next build. Sorry for the wait. I usually upload builds weekly anyways.
[Sprint Samsung Galaxy S III] morbidj:
No need to be sorry DEV, I should be the one apologizing I have bean running a build from 1-11 and didn't even notice the update listed in bold on the first page... Updated and it's a real beauty! Thank you
[Sprint Samsung Galaxy S III] shekinahsmoke:
New build. Dope

Beanstalk ROM HAHTBWAOY
[Sprint Samsung Galaxy S III] androidsftw:
I have a surprise soon ;)
[Sprint Samsung Galaxy S III] shekinahsmoke:
I'll standby :) If you can get me off of beanstalk Im dropping $$ :good:
[Sprint Samsung Galaxy S III] TheKenRob:
Nothing but goood! All quiet here... Great sign, "Keep it movin' nuthin' to see here folks"
[Sprint Samsung Galaxy S III] ChoznJuan:
Just notice a small issue on the 2/11 build, the search function in the dialer app, doesn't give suggestions of nearby business.
[Sprint Samsung Galaxy S III] androidsftw:
Same with mine. I'm not sure what the issue is there, or if that's even supposed to work (which I thought it was supposed to)
[Sprint Samsung Galaxy S III] Russ0000:
Awesome ROM thanks for supporting the d2spr. I have been running the 2/15 build and everything is running quick and smooth.
[Sprint Samsung Galaxy S III] morbidj:
Thanks chef just downloaded the 16th build off the server!
[Sprint Samsung Galaxy S III] androidsftw:
Did you do it through the delta updater? :D
[Sprint Samsung Galaxy S III] shekinahsmoke:
Found it!!!!

Beanstalk ROM HAHTBWAOY
[Sprint Samsung Galaxy S III] androidsftw:
Found what? :P
[Sprint Samsung Galaxy S III] Russ0000:
I went through the delta updater. Update download fast with no issues until installing. It reboot into recovery and the failed. I was able to manually install without issue. Sick ROM, stable and fast. I even switched to art and everything is running awesome. Thanks
[Sprint Samsung Galaxy S III] androidsftw:
What recovery are you using?
[Sprint Samsung Galaxy S III] Russ0000:
I'm running clockworkmod for recovery. Its fully up to date. I did put a kernel in the I think its called update and flash folder. Not sure if that caused it to fail.
[Sprint Samsung Galaxy S III] androidsftw:
No it's because you're running clockworkmod. You have to use TWRP or philz. CWM disables scripting by default. The FlashAfterUpdate folder inside the OpenDelta folder in your internal storage is awesome. It'll flash anything you put in there after it flashes the delta update.
[Sprint Samsung Galaxy S III] Russ0000:
Oh gotcha. No problem, I don't want to change my recovery so I'm fine with manually flashing. One thing I love is Omni picks up my 64gb SD card. Every other kk ROM I have used won't pick it up or mount it until I flash an exfat zip.
[Sprint Samsung Galaxy S III] androidsftw:
There's nothing wrong with changing recoveries.. ;) Philz has a ton of features and TWRP is just.. TWRP :P And yeah, omni has built in exfat support through FUSE. It's pretty awesome.
[Sprint Samsung Galaxy S III] morbidj:
No, I manually updated.. For testing sake or just to screw around I can try it through delta.
[Sprint Samsung Galaxy S III] androidsftw:
But now, I don't need to date my thread anymore. If people want updates, they're welcome to check for them :D
[Sprint Samsung Galaxy S III] shekinahsmoke:
this is it? highlight ->>> http://androidsftw.believable.org/index.php?dir=omni%2Fd2spr%2F
[Sprint Samsung Galaxy S III] androidsftw:
Yup. Delta updates :D
[Sprint Samsung Galaxy S III] EverDeathly:
2/15 building running awesome c: good job bro
[Sprint Samsung Galaxy S III] androidsftw:
If you happen to be running TWRP or philz, you should check for updates in settings because the 2/16 build was up yesterday :D
[Sprint Samsung Galaxy S III] ssmercurys:
I tried through Updates as well and get same thing. I am on latest Philz Recovery as of 2-15 build of it.

Manual flash worked fine though.
[Sprint Samsung Galaxy S III] androidsftw:
Alright then, I thought philz had scripting support. Guess not. I'll change my OP to only TWRP to be on the safe side.
[Sprint Samsung Galaxy S III] shekinahsmoke:
[MENTION=4666971]Phil3759[/MENTION] [MENTION=4645794]CNexus[/MENTION] :confused: interesting.
[Sprint Samsung Galaxy S III] CNexus:
Philz does have scripting support and I've flashed roms that have updates in that way too...Not sure what's going on with yours
[Sprint Samsung Galaxy S III] androidsftw:
I'm pretty sure someone using GideonX's builds (he implemented deltas in the exact same way as me) said that philz worked for them. Which is why I'm confused.
[Sprint Samsung Galaxy S III] androidsftw:
Meh I'll clean up the OP in a day or two once everything is ready to go.
[Sprint Samsung Galaxy S III] shekinahsmoke:
Proud that this was a civil interaction. Maturity is always attractive.

Beanstalk ROM HAHTBWAOY
[Sprint Samsung Galaxy S III] CNexus:
Odd...and they also said (in this thread) that flashing manually DID work? Even weirder :confused:
[Sprint Samsung Galaxy S III] androidsftw:
Well flashing manually will work with any recovery since it's just the full zip file. :P
[Sprint Samsung Galaxy S III] CNexus:
Wait...I thought the point of the delta updates was that it constructed the deltas and flashed that...the difference between your version and the most recent one? So as NOT to have to resort to flashing full zips and flash smaller files instead?
[Sprint Samsung Galaxy S III] androidsftw:
Correct. But you can still flash the whole zip manually if you want. If you use the delta updater, then it'll only flash the update and not the full zip. (Depending on the size of the updates from your build to the most recent. I believe that if the amount of updates from your build to the latest is larger than the actual zip file, then it just downloads the zip file. But that would mean you're more than just a few builds behind :P) Check my website. You'll see that I have the whole zip, an md5sum file, and a .delta, .sign, and .update file which are dated to the previous build from the current zip (it's designed this way on purpose)
[Sprint Samsung Galaxy S III] CNexus:
Ah, so when they mean "flash manually", I guess they meant manually flashing the entire zip? That's what I was missing, I thought they meant manually flashing the delta zip which wouldn't make sense if that worked but ORS flash didn't
[Sprint Samsung Galaxy S III] iofthestorm:
Err, the delta is actually applied to the last full zip to make a new full zip, which is then flashed. You can't flash the delta update, because it's not a valid zip file. Not sure if that's what you meant but it wasn't clear to me.
[Sprint Samsung Galaxy S III] androidsftw:
Yeah that's what I meant, but my wording was just off.
[Sprint Samsung Galaxy S III] trouinky:
2/16 updated OK for me with Phil's.

Have a question about the interface control in omni. In not seeing a toggle for the navigation bar. I like to turn it on when I have headphones in (so the jacks at the bottom). Is this not an option in Omni?

Not complaining, just asking. This rom Rocks!
[Sprint Samsung Galaxy S III] androidsftw:
Alright, thread is ready :D I hated my long OP from before.
[Sprint Samsung Galaxy S III] Advertize:
I just thought i would let everyone know that this is a very smooth and fast rom. I was skeptical but had to check it out and was pleasantly surprised. I threw everything at it I could think of and no FC's and no reboots. :highfive:
[Sprint Samsung Galaxy S III] Xtazy305:
the phone gets really hot with the screen off, and battery last like 2 hours with almost no use :eek::eek::eek::eek:
[Sprint Samsung Galaxy S III] androidsftw:
Blame CM's kernel :P Try a custom kernel and see how it goes :)
[Sprint Samsung Galaxy S III] Xtazy305:
Thanks bro:cyclops: testing now :laugh:
[Sprint Samsung Galaxy S III] Russ0000:
Try lean kernel seems to run really good with Omni.
[Sprint Samsung Galaxy S III] Advertize:
I havent tried lean on this rom but BMS works well.
[Sprint Samsung Galaxy S III] EnZos_Game:
Are your previous builds still available for download?

Edit: nevermind i read your op. Hopefully you can put them up...All the d2lte Roms seem to Fork LTE
[Sprint Samsung Galaxy S III] Russ0000:
Is anyone else getting this error when clicking on the downloads icon? I removed it from system apps and pulled a downloads apk from another ROM and get the same error. I even tried manually installing the downloads apk. Getting same error.
[Sprint Samsung Galaxy S III] Russ0000:
Update: Not sure what I did cause I restored my back up from a couple of hours ago and downloads is working fine now.
[Sprint Samsung Galaxy S III] trouinky:
I dirty flashed 2/18 d2lte and lost voice and data. Was on 2/16. Is there a fix or should I have installed from scratch?
[Sprint Samsung Galaxy S III] Russ0000:
What phone are you using? Did you have service before rebooting?
[Sprint Samsung Galaxy S III] trouinky:
d2spr

Was running perfectly on Omni 2/16 before flashing the LTE update...

Installed as per GideonX's OP instructions.

Even tried a clean flash of 2/18 d2lte with the same results... No phone or data after rebooting.

I restored my 2/16 nandroid backup and everything's back.

Anyone else successfully move to the LTE version?
[Sprint Samsung Galaxy S III] Russ0000:
After you restored from your back up do you have working LTE?

---------- Post added at 06:10 AM ---------- Previous post was at 06:00 AM ----------

The reason I'm asking if you had data before reboot is because if you lost data after reboot that is a known issue with all d2lte roms. If you had no data after a clean flash of d2lte before reboot it could of been a bad download. I have had that issue before and I just redownloaded the rom again and clean installed and got service and data back.
[Sprint Samsung Galaxy S III] trouinky:
Yes LTE is fine after restoring the backup.

Can't imagine the download is bad I mean if it was, the zip wouldn't open and the flash would fail.

Thought it might be a kernel thing so I let it boot with the included kernel but it was the same.

On the initial boot it tried to call in to activate the phone but I skipped that. Had to do that for previous Omni ROMs so maybe its required for the d2lte versions? I'm afraid to try that step...
[Sprint Samsung Galaxy S III] androidsftw:
Yeah guys LTE on the d2spr is messed up right now with d2lte. For technical reasons that I don't feel like getting into, d2vzw is probably the one phone with LTE and everything (as far as I've heard) working. We'll just have to wait and see what CM plans to do..

And skip the activation stuff as usual. That honestly shouldn't be showing up by default, but whatever. Just a minor quirk anyways ;)
[Sprint Samsung Galaxy S III] Russ0000:
The call in to activate always fails for me. I always just skip that. I have the d2spr as well. I went on CM11 D2LTE and looked at the change logs and it looks like they added a fix for the LTE issue Tuesday. So hopefully any new builds after the 19th will have it fixed.
[Sprint Samsung Galaxy S III] trouinky:
That would be awesome.

Is there an xposed module that might enable the navigation bar? I like toggling it on when I'm using headphones but I don't see a toggle for it anywhere.
[Sprint Samsung Galaxy S III] EnZos_Game:
Yea.. there might be an individual module but I use Gravity Box for KK in the xposed modules. works great. :good:
[Sprint Samsung Galaxy S III] androidsftw:
Are you talking about the LTE fix for gsm commit? That doesn't have to do with this. I think I might have figured out what it could be, I'll need to test though. Hopefully I'm right.