yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] Chris123NT:
Oh im not familiar with the single text issue, I just remember being on old firmware used to cause some pretty crazy bugs with CM. Wonder if this is one of the issues that cropped up when the unified builds started.
[Verizon Samsung Galaxy S III] defTwitch:
So I'm on almost the same build... just been trolling this forever. I'm on 0718.. of 10.1.

Only posting to let you know I've been on MF1 forever... so if I did upgrade (and I will soon) I guess I'd just leave that rolling.
[Verizon Samsung Galaxy S III] TwistingSoul:
So, I'm sure I'm being completely boneheaded, but I noticed I'm running (and probably have been for some time) the VRUCML1 baseband.

I've not really had any noticeable issues with it, but is this newer or older than the VRBMF1 baseband?

Also, what are the consequences of attempting to flash to this recommended one as per the first post in this thread?

More to that second question, is it even possible? Should I worry about flashing to MF1? Are there any notable differences I should worry about?
[Verizon Samsung Galaxy S III] Ryezen:
According to the change log, not much difference should be experienced after flashing the latest nightly. But for some reason, my phone seems to really like the newest build (20140721). It seems to have cleared up an issue I was experiencing where no apps were showing new updates unless I rebooted, in addition to other little areas working better. Big time thanks to the devs for making such a solid/stable CM-build with a few additional (and appreciated) features to boot!
[Verizon Samsung Galaxy S III] Master Cylinder:
VRUCML1 is the latest and greatest. If you're not having a problem there's no reason to go backwards - that would only be for emergency situations.

OP on ROM threads are frequently out of date - masta could step in here but he's probably on it, too. The only post by him re:VRUCML1 on this thread I found searching it was this: http://xdaforums.com/showpost.php?p=51345504&postcount=823
[Verizon Samsung Galaxy S III] mastamoon:
I pulled the ML1 radio from the OP when all the SMS/MMS issues hit. It isnt known if it was the issue or just happened to drop around the same time the issue hit, but it seemed better safe than sorry. I was on ML1 for quite a while without issue, but went back to MF1 and haven't gone back to ML1. I never really noticed any difference between radios all along, but what you do want to make sure is you flash the MF1 firmware package no matter what (if you are on an earlier firmware) as it updates much more than just the modem. It actually fixes a few issues that earlier firmwares had. The ML1 package is only the modem, which leaves the rest of the MF1 firmware in place.

I also updated the OP to link to the newest CM gapps package and the latest PhilZ recovery that works for us. The later builds of the recovery are not working on D2LTE right now and im not sure if it will be supported going forward.
[Verizon Samsung Galaxy S III] Master Cylinder:
My memory of when all that was happening with SMS was that is was confined to only AOSP builds. I had the problems on AOSP but not on TW, using VRUCML1. The fix at that time was easy and seemed to fix the problem for most people - disable blacklist in the SMS app and/or dump it for another. That fixed it for me, anyway, and many others.

As time went on, the issues seemed to have disappeared (?), but were never on TW as far as I can tell, though when people tried to institute AOSP SMS on TW it did screw the pooch.
[Verizon Samsung Galaxy S III] anrichardson:
I have to admit that this was very minimal use but I am very pleased with the results. Also was using dalvikand not ART.
[Verizon Samsung Galaxy S III] greekstile:
Hey Masta, any updates on this? I haven't seen this cherrypicked in your changelog. Today maybe? Fingers crossed!

Thanks!
[Verizon Samsung Galaxy S III] mastamoon:
The fix was merged on the 14th... no need for me to cherrypick :)

http://review.cyanogenmod.org/#/c/68005/

http://review.cyanogenmod.org/#/c/67866/
[Verizon Samsung Galaxy S III] anrichardson:
Yes. And it's 2 year old battery too. The same one that came with the phone. Have thought about getting a newer one but keep putting it off.

But when I am using it. I can just see the battery count down. The stand by time is amazing though.
[Verizon Samsung Galaxy S III] akakai:
I'm surprised it says 45% Screen Usage with 15 hours and 50% battery left, that is amazing.

I was wondering surely you weren't getting 5h or 6hours screen on lol.

When i was getting battery life like that on this rom, Super minimal usage was required.
[Verizon Samsung Galaxy S III] anrichardson:
Yes. I was home all day yesterday so I rarely use my phone when at home. But seriously I was surprised just as much too.

This morning I was steaming ESPN radio sand listening to music and had 5.5 hours with 38% battery left before I started to charge which is normal in my case.
[Verizon Samsung Galaxy S III] akakai:
That's pretty good battery life on stock battery on a CM based rom even with your type of usage

