yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
I've search around a bit and can't seem to find anything on this.

I've got WiFi configured to always stay on during sleep. I also have several Tasker profiles turning WiFi on or off based on which cell towers I'm connected to (home, work, whereever else). If I leave my phone on my desk at work and come back several minutes later, I find the phone in a state where WiFi has disconnected from the network, but Tasker hasn't turned WiFi off, so I don't think Tasker has anything to do with it. I find that I have to go manually reselect the WiFi network because it was avoided due to poor connectivity. I'm 20 feet from the router on the other side of the room. What's interesting is that I have the 'Avoid poor connections' setting disabled.

My theory is that the advanced WiFi settings are being ignored for some reason. WiFi is turning off when the device sleeps and it's ignoring "poor connections" even though it is configured alternatively in both cases. I am on the 3/17 nightly with 3/01 gapps and the stock kernel. Am I missing something? Has anybody else seen this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jpstiehl:
My build to share

https://www.dropbox.com/s/w1zlpvaqa6b3iiu/cm-10.1-20130326-UNOFFICIAL-d2att.zip

Please don't waste your time or mine if something goes wrong. As with anything that you flash on your phone do so at your own risk. :D

I am running this build currently. It's a build that's synced as of (Navring: Fix shortcut for uninstalled app (android_frameworks_base)) :D

I claim no development rights or otherwise claim that I had anything to do with the process of development. I simply built the ROM on my own. :D

Having said that, flash away and enjoy. Oh and how about a thanks? ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Why don't you try the Slim 2.5 build (it has the 3.0 kernel like the CM 17th build) to see if WiFi behaves any better. It is a very solid build that has nothing wrong with it that I can find.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ganjah:
Headphones Buzzing Issue

I disagree that the buzzing is a groundloop hum. I get the buzzing on 3/17 without the device being plugged in. I also experienced the same thing on the newer kernel from any of the newest nightlies. There is also a fair amount of static, not just buzzing, in the background when playing or when not playing. The static is present from directly after the phone boots to anytime playing or on a voice call or Skype session, or even when not doing any of those things.

Edit: the only time in the past that this presented itself and resolved itself was when Apollo was first included as the default music player in CM builds for this device, sometime around November of 2012 (I think). At that time, Apollo would experience the hum/buzz/static during playback and in between tracks, but Winamp would not. Seems pretty conclusively not a ground loop interference/hum issue.

I actually noticed this and mentioned it four or five months ago, but I don't think it was ever resolved or even acknowledged because most people either don't have high efficiency IEMs, don't listen closely enough, or don't care. Me, I'm an audiophile, so my Creative Zen and Sansa Fuze w/ Rockbox are never far away when wanting to listen to awesome FLAC recordings. But, I'd really love to not need them and just do everything from the phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
Because I want to figure out why this is the way it is on CM10.1? I'm not trying to be a ****, but I don't really think "try another ROM" is a good answer. That's like asking a mechanic why your car makes that noise that it didn't make 2 weeks ago when you rev the engine and having him tell you to get a hybrid because they are quieter.

I'm trying to solve this problem. It would be easier to solve if other people had experienced it as well. Hence my post.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BuBbLeFIZzY:
I was hoping someone post one :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] johnhazelwood:
Did you try uninstalling Tasker? That would be my first step to see if it's causing my problem. Also bad car analogy, as 1) a mechanic would love billing you for hours of troubleshooting, and 2) he'd be working on a non production test car which will have known issues.

On a side note: You could try out a hybrid, as that might solve the problem :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
I thought of doing that but Tasker isn't touching the WiFi when it's turning off and it worked on earlier nightlies. I'll have to run some further tests. This might be a full wipe situation with some data restore. It's been a while. Dirty flashing for mooonths.

I see your point on the car analogy, but you do agree that "try another ROM" is probably not a real solution, yea?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Point was to see if you had the same problem on another ROM. But since you added that you've been dirty flashing for months... I'd say, bingo!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
New nightly is out with pie feature. Enjoy guys
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
Pie controls are only for devices that use an on-screen nav-bar like the Nexus devices.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pcshano:
Screen is still flickering on 3/27 :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
No flickering for me but battery drain is still there
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] energyracing:
3/27:

Battery drains immensely, phone crashed after an hour. Back to 3/13 for me. They'll figure it out soon. That or they might have to ditch this kernel.:crying:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] spectrumfox:
Does anyone know of any substitute kernels that make 3/27 a little more accessible?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pcshano:
Battery is okay for me...

