yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] buddwm:
So this is really strange. I went ahead and did a re-flash of the ROM (re-flash of kernel only didn't fix it), re-flashed the kernel, and after ROM came up, notification lights worked fine. However, I needed to re-install gapps. So rebooted back into recovery, flashed the gapps package that was linked on the front page (the latest one), rebooted - and after a sync with my Google account, notification lights don't work again. I'm very confused now.

Why would gapps seemingly break it? I don't have any programs installed that I know of which would cause this behavior - in fact, the only apps I had to re-install were Gmail and an update to Google Search (and of course the apps that get installed with the flash such as the store, etc) - everything else had remained installed. I didn't make any other changes, and the store didn't auto-download/install any additional apps.

EDIT: Well now it just started working, without me doing anything. Strange - but at least it works now.
[Verizon Samsung Galaxy S III] petermac88:
Only issue I have is low quality pictures.

EDIT ** I don't mind the low quality pictures too much, I rarely get mms anyway, but I'd like a fix when the dev's have time, I'd really like same quality as the sender rather than a lower quality compared to the sender.
[Verizon Samsung Galaxy S III] ryan1977:
Re: [ROM][4.2.2][RC2] LiquidSmooth ROMs - d2vzw & d2usc - 3|5|13

I just went into themes and apps section for d2vzw on tapatalk, and searched for audio mods, acid version 7, and I installed aosp build 2. I backed up music fx, and then deleted it with titanium backup, also deleted any other music app is had. Then flashed in recovery, wiped cache and davlick and fixed permissions, and everything works well. When u flash it it will hang up for about ten minutes when installing. This is normal, I also should let you know that I use power amp with it, it is recommended.

Sent from my SCH-I535 using Xparent BlueTapatalk 2

---------- Post added at 11:04 AM ---------- Previous post was at 10:26 AM ----------

I just found a bug, I don't know if anyone else is experiencing this but every time I make or take a phone call, afterwards my status bar won't pull down, I have to reboot to get it working again. Anyone else have this issue?

Sent from my SCH-I535 using Xparent BlueTapatalk 2
[Verizon Samsung Galaxy S III] bobby janow:
I believe this is the link. Let us know when you try it if it works. Crashed my Liquid install some months ago I think V.5.

http://xdaforums.com/showthread.php?t=1923630
[Verizon Samsung Galaxy S III] ryan1977:
Re: [ROM][4.2.2][RC2] LiquidSmooth ROMs - d2vzw & d2usc - 3|5|13

Just wanted to show u guys that this did install properly on my phone running liquid rc2. Acid build properties

Sent from my SCH-I535 using Xparent BlueTapatalk 2
[Verizon Samsung Galaxy S III] bobby janow:
When you say you deleted every other music app, which are you talking about? Did you delete Google music?
[Verizon Samsung Galaxy S III] biyobe:
I'm running the KT747 kernel... any "ideal" setting for this ROM??
[Verizon Samsung Galaxy S III] trigz:
Is there anyway to get the stock launcher instead of nova?
[Verizon Samsung Galaxy S III] ryan1977:
Re: [ROM][4.2.2][RC2] LiquidSmooth ROMs - d2vzw & d2usc - 3|5|13

Yes, and the one that came with the rom

Sent from my SCH-I535 using Xparent BlueTapatalk 2
[Verizon Samsung Galaxy S III] kl323:
Anyone notice difficulty pulling up PIE controls immediately after unlocking the screen? It either takes pulling down the notification tab or actually entering Settings to get it to work for me.
[Verizon Samsung Galaxy S III] mike216:
Re: [ROM][4.2.2][RC2] LiquidSmooth ROMs - d2vzw & d2usc - 3|5|13

I needed to have the button press working on my earbuds so I tried a few AOSP roms. CM10.1 has it working. After trying all these different roms out I miss liquid so much. Please people implement the earbud button fix Mikey!
[Verizon Samsung Galaxy S III] dablitzkrieg:
Re: [ROM][4.2.2][RC2] LiquidSmooth ROMs - d2vzw & d2usc - 3|5|13

I can also confirm the charging bug when the phone is off, only showing a small purple battery but not charging
[Verizon Samsung Galaxy S III] itsmikeramsay:
Definitely a must have going into the next build. I have no clue what's missing, unless it's something in framework.... gotta find out ASAP as I need it myself....
[Verizon Samsung Galaxy S III] jl2222:
Re: [ROM][4.2.2][RC2] LiquidSmooth ROMs - d2vzw & d2usc - 3|5|13

Anyone been having problems with their WiFi connecting automatically to a saved network? If I'm on campus and switch to the schools WiFi it doesn't automatically connect. It just says disabled in my WiFi connection settings. So ever time I have to click on it and say connect. Then when I come home and switch to my home network it does the same thing. Its very annoying.

Not sure if its a hardware problem or the ROM but its been happening ever since RC1 or possibly late illusion.

EDIT: For some reason my networks were set not to automatically connect. PROBLEM SOLVED/FIXED

---------- Post added at 01:44 PM ---------- Previous post was at 01:14 PM ----------

Thanks! Acid installed with no flaws!
[Verizon Samsung Galaxy S III] d1ez3:
Does anyone else experience a lot of lag when pulling the notification shade down immediately after turning the screen on? I've had this on almost all cm10 roms, and only the faux kernel has solved this for me. I was curious if it was just me though.
[Verizon Samsung Galaxy S III] petermac88:
Re: [ROM][4.2.2][RC2] LiquidSmooth ROMs - d2vzw & d2usc - 3|5|13

Nope doing great here, what kernel are you using?
[Verizon Samsung Galaxy S III] d1ez3:
I think it's because I use widgetlocker instead of the stock lock screen
[Verizon Samsung Galaxy S III] ganGeee:
Hey Mike keep up the good work! love the rom!

May I suggest if you guys can add "toggles per row" feature for the statusbar toggles on the next build? I know its small thing but would much appreciate it!
[Verizon Samsung Galaxy S III] twistedillutions:
Can someone with 2.37 tell me how to get kt747 working properly.. I cant switch out from demand im coming from BMS
[Verizon Samsung Galaxy S III] cinco312:
Here you go brother. https://www.dropbox.com/s/7rfomjoo0io114b/ThemableMmsAllWorking.zip
[Verizon Samsung Galaxy S III] beepea206:
With KT, you have to use a version that is the same date or earlier than 11/7/13... they push out nightlies faster than BMS. BMS works with this rom, KT does selectively. I actually prefer BMS on this rom.
[Verizon Samsung Galaxy S III] jl2222:
Anyone having problems getting past the splash screen after booting for the second time after loading the 4.3 version of this ROM? I can only get up to 2.9 to load.
[Verizon Samsung Galaxy S III] cinco312:
Try clearing cache and Dalvik. If not then reflash. Are coming from a different ROM?
[Verizon Samsung Galaxy S III] cinco312:
Is this ROM going to still be based off of CM or is it switching to AOSP?
[Verizon Samsung Galaxy S III] beepea206:
Cm is based off aosp and we don't have any pure aosp roms, so I'm guessing they'll keep cm as the base.
[Verizon Samsung Galaxy S III] cinco312:
Most of the 4.4 ROMs are moving away from CM to an AOSP base. Just wondering if LS would follow suit.
[Verizon Samsung Galaxy S III] Bramton1:
I think I found the solution to my issue. I went into the Wi-Fi advanced settings and found that the Wi-Fi region code a set to Europe. I set it to United States, and the scanning has been working fine ever since.
[Verizon Samsung Galaxy S III] TheBr0ken:
We are ;)
[Verizon Samsung Galaxy S III] cinco312:
Awesome!
[Verizon Samsung Galaxy S III] jl2222:
I have cleared coach dalvik factory reset and even wiping all data. To no avail. I've been using liquid for about 8 months now.
[Verizon Samsung Galaxy S III] DieselNY:
Looking for some help. I downloaded the latest version and my sound doesn't work. Keypad clicking is gone, can't change the wound settings in that top row with the widgets. Sound doesn't work on my Sirius app. I've reflashed even different versions. Anyone have any idea what I can do? Thanks.
[Verizon Samsung Galaxy S III] junowhoo:
Any bugs with this new 4.3?
[Verizon Samsung Galaxy S III] cinco312:
Nothing major. Stable as always.
[Verizon Samsung Galaxy S III] RBarnett09:
Does anyone have a link to the kernel that 2.37 comes with? I flashed BMS and now I'm having graphical glitches... which wasn't the case before hand.
[Verizon Samsung Galaxy S III] DieselNY:
Anyone have a link to the wallpaper from 2.9. Blue and purple pinkish. The new version comes solid blue. Thanks.
[Verizon Samsung Galaxy S III] Shallow_1:
Just dirty flash 2.37 and the gapps again
[Verizon Samsung Galaxy S III] savagebunny:
So far my fresh install is working well. Just something that's odd, when I press the home button or power button there is a 2-3 second delay of the screen turning on. It was instant when It was a fresh clean install with nothing done to it. Any idea?
[Verizon Samsung Galaxy S III] raypino:
finally installed this latest and greatest ls and wow what a sight. camera transition better compared to 2.9 and so far no issues. well granted this is the second time I've installed this since the first try my capacitive buttons didn't work even after a reboot. 2nd times the charm and this thing is quick. switching between home screen was so smooth that my finger got hot from the friction and no lag at all. I do wanna know if it's ok to delete nova launcher and apollo player without harming anything.

