yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] invisiblek:
Those with random reboots please try this build and report if you get reboots or not with it and what you were doing when/if it happens:

http://invisiblek.org/sch-i535/roms/cm10.1/dragons_ahead/cm-10.1-20130424-UNOFFICIAL-d2vzw.zip

We are working tirelessly to find the fix for this...
[Verizon Samsung Galaxy S III] Kev13Dd:
Running it now. Will report back

Edit: Hour and a half of solid tethering without a reboot. Haven't been able to last longer than 5 minutes in the past

K
[Verizon Samsung Galaxy S III] emogency:
Trying it now my reboots were sitting idle or while on phone calls ill report back soon after i make a few phone calls

edit:Made a few phone calls and I didn't have any random reboots and it's been idle most of the day and it hasn't rebooted either so this build might be on the right track
[Verizon Samsung Galaxy S III] asymptoticFault:
I have been running this build for 14 hours and the stability improvement is like night and day. Prior to this build I had 10 reboots within 24 hours on the 4/20 official build. There didn't seem to be any apparent cause and they would occur during browsing, checking email, making a call, seemingly anything. This build seems to have fixed it :fingers-crossed: Thanks invisiblek!
[Verizon Samsung Galaxy S III] tv31284:
Unfortunately, I've had a reboot with the latest unofficial. The phone was idle in my pocket.
[Verizon Samsung Galaxy S III] airmaxx23:
I wonder what's causing these reboots. I've been on the official builds since 4/19 and have not had a single reboot, I always run the TK747 kernel though.
[Verizon Samsung Galaxy S III] Kev13Dd:
Have you tried the build from invisiblek in post 1447? It solved my reboot problems, and a few other people's as well

K
[Verizon Samsung Galaxy S III] JohnnyTToxic:
Running this and haven't seen any issue, except for the fact that Simpsons Tapped Out crashes every time I load it up, but works with the original nightly. Sadly I'm addicted to this game and there's this promotion (whacking day) going on. : embarrassed:

ETA: for some reason, clearing cache/data and force closing the app did not fix the issue, but reinstalling it did. So it was likely an unrelated issue. Sorry!
[Verizon Samsung Galaxy S III] tv31284:
Yeah, unfortunately that's the build I'm referring to
[Verizon Samsung Galaxy S III] AdMire:
I've been flashing this and the "Unofficial" one by Mastamoon and I'm really not sure which one I'm on anymore. Which one updates through GooManager and/or through "About Phone -> CyanogenMod Updates?

Also, I know this probably sounds tedious, but I not able to search for songs in Pandora. When I try, it looks like it's trying to bring up the keyboard but can't. Can anyone else just confirm this for me? I didn't have this issue before CM and I just want too make sure it's the ROM or the App.

Thank you.
[Verizon Samsung Galaxy S III] JohnnyTToxic:
I can confirm your issue with Pandora, I just assumed it was Swype and ignored it.
[Verizon Samsung Galaxy S III] airmaxx23:
It must be ROM related, it works fine on Beans14 and Xenon HD on my N7. I'm having the same issue with Pandora, when you press on the "create a new station" search area it opens then closes and you can't type anything in at all.

In "About Phone" > "Cyanogenmod Updates" those are the official builds.
[Verizon Samsung Galaxy S III] AdMire:
Thank you, guys. If you press the + at the top really fast, eventually the Keyboard will come up, but once you press anything on the keyboard, it goes away. I just wanted to make sure it wasn't the app. Appreciate it.
[Verizon Samsung Galaxy S III] uncleguito:
I had high hopes for 4/24's build as it was running great, but had a SOD last night that prevented my alarm from going off.

:rolleyes:
[Verizon Samsung Galaxy S III] airmaxx23:
Which kernel are you using?
[Verizon Samsung Galaxy S III] uncleguito:
I've only ever used stock. Any recommendations? I never had any issues on the old stock kernel for M2.
[Verizon Samsung Galaxy S III] Defragger51:
I just installed the KT747 kernel on the 4/24 nightly and screen flicker seems to be gone with out having to disable HW Overlay and GPS seems a little faster and a little more accurate than the stock kernel that came with the nightly, as far a reboot issues I was not having them going 47 hours on 4/24 with no rebots
[Verizon Samsung Galaxy S III] airmaxx23:
KT747, I've been using it since the CM10.1 4/19 build on each new build and have never had a reboot or any screen flicker at all. I've been getting great battery life running it with the TK Mods and one of REricks tweaks.

