yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] odub303:
That's really odd because the new commit is very similar to the old one that was reverted. In other words, the new commit is almost like having the revert.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] landale:
I guess almost isn't close enough. Just to say I really tried I just flashed the 4/25 ROM again and had it sit in my window for 20 minutes where my phone got an immediate 13 satellites on the previous ROM and it found nothing. This was after resting AGPS, google services framework, reinstalling Maps and every other possible tweak. Believe me I have tried all of this before. It just doesn't work sadly :(
[Verizon Samsung Galaxy S III] mastamoon:
Have you gone back to a stock based rom, got sat lock, leave GPS toggled on, then flash back to CM?
[Verizon Samsung Galaxy S III] goldsmitht:
... And flickers... But just a couple, and might have been due to goo manager, I'll test some more, and post again :what:
[Verizon Samsung Galaxy S III] PerCompLLC:
No flickers for me. Tested with the same games that were causing flickers on yesterday's build. :D
[Verizon Samsung Galaxy S III] Hybridnoob:
Would I just install a TW based ROM as described then restore my current Masta backup or is more to it? Or would I clean install after that?
[Verizon Samsung Galaxy S III] mastamoon:
Yeah just flash a stock ROM. Dont have to go full stock with locked bootloader or anything. Then flash, not restore my latest build. At least as a test. If it works you can try and restore your backup. If it doesn't then restore your backup :)
[Verizon Samsung Galaxy S III] mastamoon:
But have to make sure you get a lock using the GPS. Maybe reboot and do it a few times. Then leave it toggled on when you reboot into recovery to flash cm.
[Verizon Samsung Galaxy S III] airmaxx23:
Can someone test to see if Pandora is working properly on the unofficial build? Trying to search for a channel will not allow the keyboard to open on the official build when pressing the search field.
[Verizon Samsung Galaxy S III] Reborn627:
Experienced the same. Interesting.

EDIT:For the record, I'm using Pandora 4.2 and SwiftKey.
[Verizon Samsung Galaxy S III] mastamoon:
There is an issue with flickering and keyboards. I'm guessing the build prop I added stops flicker but causes weirdness with keyboards in some apps.

I'm using swift key without issue. Are you guys using swype? Try switching to stock.
[Verizon Samsung Galaxy S III] Reborn627:
Switched from SwiftKey to stock keyboard and got the same.
[Verizon Samsung Galaxy S III] AdMire:
I posted the the same thing in the "Official Build" thread, I'm also using Swiftkey. If you tap the + button at the top in Pandora over and over quickly, it will eventually bring up the keyboard but when you try and type it goes away.

Maybe someone can answer this as well: I've ran this and the Official in the other thread and I'm not even sure which one I'm on. Which MC10.1 notifies you of an update in GooManger and the "About -> CM Updates"? This or the "Official"?
[Verizon Samsung Galaxy S III] mastamoon:
Probably both.

Look in system settings, about phone.. Build will have mastamoon in it if it's mine.

I just checked Pandora out and have the same issue. Though when you move to feeds the keyboard comes right up. Maybe an app problem? Work on stock or other builds?
[Verizon Samsung Galaxy S III] Reborn627:
Also interesting, in the "feed" tab I'm able to type in the text box. Odd that it'd work in one tab and not another?

Ray

---------- Post added at 09:16 PM ---------- Previous post was at 09:15 PM ----------

Lol, funny we checked the same.

Ray
[Verizon Samsung Galaxy S III] AdMire:
Okay, thank you. So this is not yours then.
[Verizon Samsung Galaxy S III] AdMire:
Yeah, the feed box does work, just can't add a station.
[Verizon Samsung Galaxy S III] mastamoon:
Nope not mine.
[Verizon Samsung Galaxy S III] airmaxx23:
It works fine on Beans 14 and on my N7 running XenonHD.
[Verizon Samsung Galaxy S III] Reborn627:
For giggles I fired up Pandora on my Kindle hd 8.9 running a cm ROM built 4/21 and it worked fine. Not sure if that matters at all.

Ray
[Verizon Samsung Galaxy S III] mastamoon:
Figured it would. :thumbdown:
[Verizon Samsung Galaxy S III] goldsmitht:
Yep, flickers on chrome, and falcon pro. Checked hardware key, and alls fine.

May just be me... :what: :screwy:
[Verizon Samsung Galaxy S III] Reborn627:
Restored Invisiblek's 4/22 build with GideonX's kernel and it doesn't work either.

Ray

---------- Post added at 10:18 PM ---------- Previous post was at 10:00 PM ----------

Also fails with Invisiblek's 4/24 build.

Ray
[Verizon Samsung Galaxy S III] Hybridnoob:
Ok, I can verify 4/25 GPS works (clean install) after following your recommended course of action (TW install). I'm now restoring a 4/20 nandroid that had working GPS and will try to dirty flash 4/25 over that.

*fingers crossed*

Update - success!! Thanks, Masta! :cool:
[Verizon Samsung Galaxy S III] invisiblek:
http://review.cyanogenmod.org/#/c/36445/

Flicker fix (the real one) merged
[Verizon Samsung Galaxy S III] RED ZMAN:
if I want to have the best chance of squashing this Bluetooth bug for good what wiping should I do? I normally just wipe the cache, and the Dalvik cache.

Blasted from my Samsung Galaxy SIII (CM10.1 Masta Mix).
[Verizon Samsung Galaxy S III] gcutter:
GPS Test fixed my GPS

FYI I had all kinds of GPS problems on Masta 4/24 & 4/25 on 04/20 no problems. I went from 4/20 to 4/24 and no GPS dirty flashed back to 4/20 and GPS worked great. Then I dirty flashed back to 4/25 and NO GPS so I downloaded GPS Test thanks to odub303 and GPS worked right away. I tried wiping data and cache the whole bit uninstalling Maps and all didn't work until I downloaded and ran GPS Test.

Just my 2 cents worth
[Verizon Samsung Galaxy S III] landale:
I decided to try the revert to TW again which I had tried a few months ago back on CM10 when GPS stopped working but this time following Mastamoon's instructions I was able to get GPS working on the 4/25 build! Guess something changed or I just didn't do it right the last time I tried this.
[Verizon Samsung Galaxy S III] SilentAce07:
The 4/20 build has much better battery life than 4/22. 4/20 seems really stable as well.

Good work masta !
[Verizon Samsung Galaxy S III] mastamoon:
Glad it worked! Hopefully we can figure out how to get the stuff to work regardless, but from now on you shouldn't have much issue.

My battery life seems to get better with each build.. had over 2hrs of screen on time and 70 battery left on 4/25 :P
[Verizon Samsung Galaxy S III] minnysota:
Looking forward to trying your afternoonly today. It looks like flicker/reboots are a thing of the past?
[Verizon Samsung Galaxy S III] stearic:
I'm interested in this as well. Asked a few pages back but nobody answered when i asked then. Hopefully someone will answer this time around.
[Verizon Samsung Galaxy S III] goldsmitht:
what is issue with Bluetooth? Thought they had fixed it... I don't use it for music, but my earbud works fine.
[Verizon Samsung Galaxy S III] stearic:
Issue i'm having is that there is a bunch of static when i try to play music via bluetooth both with my cars headunit and with my stereo bluetooth headset. I've cleared dalvik/cache. I'm running the 4/20 build also.
[Verizon Samsung Galaxy S III] mastamoon:
Can any of you guys that have crappy GPS on yesterdays build try this build?

http://truelinux.net/sch-i535/mastamoon/ROMs/test/cm-10.1-20130426-UNOFFICIAL-d2vzw-reverts.zip

Thanks!
[Verizon Samsung Galaxy S III] mastamoon:
This one has the GPS reverted revert back in.. this should work for everybody.

http://truelinux.net/sch-i535/mastamoon/ROMs/test/cm-10.1-20130426-UNOFFICIAL-d2vzw-reverts-gps3.zip

But Im going to say, it would be better if you guys who are having GPS problems to go ahead and backup up your current rom, flash back to TW, get GPS lock, reboot, get GPS lock again. Then make sure you leave gps toggled on, boot into recovery and reinstall CM10.1 clean (but looks like it might work if you restore a backup also).

That way you should have working GPS going forward regardless of the gps revert.
[Verizon Samsung Galaxy S III] Hybridnoob:
That method worked for me yesterday, so take me off the list of people to worry about :)
[Verizon Samsung Galaxy S III] minnysota:
Hey Masta – Is this your 4/26 afternoonly? And have the flicker/reboot issues been worked out in your experience?
[Verizon Samsung Galaxy S III] mastamoon:
Yeah I'm running it. Seems fine, no flicker or reboots. Gps works. Just doesn't have the updated wifi stuff in it. Those are likely to never be merged so probably won't continue to build with them. I don't notice much of a difference.
[Verizon Samsung Galaxy S III] minnysota:
So you're not planning on anything else in your official afternoonly? If not, I'll flash away! Thanks for all your hard work.
[Verizon Samsung Galaxy S III] mastamoon:
No, did like 10 builds today working on the Gps stuff. Then my work let us out early so this build will be the daily. Not going to bother changing the OP though. That build runs good too.
[Verizon Samsung Galaxy S III] landale:
I can confirm the 4/26 build is running great so far. GPS works perfectly (which I did manage to fix on 4/25 with the switch back to TW). I did get a reboot on 4/25 but hopefully the fixes in 4/26 will solve that issue.

