yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xXFl4sh:
[MENTION=4474827]fenixus[/MENTION] Can you replace AudioFx with Viper4Android?

Other than that, great ROM, no problems so far.

EDIT: I am getting a battery drain after installing V4A. Unfortunately, I have to go back to LS 3.2. I cant live w/o V4A

EDIT 2: I am back on this rom. I was getting battery drain on 3.2 because of Google update services. I installed V4A again and no battery drain. I even installed the high quality driver.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] WHib96:
Bug report: after adding a screenshot option to my power menu, the settings app crashed and I can't get back into the power menu options because it just crashes immediately when I tab on "power menu".

Are there no options in liquid smooth to change the lock screen shortcuts? The only lock screen options I'm given are an on off for weather and an icon color changer.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fenixus:
Sorry, we do not support V4A anymore.

Mind waiting a day or two? I will be posting fresh d2att build made from rebased sources. Mind it's a beta still, but it is very stable and mostly functional. There will be 2 builds for testers (at your own risk, don't forget about backups and a clean flash), one with CM Theme engine and another with Layers/RRO engine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
What's the reason? Just curious...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fenixus:
SElinux permission problem long ago, we dropped it before LP 5.1.0 was released.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
I could PM you a flashable zip a that resolves that problem if you like.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fenixus:
here's the fresh 8/18 test build of d2att (rebased sources) with Layers/RRO engine:

https://www.androidfilehost.com/?fid=24052804347796623
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tdotdot:
Any way you can add d2tmo that the updater script? I'd do it myself but my phone isn't being recognized by my computer for whatever reason.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fenixus:
why not use the ROM built for d2tmo?

check the other thread:

http://xdaforums.com/galaxy-s3-t-mobile/orig-development/rom-samsung-galaxy-s3-liquidsmooth-t3016555
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tdotdot:
Did not realize you updated that thread too, thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fenixus:
yes, I did, d2tmo is my phone so it gets all candy first :)

note there is 2 builds now, one is with CM Theme engine other is with Layers/RRO engine, switching over even when they are near complete in age still requires a clean flash usually. For now all builds (even same family updated builds) may require clean flash at this stage.

also, for d2att there will be alternative build with CM theme engine, coming later or tomorrow, there is some problem with it right now, but it should follow soon.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] WHib96:
What theme engine was being used before?

Also, I recently read that the cm12.1 d2att builds got a thermal driver update to make the phone run cooler. On every 5.1.1 rom I've run, including this one, the phone gets a bit warmer than I would like. For this reason I'd like to ask if that was implemented (if it's possible) into the newest build here?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fenixus:
Name "Theme engine" always implies a CM based Theme Engine manager, whatever they have as it evolves every day.

SykoPath Layers (or RRO) is a different kind of customization engine that we used a bit in past before switching back to themes.

For now I post builds covering both until we reach the milestone on 5.1

not sure about any thermal driver for d2att, may look into CM-12.1 device tree and see what they changed.

EDIT:

I see no commits in CM-12.1 branch device repos related to anything like thermal anything anywhere, neither in TheMuppets vendor blobs for d2.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fenixus:
a fresh d2att test build 8/19 (rebased sources) with CM Theme engine is coming soon

https://www.androidfilehost.com/?fid=24052804347797375
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fenixus:
looks like V4A might be coming back, I saw some commits related to it, at least in CM Theme engine branch of new LS :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
Awesome! Personally, I can't live without V4A... LoL
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] WHib96:
Is that so? Hm. I had not checked it myself, but read someone say on the cm12.1 with a twist thread that there was a thermal driver update in the August builds. I had gotten my hopes up that my phone wouldn't get as hot lol

Are there any advantages to using one theme/customization engine over the other? I'll flash one but am not sure which to try out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tdotdot:
I don't think it was a driver. It's mentioned here: http://xdaforums.com/galaxy-s3-att/...ial-cm12-1-nightlies-sgh-i747-t3100439/page71
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fenixus:
if I am following correctly, looks like that thermal parameter change was done in inline kernel that CM uses. we have a different one, it was updated not long ago, but it was like 3 weeks already I believe.We use Deathly Kernel, updated by our core dev Sean.

First post should list kernel github link, you can see the commit history in there.

I believe those are the kernel changes for mentioned thermal update on d2, that CM implemented, they come from franco kernel maker.

https://github.com/CyanogenMod/andr...mmit/3ee607e8e10983803288cd2cf66c3236ef5d6c3c

https://github.com/CyanogenMod/andr...mmit/79aea1af73a3c42bdd51fd6214798176c2e5addd

Let me see if I can update Deathly kernel in my local repo and compile some fresh test build ... will let you know later.

EDIT:

Ok, just checked, we already had it in Deathly when ROM was compiled. Those listed above changes are included since 17 days.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MatAccord:
Hi there,

Im a fan of LS for a while and Ive just flashed the 8/19.

It runs smooth and fast, just like the others but my only wish is to get the DPI back to 320 instead of 220 (default on this one).

The max setting for the DPI on this build is 260, which is still too small for me.

Keep up the good work because it's still my daily by this day!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tdotdot:
Change ro. sf.lcd_density=320 in build.prop. Agreed that the options are way too small.

[MENTION=4474827]fenixus[/MENTION] I updated my twrp and tried again but same result with cpu usage sticking to 100. Seems like I'm stuck with CM builds for now, Deathly just isn't working right on my phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tanker Bob:
I made a nandroid backup with TWRP, then flashed the 8/19 att test build with the CM theme engine. Upon reboot, the boot screen consisted of four colored dots moving around, but my phone never got beyond that point. I had to pull the battery after about 10 minutes. I tried to boot the 8/19 build again with the same result, then tried reflashing it but nothing changed. I restored my backup with no problem. Not sure why this build would not run, as all previous builds have run fine. I do run xposed framework for 5.1 version 68, which has never been a problem before.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tdotdot:
Did you wipe?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tanker Bob:
No.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tdotdot:
You should. After flashing the image, on twrp it should give you an option of wiping or reboot. Wipe first (not a factory reset) and then reboot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tanker Bob:
You mean delete the cache and dalvik cache? Yes, I always do that for updates. Did it both times that I tried to flash it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] WHib96:
Okay, thank you.

Just out of curiosity, what exactly was changed and how does it affect how hot the phone gets? Not fully understanding the change and what it did.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fenixus:
Tanker Bob, not sure what's up then, if you use TWRP 2.8.7.0 and do a factory reset, then it's pretty good, then you flash the ROM and gapps and you have a clean flash ... maybe try a different kernel if you think that Deathly doesn't like your particular phone? How long did you wait to boot after clean flashing? It can take a few good minutes, and yes the default boot animation is the one from AOSP for now (same as Google Nexus has).

as per dpi settings, yeah for now you'd need to change build props as mentioned several posts above to go back to what it was before, I personally like higher density and it feels ok to me, but I understand that it could be a problem for some people.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Chinmonkie:
Hey Team Liquid! I just wanted to say thanks for keeping the project alive (Y), Even though I now use a Note 3 my mom has been using my SIII for 3 years now. Its because of you her phone is still going strong. She really proud of her SIII saying that it outperforms her friends S5's because its so clean and optimized.

We did have a slight bump on the previous nightly where it would bootloop, but a simple 3XWipe, 3X Reset,1 Reinstall fixed everything. Way to go guys :) hope to see my donation will keep the d2att project alive (Y)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DeadlyByNite:
I don't know if anyone else maybe having this problem, but my notifications sometimes don't include the icon as shown in this screen shot:

I have had this problem with a few other 5.1.1 roms. I have also done a clean flash, wiping all data and cache. The only thing is that my cache partition was f2fs at the time I flashed the rom, and I thought maybe f2fs cache partition was maybe the problem, so yesterday I changed it to ext4. Also I wiped Cache/Dalvik Cache before I flashed, but not directly after, however I did wipe yesterday before and after formating cache partition to ext4.

Edit: To be more specific, the icon I circled should look like this:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MatAccord:
[MENTION=5013359]tdotdot[/MENTION] [MENTION=4474827]fenixus[/MENTION]

Thanks for the quick reply, guys!

I might sound dumb as **** asking this but...I need to learn to go to the build.prop. you both talk about..?

Can i have a quick "how to"? If isn't too much to ask? ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tdotdot:
Download "kernel aduitor", it'll have a build.prop section in there.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fenixus:
hehe, no worries buddy. there's always a first time in everything, we all have been there lol

I find it easiest if you use an app like Build.Prop Editor (requires root of course), then in it find the line you want to change, make changes and hit Save button (looks like a check mark), then restart phone and there you go.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MatAccord:
[MENTION=4474827]fenixus[/MENTION] [MENTION=5013359]tdotdot[/MENTION]

Thanks a lot guys! It worked on the 1st try! ?

I've worked my way through the kernel audiotor through deathly kernel! Had to click on the performance card through the system settings to find the build.prop.

It was so easy to find...but now, I know where to go! Thanks again! ☺☺
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fenixus:
will be posting new d2att test builds of both flavors soon, massive improvements with some of latest commits (confirmed on d2tmo), in short expect smoother experience, faster UI response and apparently a longer battery life as I can see.

edit:

8/22 d2att test builds:

themes: https://www.androidfilehost.com/?fid=24052804347799292