This is from last week with a stock battery connected to 3G the whole time and batterystat.bin was deleted to clear the stats.
[Verizon Samsung Galaxy S III] uncleguito:
Cool, thanks. After I flash the kernel, should I install any additional apps for tweaking or are those not required?
[Verizon Samsung Galaxy S III] airmaxx23:
It comes with its own kernel app, check in the general section for the TK mods and tweaks.
[Verizon Samsung Galaxy S III] invisiblek:
Ok, so who wants pie controls?!

I've merged this: http://review.cyanogenmod.org/36474

Should be in tomorrow's nightly

You must enable softkeys and expanded desktop for this to work

You can throw this little script in /system/addon.d/ and chmod 755 it (this file survives wipes and rom flashes)

It adds

qemu.hw.mainkeys=0

to the end of your build.prop after a flash.

This zip will put this file at /system/addon.d/ and set its permissions properly (flash via recovery)

You'll need to enable expanded desktop (select the option to add it to your power menu and then enable it through your power menu) You may also have it show your status bar, configurable within the system menu right above the power menu options.

Pie controls are configurable at the bottom of the system menu.

Thanks to danl for the script! Check out his full script here where you can configure and even disable your hardware keys.

Hooray!!!
[Verizon Samsung Galaxy S III] toddrosenberger:
I've been running m2 for awhile, and recently my phone will not rotate into landscape. I have auto rotate checked under display and in cm settings. Anyone else have this?
[Verizon Samsung Galaxy S III] Restola:
If you're using a 3rd party launcher make sure auto rotate is checked there as well.

Tapatalk via CM10.1 Galaxy S3
[Verizon Samsung Galaxy S III] toddrosenberger:
No it's stock cm browser. It just started this, had been running great otherwise.
[Verizon Samsung Galaxy S III] dmeadows013:
How can the 4 way reboot menu be enabled on the latest nightly?

Sent from my S3 on Tapatalk 4
[Verizon Samsung Galaxy S III] sivarticus85:
About phone > tap build number at the bottom 7 times (unlocks developer option) > developer options > advanced reboot.
[Verizon Samsung Galaxy S III] majmuni:
Hi i havent tried this rom in a while how is data and bluetooth working on this rom now thank you
[Verizon Samsung Galaxy S III] stkiswr:
I run the 425 nightly. It is fantastic. Just remember to check disable hw overlay on boot.

Other than that it is perfect. I modded the MMS to fix the quality issue and I am super pleased
[Verizon Samsung Galaxy S III] airmaxx23:
I couldn't get any satellites to lock on the 4/28 build, they were in view but would not connect.
[Verizon Samsung Galaxy S III] phillysdon04:
Disregard
[Verizon Samsung Galaxy S III] toddrosenberger:
Still having the issue with not rotating into landscape. Wondering if it could be my gyroscope is messed up. Or if I just need to do a clean wipe and reinstall.

This is on the m2 build btw.
[Verizon Samsung Galaxy S III] lostwhat83:
The fix in the OP didn't work for me when I had this issue. Mastamoon's fix did work for me.

1) Flash TW based ROM (yes wipe)

2) Turn on GPS and keep on during this whole process

3) Lock on GPS

4) Restart lock on GPS again

5) Flash CM nightly (yes wipe again)

6) Enjoy working GPS

I didn't figure this out, but it did work for me.
[Verizon Samsung Galaxy S III] Hybridnoob:
That method worked like a charm for me a week ago. The only thing I'll add to save people some time is that I had working GPS after the fix, which was maintained for clean flashing CM (Mastamoon's unofficial builds), restoring a nandroid, and dirty flashing newer builds on top of the restored nandroid. The last bit didn't previously didn't work until I executed the suggested fix. Also, I never wiped data during the fix portion, only factory reset, which sufficed.
[Verizon Samsung Galaxy S III] soohyunk83:
I'm on the 4/29 nightly and its very stable and smooth.

