yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] jmaeishi:
Thank you very much. I can try the return to stock. I always complete wipe between installs. What perplexes me is that some ROMs work fine with just wipe (eg using 12/12 ROM now) but the two I mentioned, 2/16 and 2/18, have that prob...2/18 particularly severe, and gets worse with time.

Also I posted because it seems like this is place to post these things relevant to specific ROM; plus to let others know; plus to try to understand what causes it. I still don't know what causes it, just think it's interesting that it's ROM specific.

Thank you again I will try again
[Verizon Samsung Galaxy S III] sivarticus85:
You wouldn't happen to have Force GPU rendering on would you? If you do, either disabling it or enabling "Disable hardware overlays" sometimes fixes this problem.
[Verizon Samsung Galaxy S III] Nnyan:
Nothing too puzzling here. You never know what change may cause what effect and stop a dirty flash. I have even seen problems not start right away so just a few days is not enough to say "I dirty flsshed with no issues". And yes I make zero changes for at least a week after a flash.

This is why most mods don't want to see you post about any issue if you did not do a clean flash.
[Verizon Samsung Galaxy S III] jmaeishi:
Great idea.I'll have to try that first.

Thank you.

Also, no they aren't enabled on this ROM but maybe they are on those ones.

---------- Post added at 07:51 PM ---------- Previous post was at 07:50 PM ----------

Nah. Didn't dirty flash.
[Verizon Samsung Galaxy S III] masterxchief:
Clean install fixed the issue with the verge app :)
[Verizon Samsung Galaxy S III] anacree:
Weird thing: I flashed the latest build (I guess it was a dirty flash because I didn't factory reset, only cleared cache and the system), and when I got booted again I had lost my link to my google account. And there was no option to add it. So I went and factory reset and reflashed and it then asked me for my account info. This didn't happen the last time I didn't factory reset when flashing a new build. Is this normal?

Also, any one else having issues with bluetooth mic input in VoIP apps (such as GrooveIP or Vonage)? My bluetooth headset works as a speaker in apps like Netflix, and I THINK the mic is working in things like google now search, but my bluetooth headset doesn't want to work well with VoIP apps. Anyone else have issues with that?

Thanks for the builds though, masta! =)
[Verizon Samsung Galaxy S III] mastamoon:
new build in OP! :good:
[Verizon Samsung Galaxy S III] mastamoon:
As I stated in the OP, I'm getting some screen flicker that can be cured by the tried and true disabling of hw overlays in developer options. Most likely due to that kernel pick I cherry picked for testing for cyanogen. I'll unpick it tomorrow.
[Verizon Samsung Galaxy S III] landale:
It does seem to be the kernel as I switched to LeanKernel and the flicker went away.
[Verizon Samsung Galaxy S III] V3TTOO:
Hey Masta, would it be possible for you to include all the info you post in the OP on these notification posts?

My reason for asking is for documentation. Once you update the OP, we no longer see what changes you did to the previous build. It would be nice to go to the post and see what was on a particular build for that date/time. You currently have tearing issues with the new build, and I was looking for info on the previous build. As always, thanks for your great work.
[Verizon Samsung Galaxy S III] mastamoon:
Yeah I can do that.
[Verizon Samsung Galaxy S III] V3TTOO:
Awesome, thank you.
[Verizon Samsung Galaxy S III] cgulliver:
Still unable to use the BT voice dial with my Jawbone Era. Would it be possible to replace the stock voice dialer with Google now?
[Verizon Samsung Galaxy S III] marcviado:
Loving this ROM but my signal did decrease to 1 to no bars,anybody know a fix or another kernel that can help increase signal strength?
[Verizon Samsung Galaxy S III] chaplngrillsgt:
My first Masta unofficial and I love it!

The emoji revert makes me very happy. My gf and mom send emoji messages like crazy and I never have any idea what they are.

