yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] juancaperez2000:
Actually some posts above mention that, i check n yes but i can not make it stick

---------- Post added at 08:03 AM ---------- Previous post was at 08:00 AM ----------

Not sure uf just me but screen flickering is really bad on N13, i checked at ATT version and look like they have it too
[Verizon Samsung Galaxy S III] onpoint10101:
I installed CM10 builds on my VZ gs3. Everything works great, except for when I go to install Swift Key, when it tries to load the Language & Input selection up it crashes every time. I installed the latest one for 9-13 from: CyanogenMod Downloads The exact error i get is "Unfortunately, settings has stopped." This appears when i select "Enable Swiftkey 3" (Step 2). The rom seems to work perfectly, but does anyone know why this is crashing? Is this a known bug with CM10? Any help would be appreciated.
[Verizon Samsung Galaxy S III] lxetuo:
I think this is an issue with the latest SwiftKey update. I got around that by going to Settings -> Language & input and checking SwiftKey 3 there. After doing that, go back to the SwiftKey app and you should be able to continue the setup.
[Verizon Samsung Galaxy S III] Zacharybinx34:
Is these needed even anymore since the M1 release?
[Verizon Samsung Galaxy S III] Brian Gove:
That's been happening for quite a few nightlies now. It does it with the touch pal keyboard also.
[Verizon Samsung Galaxy S III] Droosh:
I've done my best to avoid commenting on this issue as it has been debated way too much on this thread and now there is a thread dedicated to this very topic.

That said I think there is a lot of bad advice being given here that is making this debate recirculate so I will again list what has worked for me on every nightly and is much simpler than clean flashing. I have not needed to clean flash once since the original nightly release.

Start from an official Samsung firmware, rather than a pre-rooted firmware like root66. Flash through Odin updated radios if desired, root, unlock bootloader. Nandroid this base build. Then for every nightly just simply follow these steps:

1. Wipe cache, dalvik, AND SYSTEM.

Yes, I consider wiping system as a key part to dirty flashing as many recoveries or poorly built ROMs fail to thoroughly wipe the full system partition as part of the routine.

2. In same recovery session (I like TWRP) install ROM, g-apps (I use 8/31 formula84), other mods - optional (I usually flash the 1.62 AOSP camera mod by the Unknown and LeanKernel)

3. Boot.

4. Reboot (to get data back if needed or to smooth out other issues.)

5. Sometimes bugs are easily fixed by clearing and redownloading AGPS data, maps cache, gallery cache, checking clocks, governors and I/O (I use interactive and SIO)

6. If all else fails I would then recommend clean flashing before posting issues as maybe you have some app conflict.

Happy Flashing!
[Verizon Samsung Galaxy S III] Fixter:
I really need this to get more stable. Not because I think CM10 is too bad. But because I want to get this touchwiz out of the phone bad! And I need something that works ALWAYS and that I can rely on. This thing is sloooooow. Compared to my old Galaxy Nexus the difference is enormous.
[Verizon Samsung Galaxy S III] NegativeOne:
I think the problem may be on your end. I am STILL using the original nightly (because I really don't have much time to experiment right now. Lots of obligations leave me unwilling to have an unstable phone) and I have no serious problems with performance, data, or battery.

Of course YMMV, but I don't think it's fair to say that it's unstable. From what I hear, it has only gotten better since the build I have, overall, aside from a few hiccups.
[Verizon Samsung Galaxy S III] Fixter:
If it was stable it wouldn't be a nightly which is not even close to a RC. Which is not even close to a STABLE release. The problem is not in my end. I know what I'm talking about. I'm sure a lot of people also do. I've had CM on my Android devices since the G1. Those hicups that you're talking about can be the reason I skip a meeting or miss a phone call or drop a call on an important client.

PS: Don't confuse my eagerness to use CM10 with thinking I'm talking trash about them. I love this thing and I just want it to get better! Just impatient as can be.
[Verizon Samsung Galaxy S III] Droosh:
I've disagree. Many CM nightlies are more stable than what other ROMs call RC or stable. Heck, they can be more stable than the OEM official firmware.

That said CM10 nightlies are about perfect on my G-Nex. As of these last few nightlies, I have few complaints on this device either. Video recording volume is my only bother right now.
[Verizon Samsung Galaxy S III] Brian Gove:
I haven't experienced a single data drop, messed up phone call or anything of the like. The only bugs I'm experiencing are media related: I still get the flicker(just have to tick the HW overlays in developer options each boot) and almost no volume when recording videos). And the keyboard settings bug mentioned a post or three up.