However when I play music or game... The same flickering sound every time I touch the screen
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
I miss the 3.0 kernel. :mad:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BuBbLeFIZzY:
http://xdaforums.com/showthread.php?t=1756776

Up the voltage by 10 if the lowest starts at 850

Make sure you download the right one. Which is asop something.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VashTS:
Anyone else have or know about cell data not working? Everything else is fine. Calls/text/WiFi is not a problem. I'm on 03/27 but I rolled back to 03/02 with no success. Been flashing nightly every week or so. Was on 03/23 working great just noticed this issue today.

Solved it. Set APN to default, working fine now. I notice battery drain is increased on my end too.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] spectrumfox:
I've not had any crashing or audio issues with 3/27 yet. The only thing I'm noticing is the battery drain. Even with Google Now enabled, it is falling a lot faster than it normally does.

EDIT: Whoops, spoke too soon. System UI process crashed repeatedly awhile ago and I needed to reboot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
Fwiw, KT kernel on 0327 did not stutter for me on bluetooth streaming, but stock did.

Also with KT kernel, gone are all the audio hiccups when using the phone.

Maybe battery life is better too, will see, and maybe no eventual freeze up with the KT kernel?

PS, I prefer stock. Can the cm team hire KT? Does he smell bad or something?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 9umis:
I have discover some issues regarding sound+Bluetooth +skype in 3/17 and 3/21.

Concretely, while using in the car Bluetooth + Skype. I can't hear in the speakers of the car the voice of person calling me. Seems like doesn't won't to go thru Bluetooth. And is using phone build speaker and mic. I don't think is a problem of Skype.

BTW. Bluetooth + Apollo works fine.

I will try new nightly to see what happens.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
I just got a system ui death. Had to restart nova. Swype was also freezing up, so this instability may just be the latest code, not the kernel specifically. Joy.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] howtomen:
Are all of u dirty flashing or clean flashing? Just curious... If its dirty flashing for the love of god dont complain.... Never report anything with dirty flash

sgh-i747(d2att)(sgs3) on latest cm10.1 or ultimatum
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
Dirty. And complaining. I'll work at removing emotional reactions from future posts about issues. I did however post in the last couple of days to see if anyone was seeing these issues gone with a clean flash, and perceived that latest daily was more stable than 0317. Posts I find state that clean flash has same problems with bluetooth audio, stability, and battery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pcshano:
i only dirty flashed once... and never done it again

so yeah.. there's still flickering sounds here and there when play certain games and while playing music
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xiphosurus:
sorry but i'm atheist. also, i think its perfectly fine to dirty flash nightly builds, and to discuss the new problems here. where else would be a better place for that?? it is ridiculous to expect everyone to spend the time to clean flash every day on their daily driver. the only time you are expected to clean flash is to confirm and submit a bug report on the m1 builds.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] howtomen:
I flash dirty all the time and my stuff works but dirty flashing leaves behind crap... So bugs can arise from that therefore dirty flashing and reporting bugs is useless in a thread as the possibilities are endless... As for these issues this weekend ill have to update to latest as im on 3/17 but ill see if i can reproduce after a clean flash...

sgh-i747(d2att)(sgs3) on latest cm10.1 or ultimatum

---------- Post added at 11:03 PM ---------- Previous post was at 11:02 PM ----------

Through bt or through headphones?

sgh-i747(d2att)(sgs3) on latest cm10.1 or ultimatum
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] maxrdlf95:
Thanksf or all the changes and for that Math Fixing ktoonzes :good:

So that let me a question, all the time if you said that 2106 was about 1800 so we were having lower frequencies ??? Ex I i Were on 1512 it was like 1200? or no just on higher freqs??

ANd I have a problem

I Installed all ok I configured it but I can't restart my phone :S When I restart it, it stuck and bootanimation well not like that

Bootanimation - blackscreen - bootanimation and like that.. why it's that happening :( I never had any trouble.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] howtomen:
Wrong thread.... But no the lower freq were ok... And the reboots is cuz u have to clear superuser data...

sgh-i747(d2att)(sgs3) on latest cm10.1 or ultimatum
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] benjihana:
3/27 has been giving me all kinds of nightmares. I even went back to clean wipe and install from scratch, and now anytime I'm booting it is booting to a black screen on initial boot... Reboot will get me the Google account setup screen... anyone else experiencing this? No luck with stock kernel or task's underwear.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BAM1789:
I'm fine on 3.27... well besides the normal 3.4 issues.. stock cm kernel, boots fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] spectrumfox:
This might be a silly question, but I can't seem to find the answer anywhere.

