yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
CyanogenMod (or Steve Kondik, AKA Cyanogen) actually posted on G+ about how you DON'T need to wipe between nightlies. I did a quick search and this came up. I wipe /system between nightlies but I have never done a factory reset(wipe of /data). A modern smartphone platform would never make you do a factory reset just to install an update. While CyanogenMod is a custom version of Android with nightly builds, it's not somehow going to break if you don't do some sort of voodoo ritual just to install an incremental update. If something breaks, it's most likely from not wiping the caches or messing something up, not from bugfixes or the occasional new version of Android.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Johnny424:
yeah but what your missing dude is the fact that its not just bug fixes getting merged all the time. there are experimental features being merged. especially when jumping from say 4.1.2 to 4.2.1..CyanogenMod updates and Samsung updates are two different beasts..so comparing them doesn't make much sense to me..but either way, to each their own :thumbup:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CZ Eddie:
Here is a copy of an email I just sent to CarHome Ultra developers:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Fallon:
"Car dock home 3" will exit when on a dock that trips car mode & you hit the home button as well. I expect is a CM issue not an app issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] knarfl1:
Can you give me examples of experimental feature that require wipe?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zelendel:
If you read the post by the CM all nightly changes as considered alpha. The nightlies are made to see what breaks from different code changes.

Wayne Tech S-III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] milicigoran:
As long as you install the correct carrier rom and wipe data you'll be fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Kamikaze19:
Same problem here... I check the change log everyday hoping there's a fix for this or for a new issue where my wireless signal is weaker than before. :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xaznxplaya:
Noob ass question guys, is it me or my device doesn't recognize my sd card =/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
If it's 64gb card, you have to format it as FAT32.

Google Search how to format SD card to FAT32
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shamidude:
The one workaround that I have used for this is to use the asp switcher to switch to a simple app then hit back again to exit and go to the home screen. Something like the settings can help with this. It is an extra button to click but faster than a reboot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kswa1987:
Just a quick PSA:

2/24 nightly looks good so far... no bootloops or other parades of horribles so flash away!

(used cyanogenmod updater to flash over from 2/22)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
I just flashed it. Within 5 minutes, my phone started lagging, then froze hard when locking. Had to do a battery pull. This happened right after I altered the lux settings for auto brightness.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
I am happy with this Nightly. Thanks for sharing your experience
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] awaisuk:
so I flashed another kernel but then didnt like it, so I flashed the nightly back ontop without wiping data..I did clear cache and delvik cache and fixed permissions.

Is that enough? or will it cause any issues?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Monkeymannnn:
I'm not currently having any. Flashed ktoon's kernel (dunno why, never had anything but problems with it on cm) and flashed the 2/24 nightly. Smooth sailing so far.

Edit: did what you did minus fixing permissions.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Yes. The included CM kernel replaces the whatever was there before. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] knarfl1:
So all alpha changes require data wipe?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
Only wipe IF something goes wrong. Even then, try an earlier nightly first.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
I think the general consensus is that if you are just flashing from nightly to nightly, there is no need for a full wipe. However, if you are going from major version to another major version, a wipe is probably a good idea, and people are unlikely to take your bug reports seriously if you haven't reproduced them after a full wipe. If you are experiencing an issue, please do a wipe and try to reproduce with a fresh install before reporting it. Otherwise, the developers can't know if the issue is their software or someone else's.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrhaley30705:
Permissions are fixed when you flash gapps. No need to do it twice.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] erbsmokah:
This is true but you dont need to reflash gapps after a dirty flash. So i recommend fixibg perms
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrhaley30705:
I always reflash gapps when i flash an update, clean or dirty
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] humblehyper:
Can someone tell me if there is a workaround when the phone doesn't wake up after locking? The screen is blank and the only thing visible is the soft key that lights up. Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrhaley30705:
Push the power button 2 times, slowly. Regular unlock should happen then
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] humblehyper:
Thanks :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] knarfl1:
Samsung is set to do a launch event on March 14 for S4. Will we see stable or RC CM10.1 in next few months?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BuBbLeFIZzY:
I'm not sure if this was ever resolved, but I think I found the reason why DCIM folder was taking up so much memory. Its not because of the extra 0/legacy/folders either. I dont think. I figured this out by going to properties and noticed how much memory it took and how many folders is in DCIM before I open it. It shows 7 but when I click in there's only 6 folders. I didn't know how to make The hidden file show up until I played with manager(used es file explore) I clicked on ' sd card anylst' and went to DCIM folder. And I found the 7th folder.its called thumbnail I think and the first two if I remember said data3. There's two of them that made the DCIM file 3x as large than it should be. I decided to move my pictures to exsdcard. And delete those two thumbnails file to see if it would fuk up my phone. So far everything is still running smooth. So I dont really know what they were for. Es file explore did show 3x more free space as soon as I deleted it. But I rebooted the phone and it only show the 'real amount I have free by moving my pic and vids to the extsd. But in settings/storage it shows a more accurate amount of picture/video memory usage.

