yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] Nolam20:
Like I JUST said, I'm not coming from BMS, I'm coming from Lean. BMS has never touched my phone. And I never messed with those settings in the first place, only to try and fix it.
[Verizon Samsung Galaxy S III] hallstevenson:
Excuse me for trying to help.... Forget what I said about BMS having just two files. Imo's LK is just as simple - it's just boot.img plus an init.d script, 00leanKernel. Delete that "00" file and NO traces will remain.
[Verizon Samsung Galaxy S III] RBarnett09:
Anyone else having the issue of the clock in the status bar freezing up? And it also freezes when you see the clock after pulling the status bar down on the notification drawer.
[Verizon Samsung Galaxy S III] yamaha_wins:
Anyone able to get hotspot working?
[Verizon Samsung Galaxy S III] mmikeee:
I'm having trouble with the clock and battery icons showing up at all... The clock will show up whenever I disable it then enable it but will soon disappear as well. The battery icon just doesn't show up even when I change icons for it.
[Verizon Samsung Galaxy S III] &roid:
Anyone know of a fix for the DSP manager skip problem? I've tried other kernels and replacing the dsp apk, but makes no difference. This problem wasn't there with 2.9 version. I've also tried adjusting CPU or SD read ahead settings, but still no fix. If DSP disabled everything sounds fine, but I like to use the equalizer and the compression effect.
[Verizon Samsung Galaxy S III] hallstevenson:
Yeap, works fine here.
[Verizon Samsung Galaxy S III] Stolly08:
Everything seems to be working pretty dang good here! Really glad LS got 4.3 smooth and stable!!!
[Verizon Samsung Galaxy S III] yamaha_wins:
Your using the built in hotspot? Mine will broadcast a signal but when I connect my tablet my data signal closes
[Verizon Samsung Galaxy S III] tyleras3:
I flashed this and I had some serious screen flicker. Everything flickered. What did I do wrong ?
[Verizon Samsung Galaxy S III] Nolam20:
I'm in the same boat. It has to do with your custom kernel, I'm in the process of trying to figure it out, for now I'd go back to 2.9 if I were you.
[Verizon Samsung Galaxy S III] raisins:
2.10 Build?

Can someone with the latest official 2.10 release tell me what build it is?

I am not sure if I have the most up to date build - I had the second build ( I think), which was an "updated" version of the initial release of 2.10. This was all before the OP was updated to show 2.10
[Verizon Samsung Galaxy S III] hallstevenson:
Yeap, I turned it on, then had my daughter's device connect to it. I was able to open Facebook and it loaded fine.

---------- Post added at 10:20 AM ---------- Previous post was at 10:18 AM ----------

Mine reads:

liquid_d2vzw-userdebug 4.3 JLS36G eng.teamliquid.20130929.154314 test-keys

---------- Post added at 10:21 AM ---------- Previous post was at 10:20 AM ----------

On Liquid's FB page, they're asking for additional beta testers....
[Verizon Samsung Galaxy S III] Nolam20:
Ok, so, from what it seems (at least after ten minutes of running a fresh flash with no flicker),

To fix the flicker or display or graphical issues, wipe your data and cache, flash 2.9, reboot, then wipe data and cache again, flash 2.10, reboot.

It worked for me, I really think the problem is flashing from something with a custom kernel. Coming from stock kernel on 2.9 alleviated the problem for me.

Hope this helps others.

EDIT: And of course, just as I post this, I see a flicker... I'm going to flash BMS kernel to see if it fixes the problem, otherwise I'm sticking with 2.9 from now on.

EDIT2: Flashing the latest 3.4.x BMS kernel seemed to solve my flickering issues. Good luck everyone else!

EDIT3: Of course, right after the post, it's back. I'm done, staying on 2.9.
[Verizon Samsung Galaxy S III] tyleras3:
That seems to make sense because I came from Beans with a custom kernel and my screen flicker was absolutely crazy.