What exactly does the CyanogenMod Upgrade script do? I read it formats /system and backs up gapps, then restores, but does it remove all of your settings as well? Like does it remove icon and widget placements, apps, settings, and everything you set up after the ROM is installed?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lordmorphous:
no it doesn't. setting remain intact.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] spectrumfox:
Excellent. So formatting /system doesn't remove personal settings and installed apps? Or does the CyanogenMod script work some black magic?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lordmorphous:
installed apps and settings are stored in /data
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
on 03/27, KT kernel (this is the first time I've stayed on KT to analyze if it might alleviate the stock issues)

1. I'm pretty convinced that KT kernel "resolves" any BT streaming issues, initial stutter and usage stutter are gone for two days of use for me.

2. 8 hrs with KT kernel and I got a System UI death, restart Nova. All is fine

3. 20 hrs with KT kernel, BSOD.

Seems to me KT kernel nails the audio problem and has a slight effect on the slow death of stock?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] benjihana:
Hmm... which is frustrating to me, because I am now getting random reboots running 3/21 and the task UW kernel. Just completely random.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
try playing around with different governors and schedulers.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] M0D1441:
Yup, checks to make sure you're flashing the image for the right device, backs up gapps, formats system, installs new system, symlinks, sets permissions, restores gapps, then installs the new kernal.

I just checked the update-script :silly:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] benjihana:
I will, thanks.

---------- Post added at 11:25 AM ---------- Previous post was at 11:17 AM ----------

Not to post too much today - but is anyone else using Apex Launcher with the new kernel iterations? I think my troubles might be stemming from my launcher choice.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xiphosurus:
I have Cerberus (the anti-theft app) installed as a system app. But it survives every dirty flash. Any idea how it survives if CM formats system?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] erbsmokah:
I find it funny how people say dirty flashing is bad but if you follow cyanogen on google+ they say its fine.

I have been dirty flashing since cm10, even dirty flashed from 10 to 10.1 and have never had any issues other than the common ROM related ones that everyone experiences.

I think some people just dont understand what they are doing or why they are doing it most of the time. Other times they just have a lemon phone.. After all not every sgs3 is the same.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] M0D1441:
It runs a backup script, not strictly a gapps script, I wish I could find that so I could see what exactly it does, but my guess is that it backs up anything foreign apps that aren't detected in the new nightlies /system to /tmp
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jpstiehl:
I do use Apex and have been having a good bit of issues randomly though with it or an app crashing. Having said that I have not performed a full wipe nor have I tried using Trebuchet or another launcher to see if those issues go away. Apex has always been a rock for me though. I'll reserve my finger pointing until I get a full wipe in.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] benjihana:
Not sure if that was it. I'm logcatting my output now to try to catch the reboot reason, but I don't know if it will write before it reboots.

It's just been so random. Now that I have my phone plugged in, it hasn't reboot once, but I also cleared battery stats. I really have no idea what is causing my reboots. Are you getting reboots or just issues? The new kernel could just be getting funky on your end, mine is starting to sound like a non rom/kernel related issue, though, but I'm not sure yet.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] romracer:
Its backuptool.sh in /system/bin in the zip file. The updater-script removes it from the running ROM once its done, so you can't see it on your phone.

It essentially runs the scripts in /system/addon.d which are just BASH scripts with a few specifics on their semantics. If a system-installed app survives a flash of a new nightly, its likely got a script in addon.d or its doing something "special" (on boot listener, init script, etc).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
There's no such thing as be able to wipe battery stats on this device. Choosing that option does absolutely nothing. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] loonieryan:
+1

Same here. I use TWRP and follow these steps every single time I flash a nightly:

1. Wipe cache

2. Wipe dalvik cache

3. Wipe system

4. Add nightly CM 10.1 zip to flash queue

5. Add Gapps to flash queue

6. Flash

7. Reboot system
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] benjihana:
Well... sh$#. At least I know that now. WTF phone? GO TO YOUR HOME
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
You could even skip steps 3 and 5 since flashing CM10.1 zips already do those things for you (pretty sure). It backs up your gapps, wipes system, flashes new system, restores gapps.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] erbsmokah:
I only flash the rom. No wipes no reflashing gapps.

I only do the dalvik wipes if i flash a different kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
If they are then they might also apply to Nova.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BuBbLeFIZzY:
On03-27-13 the skipping while opening apps and such is gone, but it comes back eventually if I dont reboot for a day. Only way to get rid of it is to turn touch sound off. This is the only issue I have so far. Everything else is fine. No more screen freeze or black screen. Which usually happens when I turn the phone on from the lock screen to check my messages and dont turn it off.

