yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] V3TTOO:
Man, I am so confused on all the stuff that is going on around here now a days.

FYI, there are libs with both the stock and 4.2(Photosphere) cameras. They are used for editing and filters, and there is one other for the 4.2 camera. I had issues when I used 4.2, and it caused issues when I reflashed. I had to do a complete /system wipe to make sure those lib files were properly replaced by the stock cam. Before that I had too many issues, including streaking in pictures.
[Verizon Samsung Galaxy S III] mastamoon:
http://review.cyanogenmod.org/#/c/37261/ - this might fix the 1 channel audio issue, making a build now myself, should be included in the next nightly

http://review.cyanogenmod.org/#/c/37274/ - should fix the camera issue for good, making a build now myself, should be included in the next nightly
[Verizon Samsung Galaxy S III] corey1031d:
Where can the photosphere be found in 10.1RC1? I'm sorry if this has been asked.
[Verizon Samsung Galaxy S III] mastamoon:
it cant. You need to flash a 3rd party package.
[Verizon Samsung Galaxy S III] corey1031d:
Could you possibly post a link, please?
[Verizon Samsung Galaxy S III] theraptscallion:
I will flash this the second as you post it and I can pull it down over 4g! :good:
[Verizon Samsung Galaxy S III] mastamoon:
5/09 build in the OP

-- hopefully camera and 1 channel audio is fixed with this build

-- repo sync at 3:05PM EST
[Verizon Samsung Galaxy S III] mastamoon:
Sorry, I dont have that info. Ive never used it. Maybe somebody will help you out though.
[Verizon Samsung Galaxy S III] mastamoon:
No freezes on my phone when changing settings in camera with my 5/09 build I just posted :)

Somebody else will have to check audio and let us know.
[Verizon Samsung Galaxy S III] sivarticus85:
Audio is still coming out the right side only. Tested on PowerAmp, Apollo, and Spotify
[Verizon Samsung Galaxy S III] mastamoon:
With the build I just posted? Not the one from earlier?

Does unchecking that volume option fix?
[Verizon Samsung Galaxy S III] sivarticus85:
Right, sorry. Your 5/09 build a few posts back.
[Verizon Samsung Galaxy S III] GideonX:
Camera settings working like they should again.
[Verizon Samsung Galaxy S III] odub303:
Fixed for me. Uncheck the option in the volume panel.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] sivarticus85:
The option isn't there on the 5-09 build. I thought it was removed?
[Verizon Samsung Galaxy S III] mastamoon:
Removed on the first build. The second build left the option in to see if the revert Cyanogen did fixed the issue. Doesn't look like it.
[Verizon Samsung Galaxy S III] sivarticus85:
Oh ok. I only saw the first build. Were there new audio drivers merged recently?
[Verizon Samsung Galaxy S III] billquinn1:
Did anyone ever figure a workaround for the Pandora new station keyboard issue? I remember the discussion but don't see anything.
[Verizon Samsung Galaxy S III] xHoLyx:
Well, we can always do it from our computer, right? ;)
[Verizon Samsung Galaxy S III] bmeek:
Stereo appears fixed in the May 10 nightly and RC2. thanks to all involved :).
[Verizon Samsung Galaxy S III] GideonX:
Anyone else notice the screen color temperatures in settings->advanced do not change the display colors? Works ok via term emulator when setting via sysfs.
[Verizon Samsung Galaxy S III] xHoLyx:
Change > Screen off > On works for me.
[Verizon Samsung Galaxy S III] GideonX:
Nvm me, forgot to chown the entry to system system. Oops.
[Verizon Samsung Galaxy S III] mastamoon:
Hopefully tomorrow github will stop being a ***** and I'll be able to put out a build.

What is your guys feelings about that trebuchet cherry pick I use? I don't think if it will ever get merged so it must not be all that and a bag of chips. I don't use stock launcher so I have no feeling either way.

