yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Yeah, I see that now. Did you try wiping system and a clean install? Sometimes flashing over from an older version like that can cause issues like this.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Running smoothly so fat, no issues. Will report back battery in 2nd cycle, 1st is not impressive
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] statickiwi:
I have the screen flickering on the 04/23 nightly. I think it has to do with auto brightness. I've set my display to not use auto and it seems to go away.

N/m it still happens....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jpcdeux:
Seems like all these ROMs lately have flicker issues.

This have MMS issue? Sends but person getting the message can't DL it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sk8trix:
Yes the flickering issue wasn't in earlier builds for sure but I do notice it on 4/23 also the brightness goes slightly up or down here and there not a big deal tho bit ibsee what you mean
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] howtomen:
No...

sgh-i747(d2att)(sgs3) on latest cm10.1 or ultimatum
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Domoo:
4/24 is out. It seems to have fixed the flickering for those who want to try it now, but I'll have to try it out some more. Will update later.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
The only place I see flicker and have always seen flicker no matter what is in the bookmarks of the stock browser.

Aside from that, I see zero flicker in anything I do and never have. All phones are not equal so I recommend everyone try for themselves as the comments made in this thread aren't exactly accurate.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 19fonzy:
Screen flickering is still present on 4/24. Only happens when i get a new notification, not as bad as before but it's still there.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jpcdeux:
Idk about this but I know with SlimBean the screen flickers mainly when I'm typing a message or some other form of text input
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Change the keyboard
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] statickiwi:
I've disable swiftkey and I am now using the stock aosp keyboard. Will report back if the screen flickering goes away.

Edit: as soon as I finished typing and did some other stuff.flickering appeared. At this point I'm not sure.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Same for me on AOKP too
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dschamis:
On all ROMs since M3 I have had massive random reboot issues - am I alone or is this an ongoing known issue?

I am running M2 until I figure this out.

Thanks in advance,

David
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] spectrumfox:
You should completely wipe your phone, then install one of the current builds to see if you still have random reboot issues. Don't dirty flash back and forth if you really want to figure this out.

---------- Post added at 09:20 AM ---------- Previous post was at 09:19 AM ----------

Yes, I see screen flickering too when using SwiftKey. It tends to happen mostly when I hold down one of the keys.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
Major kernel update in the middle there, the 3.4 kernel hasn't been fully stabilized yet. That being said, I've only seen one random reboot since the 3.4 kernel update. I am running ktoonsez kernel, but it's fully synced with the CM kernel. I'm on cm 4/23 with the 4/20 ktoonsez kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] statickiwi:
I agree that a clean flash will help a lot. I did a clean flash of 04/23 and then flashed 04/24 on top this morning with bms kernel and haven't seen reboots. The battery life on 04/23 or 04/24 has been better than what I have seen on 03/17 with bms kernel.

My only complaint so far is the random flickering of the screen.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] junkedBrian:
I've had 4 random reboots today.

1 time using a GPS app

1 time while playing music connected to bluetooth (car)

2 times while listening to music on headphones
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] draino623:
No problems here. 80+ hours without any problems. Still running buttery smooth. I'm running CM 4/20 and KT's 4/20 kernel.

Sent from my Samsung Galaxy S-BEAST!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dschamis:
I have gotten them when the phone was doing nothing - sitting on a desk with the screen off.

Also, I have done clean installs of the ROM and it doesn't seem to fix the problem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Unfortunately it looks like you have one of the phones that doesn't like the 3.4 kernel yet. After some more changes to the kernel and video commits all the d2s ought to be compatible with it. It is just a matter of time before it gets tweaked to that point.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bitnerd:
I also have one of those phones that reboots spontaneously with stock CM. But once I put the ktoonsez 3.4 kernel on there I haven't had a reboot at all
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rwaterspf1:
Mine reboots with stock CM and ktoonsez 3.4. I wouldn't call it spontaneous though, I can reproduce it pretty quickly (15 - 20minutes) by playing music through headphones. Don't matter the app, iHeart Radio, Apollo, Poweramp all do it. The weird part is logcat looks clean and last_kmsg shows no error. Don't happen if you keep the screen on or have it powered on usb. I work around it by keeping it plugged to usb so far.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bitnerd:
Under stock CM mine seemed to usually reboot when the screen was off. Didn't seem to matter whether it was plugged in or not. I changed kernels more or less permanently when it rebooted more than 12 times when I was at work recently
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Domoo:
Removed
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
Anyone having issue with 4/25? Updated through cyan delta and it wouldn't finish booting. Trying to manually download but getting 404 error
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
My server just downloaded it successfully and it should be in Dropbox shortly. I did get a 404 from my Nexus 7 (grouper) script, but d2att went through. They might have pulled the zips because of some issue and my script for d2att just got there quickly enough.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
if 4/25 is having issues though i'll just stick with 4/24 for now. Thanks though!