And like I said idk what those thumbnail files were for but it never came back after boot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
The thumbnails are an issue in all android, if i recall. They're the thumbnails for your gallery an such. It'll come back eventually.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] doctorspeed1:
Just wondering if anyone is having problems with the 2/24 and 2/25 builds randomly freezing. Once was during a phone call and other times just random. But it seems to be occurring when the screen turns off and occasionally there is a small horizontal stripe across the screen as if it froze during the screen-off animation. Flash with cache and dalvik wipe only. Tried fix permissions as well although I don't thinks its the problem.

If I'm the only one then it looks like a full wipe is in order.

I wonder if this is the problem

http://review.cyanogenmod.org/31110
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
I haven't flashed 2/25, but I am seeing this issue on 2/24. It didn't freeze mid-animation, but I've had it lock up several times since I flashed it. Haven't had the time to go back to an earlier nightly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] assaf.bm:
Anyone missing the reboot options? (i.e. Recovery, Download Options)

I am on 25/2 version and I am missing it from my power menu.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
That happened to me on 2/24. I locked the phone and it froze mid CRT animation. Had to take the battery our. Reflashed 2/22 and it's all good.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xiphosurus:
Please learn either to search, or just look back in this thread. This was covered multiple times.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sbddude:
I have this problem (freeze during screen off animation) on M1 20130121. I installed clean directly to this build.

Any way to disable the screen-off animation? I don't really care for it anyway.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Wado1:
I have the screen off freeze too. I'm on build 2/24. I'm going back to 2/19.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thecapitalr:
I just tried searching and went back ten pages or so... I am having this problem to can someone kindly describe how to fix it? I just updated to 2/25 from 2/16 and this happened.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
look in developer options...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SomethingAwesome:
Call end noise?

I had this as well, when I updated to build 2/24. Haven't seen it on 2/25 yet, but it didn't happen every time on 2/24 either.

Anyone know how/if it's possible to disable to call end sound/noise? My phone is set to silent but still gives off a really annoyingly loud beep when a call is disconnected or ended. :confused: A search turned up an unanswered result in another phone thread, seems like it might be a CM issue?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jpstiehl:
And before you ask, if you don't have Developer Options at the bottom of the Settings screen then go to the About screen and keep tapping the Build number until it says that Developer Options are enabled. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] boram:
I can confirm i am getting the screen freeze on the 2/24 and 2/25 builds. Last line of the CRT animation shows, and stays stuck at that. Must be rebooted. I can't figure out a pattern.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] abteer:
A temp fix would be to run ktoonsez newest kernel. Been running it for about 15 hours with no CRT freeze yet.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] czechpunk:
I had a random lockup while streaming bluetooth on 2/24 nightly. I didn't see enough of a change on 2/25 to flash so I couldn't speak to that. I just assumed it was a bluetooth streaming thing...

---------- Post added at 04:23 PM ---------- Previous post was at 04:22 PM ----------

No you didn't; if you had, you would've found these from just last week:

http://xdaforums.com/showthread.php?p=38299263&highlight=reboot+option#post38299263

http://xdaforums.com/showthread.php?p=38289520&highlight=reboot+option#post38289520

http://xdaforums.com/showthread.php?p=38289387&highlight=reboot+option#post38289387

http://xdaforums.com/showthread.php?p=38218960&highlight=reboot+option#post38218960

6th Entry using a Google search ==>> http://bit.ly/Zw0YT3

Yet another option ==>> http://bit.ly/wcfSBJ
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Monkeymannnn:
I had it happen even with ktoons kernel.

Edit: I had been running kt's kernel for about a half hour when I got the crt freeze.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrhaley30705:
I'm not seeing any crt freeze, running 2/24 nightly with included kernel. Also a fill wipe install, if that matters. Well, actually 2 full wipes. First time the ROM didn't f feel right. So i did it again. Been golden since.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
Well, for me, one problem seems to be a good thing. I'm still on 0219 because there are no further updates showing up in the about, check for updates. I saw all the issues posted so I did not flash from the website download.