I've been using my ZeroLemon 7000 mAh for awhile, but just put my stock battery back in the other day to see what i can get.

btw How long have you been on this rom without switching or upgrading?
[Verizon Samsung Galaxy S III] anrichardson:
I flashed the 21st on Monday then flashed the 22nd on Tuesday night and was going to flash the 23rd on Wednesday but decided to see battery life first so I am still on 22nd unofficial. And i will stay here for awhile too.
[Verizon Samsung Galaxy S III] akakai:
That's good. Usually it takes awhile to get that good. I'll try and see what i can get on stock battery.
[Verizon Samsung Galaxy S III] anrichardson:
This straight streaming. And this regular for me.
[Verizon Samsung Galaxy S III] Ryezen:
Is it just me, or do all the change logs look the same over the past few releases?
[Verizon Samsung Galaxy S III] anrichardson:
Yes. They do, but wasn't sure myself
[Verizon Samsung Galaxy S III] mastamoon:
I haven't had to cherry pick much since CyanogenMod has been merging most good things pretty quickly.
[Verizon Samsung Galaxy S III] anrichardson:
So not much difference in your unofficial to the official nightlies then?
[Verizon Samsung Galaxy S III] dmginc:
Look at the OP. "99.9% Cyanogenmod, .1% my hackery."
[Verizon Samsung Galaxy S III] Ryezen:
So far on both this ROM and another CM11-based ROM I've tried, I get problems after taking multiple pictures/video and switching back and forth between the two. It seems the more pictures/videos I take, the less responsive the phone becomes, until I have to restart it to take more pictures. Anyone else experienced this?
[Verizon Samsung Galaxy S III] Zacharybinx34:
On the newest nightly my battery is getting absolutely destroyed by deep sleep
[Verizon Samsung Galaxy S III] mastamoon:
not sure if serious.

Deep sleep is a good thing, right? :)
[Verizon Samsung Galaxy S III] Zacharybinx34:
I thought that too as I was writing it... but it's taking up the majority of battery life... and my phone is dying half-way through the day with less than normal use. It's really bad.
[Verizon Samsung Galaxy S III] Chris123NT:
deep sleep is a good thing. If your battery is being destroyed it's a wakelock, get a better battery stats log, make sure it's installed as a system app and root features are enabled.
[Verizon Samsung Galaxy S III] mastamoon:
Weird. I got about 3hrs screen on time yesterday out of my phone before it hit the 15% battery warning. Sounds like you got an app gone crazy or something. Gonna have to pull out the better battery stats and see whats killing.

Better Battery Stats, XDA Edition - Free

http://xdaforums.com/showthread.php?t=1179809
[Verizon Samsung Galaxy S III] mastamoon:
DAMNIT! :P
[Verizon Samsung Galaxy S III] Zacharybinx34:
I am using CPU Spy.
[Verizon Samsung Galaxy S III] Chris123NT:
CPU spy won't give you any detailed information other than CPU state times.
[Verizon Samsung Galaxy S III] Zacharybinx34:
I picked up better battery stats, but I'm not sure what exactly I should be looking for.

Thanks!
[Verizon Samsung Galaxy S III] mastamoon:
Cool, ill have to try when I get out of this bunker I call an office :)
[Verizon Samsung Galaxy S III] zcmack:
that did it. i was messing around with the settings but never actually turned it off then back on. thanks!
[Verizon Samsung Galaxy S III] duarian:
LPA?
[Verizon Samsung Galaxy S III] senorbuck:
Set lpa.decode to false in build.prop.
[Verizon Samsung Galaxy S III] ThaSik1:
You had me excited there for a sec man! lol I thought you were talking about tweaks to get the FFC to act right on snapchat haha Then I saw the pics and finally realized that I didn't have those settings for a reason haha..
[Verizon Samsung Galaxy S III] jalewis:
FYI, I've never had an issue accessing your site or downloading on 4g...
[Verizon Samsung Galaxy S III] mastamoon:
You're lucky. Mine was not working either but is now. I think the 4.8 toolchain I was using was causing some non build breaking derpage. Also think it fixes up using ART if you're so inclined.
[Verizon Samsung Galaxy S III] mikejr83:
Do you mean 4.8 Linaro toolchain? What changes need to be made to compile a kernel with Linaro 4.8?
[Verizon Samsung Galaxy S III] mastamoon:
No not Linaro, the aosp 4.8 toolchain.
[Verizon Samsung Galaxy S III] goldsmitht:
not the right forum, but figure this is where the smart people are.

any way to get a phone with a broken power button (always pushed in) to get past a bootloop? gonna send in for a replacement, but need to get it back to stock.

