yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] julesism:
anyone else use Instagram?

Anyone else use Instagram? Video has not worked properly for me on the last few builds. First shot/sequence is fine, second shot looks like watching 3D without glasses, and then the screen eventually turns green. This kills the camera and a reboot is necessary assuming phone does not reboot itself. stock Camera app and Vine seem to work fine so I'm pointing finger at the app, just curious if anyone else can recreate the issue.

I used to use the MotorolaCamera but updates killed it a while ago.
[Verizon Samsung Galaxy S III] goldsmitht:
Google instagram; think this is an issue across the ROMs, and may be the apps problem, and not related to the ROM
[Verizon Samsung Galaxy S III] Gatanater:
PLEASE HELP! I hadn't updated in a month and suddenly my data stopped working. I tried wiping cache and dalvik to no avail. I then FAC reset and installed the newest build (without saving anything -_-) and still have no data. Need help
[Verizon Samsung Galaxy S III] julesism:
Thanks goldsmitht for the instagram feedback. I've got another camera issue. My phone locks up (have to pull battery) when I take a picture with the flash on. I just wiped (data/cache/dalvik x 1) and did a clean install of masta's 7/3 build with no gapps or kernel. Took pic with main/back cam and flash and it locked hard again.

*EDIT*

So I restored a backup of AOKP 6/30 nightly... issue above

restored backup of BoneStock 3.0 (TW)... issue above (TW camera)

I flashed an older radio.. same issue

reflashed MF1 aio... same issue

Looks like I have an issue with my phone :/ I'm back on masta's 7/3. If I turn flash off in cam app but turn torch on, I can take pics with light. If anyone has any suggestions, I'm all ears. Thanks in advance.

*EDIT 2*

I was troubleshooting with my phone plugged in. After a lock up, it would auto boot up to a battery splash with a no/unknown battery logo, then it would change to a charging battery splash. I swapped batteries. I can now take pics with flash. The old one was not low. I have no idea what happened but everything seems fine now. Sorry to clutter the board.
[Verizon Samsung Galaxy S III] landale:
Make sure you're on the MF1 firmware in the original post. It's now required on CM builds.
[Verizon Samsung Galaxy S III] Gatanater:
I am, the data failed even before I updated....
[Verizon Samsung Galaxy S III] bluezr1:
Did you try pulling the sim card and then reinserting it?
[Verizon Samsung Galaxy S III] AdMire:
I had that same issue like 2 weeks ago and I tired just about everything. I had to wipe everything but External Memory and reflash the ROM. It worked; pain in the ass but it worked. Although I was probably over due for a super clean flash like that.
[Verizon Samsung Galaxy S III] Gatanater:
I did exactly what you did before reliazing it was something else. My phone somehow lost the Verizon data access point name. I had to manually re add tbe apn and all was well.
[Verizon Samsung Galaxy S III] MWFD:
Anyone else have their LED light blinking on a notification even when the phone is docked in Daydream mode? How do I disable this?
[Verizon Samsung Galaxy S III] mastamoon:
That feature was just added. IDK if they made and on off switch.
[Verizon Samsung Galaxy S III] MWFD:
Do you know the most recent build that doesn't have this?
[Verizon Samsung Galaxy S III] mastamoon:
Not off hand. Check the official changelog.
[Verizon Samsung Galaxy S III] Droosh:
LeanKernel
[Verizon Samsung Galaxy S III] soapinmouth:
Planning on building one with this?

Sent from my liquid smooth gs3
[Verizon Samsung Galaxy S III] edif30:
Running 1-16 and I don't see Chronus the app in the drawer??? I see the app in manage app but no where to get into settings? Is it because its FC? I've done the clear data but still the app icon is no where to be found and upon a reboot it stops.
[Verizon Samsung Galaxy S III] OaklandZoo:
I'm on the 1-16 build and people are complaining that they are echoing. I thought this was fixed. Is there a setting to fix this? If not, I have to flash to something else. :(
[Verizon Samsung Galaxy S III] mastamoon:
Download - http://d-h.st/b58

