yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
I may be shopping for one anyway, unfortunately, as my SGS3 has been acting flaky lately (the latest being that I can no longer restore a nandroid backup without the phone rebooting in the middle of the process). Might be flash going bad, I don't know, but if it starts getting worse, I'm going shopping. Any recommendations for a good hacker-friendly phone that has a removable battery (an sdcard slot would be nice, too, but not mandatory)?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Depends what you're looking for. If you don't mind a used phone, there's gonna be a bunch of various one on the market soon with the release of the Nexus 6. =)

Edit: Also the Galaxy S3 is still a 2.5 years old smartphone. An entry level smartphone like the Moto G can be had for 0$ with any contract pretty much everywhere or 150$ brand new... and both phone are comparable. The Samsung Galaxy S6 is rumored to hit early 2015 (March-April), putting the S3 "3 generations" behind.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
It all boils down to the device maintainer. Even S2 is supported by CM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
True, and I should point out that it's purely speculation on my part regarding the S3's "lack of love," based solely on my observation of the ongoing issues experienced by some/many with sound, Bluetooth, GPS, and mobile data. I don't have any inside info on what goes on behind the scenes, so I can only guess based on what I see. I really am hopeful that things will transpire that'll knock my speculations into a cocked hat. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
It's a phone that was quickly succeeded by another in the same line up (within a year!) and was confronted to full HD quad core phones nearly from the start. It was still a model that sold a lot, and it sucks to see support being dropped like that, but very little devs still wish to put time and effort in it.

Like I said in my earlier post, the S3 is to the point it's comparable to medium-entry level Android phones, so it's definitely a tough sell if you want someone to listen to you. :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
Well, if I weren't having these strange issues, I'd stick with mine for as long as I could get custom ROMs for it, as it's still a great phone even compared to some of today's "better" models. But, I'm thinking that circumstances are going to force my hand, so I'd best do some research. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Although painful, and somewhat long, ODIN back to stock usually fixes a plethora of problems (even if you flash back to CM after). Same for not pulling the same data over and over. Think about it before switching to another phone. Good luck! :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
I was thinking along the same lines. ;) Before doing anything, I'm going to try that and see where it takes me. Reinstalling a custom ROM from the ground up is no longer a daunting process, thanks to Titanium Backup and a few years of doing this under my belt, but it's still time-consuming and a PITA. If flashing back to stock with Odin, then putting a custom recovery back and restoring a previous setup, does the trick, then cool beans.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Yeah, at the same time we're flashing roms every other day, when the normal user will see under 5 rom flashes in his lifetime if he stays on the stock rom. Can't be THAT surprised if we end up breaking things in the process. :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CFoote:
Good points, I guess for me the qHD display and other gizmos on the new phones are just 'meh' for me.....what I want is a fast, well engineered phone that has great battery life. The Droid Turbo on VZW looks nice, perhaps they will port a GSM version over (rumors over that speculation....)...although Moto hasn't been the most friendly of the bunch for installing 3rd party stuff.

I still think the GS3 is nearly as capable as the new phones....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VQ30DE:
I switched to the OnePlus One about a month ago. Girlfriend's Vibrant kicked the bucket so I gave her my SGS3. OPO is huge but I quickly got used to it. Seems only slightly faster than the SGS3, but it has 3 GB RAM and 64 GB flash. It's both cheaper and has a few better specs than most of the flagships for the moment. The camera and battery life are both excellent, so big improvement there.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sgloki77:
I got my s3 on launch day 2.5 years ago and after all abuse and flashing I have put it through is still like day one, is amazing, this was the last device on the galaxy series that came out with unlockable bootloaders on att and verizon, the last of the mohicans haha and it pains to see the maintainers on CM neglecting it, this is still a very capable device.

