yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] TheBr0ken:
the lockscreen notifications were re-written this morning. Todays build is up on our server. here's the link

http://www.drdevs.com/devs/?dir=teamliquid/official/Test
[Verizon Samsung Galaxy S III] jaguarpaw:
got it up and running without the force closing. i have gotten a random reboot twice. and unlocking the device is a lil hit or miss.. sometimes i unlock it and only the hardware keys light up but no lockscreen. i hit it again and all is normal. strange.
[Verizon Samsung Galaxy S III] jlokos:
I'm having the same issues.
[Verizon Samsung Galaxy S III] hallstevenson:
No FCs here but am seeing frequent reboots. Since I'm using a non-stock kernel, I wasn't going to report that though... I'm seeing the same unlocking issues too.
[Verizon Samsung Galaxy S III] sk2:
Can someone please post a link for the latest gapps for the test builds. Thanks

---------- Post added at 07:46 PM ---------- Previous post was at 07:41 PM ----------

Never mind I found them.

http://invisiblek.org/gapps/

Thanks
[Verizon Samsung Galaxy S III] hallstevenson:
Gapps aren't linked to ROMs or nightly updates. Any KK Gapps will work. Some just start out with newer versions than others (but will prompt you to update them in no time through the Play Store).
[Verizon Samsung Galaxy S III] motrinHD:
hello all, I'm on 2.37. can't seem to find the option to turn off home button wakes device. I had found on 2.9 which I had been running
[Verizon Samsung Galaxy S III] sweeds:
Congrats on the working KitKat version.

Is there a separate thread on Liquid smooth KK? I'm interested in seeing a changelog and poss bug list before upgrading from 2.37
[Verizon Samsung Galaxy S III] hallstevenson:
LS has acknowledged the "issues" with the d2vzw build and it's (been presumably fixed) being re-built and uploaded.
[Verizon Samsung Galaxy S III] beepea206:
They really need a Gerrit or at the very least, to publish changelogs on their website. I'm sure I'm not the only one that won't flash their 4.4 build until they get the charge/screen issue resolved and there's really no way for us to know that it is...
[Verizon Samsung Galaxy S III] jlokos:
LS had 2 builds yesterday, Beta 1 and Beta 2. Apparently both had issues. I understand it has been fixed and a new build will be forthcoming. here is the most recent changelog/feature list https://plus.google.com/u/0/102153960718796996774/posts/CErFmBEd4KS.
[Verizon Samsung Galaxy S III] beepea206:
Ugh. I can't view G+ at work and rarely go there. Guess that's better than posting that stuff on FB and expecting us to go there....

*Edit* BTW, that's not a changelog... that's a statement of stuff to be changed in 'beta builds to come out soon'. That kind of vague info is useless when a user has a 'dealbreaker' issue and can't know if/when it's resolved. I really want to get back on LS, but unless they start posting actual commits/changelogs somewhere (anywhere really), I'm out.
[Verizon Samsung Galaxy S III] hallstevenson:
More development teams are moving there. I don't blame them for having a single "support" site. Plus, they can "mod" their own page there.

As for the "changelog", they have a gerrit or github page, don't they ?
[Verizon Samsung Galaxy S III] RBarnett09:
For whatever reason, this option is no longer available in 2.37, but I can help you fix it because this option was vital to me and I can confirm that it works.

Open Root Browser and follow these steps.

1. Navigate to: system/usr/keylayout

2. Scroll down to: sec_keys.kl

3. Press until menu pops up and select to open in a Text Editor

4. Locate line: key 172 HOME WAKE

5. Tap behind the word WAKE and delete it so until you see: key 172 HOME

6. Save and exit

7. Reboot your phone