1/20 with the usual cherry picks but no reverts for a2dp. Just a test to see if that merged commit earlier fixes a2dp officially.

Test and let us know.
[Verizon Samsung Galaxy S III] OaklandZoo:
I'll try to dirty flash this tonight to see if it solves the call echo problem too.
[Verizon Samsung Galaxy S III] invisiblek:
Did you enable the fix via an overlay?
[Verizon Samsung Galaxy S III] mastamoon:
Should because we are back to using the caf drivers.
[Verizon Samsung Galaxy S III] bobby janow:
It doesn't work for me. Not your build mastamoon, but one with the commits.
[Verizon Samsung Galaxy S III] mastamoon:
So a2dp not working with that a2dp commit that was merged? On somebody else's build?
[Verizon Samsung Galaxy S III] mastamoon:
No. Just repo sync n build without the reverts I was using. Guess that's a no no?
[Verizon Samsung Galaxy S III] invisiblek:
You have to enable the fix via an overlay. As Bobby said though, it doesn't work. He tried my build. This fix is for a different problem.
[Verizon Samsung Galaxy S III] bobby janow:
Yes, as you see Invisiblek built on the latest and it was the exact same issue. 35 seconds maybe and done. Back on your revert from the 18th now.
[Verizon Samsung Galaxy S III] mastamoon:
Ah OK.

Ah well.. So close! I did fix MMS though. :banghead:
[Verizon Samsung Galaxy S III] PerCompLLC:
Just got done talking with my mother... No echo here... mastamoon's 1/20 unofficial
[Verizon Samsung Galaxy S III] bobby janow:
I want the 1/30 build. Linky?
[Verizon Samsung Galaxy S III] dems86:
You got a build from the future? Makes sense that echo is fixed by then.
[Verizon Samsung Galaxy S III] PerCompLLC:
Oops. 1/20.

---------- Post added at 06:31 PM ---------- Previous post was at 06:30 PM ----------

Okay, enough... LOL! I'm an idiot okay? :)
[Verizon Samsung Galaxy S III] NegativeOne:
I'm very confused - So what's the status on the a2dp? I can't piece it together from these posts. It sounds like official hasn't fixed a2dp right?
[Verizon Samsung Galaxy S III] sparkerjc:
No. Masta's 1-18 build works though.
[Verizon Samsung Galaxy S III] MWFD:
Ok I looked it up. If anyone else is looking for this, it looks like 6/29 was the first official nightly with the LED still blinking while in daydream mode, so 6/28 would be the last nightly without it
[Verizon Samsung Galaxy S III] odmejia:
Are you on the latest nightly? If not let me know which one you are on.. I am on the stable 10.1.0.3 but reception at work is not as great as it use to be, 3G comes in and out. Usually I am on 4G at work which is great to tether off.. thanks in advance
[Verizon Samsung Galaxy S III] Jdelta9889:
Maps Problems

When navigating for over 10 minutes the screen becomes unresponsive and take awhile to come back to being able to update the map. I am using 7-3-2013 unofficial. I do not get this problem with CR or Beans. Is it a CM problem or maybe an issue with 4.2.2 and maps application. Either way I wanted to get the issue out there and see if others have experienced the same issue. No overclocking or voltage changes here. using stock kernel that came the ROM.
[Verizon Samsung Galaxy S III] landale:
The S4 Google Edition blobs were merged on 7/1 I believe. It's possible they are only in the nighly's as they weren't merged until after 10.1 went stable.
[Verizon Samsung Galaxy S III] juancaperez2000:
No problems here I drove last friday from DC to Kings Dominion in Richmond VA, whit out an issue running same unofficial nightly that you are
[Verizon Samsung Galaxy S III] mastamoon:
Same, used navigation a few times this weekend.. a few 1hr+ trips without a hiccup.
[Verizon Samsung Galaxy S III] odmejia:
Well I am going to try the first 7/3 nightly and see how it works out.. the stable version was added 7/2 so I would assume it would still work well but then again could be possible its only on the nightly versions, Thanks for the tip
[Verizon Samsung Galaxy S III] goldsmitht:
I understand that some signal issues may exist between TW and AOSP based roms, however, would that explain the difference between WIFI signal strength as well? And i mean the strength the SIII reads the signal, not the WIFI HotSpot signal strength.

