yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] alquimista:
Here's the best way I can explain this phenomenon on CM10 as well as other custom roms. They all have have different absolute file paths for the internal and external sdcard. Macs are super picky about using absolute paths vs relative paths. And they certainly don't follow symlinks very well.

I don't really like the crappie Android File Transfer app for mac. It runs a daemon in the background all the time. It's slow and kills off file transfers mid file whenever it feels like it.

Use QtADB (don't have a link cause I'm mobile right now) I posted some fairly easy to follow instructions with links to all the downloads (I wanna say somewhere in the official PA rom thread).

Once you get QtADB up and running you will never look back. It's cross platform so there are versions for windows Linux and mac.

Hth

Ta,

ALQI
[Verizon Samsung Galaxy S III] Zacharybinx34:
Mine does this too.
[Verizon Samsung Galaxy S III] juancaperez2000:
Same her
[Verizon Samsung Galaxy S III] NegativeOne:
On 10/19?
[Verizon Samsung Galaxy S III] Jaegermeiste:
I'm still seeing this on 10/18 (the newest one). Clearing data didn't help.
[Verizon Samsung Galaxy S III] JohnnyTToxic:
Same here. For those who don't see it or want to check, when the on screen menu appears for volume the artifacts are visible. Likewise, when rotating the device orientation from profile to landscape and vice versa it will appear.

Similarly, I am seeing the same behavior with Moboplayer, but I do not see any issues when using the baked in video player app, nor with the built in video player plugin under the baked in browser and under chrome (not sure if they use the same plugin)
[Verizon Samsung Galaxy S III] littleneutrino:
Full wipe and the Youtube / any video player, UI Glitch still present, it is not really that big of a deal for me as the glitch only happens for a few seconds..
[Verizon Samsung Galaxy S III] fix-this!:
wheres the changelog for the nightlies? im still on the m2 and am debating if i should flash something newer or not. is anybody going to stick to the monthly snapshot builds?
[Verizon Samsung Galaxy S III] msid:
I'm sticking with the M builds, M2 seems stable for me - and battery life is very good.

Nightly change log:

http://cm10log.appspot.com/?device=d2vzw
[Verizon Samsung Galaxy S III] fix-this!:
yeah i agree the m2 build is fantastic.
[Verizon Samsung Galaxy S III] RichTJ99:
I have been lurking & trying to figure out what M2 means?

Where is the download for it?
[Verizon Samsung Galaxy S III] fix-this!:
i assume it's a monthly milestone build. if you go to the first post in this thread there is a link to the downloads. the build is m2 experimental.
[Verizon Samsung Galaxy S III] That Baker Guy:
ill look into that. thanks.
[Verizon Samsung Galaxy S III] chmodbot:
Thread for Monthlies....

Is it possible to have a sub thread or another one just for the M Builds of CM10 or is it all supposed to be bunched into this one?
[Verizon Samsung Galaxy S III] sparkerjc:
I'd like that as well. Someone tried to start a new thread for any build after M2, but that got locked. I do think a monthly only thread would be nice though.
[Verizon Samsung Galaxy S III] Seirÿu:
the monthlies are milestones for nightlies, if I understand correctly anyway, the nightlies after the M series are basically M + nightly merges. So separating them out doesn't make much sense to me at least... perhaps sell me on following a separate thread for essentially the same information?
[Verizon Samsung Galaxy S III] denaliano:
Friend sent me to the EuroSkank site, noticed this about that build-

I'm about to try it.

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

and.... it worked. No more video artifacts.