Actually I spoke too soon. It looks like there is a problem with one of the new commits for today. http://review.cyanogenmod.org/#/c/36457/

I can no longer adjust the led settings for any custom apps and I am guessing its related to this.
[Verizon Samsung Galaxy S III] V3TTOO:
I don't think this is currently being worked on. I have BT on my car for Pandora, and anytime I do something on my phone, I get static. Even with headphone jack.
[Verizon Samsung Galaxy S III] V3TTOO:
I just did the update for 4/26, and there is no battery bar. What happen to it?
[Verizon Samsung Galaxy S III] mastamoon:
Battery bar has been gone for a bit. It was abandoned by the cm team. Their suggestion, download an app.
[Verizon Samsung Galaxy S III] RED ZMAN:
it was abandoned has been removed from future builds.

Try TEAM Battery Bar.

my problem is the old Bluetooth problem where Bluetooth freezes up. You have to go into app settings and force close Bluetooth share to get it back.

Blasted from my Samsung Galaxy SIII (CM10.1 Masta Mix).
[Verizon Samsung Galaxy S III] V3TTOO:
Thanks for the update you two. I will just stick with the circle battery icon. Just liked that it was included. I will check out the other, and see if I like it.

I have not had that issue in a while. I only have issues with the quality. I think my issue is related to the handoff and signal quality. Usually happens when I am driving and do something on the phone, but not usually when I am just parked.
[Verizon Samsung Galaxy S III] landale:
Can someone else try and see if they can edit led settings for custom apps? When I click on an entry it doesn't do anything except for the built in ones for missed call and voicemaill. I was able to do this on 4/25 but I can no longer edit on 4/26, just add apps. I figure the problem is that one new commit but just wanted to make sure it isn't just me having this problem.
[Verizon Samsung Galaxy S III] Hybridnoob:
Confirmed, same here. Not a big deal for me though.
[Verizon Samsung Galaxy S III] landale:
Thanks for checking. Not a big deal for me since I had set most of my stuff before updating to 4/26, I had just forgotten one app. Sure it will get fixed soon enough.
[Verizon Samsung Galaxy S III] daytonahemi08:
Just loaded it on my s3 so far so good don't use blue tooth or led settings some I'm content . much better than my att note.
[Verizon Samsung Galaxy S III] tv31284:
I've been running today's build for a few hours and everything has been running amazingly smooth. No reboots so far, but it's still early. Thanks for all your hard work.
[Verizon Samsung Galaxy S III] goldsmitht:
Did get some flickers, think im going to have to take time and do a clean install tobaee if that clears it up
[Verizon Samsung Galaxy S III] mastamoon:
I left the build prop setting in the build.prop that was helping with the flicker. Just delete the # in front of the debug.mdcomp.maxlayers=3 line. Save and reboot.
[Verizon Samsung Galaxy S III] goldsmitht:
Changed it, had a couple right off the bat, but seemed to settle Dow. I'll test it out today, and see what happens. Thanks for all the hard work.
[Verizon Samsung Galaxy S III] PerCompLLC:
And here's the link for those interested. https://play.google.com/store/apps/details?id=com.pvy.batterybarpro