thanks to all the dev's for this experience.

sent via carrier pigeon
[Verizon Samsung Galaxy S III] deadman96385:
Yes nova and Apollo can be deleted, it will not hurt the rom.
[Verizon Samsung Galaxy S III] twistedillutions:
Will this be the last of 4.3.. Is 4.4 kitkat on the way??
[Verizon Samsung Galaxy S III] cinco312:
I believe so. On their Facebook or Google+ page they said this will be the final 4.3 release.
[Verizon Samsung Galaxy S III] Shallow_1:
Or last jelly bean release
[Verizon Samsung Galaxy S III] whitey13:
Um yeah... So i just finally updated my kernel earlier from the stock on 2.37 and I'd easily advise everyone else to do the same lol. Im using KT but it's a preference. Im sure bms is just as good.

Stock from 100‰ to 90% with regular usage about an hour.

KT about 3 1/2 hours ;)
[Verizon Samsung Galaxy S III] DieselNY:
Switched back and forth from a bunch of roms and back on liquidsmooth v2.9. Everything finally working again except the gallery only shows the photos from the external SD card (photos save to external card) and nothing else shows. Nothing on my internal SD card shows up. When I use file manager app I can view everything but not in the gallery. Any idea on a fix? Thanks.
[Verizon Samsung Galaxy S III] d1ez3:
why not use the much updated 2.37?
[Verizon Samsung Galaxy S III] twistedillutions:
Are u ppl formating the SanDisk 64gb to fat32?
[Verizon Samsung Galaxy S III] twistedillutions:
As in YOUR type of people.. Lol
[Verizon Samsung Galaxy S III] DieselNY:
I did that too same issue.
[Verizon Samsung Galaxy S III] lazarus0000:
Just letting everyone know that I recently came back over from PA 3.9 to LS 2.10. I had been running 2.9 but my Maps/Nav kept crashing and that was a must have! 2.10 is running flawlessly and I just want to tip the hat to the Devs! Thanks guys - awesome work.