I can't post the link to the site, but google EuroSkank CM10
[Verizon Samsung Galaxy S III] jdhas:
Here's the direct link for those who need it: http://fitsnugly.euroskank.com/?rom=cm10&device=d2vzw
[Verizon Samsung Galaxy S III] littleneutrino:
too bad they are not adding a toggle for USB Audio, been in the kernel for a few updates now and still no method to turn it on. :(
[Verizon Samsung Galaxy S III] d1ez3:
Can anyone tell me if LPA has been added into CM10 yet? This was the only real issue I've had in the past, listening to music or podcasts at work without LPA drains the battery significantly faster.

thanks
[Verizon Samsung Galaxy S III] revolt1:
It says to avoid copybit how do you avoid it

It doesn't make sense
[Verizon Samsung Galaxy S III] sparkerjc:
Well, you wouldn't have to follow the monthly thread. People running the M builds don't flash every day so that thread would be much easier to follow and for M users to provide support for eachother. The nightly thread is mostly "build failed tonight" and "10-17 melted my phone into a pile of goo!" which is more painful for M users to wade through. Just my .02, the the thread title is "Nightlies" not "Monthlies".
[Verizon Samsung Galaxy S III] natethegreat86:
Not sure whats causing the glitches for people with youtube/video players, I'm on 10-17 and everything is working absolutely fantastic for me haven't had any glitches at all as of yet. I did a clean install, however migrated apps with titanium from a quite older build of paranoid android figured it was time to update things a bit.
[Verizon Samsung Galaxy S III] Imatoasta:
They had a commit that I THINK turned it on but I'm 99% sure that was the reason for the mediaserver wakelocks and they removed it because of that?
[Verizon Samsung Galaxy S III] ugachris:
That is correct, LPA isn't currently included in the nightlies because it caused battery and bluetooth issues.
[Verizon Samsung Galaxy S III] sincerity:
Running m2 with 1011 gapps and the gallery picasa sync and camera freezes after taking a picture. Then won't connect to camera until reboot. Any ideas?
[Verizon Samsung Galaxy S III] ercDROID:
10/18 is running like crap for me on a clean install. Stock kernel and Imoseyon 1.5, 1.5.1 exp, and 1.5.2 exp are all staying mostly in 810 mhz with very little deep sleep. Phone is warm. Is 10/18 a bad build or did I possibly get a bad download?
[Verizon Samsung Galaxy S III] Trumps:
I am having problems with the camera. Additionally the screen corrupts using Pro Capture, making me wonder if it's related to the copybit video issue. Are there too many developer hands in the cookie jar right now?
[Verizon Samsung Galaxy S III] cjohnsonthe2nd:
usb audio

where do you see it was added to the kernel. have you tried the 3rd party app galaxy sound redirector?
[Verizon Samsung Galaxy S III] PerCompLLC:
How long did you try it? I was seeing the same behavior but it settled down after the media scanning service finished its run. Now everything is running cool and the phone is deep sleeping again.
[Verizon Samsung Galaxy S III] iofthestorm:
Huh, flashed 10/17 yesterday evening, was fine last night and then just now my phone keeps rebooting if I touch it or do anything. Here's a /proc/last_kmsg if anyone can interpret anything out of it. Clearly the kernel is restarting but I can't tell why.
[Verizon Samsung Galaxy S III] thewebsiteisdown:
I'm running good on the new HE modem, the 10/18 build and the newest gapps.
[Verizon Samsung Galaxy S III] ugachris:
You're running a nightly. If you don't like it, find another ROM. No reason to criticize the CM team.
[Verizon Samsung Galaxy S III] iofthestorm:
Hmm, crap, I just got a random reboot in TWRP when trying to flash 10/18. So now I'm guessing that it's a hardware defect, blehhh, most likely related to me dropping it in water like 2 months ago. Surprised it worked for so long. I guess unless anyone else experienced reboots it's probably just me and my butterfingers dropped phone being retarded.
[Verizon Samsung Galaxy S III] fix-this!:
Im having all kinds of battery drain on the new radios and leankernel. Might try an older radio and a different kernel.
[Verizon Samsung Galaxy S III] fix-this!:
Has anybody ever complained to you that you have an echo when you talk? My dad just told me tonight i do. He said it wasnt like that before. Im wondering if its the new radio or a bug in cm10? I ran beans before this.
[Verizon Samsung Galaxy S III] dobo84:
Really don't see any sense in breaking down every little bug these nightlies have in a thread, that is what the statistics is for. CM is pretty thorough and rarely puts out a bad build. I can live with the minor things. I'm just glad to be leaps and bounds ahead of Verizon :cool:
[Verizon Samsung Galaxy S III] ew0kfarmer:
Is there any way to port the cyanogen notification toggles to a touchwiz rom? I couldn't imagine going back to touchwiz without them =(

Sent from my SCH-I535 using Xparent SkyBlue Tapatalk 2
[Verizon Samsung Galaxy S III] josh995:
Ok so I ran cm10 for a few days, like a week really, and was getting horrible battery life. It wouldn't last me through the day. I Odin back to stock and still am on stock, and and I'm going on 25 hours with 30 percent to go. I didn't use my phone any differently, at all. Can anyone tell me what could cause such a drastic difference?
[Verizon Samsung Galaxy S III] dobo84:
Might just be jelly bean it self , I noticed it seems to tear through the battery quickly. I also notice if I only flash a nightly once a week and let things settle I usually do well on battery
[Verizon Samsung Galaxy S III] XooLoo:
Same on both for me....... really frustrated with the latest nightlies.
[Verizon Samsung Galaxy S III] Imatoasta:
I ported as much as allowed over lidroids toggles awhile ago. I think this is the closest you can get unless somebody updated quicksettings with more toggles.

http://xdaforums.com/showthread.php?t=1864466
[Verizon Samsung Galaxy S III] hopesrequiem:
Sorry a little late. M2
[Verizon Samsung Galaxy S III] Trumps:
I bet you're one of the people who rates every single nightly 5 stars in Rom Manager instead of giving each nightly an honest rating based on its performance so that everybody knows which builds to avoid.

edit: All I am saying is I'm getting tired of the regressions that seriously impact the usability of the device. There were several builds in September that ran GREAT, and then a slough of bugs appeared with no substantial new features.
[Verizon Samsung Galaxy S III] TechSavvy2:
Battery sucks because they updated the kernel.....twice.....and haven't smoothed it out yet. Been that way for a week or so if I remember right.

Some peoples problems here also sound like they could be related to running the wrong gapps package with the wrong nightly/m build. Everything (if I remember right) after the m2 build is all 4.1.2 based which is specifically what the new 1011 gapps package is built for. You're gonna get wonky stuff if you run the wrong combo.....
[Verizon Samsung Galaxy S III] mustbepbs:
Gapps makes sense for new flashers, but if people have been dirty flashing they shouldn't need to since the gapps have been updating via the play store to the versions that are in the latest gapps zip.
[Verizon Samsung Galaxy S III] Zacharybinx34:
did 11-19 fail?

I don't see it.
[Verizon Samsung Galaxy S III] littleneutrino:
Tried running Dock Sound redirect and it says it is on however, it does not redirect the sound to the dock sadly. I really wish this feature would work. I keep my phone in a dock while i am at my desk at work However, having to unplug the headphone jack when i walk away gets annoying.
[Verizon Samsung Galaxy S III] jdommer:
I admit I have no idea why this would work, but it worked for me so I'll offer.

My GPS got weird after I flashed M2 over M1. It took long time to lock, then one night, it reported 0 satellites in use, but an accuracy of 30 feet (and would still navigate). Rebooted phone and it refused to lock at all afterwards however long I waited.

Cleared data on Google maps and it has locked instantly ever since. YMMV.
[Verizon Samsung Galaxy S III] Durthquake:
I'm on 10/17 nightly with the HE (newest) radio. I am getting fantastic battery. Probably around the best I have gotten on CM10. I always wipe dalvik, install nightly, wipe dalvik again and fix permissions. I also don't mess with changing the kernel, CM10 is built specifically around the kernel they provide, it also helps reduce people blaming the CM team for something that might not be there fault (aka the aftermarket kernel) :eek:

I also dont flash every nightly, I wait for an update that either fix's something that is not working properly, been a while, or has a large # of updates/features.
[Verizon Samsung Galaxy S III] ugachris:
Sorry, I don't use ROM Manager to download CM. But here's what I'm saying: this is a free community-driven project, and you are running their pre-alpha builds. There will be problems and regressions, that's why it's a nightly. I don't know why it is, but there is this entitlement attitude, where damnit, [x] feature should work on my phone today and should be completely stable. These are folks like you and me, making an AOSP-based ROM for quite a few phones (go to get.cm and count) without thanks or pay and in their spare time.

If you want something semi-stable, run the M2 experimental. If that doesn't meet your needs, go back to an ICS-based ROM until they work the kinks out. Or jump in and write a patch. Til then, wait patiently until they fix it and then thank them profusely for the service they provide to the community.
[Verizon Samsung Galaxy S III] Brian Gove:
Which nightly are you on? I had horrible drain with 10/12 and 10/14 with both stock and the leankernel. 10/17 seemed to have fixed whatever the issue was tho. I'm now losing about 1-2% an hour which is roughly what was normal for me and I'm running lk 1.5 with 10/17.
[Verizon Samsung Galaxy S III] Jay Evans:
Yep, http://jenkins.cyanogenmod.com/job/android/10447/

Something specific to the VZW build because att, tmo and spr builds were good

Doesn't look like much a change really?

===================================

Since Thu Oct 18 06:12:37 UTC 2012

===================================

* system/core

943dba1 init.rc: Fix compcache and cleanup init file

* vendor/cm

8f412cb cm: init.rc: Fix compcache and cleanup init file

* vendor/sony

e7fd716 hayabusa: initial blob import
[Verizon Samsung Galaxy S III] fix-this!:
m2 build. im back on beans for now, maybe ill try 10/17 later today. the battery drain was crazy for me.
[Verizon Samsung Galaxy S III] Brian Gove:
Yeah, not sure about m2 but I had to revert back to 10/10 until 10/17 came out just to be able to make it thru the day. I'd lose thirty percent overnight even tho my phone went into deep sleep and had no significant wake locks.

Now I'm at 17 hours and 15 minutes with over an hour and a half screen time and I got 45% charge left.
[Verizon Samsung Galaxy S III] hopesrequiem:
M2 is 4.1.2 as well
[Verizon Samsung Galaxy S III] mastamoon:
Here is my 20121019 unofficial nightly..

https://dl.dropbox.com/u/13144052/CM10/cm-10-20121019-UNOFFICIAL-d2vzw.zip

Merged a commit to fix the graphical issues I was having and I would guess others were too.

Has the S3 test 2 gps tweaks built in, along with the 'possibly required' build.prop edit.

Will default you to my favorite ringtone, so you will need to switch back to yours.

Has a TCP tweak commit ... MMS picture border commit...

Some other stuff, but 99% stock CM10. I build this to my liking.. just sharing with ya'll
[Verizon Samsung Galaxy S III] AlexDeGruven:
You can't really judge on regressions this early in the development process. These are still experimental builds, and regressions can and will happen, quite regularly.

Once we hit Alpha stage, regressions should slow WAY down (in fact, that's one of the requirements for declaring Alpha).

Once we hit Beta stage, regressions should be all but eliminated.

So, to clarify - I disagree with you. :)
[Verizon Samsung Galaxy S III] Div033:
So I'm a bit confused about the nature of the remaining issues. These include:

- Call Volume

- Incorrect Noise Reduction Mic Usage (results in echo on speaker phone)

- Occasional Data Drops

The data drops I more so understand as they're RIL related and that's basically been hacked. Are they just REALLY hard to fix? Or are they currently not fixable due to missing JB source code for our device?

Sorry if I come off as entitled, that is not my intention. It does get frustrating to have bugs on stock TW and AOSP; there's no perfect ROM like CM7 was on my droid incredible. I'll keep rooting for the talented CM devs to get things running smoothly.
[Verizon Samsung Galaxy S III] Raegx:
Not having a problem. Audio goes up and down properly. After a flash just turn the sounds all the way up and all the way down then set it at whatever level you want.

Haven't had this problem in a long time (weeks). I talk on my phone while driving using speaker phone.

Depends on your area. In my area (New York) the hand off from 4g -> 3g is a little slow sometimes but works after a few seconds. If I am in a 4g area, I get full 4g speeds. If I am in a 3g area I get 3g speeds. I only see an issue when in a fringe 4g area swapping between a 4g and 3g over and over when I move around.
[Verizon Samsung Galaxy S III] Brian Gove:
I just ran into an odd bug on the 10/17 build. Has anyone, while running that build or any other, ran into a bug where your phone doesn't lock? Even when you hit the power button to turn the screen off/lock the phone it still won't lock? I had to reboot my phone in order for it to start locking my phone. The screen would go off, but when I turned it back on there was no slider, just whatever I had on my screen before I turned it off.
[Verizon Samsung Galaxy S III] qqhorus:
On M2 having a weird issue with wifi tether not working...clean flashed too.
[Verizon Samsung Galaxy S III] Zalithian:
Use supersu instead of superuser.
[Verizon Samsung Galaxy S III] qqhorus:
Thank you sir.
[Verizon Samsung Galaxy S III] Restola:
My call volume got 'stuck' a few flashes ago after working normal for weeks. Echo on Skype is awful, but on calls mine is fine. Haven't had data drop issues yet.

VZW Galaxy S3 via Tapatalk
[Verizon Samsung Galaxy S III] Zalithian:
Glad to help. :)
[Verizon Samsung Galaxy S III] fix-this!:
tried the 10/18 nightly and wifi is hosed. back to wps failed or not in range. none of the tricks that worked for me with m2 is working now. i did a search and many people are having this on cm10.

