yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] Stealth111:
DUDE!!!?//#$#^# Seriously??????????

Masta, I think that the OP needs updated to remind people to stop with the constant comments about other peoples stuff breakin your builds. It is obvious that most people don't take the time to read all the posts...
[Verizon Samsung Galaxy S III] cynikalJ:
I read all the posts and I am running the 8/13 build with the kernel we must not speak of lol. Its running flawlessly. But I have used yet
[Verizon Samsung Galaxy S III] sbattosai:
Edited.
[Verizon Samsung Galaxy S III] mastamoon:
:banghead:
[Verizon Samsung Galaxy S III] SubwayJrd:
I agree with mastamoon, please don't ever quote a problem on a thread when you have deviated from what has been provided (for example, a ROM like CM 10.2 includes ROM (android core), a KERNEL, etc. by itself), if you've flashed any kind of Mod, Kernel, etc. over the provided, DO NOT REPORT IT. You are muddying the water for people who are here to know about the PROVIDED ROM, not your extras.

It also doesn't help the devs for you to say "I've seen screen flickers" when it isn't any kind of their fault.
[Verizon Samsung Galaxy S III] Zacharybinx34:
So what's the point if it's mere placibo? Why create the illusion of a better signal if it's not?
[Verizon Samsung Galaxy S III] Restola:
to make the bars match how TW displays based on the signal
[Verizon Samsung Galaxy S III] Reborn627:
My apologies for opening this can of worms. Lesson learned.

Ray
[Verizon Samsung Galaxy S III] SubwayJrd:
It's not bad to post to forums if you are wanting to provide constructive help, here's a good way to go about it:

(in example) You notice screen flickers with CM 10.2, but you're using LeanKernel, you re-flash CM 10.2 (because re-flashing the ROM gets you back on the Stock CM 10.2 Kernel) and test for some hours/a day to see if the problem is the same. Here we branch:

1. The screen flickers stop, you post to Imoseyon's forum to let him know about this, and provide him whatever logs he asks for to help him out.

2. The screen flickers persist, you post to mastamoon's forum, letting him know that you have screen flickers on a completely stock setup.

Boom, helpfulness.

Please don't let this experience put you off posting.
[Verizon Samsung Galaxy S III] Prack:
Not trying to be rude here, I know you are a good dude helping people and all but I did want to point out that this thread is not for mastamoon's unofficial builds only. This thready clearly stays in the OP that anyone is welcome to post unofficial builds here.

Anyway the official cm 10.2 nightly is out and alerting me on my phone. I think I'm going to give it a go today and I'll let you know how it goes.
[Verizon Samsung Galaxy S III] sbenson1226:
Lockscreen slider shortcuts are behaving strangely. I'm trying to set Google Now as the left target and normal unlock as the right target. The other three targets are empty. When I click save and then lock my screen, the Google Now target has now moved to the top-right diagonal target.

I've attempted to reset this multiple times with no success. Clean flash, stock kernel, build 08/13.
[Verizon Samsung Galaxy S III] goldsmitht:
Make sure you save it twice.

when you change the shortcut, click save;

when you finish, click on the disc icon in upper right corner; otherwise it won't save the saved shortcuts.

:fingers-crossed:
[Verizon Samsung Galaxy S III] mastamoon:
There are some more lockscreen shortcut commits in the pipeline.. seems to be a WIP after the 4.3 merge.
[Verizon Samsung Galaxy S III] goldsmitht:
Yeh, but has been a common "oops" among those having problems getting shortcuts to stick. Most miss the little tiny disc icon in the upper right hand corner that has to be clicked also, otherwise all the changes that are made do not stick. Just thought i'd suggest this first before he reflashes, or something more drastic, like, i don't know, buys an apple me-phony
[Verizon Samsung Galaxy S III] PerCompLLC:
Skirting the trademark issues I see... LOL!
[Verizon Samsung Galaxy S III] khymbote:
Just had a random power off. Not able to get logcat. **edit I am on stock rom and kernel**
[Verizon Samsung Galaxy S III] BrianAllred:
I appreciate what you're saying, but I think they (being the ones who are discouraging the custom kernel reports) are more concerned about people who just say

