yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] swordmastr54:
Question,is the 4.3 ROMs dead because of the new 4.4? They are nice and all but this ROM is more stable with less bugs ATM so are we doing anything else with this one or is it done?
[Verizon Samsung Galaxy S 4] jova33:
I think AOKP is doing a milestone for 4.3, but they're working on 4.4

Sent from your mom's smartphone
[Verizon Samsung Galaxy S 4] jova33:
Are you still going to be putting these out?

Sent from your mom's smartphone
[Verizon Samsung Galaxy S 4] apophis9283:
I talked to him last night. I cant speak for him but yeah, pretty sure hes going to continue. The 4.4 transition at least for me was a much needed break. Lets me take care of life things. Things will get going again, hopefully soon.
[Verizon Samsung Galaxy S 4] jova33:
I haven't tried any 4.4 ROMs. Waiting for something feature rich and stable. I tried CM many moons ago, and it was too vanilla for my tastes. Root Box was the jam. Tried PAC ROM after that dude quit putting out RB, but just wasn't the same.

Wish we had a Nexus 5.

Sent from your mom's smartphone
[Verizon Samsung Galaxy S 4] mcconvict:
Try ose. Its pretty good
[Verizon Samsung Galaxy S 4] bkrickles:
+1 I agree. ose is the best kitkat rom I've tried

omni runs just as well, but has fewer features right now

everything I use works on ose and I'm running it with kt kernel. I think 12/12
[Verizon Samsung Galaxy S 4] wessiide:
Really hoping to see this rom updated to 4.4!

Sent from my SCH-I545
[Verizon Samsung Galaxy S 4] jova33:
AOKP has already put out at least one 4.4 nightly. I think there's some stuff that's borked with it though and I didn't want to bother flashing it. I can wait.

Sent from your mom's smartphone
[Verizon Samsung Galaxy S 4] DaMadOne:
Hello all. I assure you I will be continuing. I was a BF4 addict for a while =P then spent the holidays with my parents. It was a much needed "android break". I am still daily driving the last SmoothAOKP 4.3 build and am quite pleased with how well it has held up to time. I got a new processor (AMD FX-8350) and a new SSD with enough space on it to house and compile the android goodness on. My compile times have dropped dramatically which is very nice. I started from scratch with the new SSD and reloaded my OS's so I don't have the AOKP 4.3 sources on it, is there interest in me pulling it down long enough to compile a smoothaokp build based on the 4.3 milestone?

A little teaser =P Not much to see here yet. I did compile it with the linaro 4.7 toolchain, but only using "stock" optimization flags. I just wanted to see what kinda trouble simply swapping out the toolchains would cause. A couple of kernel patches and I was in business. AOKP kitkat is still an infant and is missing most of the customization options we have all grown to love, but a lot has happened since I really started to watch what was going on while at my parents over christmas. I plan to try and throw my hands in and do what I can to help get the features ported back over. They have made some changes to how they are doing things and RC has obviously changed quite a bit so once I get familiar with it ill dive in.
[Verizon Samsung Galaxy S 4] jova33:
Oh, I'd love to see a linaro 4.3 milestone. So count me in.

I'm half tempted to get a Moto X DE, but as of two days ago, that's last year's smart phone lol. But seriously, the S4, loki, and all the TW/AOSP non-compatibility has really turned me off from buying another Galaxy phone in the future. At least on VZW.

Edit: for example, i take a ton of pictures, but can't stand TW. If I go with an AOSP ROM, I'm not getting the best out of this phones camera. So I delved into dual booting TW ROMs and AOSP, while fun and challenging, added a whole new layer to just flashing a new ROM.

Sent from my SCH-I545
[Verizon Samsung Galaxy S 4] DaMadOne:
Its incoming. It wont be true a "milestone build" as they did not put up a milestone specific manifest on github, they did do milestone tags but I don't feel like going through the whole manifest and making one myself. It will be based on what is in the jb-mr2 repos now, which is final as all jb-mr2 development has ceased anyways. Im pulling the source now. When its done ill run my scripts and pop out a build and test. As long as all seem g2g ill post it up! May be tonight.. may be tomorrow as it is getting kind of late and ive had a few of my high grav IPA homebrews =P

I did not stick with TW but a few hours after I picked up my S4 before hacking it to bits because it SUX! Does the TW camera app REALLY produce that much better of a picture vs aosp? I love my s4 but unless vzw policy on unlocked bootloaders doesn't shift in my favor I can see this being my last non Nexus device. We got lucky with loki... will the s5 or the s6 possibly by the time its time for me to upgrade have the same luck? not likely. Of course there is the possibility of me getting a DE Galaxy S* model... but its still not the same. I guess only time will tell.