layers: https://www.androidfilehost.com/?fid=24052804347799385

EDIT2:

applying custom themes on cm-based branch seems to cause a crash loop in SystemUI component on some phones ... mine included. that looks like only known issue so far.

ROM with layers engine should be OK.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Rickymills:
Just installed the theme version and the dpi is only 260 max.. can 320 be added it is super fine!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tanker Bob:
Hi fenixus - I am using TWRP 2.8.7.0, but did not do a factory reset. I've never had to do one before when updating. Is there something different about this one? Also, the current default is 320 dpi as you know. Is there a way to set that in the 8/17 update? If not, I'd probably like to hold off until 320 dpi is available. Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tdotdot:
Can set it using ro.sf.lcd_density in build.prop.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tanker Bob:
Thanks! I just tried using that with the 7/13 build to try out 240. Definitely too small for my eyes. I believe that I'll stick to 320 for now. I don't have time to factory reset until later this week, then try the 8/17 build. Even with my backups, it takes a few days to get everything back to normal.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Rickymills:
Where can i download August 17th update?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MatAccord:
Been on 2 days straight with the 8/22 LAYERS build.

Can confirmed a better battery life (got 2 hours more with it) and a faster ui response! Best build up to date ?

I got to raise a flag about a weird bug on some older build but this one might have fixed it.

When Im in conference call with 2 of my pals on the line and I am the one who held the conference, if I have to take another call, the conference straight on hold; which at this point, everything is normal.

However, if the conf. goes on hold, the other 2 can't hear or talk to each others, which is kinda annoying.

That happened until the 8/22 went out, which the recent one don't have it.

8/18 and older has it.

Hope I gave enough to locate the issue. If there is more question concerning this one, Ill be able to bring out a catlog out of it!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zetsui:
Kind of dissapointed in this ROM. Lots of missing functionality, weird battery/sim problems that go away if I try some of the other Kitkat roms. Im a long time tester and contributor to some of the galaxy s3 and older bravo projects. It made me give up my s3 for a newer s5 active
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fenixus:
new test builds for d2att posted:

cmte: https://www.androidfilehost.com/?fid=24052804347803881

layers: https://www.androidfilehost.com/?fid=24052804347803748
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tanker Bob:
I loaded the 8/29 cmte build after a factory wipe. It loaded fine, and generally runs well. I found a few issues so far.

First, with Developer options enabled, and the Power menu set to show the Reboot menu, and Advanced reboot set, I still don't get the option to boot into recovery mode in the Power menu. I have to use the button combination to get into recovery.

I also had Setting crash once when entering a sub screen, but cannot remember where it was. Hopefully I'll find it tomorrow.

Nice job, fenixus. Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fenixus:
weird, I have the developer options enabled always and can normally reboot to recovery via menu ... you on latest TWRP recovery?

Settings crashes on About - LS Stats screen ... as it always was lol, let me know if you find others screens so I can double check.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Rickymills:
Hi Fenixus,, i had the 8/22 but had to delete it due to the dpi...does this build have 320dpi available

if not could you assist me on how to change or add it.

thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tanker Bob:
I'm using TWRP 2.8.7.0, which I believe is the latest. I've tried resetting and even powering off and back on, but still the same. I will play more with it today.

I'll poke around today to see if I can find the offending sub screen.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tdotdot:
The latest build has 320 as one of the options, yes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tanker Bob:
Disregard the power menu issue. I went back to Developer options, turned off the additional power menu items, exited, want back and reenabled them. The power menu works fine now. Probably a stray neutrino earlier. Sorry for the misdirect.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fenixus:
Yeah, must have been. Similar behavior I can observe on Volume Rocker wake toggle by default in off position, I need to toggle it back and forth to work right (stay off in my case) the first time after clean flash :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Rickymills:
My phone feel super smooth and fast!

love it.. any kernel tweaks for better battery life.. iam all about the battery less performance
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gvsukids:
Could these be fixed by installing new nj2 modem?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tanker Bob:
I have been running the 8/29 build since Saturday and haven't encountered any significant issues. The lock screen seems to have lost the ability to input a location for weather or display calendar events. I also haven't found a way to customize the quick settings panel pulled down from the status bar. Most of the important stuff is there, but I had more quick setting elements on the earlier builds.

The nasty bug that previously crashed the Privacy Guard Advanced screen is fixed. Yea!!!

I have been running at 260 dpi, the max offered in 8/29, and like that pretty well. I probably won't bump up to 320 in build.prop at this point.