link to other xda threads on this bug: https://www.google.com/search?q=no+wifi+cm10&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:en-US:official&client=firefox-a#hl=en&client=firefox-a&hs=ItM&rls=org.mozilla:en-US:official&q=+site:xdaforums.com+no+wifi+cm10&sa=X&ei=PdyBUPDuD4qVyQHa-YGoCg&ved=0CCgQrQIwAA&bav=on.2,or.r_gc.r_pw.r_qf.&fp=92da361fb107ce2f&bpcl=35466521&biw=1664&bih=856

Has this been addressed at all?

EDIT: also mentioned here on the cm forums: http://forum.cyanogenmod.com/topic/59985-wifi-problems-in-switzerland-starting-with-20120927-cm10-nightly/
[Verizon Samsung Galaxy S III] alee:
This has all the recent merges for d2vzw, 10/19 build:

http://goo.im/devs/invisiblek/i535/roms/cm10.unofficial.nightlies

Working fine for me.
[Verizon Samsung Galaxy S III] fix-this!:
Wheres the changelog and who do i report bugs to? Id like this wifi thing fixed if possible. Work around maybe?
[Verizon Samsung Galaxy S III] beaups:
So fix it.
[Verizon Samsung Galaxy S III] fix-this!:
Whats wrong with me wanting to report a bug? Just becuase it doesnt effect you doesnt mean others arent having issues. Most people rely on wifi since unlimited data is few and far between. Trust me if i could fix it i would.
[Verizon Samsung Galaxy S III] PerCompLLC:
Haven't had any issues whatsoever with wifi (wpa at home). Running 10/18 nightly.
[Verizon Samsung Galaxy S III] fix-this!:
yeah the weird thing is this seems sporadic, not everyone has it and there is no mentioned fix. i just wish i could get it acknowledged somehow. ive tried just about everything, i hate going back to ics.
[Verizon Samsung Galaxy S III] Imatoasta:
Just go back to the build you were on previously. Is it really that hard to restore a backup or do you HAVE to be on the latest nightly?
[Verizon Samsung Galaxy S III] manywelps:
unofficial bug tracker is here: http://code.google.com/p/d2vzw-cm10-bugs/issues/list
[Verizon Samsung Galaxy S III] goldsmitht:
wifi hotspot? or wifi in general? IF it is your wifi, try making sure the United States is clicked in regions:

menu > system settings >wifi >menu >advanced >wifi region code and select US

also, if you are having problems at your home, shut off your router, let it reset, turn off your wifi on phone, then after about a minute or so, turn on router and then turn on your phone wifi. be surprised how that will fix some problems
[Verizon Samsung Galaxy S III] fix-this!:
Wifi in general. Tried all that man but thanks. Its also happening on aokp. Went back to ics and its working again. I reported this on the cm forums. Must be a driver bug with certain routers. Gonna give eclipse a try tomorrow.
[Verizon Samsung Galaxy S III] Zacharybinx34:
Don't be a tool
[Verizon Samsung Galaxy S III] The Archangel:
Problems going on?
[Verizon Samsung Galaxy S III] Brian Gove:
Nah, just the natives getting restless... Some think they're the Archangel of CM ;) hehe
[Verizon Samsung Galaxy S III] The Archangel:
Ha!

Keep dreaming guys ;)
[Verizon Samsung Galaxy S III] TechSavvy2:
I thought things got weird in here once in a while, then read the threads for cm10 in all the d2 devices to check for common bugs........some people are really fuggin crazy out there. Way worse than here. I'm not jealous of your job at all and appreciate the work, lol.
[Verizon Samsung Galaxy S III] Trumps:
Perhaps I'm used to the good old days of CM6/7 where a stable build didn't take 4 months. My bad. The one thing I remember about 6, 7, and 9 is that the builds seemed centered around the quality of the builds, not the frequency or the amount of commits.