LMK
[Verizon Samsung Galaxy S III] ddggttff3:
I personally use apex, so I have not really noticed it. Personally if people find it useful, keep it in, but I give a vote to remove it if it will never get merged.
[Verizon Samsung Galaxy S III] Hybridnoob:
Using Nova here...
[Verizon Samsung Galaxy S III] PVLMTREE:
Nova is my go-to launcher. (:
[Verizon Samsung Galaxy S III] NegativeOne:
I'm getting an msm_otg wakelock a lot and it's causing horrible drain. I'm also seeing cell standby and phone calls drain a whole lot of battery. Rebooting seems to help it sometimes.
[Verizon Samsung Galaxy S III] sthpaw01:
I use stock launcher, I like being close to stock android.
[Verizon Samsung Galaxy S III] Reborn627:
I use the stock launcher. I'll be honest, I'm not sure I've noticed a difference in the touch responsiveness, though I can't say I've payed a lot of attention to it.

Thanks

Ray
[Verizon Samsung Galaxy S III] RED ZMAN:
How's the flickering and rebooting lately everyone? I've been trying to keep up here, but need to update my phone as I'm on April 12 build. Decently stable, but a few issues. Iw ant to see if the updated wifi stuff fixes a few problems I'm having.

And what is the "Kernel" of choice right now? Built in or other?
[Verizon Samsung Galaxy S III] theraptscallion:
I've encountered the msm-otg wakelock repeatedly. For me, it's linked to when phone reboots while it's plugged in, which occurs on this build more because of the random reboots (fixed for me by using KToonsez kernel). I've also had it on TW builds, so I don't think it's a cm10 specific bug. Rebooting always fixes it (provided I'm not plugged in when I do it).

As for flicker/reboot, I have no flicker but the reboots persist as of 5/9 with a clean install. I default to the KToonsez kernel because I have settings I import for Ktweaker, which fixes my reboots
[Verizon Samsung Galaxy S III] goldsmitht:
have had no problems with any of the CM10.1 based ROMs lately in regards to flickering or rebooting. HOWEVER, i do use the latest LK kernel, so that might have something to do with it. And everythhing else is buttery smooth

:cyclops:
[Verizon Samsung Galaxy S III] NedDasty:
Everything's been more or less good for me. Once in a while the camera freezes when I'm changing a setting, but that only happens sometimes. Running on LeanKernel 5.9.
[Verizon Samsung Galaxy S III] mastamoon:
5/14 build in OP

-- removed the Trebuchet cherry-pick.. let me know if you stock launcher guys notice a difference good or bad

-- removed the Standalone Power Collapse revert.. let me know if you guys notice a battery hit or anything

-- repo sync @ 3:10PM EST

***** Got constant reboots? Update Your Phones! It was found that some/all of the reboots might be being caused by a mismatch in some firmware on our phones. This issue was causing a random reboot due to possible DRM issues caused by d2vzw phones not updating to the latest TZ file from the OTA. InvisibleK put together a flashable zip to update your phone to the latest and greatest. It also flashes the latest modem, if you dont like it.. tough! :P J/K.. feel free to download to your older modem of choice.. but latest is probably the best way to go honestly!

***** Along those same lines, though it doesn't fix anything in particular, we found out we can upgrade our SBL (secondary boot loader) files to the latest OTA versions also. So please feel free to flash that zip also.

Both files can be found in the OP!

Thanks to invisiblek for all his hard work trying to figure out this reboot issue. And thanks to noobnl for putting most of that hard work right in the circular filing cabinet with the pointer to the TZ fix. And finally, thanks to all the testers that put their phones stability on the line to help us track it down by flashing 'fixes' constantly over the past month.

:cyclops:
[Verizon Samsung Galaxy S III] V3TTOO:
So what you are telling me is that since we are using a custom ROM we don't get these updates that are normally provided? e.g. the stock ROM updates all that stuff OTA, but CM doesn't handle those files. Correct?
[Verizon Samsung Galaxy S III] mastamoon:
Yeah, an OTA would update all of these things everytime.
[Verizon Samsung Galaxy S III] stkiswr:
Hey I was going to tell you I directed a friend to download the rc2 from cm on his nexus. I looked into that Mms and all the mods we talked about are already there. I pulled the Mms from toro and dropped it in with no issues. Pics look good both ways. Didn't know if while building you could just pull the Mms and save yourself a little time
[Verizon Samsung Galaxy S III] V3TTOO:
Alright. Now I know that this is something I should look into next time. So pretty much, if we didn't have those files from InvisableK we would have to go to stock, updated, then back to CM, correct? I would assume backing up with ROM Manager and restoring after would work once the firmware has been updated. And would a rooted stock ROM work for updating the firmware?

Sorry for the questions, just trying to cover any possible situations.
[Verizon Samsung Galaxy S III] mastamoon:
You would only get these files by either OTA or an Odin flash of a fully stock rom. They will survive any sort of other rom flash through CWM or whatever.
[Verizon Samsung Galaxy S III] V3TTOO:
Alright, awesome. I will make sure when I get my phone back to update everything first.
[Verizon Samsung Galaxy S III] Hybridnoob:
Is the option to use volume keys to control media volume still in the nightlies? I noticed it was not in RC2. I'm on 5/9 and it's very smooth by the way. I like that feature and don't want to lose it by updating if it's been removed.

Edit-nevermind, its there :D
[Verizon Samsung Galaxy S III] jlokos:
I tried to do a clean flash of the 5/14 build, however, no matter what I try, I can't get the wifi to connect. I've never had this issue before and it was just working on the rom I had on the phone before I attempted this flash. Anyone else with this issue?

edit: No problem with the rom; apparently, the wifi went out on my side of the office building.
[Verizon Samsung Galaxy S III] NegativeOne:
What is TZ?
[Verizon Samsung Galaxy S III] GideonX:
http://www.arm.com/products/processors/technologies/trustzone.php?setcookie=classic

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] slambert27:
TrustZone...I believe
[Verizon Samsung Galaxy S III] Stealth111:
Is there any way to verify if the TZ & SBL are currently at the correct level on a phone?

Sent using Tapatalk
[Verizon Samsung Galaxy S III] apacseven:
Yep, by flashing the aio package. If you have already flashed it and recovery returned a success code, then you are good to go. If you havent flashed it, and you didnt take the last OTA update from a completely stock phone, then you are not running the correct version.
[Verizon Samsung Galaxy S III] RED ZMAN:
Gotta say, flickering is pretty much non existent for me now, and the phone is running like a beast.

No BT problems as of yet, I'll keep you up to date on that though, usually takes a few days before that arises.

Using the 2.5 TWRP I did the advanced wipe with System, Dalvik and Cache.

Flashed the 14th build, GAPPS, the new SBL, and the AIO zips. Rebooted to make sure it booted fine, then went back into recovery and flashed LeanKernel 5.9

Really running clean now, really fast, and REALLY smooth.

Thanks for the great work man. Every new flash is another delay in getting an S4. LOL
[Verizon Samsung Galaxy S III] goldsmitht:
Does wiping system require resetting all my apps and data? As in a clean flash?
[Verizon Samsung Galaxy S III] RED ZMAN:
^^^

Nope.

Just requires you reflash GAPPS.

I used to do this all the time, got out of the habit last year. Really helps clean up some of the pestering issues that hang around.
[Verizon Samsung Galaxy S III] wrippel82:
wow

nice work guys! after flashing InvisibleK's flashable zip's I haven't had a single reboot on the stock kernel. made my day!!
[Verizon Samsung Galaxy S III] eppo12-:
Hey mastamoon,

I don't know if you saw this, i posted in the official thread. Can I get your input on it?

Is there any work being done on the issue of Google voice search not working when phone is in car dock? (it just says RETRY) if anyone needs anything to troubleshoot, just let me know, I'll give you whatever you need.

Thanks
[Verizon Samsung Galaxy S III] no0n:
I'm on the 03/12 build, I flashed to the latest stock with Odin beforehand. Have been needing to do a lot of battery pulls lately. I'm going to flash to the 5/14 build but I'm not sure if I need to do a clean wipe or if I can dirty flash. With these RC's flying around lately I'm sure I'll be needing to do another clean wipe sometime soon.

Clean or dirty?
[Verizon Samsung Galaxy S III] RED ZMAN:
DO what I did above, you should be fine.
[Verizon Samsung Galaxy S III] mastamoon:
5/15 build in OP

-- added Mms: Add the ability to select recipients from a checkbox list - http://review.cyanogenmod.org/#/c/34094/

-- repo sync @ 3:10PM EST
[Verizon Samsung Galaxy S III] mastamoon:
eppo12-

The best bet would be to flash to RC2. Then get a log cat of the issue and report it to https://jira.cyanogenmod.org/issues/?jql=

I'm not of much help for something like that. Sorry. :)
[Verizon Samsung Galaxy S III] Reborn627:
I've not given this a try lately, with cm10.1, but I did run into this on my GS3 with the stock 4.1.2 ROM. Seems that it is some sort of issue. The "fix" or work around I was told was to enable the key press sounds. You know, the stupid sounds that occur for every touch you make. Somehow that corrected the issue on the GS3. I don't know if it's related in anyway but that's my personal experience. I'll give the voice function a shot on the way home from work. I found it affected search as well as voice to text. Any voice input function had the same failed result.

Ray
[Verizon Samsung Galaxy S III] NegativeOne:
Call volume control is broken on the 5/14 build...
[Verizon Samsung Galaxy S III] mastamoon:
Try checking or unchecking the volume button controls ring tone volume. In settings, sound, volumes.
[Verizon Samsung Galaxy S III] SilentAce07:
Is it possible the activation bug was a result of this as well?
[Verizon Samsung Galaxy S III] tehloxely:
I flashed the latest modem/rpm/tz from Dan's Google+ https://plus.google.com/u/0/104277415207525128383/posts/iAVpVPYqMtM

....But what is this SBL link and what does it do?
[Verizon Samsung Galaxy S III] Stupifier:
Due to reports of reboots/crashes/bt stream issues, I've been extremely cautious the past couple of months and have not flashed any new builds since 03/15/2013.

Is it official.....has the reboot/crash issue been crushed? I've been following this thread (and all the CM 10.1 threads) closely. I know all the devs have been hard at work to determine the cause of reboots and fix it.
[Verizon Samsung Galaxy S III] cesium:
lol the quote in the post above you explains....

"***** Along those same lines, though it doesn't fix anything in particular, we found out we can upgrade our SBL (secondary boot loader) files to the latest OTA versions also. So please feel free to flash that zip also."
[Verizon Samsung Galaxy S III] tehloxely:
LOL wow I completely missed that *head desk*

So it's safe to flash regardless of any ROM/Version?
[Verizon Samsung Galaxy S III] cesium:
Should be. I flashed it on one of the older CM builds, and then flashed a new build afterwards with no issues.
[Verizon Samsung Galaxy S III] apacseven:
Yes, as of now, it appears to be solved. I highly recommend making a backup, flashing invisiblek's aio package, and installing cm10.1.

Sure is, flash it and give it a go.
[Verizon Samsung Galaxy S III] SilentAce07:
On the 5/15 build with those extra radio and sbl files flashed.

No noticeable bugs. No activation issues. No reboots.
[Verizon Samsung Galaxy S III] V3TTOO:
http://xdaforums.com/showthread.php?t=2046439

That is a guide to root and unlock the new 4.1.2 MB1 d2vzw. There is a bootchain tar file for ODIN that does the same thing. So if you are starting out fresh, you can follow that too. Maybe put in in OP, and the flashable zip for people already on custom ROM.
[Verizon Samsung Galaxy S III] SilentAce07:
Yeah. Let me just say that between the smoothness, the battery life, and the lack of bugs, this 5/15 build is far and away the best experience I've ever had on this phone.

Battery life seems very close to stock, and the entire ROM is buttery smooth. Scrolling is incredible.

Great work to masta and invisa and the cm team (and anyone else I forgot). I really think the flashable invisa files that fixed the reboot issue had some other positive effects in bug fixing.
[Verizon Samsung Galaxy S III] PVLMTREE:
I still get flickering (massive screen flickering that is), on the 5/15 build.

I only see it in the Instagram app though.
[Verizon Samsung Galaxy S III] mastamoon:
I use instagram, no flicker here. Have you wiped system or clean installed recently?
[Verizon Samsung Galaxy S III] s'pht:
Wait, there's no Flickr on Instagram? (sorry - couldn't help myself!)
[Verizon Samsung Galaxy S III] mastamoon:
Niiice :thumbup:
[Verizon Samsung Galaxy S III] NegativeOne:
I still can't control in-call volume. toggling stuff didn't help. More importantly, I'm also still getting horrible battery drain from "Cell Standby", as well as cell calls. WiFi or 3G doesn't matter.
[Verizon Samsung Galaxy S III] PVLMTREE:
I have probably on one of the April builds. But, it won't hurt to try a clean install again I hope.