sorry, know this is not that forum, but figured with all the smart people, someone would know

thanks,
[Verizon Samsung Galaxy S III] duarian:
So far so good on the newest build, using BMS kernel and my battery still works, gonna try out the camera and see how that is.

Last night on low light pictures I was getting some colored lines all through my pictures, didn't matter what app I used. Any ideas?
[Verizon Samsung Galaxy S III] mastamoon:
There are back to stock threads on the forum, check general.
[Verizon Samsung Galaxy S III] WhammyDroid:
I know. Just posting it to gain awareness/get fixed.
[Verizon Samsung Galaxy S III] goldsmitht:
nah, i have a stuck power button and can't get past samsung splash screen. can get it to start into odin, but then, since the power button is pushed in, it boots out of it.

thanks anyway
[Verizon Samsung Galaxy S III] mastamoon:
OIC.. Either pop the back cover off or somehow brick it.
[Verizon Samsung Galaxy S III] goldsmitht:
any hints on how to brick it without being able to get past boot splash? big magnet? LOL

:confused:

and thanks, i know this isn't rom related, my post in general didn't even get any reads
[Verizon Samsung Galaxy S III] mastamoon:
Does it stay on long enough to get adb up? Could just write garbage to the partitions.. Hit up freenode.net, verizons3 channel and tell them you wanna brick your phone. I'm sure invisiblek can give you some ideas.
[Verizon Samsung Galaxy S III] Chris123NT:
I would suggest taking the phone apart and getting the power button free and then return it to stock and exchange it.

Bricking is an option too I guess, you could always flash a bunch of crap to the aboot partition and that would pretty well do it.
[Verizon Samsung Galaxy S III] zachf714:
The Nard brick is the best lol
[Verizon Samsung Galaxy S III] xyrcncp:
^this

http://www.ifixit.com/Device/Samsung_Galaxy_S_III
[Verizon Samsung Galaxy S III] mastamoon:
The culprit should be in other, kernel or partial wakelocks.. Give it a few hours to know for sure.
[Verizon Samsung Galaxy S III] tv31284:
I get the issue with the phone becoming unresponsive when I use navigation or do heavy browsing. I wonder if it's because of a heat throttling issue. I switched to lean kernel and that helped a bit, but with either kernel eventually the phone reboots itself. Kind of frustrating. I switched back to TouchWiz for a bit and the issues went away. I just can't stand TouchWiz though even if it is more stable.
[Verizon Samsung Galaxy S III] astonmartin214:
hey go over here there are D2lte ROMS I found Dirty Unicorn

http://xdaforums.com/galaxy-s3-att/development
[Verizon Samsung Galaxy S III] Chris123NT:
:confused:

Why are you posting this in someone else's thread?
[Verizon Samsung Galaxy S III] astonmartin214:
well I was helping him out since he can't stand touchwiz just find something else until issues get fixed VZW thread doesn't have a lot of ROMS to choose from
[Verizon Samsung Galaxy S III] Unoid:
Can anyone help explain what I'm missing?

Coming from CleanROM, My youtube app had a "mirror" icon in the upper right that would recognize my ROKU 3 youtube app, and stream to my TV.

Now on this CM ROM... I can't figure out why it won't work anymore? I have the latest youtube. Even the official Roku control app. Both on same wifi...

Someone please help.
[Verizon Samsung Galaxy S III] lostwhat83:
Try using all cast. It will pick up Roku, xbox , chromecast.
[Verizon Samsung Galaxy S III] Zacharybinx34:
So I ran the program for a bit here, I still am not sure what I'm looking for.

Does this log tell me what it is?

Thanks!
[Verizon Samsung Galaxy S III] dmginc:
That looks to be only about 4 minutes of logs.
[Verizon Samsung Galaxy S III] Srambo217:
Started getting an insane amount of random power downs. Has anyone else had this issue?

Galaxy SIII

My Podcast*-*http://bit.ly/WWSXbz

Twitter - http://bit.ly/VVAdb8
[Verizon Samsung Galaxy S III] Master Cylinder:
No ... not even one. Maybe one a few weeks ago. You didn't say what date you were on - you got some other frameworks going? I've had Xposed going and have been flashing a lot of these - up to date at the moment.
[Verizon Samsung Galaxy S III] Srambo217:
Oops, 0711. The only framework I applied was Xposed with Gravitybox and Unicon modules. Nothing crazy. 0709 didn't have this issue but the lack of photos in Gmail were an issue for work.

Galaxy SIII

My Podcast*-*http://bit.ly/WWSXbz