I haven't had any screen flickers or random reboots. (Stock cm)

Been running about 7 hours so far.
[Verizon Samsung Galaxy S III] invisiblek:
Those with reboots: There may be hope yet!

Please test this build. It's 100% stock cm-10.1 with just this added.

http://invisiblek.org/sch-i535/roms/cm10.1/cm-10.1-20130430-UNOFFICIAL-d2vzw.zip

Please let me/us know if it helps!
[Verizon Samsung Galaxy S III] zetsumeikuro:
<3 Mr. Moogle.
[Verizon Samsung Galaxy S III] asymptoticFault:
Whatever you did for the build back on the 24th really seemed to do the trick in my case. I have been running that build since then and it's been 135 hrs without a single reboot. Before that build I could barely make it a couple hours without a reboot, particularly if I was doing anything with the phone and it wasn't just on standby.
[Verizon Samsung Galaxy S III] Kev13Dd:
Same

I've flashed a bunch since, and the only reboot free one has been the 4/24 unofficial. Not to mention it's been quite zippy

K
[Verizon Samsung Galaxy S III] mastamoon:
Have any of you seen flicker return the past day or so?
[Verizon Samsung Galaxy S III] Defragger51:
Been running 4/27 nightly for 93 hours with No reboots and No screen flicker with the built in kernel .The only issue I have had is with GPS being Slow and inaccurate and that is why I am about to try the 5/1 nightly because of the GPS fix in it.
[Verizon Samsung Galaxy S III] Aquila76:
My GS3 did the same thing. I think the tilt sensor got stuck or something. I thumped all the corners against the palm of my hand a couple times, seemed to clear it up. Between this and tightening the screws for better GPS, I think some Samsung assemblers need to eat more Wheaties!
[Verizon Samsung Galaxy S III] Gibscreen:
I'm on the 4-30 unofficial and i have seen the flicker. Started happening when i used sd maid and continued everywhere. Stopped when i exited that app.

No random reboots though.
[Verizon Samsung Galaxy S III] mastamoon:
Thanks for the info.. looks like this commit.. https://github.com/CyanogenMod/andr...mmit/14d55c8fadd4710aecc142cb2790cc95c5ab59ad ... is probably causing them. Ill keep it reverted in my unofficial build.
[Verizon Samsung Galaxy S III] Stealth111:
I got to see my first ever psychedelic screenshow today while adding an event into my calendar. I was on last nights official nightly though.

Man... I thought the flickering issues people were experiencing was a mild type of screen annoyance , boy was I wrong!

Sent using Tapatalk
[Verizon Samsung Galaxy S III] NeoMagus:
5/1 has been solid all day here, no reboots yet I had been sitting on 3/17 since mine had been rebooting on all the new ones lately but todays seems good
[Verizon Samsung Galaxy S III] tv31284:
I've had a couple of reboots on Invisiblek's unofficial 4/30 build. Both times the phone was just laying there and I didn't noticed it had rebooted until I noticed all my recent apps were gone and saw the uptime was only at an hour or so.
[Verizon Samsung Galaxy S III] soohyunk83:
I'm on the 5/1 official nightly and it's solid as well.

No reboots and screen flickers yet.

*EDIT* I did see some screen flickers while texting. I didn't see this happen on the 4/29 nightly.
[Verizon Samsung Galaxy S III] Obaterista93:
I haven't seen it brought up much, so to help narrow it down, those with the flickers(and those without) what do you have enabled as far as GPU rendering or hardware overlays? That might help narrow down the problem.
[Verizon Samsung Galaxy S III] vaffanculo403:
how's 5/3 looking? anxious to get rid of this flickering!
[Verizon Samsung Galaxy S III] andrewc513:
I've had the Galaxy S III for 3 days now, running only CM10.1 nightlies. Is GPS not locking a known bug, is there a mod/trick needed to fix it, or is it just me? Clearing the Maps cache/data and forcing stopping/restarting as recommended by OP's guide did nothing. Have also been running imo's latest leankernel as he releases it. GPS doesn't seem to lock either way on any of the latest CM10.1 nightlies.