Not sure what the issue was. 4/25 downloaded and booted up. Haven't tested but it is in fact working.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dlove27:
AT&T visual voicemail is back to working. They released an update for it in the play store.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] czechpunk:
Still have flickering on 4/25
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hova08:
Can someone help me, Google now doesn't wake up when i say google. My language is set to English US and the option is set to wake up when google is said. Also i get some audio popping from time to time even when the phone volume is off.

* Nevermind it seems you have to be very close to the speaker for it recognize when you speak.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikecantreed:
Use Google Voice. It'll change your life.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mr_ding:
Can anyone get a GPS lock with latest nightly build? I tried 4/24 and cannot lock it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
New features to be added in CyanogenMod :

Time-Delayed and Voice-Activated Photo Capture Modes

Check this Video out: http://www.youtube.com/watch?feature=player_embedded&v=woa1rsatK44

Cant wait.:highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Malf8:
No problems with gps lock for me on the last few builds. In fact other than a bit of screen flicker at times on the lock screen I've had no other issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nakedninja42:
Funny thing, on 4/24 my GPS crapped out. But I went back to stock and factory reset and it was still borked. Have you had issues in the past, I have. I just got back from att warranty store to replace my phone, its been an ongoing struggling to keep it working.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
This.

---------- Post added at 01:36 PM ---------- Previous post was at 01:34 PM ----------

Worked last night on the way home. Try clearing your AGPS state with GPS Status (or some other app).

https://play.google.com/store/apps/details?id=com.eclipsim.gpsstatus2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VQ30DE:
A clean flash did not help me when I was trying 4/20. Made no difference whatsover. No matter what I was getting frequent random reboots with every recent April nightly. Then I flashed Tasks Underwear kernal and have had 0 reboots since on 4/20. No flicker that I've noticed, and battery life with this combo is better than 3/17.

When you all do clean flashes, are you using TiBu to restore your settings or what? I have the free version of TiBu and it takes forever, and it's a pain to re-login to all my apps and services. Anyone have a super fast/streamlined way to restore everything on a clean flash? I feel like even the pro version will not address the login issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
Paying for tibu will improve the speed of restoring apps no doubt. If you restore data to those apps then you do not have to log back in. Personally I only restore the data for very few apps that I absolutely need to. The rest of them i set back up manually to avoid any issues.

If you are STILL facing issues, a truly clean flash would be to let your apps download from the app market on a fresh install and not restoring data that google doesn't restore for you.

You can also make a nandroid back up and restore only your data. This is not a clean flash however. It will streamline the re installation of your apps and data.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
When I do a clean flash, I let Google Play sync down everything, reboot, then restore data for what I need with TiBu. I also have TiBu make backups of new data and apps every night (I'm paranoid). It cleans up deleted app backups too, since I don't need backups for apps I've uninstalled. This all syncs up to Dropbox when it's done.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] statickiwi:
That's funny, my phone hasn't been friendly with tasks kernel. I get a lot of hot reboots with that one. Bms kernel has been the best for me.

TiBu is what is use to restore apps and I selectively restore certain app data as others have mentioned. I could probably flash a new rom pretty quickly using this method.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
Still getting screen flashing in the latest nightly. I wish they would fix it already. :mad:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] statickiwi:
This is annoying to do every time you reboot, but try disabling HW overlays in developer options.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JJRules:
Same GPS problem for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
Could this be the fix for the swype keyboard screen flashing?

http://review.cyanogenmod.org/#/c/36445/

Or

http://review.cyanogenmod.org/#/c/36443/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bigfoottrucker:
Got garbled sound good in call. Had to quickly flash a TW backup to finish business. 4/24 was what I was on. Thx. First problem with calls I have had.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Makoers:
Oops didn't mean to thank you , but when I dirty flashed my call would ALWAYS be garbled and cut in and out. A clean flash will fix it .
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Domoo:
It seems like it. I'm on 426 and haven't had any flickering but it seems to show up later on. Will report back later.