Awesome app! :D
[Verizon Samsung Galaxy S III] goldsmitht:
Nope, still there. This was a dirty flash, so may try clean on on Monday, don't have time to mess this weekend (wife wants my time... Go figure) can check disable hardware overlay, that usually fixes it.

One thing, force GPU is checked, would that do it?

Thanks again, moon otherwise, works great!

:D:
[Verizon Samsung Galaxy S III] mastamoon:
I recently wiped system before installing and haven't had a flicker at all recently. No reboots either. All I had to do after was redo my Google accounts.
[Verizon Samsung Galaxy S III] goldsmitht:
Yeh, I remember it cleared up a problem I was having before that seemed to have been fixed for everyone else
[Verizon Samsung Galaxy S III] Gordon Ramsay:
Hello

Running the 4-26 GPS revert build. Still having some issues. Flip board will randomly freeze and leave text searing into my screen seemingly until I battery pull. Also spotify and chrome beta still cause reboots for me. These are all problems that started for me on this new kernel. Just thought I would throw my 2 cents in. Thanks for the builds!
[Verizon Samsung Galaxy S III] mastamoon:
It's an honor for you to use my builds chef! Haha

The 26th builds are back on the main cm10.1 kernel. Cyanogen put some extra debugging in to help track down the problems.
[Verizon Samsung Galaxy S III] Gordon Ramsay:
Haha you bet. Sorry I didn't catch the fact about the kernel. So as long as I have the reporting enabled then does the log info go straight to them? I want to make sure they get it. If so I may hang with this build for a bit just to make sure they get the info.
[Verizon Samsung Galaxy S III] mastamoon:
No, that's not what that reporting is doing. That's install stats.