Side question: Do anyone know a great way to restore Personal Dictionary after a clean install? Kind of a pain in the butt to re-enter everything in.

Unless the only way is to copy over the system file.
[Verizon Samsung Galaxy S III] stefilini:
I believe helium backup will back it up and restore the dictionary.
[Verizon Samsung Galaxy S III] mastamoon:
I tested a call today, was the first call I made since installing my latest build. Volume on the start of the call was fine. I was able to lower and raise the volume with the volume keys no problem. Low volume was low.. high volume was higher but not screaming. Totally controllable and expected performance.

Have you installed a different kernel or anything over the rom? Or any themes/mods?

My Time w/o Signal is currently 12%, which is acceptable being I work in an office building with horrible signal most of the time. No abnormal wakelocks shown.
[Verizon Samsung Galaxy S III] Hybridnoob:
Same here. Great build! :D
[Verizon Samsung Galaxy S III] WhammyDroid:
Will there be a new build today?
[Verizon Samsung Galaxy S III] mastamoon:
Sure. There isn't much going on that applies to us but I can put up a build no problem.
[Verizon Samsung Galaxy S III] apacseven:
I saw someone mention Helium as being able to do this, I also know that Titanium is able to back up the user dictionary as well.
[Verizon Samsung Galaxy S III] RED ZMAN:
Gotta say, 15th build is really stable. No issues to report of any kind at all right now.

