yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] sanjsrik:
Thanks. Quick question. Did you dirty flash over the previous nightly? I used the built-in updater and am running TWRP as recovery. Could that be the issue?

Any ideas would be most appreciated.
[Verizon Samsung Galaxy S III] jfhanny:
This is going to sound very noob of me and I apologize but I need to know.... Where did the customization go? Am I missing something? All I have installed is the snapshot! Guessing that I am missing something.
[Verizon Samsung Galaxy S III] sanjsrik:
It's not a noob question. And, no question is stupid. However, could you explain a little more what you mean by customization?
[Verizon Samsung Galaxy S III] jfhanny:
Thank you for the quick reply! I just mean on old CMs (havent been here in about a year and so much has changed) I could customize everything from the homescreen to what battery and clock I wanted or to use the on screen home buttons! Hope that helps lol
[Verizon Samsung Galaxy S III] sanjsrik:
Okay, you need to go into settings. It's not all from the main screen any more.
[Verizon Samsung Galaxy S III] Restola:
Try re-download, wipe cache and dalvik, and flash over your current install.
[Verizon Samsung Galaxy S III] Jackdog89:
I'm getting a delay on incoming calls. When ever I get an incoming call and answer there's like a 2 second delay before the other person can hear me. Is anyone else experiencing this on the M1 release? Outgoing calls are fine.
[Verizon Samsung Galaxy S III] titanshadow:
I'm still getting random reboots. Anyone else experiencing that still? I'm on the 11/05 build right now. I can't catch a reboot happening until its already underway and I need to enter my password for decryption.
[Verizon Samsung Galaxy S III] nick7893:
Any way to increase mms size?
[Verizon Samsung Galaxy S III] mastamoon:
https://www.dropbox.com/s/y10c5gbj2zc4h3z/Mms.apk

Use this mms.apk, it's the one I have in my unofficial cm10.2 rom and has the best quality you will see.

Put in /system/app
[Verizon Samsung Galaxy S III] AdMire:
Can someone tell me what the Audio FX Settings (app/icon) is for?
[Verizon Samsung Galaxy S III] ummduh:
I had been. I ended up redownloading MF1 baseband, and M1, from my phone over wifi, to the INTERNAL storage instead of extSD.

Then I reflashed both. Cleared cache and dalvik and rebooted, it crashed on first boot and worked on the second. So i went back and reflashed only the M1, and cleared cache and dalvik again. It's been great since then, have only had 1 crash in 3 days.DSP manager has been force closing on me a lot now though, when it didn't before.
[Verizon Samsung Galaxy S III] funkatronic:
Some tells me it's has something to do with audio because it always crashed or rebooted while I was playing music. The fact dsp manager crashes almost clenches it
[Verizon Samsung Galaxy S III] samman82:
For those of you who have pageplus flashed phones, this is the only rom I've found that locks 3g by itself, instantly, without toggling airplane mode. I've tried 5 or 6 aosp 4.2 roms, along with 3 tw roms, and all of them have required an airplane toggle if I temporarily lost coverage. The m1 locks immediately, even when I walk out of the dungeon I call work that kills my reception. Besides that, as a rom, no fc and zero errors with any apps. Apollo sounds phenomenal, which is a big deal for me as well. Haven't tried blue tooth. Been running for 5 days. This post is only beneficial for pageplus folks. The rest of you won't understand what I'm talking about.
[Verizon Samsung Galaxy S III] moparfreak426:
Most of the latest aosp roms such as carbon is also like that with data

