yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] iofthestorm:
I think the scrolling thing was actually fixed one or two days ago. A fix was committed and for me it seemed to work (there was an attempt to fix it last week that didn't work). Never had screen artifacts though.
[Verizon Samsung Galaxy S III] Hybridnoob:
I had it, but Mastamoon's latest unofficial fixed it. I'm not sure what he added that fixed it, but I had issues until Friday's build.
[Verizon Samsung Galaxy S III] soohyunk83:
SD card storage for pictures on 4/14

The change log seems to indicate we can choose to store pictures on the external SD card now.

Can anybody who installed 4/14 confirm? :D
[Verizon Samsung Galaxy S III] ddggttff3:
I can confirm!

Options are:

internal storage

sd card

usb storage
[Verizon Samsung Galaxy S III] soohyunk83:
I noticed the battery drain faster as well.
[Verizon Samsung Galaxy S III] rjbmier25:
I have been having lockscreen issues, it seems to be a display issue where it will lock the screen unlock it then lock it again with just a single button press. Sometimes it will open the power menu display up as well. Any idea what this is?
[Verizon Samsung Galaxy S III] razorloves:
Bug report:

The share via SMS option is missing. Not sure when it disappeared. Also confirmed on vzw gnex. Seen a couple people mention it in their threads. When you share any picture via MMS, it shows up fine. But when you try to share anything that's text via SMS, its not there.

---------- Post added at 10:08 AM ---------- Previous post was at 09:52 AM ----------

Looks like this caused it. http://review.cyanogenmod.org/35152

EDIT: Yep. Just reverted that commit and the Messaging option came back.
[Verizon Samsung Galaxy S III] airmaxx23:
How did you revert the commit, is there a simple way to do it?
[Verizon Samsung Galaxy S III] razorloves:
you can revert it if you build your own unofficial nightlies. Otherwise, you can just replace the mms.apk with the one from the April 13th nightly. Mastamoon's next unofficial nightly should have it reverted.
[Verizon Samsung Galaxy S III] yznhmr:
I dont see any mention of Random reboots..

I have switched back to 3/17 which works good.. for the most part.. but any of the newer builds cause me LOTS of random reboots..every day.. any ideas how to rectify?
[Verizon Samsung Galaxy S III] airmaxx23:
I've been one the newer builds and haven't had any reboots at all. Are you using the stock kernel?
[Verizon Samsung Galaxy S III] soohyunk83:
4/13 doesn't have reboots but I definitely noticed it with 4/14.
[Verizon Samsung Galaxy S III] airmaxx23:
I wonder if it's kernel related, I'm using KT747 kernel and haven't had any reboots on 4/14.
[Verizon Samsung Galaxy S III] soohyunk83:
Anybody have an issue where the download directory on your internal SD card does not show up when you reboot into recovery?
[Verizon Samsung Galaxy S III] airmaxx23:
Which recovery are you using? Are you sure you have internal storage selected?
[Verizon Samsung Galaxy S III] soohyunk83:
Clockworkmod 6.0.3.1.

Yea i selected internal storage and didn't see my download directory listed.

Never had this issue before.
[Verizon Samsung Galaxy S III] s'pht:
I've found a bug with a particular media player (Mort Audiobooks http://xdaforums.com/showthread.php?t=616706 ) that is present on all of the builds *AFTER* April 8 but not on or before. Running the April 8th build it plays audio just like you would expect, running the 9th through the current (16th) it plays a loud click when the app initializes and then.... nothing. Headphones or not appears to be inconsequential to the bug. I suspect it's something to do with the kernel but I have nothing to substantiate that.

build.display: cm_d2vzw-userdebug 4.2.2 JDQ39 eng..20130415.233142 test-keys

build.fingerprint: Verizon/d2vzw/d2vzw:4.1.2/JZO54K/I535VRBMB1:user/release-keys

version.incremental: eng..20130415.233142

Looks like the interesting stuff happens around line 118 of the attached 4-16 logcat.txt (I also included the 4-8 version for comparison, they look rather a lot alike)
[Verizon Samsung Galaxy S III] kyuubi08:
Been having this issue with all versions of cm after the update to 3.4 kernel. When I use my music player (double twist) every time I make a selection on screen, use the soft buttons,or open an app, my audio skips pretty bad
[Verizon Samsung Galaxy S III] airmaxx23:
Fix permissions with ROM Manager and clear dalvbik/cache. Change kernels may fix it also.
[Verizon Samsung Galaxy S III] invisiblek:
I doubt this is fixed by a dalvik/cache clear

From this: http://review.cyanogenmod.org/#/c/35779/

I found this at CAF and need it tested: http://review.cyanogenmod.org/#/c/35949/

I'll upload a build shortly...

EDIT: give this a go: http://invisiblek.org/sch-i535/roms/cm10.1/cm-10.1-20130416-UNOFFICIAL-d2vzw-5.zip

(the build has both patches, we do need detule's kernel patch too)
[Verizon Samsung Galaxy S III] airmaxx23:
Fixing permissions and clearing dalvik/cache fixed it fit myself and someone else, I'm not sure which thing actually worked though.
[Verizon Samsung Galaxy S III] kyuubi08:
Works perfectly
[Verizon Samsung Galaxy S III] s'pht:
I tried this - the loud static is gone when I start Mort Audio Books but it still doesn't play any sound.
[Verizon Samsung Galaxy S III] invisiblek:
Odd. That app plays some things for me and not others. It wouldn't play a certain mp3, but another app would. It would however play some other audio files.

Pastebin of the error: http://pastie.org/7626227

I'm going to chalk this up as an app problem and not a rom problem since other apps (Apollo, Winamp) play this file just fine, and it does properly play

some

audio files.
[Verizon Samsung Galaxy S III] Amphibliam:
My Apollo app just force closes after being open for about 5 seconds. I'm on 4-16. Any ideas?
[Verizon Samsung Galaxy S III] uncleguito:
I ended up reverting back to M2 because of this. Ever since the 3.4 switch, I've had quite a few issues with audio (most notably that described above), as well as a "static/crackle" effect on about 15% of app open effects.

M2 was pretty perfect on my phone so I'll probably just stick with it until the many issues with 3.4 get sorted out.
[Verizon Samsung Galaxy S III] Gibscreen:
I'm not able to share to text anymore. Such as when I'm on a Web page in Chrome and want to share the url. Email, dropbox, evernote, etc. all show up as options but not text anymore. Anyone else experience this?
[Verizon Samsung Galaxy S III] invisiblek:
See about 4 posts up, try that build and see how it works

Tonight's nightly should have the patches in it, should fix your audio problems

Just merged: http://review.cyanogenmod.org/#/c/35995/
[Verizon Samsung Galaxy S III] PVLMTREE:
This early build of CM 10.1 is outstanding. This is the only AOSP ROM that works with my GSM Unlocked Galaxy S3 running on T-Mobile. Just waiting for the Data Function to be fixed! (: 4.2 is literally by far the best OS yet. Thanks CM team for making this happen.
[Verizon Samsung Galaxy S III] Syndicate7:
+1 me too :good:
[Verizon Samsung Galaxy S III] Mystikalrush:
I was one of the first to report data loss hence why its mentioned in the OP of this new thread.

The only quick way I was able to restore data was to simply restore my backup IMEI then all was well.
[Verizon Samsung Galaxy S III] flamus:
Wast that on the official nightly? If so, did you use this thread for your IMEI fix: http://xdaforums.com/showthread.php?t=1801997
[Verizon Samsung Galaxy S III] PerCompLLC:
Dirty flashed, installed the latest gapps, and cleared data on the clock app (per the OP so that clock wouldn't FC). Build works PERFECTLY! Thank you mastamoon!
[Verizon Samsung Galaxy S III] peaceofpi:
This is THE best rom I have used yet. Everything is working so much better than 10. 0 I was also able to install Wallet directly from the Play Store.
[Verizon Samsung Galaxy S III] Phush:
If I flash an unofficial build, will CM updater work when the officials get all straightened out?
[Verizon Samsung Galaxy S III] PerCompLLC:
Yes. The unofficial build was pulled directly from the CM repo. The only difference is that it has cherry picked commits and it was not built by the CM automated build servers.
[Verizon Samsung Galaxy S III] Restola:
As PerCompLLC said it should act identical and update using the updater without issues. mastamoon's (http://bit.ly/12yrtcw) flashed over my CM10 installation flawlessly using the instructions in the OP. I'm going to stay on it until the data situation gets sorted out in the official nightly.

It looks like there were new comments on the commits that would fix our data in the official nightly, but it doesn't appear that they were approved to make it in yet. Probably 12/19 will still have broken data when it builds but we'll see.
[Verizon Samsung Galaxy S III] goldsmitht:
MMS

Can anyone tell me if the MMS is working? I tend to use it a lot, but on latest nightly (CM10 and CM10.1 unofficial) the picture is borked, and goes sideways if i try to send a portrait framed photo (horizontal), if it sends at all; have been getting a MMS.apk has stopped error (or something like that) and messenger FC's.

Other than that, seems to be working
[Verizon Samsung Galaxy S III] WhammyDroid:
Does anyone know where CWM 6.0.2.3 is backing up the ROMs in CM10.1? It is not in it's original location of /sdcard/clockworkmod/
[Verizon Samsung Galaxy S III] Zacharybinx34:
How did you get it to show up in the play store?
[Verizon Samsung Galaxy S III] will.bates94:
Yeah seriously....it says my device is incompatible with wallet....
[Verizon Samsung Galaxy S III] Div033:
Has anyone noticed significantly worse signal with 10.1? I'm consistently below -100 whereas on TW I hover in the 90s mostly.
[Verizon Samsung Galaxy S III] will.bates94:
Yes I certainly am also. I'm in a server class and I sit in the same seat everyday and I've had 2 bars of 4g consistently considering I'm in a concrete building and now this morning as I sat down I have 1 to no bars. Something needs tweaking.

---------- Post added at 09:27 AM ---------- Previous post was at 09:23 AM ----------

Btw why are the developer options gone in 10.1? Linda hugs me since there's more lag time between hitting the home button and getting there. Too much animation for my liking as to where in cm10.0 we could change the how fast it was.
[Verizon Samsung Galaxy S III] ctheory83:
It looks like NFC and tethering are broken.
[Verizon Samsung Galaxy S III] Restola:
Google changed it in 4.2. To get developer options to show go to Menu > Settings > About Phone. Scroll to the bottom and click on Build Number 7 times (i think). Then Developer Options will be back in Menu > Settings
[Verizon Samsung Galaxy S III] will.bates94:
Correct.

---------- Post added at 09:34 AM ---------- Previous post was at 09:32 AM ----------

Thank you good sir!
[Verizon Samsung Galaxy S III] ctheory83:
Thanks for confirming! Love everything so far, just picked a bad day to flash - I really need to tether right now (whoops)!
[Verizon Samsung Galaxy S III] cybertec69:
I am having issues with the pictures taken with the camera, they show up in my camera folder, but when I connect the phone to the computer the folder is nowhere to be found, every other folder is visible but the folder that the pictures are in, I can see them on the phone, weird.
[Verizon Samsung Galaxy S III] s'pht:
That being the case; why does it work great on the April 8 and before builds?
[Verizon Samsung Galaxy S III] detule:
Thanks, for pointing this out - I too use MortPlayer and was wondering if it was my setup that was acting up.

It's a piece of code that snuck in from CodeAurora on April 8. Hopefully it'll get sorted out soon.
[Verizon Samsung Galaxy S III] s'pht:
You don't happen to have any specifics on the commit? We can usually get the unofficial to revert stuff like that until the officials get it cleaned up.
[Verizon Samsung Galaxy S III] detule:
http://review.cyanogenmod.org/#/c/36007/
[Verizon Samsung Galaxy S III] s'pht:
Mastamoon sez he'll add that to his next unofficial

http://xdaforums.com/showpost.php?p=40445079&postcount=2382
[Verizon Samsung Galaxy S III] titanshadow:
Hey everyone, I'm a little new to this area for this phone. I've been running CM 10.1 for a while and, I'd like some help with something. I also have a Galaxy Tab 2 and over in that area they are having an issue with the P3100 and the voice dialer receiving bluetooth audio. I remember my GS3 having that same issue back in march and that one of the nightlies soon after M2 fixed it, though I can't seem to find the code review section where it was fixed.

I've searched on bbqlog and on the code review site, but still can't find it. I was hoping that sending that to the devs over there for the P3100 (since it is still running the older kernel, as was the GS3 when the problem happened there) might be able to make use of it.

Thanks in advance.
[Verizon Samsung Galaxy S III] timedroid:
I've gotten a few random reboot while not using the phone today. Running 10.1 M3.

I seem to be getting worse battery life as well.
[Verizon Samsung Galaxy S III] invisiblek:
There are 3 ways I can think of to interpret a post like this.

1. Empathetic: We are having the same problem, damn... (doesn't seem to be the case)

2. Sympathetic: That sux dude, sorry **** doesn't work for you... (although we all feel this way, see #3)

3. Dev-athetic: Please post a log (logcat, kmsg) when you have issues so that we may attempt to investigate said problems and hopefully find a fix.

I side on #3 :silly:
[Verizon Samsung Galaxy S III] dougie1792:
Is there anyway you could find out how to get photosphere on the tmo gs3

Thanks
[Verizon Samsung Galaxy S III] timedroid:
It's attached to https://jira.cyanogenmod.org/browse/CYAN-881

I don't see a panic message at the end though. Should those be logged?

---------- Post added 20th April 2013 at 12:10 AM ---------- Previous post was 19th April 2013 at 11:35 PM ----------

https://github.com/CyanogenMod/andr...mmit/4efe05baf6716f435342ffa58f5cbba28f24be68

That along with the gpiomux install error seems a bit suspicious. Seems a bit early to account for the reboot issues, though?
[Verizon Samsung Galaxy S III] invisiblek:
I don't think its related to the gpiomux, that's not our file (board-m2_vzw-gpiomux.c) and we don't have gpiomux_setting gsbi9_active_cfg

Try today's nightly, (4/20)

Cyanogen pushed some stuff yesterday, which at the very least will get us more logspam =)
[Verizon Samsung Galaxy S III] Defragger51:
I just checked and today's nightly is not available unless you have an inside connection or your not talking about the official CM build. I have been running 118 hours on 4/14 nightly with out a problem , gps seems a little slower than 3/17, specially while in the house, but other than that Not one problem. waiting to give the next one a try, when they finish it.
[Verizon Samsung Galaxy S III] RedRumy3:
So far so good with 4/20 official nightly. Haven't had any problems with 3.4 kernel and my phone though. Really love this rom ^_^
[Verizon Samsung Galaxy S III] dspcap:
My screen is flickering pretty consistently with the 4/20 build..
[Verizon Samsung Galaxy S III] RedRumy3:
Weird, don't have that issue at all. You don't have force gpu rendering checked do you?
[Verizon Samsung Galaxy S III] dspcap:
I just checked and it's not. I also just went back to 4/17 nightlie and the problem is gone. Maybe I will try re-downloading it again later.
[Verizon Samsung Galaxy S III] :
I'm having pretty bad screen flicker as well.
[Verizon Samsung Galaxy S III] dspcap:
Makes me feel better knowing it's not just me.
[Verizon Samsung Galaxy S III] RedRumy3:
Hmm weird are you guys on stock kernel too?
[Verizon Samsung Galaxy S III] dspcap:
Yes
[Verizon Samsung Galaxy S III] AdMire:
I flashed this on the stock kernel and everything seemed fine for probably an hour or so. Then I went to the Chase app and got the screen flicker as well.

edit: stock kernel too. i tried to flash LK but phone didn't boot.
[Verizon Samsung Galaxy S III] :
Yes using stock.
[Verizon Samsung Galaxy S III] phillysdon04:
I had the screen flickering issue also but after checking "Disable HW overlays" I no longer have that issue.
[Verizon Samsung Galaxy S III] airmaxx23:
I'm not having any screen flicker on the 4/20 build with the latest KT747 kernel.
[Verizon Samsung Galaxy S III] AdMire:
Does this come with a kernel? Because I tried to flash Lean Kernel and my phone wouldn't boot. Had to get boot into recovery and reflash the ROM. This is my first go with CM so I apologize if that was covered.
[Verizon Samsung Galaxy S III] luis86dr:
Every ROM you'll ever flash will come packed with a kernel. Without a kernel, the ROM will not boot. I would check to see if LK has been updated for the latest Cm builds.
[Verizon Samsung Galaxy S III] AdMire:
I did know that, I just meant compatibility wise. I'll check, Thank you.

---------- Post added at 09:39 PM ---------- Previous post was at 09:03 PM ----------

When I try to use Pandora, I get this error message. Never had it on other ROM's.

Anyone else have this issue?

Also when it did work a earlier build, when I would try and add a new station, it wouldn't let me. It would try to bring up the keyboard but it wouldn't.
[Verizon Samsung Galaxy S III] dspcap:
what is hw overlays?
[Verizon Samsung Galaxy S III] mademan420:
Its a setting under development in settings. I have seen this option work on other 10.1 ROMs as well. Not sure why though:confused::confused::confused:
[Verizon Samsung Galaxy S III] dspcap:
Found this..

http://rootzwiki.com/topic/28977-disable-hardware-overlays/
[Verizon Samsung Galaxy S III] mademan420:
Thanks Bro! Just what the doctor ordered:good::good::good:
[Verizon Samsung Galaxy S III] Defragger51:
I find it amazing that yesterday i saw No 4/18 or 4/20 builds listed but somehow others did and today I see two 4/18 builds and a 4/20 build. Well after 141 hours on 4/14 with only slow gps as an issue I am giving 4/20 a try..
[Verizon Samsung Galaxy S III] odub303:
If you look on get.cm, you will always see builds if they are available.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] soohyunk83:
radio recommendation?

Is there a particular radio and rpm that were recommended to use with the newer daily builds?
[Verizon Samsung Galaxy S III] luis86dr:
I would say experiment with each radio and see what works for you. It's difficult to recommend such things as results vary differently for every user.
[Verizon Samsung Galaxy S III] titanshadow:
I use the latest ones from Verizon and that works well for me.
[Verizon Samsung Galaxy S III] dspcap:
Which one is that? I am on K3 and pretty happy. I have just come to the realization that 4.2.2 roms don't give me the best data signals.
[Verizon Samsung Galaxy S III] havoknight:
RUIM/SIM to NV

Does the problem with switching to NV from RUIM/SIM because of reboot still occur?
[Verizon Samsung Galaxy S III] titanshadow:
The site used had them sorted by date, descending so the first one kissed was the latest, I don't remember the file name though, sorry.
[Verizon Samsung Galaxy S III] soohyunk83:
Found the link with the modems sorted.

Thought I'd share.

http://rootzwiki.com/topic/34053-modems-vrbmb1-verizon-sgs3-sch-i535-recovery-flashable/
[Verizon Samsung Galaxy S III] henrys01:
04/22 nightly still randomly reboots. My phone just rebooted while sitting idle with the screen off. It's been a month now and there still isn't a stable release! :(
[Verizon Samsung Galaxy S III] odub303:
This post is useless without a log. Also, feel free to fix it yourself instead of whining.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] airmaxx23:
Have you tried a different kernel? I haven't had any reboots at all.
[Verizon Samsung Galaxy S III] henrys01:
Simmer down boss. It's hard to get a log with random reboot. I'm not new to the CM game. I'm simply notifying anyone wanting to upgrade that its still fubared. I'm happily back on the old kernel now.

No I have not... just the CM kernel...
[Verizon Samsung Galaxy S III] stkiswr:
The 4/20 build is running great for me. P issues :)
[Verizon Samsung Galaxy S III] Argent36:
I notice my BT cycles on and off on 4-22 because my Pebble watch stops getting notifications and my computer locks itself automatically when it stops seeing the phone.

I know...no logs....and if I figure that out I'll try and post one - but its not a problem I can replicate on command...just something I've noticed
[Verizon Samsung Galaxy S III] d1ez3:
try slim rom build 4, it's completely stable for me
[Verizon Samsung Galaxy S III] dspcap:
Flashed 4/22 nightlie and still getting the screen flickering. Anyone know what's causing that?
[Verizon Samsung Galaxy S III] stkiswr:
Disable hw overlay in development settings
[Verizon Samsung Galaxy S III] dspcap:
I read that earlier, but should we have to do that or is this a bug?
[Verizon Samsung Galaxy S III] stkiswr:
I'm not 100% sure if you could call it a bug. Its def not able to decide whether to use GPU or CPU. I read a build prop mod that can be done to permanently force GPU and it fixes the issue BUT on a nightly you just check the box every reboot. I can try to find the lines to modify in your build prop if you'd like and I can agree maybe it should be done as a permanent mod before we download it, but as I nightly I will just remember to check the box after reboot :)
[Verizon Samsung Galaxy S III] Stupifier:
I believe it would be considered a bug...and disabling hw overlay is only a bandaid. It was an issue in early CM 10.1 days and people were temporarily fixing it by disabling hw overlay back then too. After some time, dev's fixed it and the bandaid (disable hw overlay) was no longer necessary

It appears the same issue has risen again and will likely go through the same treatment. Just disable hw overlay until dev's address it.
[Verizon Samsung Galaxy S III] stkiswr:
Any way to fix the MMS send size.my pics def aren't sending at the Verizon 1.2mb limit.

If anyone has a tutorial on modding the apk I'm willing to do that. I like the stock MMS.
[Verizon Samsung Galaxy S III] razorloves:
i think we may have finally found a fix for the activation bug.

changing "persist.radio.no_wait_for_card=1" in the build.prop to 0 tells the radio to wait till the simcard is ready.

invisiblek has already merged it so it will be in the next nightly.

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

fingers crossed.
[Verizon Samsung Galaxy S III] Zacharybinx34:
Screen flickering here. Really don't want to have to change that setting every reboot
[Verizon Samsung Galaxy S III] soohyunk83:
Is reboot still an issue with the latest build?

Looks like we have a workaround for the screen flickers, but i didn't see any updates on random reboots.

(This is with using stock CM kernel.)
[Verizon Samsung Galaxy S III] mastamoon:
Has anybody data wiped and flashed a build with this fix included and had no activation issue?
[Verizon Samsung Galaxy S III] sivarticus85:
I'm trying it now. Stand by.

Edit: I think we may have a winner folks. 5 reboots and no activation screen. However I am running Masta's 4-20 build, but I would assume this would make no difference.
[Verizon Samsung Galaxy S III] mastamoon:
4/20 wouldn't have the fix unless you took the build prop out of the fixed builds and put it in 4/20 before flashing?
[Verizon Samsung Galaxy S III] sivarticus85:
Yeah I made the edits to the prop and wiped caches.
[Verizon Samsung Galaxy S III] cadams122593:
I've fully wiped to build 4/22 and no activation issue after 4 reboots! Winner winner chicken dinner. lol
[Verizon Samsung Galaxy S III] razorloves:
Aside from myself, no one, until cadams replied below.

thanks for confirming cadams.

EDIT: Scratch that. cadams, 4-22 doesn't have the activation fix. lol.
[Verizon Samsung Galaxy S III] cadams122593:
well i havent been getting it anymore? oh i dirty flashed 4/23 tho.. so maybe thats the reason?
[Verizon Samsung Galaxy S III] prototype7:
Just noticed I haven't been getting activation issues either, running Slim 4.2 with an updated build.prop. Good to know that's finally fixed, my phone number shows up fine after rebooting.
[Verizon Samsung Galaxy S III] Kev13Dd:
I've been getting random reboots anytime I'm using built in wireless AP (tethering) on the last week or so of nightlies

last_kmsg of two reboots attached

K