Reason is this: My wife's RAZR HD can get WIFI signals that i can't read using CM10.1. I also noticed that while i was testing out Obsessed 1.0 this weekend (TW based) it could also see signals that my phone on CM10.1 hasn't picked up.

so was just curious if this was indeed a sympton of CM10.1 / AOSP based roms, or is there something i can do to make my phone pick up weaker signals better.

:confused:
[Verizon Samsung Galaxy S III] mastamoon:
Do you have your phone set to ignore weak WIFI AP's? If not it might just be that CM10.1/AOSP is set to ignore a different signal threshold vs TW. Haven't seen much issue with WIFI as a whole in CM so don't know if its more a feature vs a bug.
[Verizon Samsung Galaxy S III] goldsmitht:
don't think i do, in fact remember checking that box when i was looking at various apks as a work around.

would that setting be under the WIFI section?

also, have normally used 3rd party kernels in the past as they seemed to get better gas mileage, HOWEVER...

CM10.1's latest (think its called "dirty") has given me pretty much the best battery life as any of them. straight out of the box, ondemand and deadline (any chance of getting ROW added as a I/O?) Thanks for all the good work

:good:
[Verizon Samsung Galaxy S III] mastamoon:
Yeah its under advanced in wifi.

ROW is a choice in as an I/O scheduler.
[Verizon Samsung Galaxy S III] goldsmitht:
as i thought, don't have "avoid poor connections" checked, so shouldn't be a settings problem.

and as for the ROW I/O, all i can say is it was a brain fart; i even have it checked. BUT to my defense, was testing a TW ROM and it isn't available on that one's kernel.

maybe have to just play with it a bit. Wasn't some S4 radio thingy-a-ma-bobbies added to the CM10.1 base? Maybe some of them will help. Would be nice if it was all released so we could just play "nexus phone" and get this baby to really purr...

just saying...

:cyclops:
[Verizon Samsung Galaxy S III] mastamoon:
Nothing from the S4 Google Edition is for us I believe. There was a bunch of moving stuff around to support the jf/S4 but afaik we are not using any important stuff from that device.

Check https://github.com/TheMuppets/proprietary_vendor_samsung and under d2-common and d2vzw you will only see some thermald config changes which dont mean anything to us really.
[Verizon Samsung Galaxy S III] mastamoon:
7/08 build in the OP

-- repo sync @ 12pm EST

Added a link to my new favorite boot animation http://bit.ly/13Gnle3 (flash in recovery). Its from the HTC One Google Edition.
[Verizon Samsung Galaxy S III] V3TTOO:
Do you have an image that shows what it looks like?
[Verizon Samsung Galaxy S III] mastamoon:
https://www.youtube.com/watch?v=zuRJ93m7qNg&feature=youtube_gdata_player

Like this.
[Verizon Samsung Galaxy S III] V3TTOO:
Nice and simple. Do you have to add it in after every flash? I personally liked the Galaxy Nexus boot animation.
[Verizon Samsung Galaxy S III] mastamoon:
Yeah flash after every rom flash.. Using twrp makes it easy though. Add both zips to the queue and flash.
[Verizon Samsung Galaxy S III] V3TTOO:
Yeah, I been using ROM Manager to create a backup and install ROM, but to do more than one I have to buy the app. Might invest in that, if I decide it is worth the boot animation lol.
[Verizon Samsung Galaxy S III] mastamoon:
I think twrp will do that for free.
[Verizon Samsung Galaxy S III] mastamoon:
The ROMdb dev emailed me a Lil bit ago and said the fixed app should hit the market soon and I'll include it in my build tomorrow. Should clear up the downloading update bug. You will probably get a notification from the play store soon. :)
[Verizon Samsung Galaxy S III] shadrach47:
I updated the app last night. Today I got a notification for the 7/9 build and the download button worked great!
[Verizon Samsung Galaxy S III] mastamoon:
Awesome!
[Verizon Samsung Galaxy S III] mastamoon:
7/9 build in the OP