If you want to help, you can try and logcat the issue. But right now all reboots and flicker are caused by the same thing probably and they haven't found much in the logs just yet to find a fix.
[Verizon Samsung Galaxy S III] iofthestorm:
Doesn't the update script format system anyway? I guess you've still got the scripts in /etc/addon.d backing up stuff like gapps but other than that does formatting system manually actually do anything?
[Verizon Samsung Galaxy S III] mastamoon:
Not sure. I know phone behaved differently when I formated manually. Had to install gapps and re-add my Google accounts. Maybe it does some sort of magic but not sure if it's a 100% wipe.
[Verizon Samsung Galaxy S III] termleech:
If I remember correctly cwm formats system but twrp doesn't. The script backs up you gapps and then reinstalls then but only if you don't format system manually first.
[Verizon Samsung Galaxy S III] ddggttff3:
got to love how quiet this thread is.

Any plans for a unofficial today masta? thanks
[Verizon Samsung Galaxy S III] mastamoon:
:D

Yeah should have an afternoonly out. There isn't much going on in our neck of the woods recently. I think CM is holding off adding anything new till they figure out the reboot & flicker issue.
[Verizon Samsung Galaxy S III] Stupifier:
To me, the quietness just tells me nobody knows how to fix the reboot/flicker issues. Doesn't make me feel good at all lol.