I love when people suggest "writing patches"... I'd say the best way to contribute to the project is for developers to not commit code that breaks fundamental parts of the phone. How about that? Commit it after you spend more than 30 seconds playing with it. Because that's what my complaint is. I don't feel "entitled" to ANYTHING, I just have the expectation that code won't be committed if it seriously impacts functionality that used to be working.
[Verizon Samsung Galaxy S III] Nnyan:
How exactly do you know how much time any given DEV works in a commit? Do you know how hard regression testing is when you have a team of paid coders doing this full time let alone just one or more devs unpaid part time?

Let me clue you in, part of the deal is that these are community projects. YOUR contribution is to use it on your device and report issues including commits that break some things. Users of ROMS understand the beta nature of this type of work and thier role in the process.

Expecting to much? IMHO yes.
[Verizon Samsung Galaxy S III] The Archangel:
Got a problem with someone. Take it to private messages
[Verizon Samsung Galaxy S III] revolt1:
What's SMS tester on latest version
[Verizon Samsung Galaxy S III] toddley:
Not trying to call you out, I'm just telling you that as a java software engineer the things these "amateurs" are working with are extremely difficult and just saying "don't break things that are already working" is misinformed. The things going on with the CM nightlies are completely normal you're just getting insight to a process you would never ever see from Samsung or Verizon because they wouldn't make them public. Rest assured it's a normal development cycle. Give it time the CM guys are great.

On topic: they're definitely still working out kernel issues battery life is atrocious on the latest nightlies, anyone reading this deciding whether or not to flash I would wait a few days or just go with the M2 which is way more of a DD
[Verizon Samsung Galaxy S III] iofthestorm:
The problem is that there's a lot of stuff going on for a lot of different phones which can affect our phone. It's not like every developer for CM has every phone, it's most likely that the stuff that breaks was intended to fix something on another phone. I don't think there are really many devs who actually work on d2vzw specifically.