Other than that I'm running smooth on the 9/12 nightly.
[Verizon Samsung Galaxy S III] jdommer:
I use native tethering just fine with no additional file installs or anything on M1.
[Verizon Samsung Galaxy S III] apacseven:
I have to agree with the other poster that suggested it may be on your end, you have to at least be willing to accept this as a possibility. Me, and plenty of other people using these nightlies all agree that even since the very first release, its been very fast. Also, any stability problems like SOD that may have been present early on seem to be all but gone now. This is the fastest ROM I have used so far for this device.
[Verizon Samsung Galaxy S III] iofthestorm:
It sounds like he's just talking about Touchwiz being slow, not CM10. If I'm not mistaken he hasn't actually tried CM10 because people report bugs.

Also FYI guy from a couple pages ago, tapatalk does have a search feature, so please use it! And if you're not near a computer you shouldn't be flashing anyway, because if you screw up you're stuck. So no reason to post questions which you yourself admit are dumb.
[Verizon Samsung Galaxy S III] apacseven:
Ah yes I've reread his post and this is clear to me now, my aplogies Fixter.
[Verizon Samsung Galaxy S III] NegativeOne:
Stability is incidental. You can have a perfectly stable nightly build. FYI - it's not like they are like "OK guys, let's make a special STABLE build tomorrow, enough messing around". They just promote a nightly to a monthly because it happens to be stable.

If there are people here who have no problems, and you are experiencing problems, more than likely, it's on your end. You can refute that all you want, or you can accept it, and try to seek help from others to figure out what you're doing wrong. It's your choice.
[Verizon Samsung Galaxy S III] guthrien:
M1 is just stunning. I didn't think CM10 is where my stable rom would be though a lot are real close with special builds. This is absolutely an everyday, totally stable build. Congratulations and a hearty thanks to all involved. Running this on such a beast of a phone is a pleasure.
[Verizon Samsung Galaxy S III] Zacharybinx34:
So why does the original post still say that we need to install that? Is it just outdated?
[Verizon Samsung Galaxy S III] jmill75:
What about in call volume, still jacked up? I haven't downloaded the last cpl nightlies because the volume bug has been present for a while. Would love to come back to CM10.
[Verizon Samsung Galaxy S III] onpoint10101:
thanx works fine now:good:
[Verizon Samsung Galaxy S III] mustbepbs:
This is what I want to hear. I've been following people's reactions to M1 since it was released and haven't jumped yet. Currently on Clean ROM and want to get back to CM ASAP.

Also your signature is funny: Galaxy Nexus 7? ;)
[Verizon Samsung Galaxy S III] alee:
9/13 release flickers very badly. It's perceptible in every app, not just on the home screen.

Rolling back to the 9/12 unofficial by cgulliver which was a mid-day roll-up of what's in 9/13.
[Verizon Samsung Galaxy S III] PerCompLLC:
Check "Disable HW overlays" in Developer options and the flicker goes away. It'll be fixed by the CM team eventually.
[Verizon Samsung Galaxy S III] coldhardtruth:
Anyone get NFL mobile to work on M1?
[Verizon Samsung Galaxy S III] Droosh:
9-13 has NO flicker in any app for me. Must be on your end.

FYI- I suggest trying to fix without checking that disable box. Doing so disables the project butter enhancements which is a main benefit of CM10.
[Verizon Samsung Galaxy S III] seang:
M1 is really nice. no major issues after about 18 hours. good call quality.

I did a clean install, only issue i have is with the flicker. disabling the HW overlay fixes it as usual.
[Verizon Samsung Galaxy S III] evandena:
My battery life seems poor with M1.

Anyone having good luck with a different custom kernel and CM10?
[Verizon Samsung Galaxy S III] jmill75:
I asked earlier but no response....So is the volume bug fixed, meaning do yo still have to turn it up before you can turn it down all the way. Really loud on lowest setting.
[Verizon Samsung Galaxy S III] juancaperez2000:
Agree with u a lot of flickerin
[Verizon Samsung Galaxy S III] alee:
Interesting. Going back to an older nandroid for now until I have some time to debug it. Could be auto backlight as well.
[Verizon Samsung Galaxy S III] zxsix:
I have had that on every build. On 9/12 build I did a clean install, including formatting system partition. On initial startup volume could be adjusted other than slider won't go all the way down to 0 and echo was gone.

After a reboot, it is back to loud volume with non functional slider.
[Verizon Samsung Galaxy S III] jmill75:
Ugghhh Ok thanks. I use phone for work and the loud volume is a pain :) . Oh well I'm sure it will be fixed soon.

Thanks
[Verizon Samsung Galaxy S III] drbveb88:
I uninstalled it then reinstalled it. Worked perfectly after that.

