yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
I'm not sure if these means much, but I went and tried to reflash the boot image with heimdall. That process failed (or it said it failed), but I was able to boot. I got stuck at recovery again when I went to make my post update backup, and the same process got me back to Android. I'm not sure what's going on there specifically. Heimdall is throwing "ERROR: Claiming interface failed!" which is apparently an issue with heimdall 1.4RC1 and is fixed in RC2 (which I don't have time to build from source right now). That issue persists on Windows and Mac, I haven't tried Linux. At this point, I think I'll have to either wait for the boot issue to be fixed or make the time time build heimdall from source. CM Forums

I also updated to CWM 6.0.2.9, but I doubt that would cause this issue.

Interestingly, I cannot get ODIN (3.04 or 3.07) to see my device at all. I really hope the next Nexus device doesn't suck (read: has LTE for AT&T).

I just found a Win32 source built heimdall 1.4RC2 which seems to work. Of course, now the boot issue seems to be resolved without me doing anything......

http://www.d-h.st/CyD
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gd1147:
I also did the update to CWM 6.0.2.9 so maybe that is part of the issue. Where is the download for Heimdall, and I am being an uber noob here, what am I using if for exactly? Please don't flame me, just trying to get my phone up again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
I updated my post with a link to heimdall 1.4rc2 that I found. I based what I did off of the instructions here (http://wiki.cyanogenmod.org/w/Install_CM_for_d2att).

Basically:

Grab the latest nightly from get.cm, and extract the boot.img from it.

Download the heimdall 1.4rc2 as linked in my updated previous post.

Follow the instructions on the cyanogenmod wiki for getting heimdall setup, but ignore the recovery bit. Windows might try to find drivers on Windows Update, let that finish or cancel it. If Windows installs drivers, zadig.exe won't auto-populate the device for driver installation. in zadig.exe, select List all devices from the Options menu, then select MSM... from the device dropdown.

Drop the boot.img from the nightly into the same directory as heimdall.exe (Release).

Run the commandline as Administrator (open the start menu, type cmd into the search, right click on it, select Run as Administrator)

Navigate to your heimdall Release directory.

Run heimdall detect to make sure it can find your device.

If it finds it, run heimdall flash --BOOT boot.img (BOOT has to be all caps, add --no-reboot if you don't want it to reboot when it's done.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gd1147:
Thanks. I appreciate it. On a whim I just put my phone into download mode and then rebooted it without doing anything and it booted into Android. Looks like it could be a bad CWM update.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
That's fracking weird. I hope it's that simple. I couldn't test that theory earlier because ODIN wouldn't recognize my phone and I can't spend all that much time on this issue while I'm at work :D.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gd1147:
Yea, very strange. Going to test my theory out when I get a free moment.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
What's so special about the 3.4 kernel?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Good example of why some may consider it special ^^^ :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xiphosurus:
The dates on my recovery backups are messed up (all 1970). I believe this is a known issue with our phone, but on whose side? CM? Or hardware? Now I don't know which one to back up. Is there a consistent way to calculate the correct dates based on the wrong dates? Or better still does anyone know a good work around or fix? Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
USB debugging appears to be broken in 0318.

I flashed back to 0317 and it works fine.

Also, this BSOD is nasty. It seems that BSOD is occuring with USB charging. Not sure what triggers it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JDM STi:
The recent issue with BSOD, can those of you have problem right now confirm which NIGHTLY it is? 0317 or 0318?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
I had flashed 0318, and on first boot, it was locked up. I'm back on 0317, which I believe only has the freezing on phone calls.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 2new2care:
Been on this rom since the week cm10 started and 3/10 is the best build I've used by far on all of them. I'd usually use the nightlys a few times a week but its been so solid I haven't cared to.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] etham3:
Dirty flashed 3/18 nightly. Battery life today has been horrendous, with the top hog being Android OS at nearly 75% power. Lost about 40% idling in about 4 hours. Stutter on audio also seems to be back although it seemed to be fixed 1 or 2 nightlies ago.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jpstiehl:
If you turn off USB Debugging does your BSOD go away while plugged into your computer?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] maladju:
I am also interested in this issue. I did some searching a while back and didn't really find any solid answers. The only thing I can think of is that the phone lacks a clock when the phone is powered down. To illustrate, put your phone in airplane mode and reboot: the date and time should be similar to the one you see in recovery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sdotagain:
Me too. Call freezing seems to be fixed but battery is not so great.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jpstiehl:
You are correct.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bobloadmire:
Yup, 18 totally fisted my phone. back to 17th.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zmore:
The switch from the 3.0 to 3.4 kernel in the latest 3/18 nightly definitely brought some not-unexpected instability with it. Twice since flashing it about 6 hours ago, my phone quickly ground to a halt over a few seconds of semi-responsiveness (so not an instant death :)).