Sent from my SCH-I535 using Xparent Skyblue Tapatalk 2
[Verizon Samsung Galaxy S III] lou1210:
I'm still on a nightly from September and have that issue. What causes it?
[Verizon Samsung Galaxy S III] SDQB17:
I was considering using this also...dont care for what comes on this rom, question though, when installing the apk in the folder, should I remove the apk that is there now? Having never installed an apk file before, if it is not as easy as just installing it in the folder, can you direct me to a set of instructions on the proper way to do this? Thanks!
[Verizon Samsung Galaxy S III] Jackdog89:
I'm not sure, it doesn't appear that anyone else is experiencing this. I dirty flashed to mastamoon's latest unofficial ROM and for now the problem seems to have gone away. But, it may be too early to say, I've only had one call since I switched.
[Verizon Samsung Galaxy S III] mastamoon:
Easiest is to use a root explorer and just replace the app with a copy paste. You can also adb push it.
[Verizon Samsung Galaxy S III] jbjarko:
What changed on the 11/13 & 11/14 nightlies? Currently on 11/12 and the changelog states that "this is the first CyanogenMod build of this type for device d2vzw"...Any ideas?
[Verizon Samsung Galaxy S III] SDQB17:
Thank you, ...though upon pasting I get "permission denied" Anyway to remedy this? I am using ES file explorer.
[Verizon Samsung Galaxy S III] mastamoon:
You need a root capable explorer, es might have a setting to enable this, otherwise you will need to find another on the market that has this capability.
[Verizon Samsung Galaxy S III] headcheese:
I have been watching cm's gerrit and I don't think much has changed. Probably just a glitch. Haven't flashed the newest builds though.
[Verizon Samsung Galaxy S III] soohyunk83:
It seems like cyanogen installer is not compatible with my galaxy s3 Verizon. So how are we supposed to download new builds?
[Verizon Samsung Galaxy S III] titanshadow:
I second this. I'm on the road because I'm moving cross country and my phone keeps rebooting during navigation so I was going to go back to the M1 build... I couldn't get it!
[Verizon Samsung Galaxy S III] Restola:
Am I missing something? The same way you always have?

Settings / About Phone / CyanogenMod Updates

or

http://download.cyanogenmod.org/?device=d2vzw

These both work.
[Verizon Samsung Galaxy S III] Izeltokatl:
He's taking about the get.cm site, it automatically redirects traffic to the play store app now.

Sent from my S3.
[Verizon Samsung Galaxy S III] soohyunk83:
Thanks for the link!
[Verizon Samsung Galaxy S III] Restola:
If you go to get.cm is redirects you to the page in the attached picture. Click "download" to get to the old get.cm
[Verizon Samsung Galaxy S III] 996:
Just wondering. Has the MMS picture quality been fixed in CM yet? I just remember it has always been blurry.

Thanks!

---------- Post added at 11:31 AM ---------- Previous post was at 11:30 AM ----------

Just wondering. Has the MMS picture quality been fixed in CM yet? I just remember it has always been blurry.

Thanks!
[Verizon Samsung Galaxy S III] YzRacer:
2 pages back:

http://xdaforums.com/showpost.php?p=47298203&postcount=675
[Verizon Samsung Galaxy S III] soohyunk83:
Email in new build (11/17) crashes every time I try to open an email. Anybody else see this?
[Verizon Samsung Galaxy S III] jasoncallahan:
I have not updated my G SIII yet, but I am running 11/17 on my Nexus 10 - and YES the email application is crashing (not gmail).
[Verizon Samsung Galaxy S III] RedRumy3:
I did a fresh install of latest nightly email is fine for me but my camera is not working. Hmm
[Verizon Samsung Galaxy S III] 996:
Thank you very much!
[Verizon Samsung Galaxy S III] 996:
Thank you!

Just drop it in?
[Verizon Samsung Galaxy S III] levilib:
Issue with dock

I am unable to provide a logcat of this issue as will become evident.

I am running CM10.2 M1, I upgraded from 10.1.3 using recovery and flashed the new gapps package, otherwise it was a dirty flash.

Ever since then (I have since tried a later nightly) every time I remove my phone from the dock (genuine Samsung dock) my phone freezes and resets. I cannot unlock the phone, or scroll down the notification drawer. It just freezes and reboots from the cyanogenmod flash screen.

I don't know where to report this problem other than here.
[Verizon Samsung Galaxy S III] Restola:
make a backup, then wipe your phone