The home button should not wake the device anymore.
[Verizon Samsung Galaxy S III] jlokos:
Yep: https://github.com/LiquidSmooth
[Verizon Samsung Galaxy S III] motrinHD:
thank you very much!! It worked, and was quite easy. thanks again!
[Verizon Samsung Galaxy S III] hallstevenson:
Yeap, I had found that after I posted the above.... Nothing specific to the d2vzw has been updated in over a month though. I don't know how the build process works, but I'm presuming it pulls from android_vendor_liquid, android_packages_apps_Settings, android_frameworks_base, and so on though and that's where the "master" changes come from.
[Verizon Samsung Galaxy S III] jlokos:
By the way, new build is out. So far no reboots, lockscreen or screen/charge issues.
[Verizon Samsung Galaxy S III] beepea206:
Yea, they have a github (no Gerrit from what I can find), but frankly, I don't have time to sift through the branches to see changes (which is why Gerrit was created). Not to mention a git is for developers, not for average people... how is the average person supposed to know whether or not to try the newest build with a cryptic 'changelog' like their G+ and no centralized portal of changes? I don't mean to stir the pot here, but I used LS exclusively and would like to do so again... but with the issues our device (and the rom in general, it seems) faces, I need a centralized point to find the data telling me when it's time to give it another go.
[Verizon Samsung Galaxy S III] twistedillutions:
I just flashed SK last night and a update is available for LS.. Ill play with LK lil longer before coming back. Can someone confirm wen charging the screen/fone won't go bonkers on the new nightly? I had that problem and someone else too.
[Verizon Samsung Galaxy S III] tihsllub:
Where is LS doing nightlies?
[Verizon Samsung Galaxy S III] hallstevenson:
They don't do nightlies. They do "every once in a while" :D
[Verizon Samsung Galaxy S III] tihsllub:
Yeah I thought so. I'm still running 2.9 I'm probably gonna check out carbon. They are all over the 4.4 ROM.
[Verizon Samsung Galaxy S III] hallstevenson:
LS just put an update for this phone today
[Verizon Samsung Galaxy S III] annoyingduck:
Where are they? The original link is getting a 404 error.
[Verizon Samsung Galaxy S III] kentedman:
http://www.drdevs.com/devs/teamliquid/official/Beta2/
[Verizon Samsung Galaxy S III] annoyingduck:
Thanks....

Anyone know if there is a build.prop change that'll get rid of the permanent power widget in the notification drawer? I really hate that.
[Verizon Samsung Galaxy S III] tihsllub:
Anybody know what is going on with the LS team? I remember when their was more input and nightlies along with builds. It bums me out. I miss the quality.

Sent from my.......
[Verizon Samsung Galaxy S III] J913B:
Just installed the nightly for 4.4. Only issue I have so far is going to settings and hitting Volume. It force closes.
[Verizon Samsung Galaxy S III] Wh1t3Rose:
I think you miss the quantity not the quality. The quality is fine.
[Verizon Samsung Galaxy S III] hallstevenson:
Settings > Volume ? I presume you mean Settings > Sound.... Works fine here and I've dirty flashed from the official 12/28 build >> Gideon's 1/5 build >> official 1/7 build >> official 1/8 build.

---------- Post added at 09:16 AM ---------- Previous post was at 09:14 AM ----------