I'll be upgrading to the nexus 6, but I love my s3 [emoji2]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Alright, I really hope this call volume issue gets resolved sometime in the near future. Every time I answer my phone at work, everybody in our quiet office gets blasted by whoever is on the other end of the line until I can raise/lower the volume slider.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
Anyone have any opinions on the LG G3 and the HTC One M8? Both look to be pretty sweet, and both appear to be unlockable and rootable and allow custom ROMs to be installed. Both have MicroSD slots, and the G3 has a removable battery, which is appealing to me, but the M8 looks nice, too, plus it has car docks available that will enable car docking mode on the phone when plugged in (which is also very appealing). Plus, I can upgrade to either one for $49.99 with a 2-year contract renewal (I don't relish shelling out hundreds of dollars outright, and can live with a 2-year renewal, though I do recognize the appeal of owning it right from the get-go).

However, since I recognize that this is wildly off-topic for the thread, anyone with advice about either can feel free to drop me a PM or three. :) I'd great appreciate any advice you can give me, since my wife is eventually looking to upgrade her phone, too (she's been having all sorts of issues with her S3, but since she's close to renewal time, she'd rather just get something totally new).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dracinn:
Hope we get Lollipop!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
I think this bug has been resolved in the cm bug tracker on 31st October.. add your comments in the tracker if you still face this issue
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Oh, nice find! I'll check this out and report back later.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vitalym:
Anyone figure out the no data issue after updating to the latest version? All the APN settings get wiped and it doesn't let me save any manually entered APNs.

I flashed the latest modem right after installing CM and wiped cache/dalvik.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
I've seen some people talking about flashing back to stock to resolve issues, but I can't seem to find a stock image to flash back to for the i747. Everything seems to old to be able to flash safely what with the bootloader compatibility and such. Can anyone help a brother out? My **** has been acting way to funky to not flash back to stock and see if that fixes issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gephross100:
i hope im not backtracking on this, but running the last stable release I have been having a lot of issues with the ROM's camera app, Googles camera app, and occasionally with instagram when I open the camera. It either makes the phone lag with those applications or it disconnects the camera and i have to restart the phone to be able to use it.

has this been patched in a nightly? is this even a cm ROM issue? I have reflashed to try and solve this problem, maybe it has to do with my settings?

other than that this has been a great build, keep up the good work cyd :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
Been having that issue, too. Trying to find a stock image to flash back to.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kmarc33:
I used this one, no problem for me:

http://xdaforums.com/showthread.php?t=2788357
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blasterrr:
Camera crash, especially after long press to auto focus has been a long time issue. It has been fixed recently. There were over 10 asserts about camera functionality last week or so. Since then mine hasn't crashed. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
So you are still facing this issue or this has been resolved
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
It seems to be resolved for talking on the handset, but when routing the call through speakerphone it still seems overly loud even on the lowest volume.

So I guess I can say that this issue is 50% resolved? Or maybe 75% since the handset volume is what is being used the majority of the time.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] korrectmethod:
Just thought I'd share that NVRebuild method (http://forum.cyanogenmod.org/topic/99965-Gps-Issues-With-Latest-Nightlies#entry487191) after clean flashing stock rom (http://xdaforums.com/showthread.php?t=2788357) then clean flashing m11 again indeed provides working GPS again. Thanks guys.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
So am I the only one with a looping ringtone that plays over itself? Like a few second after it starts ringing, I'll hear the ringtone start again while the other is still playing.

Ideas?

Edit: Ignore this. Found the answer, it was caused by Autoring, an app created so certain numbers ring even when in vibrate/no sound mode (good for emergencies!). I had the Force ring option set, and that caused the issue. Disabling this still leaves the software working, without the glitch. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tcaudill01:
I appreciate this info, I can confirm that this does indeed work.

I would also like to add that dkp's - d2att kernel from 10/29/14 will give both mobile data and wifi.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kmarc33:
Ever since the latest update Cyandelta has been odd for me. Before I pursue this elsewhere is anyone else seeing this null?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kevinga:
Yes, I also have had the same thing. Not sure what to make of it. The delta updates seem to be working though. This would be on my Oneplus One. I have 2 S3's in my family but I have not been doing any updates on those phones.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Just noticed that I get a can't connect to camera error with Google Camera after trying to record a video. The only way to get my camera back afterward is to delete the resulting video file from my gallery and clear the camera app data. Is anyone else experiencing this? I'm just trying to isolate the problem to either my ROM or custom kernel.

I'm running the 11/01 cm11 nightly with the latest dkp kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] davenrai:
Have most of the camera issues been fixed yet?