Not one.

If there were anything to even comment on, is that my battery isn't lasting as long.

I think cause I'm using the phone more though. LOL

L O V E I T!
[Verizon Samsung Galaxy S III] goldsmitht:
i've noticed worse battery stats as well, but using LK 5.9exp1 and didn't want to bring it up. And really haven't attempted to do study as to why, just chalked it up to bad service area as well as over-use of my phone.

and to take it further, have noticed it on AOKP nightly as well, so there might be something there.
[Verizon Samsung Galaxy S III] cesium:
Do you know if all the PIE control stuff that they added works?

I see 5/17 is up now! Flashing in a few!
[Verizon Samsung Galaxy S III] mastamoon:
5/17 build in OP

-- repo sync @ 3:35PM EST

Have a great weekend everybody!
[Verizon Samsung Galaxy S III] airmaxx23:
I posted this in the official thread as well since it's happening with both builds.

So I've had a bug with the messaging app that has been present for quite a while where I only get a partial notification sound when receiving a text message, I finally figured it out. It is caused by having the "quick reply" option turned on with "wake and unlock" turned on and leaving the messaging app opened. If I leave the messaging app opened and let the screen turn off I only receive a partial notification sound, sometimes only a fraction of a second long. If I close the messaging app prior to letting the screen turn off it works fine or if I disable "wake to unlock" it works fine also. I can replicate it at any time. Is this something that can be fixed?
[Verizon Samsung Galaxy S III] NegativeOne:
Odd. Thanks Masta. No, I'm using all default cm stuff, latest sbl, etc per your other post, and I just recently did a clean build.