Has been smooth sailing for months (latest gapps & stock kernel) -- but now we're in rough alpha waters again. yarrr mateys.

edit1: didn't have any recovery-related issues, because, TWRP.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
I'd say it's time for you to do a clean flash. I am having

zero issues

running the CM 3/18 ROM with Task's underwear kernel posted today.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
How about with stock? I'm too lazy to flash a kernel on top of the nightlies.

What keeps all the awesome kernel work done for Tasks's kernel from being rolled up into core? Too far from AOSP?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pixbuf:
I flashed 3/16 when it was released and then 3/18 today and have had 8 or 9 random crashes or freezes since 3/16 not related to phone calls. No OC or UV or anything. Stock kernel. Annoying.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rockynewsmaster:
I odined to stock, then clean flashed 03/18 and I'm having zero lag and zero other problems, plus my battery is doing great, but of course everyone's phone is different because of apps and widgets they use as well as sync settings and data use

Edit: also using 03/01 gapps and stock Cm Kernel that came with rom
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
Based on the fact that koush reverted the 6.0.2.9 CWM to 6.0.2.8, I'm going to guess that was our issue. Haven't tested it, but that's my gut.

EDIT: BOOM! I was right, although it was worse than I expected. http://review.cyanogenmod.org/#/c/34068/1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gcamp0730:
I dirty flashed from 3/17 to 3/18 (last clean flash was going from 10.0 to 10.1) and have had zero issues; I'm using the stock kernel. Actually my battery life got noticeably better compared to the 3/17 build.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VashTS:
hey all, new to sgs3, came from samsung captivate, just posting my experience.

i have had a few phone shut offs on early March builds, but I have been updating ever since and its happening much less. it occurred on day one, i almost **** a brick when my phone was black screen. took me a few minutes to realize it powered itself off. other than that, no issues, been running PERFECT. maybe its just because i upgraded and its still new but this phone + this rom = perfection. battery is great, although i have wifi at work now, so im not on cell data connection as much.

i have not even clean flashed since i got CM running. i might soon but waiting for a good milestone to do it. i am also an app whore. i got quite a few games and stuff on my phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AlbertoM:
And you'd be right, oh wise one. After getting into I-can't-get-out-of-Recovery-Loop for the past couple days and having to get into Download to get out of it, I read your post, reverted back to 6.0.2.8 CWN and all's well.

Thank you thank you.

Alberto
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] techniq35:
Wireless Channel 11

Has anyone else had issues connecting to a wireless SSID on channel 11? I can connect fine to other SSIDs on channels 1 and 6, but have 2 different networks which I can't connect and they are both on channel 11.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] spectrumfox:
Performed clean install of 3/19. Using stock CM kernel.

I'm noticing audio skips and stutters whenever something on screen is pressed or activated. Also on my way to work this morning while playing audio from Google Play Music, my phone gave a high pitched squeal for a few seconds, then rebooted itself.

Has anyone else seen this issue? I take it its because of the new kernel being used in the latest builds. Since I'm not sure LogCat would be useful in this situation, does anyone know how I can help troubleshoot or provide logs of some kind?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jpstiehl:
This exactly, "audio skips and stutters whenever something on screen is pressed or activated" was happening on Saturday 16th for sure. So as far as I can tell it has nothing to do with the 3.4 kernel that was merged on Monday the 18th.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
This has been an issue for several weeks. I'll see if I can find when I first posted it here.

---

This is the first post I can find specifically noting stutter related to lock screen, power button, etc.

http://xdaforums.com/showthread.php?p=38352902&highlight=stutter#post38352902

Looks like it was introduced between 0219 and 0221
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aznkenshin:
Did YouTube videos stop playing for anyone else on the 19th nightly?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] evil5826:
Last two Nightly's borked Lean Kernel. Since it can't be installed now, would one please include Fast Charge in CM!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BuBbLeFIZzY:
03/14 was the nightly that broke it. I had 03-17 installed and kept downgrading till I hit 03/13 which seems to be working fine. If your using a different kernel you might wanna down grade an update back. Because I used KT 03/16 kernel which make the skipping happen. Went back to his 03-14 it stopped. So idk which to blame. I just know 03-13cmnightly stock kernel is the one that made the skipping on anything I pressed go away.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] spectrumfox:
It appears to be a CM kernel issue, as I installed Task's new Underwear kernel from his page and his latest release and the phone seems to be a lot more stable under 3/19. I will test audio this evening on my way home from work and report back.