[MENTION=3034902]vaffanculo403[/MENTION]: None today, but then again I've only seen the flick just once for about 3 seconds the other day, then never again.
[Verizon Samsung Galaxy S III] Hybridnoob:
From Mastamoon's Unofficial Build thread (http://xdaforums.com/showthread.php?t=2094251). It worked for me and really didn't take very long to do! You can restore your nandroid after doing below and all should work fine. I downloaded and used CleanROM to fix the GPS.

1. Do nandroid backup (optional)

2. Download any stock/TW based ROM and install.

3. Get GPS lock (I say reboot and do again to make sure).

4. While leaving your GPS toggled on, reboot into recovery and reflash cm10.1 (or AOSP ROM of your choice).

5. You should now have fully functional GPS regardless of what AOSP ROM you are on.

6. Profit
[Verizon Samsung Galaxy S III] andrewc513:
Thanks! I usually did this on HTC devices long ago with Sense roms for when GPS didn't lock on AOSP roms. This is my first non-stock Samsung device(had a GNex before) so I wasn't sure if the same trick applied.
[Verizon Samsung Galaxy S III] stefilini:
I've been running 5/1 build for the past two days and no reboots or flickering. I did a completely clean install (didn't restore any apps or anything). :good:
[Verizon Samsung Galaxy S III] AdMire:
GPS seems to be a non-issue with me, knock on wood, but I've had the worse screen flicker ever on this 5/3 build coming from 4/30 (or maybe 5/1). And when I installed this 5/3, I wiped cache, Dalvik, Factory reset, System, Internal Storage, and Format Data AND then flashed 5/3 and it started the screen flickr as soon as I got through the set-up process.
[Verizon Samsung Galaxy S III] JPD19:
anyone suddenly having MMS (pic text ok but group text not working) issues with the recent builds?
[Verizon Samsung Galaxy S III] AdMire:
I think there was mention of the MMS issue in Masta's Unofficial thread.

Edit: http://xdaforums.com/showthread.php?t=2094251&page=54 last hand full of posts.
[Verizon Samsung Galaxy S III] vaffanculo403:
How's the Bluetooth streaming on these latest builds? I'm about to get some Bluetooth headphones to stream music while I cut grass but I was hoping to make sure everything worked well before I shelled out the cash...
[Verizon Samsung Galaxy S III] ryzilla23:
My screen is flickering on 5/3 every time I use the backspace on Swype keyboard.

---------- Post added at 07:02 PM ---------- Previous post was at 07:02 PM ----------

Bluetooth streaming is working fine for me, I use it at work all day.
[Verizon Samsung Galaxy S III] airmaxx23:
Where did the unofficial cm10.1 thread go? I can't seen to find it.
[Verizon Samsung Galaxy S III] Hybridnoob:
http://xdaforums.com/showthread.php?t=2094251

[UNOFFICIAL]CM10.1 UNOFFICIAL Builds for D2VZW GSIII
[Verizon Samsung Galaxy S III] imtoomuch:
05/04 nightly got stuck at the loading screen for me.
[Verizon Samsung Galaxy S III] titanshadow:
Works pretty well for me. Haven't noticed any problems.
[Verizon Samsung Galaxy S III] PeterGunz:
Running flawlessly for me.

Just came back from a TW rom, and did I ever miss CM10.1.
[Verizon Samsung Galaxy S III] titanshadow:
Still getting a lot of flickering on the screen.
[Verizon Samsung Galaxy S III] Restola:
Some have suggested wiping system (not data) then re flashing CM and gapps. You'll have to log back into Google services but you data should be intact. (I'd still make a backup first if I were you)

Tapatalk via CM10.1 Galaxy S3
[Verizon Samsung Galaxy S III] trewang:
Anyone find a fix for Bluetooth mono? Found a few threads citing its not working but no solutions so far.
[Verizon Samsung Galaxy S III] d1ez3:
is it safe to go from 4.2.2 AOSP to 4.1.2 touchwiz? I would think the /0 folder could cause some sore of issue
[Verizon Samsung Galaxy S III] mastamoon:
Recovery takes care of the /0 bit. I would obviously make a backup first JIC :P