Update: screen flicker is fixed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] indymx:
4/26 seemed to cause some SMS issues. Anyone else having issues sending?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JDM STi:
Yeah true... mine still no 0422 NIGHTLY and flickering bothered me much and I need to disable HW overlays every time when phone reboots.

HOWEVER, phone does not have any flickering since this morning it's turned on and it is still on 0422.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
no issues here
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ozzman54:
I've been on 4/20 all week and all is well except for the occasional screen flickering which I can tolerate. Last night tried flashing 4/25 and I lost 4g signal (only was getting 3g) so I restored back to 4/20 for now. Anyone else have this issue?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mr_ding:
Tried both 4/25 and 4/26 and both version cannot get GPS lock (have tried flushing GPS cache already)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] johnhazelwood:
I had GPS lock issues too. From this thread: http://xdaforums.com/showthread.php?t=1995347&page=9 I tried harshaedvern's proposed solution and it worked for me. The only negative with the solution is it requires going back to any Stock TW ROM, performing the steps, then you can reflash back. Here's what I did:

1) Download any TW ROM (I also downloaded the latest CM10 build)

2) Go into Recovery and Backup current ROM (remember to uninstall Google Wallet if you had it installed - just in case)

3) Wipe Data (the first wipe option in TWRP)

4) Install TW ROM and reboot

5) Follow steps below:

if you dont see your gps icon on status bar. there is problem on your gps chip.

becouse that was happend to me my I747. im more confused about it.

i try more things like rom change,, firmware upgrade,, orginal samsung updates,, etc,, no more fix

after i go to the samsung service mode *#197328640#

then go to mainmenu>UMTS>Common>NV REBUILD>NV REBUILD>finish and dont exit menu

wait 30 sec

long press power button and select restart..

thats all

now check your GPS from gps software...

if this is fix your problem dont forget to thanks....

6) Go Back into TWRP and Wipe again

7) Install CM10 whatever version you want, and then restore the data only from the backup you did earlier

8) Reboot and enjoy GPS lock
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AlbertoM:
426 is running pretty smoothly for me except for the occasional crash and reboot...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sk8trix:
Yes it was on early cm9 and cm10 builds
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SirGeraint:
Gee, that sounds like a lot of work. In my case I just went back to 04/23.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] indymx:
Seems my SMS issues were network related... Things are fine now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] johnhazelwood:
Did that work? You get GPS locks now?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fatty001:
hi from a i747 noobie

hi all, I bought two i747's for my wife and I on the 23rd and had them both running CM on the 24th, using the nightly from the 24th.

We have put these phones through their paces, using alot of their features as we're on a road trip and using navigation, skype, fring... and they are working great, much better than our old htc.

But, couple issues, the screen flickers using the keyboard, and we have had freezes when we are in low signal areas.

Can anyone else confirm the flicker is gone in the update on the 26th? (turning of hw overlays does fix it but what a pain every reboot it resets this option)

Anyone else getting freezes in low signal areas? we were using 3G, wifi hotspot at the same time too.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] humblehyper:
LOL, you can just clear data and cache on the "google services framework" under apps and boom instant lock on gps.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SirGeraint:
Yes, that's all it took to fix mine. Clearing (as other recommended) did nothing for me. As it was on 04/25 I was get 0 satellites so I don't think a clear would help with that. On 04/23 I get get 22 satellites from the recliner in my living room.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] johnhazelwood:
I tried that, which didn't work.

I wonder what caused that to work? If it was a 4/25 thing, then it shouldn't be working on mine now (which it is), but I had the same thing as you had which is 0 satellites showing. Interesting. Did you restore a backup, or install CM on top of itself? I see a number of people are having GPS issues, and am wondering what's causing it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] humblehyper:
Did you reboot after clearing it?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] johnhazelwood:
Yep
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Monkeymannnn:
Has anyone gotten good battery life from 4/20 or later? I flashed 4/22 and while it was the most buttery smooth experience I've ever had on this device, battery was the worst I'd seen.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
I always use a different kernel but my batt life is phenomenal
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Monkeymannnn:
Which one are you using? Ktoonsez's main one and my phone couldn't get along the handful of times I tried it.

Edit: mixed up the kernel dev with someone else :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
BMS has been doing very well for me. But I take a lot of extreme measures to get the most out of my battery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Domoo:
Been on 4/27 for a few minutes now. It's pretty solid, no issues so far. The camera features work, but you need to speak loudly for the voice feature.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
Latest nightly and last few njghtlies, I'm still getting Bluetooth stutter on every connect for first full minute. Someone suggested a full wipe, but that is a bit of work for me to get everything back.