I use my backup pro so I don't think its confined to tibu restores.
[Verizon Samsung Galaxy S III] kls629:
i noticed on the last nightly, when downloading an app, it automatically adds a shortcut to the homescreen. never happened before, is this a setting that can be changed?
[Verizon Samsung Galaxy S III] chetqwerty:
I have like ten voicemails waiting to be deleted in my box because of this! Obviously i do it when i get home from the landline nevertheless still a hassle.

I'm thinking this is caused by whatever method they used to get rid of the echo. Hard to believe this doesn't effect more people.
[Verizon Samsung Galaxy S III] Nightwind Hawk:
In the market settings, disable "Automatically add widgets"
[Verizon Samsung Galaxy S III] apacseven:
Thats an option in the play store, been that way for a while now. Not sure why you didnt experience it until now. Go into play store settings to turn it off.
[Verizon Samsung Galaxy S III] coldhardtruth:
Attaching files in gmail not working on M1. Can someone please confirm this for me.
[Verizon Samsung Galaxy S III] PerCompLLC:
Doesn't work for me on the latest nightly either for me. Just tested sending a message to myself and the attachment was dropped.
[Verizon Samsung Galaxy S III] ugachris:
I have not had this problem at all, and I know it would be an issue because I have to press 1 to receive a call from Google Voice. Did you clean or dirty flash? Which nightly? As previously stated, what I do is: reboot into recovery, wipe data/factory reset, wipe cache, wipe dalvik cache, format /system, flash the latest nightly, flash gapps, fix permissions, and reboot.
[Verizon Samsung Galaxy S III] tdperry:
Correct, it does. Just press the menu button and in the lower left corner you see "search". Not being familiar with the software being used can bite a person.

TAPPED in on my (now unlocked bootloader) Verizon S3

---------- Post added at 11:36 AM ---------- Previous post was at 11:32 AM ----------

Not a ROM problem. You need to go into Play Store settings and turn that option off.

TAPPED in on my (now unlocked bootloader) Verizon S3
[Verizon Samsung Galaxy S III] ruben8448:
I went to the latest nightly and I am still getting some major lag. It ran fine at first then I reboot it and it started happening
[Verizon Samsung Galaxy S III] NegativeOne:
One other user is complaining of this. Please post more descriptive information about the type of lag, when it happens, how long it persists, etc.
[Verizon Samsung Galaxy S III] ruben8448:
I notice a lag when swiping from screen to screen. It's a slight lag when it reaches the next screen. You can really notice the slow frame rate. When running an app it seems fine. Opening and closing the drawer also has slow frame rate including moving from screen to screen on the drawer. This problem is constant and does not go away.

When I disable HW overlay it gets a little bit better
[Verizon Samsung Galaxy S III] NegativeOne:
So you're only having problems with your launcher. Trebuchet? Try a different launcher please and report your results. Did you clean flash or dirty flash? Try to clear your data/cache for launcher.
[Verizon Samsung Galaxy S III] mastamoon:
I can see my live wallpaper, the Nexus one, stuttering and lagging almost all the time. On boot up you can really see the lag, once its settled in its pretty smooth, but if you just watch, you will see all the dots stutter every now and then.

Running on a caches wipe only from 9/12 to 9/13. Lag was on the clean 9/12 also. Not complaining just adding .02.
[Verizon Samsung Galaxy S III] ruben8448:
I tried it with trebuchet, apex, and nova. Apex and nova are worse. Trebuchet is not as bad. I clean install each one wiping everything and for the 9-13 build I reformatted the system as well
[Verizon Samsung Galaxy S III] Coop9:
I'm on 9/10 and do not have this issue. It would be a showstopper for me, but I've not seen this issue on any AOSP rom I've used.
[Verizon Samsung Galaxy S III] Dirty13ear:
Personally I really like the lean kernel...the last few releases have really improved my battery life with CM10...

http://rootzwiki.com/topic/32286-kernel-aosp-jb-leankernel-minimalistic-kernel-v014-beta-91212/
[Verizon Samsung Galaxy S III] djeddieone:
If your having problems I recommend you all to stick to the experimental build runs smooth for me data still drops but not as much as the nightlies. And if it does data drops it comes back on its own with having to reboot
[Verizon Samsung Galaxy S III] AlexDeGruven:
Did it still do it after a full wipe?
[Verizon Samsung Galaxy S III] evandena:
That's what I'm noticing too. With the nightlies for me, data would drop every minute or two and stay down for 15-20 sec. On the M1 build, it drops maybe once an hour, and is usually only down for 3-5 seconds.
[Verizon Samsung Galaxy S III] vdefender:
I have always had pretty bad screen flickering, and every time I disable HW overlays it just makes everything super slow and laggy. So personally I prefer the flickering over laggy UI.
[Verizon Samsung Galaxy S III] mastamoon:
I haven't clean installed since 9/12 where it did stutter. Probably wont clean install until next week or something unless something comes up that it is necessary. Lag is manageable for me, nbd.
[Verizon Samsung Galaxy S III] littleneutrino:
Clean installed from M1 to N9/13