This build is the first functional stable build I've seen in quite some time if others might want to try flashing back.

Does anyone know why I'm not seeing updates?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sbddude:
Went from M1 to 0219 to try and solve the freeze during power off animation. Using KT747 (Ktoonsez) kernel on both.

I still got the freeze. :(

Is there a way to disable the CRT power-off animation?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrhaley30705:
Edit:

Just had a freeze. Had to reboot
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
I'm full stock. No custom kernel.

---------- Post added at 01:57 AM ---------- Previous post was at 01:56 AM ----------

And gapps 121212.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] maxiimida:
CRT freeze here too. Last night's nightly. Phone suddenly gets really laggy then locking it causes to freeze at the end of the CRT off animation
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] smeatr0n:
You can disable the CRT animation by changing the animation settings to anything .5 or lower in developer options. See if that prevents lockups as a temp workaround.

Sent from my thumbs to your brain.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
KT said that it's some CM kernel commits from the 24th (late on the 23rd). He added them to his kernel late on the 23and everybody on all ROMs started having these freezes. His newest kernel from yesterday has the commits removed, and with them the freezing... although I am on BMS now... with no freezes in 24 hours running the the CM10.1 from 2/24.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Wait for the next nightly. Cm reverted the commits to their kernel that are causing that. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BAM1789:
The CRT-Off animation is happening to everyone no matter what kernel they are using.. someone obviously needs to read more..

On-Topic: Happened to me twice today, stock CM kernel..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] C2Q:
To everyone experiencing the home button bug, you can set your phone to automatically reboot at some time during the day/night so you can wake up with a non-buggy phone in the morning. It was just annoying having to reboot my phone as the first thing I do every morning, this pretty much solves it until an actual fix is released.

http://linuxplained.com/setup-automatic-scheduled-reboot-in-android-phones/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] draino623:
I don't have this problem. I'm on 0224 build with 0208 ktoons kernel.

Sent from my Samsung Galaxy S-BEAST!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
The commit mentioned in doctorspeed1's post has some heavy changes to memory management. Based on my experience, this change borked the kernel. This is why people using kernel's other than the stock kernel are less likely to see it unless the kernel they are using also has a similar change.

DISCLAIMER: OPINIONS AHEAD

IMHO, people who aren't using the stock kernel shouldn't even post bugs or other info in this thread as it detracts from the actual troubleshooting and development process and muddies the waters about what CM's features and capabilities are. It's harder for users to figure out where the stability is and it's harder for the devs to track ongoing issues, especially when it just starts wars between the stock guys and the ktoons guys. This is not intended as a flame or any sort of insult whatsoever.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sbddude:
I tried both 0.5 and 0/off for all three animation settings in the developer options. Animations are now off for switching between apps, etc. but the CRT-off is still happening.

BTW, 0219 nightly seems to freeze more than M1 did.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] etham3:
Anybody else experiencing tremendous battery usage by Google Services on the latest nightly fully stock? Actually, I've noticed this the past few nightlies but the 2/25 is the worst by far (as much as 50%+ is used by Google Services alone)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
I'm on 0219 and services is typically around 40% of battery. I'd like to understand this better or maybe kill it dead and see what breaks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrhaley30705:
Me too on the crt animation. I wish the option were there to remove it completely
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sbddude:
Besides the CRT freeze issue I also have my music playback volume (pandora) jump up when a notification sound plays. I saw that issue mentioned earlier. Is there a fix?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] czechpunk:
FWIW, I haven't noticed a screen freeze yet on 2/26 nightly. Been running it since 5:30am this morning.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blacura:
Anyone having issues forwarding pictures or slide shows from a text? I seem to have to save the files to my phone then recreate the slide show to be able to send it out.Also how can you send a group text?I tried creating a message but no option to send to group. maybe its me.

Thank you for your help
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] doctorspeed1:
I'm no expert but several posts back, Task said that Steve reverted the commit that was causing the CRT freeze on the 226 nightly. I haven't had a phone freeze all day since updating to 226.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flashedmytiltblind:
I'm no expert either, but if I had to guess:

hardware/qcom/display-caf

daf2395 overlay: Add support for pipe dumps.

c47fa2e overlay: Fix rotator output buffer size.

was the fix.

I'm in the same boat. Had multiple freezes on 2/24. No problems since 2/26 update.

or rather:

kernel/samsung/d2

1d80bcf Revert wait4vsync changes util panel init sequence is fixed
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NYFan:
NIghtly 2/25 & 2/26