Twitter - http://bit.ly/VVAdb8
[Verizon Samsung Galaxy S III] Master Cylinder:
I thought this sounded familiar http://xdaforums.com/showpost.php?p=54198294&postcount=1144

Why not do a nandroid, flash the latest ROM, wipe dalvik/cache and see if the problem gets solved?:good:
[Verizon Samsung Galaxy S III] TwistingSoul:
So, I went to the Motley Crue/Alice Cooper show here in Utah last night, and I took well over 200 pictures, but sadly, all but probably 3 of them are corrupted.

The battery was not fully charged during the concert, and I did use burst mode during Alice's performance to get as many as I could without a full-on video recording. The phone was connected to a portable battery pack to charge the phone so that I could take pictures, which were also done in airplane mode to save battery and allow for faster charging on the pack. Also, the phone did not die from being extremely low until the concert was done. Between the time of my last photo and when I reconnected power was at minimum 30 minutes when I got back to my truck and connected the phone to the cigarette lighter charger.

Is there any way to recover the photos that now show nothing but black squares in the gallery? I've reflashed the latest ROM release (08/01) with Gapps, but to no avail.
[Verizon Samsung Galaxy S III] Master Cylinder:
Oh Man! What a heart breaker! Can you get them to redo the show so you can get some pictures?

When you use burst mode, they save on the internal card rather than the external card I think. Might save in a different place, too. You might look into that. Maybe your gallery doesn't know where they are? Can you browse to the pictures using your file explorer? You can check the details/properties, etc..., and see if you have the size files that compare to other pictures that are right. Was it just too darK? Seems like they should have got something on those. You can transfer some of them to a PC and have a look at them. Other than that, as an amateur, I don't know anything else to help.
[Verizon Samsung Galaxy S III] TwistingSoul:
It would be awesome if they could redo the show just for little old me. Lol the weird thing is when I try to pull up the individual files using a file explorer, there's no thumbnails for the pictures that are saved, yet they all have the appropriate file sizes characteristic of other photos in my camera roll.

I have rebooted multiple times, and shockingly after about now eight and a half hours of trying to undo the root access and go back to stock, this failed, so I decided to give up and stay on this rom. I was thinking somehow that being on stock would have magically fixed the pictures somehow.

I have been tempted to clear the data in camera and gallery, but doesn't reflashing the ROM and the gapps package do that anyway?
[Verizon Samsung Galaxy S III] Master Cylinder:
It won't matter which ROM you're on - the pictures should remained untouched when you flash. In fact I would think that short of wiping your entire internal or external storage, they should be okay.

Heck, I can't even get Burst Mode to work! I've turned it on in Camera settings but nothing happens.
[Verizon Samsung Galaxy S III] TwistingSoul:
I'm really hoping I don't have to wipe my external storage, since that's where all of the photos are stored when they're taken from the native CM 11 camera app. Though this 64 GB SD card has been good to me, it's not a class 10 as is usually recommended here on XDA, so I guess I may have gotten what I paid for, and it's finally come back to bite me in the hind end.

I also noticed that there was no .thumbnails folder in the DCIM folder, which I thought was odd, so I copied that folder from the main phone storage to the external card, but no thumbnail files are showing up to even rebuild anything.

I'll try doing a factory reset and reinstalling to see what happens. Fingers crossed!
[Verizon Samsung Galaxy S III] Srambo217:
Put 0801 on top of my last stable backup and got the same issue. Didn't even apply xposed this time. Guess this ROM just won't play nice with my phone.

Galaxy SIII

My Podcast*-*http://bit.ly/WWSXbz

Twitter - http://bit.ly/VVAdb8
[Verizon Samsung Galaxy S III] DigitalMD:
You might have a bad SD card if you go to a clean install and still have problems. Change SD cards or remove it and see what happens
[Verizon Samsung Galaxy S III] Snypercell:
No Preview When Changing the Ringtone/Alerts/Alarms

So... First off, Masta, I love your work. You do a great job of keeping your ROM updated and in excellent working order, and you work harder than most OP's to help your users fix their issues. /props

Second, I'm running my own custom build, compiled from CM source, and using TheMuppets repo for proprietary files.

I've been running my own builds for over a year now, and I've seen a lot of quirky errors, but this one is just plain weird. I've Googled the issue, but that hasn't returned anything related to the problem.

My question: Has anyone else noticed, on any build compiled from 7/19 thru 7/26, when changing ringtones/alerts/alarms as you select each there is no preview played? The build I'm having the issue with was repo sync'd on Saturday July 26th, and compiled immediately following.

I usually sync and build once a week, every Saturday. I don't always flash, but I like to keep my builds updated on a regular schedule, just so that I can track issues like this particular one.