I'm willing to do this if it would work. Can anyone confirm this will do the trick before I go ahead?

Ps . awesome to see flicker dead! Especially since I just bought swype!

Battery life seems short even with all the useful location services disabled. About 5% per hour.

Warp o vision still present for 720p video preview.

All stock. Last clean flash was about a week ago.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
Try going into your build.prop and look for lpa.decode=true. Set it to false. And reboot. See if that helps.

As for battery maybe another governor or kernel. I'm getting 0.5% drain overnight when idle.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Nrod0784:
Sorry to beat the battery life horse to death, but what are peoples recommendations for battery life savers using ktoonz kernel and cm 10.1? what governor should i use for best performance and battery life combo? scheduler? I tried ktoonservative and row, with uc to 1294(?) yesterday and basic syncing for email and i use google now, and i dropped battery about 5 an hour. Thanks for any help.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
Battery life is always dependant on the device. It's going to take some playing around to figure out what works best for your phone specifically.

If you are on ktoons latest give asswax a try and make sure you enable hot plugging. For more kernel questions I would look at the ktoons discussions thread in the general section. I also turn Google now off
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AlbertoM:
With 427 I seem to have less reboots. so far just one. otherwise smooth!

Alberto
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pixbuf:
Cause of GPS failure?

Does anyone know why GPS failed after 4/23? I looked in the changelogs and didn't see anything obviously related to GPS. I was really liking 4/26 -- very stable and smooth, but no GPS is a deal killer. Going back to 4/23 fixed it, though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
GPS works fine on 4/27 for me. I think there was some commit having to do with GPS that was labelled as something to do with the RIL or radio HAL.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blasterrr:
Same Here

I too was having GPS issues on 4/26. I went to the one from March 30th with older Kernel using Nandroid. Booted the phone, checked GPS and it was working. Re-installed 4/26 nandroid and wola...for some reason GPS started working again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pixbuf:
Curious. I couldn't get GPS to work with 4/27. But when I went back to 4/23 it didn't work at first. I cleared and reloaded AGPS, and then it worked. Maybe that did it, rather than just going back to the previous ROM. I'll try flashing 4/28 tomorrow, see what happens.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
The build prop setting didn't seem to help. Maybe I'll make a nandroid and try a clean flash.

I'll try another kernel. Interesting that Google doesn't seem willing or able to deal with the battery issue of Google now or location services in general.

If I could control which applications can access location, maybe that would be all that is needed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
Was just told there is echo when using speaker phone. I sound fine but the person on the other end can hear themselves echoing pretty badly. Anyone else?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Aqua1ung:
I keep getting reboots while streaming Google Play Music via A2DP Bluetooth. Anyone else?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AlbertoM:
I get reboots. Period.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SirGeraint:
Thanks for finding that. Earlier today I had gone back to 04/23 and my GPS worked. Then I tried 04/24, 04/26 and 04/27 and the GPS wouldn't work. But I just tried flashing back to 03/30 and then to 04/27 and now my GPS is working on 04/27. Crazy....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Fix for GPS Issue(tested and working for me)

1. Backup your existing ROM

2. Restore your old backup or install the last ROM which has GPS working

3. Enable Location and wait until you have GPS Lock on any App using the GPS, preferred Maps.

4. With GPS Lock on the app, Press the power button and reboot into recovery and restore to the backup done in Step 1.

5. Voilla you have the GPS working :highfive:

Credit to the person who have posted this in TW Forum, think Venom was the man
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] swtnix:
i flashed 4/27 and no gps. i flashed 4/28 and it wouldn't boot pass the cm sid....I'll try 4/24 and we'll see. I was on 4/21 and it was ok except battery life.

also anyone notice the bbq changelog has no changelog for 4/25-4/28 ?

edit: ok flashed 4/24 and it booted fine. for s&g i tried to flash 4/28, booted no problem. i'll update with anything worthy.....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] swtnix:
Well 4/28 wasn't giving gps. i followed the steps above and it worked, weird but it worked. thanks bro....

so now I have 4/28 with gps. we'll see how the rest of it works.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Aqua1ung:
I now understand why Apple don't allow SD cards in their phones. I switched my camera's storage to the SD card (a relatively new and sparsely used SanDisk Ultra 32G uSD): A few minutes after shooting the first video with this setting, the card died. Just like that. :mad: That'll teach me to rely on SD cards from now on!

I don't suppose there might be a way to revive it and retrieve what was on it, is there?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] djjuice:
Agreed, this worked great...