Overall very nice job on this build! I haven't seen any lagging whatsoever. I know that you almost always lose things in code rebaselining until you rebuild the customizations for the new base, and look forward to regaining some of the earlier functionality.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fenixus:
next build will have DPI up to 320, that is merged and working on my current test build (wasn't posted publicly).

Still waiting for a fellow dev to help me out with cm theme engine crashing on d2 builds, other than that and some missing stuff like LS boot animation (for now we have Nexus boot ani), Quick Settings and a few other non-critical things this ROM is very stable and performs really well. With LS boot ani and theme engine fixed we will be going back to official nightly releases.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Rickymills:
Thanks for the update.. question can you dirty flash or it must be clean?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fenixus:
dirty flashing should be OK if your former ROM was a build from August.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Rickymills:
Yes it is..thanks again
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fenixus:
we are still in testing stage on rebased ROM, more or less because we don't have yet the new boot animation (you will see AOSP Nexus boot animation), some features are missing from ROM (e.g. Quick Settings tiles) and the Default theme on cmte is SlimRoms :)

Other than that all looks good!Post here if you find some problems, if they can be replicated by somebody else we will look into it.

new d2att 9/4 test builds posted:

*cmte: https://www.androidfilehost.com/?fid=24052804347808309

layers: https://www.androidfilehost.com/?fid=24052804347808328

* Some themes from Google Play seem to be based on broken code and may cause crash loop of the SystemUI, one example family of such that we identified are Deep Darkness themes by moelle, they seem either broken or incompatible with our ROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kenetix:
I tried two themes. Both messed it up. The new S6 theme, and the rocket theme. I guess i will hold off on themes for a while..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fenixus:
yeah, I can understand, was holding off myself with using themes for a while while testing this rom daily. till now we are not sure yet what the problem is, but some themes screw up rom stability entirely, mind I mean some not all.

For now I tested daily those 2 themes with zero trouble, so it seems like maybe recently updated themes have some framework commits that we are missing?

https://play.google.com/store/apps/details?id=com.resurrectionremix.pitchblack&hl=en

https://play.google.com/store/apps/details?id=it.antaresone.darksidetheme&hl=en

do you mind linking the themes you tested faulty on our rom, so we can see? unless you want to post the logcat yourself ...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kenetix:
https://play.google.com/store/apps/details?id=com.wsdeveloper.galaxy

https://www.dropbox.com/s/mvcva46ew4tjsoh/Rocket 4.4.4.apk?dl=0

No logcat because i can't keep it running with a theme error.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fenixus:
ok thanks will test it after backup tomorrow.

BTW, you can use ADB minimal environment to pull logcat from PC over USB even when it's crashing ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kenetix:
Thanks. Did not know that. BTW, the rocket theme rocks. Try it out. And thanks for the hard work. Other than the theme thing, it is a sweet rom.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fenixus:
Thank you, lol I love this ROM myself, trying to figure out what we are missing, but looks like core devs need to pull a few of CM theme engine commits that we don't have otherwise it will be a risky lottery at something as simple as applying a theme from google play ....

S6 theme crashes my phone too.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tanker Bob:
I installed the 9/4 build last night over the 8/29 build with no problems. After some trial and error, I settled on 260 dpi for the display. Most everything works fine.

Like 8/29, one has to have some location service enabled to get weather on the lock screen and Quick Settings. The older builds allowed the user to set a manual location, which I prefer. The ad blocker doesn't seem to work in the 8/29 and 9/4 builds. It downloads the data files and creates a hosts.alt file, but doesn't overwrite the original hosts file. Ads still appear in some apps.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tanker Bob:
I installed AdAway and the ads are now gone. AdAway changed the hosts file itself w/o creating a hosts.alt file. There's definitely something not working in the 8/29 and 9/4 builds as far as the built-in ad blocking is concerned.

Otherwise, the new ROM seems to be working great. Haven't played with themes. I used the Space Theme in an earlier version, and the icons and background apparently survived through Nova Launcher Prime. Don't want to push my luck.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VanThePimpMan:
Been using this rom for quite a while and have had relatively great success, save for really bad battery drain on certain builds, other than that I enjoy the feel of the rom immensely. Right now I am having google search box completely kill my battery on the 8/22 build, I was getting ~20%/hr battery loss and BetterBatteryStats showed the google search box process had been continuously running.

I am also completely unable to try out the 8/28 build to see if it was an issue with that build because I get "error executing updater binary"

Full error in recovery is

"ApplyParsedPerms: removexattr of /temp/install/bin/otasigcheck.sh to 0 failed: operation not supported on transport endpoint

set_metadata_recursive: some changed failed"

I have never had this error before when updating to any other version.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tdotdot:
Remove the google search box from the home screen.

---------- Post added at 05:29 PM ---------- Previous post was at 05:29 PM ----------

Also, I too got an error message similar to that on the d2tmo layers build.