yashsingh1/xdaforums huggingface dataset:
[Sprint Samsung Galaxy S III] nocoast:
The compiler is still compiling using linaro's latest 'official' 4.7 TC, the compiler output is looking identical to our usual google/linaro 4.7 output. Linaro's toolchain supports a wider array of architectures and boards than google's but even on linaros website their instructions for fetching the android toolchain refers to getting the source *from* google...I highly doubt there is any practical difference between 'linaro's' toolchain and 'googles' Will upload the 'official' build momentarily as the kernel just compiled i doubt the compile will sputter out now..
[Sprint Samsung Galaxy S III] bigwillyg:
Re: [ROM] [AOSP][LINARO] LIQUIDSMOOTH JellyBean [4.2.1] Beta 3.2 [d2spr] » Jan 24

Actually linaro's instructions say that the steps are the same except that you would use linaro's got instead of Google's when building the tool chain.

Like I said, if I'm wrong I will apologize.

Once someone installs the build an app like kernel tuner would show what the kernel was built on. Maybe someone could upload a screenshot of that.

Either way the ordinary users are now more informed so they won't fall for those that claim linaro and aren't.
[Sprint Samsung Galaxy S III] Parkourkid93:
Re: [ROM] [AOSP][LINARO] LIQUIDSMOOTH JellyBean [4.2.1] Beta 3.2 [d2spr] » Jan 24

I doubt it did, but I was hearing that also, I just find it strange that the messages are sending tho, because everyone I text is replying lol, even the its saying the message isn't sending, I will just wait till I get info on if sprint fixed the problem or whatever, thanks also :)
[Sprint Samsung Galaxy S III] nocoast:
The kernel was built using google's 4.7 GCC as per our cross compile rules, the entire ROM was built using the 'official linaro toolchain' in O3 fstrict using this command

mka TARGET_TOOLS_PREFIX=/home/nocoast/Downloads/android-toolchain-eabi/bin/arm-linux-androideabi- TARGET_PRODUCT=liquid_d2spr

(this command was used as per Linaro.org's instructions)

the android-toolchain-eabi is the untarred toolchain found here Im 100% positive if i set the cross compiler to use my toolchain in Downloads instead of prebuilt we'd get the same outcome...This is besides the point as we are ROM developers, not kernel devs and we highly reccomend flashing your favorite kernel of choice (often times compiled with the 'official' linaro toolchain anyways) Anywho the build is finished and for those who were wondering the file size doesnt appear to be all that different, feel free to give it a whirl and let me know if you notice any stability/speed differences... THE LINARO MOMENT YOU'VE ALL BEEN WAITING FOR CAN BE DOWNLOADED HERE
[Sprint Samsung Galaxy S III] dg4prez:
bigwillyg, please weigh in when you've investigated to your satisfaction. folks seem to trust your opinion and we want the air cleared.
[Sprint Samsung Galaxy S III] banccalif:
Re: [ROM] [AOSP][LINARO] LIQUIDSMOOTH JellyBean [4.2.1] Beta 3.2 [d2spr] » Jan 24

Yes we do
[Sprint Samsung Galaxy S III] GETCASHMONEY:
Re: [ROM] [AOSP][LINARO] LIQUIDSMOOTH JellyBean [4.2.1] Beta 3.2 [d2spr] » Jan 24

I keep hearing about the greatness of the anthrax kernel. Does that play nice with this ROM?
[Sprint Samsung Galaxy S III] bigwillyg:
Re: [ROM] [AOSP][LINARO] LIQUIDSMOOTH JellyBean [4.2.1] Beta 3.2 [d2spr] » Jan 24

Well, I'm not entirely convinced for a couple of reasons:

1) the build process was entirely too short, my kernel alone takes longer than that to build.

2) the size difference isn't like that of a linaro build. A fully optimized Rom or kernel grows substantially in size. A kernel grows almost to the point where it gets past the 14mb boot limit, the one room that I saw that was fully optimized to the point where it took the dev a couple of months to just clean out the errors was almost 200mb in size.

Let me find the correct flags that only work on linaro compilers and it can be tested like that. Also for it to be fully optimized you would need to go through every last makefile and android.mk file to remove the -fno-strict-aliasing flags since the local flags will over ride the global flag.

Trust me, it's complicated and I had a headache for days and I only did a kernel.

Oh also, you will need to change the /build files to point to the linaro tool chain as well.