And, yea... after looking at the dual boot stuff you posted... its way too much involved for flashing builds. When actively deving and testing I may flash 10+ builds in one evening. NO GO!
[Verizon Samsung Galaxy S 4] jova33:
The TW camera is way better because TW has that closed source goodness that maximizes the hardware's potential. I guess that's way nexus phones usually have sub-par cameras; camera manufacturers don't want their stuff open source.

And dual boot is way more work than I'm willing to continue doing.

As far as DE Samsung phones, they put out the S4 DE and offered no support for it. Don't they have issues with custom ROMs because the hardware is different than the regular VZW S4?
[Verizon Samsung Galaxy S 4] jova33:
Oh, with the 4.3 did they fix the Wi-Fi tether hot reboot if Wi-Fi was on?

Also I know they fixed the issue with the MJ7 radios, I'm on the build right before it was put in.

Sent from your mom's smartphone
[Verizon Samsung Galaxy S 4] DaMadOne:
OP is updated with SmoothAOKP 4.3.1 FINAL!
[Verizon Samsung Galaxy S 4] DaMadOne:
I have been running the MJ7 radio without issue for a long time. Please elaborate on the problem. I JUST now tried to enable wifi hotspot while wifi was enabled and was met by a reboot. so no.
[Verizon Samsung Galaxy S 4] apophis9283:
Where have you gone to?
[Verizon Samsung Galaxy S 4] DaMadOne:
:laugh: I'm working on it, I wanna make sure that it's right.
[Verizon Samsung Galaxy S 4] GTvert90:
It's all good man. Just reflashed the 8-10 build last night with some inverted gapps it's running great
[Verizon Samsung Galaxy S 4] DaMadOne:
Well it looks like in my "way past my bedtime" state last night I missed something when setting up the build for 4.8 linaro. MOST of the toolchain pointers were pointing to the 4.8 toolchain. But I missed one. So it party compiled with the old chain. Good news is I fixed it and did a real full 4.8 compile and all is still working like it should. silky smooth. Going to add in the IR and mods from 8/10 and see what happens.. *fingers crossed*
[Verizon Samsung Galaxy S 4] GTvert90:
I need to re read about linaro and try to understand why it makes things smother it's been a while
[Verizon Samsung Galaxy S 4] catapilla:
Awesome. Can't wait bro!
[Verizon Samsung Galaxy S 4] DaMadOne:
Hey what's up fellow android lovers. Just to update, I had to pretty much throw out and rework the script I was using for linaro compiling. 100% sure I have the build directory setup properly to fully use ANY toolchain I want by only changing 1 line in a config file (thanks to Neo and the old project unicorn butter repo for that) Things are going well and I pretty much expect to post a working SmoothAOKP (that's what I'm calling it for those that missed it) tonight. I'm compiling away right now. Rest assured though that I have great help coming from Apopsis and IAmTheOneTheyCallNeo (from now on will be called Neo haha). I have learned soooo much the last couple of days by struggling with linaro and getting the build environment setup properly to use it fully. At this point I am glad I have had these problems because I know so much more about the structure of the source, where things are, what they do and even understanding more of the C/C++ language than I would have learned at this point otherwise. I have learned to use git much more effectively, before when I broke something I didn't know how to properly revert back to a previous state. So I would basically clear out and start over.. the script helps get back to where I was, but it was still a pain because there is stuff I need to do manually after running the script which eats up precious time. Especially on weekdays. Gotta work to pay the bills. :laugh: Overall learning these things saves me 20+ minutes between getting an error and starting over building again. Once all of these things are worked out with linaro it should be smooth sailing from there on out.

tl;dr - Sorry, for not having anything new for you guys, but trust me it was for the better.
[Verizon Samsung Galaxy S 4] Jerryatric:
Don't apologize! I sincerely appreciate the fact you put time into making my favorite ROM from my GNex days fully functional on the s4. Thank you.
[Verizon Samsung Galaxy S 4] jova33:
Yeah, don't apologize to us! Apologize to your wife/girlfriend for spending too much time on the computer lol. And if you don't have one of those..... lucky man.....
[Verizon Samsung Galaxy S 4] DaMadOne:
There we have it. For real this time! Linaro 4.7 for now. I will play with 4.8 on the side... its easy now to switch back and forth =P This was built with -O3 optimization w/ conservative optimization flags to start with. If any of you remember Project Unicorn Butter, I'm using the same exact flags they used. I will work on enabling more flags as I go. I also have have a list of cpu specific optimization code that I will add in. One step at a time though. I scored a 25575 on AnTuTu 3.4 and consistently stayed close to that going above or below a bit, but never going below 25256 (I did hit 26104 once, but that had to be a fluke). That's on the linaro AOKP kernel. While I have gotten into the 25000's on the stock kernel before I got more scores in the high 24000's more often than not. Gonna flash Ktoonzes kernel in a minute and see if it does any better.