If this fixes it, then it appears the release is fine but the CM kernel is problematic.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nakedninja42:
Did a clean install of 3/19, I was able to stream with no issues for the last couple hours via Bluetooth using Play Music

Edit: I'm on stock kernel w/ stock settings...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] spectrumfox:
The skipping/stuttering issue when pressing an onscreen command also happens with Task's Underwear kernel. So it's not just the kernel, something else is wrong.

---------- Post added at 07:21 PM ---------- Previous post was at 07:20 PM ----------

Try navigating around the phone, pressing and scrolling stuff. Change some options here or there, open Google Maps and search for something all while the music is playing and you will probably see what I mean.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nakedninja42:
After I posted earlier, I was streaming to my Bluetooth speaker using Play Music. During that time I was going in and out of tapatalk, falcon, Google + and few other things. I would put then phone down for a few minutes and then turn screen on and didn't happen. I would hammer the power button sometimes on/off to make it stutter...

Fwiw, I had the issue a couple days ago so I know what you are talking about. I flashed another ROM this morning cause 3/18 was not running well for me. I decided after half a day to go back to CM. I was streaming to my headset earlier as play store restored my apps. Above was my second test. I will keep messing with my phone and see if I can reproduce...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gleonard3:
Anyone got a copy of 3-13 they can share? I need a daily driver with no stuttering sound issues, and it looks like that build is the ticket. Seems the archives don't go back that far.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BuBbLeFIZzY:
I think they're talking about when playing from the phone speaker. Cause I dont have a problem with 'streaming'. Just playing from the phone skips. Which I already resolved myself.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eAiur:
The earliest I have is 3-14, want it?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gleonard3:
Sure, I'll take it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eAiur:
http://dl.dropbox.com/u/27313466/cm-10.1-20130314-NIGHTLY-d2att.zip
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jointedman:
http://goo.im/devs/cm/d2att/nightly
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
I get better battery life with the old kernel. Why is that?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
The latest kernel was released 2-3 back, it will take time for the kernel to evolve over the period of time. Give dev's some time to settle down
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Probably because the new kernel doesn't hot plug. Both cores are always on. Perhaps they'll change that one day.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gleonard3:
Yeah, I tried that before I asked but the link to 3/13 doesn't work. Presumably nothing older works either.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blehq:
I flashed the 3/11 I downloaded from goomanager last night... So yes it works ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gleonard3:
Did you try the version I asked for, 3/13? Whatever it's downloading is unusable. I'd still like a copy if someone's got it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lfbmike:
http://get.cm/get/jenkins/22376/cm-10.1-20130313-NIGHTLY-d2att.zip

give that a shot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xiphosurus:
Hey guys, I noticed that if you turn off System settings > Sound > Touch Sounds, all the stuttering issues go away!

Edit: As you can guess, turning off the lock screen sound also prevents stuttering when locking/unlocking screen.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blehq:
No same problem... Could not use 3/13 so I got the next best thing... I guess 3/12 build failed so i flashed 3/11 instead and everything works just fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] funkdoobi:
anyone have any clue why some APK's aren't compatible to download from the play store?

trying to grab, https://play.google.com/store/apps/...lt#?t=W251bGwsMSwxLDEsImNvbS5qYXdib25lLnVwIl0.

it wont let me download it on any of my CM10 devices (s3 and nexus7).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
I think this might be coincidence. I already had this setting off and it still stutters. Also the power button stuttering is intermittent. Finally, the stuttering that happens when I start streaming music goes away if I pause Pandora long enough. It's almost like the same effect as buffering the sound.

---------- Post added at 12:21 AM ---------- Previous post was at 12:15 AM ----------

Try 10.1? Seems to work for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ysandhu:
Wifi tether

Hello everyone,

I am coming back to this forum after 2 months. Just a simple question,, Is wifi tether working in latest nightly..

Please don't flame me for asking this stupid question ? last time i used nightly wifi tether was not working and i don't know any place where i can check what is still not working in nightly.

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sbddude:
Did you change your LCD density setting? Try using LCD Density Modder pro to install the "patched" play store. Fixed it for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
Yes
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] maxiimida:
Just flashed latest nightly with no other zips. It keeps rebooting every five minutes or so. Anyone else having this issue?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pixbuf:
Yup. It stopped after a while but it's still a bit unstable.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ganjah:
Yeah, it feels like we've been going backwards for the last week after really getting stable in the prior week.