I'll try another build when I get home.
[Verizon Samsung Galaxy S III] fromthesticks:
After installing today's build, I've tried taking a few pictures. The whole screen goes black and locks up. Have to pull battery. Even holding the buttons for a reset isn't working right.
[Verizon Samsung Galaxy S III] mastamoon:
I just snapped a few pics without issue.

You may have to go into camera setting and change the scene mode to anything but auto, reboot, then go back in and set it back to auto.
[Verizon Samsung Galaxy S III] Hybridnoob:
Do you have advanced reboot selected in developer options?
[Verizon Samsung Galaxy S III] fromthesticks:
I followed mastas instructions and the camera is working again fine now.

And yes I do have advanced reboot enabled
[Verizon Samsung Galaxy S III] jguns112:
Pressing the plus sign next to where you enter recipients on messaging causes the app to crash for me.

Also, I'm still getting the Pandora keyboard bug.. Is there a fix for this?

I'm on the 5/17 build
[Verizon Samsung Galaxy S III] mastamoon:
Mms recipient selector works fine on my phone. Maybe need to clear mms app data? Weird.

Not sure about the keyboard bug. Happen on official? Somebody needs to flash rc2 and get a logcat and submit to JIRA.
[Verizon Samsung Galaxy S III] stearic:
Is anyone having issues with Google+ where if they try to go into a post and the app quits with the "unfortunately, Google+ has stopped." error? Funny as it's not every posts that does that.
[Verizon Samsung Galaxy S III] mastamoon:
5/20 build in OP