Quiet threads can mean many things
[Verizon Samsung Galaxy S III] landale:
Maybe I am in the minority but I haven't experienced any flickering on either the 4/25 or 4/26 builds. If it helps the 4/25 build I did as a clean install after reverting back to TW to fix GPS issues. I have experienced reboots on builds for the past couple weeks but only on the stock kernel. Switching to LeanKernel seems to have cleared up any reboots for me.
[Verizon Samsung Galaxy S III] gcutter:
I 2nd this but mine is dirty flashes from long time ago. I am on 4/25 and i have not had a problem since I got GPS working once I downloaded GPS Test.
[Verizon Samsung Galaxy S III] mastamoon:
If you are going to wipe data.. before you restore anything, even with that SMS backup app, please send/receive an MMS and see how it goes. If it works, then restore your SMS and try again. Only way to know for sure if its your data restore thats causing the issues.
[Verizon Samsung Galaxy S III] PerCompLLC:
Good call!
[Verizon Samsung Galaxy S III] yznhmr:
ok wiping now
[Verizon Samsung Galaxy S III] nativesmiley:
are u guys using mastamoon builds??
[Verizon Samsung Galaxy S III] tducote:
I'm having the same issue. Using Handcent and tried with the Stock Messaging app.

Baseband Version is I535VRLF2. If this is something I need to change, could you possibly point me in the right direction? Thanks.
[Verizon Samsung Galaxy S III] mastamoon:
http://xdaforums.com/showthread.php?t=1788313 will get you to the right place for the newest baseband/modem.

That doesn't seem to be the issue however with the user above you, but would still probably be best to get the latest modem unless your sticking with that modem for a particular reason (better signal or magic).

Did you restore SMS/MMS data on install?
[Verizon Samsung Galaxy S III] tducote:
I didn't do a factory wipe from official cm10.1 to your build. It's not really that important to me to have the MMS stuff working right now. TBH, I really just wanted to ask about updating the modem. Figured it'd probably be a good thing to do. I am having mobile data drop outs every now and then. I'm assuming that updating the modem might help, yeah?

Also, what is the correct order for flashing ROM, kernel, and modem? And I'm assuming I won't need to re-flash the latest modem with every flash of a new ROM, correct?
[Verizon Samsung Galaxy S III] PerCompLLC:
I am... Haven't noticed a signal strength change (signal is based on the radio software which is separate from CM). But my handoff issues between 3G and 4G have disappeared completely!
[Verizon Samsung Galaxy S III] mastamoon:
Was MMS working on official CM10.1?

I dont think the data drops are really due to the modem itself, but staying up to date on the latest released from Verizon/Samsung always seems to be a good idea to me.
[Verizon Samsung Galaxy S III] senorbuck:
I'm on the 1/16 build of mastamoon's and I've noticed by signal strength here at work is slightly better than it's ever been using a TW ROM. I'm usually sitting at 4G with no bars lit up. Never seems to drop to 3G. :good:
[Verizon Samsung Galaxy S III] tducote:
I could be wrong, but I seem to remember a short time in some of the later nightlies where MMS was working in official cm10.1. I use other web-based messaging services (like GroupMe) quite a bit though, so I may just be thinking of that. (Sorry for the lack of helpfulness here.)
[Verizon Samsung Galaxy S III] Restola:
MMS works on official nightly.
[Verizon Samsung Galaxy S III] sparkerjc:
Same here, says "Invalid recipient"
[Verizon Samsung Galaxy S III] mastamoon:
Have you tried sending a MMS to different people or all to 1 person?

Have you tried manually typing in the phone number vs picking from your contacts?

Do SMS work to this person but not MMS?
[Verizon Samsung Galaxy S III] yznhmr:
seems it wasnt anything but the check box about allowing while roaming..

I have a network extender from Verizon, and it doesn't recognize the new modems

so im in "roaming" in my house

getting complaints of echo using the handset(not speaker) still

---------- Post added at 12:54 PM ---------- Previous post was at 12:52 PM ----------

mine did not have that error message.. it was just stuck in the sending mode
[Verizon Samsung Galaxy S III] sparkerjc:
Yes to everything. Invalid recipient is if I type the number in. If I don't type the number it still won't send but the message doesn't appear saying invalid recipient, it just says failed to send. Texts work just fine, but not "Group MMS" which is not an option that I can find as it is in other ROMs.