Signal strength is solid so far and no screen flickering. Awesome build!
[Verizon Samsung Galaxy S III] NegativeOne:
I don't get why tether security hasn't been merged yet . Those poor official folks :p
[Verizon Samsung Galaxy S III] PerCompLLC:
For me, this is the closest to a perfect build I have experienced so far! :good: Note that I am using a custom kernel (leanKernel 2.7.3)...

Thank you Masta!
[Verizon Samsung Galaxy S III] WhammyDroid:
I could say the same thing about the GPS commit. Why is it taking so long to get this commit working in the official build?

<crickets>

I am happy that masta takes the time to build this release.
[Verizon Samsung Galaxy S III] bobby janow:
Same here. If I could get the center clock w/ options and the transparent lockscreen or pulldown... Wow. :)
[Verizon Samsung Galaxy S III] PerCompLLC:
Center clock would be nice... But I don't think that CM has implemented that, so it would have to be a custom framework. I could do it, but I'm hesitant until after CM has completely stabilized.
[Verizon Samsung Galaxy S III] goldsmitht:
Masta -- thanks for all the hard work, figured i drop a beer or two in your inbox, since this is THE most stable version of any ROM i've tried on my S3. Keep trying others, but keep saying to myself, "self - why put up with crap that doesn't work" and i'm back to your builds.

thanks again for all the hard work!

Confirmation number: 70H19433WL506711P

:cyclops:
[Verizon Samsung Galaxy S III] mastamoon:
Thanks man! Appreciate it!

And thanks everybody for the kind words. Glad somebody can see the benefit of a unofficial build not having to have a fancy name or 'team' behind it. Glad I found a niche that people can enjoy.
[Verizon Samsung Galaxy S III] mastamoon:
Somebody with more skill than me should make those mods and commit them to the CM gerrit. Even if they never get merged, I would still be able to include them for those that want it. You never know how the CM team will react to something, worth a shot. :D
[Verizon Samsung Galaxy S III] mastamoon:
Has anybody seen any downsides to bumping the 'burst' speed from 1134 to 1512? I see that my cpuspy now shows 1512 being used much more often so it seems to have worked and it doesn't look like my battery life has suffered much.
[Verizon Samsung Galaxy S III] PerCompLLC:
That's a good idea! I'll look into it...
[Verizon Samsung Galaxy S III] sivarticus85:
Battery hasn't taken a hit for me. If anything, it runs way better than it did before... But that could also be from the Trebuchet commits too. Either way, rock solid work as always. The audio from the cam sounds incredible, even if it is a bit quieter than TW. It really picks up the bass beautifully, without distortion. Perhaps the lower cam volume benefits from this?
[Verizon Samsung Galaxy S III] stevey500:
Running latest CM10.1

Anyone else had issues at all when putting the phone to sleep? My phone will lock-up at the end of the "CRT Screen off" sleep animation with a white line in the middle of the screen (from the animation) and fail to sleep, it does this at random times when I try to put it to sleep until I do a battery pull and reboot. Running stock kernel, unless the latest releases have a different kernel lately. I have never flashed a kernel at all.

Thanks for reading :)

I have reflashed the rom, tried reverting back to the feb13th.zip, cleared cache/dalvik. Same deal.
[Verizon Samsung Galaxy S III] anacree:
I've had similar issues where my phone won't wake up from sleep (touch buttons light up, but not the screen). I've had it happen with the charging cable plugged in and out now. Happened twice yesterday. Doing a battery pull is the only way I've found to get past it. I can't find a way to hard reboot this phone.I'm running one build back of the ROM in the OP (2/22 afternooly I think).
[Verizon Samsung Galaxy S III] goldsmitht:
CRT OFF has been discussed in AOKP chain as well, as cause of SOD or something, but don't think they thought it was culprit. Not having any issues here at all
[Verizon Samsung Galaxy S III] anacree:
Oh, another issue I've found is that sometimes a notification of "Location set by GPS" will show up, and I can't get it to go away. Not a problem per se, just clutters my status bar at the top... =P
[Verizon Samsung Galaxy S III] bobby janow:
Open gps status, then close it.. gone.
[Verizon Samsung Galaxy S III] mastamoon:
yes that is annoying to say the least.. but known issue. Usually opening up the app again and closing will get rid of it. I keep GPS Test from the market installed for the times where it wont go away. Just open and close app. Done.
[Verizon Samsung Galaxy S III] M Diddy:
You can open Maps for this too. It'll work fine to remove the icon.
[Verizon Samsung Galaxy S III] masterxchief:
Having the same issue here multiple times a day. I had it lock up just sitting at my desk playing music earlier. I'm using lean kernel though. Wonder what the problem is
[Verizon Samsung Galaxy S III] mastamoon:
02/26 Build...