Oh and in Apollo the add to playlist option is gone. I can go and hold the song file and save it but it ends up saving every single song I have in it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] benjihana:
Even reverting to old nandroids was messing things up. Not sure if I corrupted something, but I put one nandroid on my external, moved all my DCIM/Download /sdcard stuff to external, pulled the external, wiped the WHOLE thing (minus recovery), but wiped /system /data /cache /sdcard, etc., and now it's working (albeit on a 3/4 build). Afraid to update until the new kernel is worked out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] howtomen:
Dirty flashing isnt bad but if u get issues dont complain with a dirty flash...

sgh-i747(d2att)(sgs3) on latest cm10.1 or ultimatum
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
Ok, I've now had two bad initial stuttering issues with streaming bluetooth and KT kernel, so apparently KT kernel does not fix the issue, or does not completely fix the issue. Most likely, it was just odd coincidence that the first three times I ever tried with KT kernel it worked, and then suddenly did not.

It seems the phone is slightly more stable with KT kernel, but at this point, I'm not sure there are any advantages to it over stock. Maybe battery life.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xiphosurus:
It's fine to discuss here about issues after dirty flash. You don't make the rules.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blackangel104:
Uh oh ...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] phositadc:
Somebody got pwn3d!!!1!1!!

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] erbsmokah:
If you have issues you shouldnt complain period. This would also be the wrong place to do it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] howtomen:
And you do... Dont be an idiot its common knowledge that if u have issues after dirty flashing theres to many variables to take into consideration so complaining or discussing is useless this isnt a general thread tho some of u people would treat it like it is... Its still under development and discussing issues after dirty flashing is useless... U guys wonder why there's no devs around here... Because the users dont have the decency to keep the thread on topic and help any development... Everbody in this thread is like i flashed a nightly and theres bugs wth... And well seems like most of u dont even know the basics of rom development or much less how to help.

sgh-i747(d2att)(sgs3) on latest cm10.1 or ultimatum
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] erbsmokah:
Its just a rom thread in the development section at XDA. The cyanogenmod team has their own dev forums and thier own bug reporting system. Thats why there are no devs around.

And I might point out that it is you and people like you who initiate debates such as this one. Otherwise it would have been left as one post of me stating that I dirty flash. Which by the way is encouraged by the devs.

Also try to keep in mind that this is not a bug reporting thread. There is a system in place to report bugs to the devs and its the only one they care about.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rani9990:
It's not necessarily encouraged, but even devs do it all the time. One of the devs I know has dirty flashed all the way from CM9! And he doesn't have issues, except the known ones.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] spectrumfox:
Yowza. That's one brave soul.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] erbsmokah:
I would consider them saying that its ok to dirty flash on google+ encouragement. But its not like they pressure you into it. I just dont understand why some people make such a big deal about wiping when they dont even know why. They just assume its because there is "left over" data when there isnt.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pcshano:
none.. lol just play music through apollo without anything
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] howtomen:
There is left over data dude... Settings preferences and stuff left in /data partition.... Bro im no noob;) i know what im talking about dirty flashing is ok just dont expect support... Because theres somethings that are fixed when wiping... Just sayin... Ive worked with roms before trust me... Wiping sometimes just has to be done

sgh-i747(d2att)(sgs3) on latest cm10.1 or ultimatum
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xiphosurus:
The typical user will NOT have the time to do a clean flash of the nightlies. But they will still want to check with other users if the new bugs could have a work around, or could perhaps be due to a dirty flash. This thread is not meant for dev discussion, it is for the devs to see the general response of the typical user. So where else do you think uesrs should discuss new bugs? The devs already have a forum where only they can post ==> http://xdaforums.com/forumdisplay.php?f=2056 So please stop being a self-righteous moron and telling us what to do.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zelendel:
Well then the typical user should not be flashing alpha software that could brick their device.

He is right. Posting bugs without doing a full wipe first is just clogging up the thread with extra useless posts.

This thread as well as any in the Development forum are for developers to talk. This is a developers site. Plain and simple.

Wayne Tech S-III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] howtomen:
I think people assume since my name doesnt have any dev tag under it i dont do any deving. Shame really... General is for discussion and development is for development or bug post with useful info.

sgh-i747(d2att)(sgs3) on latest cm10.1 or ultimatum
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] spectrumfox:
I can understand why devs would prefer to get bug reports from people who have done a clean wipe. However, I do find reports from people who have upgraded from prior nightlies to be very beneficial from a user experience standpoint. It gives me a general idea of how stable the build is and what to expect.