Does Google camera offer HDR on the s3?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
I'm having issues recording video at the moment, and HDR is not currently supported on the S3 through Google Camera.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ¿Will-it-Blend?:
I'm using snap camera and I'm getting great shots with full 1080p video recording and working HDR. No issues here.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Hm. I'm getting the issue on both the stock CM camera and Google Camera. I would've thought that any camera app would have this problem as it seems like it's an API/ROM issue. Maybe it's my kernel then.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Old cyandelta issue, don't mind it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blasterrr:
Can't connect to camera issue is still there : using NOV 9th nightly :mad:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbrian27:
On 11/10 nightly and I'm not having the issue. I was having issues with the camera beforehand, so I clean flashed 11/10 and it's working just as it should.

---------- Post added at 06:46 PM ---------- Previous post was at 06:45 PM ----------

Edit: I'm on the latest Lean kernel if that is any help.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Have you tried recording a video? That's when I get the error.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbrian27:
Yep, that's the first thing I tried. I was able to record a handful of videos then take pictures, then a couple more videos without the error.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blasterrr:
I'm on stock kernel and get camera FC sometimes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rifleman2:
I'm on M11 stock kernel with latest Google camera and getting the same issues with videos.

Took me a while to figure out I had a corrupt file causing the very familiar can't connect to camera error.

Sent from my external brain.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Yeah, it's definitely an issue with the ROM regardless of kernel. Not sure when it was introduced. The corrupt video file that is left behind after trying to record is what makes the camera app repeatedly crash afterward. Just gotta delete that file and then the camera will launch again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nirogu325:
Pardon me but...which file is that and in which directory?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Look in your gallery for a video file that just shows black in the thumbnail preview and then delete it. Should be the last video you tried to record.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nirogu325:
It's kinda weird because last nightly I tried was 11/8 and it crashed as soon as I changed a setting, any setting in it. I'm amazed on how stable CM11 is on the GS1...compared to...the GS3 situation that has been ongoing for long months. Makes me wonder if they'll just drop the KK mess and bring us directly to L.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I'm actually running 11/09 with 0 issues, for what it's worth... stock kernel & all.

Edit: Also can anybody shed light on the camera issue? I just took 4 videos with the stock camera, once again with no issue whatsoever.

Edit 2: I was only able to recreate the issue using Google camera, stock camera i can take 1 second long videos and it doesn't glitch. So there's that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Hm, so it is a problem with Google Camera exclusively? I'll have to go back and try the stock camera again. It was giving me the error before too, but I think I maybe hadn't deleted the corrupted video file yet before trying it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
As far as I can see, yes. This doesn't mean it's not fixable in the rom though, the camera on the S3 is notable for being... picky... in anything but stock TW.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blasterrr:
Can you elaborate please? What corrupt file and what is the remedy?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nirogu325:
You may look five posts before yours for the answer.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
M12 is out for our device. This could be the last M build for our device, all depends on CM
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blasterrr:
Just read online that Google has eased restrictions with micro SD cards in lollipop. Ah man... Its about time that we get this, just like we had before kit Kat :D

Apps will now be asking for access to micro SD. Feature is called Richer Access.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Wasan't an issue with custom roms, only with stock ones.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] davenrai:
Any significant bugs for M12 Might flash from tw 4.3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] korrectmethod:
Dirty flashed m12 on top of clean m11 and I still have GPS surprisingly. No issues that I can see so far.

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tanker Bob:
Why do you say that?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dracinn:
Fingers crossed.

---------- Post added at 06:34 PM ---------- Previous post was at 06:31 PM ----------

I think it has to do something with the kernel version why we may not get it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Sorry, I meant this could be our lat CM 11 build. I can't confirm about CM 12. There are rumors that CM will support 50 devices in CM 12
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MikeRWK:
Any known bugs in M12? I'm looking to go from kitkat to CM.I had cm8 or 9 on my lg p500 it turned the phone into a completely different beast.Also will flashing CM erase my internal memory?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
No, but you should wipe everything if you're coming from a TW rom. Switching from one to another trying to clear as little as possible is always going to end up in less than par experience.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MikeRWK:
Thanks, I've it up and running the only problem I'm having is when I go to uninstall system apps like Email,Exchange Services,Google games-movies-music with Titanium Backup the apps 'uninstall' but dont actually uninstall!?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tanker Bob:
Ah, got it. I don't think that we'll see any CM12 builds until after the beginning of next year. It takes a while to analyze the AOSP code changes and incorporate CM-specific features. I'd be surprised if there were any M builds of CM12 before the spring, maybe early summer. That's pretty much how long it took with CM11.