Official nightly 1-18 just sits on the sending screen forever with no error but never sends.
[Verizon Samsung Galaxy S III] mastamoon:
For those having MMS issues.. http://xdaforums.com/showthread.php?t=2027347 ... looks like 3rd party SMS/MMS is a no go on 4.2.1 still, so that might be your issue.

For those having issues using the stock SMS/MMS... :confused:
[Verizon Samsung Galaxy S III] tducote:
I don't have any problems with SMS for 4.2.1. Never have. And I've only used third party apps for messaging. Veeerrrry intradesting.
[Verizon Samsung Galaxy S III] sparkerjc:
I have just done three clean flashes, first the masta 1-17, no mms. Then dirty flash official nightly, no mms. Then clean flash official, no mms, then clean back to masta still not working.

The other confusing thing, I thought there was supposed to be proper group threading for group texts as mms, which doesn't seem to exist either (in either rom). I posted in the Q & A thread with no response yet (I think).

I'm coming from TW ROMs, using CWM 6.0.2.3

I did:

Wipe Data/reset

Wipe Cache

Format /system

Wipe dalvik

Flash ROM

Flash Gapps

Did I miss anything? Edit: just to be clear I have never installed any third party mms apps
[Verizon Samsung Galaxy S III] mastamoon:
Are you using a VZW extender?
[Verizon Samsung Galaxy S III] PerCompLLC:
No flickers or reboots here! I'm on the 4/26 build with the stock kernel (dirty flashed). :good:
[Verizon Samsung Galaxy S III] gregurbo:
I'm still running the 4/12 adreno build. It works great. Very smooth. I haven't experienced any glitches or reboots. Everything just works. :thumbup:
[Verizon Samsung Galaxy S III] goldsmitht:
Clean flashed to 4/26 over weekend, and paired it with a nice LK 5.6exp1, and also well now! Was having the flicker issues, but clean flash cleared them all up. :D
[Verizon Samsung Galaxy S III] Stealth111:
Things have been pretty smooth for me for the last few weeks (flashing every single nightly, official and unofficials!), no flickering, no reboots, pretty stable other than small glitches that they were working on/fixing, and so-so battery life. I dirty flashed last nights official nightly, and was greeted with a few frustrating things. I was in my Verizon Visual Voicemail, and now the audio is messed up again (It was fixed a couple weeks back)... It totally ignores if you have it set to speaker or earpiece, it just plays messages blaringly loud out of the speaker only. When I tried to change it back and forth a few different times, I was presented with my first reboot in a long time! Just wanted to throw it out there! :)
[Verizon Samsung Galaxy S III] mastamoon:
4/29 build in OP

-- NO GPS cherrypicks/reverts... please see the note in the OP

-- using invisiblek's kernel (has wifi drivers merged and new CAF & korg merges)
[Verizon Samsung Galaxy S III] mastamoon:
I had the same issue, but with Google Voice a few weeks back which was fixed like you said. But unlike you, its still working. Strange.
[Verizon Samsung Galaxy S III] goldsmitht:
has anyone noticed a big fix with the wifi drivers? reason is, i have had issues with the CM kernel, and was curious if this was reason enough to use it?

:confused:
[Verizon Samsung Galaxy S III] mastamoon:
I havent found something it fixes per-se.. I think I get slightly better battery life. Might have some better wakelock handling. The Note2 guys are using and have noticed the same thing.
[Verizon Samsung Galaxy S III] ugachris:
Are you still bumping up the MMS size? I noticed it isn't listed in the tweaks any more.
[Verizon Samsung Galaxy S III] mastamoon:
The changes were merged a bit ago, I just never took out my fix. Should be comparable. If not, let me know.
[Verizon Samsung Galaxy S III] ugachris:
I just sent myself a message and it was only 24kb in size. I was looking because I noticed someone on the Q&A thread posting about his/her own fix.

http://xdaforums.com/showpost.php?p=40753928&postcount=1476