yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] Perseus:
You are supposed to press the button at bottom center of the screen. The one that looks like a phone keyboard
[Verizon Samsung Galaxy S III] Droid316:
I do that it just has a blank screen with the phone on the bottom.not until I Swype the center of the screen it Will show my contacts then the dialer pad will show back up.I was on the latest weekly when it did that so I went back to the stable and it still had it, even did a dalvik wipe and cache wipe I still have to Swype it to work
[Verizon Samsung Galaxy S III] Sycobob:
Now that there's an official 4.4 release, our phone should no longer be blacklisted on Google Wallet right? Is there any way to get it working now without changing our build.prop to spoof a nexus or something?

Also, for the last several versions of the ROM there's been a bug with lockscreen rotation. After a clean flash, the lockscreen will rotate, but if you go to the settings it's actually set to not rotate. You have to enable and disable it for it to stop rotating.
[Verizon Samsung Galaxy S III] jonny30bass:
I too have the lockscreen rotation bug.
[Verizon Samsung Galaxy S III] jonny30bass:
I believe that I may have found another bug. If I try to use a custom lockscreen slider target icon (by choosing gallery instead of system icons), then it just appears as fully transparent. I have tried many different icon sizes all formatted as png, but they all appear fully transparent.
[Verizon Samsung Galaxy S III] Perseus:
Thanks for mentioning! Can you be kind to get screenshots ?

In case of the first issue, no screenshot needed
[Verizon Samsung Galaxy S III] jonny30bass:
The icon I want to use from the gallery:

The result:
[Verizon Samsung Galaxy S III] Perseus:
Between the two cases, which icon on the Lock scree you were trying to change ? Since they both look identical, I am not sure.
[Verizon Samsung Galaxy S III] jonny30bass:
There is only one case. I was trying to change the icon for the calculator app with an icon from my gallery. The top picture is the icon that i chose. The next two pictures are what it looks like in the slider targets settings. The last picture is what it looks like on the actual lockscreen. There should be eight icons on the lockscreen, but there are only seven because the calculator icon is fully transparent for some reason.
[Verizon Samsung Galaxy S III] Perseus:
Ok Got it. Thanks.

I didn't realize until now that the missing calculator is on 4 O'Clock Position.
[Verizon Samsung Galaxy S III] skytbest:
Just installed latest weekly (6.8) and my wifi will not turn on. When I go to the wifi page it is stuck at "Turning wifi on.." I'm using the latest KT747 kernel

Is this a common issue? Any ideas how to fix this?
[Verizon Samsung Galaxy S III] jonny30bass:
Yes it is common if you are using an old kernel on a new ROM build. The only way to fix it is to wait for a new update to the kernel that you are using. Or you can use a newer kernel. WiFi modules are now built into the kernel.
[Verizon Samsung Galaxy S III] tvl76:
Try this:

turn off WiFi

turn on airplane mode

turn on WiFi

turn off airplane mode

See if that gets you connected
[Verizon Samsung Galaxy S III] SlimSnoopOS:
This will not work. They need a kernel built AFTER 7/27. Lots of kernel changes that also impact wifi connectivity from CM.
[Verizon Samsung Galaxy S III] tvl76:
Works for me with 7/14 BMS
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Hmm, I wonder if the latest wifi module commits aren't in SlimKat 6.8 then?
[Verizon Samsung Galaxy S III] Perseus:
Yes it is.

https://gerrit.slimroms.net/#/c/11890/
[Verizon Samsung Galaxy S III] NMEAGENT:
My phone dies (turns off automatically) right when it gets to 10% if I boot it back up it will turn off again is this normal?
[Verizon Samsung Galaxy S III] Perseus:
Signs of dying battery in my opinion.
[Verizon Samsung Galaxy S III] griz.droidx:
I haven't been on any newer ROMs in over two weeks. Has anyone heard about progress on the new theme engine implementation?
[Verizon Samsung Galaxy S III] savagebunny:
Figured you guys would like this... Maybe. Using ZeroLemon 7000mAH battery btw
[Verizon Samsung Galaxy S III] uberbdon:
With the latest weekly I've got a couple issues that may be related. I keep getting a message to reinstall google+. Also, in the play store, all of the apps that I have purchased shows not purchased so I'd have to buy them again to download and install them. Anyone else seen this issue? I've tried it with multiple different gapps with the same issue.
[Verizon Samsung Galaxy S III] radici:
I'm on build 6 official 5242... Full wipe. Camera doesn't work (cannot connect to camera error) . For more clarity this is a sch-s968c model. Any suggestions?
[Verizon Samsung Galaxy S III] deuce237bblock:
I sometimes get that error, a simple reboot fixes it but if that doesn't work try clearing caches.