Download - http://bit.ly/128VqDz / MD5SUM - 07af33c827edf4e8ee26684c416fc458

*removed kernel cherry pick that was causing flickering
[Verizon Samsung Galaxy S III] V3TTOO:
Cool, thanks. I have been using your last build and I have not had any issues with screen flicker. Is there a particular time that it happens?
[Verizon Samsung Galaxy S III] mastamoon:
It happened to me, for example, when looking at storage in settings. Screen went flicker crazy. Steve (cyanogen) said it seems to be hardware variances that cause some people to get some not and abandoned the patch so I don't think it was just me.
[Verizon Samsung Galaxy S III] anacree:
I posted two questions in one post yesterday, and I think the second got missed. So here it is one more time...

My bluetooth headset works with media output (watching youtube videos, netflix, etc). It also works fine when I use the stock dialer. It does not work when using VoIP apps like Vonage or GrooveIP. Sound either doesn't come through the headset at all, or it starts to come through and then stops. If I switch the app over to using the phone speaker or the phone earpiece, sound is fine. I would have thought this was an issue with the app, but it happens in both Vonage and GrooveIP. I haven't yet tried any other VoIP apps. Any one else had this issue or have thoughts on this? If not, I'll shut up about it. :)

Thanks.
[Verizon Samsung Galaxy S III] mastamoon:
All audio routing right now is a bit off depending on what you are doing. I would check out cyanogenmod's issue tracker and see if it has been put up there, and if not, submit a trouble.

I think this is it.. https://jira.cyanogenmod.org/issues/?jql=
[Verizon Samsung Galaxy S III] PVLMTREE:
Is it possible if you, Mastamoon, can revert the commit that is causing us not to be able to switch to Global/GSM network? It's one of the commits on the 01.25.13 build, if it's possible for you to. If not, I guess I have to wait for a fix, because CM10.1 is pointless without data and calls due to I'm running on T-Mobile.
[Verizon Samsung Galaxy S III] mastamoon:
Your sure that the 25th build was the last one with working gsm?
[Verizon Samsung Galaxy S III] PVLMTREE:
24th was the last one with working GSM. Others have encountered the same problem. So flashing back to 24th build was the only way to get working GSM/Global Roaming. APN is correct, Phone Info Network preferred is correct.
[Verizon Samsung Galaxy S III] V3TTOO:
Wait, you saying this ROM works on T-Mobile S3? That would be cool since my friend might be getting hers soon.
[Verizon Samsung Galaxy S III] craigbailey1986:
I think he/she is saying they are using a T-Mobile sim with their Verizon phone.
[Verizon Samsung Galaxy S III] PVLMTREE:
He, haha. LOL

But yes, I'm using a T-Mobile sim for my Verizon S3. Everything works, with an exception to EDGE connection. But it's fine. I'm currently running Official CM10.1 01.24.13 NIGHTLY build, which it can be achieved. But I'm desperate for an update, due to new features and bug fixes CM has implemented; but it's not worth it if I don't have data or calls/SMS. That's my side of it. :P
[Verizon Samsung Galaxy S III] NegativeOne:
Sod is caused by low clocking during screens off. At least it has been in the past.
[Verizon Samsung Galaxy S III] landale:
I am trying to find a copy of the 1/24 Official Nightly as I have a trip to Europe coming up in 2 weeks. Would you or someone else be able to upload it or point me in the direction to it?
[Verizon Samsung Galaxy S III] mastamoon:
I cant find any officials that old. You could try http://d-h.st/kJO, its my 1/23 build, probably as close as you can get to the official from that time.