Even though you encourage the users to utilize the kernel of their choice, it would make your Rom better overall if the kernel was also compiled using linaro.

In the end, your users will appreciate you more for that effort.
[Sprint Samsung Galaxy S III] nocoast:
1. I built on this setup os[Linux 3.7-trunk-amd64 x86_64] distro[Debian 7.0] cpu[8 x Intel(R) Core(TM) i7-3770K CPU @ 3.50Hzz (GenuieIIntel) @ 1.60GHz] mem[Physical: 31.4GB, 78.0% free] disk[Total: 225.2GB, 10.2% free] video[NVIDIA Corporation Hewlett Packard] ether[Intel Corporation 82579V Gigabit Network Connection] sound[HDA-Intel - HDA Intel PCH1: HDA-Intel - HDA NVidia] ....Compiles when i OC my 3770k can be as fast as 9 minutes, this one was on the slow side because i mka clobber'ed beforehand.

2. You dont see a size difference because Google's GCC 4.7 is for all intents and purposes the same, we slim our roms down very much so using a number of techniques so yes while although youd Expect an O3 ROM to be larger, we work very hard at making our otapackages slim, look at our source for more info on that

3. Trust me, I agree with you its complicated, Ive been making O3 linaro builds since ICS, if you dont believe me you can dig up rootzwiki threads to prove it...I might even have an OTA for the Gnex still lying around, and our ICS source (which used the 'real linaro toolchain') is all still there on our github for you to see...I spent a lot of time going through the measures of your experiment today, do understand that we HAVE patched almost every repository we use to compile with -O3, another thing you can see for yourself, the rest of the patched repositories are tracked upstream in our manifest...

PS I highly reccomend this hardware configuration for compiling source on /sysinfo didnt post the SSD i use which is a samsung 830 pro, which i highly reccomend.
[Sprint Samsung Galaxy S III] WindowsSucks:
Re: [ROM] [AOSP][LINARO] LIQUIDSMOOTH JellyBean [4.2.1] Beta 3.2 [d2spr] » Jan 24

;)

Sent from my SPH-L710 using Xparent Blue Tapatalk 2
[Sprint Samsung Galaxy S III] nocoast:
Thank you very much my man ;) That is indeed the latest release i downloaded and used for our compile.... I <3 Nerds :D
[Sprint Samsung Galaxy S III] WindowsSucks:
Re: [ROM] [AOSP][LINARO] LIQUIDSMOOTH JellyBean [4.2.1] Beta 3.2 [d2spr] » Jan 24

I wouldn't thank me yet. ;)

Sent from my SPH-L710 using Xparent Blue Tapatalk 2
[Sprint Samsung Galaxy S III] nocoast:
Well even in the other binary compare it shows were using gcc 4.7 my man...Im waiting to see whatever else you got up ur sleeve ;)
[Sprint Samsung Galaxy S III] bigwillyg:
Re: [ROM] [AOSP][LINARO] LIQUIDSMOOTH JellyBean [4.2.1] Beta 3.2 [d2spr] » Jan 24

In the screenshots above, your build from this morning is on the left and the previous build is on the right. This morning's build actually has linaro in there but the previous one doesn't. I must commend you, your Rom is definitely linaro compliant but not completely optimized.

Stick to the linaro tool chain, plus I can provide you with the cflags if you like that can further optimized your Rom in addition to the other stuff I mentioned in my previous post (i added to it before I saw your response).

So, no, your Rom wasn't previously being built on linaro but this morning's was.

You can remove linaro from your thread topic or make the switch, you're call.
[Sprint Samsung Galaxy S III] WindowsSucks:
Re: [ROM] [AOSP][LINARO] LIQUIDSMOOTH JellyBean [4.2.1] Beta 3.2 [d2spr] » Jan 24

+1

Sent from my SPH-L710 using Xparent Blue Tapatalk 2
[Sprint Samsung Galaxy S III] nocoast:
Google's GCC 4.7 IS linaro for all intents and purposes my brother. Standing by that claim. And We are aware of compiler optimizations. I have implemented a few boardflags/-CFLAGS myself on various devices... The ROM is compiled Fstrict O3 you are welcome to view our source if you dont believe...