Sent by me.
[Verizon Samsung Galaxy S III] pyrite123:
Could you please tell me what theme this is? I love the notification panels and toggles!
[Verizon Samsung Galaxy S III] Perseus:
Add a different Google account on the phone then remove the main Google Account from the phone, reboot and then add the original account. If that didn't help, do a Factory Reset.
[Verizon Samsung Galaxy S III] uberbdon:
Each time I flash I do a factory reset. I'll give adding another Google account a shot, thanks.
[Verizon Samsung Galaxy S III] Perseus:
Please see #2213by [MENTION=3698016]jorv976[/MENTION]. Contact that user if necessary.
[Verizon Samsung Galaxy S III] Perseus:
Has Anyone tried this Mod ? Although posted on Sprint Forum, its CM Specific not Sprint.

[MOD] Increase Over all Sound Volume CM11 4.4.2 (Flashable) (01-25-14)
[Verizon Samsung Galaxy S III] lZnGl:
Is there any further development on the boot time issue? I just did a soft reboot and it took well over 10 minutes
[Verizon Samsung Galaxy S III] Magicman500:
Does stable 7 suffer from the boot time issue?
[Verizon Samsung Galaxy S III] Perseus:
Yes we identified the issue based on the Logs provided. The issue was fixed in the subsequent releases. Try the Stable 7.
[Verizon Samsung Galaxy S III] lZnGl:
Thanks for the quick reply buddy, I appreciate all the work you guys do for my favorite rom!
[Verizon Samsung Galaxy S III] Fivecent:
Installed it and damn does it work. Max volume is a little too high and will distort the sound, but it's good to know that I can put it up to 11 if necessary.
[Verizon Samsung Galaxy S III] savagebunny:
So to clarify, saw a post of someone running 4.4.4 and using the NE1 baseband, we can flash the latest and still able to have root/flash new roms/working recovery?
[Verizon Samsung Galaxy S III] Perseus:
Even on the lowest setting, the volume is too loud for me. So I am not sure if I want it this high. So I am going to incorporate it in the next weekly but with slightly lesser volume than this. Thoughts ?

Yes.
[Verizon Samsung Galaxy S III] NMEAGENT:
That would be nice! The volume is also too loud for me with this mod but with slightly lesser volume it would be perfect.
[Verizon Samsung Galaxy S III] savagebunny:
Thanks man. Is there a specific NE1 AIO that I need to download? Because I've noticed with all my Android phones in the past, you gotta make sure you flash sometimes only the modem, and not the full AIO w/ Firmware so you don't lock the bootloader.

Information is scattered atm, digging through rootzwiki, and here
[Verizon Samsung Galaxy S III] Fivecent:
Fine idea. The mod seems good as a proof of concept, but the volume can be so loud I do wonder about potential hardware damage. I can't see any problem bringing it down a notch or two.

Absolutely incorporate it though as low volume, especially for the speakerphone, seems to be a pretty general complaint of CM11 roms.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Nope. For unlocked bootloaders, all we can flash from TouchWiz OTAs is VRUCML1, VRUCNC1, and VRUDNE1 modem ONLY.
[Verizon Samsung Galaxy S III] jhoutz:
I've been editing that sound file to fix the sound manually for a while. Usually set all the volumes at 73%. Seems to work well.

Glad to hear that its being incorporated in this ROM.
[Verizon Samsung Galaxy S III] Perseus:
Thanks for the feedback. this will be incorporated in the next weekly. But I have reduced it a notch. Now if its too low, I will jack it even further. Good to know the rear speaker is particularly affected. Please let me know after next Weekly. I did contact one of the CM developers for them to include the fix. But dunno, if they'd care to include.

Speaking of Weekly, please bear in mind, I have some secret sauce mixed into the Kernel. The testing so far has shown that there are two effects. First one is that, it shot your AnTuTu Score up by 200 to 700 points. The second effect is that your network speeds and performance has gone up. This applies to both Data and Wireless network. The amount of improvement you'd see depends on your network coverage or your Router.

Keep in mind, these changes are in the Dalvik for Kernel. So if you flash another kernel or changed to ART, you won't see the effect.