No permanent solution to turning off LTE in the latest builds, which is a fairly enormous deal for battery life.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BuBbLeFIZzY:
Try installing aosp KT updated 3.4kernel after you boot stock. I had the phone reboot every time I try to get in an app and back out and running a different kernal seems to make it stop. Everything works for me so far. Havent tested bt streaming though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xiphosurus:
Turning off "Screen Lock Sound" eliminated this stutter during locking/unlocking screen for me. Does doing that help you?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] patthe:
Last few update my phone freeze once in a while 3 time today. Freeze screen stay on and i can see it freeze as clock stop and no other option to reboot? Anybody else?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
million bucks says if you just search really quick or just read the last couple of pages you will know if anyone else is experiencing this dude.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Aqua1ung:
Yep, I'm getting freezes and SODs galore with the latest nightlies. Not a happy camper.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sbddude:
Clean install on 3/13 nightly seems to be running well for me, much better than M1 from a month ago. (I went back to CM10.0 M2 in the meantime) CRT animation no longer freezing, tethering working, seems smooth and fast overall.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Hmmm... You must be new here. Its alright. You'll learn I'm sure. But either way. You mentioned freezing. Well. There have been many reports about freezing in quite a few situations here in this very thread since the release of the 3.4 kernel integration. That should have been your first clue dude.

Now read my post again and then evaluate which one of our posts is useless. If you don't like to read that's fine. But don't take it so personally when I mention the obvious to you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] moose&beer:
it has been mentioned multiple times in the past 5 or more pages, if you read through them more carefully.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BuBbLeFIZzY:
Use KT aosp new kernel. It will stop.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] oka1:
from the moderator

Why is it That every so often..... some people come in here and argue or derail the thread by posting personal or argumentative comments toward others in a personal nature

......... THIS IS A DEVELOPMENT THREAD........ LEARN TO SEARCH AND READ(this is a must)....... post respectfully post on topic....... or do not post......... simple.........

......... If you do not like this Rom or any other.......... then make your own......... if you can't then, try to be knowledge enough to post on topic and coherently......... Remember, it is YOUR RESPONSIBILITY to manage the risk YOU take when flashing custom roms...... anyone who helps you along the way should be thanked for that help they provide.

Thread has been Cleaned,

....... Thanks ~~~ oka1 .
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
Yeah, I also already had that setting off, and I still have stutter triggered by power button, home button, starting apps, etc.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] huladaddy:
Being a development thread, do CM developers actually read this?

If so, I would like to suggest that the power-off animation (which I love) should use the current brightness settings. Presently, I believe it uses 100% brightness. It can be a bit jolting turning off the phone after reading in bed with the brightness set to -50% (using lux app).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
Just to add to the pile, I flashed the nightly, and in about 30 minutes got a BSOD. I haven't gotten another today.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] phositadc:
Can you give link for cm10.0 m2? I don't see it on goo.im.

Sent from my GT-I8190
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sNoxious:
It's under CM/d2att/snapshot.

Sent from my Samsung Galaxy S III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 9umis:
Hi,

First of all, fantastic job with this recent build. I had problem with clock but after clearing cache and data of the clock every think is fine.

There are minor things that came to my mind while using cm10.1 nightly 3/13.

1. I noticed that I can't switch off the vibration for the keyboard. It works for other buttons but for keyboard not.

2. Battery drainage is pretty fast comparing with the stock.

Beside these, other things work well.

That's my 1post so sorry in advance.

|============|

SGH-I747

->stock --> cm10.1 nightly 3/13
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] maladju:
1- settings > language and input > keyboard settings (slider tile on right) > uncheck vibrate on keypress.

2- battery drain was discussed, seems to be related to the kernel upgrade. They have not optimized it yet, but be patient. It'll rock when they do. In the mean time, you can check other kernels to see if they are to your liking.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
Is there a way to make the menu and back key lights to stay on all the time? I hate it when I have to touch the screen so the lights can come back.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chris_barsoum:
+1

Sent from my I747 running cm10.1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bxsteve31:
camera preview

hey guys. i have a question and im posting here because i dont know if this is a CM10 glitch or a feature or a general android glitch. and frankly i dont even know what terms to use to search. so here it goes.

i pull up the camera app. point at what i want to take a picture of and i obviously see what im pointed at. BUT after i take the picture , the picture shows more area than what i originally saw on the screen.

glitch? feature that i may have messed with accidentally?

thank you.