Feel free to read more about the linaro/android upstream toolchain here... https://wiki.linaro.org/Platform/Android/UpstreamToolchain <You do see how the two are intertwined and how the 4.7 toolchain used @ google is a linaro derivative, and is maintained by the linaro devs? They even tell you to fetch 'their' toolchain from android.googlesource Im not sure how much more proof you need. The file size barely changed between the two compiles...Really i highly doubt the linaro toolchain holds any major differences or advantages over google's 4.7 gcc maintained by linaro
[Sprint Samsung Galaxy S III] GETCASHMONEY:
Re: [ROM] [AOSP][LINARO] LIQUIDSMOOTH JellyBean [4.2.1] Beta 3.2 [d2spr] » Jan 24

Can anyone answer my last question please? Sorry it got buried.
[Sprint Samsung Galaxy S III] bigwillyg:
Re: [ROM] [AOSP][LINARO] LIQUIDSMOOTH JellyBean [4.2.1] Beta 3.2 [d2spr] » Jan 24

Excellent question, in theory it should but toast once announced that upstream cm would specifically block it. Truly a shame, that is one fine piece kernel.

---------- Post added at 10:35 AM ---------- Previous post was at 10:33 AM ----------

Sorry but no, linaro is linaro and Google is Google. Google may have updated to gcc 4.7 but it's still not linaro. Again, I must commend you on the fact that your build compiled on linaro.
[Sprint Samsung Galaxy S III] nocoast:
From all ive read Googles gcc 4.7 contains all the same patches as linaro...that said I will be using the official linaro toolchain in the future on release builds just so we can avoid confusion...
[Sprint Samsung Galaxy S III] dg4prez:
So can we all agree that the use of "linaro O3" in our OP is legit, please?
[Sprint Samsung Galaxy S III] bigwillyg:
Re: [ROM] [AOSP][LINARO] LIQUIDSMOOTH JellyBean [4.2.1] Beta 3.2 [d2spr] » Jan 24

And with that I bid my adieu :)

Don't forget to grep your source for "-fno-strict-aliasing" so you can remove those flags.

---------- Post added at 10:53 AM ---------- Previous post was at 10:52 AM ----------

It will be now that he said he is going to use it.
[Sprint Samsung Galaxy S III] dg4prez:
[YOUTUBE]fQbRyay_ojY[/YOUTUBE]
[Sprint Samsung Galaxy S III] nocoast:
So that it compiles. Not all repositories are patched for ISO11 compile sadly so we do the best that we can. Our rom is a work in progress and we will be looking to O3ify it and fstrict it more with time...
[Sprint Samsung Galaxy S III] toxicthunder:
Wonderful discussion here. Thank you both :)
[Sprint Samsung Galaxy S III] banccalif:
Re: [ROM] [AOSP][LINARO] LIQUIDSMOOTH JellyBean [4.2.1] Beta 3.2 [d2spr] » Jan 24

Given the above statement, to a linaro noob like myself, does this mean the ROM in its previous state (yesterday's build) and/or current state (today's build) are in fact 100% linaro? I only ask for clarity, not to stir the pot
[Sprint Samsung Galaxy S III] bigwillyg:
Re: [ROM] [AOSP][LINARO] LIQUIDSMOOTH JellyBean [4.2.1] Beta 3.2 [d2spr] » Jan 24

The Rom is linaro compliant, this morning's build is linaro -O3 compiled but semi optimized. Once they can get rid of the flags and get it to compile that way it will be much more optimized. Again, if the OP wishes I can share the linaro specific cflags so they completely optimize it.
[Sprint Samsung Galaxy S III] nocoast:
not opposed to hearing tips my brutha
[Sprint Samsung Galaxy S III] thznutz87:
Re: [ROM] [AOSP][LINARO] LIQUIDSMOOTH JellyBean [4.2.1] Beta 3.2 [d2spr] » Jan 24

Take your ROM over to the anthrax forums. A lot more linaro help there. The devs over there are real devs, not just patching stuff together like a lot of "devs" here.
[Sprint Samsung Galaxy S III] bigwillyg:
Re: [ROM] [AOSP][LINARO] LIQUIDSMOOTH JellyBean [4.2.1] Beta 3.2 [d2spr] » Jan 24

What he said ^ would help you out a lot as well.
[Sprint Samsung Galaxy S III] dg4prez:
we're always open to ways to make the rom better for you guys. :good:
[Sprint Samsung Galaxy S III] nocoast:
are we not allowed to discuss compiler optimization here? Id prefer not to join another forum i do my best to stay away from them as much as possible as they ultimately distract me from working on the rom. Todays a release day so i have a lot of freetime. BigwillyG Im well aware that the more repos we can compile in fstrict the better...do you have any specific advice beyond go to another forum?
[Sprint Samsung Galaxy S III] bigwillyg:
Re: [ROM] [AOSP][LINARO] LIQUIDSMOOTH JellyBean [4.2.1] Beta 3.2 [d2spr] » Jan 24