So Stay tuned for next weekly!
[Verizon Samsung Galaxy S III] Durhammer:
Dirty flashed the Stable 7.0 and am getting pretty frequent random reboots. It also goes into this thing where it does the reboot vibrate several times in a row but no screen activity. Does this sound familiar to anyone?
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Do not dirty flash and post about your issues. I clean flashed stable 7 upon release. For any given weekly, I do not get a random reboot more than once or twice in a week and I always clean flash. I'm operating on 80 hours of up time right now, used Google Maps all day the last two days, lots of LTE use, listened to couple hours of podcasts, usage of a variety of apps, restored all apps with data using Titanium Backup, running ART, and using BMS kernel. Consistently smooth performance. All that and I have one random reboot since release.
[Verizon Samsung Galaxy S III] deuce237bblock:
I'm on stable 7 with TRDS enabled and my play store is not themed. Is this a gapps issue or an issue on my end?

Sent by me.
[Verizon Samsung Galaxy S III] netlagger:
I am currently on AllianceRom and am trying to flash SlimKat 7 stable. I keep getting an error in recover when trying to flash. It's saying can't execute unpacking command. I am using twrp 2.6.0.0, is that an issue?
[Verizon Samsung Galaxy S III] Malave:
Try updating your recovery to the latest version. I used the latest philz recovery without a problem. Good luck the ROM is worth it.
[Verizon Samsung Galaxy S III] Perseus:
I don't see why that version would have an issue. But latest TWRP 2.7.1.0 will get the job done.

Pay close attention. ABOVE the message of Can't execute Unpack, there will be additional error messages. Potentially this could be like "Assert Failed" or something similar. That is the "Real" error why you are not able to flash.
[Verizon Samsung Galaxy S III] netlagger:
If it is the "Assert Failed" message, then what is the cause of that? Bad download perhaps? or is it something more serious?
[Verizon Samsung Galaxy S III] Perseus:
No Not really. It just means Alliance rom has set your Build.prop to something the Rom Updater script didn't like. You could either format /system, /data, Dalvik and Cache then try or you can flash whatever samsung firmware you had before Alliance.
[Verizon Samsung Galaxy S III] Farabomb:
I noticed this too. If I update gapps I loose the dark slim theme. Tried switching it off, installing then turning on dark and still no dark theme in gapps.

I will try a factory reset and the 7.2 weekly and that should fix it.

I also notice a weird issue that has gotten worse with the newer releases. Waze will have no issues with GPS my whole hour commute into work. On the way home is a totally different story. Constantly loosing lock and the only thing that will sometimes fix it is a reboot. I don't think I've ever gotten all the way home without a GPS issue. It may stem from the fieldtrip app I have. I uninstalled that to see if it gets better.
[Verizon Samsung Galaxy S III] netlagger:
Yeah, before AllianceRom I had HyperRom. I will give all that a shot tonight. See how that goes for me. Thank you for the advice on it all.
[Verizon Samsung Galaxy S III] Perseus:
No Not that one. I meant Samsung firmware that you flash via Odin.
[Verizon Samsung Galaxy S III] NMEAGENT:
I'd say it is much easier to just wipe /system and factory reset before flashing. I do this every time I flash a ROM and I haven't had a problem yet.
[Verizon Samsung Galaxy S III] netlagger:
Ah gotcha, the one before I decided to go custom. I have that somewhere. It is the route66 one. I will give that a shot tonight. When I am safe at my home pc and not at work, lmao.

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

Yeah, I thought I did wipe /system last night. Still got that failed. I will definitely try it tonight. Been so long since I have done this. Maybe I am getting rusty and forgetful or something. Who knows.
[Verizon Samsung Galaxy S III] BattsNotIncld:
7.2 running great with Leankernel 9.9. I did a full wipe, clean flash. Boot time is normal. ROM is smooth/snappy as usual. Also noticed a increase in cell signal strength which is a nice surprise. Around 10 dbm. Not sure if it's ROM related or Verizon upgrading towers around me. I'll report back when I travel around a bit more.
[Verizon Samsung Galaxy S III] Farabomb:
It is providing you have a fast data connection at home. It takes hours for me to download all the apps.