Flicker is worse now. screen off animation happens, and then the screen turns back on for a fraction of a second and turns off.

Reception issues and data drops still present. other than that does not look like any of the issues i have experienced are fixed.
[Verizon Samsung Galaxy S III] ruben8448:
For the lag issue I'm having it is happening on the m1 version as well.

---------- Post added at 07:45 PM ---------- Previous post was at 07:38 PM ----------

Hmm I just switched the cpu govenor to interactive as apposed to on demand and the lag is gone.
[Verizon Samsung Galaxy S III] cgulliver:
Yeah but I have found that even LK has unpredictable issues with the velocity of the nightlies. May have to wait for a good stable to move to a custom kernel.
[Verizon Samsung Galaxy S III] Brian Gove:
I'm running leankernel v0.14 on 9/12 nightly with Nova as a launcher and I experience absolutely no lag switching screens/drawers/etc. I also have no data drops(If they do happen I don't notice them) but the screen flicker is still around. Disabling HW overlays takes care of the flicker but doesn't seem to add lag.

Lk v0.14 may or may not function well with the 9/13 release, usually he's good about making a quick update if there's conflicts. But I know for sure it plays nice with 9/12.
[Verizon Samsung Galaxy S III] Lastb0isct:
I'm still having issues with 3g/4g connectivity. When I first got my phone, before root/CM10 and on stock wiz, I was getting lightning fast 4g. Now I don't even get a 4g signal ever, in the exact same spot I was getting 4g before. I now get very low bars of 3g. The fastest thoroughput I get is ~2mbps, WEAK! Does anyone have suggestions on how to fix this issue? I have been doing dirty flashes for a while now and just did a clean flash (wiped data/cache/dalvik), which I thought would fix it, of the M-1 release.
[Verizon Samsung Galaxy S III] nnnnr14:
Goto system settings-more (under data usage) - mobile networks and make sure network mode is set to lte/cdma/evdo

-tapped from my cm10 ktoonsez kernel'd Galaxy s3
[Verizon Samsung Galaxy S III] Lastb0isct:
Wow, you're awesome. I knew that setting was there...I had checked it before as well...but rechecking it seems to have fixed it. The setting was on LTE/CDMA only, which is weird because that setting doesn't exist! haha. Either way, thanks for forcing me to do the obvious...
[Verizon Samsung Galaxy S III] TheBiles:
There's a replacement app that's better than NFL Mobile on the Themes and Apps board.
[Verizon Samsung Galaxy S III] Seirÿu:
I had the same issue last night when i went to 9.12 nightly.

M1 and 9.12 were the first builds i had any data issues with and then i realized the setting was set to LTE/CDMA, and when going into that option - neither LTE/CDMA/EvDo or CDMA/EvDo auto were checked. and as soon as i checked LTE/CDMA/EvDo my data hasn't had any issues at all... a couple of snags switching off wifi back to the carrier's network if in a low-medium 3g area but even that isn't too bad.
[Verizon Samsung Galaxy S III] Arekku:
Anyone have a fix for network going out EVERY FEW MINUTES?

Settings are set to LTE/CDMA/EVDO. I can barely stay connected for a few minutes.

I'm on the build from 8/16. Considering updating to a new Nightly but reading the Screen issues has me scared.
[Verizon Samsung Galaxy S III] Ratzinc:
Just try a new nightly and see if you have any problems.
[Verizon Samsung Galaxy S III] TheBiles:
That's build is hella old. Why would you even bother asking about a month-old build when everyone is trying to focus on current issues?

Sent from my Nexus 7
[Verizon Samsung Galaxy S III] coldhardtruth:
Agreed. It's worse than 9/7 was for sure
[Verizon Samsung Galaxy S III] sullivan1985:
In recovery, go to mounts and storage and select "format /system" in addidtion to the factory reset, cache, and dalvik. This will clear any trace of the old ROM. This cleared up many connection and GPS issues for me.

I still do experience 3G data drops but not nearly as often and before.

I flashed 9/11 and 9/13 this way and all is well! I will probably continue to flash like this until a CR or a stable is released.
[Verizon Samsung Galaxy S III] Brian Gove:
When flashing the flash usually formats the /system before it writes to it.