I am building with the addons from the last release right now and as soon as I test it out and make sure stuff is working as it should I will update the OP!
[Verizon Samsung Galaxy S 4] DaMadOne:
Thanks guys, my gf has actually been pretty supportive of this endeavor. She thinks it pretty cool actually. I think she sees this as using my time more wisely than playing video games :p

On a side note, I just checked the build. The builder is zipping it up as I type =P lets hope it all works. Ive kinda missed the IR especially here recently as I have been running my wannabe linaro vanilla aokp test builds since I started playing with linaro. Ill test and hopefully have the build up and OP updated within the hour!
[Verizon Samsung Galaxy S 4] jova33:
Sweet! I'm back on Hyperdrive. I hate touchwiz. If you could port the TW camera over to AOKP, that's be great lol.

I kinda like what nitro has been doing with his TW and GPE, but they're still lacking some of the features I just can't enjoy my phone without.
[Verizon Samsung Galaxy S 4] DaMadOne:
Well, The OP was just updated with the inaugural release of SmoothAOKP. :cool:

I want to say I have seen the TW camera ported to AOSP.. Maybe not, I'm tired, Going to bed! Hope everyone enjoys the new build. Let me know if you find a bug or there's a feature you want me to look into adding in.
[Verizon Samsung Galaxy S 4] leyvatron:
You are rocking this thread. I'm west coast so I have a little time to test. Downloading now.

The TW camera would be awesome. The tw camera with the Google edition doesn't work really well. It does take pics but the animated and the little stamp front camera don't work.
[Verizon Samsung Galaxy S 4] jova33:
Downloading now. And the way it's been explained to me is, the TW camera will never be ported. If it could, I'd never be on touchwiz again.

Also, is there a call recording app that works on AOSP ROMs?
[Verizon Samsung Galaxy S 4] dogg94:
Would you be willing to expand on this by chance? (the way it was explained to you) This is honestly the one feature that I've been coming back to TW roms for (Use IR blaster too but that has been successfully ported). The TW Camera is effing fabulous and on aosp roms I seem to have problems with the camera even functioning properly all the time let alone the pictures don't seem to pop the way they should (imo). Thank you in advance.
[Verizon Samsung Galaxy S 4] jova33:
There's too many proprietary files that the camera depends on. TW is closed source. Samsung paid a lot of money to develop their source and they've paid other companies to use patented hardware and software. They're not giving it out for free. It's just not possible to pull the touchwiz camera and run it on AOSP. TW and AOSP are both android, but they are completely different operating systems.

I've tried many different camera apps, even paid for a couple of them, but they just don't compete with the TW camera. The AOSP camera straight up sucks. I'm hoping CM's focal will fix this on AOSP based ROMs.
[Verizon Samsung Galaxy S 4] dogg94:
Thanks for the clarification, I didn't think closed source was as much a physical roadblock as it is a legal one though but maybe that's enough in these days. I've tried focal briefly on one of the unofficial 10.2 cm nightlies, hopefully that will come around obviously at this point it is very beta.

Sent from my SCH-I545 using Xparent Skyblue Tapatalk 2
[Verizon Samsung Galaxy S 4] jova33:
Ok, not impossible, but may not work right.

http://xdaforums.com/showthread.php?t=2370869

I haven't tried yet because I'm still on hyperdrive. I'm going to take a few pictures, flash AOKP, flash this camera, and compare. Some are saying the quality isn't TW quality because some of the libs are missing. We shall see.
[Verizon Samsung Galaxy S 4] DaMadOne:
I am going to look into the TW camera probably this weekend. I did some looking around and I see the GS3 TW cam and gallery app was ported to aosp. Though not 100% working so I'm sure it is possible. I need to look into figuring out what files and libs the camera uses and pull them from my TW backup and see what I can come up with.