Clean flash and play store does not have the dark theme. :(
[Verizon Samsung Galaxy S III] dpeeps74:
No, there were changes on the app side for some gapps and they're no longer able to theme them the same way.
[Verizon Samsung Galaxy S III] tvl76:
Google now is not dark either
[Verizon Samsung Galaxy S III] savagebunny:
Is the new weekly out with the fancy network tweaks you mentioned a few posts back?
[Verizon Samsung Galaxy S III] Farabomb:
Not a big deal at all. Still the best rom I've ever had on this phone.

Thanks for everyone that puts all the time and effort into it.
[Verizon Samsung Galaxy S III] netlagger:
Probably a stupid question, but what happened to the reboot recovery and download options in the power menu? Anyway to put those back or add them in?

---------- Post added at 07:31 PM ---------- Previous post was at 07:24 PM ----------

Where did you get Leankernel 9.9?

Never mind. I found it, lol
[Verizon Samsung Galaxy S III] NMEAGENT:
Settings> Security > Advanced Reboot
[Verizon Samsung Galaxy S III] netlagger:
Thank you!
[Verizon Samsung Galaxy S III] Perseus:
Afraid not. CM pretty much crapped out the branch and are now cleaning up. We have cascading effect and I have my hands full. I did however got the Sound Volume change in. But that will go in next weekly. I am hoping to make my network changes by then too.
[Verizon Samsung Galaxy S III] RedRumy3:
My gmail is loading images now with latest weekly and gapps! Woot. Not sure what changed but its finally working :D
[Verizon Samsung Galaxy S III] savagebunny:
Ah okay man. I did see the change log notes for the sound volume. Wasn't sure if there was gonna be a ninja affect insert of the network changes. What a bummer. I want a excuse to fully wipe my phone and move from 6.8 currently :P
[Verizon Samsung Galaxy S III] Perseus:
Wait for next weekly. I hope the crap is cleared out by then.
[Verizon Samsung Galaxy S III] infsoul:
what is going on when some app will not open I will select them and they will go dark as if they are about to open but then they do not some random apps will open when I select them but then eventually none will open and I have to restart this happens after being on for short or long time I'm on latest stable clean install
[Verizon Samsung Galaxy S III] dpeeps74:
Hmm, that didn't happen to me until 7.2 so I just flashed 7.2.1
[Verizon Samsung Galaxy S III] Perseus:
I am personally on 7.1 that I had ran 3 weeks ago. I just now made me a new build. One with the sound mod. Will test it for this before submitting to next weekly.
[Verizon Samsung Galaxy S III] Blaiser47:
This app not opening happened for me on both of the latest weeklies but not on stable 7.0 so reverted for now. This was on a dirty flash though. Clean flashers of latest weekly, are you getting the apps not opening issue?
[Verizon Samsung Galaxy S III] Perseus:
Did it go away with 7.2.1 ?

No I am not. I dirty flashed 7.2.5 today. I will keep a lookout for this. May go for a clean flash later.

To all of you, if you still experience this, will you be kind to grab a Logcat for me ? Syslog will do the job nicely.
[Verizon Samsung Galaxy S III] dpeeps74:
I just flashed it yesterday so I'm not sure. I only saw it once and got to wondering if it was related to the problems introduced in 7.2. I had an app hang up my phone and saw it after that. I just knew that before 7.2, even though the app does run a bit dogged on my phone usually, I hadn't had it completely hang. It happened with multiple apps though, some would not open at all, some would just give a black screen. Launcher seemed to be working fine at the time.
[Verizon Samsung Galaxy S III] Perseus:
Did you have a lot of things going on in the background at the time ?
[Verizon Samsung Galaxy S III] Malave:
I got the black screen when selecting the torch from the tiles and had to reboot. I'm on the 7.2 weekly, everything else is working great.
[Verizon Samsung Galaxy S III] dpeeps74:
In my instance I do believe that an app helped the issue occur but otherwise the phone seemed to respond normally. I'm keeping an eye on it. When I drive home I'll even be using that same app. I honestly don't know if it was rom or app related or a combination, only that I saw the same end result. So far it hasn't happened since I flashed last night.
[Verizon Samsung Galaxy S III] savagebunny:
Question, what does anyone recommend for TCP Congestion control? I've just upgraded my house to 802.11AC and using my GS3 on 5Ghz... Still seems slow loading webpages sometimes. Have optimized DNS also on the router too
[Verizon Samsung Galaxy S III] Perseus:
Slim Kernel supports Cubic and Reno algorithms. I had a special build which had turned on Reno. But with the recent CM Branching and remerging of stuff, that change is gone from recent builds. If you want to test, I can PM you a link to download that build.

I do plan on turning that back on in future builds. But fo now I have to deal with this branch cleanup.
[Verizon Samsung Galaxy S III] savagebunny:
So general idea is use Cubic/Reno or use Westwood? I'm always wondering because there isn't much documentation on it, nor do I know of a test method of which one is the best/good/worst.

I'll take you up on the offer on the build. What does the build all entail then?
[Verizon Samsung Galaxy S III] Perseus:
Well Our kernel only supports those 2 for now. So that's your choice. I went for Reno as Cubic isn't really suited for Cellphones with varying signal strength of Data.

The testing is pretty simple. You use FCC Speed Test App. Make sure the app connects to the Same Server repeatedly. You do a speed test before and after. There are more complex and involved tests but this is the simplest.

Check your PM.
[Verizon Samsung Galaxy S III] savagebunny:
Okay will do. Forgot to mention that I was on a custom kernel, but I'll do a nandroid of my current. Fresh Flash and use the FCC App and see how it goes. Looks like i'm gonna have a issue with consistently using the same server, it's automatically switching me between D.C and Chicago :/

Flashed it, been staying on Chicago

So FAR:

ISP Advertised Speed - 20/2

Asus RT-68R / Wireless-N / 150Mbps according to phone

Chicago - Reno

22.40 / 2.22 / 56 ms / 0% Packet Loss

22.42 / 2.16 / 59 ms / 0% Packet Loss

20.57 / 2.24 / 62 ms / 0% Packet Loss

Chicago - Cubic

22.46 / 2.10 / 61 ms / 0% Packet Loss

22.52 / 2.20 / 57 ms / 0% Packet Loss

20.92 / 2.17 / 55 ms / 1.75 % Packet Loss
[Verizon Samsung Galaxy S III] ben999_:
Seems to me this is kernel related. Haven't seen the issue with kt747 or BMS kernel.Latest builds of SlimKat with kt747 have bug that WiFi cannot turn on. Using BMS in the meantime. I should mention I did experience the same bug with the stock kernel. Could be a coincidence but not sure.
[Verizon Samsung Galaxy S III] tvl76:
BMS 8/6 works really good with slim7.2
[Verizon Samsung Galaxy S III] Perseus:
Thanks for sharing.

Don't suppose you captured similar before flash ? If you have restored the nandroid, perhaps you can run again ? See if there's any improvement on before. Cubic's download seem better but are you sure the change did stick after reboot ?

I have incorporated the same changes to current code base and have a build flashed on my phone right now. Going good so far.
[Verizon Samsung Galaxy S III] dpeeps74:
My phone flipped ass this morning. I clean flashed then when I finally got it booted up, no service. Verizon showed my phone as suspended so I reenabled it and show connected to LTE but I have some persistent notification saying that I have no service even after hard setting to Verizon.
[Verizon Samsung Galaxy S III] Perseus:
Is your IMEI Ok ?
[Verizon Samsung Galaxy S III] dpeeps74:
Nope, shows 0
[Verizon Samsung Galaxy S III] Mystique:
Audio phone disconnects..

Where I work my mobile phone has terrible coverage.. due to the structure I work in.

So we have wifi, but people regularly need to leave the building to make a phone call.

What has been happening as of late is that, I will walk outside (still having wifi) and get cellular signal; place call and start talking successfully wifi still running.

When the wifi signal is out of range (again very very close to the building); when wifi hangs up and switches over to vzw data; the phone conversation also disconnects.

Turning wifi off before starting the call results in the same as there is no mobile data, but when mobile data kicks in; all current voice calls are disconnected.

Then when 3G might possibly go to LTE (depending on the clouds in the sky or direction of wind) it then disconnects the audio to make LTE work..

Does this happen to anyone else?

I am on 7.0 stable, just switched to BMS (great kernel btw), running MF1 baseband.
[Verizon Samsung Galaxy S III] Perseus:
Ok so that's the reason. See if you took a backup of EFS Partition AKA NV Backup. If not then you'd have to go back to stock via Odin to restore it.
[Verizon Samsung Galaxy S III] dpeeps74:
yeah, i was afraid of that. any advice on where to get odin, because quite honestly, every attempt I have ever made to find it was full of malware.

hmm, looks like i found one that should be good...now just trying to find something I can odin. this is how my last 2 months has gone.
[Verizon Samsung Galaxy S III] savagebunny:
Hello, I have restored my Nandroid backup which is 6.6-5730 weekly, but I am using DKP 3.4.95 05JUL14 kernel build with many different congestion control options.

I know it isn't the same kernel, but would you like me to run tests with this cubic/reno and various others? my internet is stable atm and no usage besides me like last night, so I should have great accuracy across the board.
[Verizon Samsung Galaxy S III] Mystique:
tcp congestion control is not a one time thing or one size fits all.

3G is different than LTE, and every site you connect to will be different as well.. You do not have a proxied connection that you are trying to make better..

Westwood is good, hybla is good, cubic is good, etc.. they all are good; that's why they are there..

But are they applicable to what your goal is.. that is left up to the end user to decide.

Wireless (cellular) networks will have latency. Wifi will have a different latency..
[Verizon Samsung Galaxy S III] savagebunny:
Yes I understand what you're saying. Guess I had the wrong goal in site. As you said each type of connection is differnet. It was just food for thought at first to see if I could offer any results.

Sorry, in zombie mode atm, been up for 28 hrs