do a clean install

boot up

see if the issue repeats itself
[Verizon Samsung Galaxy S III] titanshadow:
So for a while now I've been suffering from random reboots. Well on my trip across the country (California to Kentucky) so far the problem has intensified... Because of this I was able to get a logcat of it happening. I didn't see anything unusual. Keep in mind that I'm using GPS in Google Maps to navigate while the logcat is going on.

https://www.dropbox.com/s/7ggqrcj4yssj7o6/logcat.reset.txt

I wondered if anyone could give me a hand deciphering it. I'm not very good at it and the log actual stops mid-statement which I find really strange. I don't see a kernel panic or anything else.

I'd also like to note that it happened a lot in areas of really poor Verizon service, I think that has something to do with it.
[Verizon Samsung Galaxy S III] rhcreed:
miracast to a ptv3000?

anyone have any luck getting this phone and rom to work with miracast?

Running latest nightly (11/17/2013), sees device, attempts to connect, appears to connect for a second (only on phone), then disconnects.

Any suggestions?
[Verizon Samsung Galaxy S III] Prack:
I had to go back to the 11/15 build due to the 11/17 email force close issue. Hopefully this is corrected soon.
[Verizon Samsung Galaxy S III] SDQB17:
I have been running M1 and it works flawless, I am having an issue though I don't even know if it's ROM related...it may just be the s3...if anyone has any advice. The call volume is just average at best when turned to max, I find my self always wanting to turn it up but it is already at max. Ringer volume is fine, music and everything else, just the call volume & speaker phone is even worse. I there a hack or app or something I can do to remedy this? Thx!
[Verizon Samsung Galaxy S III] jbjarko:
Just to let everyone know, the email issue has been fixed in the 11/21 nightly, mine works fine now.
[Verizon Samsung Galaxy S III] jdiamond7:
I haven't tried it yet on this ROM version, but I've had the same issue with all other CM roms I've tried. I've only been able to get miracast to work with touchwiz roms. Admittedly, I have not put in a lot of effort.

Maybe I'll dust off my old AllShare Cast Dongle and see what I can come up with. I'll post back if I do get the chance.
[Verizon Samsung Galaxy S III] aypeeootrek:
I would love an answer for this too. I have the same issue and I hate it.
[Verizon Samsung Galaxy S III] rockingondrums:
Just updated from an October nightly to the latest nightly. I have camera but no gallery.
[Verizon Samsung Galaxy S III] daruiner:
I'm on 10.1.3-d2vzw and have been since it was released. I've also been having this issue occasionally. I'll try to grab some logs and post them for someone to compare. I'm a novice at these things but I'd love to at least help and give someone an additional sample set to look over.

Mine are not frequent (though it seems like it has been a bit more often recently), maybe once a week at most, but there's really no rhyme or reason to when they happen. I have good coverage in my home, but today I was on the phone while driving through a spotty Verizon area and did suffer a reboot.

In addition, usually it seems like the reboot takes less time than if I had initiated it, I don't usually see the Samsung logo, just the spinning cyanogen logo. My phone usually behaves very sluggishly and apps seem to crash a lot after this, so I end up pulling my battery and then things calm down again and start acting right.
[Verizon Samsung Galaxy S III] ericsdeadinside:
The reboot issue is a killer. What has Google done to the 4.3 code gotten rid of error handling or something?
[Verizon Samsung Galaxy S III] Restola:
Virtually guaranteed its a widget or app you installed.
[Verizon Samsung Galaxy S III] titanshadow:
That is not necessarily true. During my trip, yes I had apps and widgets installed but I went from a reboot perhaps every 4 or 5 days to at times 4 reboots within 30 minutes! No change in apps. This points to something else. Unfortunately the logcat I got just stops mid entry and yields no useful information.
[Verizon Samsung Galaxy S III] ericsdeadinside:
It's a 4.3 issue
[Verizon Samsung Galaxy S III] annoyingduck:
FYI, I extracted the 4.4 aosp email from one of the kanged cm builds and an running it perfectly on the current 4.3 nightly. It's awesome, modeled after gmail. I uploaded it to dropbox if anyone wants it. Just clear data on the original email app, delete it from sytem/app, copy new email to system/app, set permissions to rw/r/r, then reboot. I love compared to the old one.