Have you checked to make sure the latest official didnt help with your gps? They did some updating.

http://review.cyanogenmod.org/#/c/36979/
[Verizon Samsung Galaxy S III] d1ez3:
thanks, I went to synergy and followed your instructions and it worked!

I thought I might want to stick with TW for a little bit again just to see how it was.. but it's just so ugly, I hate the notification pull down, menus, bad placement of clear notifications button, big icons, and less customization. Performance didn't seem too bad though, and multi windows is pretty nice, I hope PA's implementation will work out nicely for AOSP.
[Verizon Samsung Galaxy S III] mastamoon:
Awesome, glad it worked for you.
[Verizon Samsung Galaxy S III] masri1987:
Mastamoon what happened to your thread?
[Verizon Samsung Galaxy S III] mastamoon:
Got moved into the regular development thread.
[Verizon Samsung Galaxy S III] masri1987:
Whew, why they all getting moved there? Thx
[Verizon Samsung Galaxy S III] mastamoon:
Somebody on xda got a bug up their ass and went on a rampage. Lol
[Verizon Samsung Galaxy S III] Snakehn:
Off topic but where did you get TW ROM 4.2.1 for Verizon galaxy?
[Verizon Samsung Galaxy S III] Hybridnoob:
Looked like a typo to me.
[Verizon Samsung Galaxy S III] d1ez3:
My bad, I meant 4.1.2 TW and 4.2.2 AOSP, I was wrong about both.. lol
[Verizon Samsung Galaxy S III] toddrosenberger:
I got a notification a couple times saying that “Windows detected spyware on your computer". Anyone ever seen this, is it something to be worried about, and will a full wipe and rom reinstall fix it? I downloaded a spyware app and it says none detected.
[Verizon Samsung Galaxy S III] Stupifier:
LOL!

1. Your phone isn't running Windows

2. Your phone isn't a computer

3. Using that information, I doubt that notification is telling you anything useful to you

3. Sounds like websh*t to me

4. Full wipe / rom reinstall will certainly fix this

I find it funny that an android notification on a phone would mention "Windows" and "Computer".....wtf....
[Verizon Samsung Galaxy S III] soohyunk83:
5/7 build

Any feedback on 5/7 build?

Seeing any screen flickering?
[Verizon Samsung Galaxy S III] titanshadow:
Definitely screen flickering still. Other than that, works fine.
[Verizon Samsung Galaxy S III] zetsumeikuro:
I haven't seen any screen flickering yet. I also haven't see any animation stuttering either. Good thing is disabling the HW overlays fixes both of those.. Maybe one day that will no longer need to be checked!:good: Edit: Still see the animation stuttering but it's not as bad as before.
[Verizon Samsung Galaxy S III] FryDay444:
I have an issue where if I change ANY setting in the camera, the app locks up, and then will not allow me to use the camera until I reboot. O_o
[Verizon Samsung Galaxy S III] Restola:
I also have this issue (5/7 nightly, stock everything).

logcat (booted up the camera and tried to change the Picture size to cause it to freeze, then eventually selected the option to "close" the gallery when prompted):

https://drive.google.com/folderview?id=0B89vrGhlDBcENmtZU0Zsb2xDbEU&usp=sharing

I have no flickering though. I did do a 'wipe system' (not data) prior to installing it. Not sure if that made a difference or not.
[Verizon Samsung Galaxy S III] FryDay444:
I did a full wipe prior to installing. I also have not experienced any screen flickering.

Not sure if this helps at all, but I also tried installing LeanKernel, and I still had the camera issue.
[Verizon Samsung Galaxy S III] mastamoon:
Looks like flickering should be fixed in official, again.

https://github.com/CyanogenMod/andr...mmit/41f55d87458439a481cf587aabd78c952509aab9