-- Repo sync @ 11:30am EST
[Verizon Samsung Galaxy S III] ElementR:
Edit: nvm it worked after a reboot.
[Verizon Samsung Galaxy S III] apacseven:
synced at 10 hours from now, nice! =p
[Verizon Samsung Galaxy S III] mastamoon:
That's how good I am! :beer:
[Verizon Samsung Galaxy S III] Chris123NT:
Download button in the app worked great today! :good:

And wow, this ROM has come a long way in 3 months since I last tried it. Phone volume issues are fixed, seems smoother, battery life is significantly better and the bluetooth is frickin amazing, seriously. I tap the next track button in my car and it goes to the next track with zero lag which never happened with TW roms, there was always a delay. Awesome work :D
[Verizon Samsung Galaxy S III] papasmurf3:
Play Music Mono?

Sorry if this has been posted but I'm running 10.0.1.3 and Google Play Music will only play in mono through headphones. It will however play in stereo if you forward the track a bit.

Seems to be the only App effected that I can see.
[Verizon Samsung Galaxy S III] AdMire:
Anyone having issues with Root Explorer? "Unfortunately, Root Explorer has stopped". It happens when I tried to long press/edit the build.prop. First time this has happened. I tried to wipe/reinstall the app. Just started happening on 07/09 - I even wipped EVERYTHING but external memory (even formatted data) and reflashed the ROM and still no go. Any ideas?

I actually can't long press anything without it stopping.
[Verizon Samsung Galaxy S III] Chris123NT:
You might be referring to a different app but the built in file manager works fine with no FC issues for me.
[Verizon Samsung Galaxy S III] AdMire:
The "File Manager?" Can you edit the build.prop with that?
[Verizon Samsung Galaxy S III] Chris123NT:
Yeah, just set it for root access then tap on build.prop and edit it with "Editor" I believe it's called.
[Verizon Samsung Galaxy S III] AdMire:
Holy crap, I never knew you could do that with File Manager. Took me a few minutes to find out how to give that app root access but it worked like a charm. Thanks a ton, Chris.
[Verizon Samsung Galaxy S III] sivarticus85:
Any ROM after this version has that issue fixed. Ironically, the nightlies are more stable than the... uh... stable ones.
[Verizon Samsung Galaxy S III] Chris123NT:
Yeah, it seems like that's always the case with CM. Stable build has some crazy bug and the nightly right after it fixes said bug lol.
[Verizon Samsung Galaxy S III] AdMire:
But anyone else having issue with Root explorer? It's just bothering me that I can't figure it out.
[Verizon Samsung Galaxy S III] apacseven:
You can try clearing data for the app in app manager. I know you wiped data but still worth a shot. Maybe try fixing permissions, but I doubt that is going to do anything.
[Verizon Samsung Galaxy S III] AdMire:
I did it all. Wiped the data in the app, then fixed permissions again for the hell of it. Keeps 'unfortunately stopping'. Never happened before. I love this app too. Maybe someone will have a resolution or insight.
[Verizon Samsung Galaxy S III] damnyouwaffles:
Hey Masta, I'm still kinda new at AOSP type ROMs. What does repo sync do in the updates?

---------- Post added at 02:16 AM ---------- Previous post was at 02:15 AM ----------

What kind of issue?
[Verizon Samsung Galaxy S III] shadrach47:
Not sure if it's related at all, but since a couple days ago Cloud Music Importer app hasn't worked for me. Everything I do, wipe data, cache, uninstall, nothing gets it to work. It just opens a black screen then FC.

I'll see if going back to older build helps.
[Verizon Samsung Galaxy S III] AdMire:
Just a few posts up I explained it. It stops working any time I long press something, build.prop for example. Or thing to long press an app to delete it. I went back to 06/06 and it worked. Can anyone just try root explorer and long press some files and see if it 'unfortunately stops'?
[Verizon Samsung Galaxy S III] cesium:
Repo sync means he synced his rom source with the official cm10.1 source repository. Thus any commits to the cm10.1 repo up until the sync time are reflected in masta's rom.