The reason the other forum was mentioned is because there is a dev over there that got me going in linaro. I can definitely pass on ideas and what not but again, he taught me and everything he does is fully, 100% linaro optimized.
[Sprint Samsung Galaxy S III] nocoast:
Thats cool...you do realize linaro offers its own manifest that comes prepatched and ready to go for 'true linaro' building?
[Sprint Samsung Galaxy S III] Ascertion:
Re: [ROM] [AOSP][LINARO] LIQUIDSMOOTH JellyBean [4.2.1] Beta 3.2 [d2spr] » Jan 24

Small bug, when using volume rockers to go to next song while screen is off, it adjusts ringer volume slightly (I usually have my phone on vibrate but it turns vibrate off every time I switch tracks.)
[Sprint Samsung Galaxy S III] bigwillyg:
Re: [ROM] [AOSP][LINARO] LIQUIDSMOOTH JellyBean [4.2.1] Beta 3.2 [d2spr] » Jan 24

I do. But I'm more of a hand on, learn it from scratch kinda person.
[Sprint Samsung Galaxy S III] jayharper08:
Simple solution.........stay on anthrax forums. If XDA is not up to your standards, then no need to be here.

I'm getting really tired of getting reports about this thread, hearing about "so and so's kernels", and this whole Linaro thing. I've been as nice as possible, but there is only so much I'm going to allow.

It's not rocket science. If you do not feel like this rom is truly what it says it is, or you feel there are better builds somewhere else, then go there and keep the bickering out of here. Go do it there.
[Sprint Samsung Galaxy S III] nocoast:
same for me hence we didnt use their manifest
[Sprint Samsung Galaxy S III] psousa781:
No disrespect intended with this, but I am not seeing the problem with the most recent discussion. The end result seems to be devs working together to improve this ROM. If that isn't exactly what a development thread is for then I don't know what would be. And the mention of that forum is because a dev there who isn't allowed on XDA could help the dev of this ROM. If he goes there and gets some assistance, and in turn can offer a better ROM here, what is the problem?
[Sprint Samsung Galaxy S III] Circaflex:
the reason we bicker is because its falsely being advertised as one thing when it actually isnt, instead of trying to cover up this mess why dont we fix it? why are certain devs and threads allowed to blatantly lie to the user? Granted we came off strong, we want the truth not to keep having it hidden and covered up, which is happening a lot lately.
[Sprint Samsung Galaxy S III] jayharper08:
I understand what you guys are saying, I do believe me. I've been around a while. What it comes down to is what I posted in the SlimRom thread:

http://xdaforums.com/showpost.php?p=37064591&postcount=376

And it's not just what it being said, it is HOW it is being said. As I said in this post. This is what I'm saying and what I am trying to get across.
[Sprint Samsung Galaxy S III] KennyG123:
New development is awesome. However the negativity and bashing of XDA and devs in general will not be tolerated. It turns into childish bickering and no development is coming out of that. If people want to help then help. There is no need to waste everyone's time reading crap about whose lying and whether or not it is true linaro. Either work together constructively with a true desire to help or refrain from posting. Then there will be no bickering and we would not be getting reports on this thread. As a matter of fact if you guys want to build a pure linaro product together why not start a thread in the developers discussion area.

Thanks for understanding