What's it called? I searched real quick and couldn't find anything.
[Verizon Samsung Galaxy S III] Byonik:
I had good results with lean kernel on M1, but I stayed with the native kernel on my last flash (9/12), and I'm seeing good results. Granted, I didn't use it much today, but this is still better than what I'm used to...
[Verizon Samsung Galaxy S III] wera750:
Usually being the key word. I've found that some ROMs don't format system.
[Verizon Samsung Galaxy S III] nnnnr14:
My phone wont boot it's stuck at the CyanogenMod animation and won't any further... what do I do?
[Verizon Samsung Galaxy S III] iofthestorm:
CM10's updater script does format system though. You can check yourself by opening up a zip file and looking at META-INF/com/google/android/updater-script. No need to inject uncertainty into things which can be easily verified. Code is code.
[Verizon Samsung Galaxy S III] Byonik:
I had the same problem on my last flash. Do a battery pull, then boot your custom recovery and re-flash the rom. You should be able to boot recovery by pressing power while holding volume-up and home (or is it vol down? always forget).

If that doesn't work, try a clean flash or restore a Nandroid backup.
[Verizon Samsung Galaxy S III] nnnnr14:
I couldn't boot into recovery for anything!
[Verizon Samsung Galaxy S III] NeoMagus:
just moved to 9-13, everything is working but so far noticeably more flickering with Disable HW overlays off than 9-10 which I just came from
[Verizon Samsung Galaxy S III] Brian Gove:
Pull the battery for a few seconds then put it back. Press and hold in this order, volume up, home and then power. Hold it till you get to recovery. It can be finicky sometimes if you hit power before the others or if you let go to soon.

Once you see some life in your phone you can release the power button but keep holding the other two just for good measure.
[Verizon Samsung Galaxy S III] manywelps:
I actually like doing a FULL wipe, then booting up and making sure everything's stable.

Then I advanced restore the data partition from the nandroid I made just before the wipe and check for stability. So far so good.
[Verizon Samsung Galaxy S III] nnnnr14:
Thanks guys for real. I had a flashback of my razr days..... But I got it into recovery and wiped EVERYTHING and now its runnign fine back on cm10! :cyclops:
[Verizon Samsung Galaxy S III] wera750:
Didn't think I singled out cm10 as the Rom that didn't format system. My bad.
[Verizon Samsung Galaxy S III] guthrien:
I haven't had a single problem with cm10 yet. Not even a flicker. Good call quality. Running the base kernel with good battery. I don't want to jinx myself but easily best cm build I've tried on phone.
[Verizon Samsung Galaxy S III] neh4pres:
Where is the changelog? Tried the link.. Just a recovery picture.

Does cm10. Have a sms dropdown now, like miui has?
[Verizon Samsung Galaxy S III] manywelps:
I'm going to run 9-13 around this afternoon and may post thoughts in the evening.

9-5 had it so I assume 9-13 does.
[Verizon Samsung Galaxy S III] sullivan1985:
I'm sorry. You're right. I meant /data.
[Verizon Samsung Galaxy S III] Lastb0isct:
My issue was fixed by just reselecting the network in settings-> more under data usage as was said before
[Verizon Samsung Galaxy S III] XDAholic:
While this is true most of the time, it is up to the author to include system formatting in his script.

Formatting the system partition manually is never a bad idea when flashing a ROM. Even if the script author includes it, no harm will come from doing it twice.

Formatting data on the other hand is pretty much a waste of time if you do a factory wipe prior to flashing. The full wipe formats the data and cache partitions already.
[Verizon Samsung Galaxy S III] abissel22:
My phone wont activate on any of the builds no matter how many reboots. Im currently trying m1 but its a no go. Anyone wanna help? Id apreciate it.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] Byonik:
I know. CM10 has stabilized so quickly. It's funny, I've been watching this flurry of activity the last few days on the leaked TW Jellybean threads, and I was tempted to try one again, but CM10 is a true DD at this point (well, for most of us), so I'm staying put. Been there, done that!
[Verizon Samsung Galaxy S III] seang:
what kind of wiping did you do?
[Verizon Samsung Galaxy S III] nnnnr14:
Especially when combined with this http://xdaforums.com/showthread.php?t=1853816 kernel

-tapped from my cm10 ktoonsez kernel'd Galaxy s3
[Verizon Samsung Galaxy S III] seang:
i just miss a the camera features of TW.
[Verizon Samsung Galaxy S III] Byonik:
Did you already check the Network Mode setting? (should be LTE / CDMA / EvDo)