---------- Post added at 09:17 AM ---------- Previous post was at 09:14 AM ----------

Just tried root explorer 3.01 with no issues long presssing on files or folders. Am on 07-03 nightly.
[Verizon Samsung Galaxy S III] AdMire:
Thank you. I had no problem on 06/06 (that was my last back up I could flash back too). Now I'm on 07/09 and it stopped working after two complete clean flashes.
[Verizon Samsung Galaxy S III] mastamoon:
I also don't have a problem with root explorer. Do you get the dialogue for root permissions when you try to edit? Try installing something like superSU to see if its a superuser/root permissions issue.
[Verizon Samsung Galaxy S III] AdMire:
I'll try that. It gets root access and I can navigate thru files and folders, but anytime I try to long press anything, it stops and exits the app. Maybe there is an issue with the permissions, I'm gonna get superSU and check it out.

Well superSU didn't do anything. Anytime I long press anything, I get this and it closes.

Apparently I can't upload pictures right now. Anyway, just says unfortunately this app has stopped.
[Verizon Samsung Galaxy S III] mastamoon:
Strange. Can you long press in the stock file manager?
[Verizon Samsung Galaxy S III] AdMire:
Yes, I can. Typically I can figure stuff out Google'ing it and such, but this is just bothering me because I can't figure it out. I've reinstalled it, wiped it, clean flash the ROM and flashed back to 06/06 and it worked. I don't know what else to try! Haha! I really appreciate all your guys help though, it's very much appreciated.
[Verizon Samsung Galaxy S III] mastamoon:
Do you have a theme applied or anything else that's not stock?
[Verizon Samsung Galaxy S III] AdMire:
Actually, yes I do have a theme applied... I have the AC!D mod installed as well, but neither effected RE in the past. Should I go back to stock theme?

Went back to stock theme, cleared the caches, still no go.
[Verizon Samsung Galaxy S III] RED ZMAN:
Have you wiped System any time recently?
[Verizon Samsung Galaxy S III] shadrach47:
Well, you solved my issue. I was running a new theme, Holo Glass. Guess the app didn't like the changes. Thanks
[Verizon Samsung Galaxy S III] mastamoon:
Did you go back to stock theme by reinstalling the rom or flash a "stock rom". I would wipe system then reinstall the rom and gapps only and see what you get before adding anything else to the mix.
[Verizon Samsung Galaxy S III] AdMire:
I wiped everything except external data. After thinking about it, I wonder if it has to do with the fact that the app isn't a "market app". My buddy sent me the newest one a month ago but then again, it always worked on every nightly up until now. It's okay, thanks for all the help. I realized I'm cluttering your thread with this.
[Verizon Samsung Galaxy S III] Gatanater:
Any whereabouts on our update to fix the "loophole" in Android
[Verizon Samsung Galaxy S III] ugachris:
http://www.cyanogenmod.org/blog/cyanogenmod-10-1-1-release
[Verizon Samsung Galaxy S III] mastamoon:
Ill have a build out today that should incorporate those fixes.
[Verizon Samsung Galaxy S III] Hybridnoob:
I thought those were merged into the nightlies a couple of days ago. No?
[Verizon Samsung Galaxy S III] mastamoon:
http://review.cyanogenmod.org/#/c/45026/ , http://review.cyanogenmod.org/#/c/45025/ I believe are the commits that fixed the issue, but I wasn't sure if it was all of it. If that is so, it has been in my builds since 7/2. Some things do not show up in gerrit, so I wasnt fully sure when exactly the switch was flipped, so to speak.
[Verizon Samsung Galaxy S III] zcmack:
I've had terrible reception (both reported and actually experienced) as well as data speeds since upgrading to the MF1 radio. I upgraded on an older nightly and then upgraded my rom to the 7-9 release. Do I have any options or do I just have to wait until a new radio is released and hope it resolves my issues?
[Verizon Samsung Galaxy S III] mastamoon:
7/11 build in the OP