I didnt realize he said it was official 1/25 and earlier that had working GSM. You guys might want to head over to the OFFICIAL nightly thread. Somebody there might be able to help you.
[Verizon Samsung Galaxy S III] zcmack:
i'm still on CM10 because after having dealt with weak signal issues / slow handoffs from 3g to 4g for a few months, I finally found a build that worked as well as stock. It was a night and day difference, certain places where I was seeing 1 bar of service if any at all now have full bars.

I know earlier in both this and the official CM10.1 thread there were issues with weak signal. Have these been resolved? I know this is highly subjective based on location, but can anyone comment?
[Verizon Samsung Galaxy S III] Hybridnoob:
Typically, my device is showing less bars than TW on CM10.1 (Feb 26 build), as I have another S3 running stock TW to compare with. What's interesting is the signal strength db is about the same between the two phones, so really actual signal is no better or worse. TW reports more bars than CM given the same db in my experience.
[Verizon Samsung Galaxy S III] Stealth111:
Here ya go!

Filename: cm-10.1-20130124-NIGHTLY-d2vzw.zip

MD5sum: 3e02f91d018ba045ffa8b8a3e3e4f4f3

http://tinyw.in/Lavs <---- Redirects to "goo.im", a repository for D2VZW and other ROMS!

:)
[Verizon Samsung Galaxy S III] PVLMTREE:
http://goo.im/devs/cm/d2vzw/nightly