Hey all, I've been running these nightly updates and the last 2 days I had a few issues where my screen would not wake up when trying to turn it back on. I had to restart my phone a few times. On some occasions i would look at my screen and there was one white line through the center so the screen was on in some capacity. Yesterday's 2/26 update my phone screen would not go on only 1 time. Can someone verify if they had a similar issue in the last 2 days, is this a known issue?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] airtower:
In case anyone doesn't follow CM on google+, one of the device maintainers has fallen ill and the team has reached out to the community for donations to cover medical expenses. If you've never donated to the CM project, this might be the time.

https://plus.google.com/+CyanogenMod/posts/ib5wz8jk1Jy
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rykr:
Did you ever get an answer to this? This one issue is what has been keeping me off AOSP. I have nandroids of CM and AOKP on my phone right now but with 4 kids I really like taking nice videos of what they do and with AOSP having very low recording volume that is hard. I seem to remember cm10.1 fixing this issue some weeks ago (maybe M1) but recent nightlies I've tested still show low volume when compared to stock.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] smeatr0n:
It's been around since cm10, I've never seen a aosp/cm/aokp ROM that doesn't have this issue, but nobody seems to mention it. I'm with you and stuck on touchwiz for now until someone decides to work on that for us. I want to use this ROM but can't justify missing out on the family memories just because I insist on running the latest ROM! Siiigh. Aosp themed touchwiz ROM is the best I can do ATM.

Sent from my thumbs to your brain.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jpstiehl:
Hold back to kill ability? That feature is the last option in the Developer Options menu in CM. The more you know... :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] predatorian:
Anyone else getting "can't connect to camera"? Since my phone came back from a screen replacement I don't know if they made something or was just the update. I read something a few posts before about a fix for camera, maybe I'll try that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] python2121:
This is my second post on the subject so I apologize, I am merely posting out of sheer desperation. Has anyone been able to disable LTE? My office situation is a 1 bar of LTE, with every connection failing, and perfect hspa+, an issue shared with everyone in the company. One person posted responded to my previous post simply telling me that the issue was fixed months ago in a radio update, but I am on LK3 and tried a few of the others and have had no luck.

I am literally so desperate that I am ready to move to the Nexus 4 simply because it doesn't have LTE at all.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sbddude:
What about changing the APN?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ganjah:
That does not do it on any cleanly-installed CM10.1 nightly or milestone. None of the options in APN change anything whatsoever, that I can tell, except for one thing: changing the APN to anything other than ATT LTE (pta) will often make the phone unable to switch to data via cellular network after it's been on wifi for any period of time.

Changing the Network Mode does nothing, and in fact, it always reverts back to LTE/GSM/WCDMA instantly.

The same with "Use only 2G networks." It does absolutely nothing as far as I can tell in Signal Type.

I'd really, REALLY like to change the APN to permanently prevent LTE connections, but nothing in the settings does it. I've also tried a variety of phone ## numbers #* combinations recommended at various places around the AT&T S3 forums, and not a single one of them work.

I've searched for resolutions to this problem ad nauseum, but have yet to find a single solution that will prevent LTE at all.

If you can be of any assistance, I'd really appreciate it!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kingpongg:
tethering

it looks like WPA/WPA2 tethering may be fixed in the next nightly.

http://review.cyanogenmod.org/#/c/31356/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] radeon_x:
After adjusting my auto-brightness levels, the phone rebooted the instant I hit the apply button. Now, I get stuck on the boot animation. Tried battery pull and wipe cache/dalvik. Anyone know where the brightness settings are stored in /data/data so I can try to clear them and restore from a backup?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 02busa:
And tonight's build just failed... Alot of fails as of late.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] czechpunk:
I found something on this when I first got my phone. It had something to do with popping the sim card out with the phone still on, then changing to gsm/wcdma, and then putting the sim card back in. It will stay on HSPA(+) until you reboot
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ormandj:
Did you submit a bug report? If it was a problem with the M build then you should, as the devs don't actively read this thread.

Search first to make sure an existing bug report doesn't exist (if it does and you have additional useful information then update it).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
So far, 2/26 is the best ROM I've used so far. The battery life is groovy, speed is groovy, and I've had no freezes or anything.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ganjah:
Right, I've tried that. Unfortunately, it doesn't work - as soon as I pull the sim card, it says "no network until you restart," and that is actually the case. I get zero service until I reboot, even if I airplane mode, etc.

Even if it did work, 10.1 is so unstable with the home button bug and the creeping lag bugs that it needs a reboot every 12 hours or so, if not more.