On a side note, I am going to be building for Asus Nexus 7 (2012/Grouper) as well since I have one and I might as well run my own builds on there too. I just started a build on my lunch break.. hopefully when I get home it wont have stopped due to an error :rolleyes:. I will post links to them for you guys if you happen to have one. But don't worry the S4 will be priority! Later guys, back to work I go.

yep that's the one I was talking about. I didn't have an S3, whats the difference in the apps? I would assume there are optimizations not only in the app but the libs as well for the s3 hardware so it probably wont act right on an S4? Ill give it a shot when I get home.
[Verizon Samsung Galaxy S 4] jova33:
I hope there's not too much of a difference lol.

Edit: I don't understand why it would only work on the international S3 and not the LTE S3. I think they must have a different chip set and the libs are chip specific. Hmmm.... Maybe just flashing this wouldn't work on the S4. Their software update is also labeled ME7, so I'm thinking it's the same as our camera app, just different libs.
[Verizon Samsung Galaxy S 4] GTvert90:
I believe there is a mostly working tw camera on the GPe port. But that's confusing as well considering the GPe still uses TW and not aosp kernels.
[Verizon Samsung Galaxy S 4] DaMadOne:
yep different chips, from the S3 wikipedia page

Samsung Exynos 4 Quad (international, AU, and KR versions)

Qualcomm Snapdragon S4 MSM8960 (NA and JP versions)
[Verizon Samsung Galaxy S 4] DaMadOne:
Just quoting from the OP in case nobody reread it after I changed it around.

I should have all of the current source up on github before I go to bed tonight. I will be setting it up so that if you want to setup your own build environment and build your own builds from source you will be able to in the exact same fashion that AOKP shows HERE. Except instead of using the "repo init -u git://github.com/AOKP/platform_manifest.git -b jb-mr1" command you will use "repo init -u git://github.com/SmoothAOKP/platform_manifest.git -b jb-mr1". Then it will fetch all of the source to your local machine and to build for our VZW SGS4 you would simply run ". build/envsetup.sh && brunch jfltevzw" and sit back and wait for it to spit out your flashable zip =P. This will also make it easy for others to port this rom to other devices should they choose.

As with the linaro learning experience, this has been another great step in teaching me invaluable skills to help make this project good, and bring you guys the features you want. I am taking the silence in the thread the same as quiet people at a dinner table.. things must be working well because nobody has said otherwise =P I know it's been working just fine for me.

later!
[Verizon Samsung Galaxy S 4] jova33:
Thanks main. Did you happen to figure out the TW camera thing? Qualcomm locks their stuff up pretty tight, so I'm thinking that's why the port wouldn't work on Qualcomm chips.

Oh, and did you ever give Rootbox another look?
[Verizon Samsung Galaxy S 4] GTX1:
The quiet in the thread may have to do with dev's from AOKP showing that they are currently running test builds of 4.3 AOKP. Seems like they have everything ported over and are now in phase of testing it and trying to find any major bugs before nightlies. BMC08GT posted a pic on his twitter of his VZW GS4 running 4.3 AOKP. It's getting closer!
[Verizon Samsung Galaxy S 4] mcconvict:
TW camera will not work on AOSP. It partially worked on Google Play Edition because it has a TW base.
[Verizon Samsung Galaxy S 4] DaMadOne:
Yea Qualcomm has some pretty tight butt holes when it comes to their stuff. I'm assuming you saw all the drama with JDQ? As for the camera it's 1st thing on the list to do as soon as I have the source on the github to where all you have to do is repo init and then compile.. I JUST got done setting up all of the repos. Now to go through and add all the patches.. there's about 40 of them. Shouldn't take but a couple of hours, OR I might stop in an hour and go get my drank on.. so if not tonight then tomorrow while I sit around and nurse a hangover.

I'm not even gonna mess with that sgs3 port.. I'm pulling the TW camera from one my TW backups and going from there. With and apk and libs that I KNOW are made for this phone. Just gotta figure out how to figure out (lol) exactly which libs the apk needs and go from there..

With rootbox it's definitely not something simple.. messed with it for about 4 hours and tried every trick in the book I could think of.. the logcat didn't help either. Just from poking around in the working and non working zip there was quite a change. the new one has libs the old one doesn't and visa-versa, The APN's are fine.. I tried backing up my APNs on AOKP and then restoring them on rootbox.. I have a hunch they changed up the telephony driver.. the line ro.telephony.ril.v3 in the build prop was different between the two. I tried changing it to the working one.. but I got absolutely no service after that.. likely because it's not there. So im assuming that is what tells the phone what lib to use for the telephone radio. But ill add it back to the list of things to look at again because I now know quite a bit more about the system now than I did when I first looked at it.