Camera issue sucks.. has anybody reported to JIRA yet? I was going to today, but if somebody else did, I wont bother looking :P
[Verizon Samsung Galaxy S III] Restola:
I think you'll just be told "no bug reports against nightlies"
[Verizon Samsung Galaxy S III] FryDay444:
Isn't that kind of the point of nightlies?
[Verizon Samsung Galaxy S III] mastamoon:
https://jira.cyanogenmod.org/browse/QSDB-44

Camera issue reported
[Verizon Samsung Galaxy S III] stkiswr:
Mine crashed over and over Lol. I went back to 5/4 and it stops if I am at the lock screen and turn landscape whole opening the camers
[Verizon Samsung Galaxy S III] s'pht:
This has been reported in other threads but not sure if it is in this one yet: when the kernel went to 3.4 it broke HDMI / MHL output. Anybody know if/when that's going to be back and happy again?
[Verizon Samsung Galaxy S III] stefilini:
I was having a ton of random reboots on the 5/8 nightly. Downloading the rc now.
[Verizon Samsung Galaxy S III] FryDay444:
Fix is already underway :)

http://review.cyanogenmod.org/#/c/37205/
[Verizon Samsung Galaxy S III] joeinternet:
Encryption Support - MSMFB_OVERLAY_SET errors

Aloha,

I posted this in mastamoon's thread, but think I'll have better luck over here.

Has anyone played with encryption on this ROM? I'm getting the following when encryption is enabled:

E/qdhwcomposer( 4841): Failed to call ioctl MSMFB_OVERLAY_SET err=Out of memory

Logcat is filled with these.

The system encrypts just fine, but on reboot, the log is filled with the above error and the system gets really sluggish. The radio doesn't come to life, either.

I'm happy to keep testing if anyone has ideas about what's going on.

The errors show using mastamoon's or the official nightlies, with or without autopatcher's openpdroid applied.
[Verizon Samsung Galaxy S III] mastamoon:
Fixed Camera - http://truelinux.net/sch-i535/mastamoon/other/Gallery2.apk

I +1'd it so hopefully it will make it into tonight's official if you would rather wait.

Edit: Merged!
[Verizon Samsung Galaxy S III] wierdo124:
Question - has the signal issue been fixed yet? Wasn't last time I was on CM10.1, on AOKP from a couple weeks ago and it's got the problem still.
[Verizon Samsung Galaxy S III] mastamoon:
What signal issue?
[Verizon Samsung Galaxy S III] wierdo124:
The one where AOSP ROMs report far less signal than TW ones. Right now I've got 2-3/5 bars, on TW I'd have a perfect full signal.
[Verizon Samsung Galaxy S III] Hybridnoob:
Compare your actual phone signal between the two. I think you'll find it's the same.
[Verizon Samsung Galaxy S III] wierdo124:
Shows up in battery life screen too. Where it shows signal quality throughout the day, AOSP reports yellow/brown all day, TW is perfect green.
[Verizon Samsung Galaxy S III] Eloquence:
Hardware Keys

Hi Everyone,

Just a quick question, I apologize if this has been answered before, I was wondering -- has the sticky hardware keys (50 hours then reboot) been fixed yet? That used to drive me crazy and I ended up switching to a TW based ROM because of it. However, if it's been fixed, I will gladly return! I'm sorry if this has been answered before. :laugh:

Thanks!

-Elo
[Verizon Samsung Galaxy S III] Hybridnoob:
That was fixed about two months ago. Enjoy!
[Verizon Samsung Galaxy S III] Eloquence:
Thanks! I'm gonna try the RC1!

;)

-Elo
[Verizon Samsung Galaxy S III] Restola:
Please continue to post issues you have after upgrading to RC1. I'd like to update the OP with any RC issues and fixes.

Please also post logcats with any issues posted in this thread! You're wasting your fingertips if you make a bug complaint without a logcat.
[Verizon Samsung Galaxy S III] Restola:
FYI coming from 5/7 to RC1, including a wipe of cache/dalvik/system with a reflash of gapps + RC1....the camera lockup issue is still present. I couldn't figure from the timestamps if it made it into RC or not. Looks like the best bet would be to flash tomorrow's 5/9 (which will essentially be RC1 + at least the camera fix).
[Verizon Samsung Galaxy S III] stefilini:
Clean installed RC and camera issue is still present fyi