Are there any deal breaking bugs? Like I flashed 4.3 PAC and the camera wouldn't connect. I love Beans but I want to be back on AOSP and 4.3 but I'm very picky about my phone working fully.
[Verizon Samsung Galaxy S III] Nolam20:
WELL actually the flicker is back now, so I'm restoring to 2.9 and staying there until we can get a completely stable 4.3 ROM for LS, because I like you refuse to use a rom with any bugs or problems. Obviously while the flicker is a slightly uncommon problem (only half a dozen reports), it's an annoyance and I don't believe it's our faults if the stock kernel is causing this even after wipes...
[Verizon Samsung Galaxy S III] tyleras3:
So 2.9 is pretty stable then :0? Daily driver material?

Could I get a download link?
[Verizon Samsung Galaxy S III] Nolam20:
Yes it's 4.2.2, very very few bugs (and tolerable ones). I don't have a download link at the moment but I can get one to you in about 10 hours when I get home... Perhaps someone else could get you it. I don't know why he took them down...
[Verizon Samsung Galaxy S III] tyleras3:
Ah 4.2.2 thats why. Okey that's okey thanks anyway :)
[Verizon Samsung Galaxy S III] Nolam20:
Yeah... I'm just sticking with it until we get a more stable 4.3 build...
[Verizon Samsung Galaxy S III] hallstevenson:
2.10 is working fine for the majority of people. Make sure you download the currently linked one. There was a link to one posted previously, and labeled 2.10, that is not good. Pretty poor form on Liquid's part to re-release it and not update the version number though.... Or, the first one that was labeled 2.10 should have been labeled something different.
[Verizon Samsung Galaxy S III] rhamorsky:
question, have you changed the dpi settings at all and if so are you restoring those same changed settings?.......just a thought
[Verizon Samsung Galaxy S III] Nolam20:
We're talking about the flickering problem a few of us are having. In that aspect it's not stable for us, and yes we have used fresh downloads.

Umm... I don't believe that there's a way for me to restore changed DPI settings (or at least I didn't do it) ...although I will point out that when I restore from a titanium backup that was when the flicker started after BMS seemed fine. It was only apps that I restored though.
[Verizon Samsung Galaxy S III] rhamorsky:
when i flash new roms i always redownload. its a pain in the butt ive heard of alot of people have problems restoring from tbu. you may have to reflash and restore one app at a time till you find the culprit. most apps have been updated to work with 4.3 but sounds like you may be restoring something that isnt. hope this helps...if not...well i tried. good luck!:D
[Verizon Samsung Galaxy S III] tyleras3:
Its for this reason that I usually just manually redownload my apps haha even tho its a pain. Needless to say o don't switch ROMS as often as I use to :P I find daily driver material and stay with it until something better comes along.
[Verizon Samsung Galaxy S III] Nolam20:
I have 100 apps haha. Something tells me it isn't linked to that because the flicker happened on a clean flash with stock kernel, and I doubt any app could cause graphical errors that severe (and that I would think are most definitely kernel related), although I'm not sure. I think I'll just wait it out.
[Verizon Samsung Galaxy S III] tyleras3:
Is 4.2.2 giving you any camera problems? I was on Slim 4.2.2 for a long time but front facing camera in apps like Snapchat and Instagram would cause a hot boot but that was on the MB1 modem. I've since updated to the MF1 modem but I haven't been on an AOSP ROM with the new modem yet.
[Verizon Samsung Galaxy S III] Nolam20:
Yeah, occasionally it will crash and snapchat will say I need to restart the camera app. The only way to get it to work is a reboot. Very rarely it will hot boot, but maybe once a week while using snapchat (which I use 50x a day), yes. I was wondering about what the MF1 modem was/what it will do for me if I update, care to explain briefly?
[Verizon Samsung Galaxy S III] tyleras3:
I updated my modems last night just because I like being up to date. There's a thread about it, I'd link you but I don't remember where it is. People report increases signal reception but I haven't honestly seen any. The OP of that thread says it can cause camera problems if your kernel isn't up to date (if you're on 2.9 then you're fine) and I was wondering if the outdated modem is what was causing the snap chat camera to stop working. You should update the modem and experiment for me :)? Just a simple flash in recovery it took me all of 5 minutes.
[Verizon Samsung Galaxy S III] Nolam20:
Will do, thanks! Does it survive a wipe or backup/restore, or is it lost when a new ROM is flashed, etc?
[Verizon Samsung Galaxy S III] tyleras3:
It survives so once you flash it then it's not going anywhere :P care to message me when you figure out if it fixes the snapchat thing? I'd love to go back to AOSP.
[Verizon Samsung Galaxy S III] Nolam20:
Will do, it may take a while to see it. Thanks!
[Verizon Samsung Galaxy S III] hallstevenson:
I said "the majority of people". I always say, give it a try. Why should he/she NOT try it based on the experiences of a few ?
[Verizon Samsung Galaxy S III] encephalon9986:
Everything is running smooth and fast here. Been running it for over 24 hours. No issues since the reflash to get 1x and 3g working. I just need a bigger battery in my s3 lol.
[Verizon Samsung Galaxy S III] hallstevenson:
Damn, best battery life I've seen yet!

View attachment 2315875

Wish I knew where this Google Services was coming from...
[Verizon Samsung Galaxy S III] rhamorsky:
do you have location enabled?
[Verizon Samsung Galaxy S III] &roid:
I have the same problem with Google services...
[Verizon Samsung Galaxy S III] hallstevenson:
Yes, but I've ALWAYS had it enabled (on every ROM I've ever used). I saw mention of this recently, suggesting Google has enabled something that wasn't on in the past. If you expand that item in the battery usage screen, it says "Manually control GPS to prevent....". So do I turn off "Access to my location" or "GPS satellites" ? It could be a 4.3 or AOSP/CM glitch as well because I've only seen it on those ROMs, not on TouchWiz.