No notification screen power widget here. It was on older builds (maybe 12/28 and up to Gideon's 1/5 build), but not here on 1/8 build.

---------- Post added at 09:19 AM ---------- Previous post was at 09:16 AM ----------

Nightlies and quality don't always go hand-in-hand.
[Verizon Samsung Galaxy S III] tihsllub:
I'm referring to quality in the fact that I was running their 4.1.2 job beta as a daily driver. And it was amazing. It was better than the stock ICS ROM that shipped from verizon. Issues were resolved relatively quickly and their was proper cross communication between users and developers through this forum. But now it seems that its generally users helping users or users going to other forums and other admins and devs walking us through.
[Verizon Samsung Galaxy S III] hallstevenson:
I've seen "LiquidSmooth" and other developers on their team responding and commenting plenty of times.
[Verizon Samsung Galaxy S III] Tallica21:
Getting the exact same issue with Beta 2, using TWRP 2.6.3.0. What do you mean renamed the theme for TWRP? I'm using the stock theme

Although I haven't dirty flashed. This is the 1st 4.4. Rom I've tried
[Verizon Samsung Galaxy S III] jlokos:
The 1/8 build solved the screen/charge and reboot issues for me.
[Verizon Samsung Galaxy S III] jaguarpaw:
+1. running the 1/8 build since last night. no reboots. no lock screen issues and the screen wigout while charging isssue seems to be resolve (altho i didnt really do to much testing).

Thanks again to the dev and all of you for your help.
[Verizon Samsung Galaxy S III] Tallica21:
Just tried flashing CM 11. Same error. Do you need Clockwork to flash 4.4 or something?
[Verizon Samsung Galaxy S III] hallstevenson:
I'm using TWRP 2.6.3.X (X = something other than 'zero', maybe "1").

As I said in that post, rebooting recovery and trying it a 2nd time worked fine....

---------- Post added at 12:23 PM ---------- Previous post was at 12:22 PM ----------

Yeap, seems much better. I did have one random reboot (that I saw happen) and it was when I was running Play Store. Seems to be the only instance, so I ain't losing sleep over it !
[Verizon Samsung Galaxy S III] Tallica21:
Just tried again.

From working 4.3

Reboot recovery, factory reset, flashed Beta 2, failed, reboot recovery, flashed Beta 2, failed, reboot recovery, flashed Beta 2, failed. WTF!?
[Verizon Samsung Galaxy S III] Relentless D:
You should quote the person you are replying to so ppl know what you are talking about.
[Verizon Samsung Galaxy S III] annoyingduck:
In twrp, be sure system is unchecked under "mount"... Some wipe/restore actions cause this to get checked sometimes. With it on, all rom zips will fail...
[Verizon Samsung Galaxy S III] Wh1t3Rose:
Make sure you have the latest recovery. Use ROM installer from the play store to check recovery version and update
[Verizon Samsung Galaxy S III] kentedman:
You need TWRP 2.6.3.1 to flash any KitKat ROM.
[Verizon Samsung Galaxy S III] Tallica21:
I realized that after updating my recovery, then it flashed fine. Thank you.
[Verizon Samsung Galaxy S III] drewmey:
I could be missing something here. I'm still on 2.8 and I'm wondering if there is a way to change the color of the wifi and data symbols in the status bar. I am searching all over the settings and can't find it. I've got the clock and battery color changed. Any help would be great. Thanks.

Sent from my Nexus 7
[Verizon Samsung Galaxy S III] twistedillutions:
Install xpose framework and try xblast module it work for me
[Verizon Samsung Galaxy S III] RBarnett09:
This guy is on 2.37.

Will be patiently awaiting an official 4.4 release.
[Verizon Samsung Galaxy S III] cinco312:
Flashed the 1/8 build last night and I wasn't getting any data. Changed some data settings. rebooted and still "unknown" phone number, meid, etc...Tried flashing it again and still the same issue. I went back to the 12/28 build and all is normal.
[Verizon Samsung Galaxy S III] J913B:
Settings > Sound > Volumes gives me a FC
[Verizon Samsung Galaxy S III] pendata:
1/8 build with BMS kernel is pretty much flawless...
[Verizon Samsung Galaxy S III] cinco312:
Did you flash during when flashing the ROM? or after first boot?
[Verizon Samsung Galaxy S III] pendata:
You mean flashing the kernel? I flashed it after the first boot.
[Verizon Samsung Galaxy S III] yamaha_wins:
Can I dirty flash the beta 2 over pa KitKat version?
[Verizon Samsung Galaxy S III] hallstevenson:
Sure you can.... Is it advisable going from one ROM (design) to another ? Not really. Can't hurt anything though.
[Verizon Samsung Galaxy S III] beepea206:
Not necessarily. PA is CM-based, Liquid is AOSP-based, so there are framework differences. You can dirty flash, but be prepared to go back into recovery to wipe data when something goes wonky or you get some force-closes. You'll probably be fine, but it's not as certain as if you were to flash a CM/CM or AOSP/AOSP rom dirty.
[Verizon Samsung Galaxy S III] jaguarpaw:
1/8 build still running great. you guys having an issue using the swipe function on the stock keyboard? freezes mine up for like 15 seconds
[Verizon Samsung Galaxy S III] hallstevenson:
Sorry, I was being a bit of a smart-ass in my response. I'd like to think that people flashing custom ROMs know that a) clean / full wipes are always preferred, b) flashing from an older build of a ROM to a newer version is possible to dirty flash, but not certain to be the ideal situation, and c) going from ROM "x" to ROM "y" 99% of the time requires a full wipe.

By "can't hurt anything", I meant his phone ain't gonna blow up ! :D It might run like crap, with constant FCs, etc, etc, but it will "work".
[Verizon Samsung Galaxy S III] beepea206:
lol wait.... you mean if I dirty flash a rom, G-d doesn't kill a kitten? Well then... that changes everything. :D
[Verizon Samsung Galaxy S III] hallstevenson:
I dirty flash all the time*. I don't give recommendations to others that they do it though - that's their call. Also, if I dirty flash, I will rarely ever report issues without first wiping clean and trying to replicate it. If I do report a problem, it's usually something like, "yeap, I am having the same issue" and I will include the fact that I dirty flashed.

* I don't do this going from PAC to LS or Omni to (pure) CM though. I've been skeptical of "devs" in the past who insist that you must wipe clean when going from a build they put out a week ago to one just released. Often, this involved ported ROMs and the dev really didn't know what changed and has to take the safe route. Other devs I've seen confidently say it was okay to dirty flash going from builds that they release a long time apart. Why ? Because they know exactly what they changed.
[Verizon Samsung Galaxy S III] beepea206:
You need twrp 2.6.3.1 for 4.4 roms to flash.

---------- Post added at 12:22 PM ---------- Previous post was at 12:20 PM ----------

Anyone on beta 2 that was posted last night? I'll guinea pig it if needed...
[Verizon Samsung Galaxy S III] pendata:
Yup. Pretty stable.
[Verizon Samsung Galaxy S III] hallstevenson:
I've been running it since it was released. If you haven't already installed it, I'd hold off. They said a 2.1 build is on the way soon. The d2att, d2spr, and others have already been built and uploaded. They also mentioned a toolchain problem affecting many phones and if your phone has a beta 2 build already, it will get a 2.1 build first (which is good for the d2vzw).
[Verizon Samsung Galaxy S III] beepea206:
Nice one, thx. I was just about to flash it, but I'll wait til 2.1 is released.
[Verizon Samsung Galaxy S III] twistedillutions:
I accidentally deleted my 1/8 build anyone have it and plz share. I went to see team liquid builds only saw beta 1 1/7 build and on beta 2 shows 1/9 build
[Verizon Samsung Galaxy S III] hallstevenson:
Get the 1/9 build or just wait a day or two for their beta 2.1 build.
[Verizon Samsung Galaxy S III] daihl92:
Just letting everyone know, I was on twrp 2.6.3.1 and did a complete wipe coming from PA 4.4.2 and it bricked my phone. Not hating on liquidsmooth because I have loved their roms in the past, just putting this out there. I was able to save it by going through odin and going back to stock but it wasn't fun. Just a heads up, look forward to trying to flash again in the future.
[Verizon Samsung Galaxy S III] hallstevenson:
ROMs don't brick phones...
[Verizon Samsung Galaxy S III] RBarnett09:
This was most likely caused because of an incompatible kernel.
[Verizon Samsung Galaxy S III] LeoRex:
Running latest... with the 12/31 bms... very smooth, and after 4 hours or so, very little issues and no boots.

a clock fc on boot, which is probably an issue with hd widgets, not the OS.

Still have the screen freak out when charging and the circle/busy graphic. I did lose audio once as well...not sure what that was about.

But so far, seems the most daily drivable KK I've tried
[Verizon Samsung Galaxy S III] achaia40:
Can someone tell me what pocket mode does.... Under active display.

Thanks
[Verizon Samsung Galaxy S III] LeoRex:
When Active Display is on and pocket mode enabled, it won't turn on the display when the proximity sensor is detecting something close.... in your pocket for instance.

---------- Post added at 09:57 AM ---------- Previous post was at 09:50 AM ----------

Spoke too soon. heh....

Yep, there is definitely something going on with the power sub system.... The battery ring in the notification bar doesn't show the true value... if I am at 90%, the ring will sometimes be 1/4 full, 2/3rds, sometimes 'empty'.

And when it is charging.... ooof.... It'll boot about half the times I unlock the phone, if I DO get it unlocked, the wallpaper goes black... the battery ring flashes, and it'll bounce back and forth between the desktop and lock screen (then boot). So yeah, that's a mess. When it is unplugged, it's rock solid though. :)
[Verizon Samsung Galaxy S III] yamaha_wins:
I just came from pa to liquidsmooth had no issues. Liquid is 100 times better than pa.. I think anyways! Just started messing with the ROM. Noticed if you select the circle dotted with percentage and put the phone on charge it flicker's the dotted circle.