---------- Post added at 08:20 AM ---------- Previous post was at 08:15 AM ----------

Same update sequence here. Checked GPS last night an it locked onto my position quickly. WiFi and BT seem to work OK as well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ¿Will-it-Blend?:
Is there a change log for the M12 build anywhere? I'm currently on LikeWise but I'm interested in seeing what the new M12 build is offering. I always like to read the change log before I l flash anything though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] korrectmethod:
Change log link is at the bottom of the first post.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
This does not apply to M releases, because they're builds from different nightlies. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Herox:
Rom is great but I can't get service. My Sim is in the phone and looks active but it says "No Service". I updated both the bootloader and Modem before flashing from 4.4.3 to this newest 4.4.4 nightly. Anything I can do here? I have full bars but no service?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tanker Bob:
Are your APNs still good? Maybe manually creating one as illustrated here may help.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Herox:
I tried to put in APNs myself and they all refused to save. When the rom first boots it says I need to activate my sim during the first time setup stuff. I switched to SlimKat and it works perfectly. It's either a problem with that specific nightly or just bad luck. Of course I did a complete system wipe.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tanker Bob:
Something else that sometimes works is to do a factory wipe and load a TW ROM like this one, follow the instructions at the link, then after that's working do another factory wipe back to CM11 M12. That's a lot of wiping, but it should get your phone working again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Nico3d3:
Anyone else had trouble with Deskclock app on CM11 M12? It was freezing and crashing when I tried to schedule a new alarm. I had to replace the app with the one from CM11 M11. Also, does it still have the bug where the phone randomly freeze and reboot while using Google Chrome?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MikeRWK:
Anyone know why I can uninstall System Apps with Titanium Backup but they dont actually uninstall?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] johnhazelwood:
When I install a new nightly via TWRP, it appears to rebuild the cache every time. This isn't a big deal with Dalvik enabled, but Art takes forever. Is there a way around this? Or is this how CM updates work?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kbatman74:
It may wipe cache when you flash it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] airtower:
Drunk. 3/31 no boot with ART.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
Don't flash 3/31 with KT's latest kernel. Errors. Errors everywhere. Good night.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sugarkryptonite:
Thanks guys.

Sent from my S3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] doctorspeed1:
331 with stock kernel good
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jep56:
Can we dirty flash nightlies over previous CM11's
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Phazonclash:
03/31 is broken for me, with QuantumKernel. FC everywhere, at boot. Rolled back to 03/27, everything's good
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Use stock kernel, works just fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Phazonclash:
I will give it a try polobunny, thanks for the advice.

I could continue to use Quantum with QuantumKernel but honestly, I have a hard time living without ART (currently broken with Quantum). ;)

Gotta chose the lesser poison
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I can't vouch for ART working though, it works fine with Dalvik but I haven't tested ART! I usually test it, but I gave up not long ago when half the time it was broken. :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] airtower:
ART very much does not work on 3/31. Dalvik is just fine. Luckily I happened to be flashing on two phones at the same time, one on ART the other on dalvik so I didn't have to spend a bunch of time troubleshooting. Thank god for your revert zip:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Phazonclash:
Yup, ART is broken on 3/31 regardless the kernel I use (KT747, Quantum, Lean) Dirty-flashed 3/27 over 3/31 without problem though, and everything's fine. I hope they'll fix it in the upcoming nightly ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
That's how all ROM updates should work. Any change made to the runtime code (Dalvik or ART) means rebuilding the appcache for the new runtime build. Leaving old appcache files from a previous build can (and usually will) cause app crashes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] johnhazelwood:
Thanks. I guess I didn't care as much before, but because ART takes 20 minutes or so to rebuild I'll be a little less flash happy :) I think I was hoping it would just rebuild the delta..oh well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
To figure out the delta between builds, the runtime would have to recompile each app individually to see how the new output differs from the old output that's already in the app cache, so it's actually

faster

for Android to just ignore/delete the entire cache and start fresh as soon as a runtime change (either an update, or just switching between runtimes) is detected.