Got a link for ^^^ that ? On the current, 8/13 gapps build, GMail doesn't refresh the inbox view on it's own. I have to force it. I can even get a notification of new messages, go to GMail, and none are showing (until I manually refresh). Or, do you see the same issue with Mastamoon's build ?
[Verizon Samsung Galaxy S III] rhamorsky:
are you using tbu to restore system and user apps?
[Verizon Samsung Galaxy S III] Nolam20:
Nope, just user apps. Exactly 100 of them... X.x i can get you a list probably
[Verizon Samsung Galaxy S III] rhamorsky:
http://xdaforums.com/showthread.php?t=2405425 read the OP here for the link

---------- Post added at 01:57 PM ---------- Previous post was at 01:56 PM ----------

nah i believe you, thats too much for me! lol
[Verizon Samsung Galaxy S III] Stolly08:
Figured this out a while ago... It annoyed the **** outta me as well... Go into where u change the LCD density and clear all relevant market data then restart... Should be gone after that...
[Verizon Samsung Galaxy S III] hallstevenson:
Huh ? LCD density is a line in /system/build.prop while the other is under Settings, Apps.
[Verizon Samsung Galaxy S III] nabour:
version confusion

So I am confused. Happily runnung on version 3.0. So....is 2.10 an upgrade?
[Verizon Samsung Galaxy S III] hallstevenson:
The version sequence is 2.7, 2.8, 2.9, 2.10. Liquid was planning on making a substantial jump from 2.9 to 3.0 (going from Android 4.2 to 4.3 (which they still kept with 2.10), Halo 2, etc, etc) but there were issues, so they rolled some things back and put out a smaller update, hence 2.10.

IMO, the versions should be 2.07, 2.08, and 2.09. Then, 2.10 would make a bit more sense !
[Verizon Samsung Galaxy S III] rhamorsky:
settings>interface>tablet settings>dpi
[Verizon Samsung Galaxy S III] hallstevenson:
The version sequence is 2.7, 2.8, 2.9, 2.10. Liquid was planning on making a substantial jump from 2.9 to 3.0 (going from Android 4.2 to 4.3 (which they still kept with 2.10), Halo 2, etc, etc) but there were issues, so they rolled some things back and put out a smaller update, hence 2.10.