I sync'd and built last night, and I'm about to flash it to see if there is any change, so I'll post my results here. I'm just curious to see if anyone else has experienced this, since it shouldn't be just me, as I do not make any changes to the code. I have, in the past, coded changes into various apps in order to create my own flowing theme, but I dropped that work with the recent improvements to theming.

**EDIT** Flashing my 8/2 build fixed the issue.
[Verizon Samsung Galaxy S III] droidxxxxx:
It says to use the MF 1 modem.. How come we should use an older modem with such a new ROM? I thought ml1 was the one to be using.
[Verizon Samsung Galaxy S III] ugachris:
There's a search bar up and to the right. Type in 'ML1' and press Enter. Mastamoon addressed this just a few days ago.
[Verizon Samsung Galaxy S III] droidxxxxx:
I'm noticing the GPS doesn't want to stay locked like it normally does. Seems to come and go. I use waze a lot and it keeps searching for its location.
[Verizon Samsung Galaxy S III] mastamoon:
Must....resist....begging...for.....new...phone.......moniez............

hargarlblargle... so bored.... marghlerblargle
[Verizon Samsung Galaxy S III] droidxxxxx:
Is it a kitkat problem or just me? It seems to work spot on for about 15 or 20 minutes.. then i notice the dropping of the location lock.. Im also running my WiFi tether at the same time..maybe that affects it. Everything else seems to be running really smooth.
[Verizon Samsung Galaxy S III] Master Cylinder:
Go on back to the Casinos - maybe you can get fixed up?
[Verizon Samsung Galaxy S III] Darryl Henley:
lost cell connection on 8/6. rolled back to 8/5 and it works.
[Verizon Samsung Galaxy S III] mastamoon:
Yeah that's why I pulled the file. . Did some investigation first so I'm sure a few of you installed it.. So... Sorry ☺
[Verizon Samsung Galaxy S III] Ryezen:
I had weird GPS stuff going on with this ROM, too. I'm not sure if it was due the CM-base or something to do with 4.4.4. I've switched over to a release based on AOSP for now to compare. Will try and post back when I've had sufficient time to compare.
[Verizon Samsung Galaxy S III] droidxxxxx:
I've tried this one..spirit..and gummy. All the latest builds with the same issues. Including voice text causing force closes.
[Verizon Samsung Galaxy S III] Zacharybinx34:
On 8-7 build getting lock ups with maps and call drops
[Verizon Samsung Galaxy S III] mikejr83:
Anyone running this post M8?

It's been a while since I've flashed. Phone started acting up a few days ago so I figure it's time to clean house and was going to start with the 8/20 build.
[Verizon Samsung Galaxy S III] Darryl Henley:
works great. go for it.
[Verizon Samsung Galaxy S III] Notorious:
[MENTION=2963287]mastamoon[/MENTION] would it be possible for you to build a cm11 ROM with this edit https://github.com/datagutt/android...mmit/0459e1264b340da440d69cbb8f3248b218ee92af ? I need it so I can work on a ROM [emoji3]
[Verizon Samsung Galaxy S III] mastamoon:
What does this commit do exactly?
[Verizon Samsung Galaxy S III] Notorious:
Disables selinux. I work on MIUI and it does not support selinux
[Verizon Samsung Galaxy S III] bamaredwingsfan:
Has anyone had good blue tooth results with bms kernal
[Verizon Samsung Galaxy S III] daimerion:
I have, but different ROM.

Brought in on my hellish Dirty Unicorn S3
[Verizon Samsung Galaxy S III] dmginc:
Anyone on 9/2 notice things are a little bit slower/delayed. Typing isn't as quick. There is a delay with the screen turning on after you press the power button. Vibration intensity also seems way down.
[Verizon Samsung Galaxy S III] Master Cylinder:
Just reporting amazing battery results!

I had to do a fresh install on 8/15 from general flakiness of many dirty flashes - did not bother with other partitions though. Hadn't flashed since (I was flashing 2-4 days a week!) and I'm amazed at going to bed with over 50% left on the battery the past 10 days or more. I've owned this phone for 18 months - this is far better than anything previous.

:cool:
[Verizon Samsung Galaxy S III] ugachris:
I'm on 9/2 and I noticed that there is a definite delay from pressing the power button to when the screen come on.
[Verizon Samsung Galaxy S III] mastamoon:
Have any you that are getting lag tried official? I haven't really noticed a difference, but id like to know if its something ive done that's causing it.
[Verizon Samsung Galaxy S III] ugachris:
I haven't tried official to see how it compares. I was thinking I'd flash your build from today to see if it was still there, but you have quick a long pick list for today's build. Is it semi-stable?