This is my new daily driver and with good reason! I've flashed just about everything AOSP / AOKP / CM for this phone and this has the BEST (!), hands down combination of features and reliability! Used to be a flashaholic but this has calmed my flashing nerves...

Thanks!

"I've got a revolution behind my eyes..."

--Battle Flag
[Verizon Samsung Galaxy S III] raypino:
flash player not working. anyone know why

sent via carrier pigeon
[Verizon Samsung Galaxy S III] Wrngway:
I just flashed 2.10 and the gapps in TWRP after wiping system, cache, and dalvik. My phone hangs on the LS boot animation. I gave it a good 15 minutes before trying to reboot into recovery. I had to do a battery pull to turn the phone off. I held the up vol, home, and power down as I usually do and the phone won't get to the "Samsung Galaxy S III" screen. When I release the buttons it just reboots into LS again and hangs on the animation.

What am I doing wrong? Do I need to reflash my recovery? I know I didn't wipe it.

[EDIT]Grrrr...forgot to wipe data. Any recommendations on how to proceed?
[Verizon Samsung Galaxy S III] RayMcGrath:
Boot into recovery and restore a backup. Then make sure you have all the correct downloads for a Verizon Samsung Galaxy s 3. Try again.
[Verizon Samsung Galaxy S III] Wrngway:
Thanks. That was my first thought too, but it won't boot to recovery. Holding vol up, home, power I get the initail bootup vibration and samsung screen, but then a black screen. When I release it reboots again and I'm back in the bootloop for the rom.