IMO, the versions should be 2.07, 2.08, and 2.09. Then, 2.10 would make a bit more sense !

---------- Post added at 04:46 PM ---------- Previous post was at 04:42 PM ----------

Ahhh, okay.... The issue with Google Services running (a lot) and using battery life has nothing to do with this though. This is dealing with changing the DPI and then the Play Store not liking your phone (I've encountered this in the past) and telling you apps, that you may have currently installed, are now all of a sudden "not compatible with this device". I manually cleared data for the Play Store and Google Services while I guess going through this method will do it for me.
[Verizon Samsung Galaxy S III] RayMcGrath:
That's what I've been saying... Is it a new way to count? :confused::eek:
[Verizon Samsung Galaxy S III] ridenickel9:
Did that over and over yesterday fully agree. 2.9 for me for now to avoid a strobe light screen. Guess Nolam and I are fighting a ghost!
[Verizon Samsung Galaxy S III] eXPilce:
that sense of counting would be wrong. It would make 3.0 become 3.00 or rather in your format 3 no dot. In the fashion of liquid's versions, when a small fix is introduces 2.10 would become 2.10.1 not 2.11. With a new version becoming 3.0(.0). Of course versions could start at 1 making 2.0 become 2.1 and and 2.10 to become 2.11(.0) therefore the would never be a 2.0 version assuming the very first version would have to have been 1.1 not 1.0. Confused?

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

Respect!!!

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

Sent from my GalS3xy SCH-I535 now Free
[Verizon Samsung Galaxy S III] RBarnett09:
Had to switch back to 2.9 today.

3.0 GPS will not lock or determine my location for directions, which is a must have with my job.
[Verizon Samsung Galaxy S III] Nolam20:
Damn ghosts. Hopefully the next build will fix whatever this issue is!
[Verizon Samsung Galaxy S III] rossbeck:
Anyone else notice that status bar icons (4g,3g,wifi) don't turn blue?

Everything is working but for some reason they are not indicating an Internet connection. Using 2.10
[Verizon Samsung Galaxy S III] krwdre:
Hey everyone, I was wondering if I could dirty flash 2.10 over 3.0. Has anyone done this with no problems? Thanks.
[Verizon Samsung Galaxy S III] Stolly08:
It doesn't have to do with what the LCD density but u just use the directions I said to fix the Google services from doing what its doing... I had it happened and that's just the easiest way to fix it...
[Verizon Samsung Galaxy S III] jsdecker10:
:confused: This is soooo strange that there are sooooo many people on Liquid 3.0 and Liquid 2.10 that are just having issue after issue after issue. I don't know what's causing this rampant misfortune amongst all these different people's phones, but my d2vzw hasn't even had the slightest problem with Liquid's 3.0 on either BMS or KT747. The worst thing that I spent some time dealing with was my screen rotation problems while in texting apps. That was a P.I.T.A., but after some tinkering around, it was just due to a setting that I needed to change within the apps themselves....it wasn't anything ROM/kernel related. I ran the BMS kernel for a week or so and ended up making the switch over to kt747 because I love having my ktweaker app! :) So far everything has been running great(*knock on wood!* lol)...let's hope it stays this way! hah ...maybe I'm just one of the lucky ones?
[Verizon Samsung Galaxy S III] LuigiBull23:
Count me in there as well :)
[Verizon Samsung Galaxy S III] Stolly08:
On the newest 2.10 and no issues besides I can't seem to fond how to turn off the vibrate when typing... I don't see it in the language and input like it normally is...
[Verizon Samsung Galaxy S III] eXPilce:
Is that setting under each keyboard settings?

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

Respect!!!

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