https://www.dropbox.com/s/uahjerkqmuhdcqo/Email4.4.apk
[Verizon Samsung Galaxy S III] Restola:
It's an issue for some user's special circumstances (which none of them are willing to do the simple legwork on and go back to stock cm for a day and run a logcat to catch these "4 reboots every 30 minutes").
[Verizon Samsung Galaxy S III] annoyingduck:
Yup.... And I assure anyone with reboot issues to Odin to stock Mf1, re-root/unlock, then flash away. Your reboots will magically disappear!
[Verizon Samsung Galaxy S III] Restola:
Never said to go to TW...

But anyways /shrug. Not my phone having issues.
[Verizon Samsung Galaxy S III] ericsdeadinside:
Doesn't explain at all why cm10.1 can run forever without auto rebooting
[Verizon Samsung Galaxy S III] annoyingduck:
Yes it does. All 10.2+ builds had reboot issues due to firmware partitions not upgrading. The aio mf1 package worked for most, but didn't for some. When you odin to stock mf1 all of those partitions are fully updated. Re-root/unlock/flash recovery/flash cm (or any other rom) and you'll be good to go. If not, then unfortunately it's a device specific issue that'll likely never be solved.

To summarize:

-pre 4.2=any radio/firmware.

-4.2+ requires full mf1 firmware

-some phones partitions are not fully upgraded with the aio mf1 package, some are.

-going stock will upgrade those devices correctly.
[Verizon Samsung Galaxy S III] ericsdeadinside:
I didn't root my phone until after I upgraded to mf1 thanks for the info though.
[Verizon Samsung Galaxy S III] annoyingduck:
So you took the OTA? It will absolutely not hurt to Odin the complete mf1. After all, an OTA is just a dirty flash....
[Verizon Samsung Galaxy S III] ericsdeadinside:
What if I try flashing the mf1 firmware?
[Verizon Samsung Galaxy S III] headcheese:
I'm on 4.3 with mb1.
[Verizon Samsung Galaxy S III] 996:
When do people get random reboots usually? Using the camera or other apps or something? Or just when the phone is sitting.
[Verizon Samsung Galaxy S III] bmeek:
For me, "random" is a very good description of when the phone reboots... While messing with settings, while listening to an audio stream with the NPR app, while preparing to make a call... random.

The not-quite-right-MF1-radio-flashed-using-the-aio-package theory is interesting... It may apply to me because I don't recall ever seeing a full ODIN package that includes the current radio.

BTW, I just updated to CM10.2 RC1! So far, so good (no random reboots yet at any rate).
[Verizon Samsung Galaxy S III] annoyingduck:
The theory here is the same that applies to nexus devices. With a nexus, if a new bootloader is released, it's advisable to flash using adb+fastboot. Flashable zips are created for this eventually, but have a tendency to "miss", which can brick your phone. The same principle applies to odin. The uncommon partitions can easily be borked when flashed through recovery. Another example is the goo manager app..it often fails to write a twrp update if it's an incremental update. Flashing a recovery via fastboot/odin is fail proof.
[Verizon Samsung Galaxy S III] Samsung.Galaxy.S3:
Can't quite seem to get Photo Table in Daydream mode to work like in 10.1.3 version. 10.2 version slides the photo in but blacks out quickly and photo is no longer present. 10.1.3 slides the photo in and remains present on screen. Strange.