Also is it possible to remove launcher 3? I prefer apex and all the launchers seem to be a waste of phone storage.
[Verizon Samsung Galaxy S III] hallstevenson:
Turn off charging animation

---------- Post added at 10:08 AM ---------- Previous post was at 10:04 AM ----------

The inaccurate battery ring still exists. I pay little attention to that though as I always turn on the value. The second issue was fixed in the 1/8 build though and many others confirmed this. Odd that you're seeing it... As I mentioned above, turn off charging animation and see if that helps.
[Verizon Samsung Galaxy S III] LeoRex:
! that worked....

That was it!? I popped that off and the wonky freakouts have stopped for the time being. Crazy that a silly little non-descript animation option can wreak total havoc... It hasn't rebooted, it's reliable coming in and out of lock, etc... that's crazy.
[Verizon Samsung Galaxy S III] hallstevenson:
It was luck on my behalf that I related the two. :)
[Verizon Samsung Galaxy S III] beepea206:
So it sounds like the charging and battery /screen issues were NOT resolved as someone claimed they would be with the new build. Shame... I'll stick with gummy til they're fixed.
[Verizon Samsung Galaxy S III] jlokos:
I haven't had any charging or battery screen issue on the latest beta 2 build. I've been on it for several days with LK.
[Verizon Samsung Galaxy S III] beepea206:
Bah. All these conflicting reports. I'm gonna test it out.
[Verizon Samsung Galaxy S III] swan3609:
So I just flashed my GFs S3 after watching how terrible it ran stock. All was good except for some reason she doesn't have any notification sounds or ring tone. Volumes are up all the way but I can't figure out why there is no sound.