All the NIGHTLIES can be found here also (:
[Verizon Samsung Galaxy S III] landale:
I wonder what changed in the official on that day. If I recall correctly that was the day they merged in the IPV6 changes to the APN file. I can't imagine it would impact GSM roaming but maybe it did?
[Verizon Samsung Galaxy S III] s'pht:
Any chance this could be added: http://gerrit.sudoservers.com/#/c/5293/ (yes I know it's AOKP - I couldn't find a CM commit for it) - here's background on the issue: https://code.google.com/p/android/issues/detail?id=39662 short of it: Google decided to remove the car dock function.
[Verizon Samsung Galaxy S III] mastamoon:
if the APN change did it thats an easy fix then. Will just have to grab the old apn file and stick it in /system/etc
[Verizon Samsung Galaxy S III] zcmack:
thanks. the difference was definitely noticeable when using the phone though, pages wouldn't load in the browser and foursquare check ins would fail. i think i'll just make a backup and take the plunge.
[Verizon Samsung Galaxy S III] ugachris:
You might also update your modems, some notice a difference (I did) and some don't.
[Verizon Samsung Galaxy S III] landale:
That is what I was thinking too. I ordered a T-mobile PAYG sim today and will play around with that as well as different APN files. I might even just try the APN file from the d2tmo variant as that should have all of the correct APN's for T-mobile and with a T-mobile SIM the Verizon ones are irrelevant anyway.
[Verizon Samsung Galaxy S III] mastamoon:
Actually that makes a lot of sense. The apn file we are building with have only vzw apns.

I have an apn file that has both the good vzw apns and all the other apps from other carriers that were being used before. But it's at work. :(
[Verizon Samsung Galaxy S III] mastamoon:
But then again, that should only have cdma carriers, so not sure now. Thankfully that's an easy file to replace to play with.
[Verizon Samsung Galaxy S III] mastamoon:
Forgot to post that there is a new build in the OP.

No changes besides repo syncd.
[Verizon Samsung Galaxy S III] Restola:
Looks like tether security will be in the next official build.

Tapatalk via CM10.1 Galaxy S3
[Verizon Samsung Galaxy S III] mastamoon:
Yeah finally and surprisingly!
[Verizon Samsung Galaxy S III] ctsail410:
Y'all beat me to it! I just repo sync'd to do a build this evening and was shocked to see it was merged (along with the emoji). There are also a handful of audio-caf commits that appear to address some bluetooth and usb headset issues.
[Verizon Samsung Galaxy S III] sivarticus85:
I read a few posts back there were some APN changes? IPv6 merges? Is this causing a weak signal? I've noticed recently that places I normally have good 4G service that I'm only getting 3G, and sometimes even 1X.
[Verizon Samsung Galaxy S III] mastamoon:
No, no, no :D
[Verizon Samsung Galaxy S III] PVLMTREE:
So, I tried using the 1.24.13 Official apns-config.xml on the latest build by you, Masta. If it didn't overwrite correctly or something, but still having the issue. Will still investigate though.

Also, I've compared both apns-config.xml files, and both are exactly the same.

EDIT:

So I've tried T-Mobile's apns-config.xml courtesy of landale, which has WAY more GSM-based APN's. But sadly that did not work.

The thing is that I found out it's not an APN issue, but within the telephony-common.jar within the /system/framework directory.

I have overwrited Masta's latest build with Official 1.24.13's telephony-common.jar, and walla, GSM/Global works... with an exception of couple FC's from Network Location and Fuse services.

So, narrowing it down to that, I would like to address this to the CM team somehow.. can't via Jira due to this is a NIGHTLY. Github?
[Verizon Samsung Galaxy S III] amancini92292:
Dirty Flashed the 2/27 over 2/22 and had all sorts of crazy restarts and force closes. Just an FYI for anyone thinking about doing the same. Fixed my problem by restoring
[Verizon Samsung Galaxy S III] craigbailey1986:
Hey masta just an FYI my signal strength with yesterdays build has gotten significantly better... Not sure what under the hood tinkering has been done but I am on par with tw as of late. Thanks beer on me coming today.
[Verizon Samsung Galaxy S III] mastamoon:
Good work! Have you tried 1/25's telephony-common.jar? Would be awesome to know if that was the exact date.
[Verizon Samsung Galaxy S III] Zacharybinx34:
Has there even been any changes is either this build or official that would effect signal?
[Verizon Samsung Galaxy S III] anacree:
If bluetooth works with my VoIP apps, I'll be a happy camper. =)
[Verizon Samsung Galaxy S III] landale:
If it is indeed something in that file starting on 1/25 it would be interesting to know what it could be as looking at the merges I can't see anything obvious.
[Verizon Samsung Galaxy S III] ctsail410:
Masta, head's up: Recent merge http://review.cyanogenmod.org/#/c/31746/ is breaking builds (including mine and at least one other reviewer's).
[Verizon Samsung Galaxy S III] mastamoon:
Thanks for the heads up, I added it to my revert list.
[Verizon Samsung Galaxy S III] mastamoon:
yeah same here. And the apn merge was on the 30th so its not that, for sure! :)

Though I think any patch or build that will end up working with Tmobile would still need Tmobile APN's correct? In CM there is a apns list and an apns-cdma list.. I would think the standard GSM apns would need to be pulled over also.. https://dl.dropbox.com/u/13144052/apns-conf.xml You can see the T-Mobile lines in there.

Not sure how it works on an old official d2vzw build since only CDMA apns are included.
[Verizon Samsung Galaxy S III] mastamoon:
Looks to be the same as this http://review.cyanogenmod.org/#/c/31988/

Yeah Ill pull it in for ya.
[Verizon Samsung Galaxy S III] icon123:
What's the easiest way to revert something once it's been merged?
[Verizon Samsung Galaxy S III] s'pht:
W00t! thanks - it's been bugging me, thought it was a bug with my Car Home app until I googled it yesterday.
[Verizon Samsung Galaxy S III] mastamoon:
You have to find the hashtag of the commit first, then you cd to the repo and run a git revert 'hashtag'