-- some RIL cleanup work has been done by noobnl and are included in this build

-- repo sync @ 3PM EST
[Verizon Samsung Galaxy S III] V3TTOO:
Downloading now. Let you know if I have any issues.
[Verizon Samsung Galaxy S III] yiannit:
Anyone having problems installing Google+?
[Verizon Samsung Galaxy S III] GideonX:
Sounds like a Google issue, folks on official thread reporting same thing.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] Restola:
I can't hang up from a call with this build. Works normally on official 5/20.

Tapatalk via CM10.1 Galaxy S3
[Verizon Samsung Galaxy S III] goldsmitht:
Not having any issues with 5/20 and LK 6.0exp1. Google+ updated fine, and voted 5 times on dancing with the stars with no issues as well

:what:
[Verizon Samsung Galaxy S III] mastamoon:
No hang up issues here. :confused:
[Verizon Samsung Galaxy S III] Restola:
Weird. I refreshed 5/20 official and it works again (on official).

Tapatalk via CM10.1 Galaxy S3
[Verizon Samsung Galaxy S III] alee:
Anyone having Bluetooth related issues with pairing and reconnecting with 5/20? Have had BT issues since last night.
[Verizon Samsung Galaxy S III] goldsmitht:
haven't tried mine yet on 5/20, but usually when i have problems, i just clear listed bluetooth devices within bluetooth, and let them link again. that usually clears up the problem.

:cyclops:
[Verizon Samsung Galaxy S III] alee:
Yeah... no luck... even repairing devices wasn't working or intermittent at best.

Rolled back to 5/17 and BT worked immediately.
[Verizon Samsung Galaxy S III] mastamoon:
I just went through github and gerrit looking for something that would have changed BT behavior but do not see anything. I could easily miss something I suppose but nothing stands out unless it was part of another merge that really isnt listed in the description.

All I can say is delete the devices from bluetooth settings and/or wipe bluetooth data. Titanium Backup shows Bluetooth Pairings and Bluetooth Share... maybe one of them has some corrupted data?

You could also try using a few day old kernel and 5/20 to see if its kernel related.