It COULD be as simple as finding the lib on the working one and adding it to the new build.

Oh yea I saw it! Can't wait.. i've hardly messed with 4.3 at all. I put it on my nexus 7 to poke around for a bit.. but I gotta have ribbons..

I'm sure it's gonna take some time to get all the patches worked out for the linaro toolchain on 4.3 depending on just how much has changed. But Ill definitely be setting up a build with the IR and the added features we have by the time it comes out.
[Verizon Samsung Galaxy S 4] jova33:
They got TW camera partially working on the international S3, non-Qualcomm, for AOSP. The only thing they couldn't get working was camcorder.
[Verizon Samsung Galaxy S 4] DaMadOne:
059HM-V2CG3-6WC0C <- original Dead Space key for steam.. guess the first to redeem it gets it =D

8VHZ-W87V-9JDB-Y2VR-MCBC <-- Key for Battlefield 3 on Origin.. first to redeem gets it
[Verizon Samsung Galaxy S 4] prstorero:
Saw the post about a banner and I needed something to do so here you go :P

http://db.tt/vzKnhtmQ

prshosting.org
[Verizon Samsung Galaxy S 4] DaMadOne:
I appreciate the effort but not quite what I was looking for.. I would like it to incorporate the AOKP unicorn gear somehow

On a whole other side note. I think I finally have the github right.. im building from what source is on it now, so ill know soon =P if not it can't be but another fix or two then ill be done. Then im going to start messing with more optimization flags and try to get take the smoothness to another level =P plus I have some goodies I want to bake in.

On the TW camera front I have the files pulled that I will need. I tried just flashing them.. of course that doesn't work haha. wont even show up in the app drawer. I haven't really looked into it, but what does it take to even get them to shop up in app drawer? Does anyone have any good links to info that might point me in the right direction?
[Verizon Samsung Galaxy S 4] jova33:
No clue.... you've surpassed my level of knowledge on the subject matter. I'm thinking it's not possible. On the S3, they were only able to port it on the non-Qualcomm, international version, so I'm thinking there's something up with Qualcomm devices. Yeah, I watched the JBQ thing. Is he still working at Google? AOSP?
[Verizon Samsung Galaxy S 4] jova33:
http://aokp.co/blog/aokp-and-android-43-status-update

Saw this over at rootzwiki today. Well duh, AOKP has a lot more bells and whistles than CM, and they have to recode everything to fit with 4.3.
[Verizon Samsung Galaxy S 4] DaMadOne:
Yea I saw that. these lines confirm my suspicions. " Some of you may have noticed a distinct lack of movement on our Gerrit and Github accounts. This is due to the nature of where the merge is taking place, not that it isn’t happening."

Me and Apopsis tried syncing with 4.3 over the weekend thinking I could build at least what BMc had shown on twitter.. upon further inspection we realized almost NONE of it is on their github. They must be working out of a private one somewhere. I would not have released a 4.3 build even if I built one, not until they release at least a nightly or preview or something. I was just hoping to get a head start on figuring out the code patching that will need to be done in order to compile with the linaro optimizations I have been using as well as porting over the added features that I have put into SmoothAOKP so far. I guess they really didn't want anyone to see it at all until they are done. Hope its soon. I am testing some things locally (compiler optimizations for speed) as well as messing with linaro 4.8, but I almost see no reason to keep popping out 4.2.2 builds with 4.3 right around the corner. Though rest assured if the IR stuff is not in the first 4.3 release I will build it in immediately (it's simple) and post it to tide everyone over until I can get the linaro stuff figured out.

Just a heads up my monitor for my computer is starting to give me backlight problems, the backlights don't like to stay on and its getting worse fast. Im hoping my buddy still has his old one that I can use for now, because I'm gonna have to eat ramen for a month if I have to run out and buy one right now =/ It's 5+ years old and I can't decide if I want to fix it or get a new one. Replacing the cfl's and transformer will cost $100+ anyways. Has anyone seen any AWESOME deals on a 26"+ LCD's?
[Verizon Samsung Galaxy S 4] GTX1:
http://www.newegg.com/Product/Product.aspx?Item=N82E16824014300

27" BenQ monitor. LED backlit LCD panel (1080p), HDMI, 5000:1 contrast and 4ms response time. $219 usually, theres a deal for today that gives you a $20 off promo code.