I suppose I'll just try adb reboot into recovery when I'm back home. If that fails, maybe reflash recovery and try to reboot into it again. I was hoping for a quick fix. I guess this will take some more work.
[Verizon Samsung Galaxy S III] RayMcGrath:
sometimes my phone is tricky to hold to get into recovery that way too. Hold it until you see the little blue flash of words in the upper left corner of the screen, then let go.

I hope this helps!
[Verizon Samsung Galaxy S III] Wrngway:
Huzzah! That did it. Thanks man!! All is well with the world again.
[Verizon Samsung Galaxy S III] elrichmeister:
K

2.10 had special flashing instructions

Factory wipe

Clear davlik

Clear cache

Format system

Flash ROM

Reboot let the rom settle

Boot into recovery

Flash gapps

Clear davlik

Clear cache

Reboot

The you add your Google account manually in settings.

Not sure why you're flashing 2.10 unless you're having trouble with 2.37
[Verizon Samsung Galaxy S III] phatreno:
Reboot into recovery and flash your backup or just do a full wipe and fresh install from recovery, volume up, home button, power button
[Verizon Samsung Galaxy S III] RBarnett09:
On 2.37...

Anyone know where the option is to disable the home button from waking up the device. I cannot find it anymore.
[Verizon Samsung Galaxy S III] rhamorsky:
its under display settings on mine
[Verizon Samsung Galaxy S III] RBarnett09:
You must be on a later version.

That's where it used to be on mine. Now I can't find it.
[Verizon Samsung Galaxy S III] rhamorsky:
well ill be damned. i dont use it so i didnt notice it was gone, sorry! i see some steps in other forums about going into file explorer and making changes that way but i havent tried it

---------- Post added at 06:56 PM ---------- Previous post was at 06:47 PM ----------

ok, itried this using rom toolbox pro and it worked for me. in using rom toolbox all i did was open root browser, i didnt have to mount anything.

open root explorer

navigate to : system/usr/keylayout

now press the mount r/w button near the top of screen to enable read and write permissions

scroll down to: sec_keys.kl

press and hold until menu pops up, select: Open in Text Editor

locate line: key 172 HOME WAKE

tap behind the word WAKE and delete it so you see: key 172 HOME

press menu and select: Save and Exit

now press the button at the top of the screen to disable read and write permissions: Mount R/O