Sent from my GalS3xy SCH-I535 now Free
[Verizon Samsung Galaxy S III] Shakes The AssClown:
I am on 2.10 official. I followed the directions and I did a full wipe as well and this has been running great for me.
[Verizon Samsung Galaxy S III] rhamorsky:
look in settings under sound. there is an option for vibrate on touch....go figure:eek: also in language and input under android keyboard there is an option for vibrate on keypress
[Verizon Samsung Galaxy S III] jsdecker10:
I ALWAYS do a full wipe, regardless of what I'm flashing. For the most part though, I have been on Liquid's ROMs for over a year or so without any of these major issues others are describing. I "swear by" always doing a full wipe. It's just the smart thing to do, in MY OPINION. I don't see why anyone wouldn't want a "fresh start" on a "clean slate." To me it just seems like doing a full wipe just pretty much rules out a lot of potential errors or conflicts. Maybe it's just in my head, but this is just MY practice.
[Verizon Samsung Galaxy S III] hallstevenson:
If one didn't do a full wipe and has any issues, the first step is do a full wipe and reinstall the ROM. Full wipes are NOT always necessary - I dirty flash all the time and 90% of the time, it's fine. But if I have any issues at all, I know I'm probably going to have to do a full wipe.
[Verizon Samsung Galaxy S III] tekhna:
Is there a suggested or required radio for 2.9/2.10?
[Verizon Samsung Galaxy S III] hallstevenson:
Developers generally aren't going to test multiple radios, so they almost always say to use the latest.

That said, I'm 99% certain that a certain radio is NOT required. If your current radio is working fine, don't change it.
[Verizon Samsung Galaxy S III] kerfex:
I'm one with issuses

Ok, been flashing for years. This is my 4th android phone and have been running custom Touchwiz roms for the last year. Got tired of TW and missed AOSP so went for LS. I have been running 2.9 with the BMS kernel with no issues except the know wifi under 5GHZ wont connect to some channels. So I decided to upgrade to 2.10. I always full wipe, and wipe the cache and Dalvik. Usually 2-3 time to make sure the wipe got everything.

Flashed 2.10 and BMS Kernel and it would boot loop. So I pulled the battery and wiped again and flashed 2.10 without flashing the BMS kernel. Worked fine or so I thought until I got a call. Phone kept crashing and when it finally did work and I minimized it, the was no phone HU notification in the pull down notifications like there usually is. After that Android keyboard stopped working. Anyone experience this? I'm back on 2.9 and now Google search keeps crashing. Strange....

I have to update my sig.........
[Verizon Samsung Galaxy S III] rhamorsky:
are you using the latest gapps listed in the OP?
[Verizon Samsung Galaxy S III] jsdecker10:
Yea. it's not NECESSARY by any means, but it's just a little extra insurance. It's most definitely not any guarantee that you're going to have a problem free setup, but it sure does help the situation a little bit. I'm almost positive that there's no fool-proof method of flashing/installing a ROM, but I feel that a "full wipe" is definitely worth any additional, minimal amount of time and effort involved. By all means, to each their own, but I just prefer this method over "dirty flashing." ;)
[Verizon Samsung Galaxy S III] RBarnett09:
[NEW] Liquidsmooth Bubble Wallpapers by RBarnett09

Okay guys and girls, I know some of you have been awaiting my Liquidsmooth wallpapers to release that will better suit your theming needs. Since Liquid forgot to add them to the 2.10 release, I will release them right here. I will remind you that these wallpapers are the same style. Previews of the wallpapers are available via the link. To download, click direct download or the download icon at the top right.

These will save to your gallery. Once downloaded, find in your gallery and set as wallpaper.

Enjoy.

Black:

https://db.tt/a7VmfM10

Blue:

https://db.tt/46kn5sJO

Green:

https://db.tt/sNcfqDv4

Neon Green:

https://db.tt/1zKPBeKD

Orange:

https://db.tt/Xw2HKzH3

Pink:

https://db.tt/d9cgRySG

Purple:

https://db.tt/fbIb95zA

Red:

https://db.tt/CWIsaoNW