Friendly Neighborhood Moderator
[Sprint Samsung Galaxy S III] Ninja25:
how do i get the google now bottom circle? i dont have it:(
[Sprint Samsung Galaxy S III] dg4prez:
turn on the nav bar.
[Sprint Samsung Galaxy S III] psousa781:
Just to clarify, is the discussion between nocoast and bigwillyg part of what you are looking to eliminate? I ask because while there seemed to be some tension at points between them, I think ultimately the goal was to help improve this ROM. And the mention of the other forum was also with the intent of helping nocoast in his development of this ROM, not advertising the other forum and whatever ROMs or kernels may be available there.

I may have missed some posts as well if the thread was cleaned up, so I apologize for any ignorance on my part. As an end user I just love to see guys that are way smarter than me hash stuff out for the good of everyone else. I know the linaro discussion seemed to drag on, but at its end it seems to have been for the better.
[Sprint Samsung Galaxy S III] bigwillyg:
Re: [ROM] [AOSP][LINARO] LIQUIDSMOOTH JellyBean [4.2.1] Beta 3.2 [d2spr] » Jan 24

No dev status here friend, don't think I have access to that area :) I can only speak for myself, the end result of my discussion with nocoast will result in his Rom being better. True others are coming off a tad abrasive but I don't see this thread getting out of hand. Our discussion is pretty much wrapped up.
[Sprint Samsung Galaxy S III] jayharper08:
Re: [ROM] [AOSP][LINARO] LIQUIDSMOOTH JellyBean [4.2.1] Beta 3.2 [d2spr] » Jan 24

OK. So let us all start over and fresh. Deal?

Like I said earlier. Respect is everything. You give it, you get it. Please keep that in mind and let's keep going forward with this project.

P.S. Let Anthrax be Anthrax. There's no need for me to see every other post about Chad and that site. This is XDA, not infected.

Let's get back to good times. :) :highfive:

--Jay-- Moderating from the Slimmed™ GSIII
[Sprint Samsung Galaxy S III] bigwillyg:
Re: [ROM] [AOSP][LINARO] LIQUIDSMOOTH JellyBean [4.2.1] Beta 3.2 [d2spr] » Jan 24

Nocoast, as soon as I get back to a pc I will look for the list of cflags for full linaro. It's a bigger beast but once you get to it, it will be worth it.
[Sprint Samsung Galaxy S III] sonwon:
+1

---------- Post added at 04:23 PM ---------- Previous post was at 04:21 PM ----------

I haven't heard any bickering, I respectfully say that I think you moderators are overreacting.
[Sprint Samsung Galaxy S III] jayharper08:
Re: [ROM] [AOSP][LINARO] LIQUIDSMOOTH JellyBean [4.2.1] Beta 3.2 [d2spr] » Jan 24

You also haven't seen everything that was posted. I respectfully disagree. ;)

Now can we get back on topic please.

--Jay-- Moderating from the Slimmed™ GSIII
[Sprint Samsung Galaxy S III] sonwon:
True so back on topic we go.
[Sprint Samsung Galaxy S III] Zor Omega:
Re: [ROM] [AOSP][LINARO] LIQUIDSMOOTH JellyBean [4.2.1] Beta 3.2 [d2spr] » Jan 24

So there's a kernel that it's optimized for this Rom that comes packaged in the Rom, right? Also how's the battery life compared to cm 10.1?
[Sprint Samsung Galaxy S III] ervman1:
Re: [ROM] [AOSP][LINARO] LIQUIDSMOOTH JellyBean [4.2.1] Beta 3.2 [d2spr] » Jan 24

Any update on wifi tethering? Someone a few pages back said it doesn't work but the op says tethering only works without encryption. Im really loving this ROM but I'll have to go back to 4.1.2 if tether doesn't work :(
[Sprint Samsung Galaxy S III] nocoast:
it works without encryption.
[Sprint Samsung Galaxy S III] NYCHitman1:
Re: [ROM] [AOSP][LINARO] LIQUIDSMOOTH JellyBean [4.2.1] Beta 3.2 [d2spr] » Jan 24

Anyone here in an LTE area that can comfirm it is working? Just passed by a spot that supposedly has it in NYC, but nothing clicked :(
[Sprint Samsung Galaxy S III] carhauler1969:
Re: [ROM] [AOSP][LINARO] LIQUIDSMOOTH JellyBean [4.2.1] Beta 3.2 [d2spr] » Jan 24

Was working from Fort Worth to Abilene TX this morning, and they just flipped the switch in San Gabriel CA a little bit ago.
[Sprint Samsung Galaxy S III] ervman1:
Re: [ROM] [AOSP][LINARO] LIQUIDSMOOTH JellyBean [4.2.1] Beta 3.2 [d2spr] » Jan 24

?? How so? WiFi tether? Settings used? Ive tried a lot of the settings if not all and I keep getting errors with starting and configuring ap
[Sprint Samsung Galaxy S III] gosueric:
Anyone else having issues with text messages? They come in through google voice but not through the regular text messaging app.

Tried re-flashing both with KToon kernel and the stock one and still nothing.
[Sprint Samsung Galaxy S III] EvgeniX:
Re: [ROM] [AOSP][LINARO] LIQUIDSMOOTH JellyBean [4.2.1] Beta 3.2 [d2spr] » Jan 24

Settings-More...-Tether..-Portable WiFi hotspot...
[Sprint Samsung Galaxy S III] ervman1:
Re: [ROM] [AOSP][LINARO] LIQUIDSMOOTH JellyBean [4.2.1] Beta 3.2 [d2spr] » Jan 24

Thanks but I've tried that already..my laptop connects but no data is transferred
[Sprint Samsung Galaxy S III] astarling10:
yes, LTE is working. I'm in Manhattan, Kansas.
[Sprint Samsung Galaxy S III] Custodian:
Re: [ROM] [AOSP][LINARO] LIQUIDSMOOTH JellyBean [4.2.1] Beta 3.2 [d2spr] » Jan 24

I love liquid ROM and would like to see it fully optimized. The more knowledge the devs have the better. I know coding takes alot of work and time ..can make you lazy as **** especially if you're doing this **** for free. As a blizzard entertainment Dev I understand the pressure.
[Sprint Samsung Galaxy S III] EvgeniX:
Re: [ROM] [AOSP][LINARO] LIQUIDSMOOTH JellyBean [4.2.1] Beta 3.2 [d2spr] » Jan 24

Do you have good sprint connection? Maybe it's sprint?
[Sprint Samsung Galaxy S III] thearch1tect:
Re: [ROM] [AOSP][LINARO] LIQUIDSMOOTH JellyBean [4.2.1] Beta 3.2 [d2spr] » Jan 24

Check the notification settings in your Google voice app and make sure its set to system messaging app

Sent from AOKP S3

-------------------------------------

Hit the "thanks" button if I helped you!
[Sprint Samsung Galaxy S III] bdsullivan:
Re: [ROM] [AOSP][LINARO] LIQUIDSMOOTH JellyBean [4.2.1] Beta 3.2 [d2spr] » Jan 24

Sent from my SPH-L710 using Xparent ICS Blue Tapatalk 2

I can confirm 4G is working perfectly.
[Sprint Samsung Galaxy S III] gosueric:
It's probably just me, flashed another ROM and still doing the same thing.

Same issue with/without Google Voice installed, and GV has been set to sync with the messaging app.

It's strange though, my mom and brother's phones are working fine :/
[Sprint Samsung Galaxy S III] thearch1tect:
Re: [ROM] [AOSP][LINARO] LIQUIDSMOOTH JellyBean [4.2.1] Beta 3.2 [d2spr] » Jan 24

I'm having similar issues with my as well. The settings just won't stick for some reason. Did you go to your google voice account on a computer > settings > and uncheck the box for receive texts on this phone?

Edit: so I uncheck the box on the computer go into Google voice app on the phone and the settings revert back to "receive texts via Google voice app" and refreshing the browser shows the box checked again. :banghead:

Sent from AOKP S3

-------------------------------------

Hit the "thanks" button if I helped you!
[Sprint Samsung Galaxy S III] bigwillyg:
Re: [ROM] [AOSP][LINARO] LIQUIDSMOOTH JellyBean [4.2.1] Beta 3.2 [d2spr] » Jan 24

Nocoast, these screenshots have the cflags you need that only work on linaro
[Sprint Samsung Galaxy S III] ihugyou:
Re: [ROM] [AOSP][LINARO] LIQUIDSMOOTH JellyBean [4.2.1] Beta 3.2 [d2spr] » Jan 24

4g is working in Charlotte nc!! Even in non 4g areas seems the 3g is faster. Oh and how do I take screenies with this ROM..without downloading an app?
[Sprint Samsung Galaxy S III] xblackvalorx:
Re: [ROM] [AOSP][LINARO] LIQUIDSMOOTH JellyBean [4.2.1] Beta 3.2 [d2spr] » Jan 24

Enable screenshot in power options
[Sprint Samsung Galaxy S III] EvgeniX:
Re: [ROM] [AOSP][LINARO] LIQUIDSMOOTH JellyBean [4.2.1] Beta 3.2 [d2spr] » Jan 24

Does this ROM play nice with ktoonsez kernel?
[Sprint Samsung Galaxy S III] 88EVGAFTW:
Got a question. I changed DPI to 260 and noticed that now when I get an incoming call, the white Orb you move to answer it is off center and looks weird. Is there something we can edit to move it back to center?
[Sprint Samsung Galaxy S III] dg4prez:
sure does.