(once pressed should now read : Mount R/W again.

Exit root explorer

Reboot your phone

see if it works
[Verizon Samsung Galaxy S III] DieselNY:
The one thing I don't do is format system. Doesn't that delete internal data? Not sure why that step is needed?
[Verizon Samsung Galaxy S III] ldc2335:
System is the rom. Always format system, data, cache.

Sent using Tapatalk for Android.
[Verizon Samsung Galaxy S III] DieselNY:
Sorry yes I do its format data I never do.
[Verizon Samsung Galaxy S III] phatreno:
What's the difference between 2.10 and 2.37 where's 2.37 op just seemed to jump to 2.10 to 2.37
[Verizon Samsung Galaxy S III] beepea206:
That's not really good advice. You only need to wipe the system if downgrading or upgrading the framework. So if you on cm10,you can flash aokp and only wipe dalvik and cache; the core framework is the same.

But you always, ALWAYS, wipe dalvik. That's how Android caches system app data so if you don't wipe it, you get mixed and bad data, which can lead to a bootloop.
[Verizon Samsung Galaxy S III] ldc2335:
Will it work? Yes. But any good dev will tell you to wipe. Fresh installs are less troublesome.

Sent using Tapatalk for Android.
[Verizon Samsung Galaxy S III] flyestAC:
I always wipe system with any flash I do. I keep all my important stuff on the SD so it's no big deal.
[Verizon Samsung Galaxy S III] beepea206:
I've been compiling and flashing Android since the Droid 1 came out and I only wipe data when I find there's an issue; devs post that so n00bs won't post "I got a bootloop" or "It won't boot right". They don't know what you're coming from, so it's a general disclaimer,but if you know what you're doing, you only need to wipe data when crossing over framework bases. 'Data' is just apps and system data related to framework; if you have the same framework (CM10 to AOKP 4.3), there's no need to wipe data. I've had to wipe data maybe 2 out of my last 10 flashes, so yea, it works.

Besides, it's much easier to dirty flash, then reboot into recovery to wipe data if necessary, than it is to restore system apps and their data whenever you want to try a new rom.
[Verizon Samsung Galaxy S III] RBarnett09:
Dude, you're awesome!! It worked!! Thank you very much!!
[Verizon Samsung Galaxy S III] raypino:
in case you haven't found the controls, it's under interface and then clock widget.

---------- Post added at 08:03 AM ---------- Previous post was at 08:00 AM ----------

just updated to 2.37 from 2.9 and now it's showing the same thing. was wondering if anyone figured out why your unable to adjust vibration.
[Verizon Samsung Galaxy S III] griz.droidx:
To each their own. But so many people have so many problems trying to partially clean flash or perhaps someone could come up with a new name for flashing when wiping only cache. If you wipe cache you wipe dalvik. dalvik is a part of that cache. You're right that system app datta causes issues, between differing roms.

Personally, and I've been flashing roms for a while now. With pretty good luck knock on wood.. I always wipe data/cache before installing a rom. Unless it's a nightly to nightly then I might only clean dalvik or the entire cache. At least with clean flashes if you encounter issues that's one thing that can be instantly ruled out for the devs.... So they won't get an issue reported when the user didn't follow their directions.. Which usually state to wipe data/cache. Even on two roms with the same android version, the framework could have minor changes I would assume because they could change the source or add/remove things or cherry picks when "making" the rom before building it. I guess they do make then make install I don't know. I'm no dev.. I just remember the days of "using the source" to install stuff on various distros. But again, not trying to start something I just think it needed a little clarification.. perhaps someone else can clarify even more.. You may be right after all.

Thanks for your help though.. The devs and community are what makes android and linux in general so great.

---------- Post added at 07:59 AM ---------- Previous post was at 07:54 AM ----------

One other thing. I thought I read several pages back that 2.37 was newer than both 2.9 and 2.10. I am 99% certain of this, unless, they re-releassed 2.9 and 2.10. I know the version number make no sense.. At least not to me, but I'm sure it does to them. I'm sure there's a reason. They're a pretty dang gone good bunch of dev's Been using and testing their roms on my devices since I got my Droid X.

---------- Post added at 07:59 AM ---------- Previous post was at 07:59 AM ----------

One other thing. I thought I read several pages back that 2.37 was newer than both 2.9 and 2.10. I am 99% certain of this, unless, they re-releassed 2.9 and 2.10. I know the version number make no sense.. At least not to me, but I'm sure it does to them. I'm sure there's a reason. They're a pretty dang gone good bunch of dev's Been using and testing their roms on my devices since I got my Droid X.
[Verizon Samsung Galaxy S III] ldc2335:
Like I said, I don't dirty flash unless maybe a nightly. Even then, I wipe system and cache.

When switching roms, I wipe everything. To each their own like you said. I'm just not sure he should be telling people what "could" work instead of what "does work."

About the naming. 2.37 is newer than 2.9 and 2.10.

Liquid tweeted that he wanted to wait to release 3.0 until all the bugs were fixed. So they went to 2.10 instead. Kind of backwards in regards to typical rom naming, and confused a lot of people.

I would have called it 3.0 beta or something. Maybe even 2.95.

Sent using Tapatalk for Android.
[Verizon Samsung Galaxy S III] whigs:
I'm guessing it is just incrementing by point release version...since 2.10 > 2.9, 2.37 > 2.10
[Verizon Samsung Galaxy S III] tihsllub:
Another awesome battery stat from the 2.9 romView attachment 2426910View attachment 2426911View attachment 2426912View attachment 2426913

Sent from my........
[Verizon Samsung Galaxy S III] moparfreak426:
So hiw is liquid? Heard yalls first really customizable like pac or carbon to have a 4.4 build but i cant find it

Sent from my SCH-I535 using Xparent Skyblue Tapatalk 2
[Verizon Samsung Galaxy S III] RBarnett09:
There is no 4.4 build yet.

It's 4.3.1
[Verizon Samsung Galaxy S III] Óðinsdagr:
Is 2.37 the most current build ?
[Verizon Samsung Galaxy S III] RBarnett09:
Yes, and in my opinion, is more stable than the 2.10 build.
[Verizon Samsung Galaxy S III] savagebunny:
Question, on 2.37 my phone sometimes doesn't wake up pressing the power button and takes about 3 seconds to wake up the screen using the home button. No other ROM has does this before... Even when I was on v2.8 of LS it never did it. Anyone have any idea what's causing this?
[Verizon Samsung Galaxy S III] whitey13:
Might be the daydream feature. Did it to me on 2.36
[Verizon Samsung Galaxy S III] RBarnett09:
Have you undervolted at all? If not, I really can't imagine what your issue would be coming from. But if you have undervolted, you may need to increase the voltage a bit.
[Verizon Samsung Galaxy S III] beepea206:
MUCH more stable. It also has the updated CM/stock kernel, so you can use the updated KT and BMS kernels with no issues.
[Verizon Samsung Galaxy S III] savagebunny:
I have undervolted. I increased the voltage to default values and still does the same thing as described in my OP I made
[Verizon Samsung Galaxy S III] RBarnett09:
Keep it on defaults and give it some time. Hopefully this fixes your problem.

I used BMS with 2.37 but I started getting graphical glitches. Had to just switch back to the kernel included in 2.37.
[Verizon Samsung Galaxy S III] capt730:
Anyone having an issue where your music player won't play wma audio files (rocket, apollo, Google play music)? On tw roms, they play fine.
[Verizon Samsung Galaxy S III] twistedillutions:
Do i have to format my SanDisk 64gb to sdxc to fat32??? I ask before but no answer
[Verizon Samsung Galaxy S III] savagebunny:
I upped the voltage on the sleep frequencies and the lower scaling and gonna see how it goes
[Verizon Samsung Galaxy S III] sweeds:
Wow. This ROM is blazingly fast. Running really well after 1 full day.

Question: Is there any multiwindow functionality on AOSP ROMSs?
[Verizon Samsung Galaxy S III] beepea206:
I believe that functionality is available on AOKP... I don't use it, but roms that offer the ribbons seem to allow dual-pane.
[Verizon Samsung Galaxy S III] roghitmanx47:
Why can't I find the 2.3.7 download?
[Verizon Samsung Galaxy S III] Shallow_1:
http://www.drdevs.com/devs/teamliquid/official/2.37/

---------- Post added at 06:01 PM ---------- Previous post was at 06:00 PM ----------

Make sure you grab d2vzw
[Verizon Samsung Galaxy S III] thelangosta:
Omni Rom has it. So do others that have kanged that feature. It wouldn't surprise me to see most of the AOSP roms(except maybe CM) use it.

Sent from my Transformer TF101