-- repo sync @ 2:30PM EST
[Verizon Samsung Galaxy S III] Chris123NT:
This build is running awesome, only thing I noticed is I still get the lovely 0 db 99 asu thing under signal every now and again, doesn't really bother me though since data doesn't seem to drop when it happens, just a general observation I made.

Also with Bluetooth audio every once in a while the phone hard freezes when connecting to the car (screen wont turn on) and I have to do a battery pull, anyone else seeing that?
[Verizon Samsung Galaxy S III] dushotgun:
Hey is anyone else having problems with usb otg? When I plug it no event is registered in logcat. It won't mount unless I use my cable I spliced for external power.
[Verizon Samsung Galaxy S III] Stealth111:
I get the 0dBm/99asu actually quite a bit, and my data crawls to a stop. It literally won't even load a webpage when it happens. It seems like issue was nixed a while back, but is now back again. I wish I could remember when it was, but back then, it was so rare for me I forgot all about it. I hate when I need to do something and it is stuck, makes me start to hate my phone. Not quite enough to go back to stock though! Well maybe.... If my Verizon Visual Voicemail stays broke, I keep getting data stalls, I would be only about 1 more shovel away from a ditch..

Other than that, keep up the great work! It still is the best rom out there...

Sent using Tapatalk
[Verizon Samsung Galaxy S III] Chris123NT:
If your data stalls when the 0DB thing hits, you can try disabling LTE temporarily as the issue never seems to pop up when on 3G, so that's a quick way to get data back if you need to, and you can add it to the quick settings pulldown which I'm sure you already know.
[Verizon Samsung Galaxy S III] mastamoon:
It's being worked on, promise.
[Verizon Samsung Galaxy S III] Chris123NT:
Awesome, that is pretty much the last thing I can see that needs to be fixed and this ROM will be perfect.

Not going back to stock because of it though, i just can't take TW anymore lol

And as for the BT issue, hasn't happened yet on 7/11, happened 2 days in a row on 7/9 so I'll see how it does tomorrow.
[Verizon Samsung Galaxy S III] Chris123NT:
I just noticed that there's a signal strength test build on get.cm. I wonder if this helps the 0DB issue. Any way we can figure out what commits are in this and cherrypick them for today's build masta?
[Verizon Samsung Galaxy S III] mastamoon:
7/12 build in the OP

--SamsungQualcommRIL: cdma lte sleep fix - http://review.cyanogenmod.org/#/c/45374/ - Doesnt seem to help my 0dbm/99asu issue just yet.

--TunnelAudio: Fixes playback with Qualcomm tunnel audio for players which use gapless api - http://review.cyanogenmod.org/#/c/45439/ - hoping this helps with you guys that have the weird headphone audio switching back and forth issue

--repo sync @ 11:30AM EST
[Verizon Samsung Galaxy S III] Obaterista93:
People are having SMS issues on the official where it'll send, but display as "sending" for a while and fail out (even though the message sent). Have you experienced this on your build?
[Verizon Samsung Galaxy S III] mastamoon:
Yeah looks like mms sends Ok, sms also sends Ok but is stuck "sending".
[Verizon Samsung Galaxy S III] AdMire:
Got the same issue.
[Verizon Samsung Galaxy S III] mastamoon:
http://review.cyanogenmod.org/#/c/45444/

Probably fixed here. I'll try and roll another build out today or tonight. Still watching the 0dbm/99asu work being done, hoping to get that in there too.
[Verizon Samsung Galaxy S III] Obaterista93:
You're awesome, man. :thumbup:
[Verizon Samsung Galaxy S III] PerCompLLC:
Yup, happening here as well... Looking forward to the replacement build.
[Verizon Samsung Galaxy S III] Chris123NT:
SMS thing happening here as well, looking forward to the fix.
[Verizon Samsung Galaxy S III] thefuzz4:
I too am having this issue.

---------- Post added at 03:00 PM ---------- Previous post was at 02:59 PM ----------

Giving the experimental a whirl. Will post to let you know how it goes :)