Yellow:

https://db.tt/s5YqoWQ2

*Credit to team liquid for the wallpaper design. All I did was add new colors*
[Verizon Samsung Galaxy S III] crjjr:
Did you ever figure out where turning off vibration for typing is???
[Verizon Samsung Galaxy S III] helobubba88:
See post 5884.
[Verizon Samsung Galaxy S III] Stolly08:
No and post 5884 was not right... There isn't anything in settings for it or language and input like I said in the op....
[Verizon Samsung Galaxy S III] crjjr:
Thanks, but I just found it. It's under the AOSP keyboard options, even if you have voice typing selected, for anyone still looking.
[Verizon Samsung Galaxy S III] geeheeber:
Just flashed this and I have no data. I had a 3rd party flash the phone to Page Plus, and that worked great. I was using AOSPA paranoid android 3, but wanted to switch things up. I have googled and I can't find anything I need to do to get data working. Any suggestions? I need some help, as I'm having a bad time with some broken ribs and collar bone and midterms. This was a bad time to flash my phone, and I should know better.

Please and thank you!
[Verizon Samsung Galaxy S III] Droid316:
You need to flash all three files at once as this is a 4.3 problem and not Rom specific.

ROM_GAPPS_KERNEL all in the same session.You can just reflash those now without having to start all over and erasing your files.

™ Sent From My SLIMROM BUILD 1.6- 4.3 Rom Running BMS Kernel With Killjoy Script Powered By 7000MAH Of LEMON JUICE Power™
[Verizon Samsung Galaxy S III] rhamorsky:
@ Stolly08, Excuse me for not being more accurate. It IS correct in language and input and "Android Keyboard (AOSP)". On my phone, thats where it is and always has been on this ROM:D
[Verizon Samsung Galaxy S III] flydeep:
Buggy camera app on 2.10

The phone has been working great, was clean flashed as per instructions.

The camera app works well when it starts but there were numerous occasions during the weekend get together that it came with a blank screen. Going to home screen and restarting camera didn't help. The only thing that made the camera start was a reboot. Even after a reboot, starting the camera after few times would give a blank screen without response. Another reboot was needed. Has anyone faced these issues on the newer 2.10 rom?

If I would like to update/go back to an earlier stable camera app, is there a way I could do that? I care much less about the panaromic mode. In fact I preferred the 4.1 camera which had the pause option in video mode, it was extremely useful.
[Verizon Samsung Galaxy S III] eXPilce:
So I was right in post 5882 and which Rhamorsky reconfirmed in 5884.

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

Respect!!!

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

Sent from my GalS3xy SCH-I535 now Free
[Verizon Samsung Galaxy S III] joshua5683:
This rom is legit.
[Verizon Samsung Galaxy S III] doodlebro:
can anybody explain to me why TWRP has such a hard time reading the filesystem as if it's encrypted from the start?

Titanium backup tried to restore my android ID, but it hangs on the reboot and I'm forced to reflash >:(

Really upset with how ****ing difficult it is to install this... No instructions to install anywhere to be found!

Yeah, this rom's "great"

Oh, it just wont ****ing reboot no matter what I do. Man, what a fantastic ROM!

Try including a SIMPLE instruction, it goes a long way. I went back ten pages and found nothing to help me.
[Verizon Samsung Galaxy S III] hallstevenson:
Instructions are in this thread...
[Verizon Samsung Galaxy S III] doodlebro:
Not in the OP. Where?

Edit: Well, after successfully soft bricking my phone, reflashing CWM, and installing another ROM, I was able to get this one working.
[Verizon Samsung Galaxy S III] eXPilce:
I concur about the instructions not being readily available on XDA. The instructions are on the Facebook page (which is the last place I looked) should not be that you have to scour the web or XDA to get up-to-date info, only to get reprimanded that you didn't follow infarctions when you get/have problems.

Lots of Love for LiquidSmooth!

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

Respect!!!

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

Sent from my GalS3xy SCH-I535 now Free