On 2.37.
[Verizon Samsung Galaxy S III] LeoRex:
Well... the workaround was as simple as disabling the charging animation. No fancy spinning battery ring, no issues.

Wonder is the devs know the connection.
[Verizon Samsung Galaxy S III] hallstevenson:
Good thing I dirty flashed between builds after turning off the charging animation. I'm on 1/8 and just turned the animation back on while it was plugged in.... It was all screwed up when I tried to unlock - non-responsive, soft rebooted twice in one minute, and so on. Pretty bad ! They do have a 1/9 build (Beta 2) but I'm waiting on Beta 2.1 for now.
[Verizon Samsung Galaxy S III] twistedillutions:
Darn i was about to come i running.. Disable battery animation and fone won't go bonkers wen charging.

Lil late to the party. I think slimkat had the same issue not sure was on it for couple days. LS my DD. The stock launcher not my cup of tea i like nova launcher..
[Verizon Samsung Galaxy S III] beepea206:
I flashed and still had plenty of wonky animations... from the circle on the initial boot, to the battery icon.
[Verizon Samsung Galaxy S III] LeoRex:
Yeah.. the little wait circle is a little crazy. But when charge animation is on, the phone will boot.

I am also getting boots when I leave home and my Wi-Fi disconnects.

Livable for now.
[Verizon Samsung Galaxy S III] cinco312:
The battery issue has to be a 4.4.2 issue. I get the same thing on my Nexus 7, which is completely stock. The 1/9 build seems to be fine. Data still didn't work for me, then I flashed BMS and got all data back. Running smoothly for now.
[Verizon Samsung Galaxy S III] LeoRex:
Well... dropped back to my 4.3 daily driver... PA 3.99.... for the second time, my audio dropped out: no notification sounds, ringtones , etc... just one basic ui sound. Reboot and clearing cache didn't help so I restored a backup.