Update: problem solved. I took the PhotoTable.apk file from the 10.1.3 build and replaced the one in 10.2. It's working fine now. So is something up with the 10.2 version? Don't know.
[Verizon Samsung Galaxy S III] d1ez3:
How is everyone's experience on RC-1? I am getting a lot of random reboots using latest AOKP nightly and want something stable
[Verizon Samsung Galaxy S III] ericsdeadinside:
I flashed the new twrp, flashed the mf1 firmware over the existing and now I'm running dmeadows kitkat. I have gotten one reboot while listening to Apollo and using navigation in the car.
[Verizon Samsung Galaxy S III] titanshadow:
Mostly mine were travelling or anywhere with a potentially questionable signal. Although, not always, sometimes it seems to be no cause at all and no consistent app problem.

---------- Post added at 03:13 PM ---------- Previous post was at 03:10 PM ----------

Sammobile has the latest that was released by Verizon that you can flash via ODIN, then checking settings reveals it is MF1. I just did the Odin back to stock and then reinstall Cyanogenmod. We'll see what kind of impact that has on things.
[Verizon Samsung Galaxy S III] bmeek:
So does this mean going entirely back to stock - so that you've got to unlock the bootloader, etc?

It would be cool if there was a simple ODIN image that set things right and left you with a clean & rooted device :).
[Verizon Samsung Galaxy S III] titanshadow:
Well, I think the best thing to do for this is to actually fully go back to stock, I even went so far as to go through the initial setup and activation in stock. Then, I did the CM install process all the way through as if it had never had CM on it before. I don't yet know if this did any good but I'm hopeful.

I believe there are stock (TW) based roms that flash the way you want but the problem I personally was trying to deal with was a potential of crashing due to the modem not flashing correctly, for that stock was the best way to go IMO.
[Verizon Samsung Galaxy S III] eaglesfan398:
Does anyone have a problem sending messages but not receiving them?
[Verizon Samsung Galaxy S III] Sniper_5:
Turn off the Voice + setting that allows you to send messages from anywhere on the phone.

Edited for accuracy. I had Google + by accident. My apologies.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] funkatronic:
In went back to stock and I still ran into the reboot issue. Sticking with 10.1.3 atm
[Verizon Samsung Galaxy S III] Prack:
Actually I was able to use voice+ as long as I opened voice and deleted messages older than 30 days. If they stayed on my phone any longer I would stop receiving sms. Then when I would get them they would come in bulk all at once.
[Verizon Samsung Galaxy S III] wpbear:
I can't get Verizon voicemail to hear my touch tones to delete a message if I have auto login setup with my pin saved.
[Verizon Samsung Galaxy S III] Restola:
That's been an issue forever. I should add it to the op.
[Verizon Samsung Galaxy S III] titanshadow:
That and not being able to get Visual Voicemail on Verizon is also an issue isn't it? I use Google Voice but I know some people don't have that option for whatever reason.
[Verizon Samsung Galaxy S III] 996:
How are you guys doing with battery life on the stock kernel?
[Verizon Samsung Galaxy S III] mikalhernandez:
Do you have speakerphone on when you're entering the code? If so, hang up and try again without ever using speakerphone. I had an issue back before I even rooted my phone where if I used speakerphone even once during an automated call, entering numbers from the dialer didn't register at all until I hung up and did it without using speakerphone.
[Verizon Samsung Galaxy S III] Div033:
Has anyone else had the issue where incoming callers appear as "In call"? It happens every so often and a reboot usually fixes it, but is there a different way to prevent this from happening? I'm on RC1 with stock kernel.

To the poster above about battery life, jury is still out... But so far what I've observed hasn't been glorious. Then again I still have my stock battery and that's surely aging too.
[Verizon Samsung Galaxy S III] sanjsrik:
I just flashed the 11/29 nigthly, endless bootloops. I tried to go back to 11/27 and no luck. I get through the "Android is upgrading..." screen and then it reboots itself.

I flashed over previous nightly after wiping cache and dalvik.

Anyone have any suggestions to get the device up and running? Any help would be VERY appreciated.