Okay, cool, but is it also broken on the stock kernel? It needs more information to be helpful. On the other hand, I think the example you provided would be acceptable (at least I assume so, because I've done the same thing). But then that needs to be it.

Okay, bam, one post. Now that we know it doesn't happen on the stock kernel, it doesn't need to be brought up again, just as a matter of keeping the thread clean. Others with the issue can search the thread here or the thread for their kernel if they're experiencing the issue (as they should be doing anyway).
[Verizon Samsung Galaxy S III] mastamoon:
Well hopefully everybody gets the hint and can make their own decision on whether to post a certain issue since it has now been discussed on 2 or 3 pages.

I have no problem with the example provided by [MENTION=3227712]Chris Hansen[/MENTION] ...

That's informative, what I don't want is 10 people after that post saying "me too".
[Verizon Samsung Galaxy S III] Restola:
Me too, also on agreekernel
[Verizon Samsung Galaxy S III] sbenson1226:
Well aware. Thanks anyway.
[Verizon Samsung Galaxy S III] Chris Hansen:
I'm glad you guys were able to take away what I was trying to say, I always fear that, since it's the internet, my message might be misconstrued. Thanks again for making my phone rock, mastamoon! :good:
[Verizon Samsung Galaxy S III] PsiPhiDan:
It's very simple: people believe it. Look at how many people every day post that they prefer TW because it has better reception. It's unreal.
[Verizon Samsung Galaxy S III] sivarticus85:
Recently with CM I can't tell the difference in reception. I've done a lot of comparisons between TW and CM in terms of signal strength, and they are pretty much the same nowadays. In either ROM if I'm in a bad area I get bad signal, and the opposite is true. Really the only thing I've found to be different is the speed. On CM I average about 14-15MB/s, where on TW it's sometimes double that.
[Verizon Samsung Galaxy S III] khymbote:
I am seeing screen flickering in some game apps. I'm 100% masta stock. If I tap the screen it stops. I have uninstalled and installed the games again. Words with friends it happens most. Candy crush only once. I'm not over clocking anything.

I know a few had mention screen flickering already.
[Verizon Samsung Galaxy S III] goldsmitht:
which version of MASTA's are you using? Think the latest fixed most of it
[Verizon Samsung Galaxy S III] khymbote:
8/13 rom but I didn't see the newer gapps. I just installed that. Will mention it again. Is there an app that I can get a logcat to help out?

So I just tried it again after clearing and still flickering. :(
[Verizon Samsung Galaxy S III] goldsmitht:
New GAPPS

deleted -- brain farted and wasn't paying attention!
[Verizon Samsung Galaxy S III] mapatton82:
Those gapps are for 4.2.2 the correct gapps for 4.3 are here:

http://goo.im/gapps/gapps-jb-20130813-signed.zip
[Verizon Samsung Galaxy S III] khymbote:
I managed to install a logcat program run it and got the program to do it again. In WWF it happens when I go between screens.
[Verizon Samsung Galaxy S III] goldsmitht:
DOH! BRAINFART! :eek:

thanks, didn't even catch that and i even have the correct version on my phone. NOT sure of the differences tho
[Verizon Samsung Galaxy S III] Stealth111:
^^^ HAH! :laugh:
[Verizon Samsung Galaxy S III] Evil Genius Jr.:
Also CM does not support network extenders. That is the deal breaker for me.
[Verizon Samsung Galaxy S III] Chris123NT:
Works fine on my network extender, it just thinks it's roaming.
[Verizon Samsung Galaxy S III] Evil Genius Jr.:
Oh, I guess I will give it a shot then. Is there a way to remove the roaming notification?
[Verizon Samsung Galaxy S III] Prack:
Yeah mine says roaming randomly on my wifi as well. The only issue I've had is I have dual band 2.4/5g and it won't connect to the 5g. 2.4 only. It sees the 5g but just says connecting forever and won't connect. Wife's phone works fine and it worked fine on 4.2.2
[Verizon Samsung Galaxy S III] mastamoon:
8/14 build in the OP

-- camera cherry-picks got merged - removed.

-- 2 cherry-picks to add NAVBAR switch in Developer Settings (not my cup of tea but I know some of you like)

DSP Manager is forcecloseing so dont bother to go in there right now. USB dock audio isnt working (part of this whole redoing of the Settings Menu.
[Verizon Samsung Galaxy S III] posaune76:
Had this problem today w/clean flash of 8/13, stock. Previous issue had been that it was stuck just saying it was turning off; now it looks like it's trying to fool me, then comes back. Occurs for me after playing a podcast; didn't try turning off w/o having played something, but the previous issue didn't rear its head until something had been played.
[Verizon Samsung Galaxy S III] sbenson1226:
So where do I adjust the nav key timeout now?
[Verizon Samsung Galaxy S III] GatorsUF:
Hey guys, haven't tried AOSP in a while. What is the camera situation with cm10.2? Ant other big bugs?
[Verizon Samsung Galaxy S III] fireproof1905:
Has anyone tried the Official rom? here's a link

http://get.cm/?device=d2vzw&type=nightly

Noticed it's the first 10.2 nightly posted yesterday
[Verizon Samsung Galaxy S III] mastamoon:
Don't turn off bluetooth on the phone, turn off the other device is all I can offer. Otherwise force stop bluetooth service if it's locked up.

Nav Key timeout?
[Verizon Samsung Galaxy S III] khymbote:
Installed the newest rom and still having the screen flickering issues in words. its probably the way the game accesses the gpu or something. I'm not gonna make a big deal anymore after this post as it stops after I touch the screen.
[Verizon Samsung Galaxy S III] Hans5849:
http://mobile.10.2.cmxlog.com/?device=d2vzw

Official change log, for reference.
[Verizon Samsung Galaxy S III] Restola:
Anyone else Google music crash on/after 8/13? 8/12 works fine.
[Verizon Samsung Galaxy S III] BrianAllred:
No, but someone else in the thread said they had to wipe their Play Music data on the 8/13 build, so I did that before I even tried.
[Verizon Samsung Galaxy S III] sbenson1226:
Timeout of the hardware keys... back and menu...
[Verizon Samsung Galaxy S III] mastamoon:
Ah. I think there is a build.prop entry that could go along with this to disable those buttons, but technically CM is only "allowing" this for "dev" reasons so I don't think it will ever be added to do that automatically.
[Verizon Samsung Galaxy S III] sbenson1226:
Hmmm, it was in your previous build under advanced settings... always has been to my knowledge.

Just to be clear, I'm taking about the hardware keys, not the on screen keys.
[Verizon Samsung Galaxy S III] mastamoon:
Oh yeah. Advanced settings is MIA for a moment. CM is reorganizing some stuff.
[Verizon Samsung Galaxy S III] mastamoon:
I was getting some weird flicker just now while playing candy crush. It wasn't a screen on/off flicker though like what we used to call flicker, the screen was actually getting brighter then dim then brighter over and over till I exited the game.

Is this what you guys that were reporting flicker were seeing?
[Verizon Samsung Galaxy S III] sbenson1226:
I figured that was the case. Thanks man.
[Verizon Samsung Galaxy S III] Chris123NT:
I wonder if that's due to content adaptive backlight control or whatever it's called.
[Verizon Samsung Galaxy S III] mastamoon:
Really lagged the hell out of the phone at the same time. Don't know.
[Verizon Samsung Galaxy S III] blempka:
If you're talking about the lights go to settings > advanced > sensors. Last option there will turn them off. If you want the keys off there's a script some pages back that I can confirm works with this ROM.

EDIT: Just read more closely and you say advanced settings are missing. I definitely have them on the 8/13 build. I haven't tried 8/14 yet though.
[Verizon Samsung Galaxy S III] yznhmr:
I'm on 14 ever since 13 my dialer does not bring up names when I am dialing numbers if I go to call history it shows people I called but it will not populate with peoples names dialing the first few digits in the dialer. Any thoughts on how to fix this
[Verizon Samsung Galaxy S III] mastamoon:
I believe there are a few commits in the works to bring this back.
[Verizon Samsung Galaxy S III] Restola:
That worked. Thanks
[Verizon Samsung Galaxy S III] Rig24:
Anyone else having issues with trebuchet? It won't hold any changes I make to the home screen after a system crash I had on Monday (build 9). Been updating each night and no change (on 14 now). Did a force stop/clear data, no change.
[Verizon Samsung Galaxy S III] GatorsUF:
I just went from JellyBeans18 to CM10.2 and when I rebooted no apparent issues. Then I restored TiBu data on certain apps, not all, and started having issues. Mainly that Nova Launcher wouldn't load and kept crashing, tried deleting data etc...didn't work. I uninstalled Nova and now the Play Store gives me an error when I try to reinstall Nova. Either way I rebooted and I am not getting this error.

"UIDs on the sysytem are inconsistent, you need to wipe your data partition or your device will be unstable."

with a button that stays "I'm Feeling Lucky"

I was curious if anyone else has had this and if a simple wipe will fix it? Since I just came from a clean wipe I am skeptical to say the least.
[Verizon Samsung Galaxy S III] zachf714:
Did you do a factory reset when you flashed, did you restore system data
[Verizon Samsung Galaxy S III] GatorsUF:
Yes I did a factory reset, I only restored data to some user apps (ie: Falcon Pro, Feedly....)
[Verizon Samsung Galaxy S III] khymbote:
No it is kind of like a strobe light. It never turns off but this the idea.
[Verizon Samsung Galaxy S III] Hybridnoob:
I think your problem is with TiBU. Did it ask you to restore your previous ID (or something like that) when you first launched it?
[Verizon Samsung Galaxy S III] khymbote:
My brother had that happened. He flashed today's build and all his settings were gone on the launcher.
[Verizon Samsung Galaxy S III] Chris123NT:
http://review.cyanogenmod.org/47944

Wonder if this will resolve some of the data issues. I get weird data drops from time to time that I can't seem to explain.
[Verizon Samsung Galaxy S III] capt730:
Made the switch from beans18 to try 10.2. Full wipe dalvik, cache, system, data. Stock kernel. Only issue is trebuchet isn't remembering all my home screen settings. Icons will move. Icons in folders are moving out to their original spot. Wiped cache and dalvik. Still happens randomly. On 8-13 build.
[Verizon Samsung Galaxy S III] zachf714:
From what I have seen at least in my crappy service area it can help a little , I barely pick up data in my bedroom but can somewhat keep an lte connection when I get one
[Verizon Samsung Galaxy S III] SubliminalME:
Man...The build is running great! My phone is like a new phone. Just wish data was better.

Is it pretty safe to say, as this phone is coming up near the end of its time, that data will never get fixed?

Can't believe Samsung won't just release the damned modem drivers.
[Verizon Samsung Galaxy S III] PerCompLLC:
I keep seeing posts about data problems... Maybe I'm just one of the lucky ones. My data connection has never been better, or more consistent. For my device and location there is nothing that needs to be fixed. But again, maybe I'm just geographically fortunate.
[Verizon Samsung Galaxy S III] don_xvi:
Play Music app causing meltdowns

Has anyone else had problems with the music app causing major system crashes?

Last Saturday I was on one of the newest mastamoon builds at the time (I don't recall exactly which) and now this morning on the 8/14 build (stock kernel!), I've been streaming music over bluetooth and last weekend had a spontaneous reboot (I think it was when I went to turn the screen on) and today when I turned the screen on, I had a never-ending string of "System UI has crashed" cycling with another "...has crashed" message which I have to admit I've now forgotten. They kept cycling so I couldn't even unlock the phone; eventually I figured out that in the half-second between messages popping up, I could press & hold the power button to get the power-off menu to pop up, (then dismiss another crash message) and then hit the reboot option in the power menu and get out of it.

I use WidgetLocker and the phone was plugged into a charger both times. I haven't seen a similar crash before.
[Verizon Samsung Galaxy S III] locozildjiangodx:
Go into the Phone app settings and make sure Dial pad autocomplete is checked.
[Verizon Samsung Galaxy S III] SubliminalME:
That's exactly it. If you're in a location that happens to have good service, you just get good service. If you go in and out of 3g/4g a few times, and maybe pass through a region which has no service, the switching is terrible and the reception is definitely sub-par compared to even the same phone with the same baseband under touchwiz.
[Verizon Samsung Galaxy S III] Reborn627:
Ok, data drops. Is this along the lines of hand offs from 1x to 3g to LTE & Wifi? Lately I've been getting weird stuff, like no data I LTE zones and an inability to acquire a data signal after being on wifi. Seemed to have been present with 10.1 as well but I don't remember it being quite as noticeable.

Peace,

Ray
[Verizon Samsung Galaxy S III] PerCompLLC:
Understood. Didn't used to have good service, but VZW finally upgraded the tower right next to my house so I have 4G at home...
[Verizon Samsung Galaxy S III] SubliminalME:
Handshakes are definitely a beyotch. I've seen it on everything that doesn't have the original TW drivers. It stinks. It's the only thing that makes me anxious to dump this phone.
[Verizon Samsung Galaxy S III] thelangosta:
I could use some help diagnosing a major problem when moving to 4.3. I have now tried both unofficial and official versions with the latest gapps(clean flash coming from CR7). Everything boots fine and I am good to go initially. I can get everything set up app wise and then go in to developer settings to change the root permissions to apps and adb but, here is where my issues start. If I reboot the phone at all it just gets stuck at the Cid splash screen on the reboot. I let it sit there for 15 minutes and nothing so I pull the battery and reboot, still stuck on Cid. Boot into recovery(twrp) and wipe caches/fix permissions(oddly enough this fails). Reboot recovery and fix permissions works now but phone still stuck at Cid. Then I wipe the phone(not format data) to start over and reflash rom and gapps, which is successful, reboot and get stuck at the boot animation. Pull battery rinse and repeat. I had to Odin back to stock last night just to have a functioning phone. The phone is now squeaky clean including reformatting the extsd just in case. So does anyone have any ideas? To be clear this was a clean flash in the first place both times and not my first rodeo where flashing is concerned.
[Verizon Samsung Galaxy S III] yznhmr:
thats it.. thanks..
[Verizon Samsung Galaxy S III] Chris123NT:
Yes, this is exactly what I mean. I built with that merge last night so I'll see how the phone acts. Sometimes takes it a while to get in one of it's no data moods lol.
[Verizon Samsung Galaxy S III] cornelious1212:
Dirty flash of 8/14. Long press of home will no longer pull up Google Now. If I set long press of Menu to Google Now, it works fine. Long press of home only pulls up recent app switcher.
[Verizon Samsung Galaxy S III] zachf714:
Re-enable the settings for it
[Verizon Samsung Galaxy S III] tom108:
Pretty sure long press on menu has always been for Google now. My phone has always used LP+menu for GN and LP+home for Recent apps.
[Verizon Samsung Galaxy S III] cornelious1212:
Before 8/14 it was customizable. Still is, but it doesn't stick. System settings>buttons>long press home.
[Verizon Samsung Galaxy S III] PsiPhiDan:
"Page not found"...
[Verizon Samsung Galaxy S III] Prack:
try again, sorry about that.
[Verizon Samsung Galaxy S III] PsiPhiDan:
Does anyone know why after updating to masta 8/14, I'm now using my Google Voice number when I text people? It never has done that, I only use it for voice-mail.
[Verizon Samsung Galaxy S III] SubwayJrd:
Sounds like Voice+ got enabled, that is its exact function.
[Verizon Samsung Galaxy S III] PsiPhiDan:
How can I disable it? I never use it.

I already logged out.
[Verizon Samsung Galaxy S III] SubwayJrd:
Open the Voice+ app and click the disable Radio Button.
[Verizon Samsung Galaxy S III] PsiPhiDan:
I'm not seeing that option. I've looked in the menu/settings, and that bar on the left. Am I just being dumb?
[Verizon Samsung Galaxy S III] SubwayJrd:
It's literally in the App drawer as an App, same icon as Google Voice (or "Voice" in the App Drawer) has, just says Voice+
[Verizon Samsung Galaxy S III] PsiPhiDan:
I was being dumb! :p

I was looking in the Google+ app instead!
[Verizon Samsung Galaxy S III] khymbote:
Possible bad download. Sometimes I have had to flash the ROM then boot and go back and flash gapps and then the kernel.
[Verizon Samsung Galaxy S III] ugachris:
So I had the inconsistent UIDs warning recently. I googled and found a mention of it and that a fix permissions in recovery fixes it. I did that (and do that after each flash) and haven't seen this come back up. But it did scare the crap out of me the first time I saw it.
[Verizon Samsung Galaxy S III] bmeek:
From force of habit, I use the latest standard cwm (not TWRP), but when having odd and seemingly inexplicable issues like this, I'll format /system in cwm before doing a clean flash of the new ROM...
[Verizon Samsung Galaxy S III] BrianAllred:
Happened to me, I had to go completely back to stock, ROM and recovery, to fix it. No matter what I did, just kept hanging on boot after the first one. After booting into stock ROM and re-doing the root/custom recovery/custom ROM stuff, no problems.
[Verizon Samsung Galaxy S III] ctsail410:
I never tried this, but simply switching to CWM from TWRP fixed it for me. I prefer TWRP but the switch fixed the issue and I haven't had the time/desire to start over completely.
[Verizon Samsung Galaxy S III] thelangosta:
Yeah I am stock w/ root again for now. Does anyone know if our CWM recovery has been updated yet? I know Koush sent something out about having to update a load of recoveries.
[Verizon Samsung Galaxy S III] jlokos:
CWM latest is 6.0.3.6.
[Verizon Samsung Galaxy S III] jdommer:
Mine does not seem to want to switch bands. If I connect at work where I have both 5/2.4, it'll jump on the 5GHz. But at home where there is only 2.4, it'll sit at connecting. If I reboot it connects fine.

It was weird and I've given up for a while but will keep following the development and try again. Especially when fitbit supports 4,3,,,
[Verizon Samsung Galaxy S III] mastamoon:
8/15 build in the OP

-- repo sync at 3:10PM EST

DSPManager no longer force closes.. USB Dock Audio still doesnt work.
[Verizon Samsung Galaxy S III] juancaperez2000:
Excuse me Masta do you know why i can not remove the slider shortcuts on lockscreen? Is there a way to fix that?
[Verizon Samsung Galaxy S III] RED ZMAN:
Anyone else having phone locking up problems when receiving a call and it goes into landscape?

I'm trying to figure this freezing problem out. Dirty flash no mods.

There are like 4 places to pick "Auto Rotate" and other rotation options in the rom settings screens.
[Verizon Samsung Galaxy S III] mastamoon:
Works for me.

1. Choose which shortcut you want removed. From the list pick Empty. Then hit ok.

2. Hit the save icon in the upper right hand corner.
[Verizon Samsung Galaxy S III] RED ZMAN:
Also, has there been any movement on the bluetooth issue? I know there was a JIRA for it on 10.1, but I don't know if those get pulled to the new versions or not.

I ask because it wasn't too bad before, but in 10.2 it is locking up every single time it gets turned off now.

No, I still can't leave BT on 24/7. We aren't allowed to use wifi or bt at my work.