I'll reload the ls backup to see if that clears it, but no sound is a deal breaker.
[Verizon Samsung Galaxy S III] LeoRex:
IMEI dropped out and I had to do an nvrestore to get it back... Phone radio would crap out the instant I tried to make a phone call.

Glad I made sure I got a good backup of that stuff.... that would have sucked.

So folks... just as a precaution, make sure you have a valid IMEI/EFS backup on your phone. It is not backed up when you do a CWM/TWRP backup. There is a VERY detailed post somewhere here that explains it all... I suggest you find and read it if you don't know what I am referring to :) . I guess the EFS partition on the SIII is torqued up from the factory and it's best to redo it to make sure you have a backup. Losing the IMEI/EFS partition without a valid backup present is very very bad news I guess.... not sure how easy that would be to fix.

I was able to do it with a simple command from a terminal emulator as root:

To backup:

(from terminal emulator, as root):

reboot nvbackup

From ADB:

adb reboot nvbackup

To restore:

(from terminal emulator, as root):

reboot nvrestore

From ADB:

adb reboot nvrestore
[Verizon Samsung Galaxy S III] RBarnett09:
So if I open terminal emulator and do reboot nvbackup it should save a backup of my IMEI to my phone? And where does this store?
[Verizon Samsung Galaxy S III] LeoRex:
It is stored on a hidden, persistent partition (wipe doesn't clear it).

Yeah.. open term session, su to root, run the commands. It'll boot, backup the partition and then boot the phone back.

read this first

:

[HOWTO]Comprehensive IMEI/EFS Backup

That has all the grisly details and explains the importance. You don't want to be left without a working IMEI.
[Verizon Samsung Galaxy S III] m_s_ifland:
Man, I'm loving the new lockscreen notifications :)
[Verizon Samsung Galaxy S III] hallstevenson:
A beta 3 folder showed up on LiquidSmooth's download page, but only (1) phone has a new ROM. In the beta 2 folder, a whole bunch of phones -- including the d2vzw -- have new builds too. Nothing posted on the LS Google+ page yet though....
[Verizon Samsung Galaxy S III] skrypj:
Looks like the Beta 2 for d2vzw was just posted today.
[Verizon Samsung Galaxy S III] RBarnett09:
I just can't help but get lost in the confusion of having beta folders within the official folder. Lol.

Either way, I'm overly thankful!

I'll always run LiquidSmooth ROMs.
[Verizon Samsung Galaxy S III] twistedillutions:
http://www.drdevs.com/devs/teamliquid/official/Beta2/

Liquid-Kitkat-v3.0-NIGHTLY-d2vzw.zip 13-Jan-2014 16:04 141M

anyone running that file?
[Verizon Samsung Galaxy S III] cinco312:
I flashed it a couple of hours ago. So far so good. More features added
[Verizon Samsung Galaxy S III] twistedillutions:
ok ..will flash tonight ..

i wanna try other roms but these releases keeping me here lol
[Verizon Samsung Galaxy S III] pendata:
Nothing else is really worth it. I tried them all.. This is the best kk ROM right now! :)
[Verizon Samsung Galaxy S III] cinco312:
I agree. Me personally, LS ROMS are the best out there. I tried other ROMS at most for a week or so and always come back home to Liquid.

---------- Post added at 04:14 AM ---------- Previous post was at 04:12 AM ----------

Anyone know what setting I need to untick to get rid of my phone waking up when hovering above it? It's annoying. Can't seem to find it anywhere