For example.

cd ~/android/system/external/wpa_supplicant_8
git revert d04091d01db0ddfb13e0c1279e232bf9c3365cfb

But according to Steve Kondik, the commit that is breaking the build has "long been reverted". IDK.

No problem.. that's beauty of these unofficial builds! :good:
[Verizon Samsung Galaxy S III] ugachris:
It looks like all of these commits are in preparation for an M2 build. I wonder if they will fix the GPS issue that you've been reverting.
[Verizon Samsung Galaxy S III] ctsail410:
If you check github he did merge a revert this morning to fix it. Should be good now.
[Verizon Samsung Galaxy S III] icon123:
Built just fine after a current repo sync without any reverts.
[Verizon Samsung Galaxy S III] mastamoon:
2/28 build in the OP! Last one for a bit, going to Disney with the family.

*Changes

***WPA2 tether commit got merged

***Dock Home Button cherry pick added

***Repo Sync as of 3pm EST
[Verizon Samsung Galaxy S III] tducote:
I swear to god I tried that before posting and it didn't work. Works now. It was probably an id10-T error on my part.
[Verizon Samsung Galaxy S III] yosterwp:
I've been running the latest unofficial nightlies by Mastamoon, however, I have noticed that when booting the phone, the phone no longer shows "Samsung Galaxy SIII" before the Cyanogenmod bootanimation. Is anyone else seeing this too? Is there a fix for this?

Other than that, the unofficial nighlies are great! Thanks to everyone who has worked on Cyanogenmod and this ROM!

EDIT: I have done a clean flash, but still nothing
[Verizon Samsung Galaxy S III] rampantandroid:
OK, should I do a log now, or when this happens?

Why is the bug report option in cm10 if that isn't what the devs want for bugs?
[Verizon Samsung Galaxy S III] invisiblek:
framebuffer is screwed up there, its low priority on getting it fixed
[Verizon Samsung Galaxy S III] NegativeOne:
Yes, don't worry about it unless your phone boots up with a logo of MechaHitler.
[Verizon Samsung Galaxy S III] bluezr1:
For some reason every time my phone sits for a while with the screen is off I lose data. I have to turn on airplane mode and then back off the get it to connect, and then it connects instantly. Is there something that I'm missing, or something I have to live with for the time being?

Edit I was on wifi all morning and didn't have any problems, it's just with connecting with Verizon.
[Verizon Samsung Galaxy S III] brockkk:
meh bluetooth seems to have got worse after flashing this. sometimes wont even okay music through my speakers.
[Verizon Samsung Galaxy S III] rampantandroid:
Go into settings, under wireless do more, mobile networks, Network Mode. Make sure it's set to LTE,/CDMA/EvDo, then CDMA subscription, ensure it's set to RUIM/SIM.
[Verizon Samsung Galaxy S III] bluezr1:
Thanks for the reply, although I ended up updating the modem and rpm and it seems much better now. I even went into the basement where I can only get 3g, then went outside and it connected to 4g instantly. :win:
[Verizon Samsung Galaxy S III] Stealth111:
I am/have been experiencing that for a while now. No rhyme or reason, screen on or off. Decent signal, but data totally stalled. I know to check my settings, I was actually doing airplane as a fix, I also notice that if I go in and just reselect each of the 3 network settings it seems to restore data for the most part. I am just holding on for the ride. I am not looking back, I will just keep pulling for the team to get fixes in as quick as they can. I have a small list of bugs, but I will keep my mouth shut so the focus can be on core functionality! I also know there are a few things out there waiting for a final review that might help these issues, hopefully they will arrive soon.

keep up the great work!

Sent using Tapatalk
[Verizon Samsung Galaxy S III] WhammyDroid:
For those having issues with A2DP, it appears google is addressing the issues in 4.2.2. Not sure when it is getting released.