Thanks in advance
[Verizon Samsung Galaxy S III] Hybridnoob:
Here's the order of things I would attempt. You can try wiping system and reinstalling the nightly. Restore a nandroid backup. If you don't have one, you can try a clean install by factory resetting, etc. Worst case, Odin back to stock and start over.
[Verizon Samsung Galaxy S III] sanjsrik:
I really do appreciate it. Got the thing backup using a 11/27 nightly. I'm just curious if the 11/29 one is having issues?

Also, is anyone having issues with screen flickering? REALLY BAD screen flickering? It's only been happening since (I think) the RC1 build. Only just noticed it a few days ago. Is this a known issue or is there a fix for it?
[Verizon Samsung Galaxy S III] xgujuplaya:
Anyone have an issue with the speaker volume being really loud on RC1 even when it's all the way down
[Verizon Samsung Galaxy S III] bmeek:
The rc1 build and subsequent nightlies have been flicker-free for me. On the rare occasions I've seen flicker with cm10.2, it was (3rd-party) kernel-related.

What kernel are you using?
[Verizon Samsung Galaxy S III] cheekoo:
installed 10.2 release version. Can't wait to use it!

Update - looking good so far (for last 2 hours). me happy!
[Verizon Samsung Galaxy S III] UberSuber:
10.2 changelog

Since Sun Nov 24 06:21:00 UTC 2013

build

•*aff836a Just a few more for flexibility

•*428c25c Additional overrides

•*c253d08 kernel: use target strip command

device/samsung/d2vzw

•*d423dd7 d2vzw: set default cdma subscription to RUIM

frameworks/base

•*aba92e3 WMS: fix no thumbnail image of Gallery in the recent tasks list.

•*e178662 api: Add networkAttributes to the public resource list

•*93a579a Fix resource id of networkAttributes

packages/apps/Gallery2

•*5c49d64 Merge "Gallery2: HU translation" into cm-10.2

•*7a12343 Gallery2: HU translation

•*90b4d94 Merge "Camera: add translatable false for ASD" into cm-10.2

packages/apps/Mms

•*577dbfa ClassZeroActivity: Queue messages instead of displaying them all at once

•*8667cee ClassZeroActivity: Holo it

vendor/cm

•*b6be1be 10.2.0

vendor/lge

•*0fa4db0 Merge pull request #22 from toastcfh/cm-10.2

vendor/motorola

•*64e9fd9 Merge pull request #108 from razrqcom-dev-team/cm-10.2

•*f01bd6f Update proprietaries with xt1080 specific stuff and fix touchscreen fw

vendor/samsung

•*d36e05b Merge pull request #352 from arco/cm-10.2

•*4150563 Update to NFC firmware from S4 Google Edition
[Verizon Samsung Galaxy S III] xgujuplaya:
Updated to 10.2 the speaker volume still seems loud during calls even at the lowest point I can hear the person on the other end when I pull it away from my ear
[Verizon Samsung Galaxy S III] cdrshm:
Anyone just run the update from the settings and install it? Do I need a new gapps also?
[Verizon Samsung Galaxy S III] LudicrousPeed:
Dead Trigger 2 is working on RC 1. Wasn't for previous builds. Not sure if it was a bug fix on their end or the RC 1 build. (MF1)
[Verizon Samsung Galaxy S III] cdrshm:
Oh and I'm on 10.1.3 Currently
[Verizon Samsung Galaxy S III] cheekoo:
I did not use 'update from settings' when i moved from 10.1.3 to 10.2. I downloaded the file onto SD card and used TWRP to install it. I think I used the ga-apps mentioned in the opening post.
[Verizon Samsung Galaxy S III] Bright09:
Anyone on the new 10.2 stable how is it

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] wolficus:
been running it all day...

i am getting better battery life than rc1.

working pretty smooth so far.
[Verizon Samsung Galaxy S III] lou1210:
Question... I'm currently on an unofficial release of cm11. If I wanted to downgrade from cm11 to cm10.2, what's the process? Has anyone tried?
[Verizon Samsung Galaxy S III] mawells787:
Just make a backup of your current set up. Download cm10.2 wipe in recovery and install and don't forget gapps.