yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] Div033:
Video drivers are certainly wonky right now.

I'm getting unusual amounts of UI lag where I didn't on 10.1.

To name a few examples (compared to 10.1):

1. Scrolling through Google Voice is very laggy unless you enable Force 2D acceleration

2. Scrolling through the Press widget and application is significantly laggier with hardware overlays disabled

3. Scrolling through Play Store search results is extremely laggy despite any settings

Wouldn't be surprised if these issues were somewhat related to the ones you're describing. I was wondering if there was a way we could roll back to the old drivers prior to 4.3...
[Verizon Samsung Galaxy S III] mastamoon:
I also just had the no radio bug but no amounts of reboots or toggles would bring it back. No cache wipes worked either. Had to reinstall the ROM to get it to work. Everything is getting worse lol.
[Verizon Samsung Galaxy S III] Chris123NT:
Yeah I reverted the RIL commit on gerrit, noone has looked at it yet though, but I'm expecting to get yelled at by people who think their code is perfect.

I think noobnl knows something is up with it though.
[Verizon Samsung Galaxy S III] bitterroots:
I have been getting some strange "artifacts" while using Overdrive epub reader. On again, off again. Might be related?
[Verizon Samsung Galaxy S III] khymbote:
Same with me.
[Verizon Samsung Galaxy S III] dpaine88:
Thinking it's a good idea to stick on 8/20
[Verizon Samsung Galaxy S III] Chris123NT:
At least until tomorrow when masta can revert that RIL commit and fix the issue.

Look at the comments on my revert, Shareef brought up kernel which I know isn't the problem, would have been happening all along if that were the case.
[Verizon Samsung Galaxy S III] BrianAllred:
Are we sure? I've had zero data drops on BMS kernel.
[Verizon Samsung Galaxy S III] Wh1t3Rose:
So I took a nandroid b4 I updated to the latest build. Of could signal was gone just like since other people. It's my baseband. Says unknown. I restored my nandroid and I still have no baseband. I reflashed the MBF1 modem and still no go. I did an nvbackup before I installed my first custom ROM about 2 weeks ago. Should I restore that? It should be in intact right? What's the command for restore? Oh and going to status under about phone gives me a force close.
[Verizon Samsung Galaxy S III] Chris123NT:
Try re-flashing the ROM first, but before you do that take a screenshot of the unknown baseband, if this commit is screwing with the baseband that's very interesting. OR it's causing the ROM not to recognize it.

Also make sure your IMEI is intact and not displaying as 0 or something.
[Verizon Samsung Galaxy S III] Wh1t3Rose:
Dude forget that my systen/efs is empty. :crying: what should I do? Isn't that where the nvrestore comes into play?
[Verizon Samsung Galaxy S III] Chris123NT:
Yeah, go into terminal and do su followed by reboot nvrestore

that will restore your IMEI/ERI/EFS backup
[Verizon Samsung Galaxy S III] Wh1t3Rose:


---------- Post added at 11:23 PM ---------- Previous post was at 11:21 PM ----------

Just to make sure I took a backup when I first got my phone. There's no way that backup is corrupt right? Where is the backup exactly? I what to know exactly what I'm restoring.
[Verizon Samsung Galaxy S III] Chris123NT:
Does it show an IMEI?

Edit, I've never heard of a backup being corrupted, you did reboot nvbackup when you first got the phone correct? It's stored in a special backup block, not accessible to anything other than the bootloader AFAIK.
[Verizon Samsung Galaxy S III] Wh1t3Rose:
Can't look. When I go to status under about phone I get a force close. See above screen shot

---------- Post added at 11:27 PM ---------- Previous post was at 11:25 PM ----------

I'm going to try a clean install of yesterday's build before i nvrestore. Brb
[Verizon Samsung Galaxy S III] Chris123NT:
Yesterday's build has that commit too, clean install build from the 20th if you can.
[Verizon Samsung Galaxy S III] Wh1t3Rose:
Lol wtf. I did a clean flash of yesterday's build and everything was back to normal. So I thought I would restore only the data partition of my nandroid. Baseband unknown again. Gonna clean install again without restoring data.
[Verizon Samsung Galaxy S III] Chris123NT:
That's really weird.
[Verizon Samsung Galaxy S III] Div033:
I just did something crazy/potentially stupid. I took the sound driver from the latest nightly and plopped it in the 7/19 10.1 unofficial and recording sound is fixed! I haven't observed any ill effects yet but... Well, watch for me on the news. You might hear another story about a phone pocket explosion. We shall see......
[Verizon Samsung Galaxy S III] Wh1t3Rose:
OK so I an up and running again. Using TIBU to restore all my apps. I'm deleting all nandroids and making a fresh batch. I'm also going make a fresh backup of my eri/IMEI using nvbackup.
[Verizon Samsung Galaxy S III] Chris123NT:
snd_soc_msm_2x is the same format from 10.1 to 10.2 AFAIK
[Verizon Samsung Galaxy S III] Wh1t3Rose:
Omg are freaking kidding me??? :( :( :( So I was all good. Had a baseband and IMEI. I had service. I went and did an nvbackup and after the reboot I had the same ****. No baseband no service. Should I do a nvrestore? I'm afraid to. It might be a bad backup. The way I see it is if I restore the backup and it fixes my issue I need to go flash an older build and make anew nvbackup. As long as I don't backup a corrupt IMEI I should be fine right?
[Verizon Samsung Galaxy S III] Chris123NT:
Yeah as long as your backup isn't corrupt you'll be fine. But forget that for a second.

What build did you clean flash? If it was yesterday's that has the commit that I believe is causing all of this. Clean flash the build from the 20th. I don't think your IMEI is the problem here.
[Verizon Samsung Galaxy S III] Wh1t3Rose:
OK will do. I didn't have this issue yesterday or today though while running the 21st build. I'm on the 21st build now. Gonna get the 20th

Edit: where can I get it?

---------- Post added at 12:54 AM ---------- Previous post was at 12:28 AM ----------

I don't see where to get any of the previous builds
[Verizon Samsung Galaxy S III] stearic:
While i only had the no radio bug just once, i only had that when i rebooted my phone. Is anyone else getting this while the rom is running or after a cold/soft boot of the phone?
[Verizon Samsung Galaxy S III] Wh1t3Rose:
Me!!! Lol read last 2-3 pages. Haha. Hey do you know where I can get the build from the 20th?
[Verizon Samsung Galaxy S III] sbenson1226:
Here: https://www.romdashboard.com/developer/mastamoon
[Verizon Samsung Galaxy S III] Wh1t3Rose:
Thank you. Now I can fix this and get service back
[Verizon Samsung Galaxy S III] sbenson1226:
Good luck man, that's really frustrating.
[Verizon Samsung Galaxy S III] Chris123NT:
Did you sort it out?
[Verizon Samsung Galaxy S III] cornelious1212:
OK, so, anybody have problems with Google Now? And still nobody with keyboard issues? I'm about to to a clean install. Wiping everything including internal SD
[Verizon Samsung Galaxy S III] Zacharybinx34:
How do I figure out what is destroying my battery life?
[Verizon Samsung Galaxy S III] Chris123NT:
Betterbatterystats, look at wakelocks.
[Verizon Samsung Galaxy S III] sbenson1226:
Are you the one that had the black keyboard?
[Verizon Samsung Galaxy S III] mastamoon:
8/23 build in the OP

-- reverted DcTracker: ensure subscription is from NV before calling onRecordsLoaded - http://review.cyanogenmod.org/#/c/48680/ to maybe fix/help the weird radio issue

-- repo sync @ 10AM EST

#1 - *** didnt work, still have issue*** it looks like the BMS kernel might get rid of the graphical issues we have, looks like it has many more commits having to do with our graphic driver there. If you are one of us that has screen flicker (bright/dim), try http://www.droidhype.com/kernel/34/, make sure you download the d2vzw version. Let me know how it goes. Im running it right now, but haven't had much time to test.

#2 - it looks like Focal kind of works now. I was able to take 30 shots without incident. First snapshot caused a momentary freeze, but no crash and it continued to work. Able to close and reopen without the same issue on first snap either. DO NOT USE THE FFC with Focal. It will lock up your phone with a black screen then hard reboot.

Have a good weekend!
[Verizon Samsung Galaxy S III] cornelious1212:
No, just stopped gesture typing after dirty flash. I wiped EVERYTHING and flashed 8/22. Rebooted 3 times with no radio issue, Google now works again and keyboard works fine. Can't DL 8/23 till I get off 3G in the hospital.

---------- Post added at 04:54 PM ---------- Previous post was at 04:49 PM ----------

So we are supposed to be on NV rather than RUIM/SIM?
[Verizon Samsung Galaxy S III] Chris123NT:
No, we are supposed to be on RUIM/SIM, but that commit was screwing with our radio initialization.
[Verizon Samsung Galaxy S III] dushotgun:
Ok for the high battery drain its related to the Wi-Fi always scanning. Go to Wi-Fi, click menu and select advanced, then deselect scanning always available. Unchecking this substantially lowers the battery drain. My battery was dropping 20% per hour and now it's back to a reasonable rate.
[Verizon Samsung Galaxy S III] zachf714:
Yup I did the same and the problem is fixed
[Verizon Samsung Galaxy S III] khymbote:
So my my PC reads the SD card but the gallery or camera will not read it. I tested in another phone to verify that it wasn't my card and was able to copy and read off it. I am gonna completely wipe my phone and go to 10.1 and test it there.
[Verizon Samsung Galaxy S III] Chris123NT:
Awesome, thanks. This was really driving me nuts because it looked like location services causing it. Turns out it was, just not in the traditional sense.
[Verizon Samsung Galaxy S III] airmaxx23:
Mine was already unchecked and android system is still very high.
[Verizon Samsung Galaxy S III] bubba911:
I just unchecked mine. My android system was at 38% of battery drain on 4 hours on battery (at 58% now).... Will see if that goes down any before I get off work
[Verizon Samsung Galaxy S III] Chris123NT:
Just flashed 10.2 about an hour ago, restored my app backups, multiple reboots, took some pics and my sd card is fine, I can read it perfectly. You SD Card COULD be going bad, the phone tends to act up before the PC will when that happens, I had one go out on me a few months ago.

Was the other phone an S3? S3 is very sensitive to finicky SD cards.
[Verizon Samsung Galaxy S III] DiGi91:
Finally going to give Mastamoon's build a try after being on M.O.A.R for far too long!

Just getting sick of TW and the fact that it seems we might never get past 4.1.2 on TW!

:cool: I will be one of the cool kids now ;)
[Verizon Samsung Galaxy S III] sivarticus85:
Are you running masta's 8/1 build, or another more recent build?
[Verizon Samsung Galaxy S III] Chris123NT:
Running my own build, same cherrypicks, but I repo synced around 5 PM
[Verizon Samsung Galaxy S III] kidhudi:
Thanks to all the devs involved. I was just going to flash this and test it out and immediately restore a TW nand. but this thing is solid as hell for me. not one hiccup ( not including focal). i will check it out some more tomorrow. once focal is figured out this thing will be even awsome-er.
[Verizon Samsung Galaxy S III] sivarticus85:
I seriously need to learn how to do that. I've got an itchy flash finger.
[Verizon Samsung Galaxy S III] dushotgun:
Yeah there's still something else going on in 4.3, my phone still feels warm compared to normal. I'm going to keep digging to see if I find anything else.
[Verizon Samsung Galaxy S III] Chris123NT:
My phone is as cool as it always is at the moment, battery life seems ok so far using it here and there. I'll have a better idea of how it is when I spend the day with it at work tomorrow.
[Verizon Samsung Galaxy S III] dushotgun:
Lol yeah you're right tomorrow will be a better estimate. Mine might still be recovering from all the Wi-Fi draining and charging.
[Verizon Samsung Galaxy S III] NeoMagus:
Been using ek's build all day, only irregularity I have come across with it is the high Android System usage as others are commenting on. I have the scanning wifi thing unchecked in advanced wifi and it still seems to be taking about 25-30%- goes up noticibly when I turn my tethering on but the phone does at least seem to be deep sleeping, I can live with it til its figured out
[Verizon Samsung Galaxy S III] kidhudi:
First speed bump. A random reboot to a black screen and the capacitive buttons lit up. Had to restore a nandroid.I can't wait for a future release.
[Verizon Samsung Galaxy S III] 0331:
Yes. I am. My sdcard is all outta whack, but it's more than likely my own fault.
[Verizon Samsung Galaxy S III] stearic:
Anyone on here have a fitbit one and able to sync over bluetooth with it? I can see the fitbit but it seems the app doesn't want to see it and sync with it. On a plus side though it sees and connects with my polar H6 though over bluetooth le.
[Verizon Samsung Galaxy S III] Chris123NT:
Someone might kill me for posting this, but if you want fully working front facing camera, delete gallery2.apk and drop in the one from CM 10.1. I have no idea why that fixes it yet but it does lol.
[Verizon Samsung Galaxy S III] cornelious1212:
Thought so, just reassuring myself.
[Verizon Samsung Galaxy S III] goldsmitht:
currently running 8/20; got message of a new update, and it was 8/23. Then ROMdb said i had downloaded it (hadn't); cleared data, re-suscribed, got the message and it now says version is 8/21.

still no biggie, can download from the OP, but not sure what's up with ROMdb. But hey, alls good!
[Verizon Samsung Galaxy S III] mastamoon:
That's even more weird than usual. :-/
[Verizon Samsung Galaxy S III] khymbote:
Every time I install that kernel I end up with no service and no reboots help. I guess I have to do everything in one shot.
[Verizon Samsung Galaxy S III] mastamoon:
I flashed the ROM then kernel at one shot, rebooted and had signal.
[Verizon Samsung Galaxy S III] khymbote:
I am still having that issue with my gmail and what not showing back up. I have used the latest version of gapps that you have posted.
[Verizon Samsung Galaxy S III] GideonX:
Flash rom, gapps, then kernel again (in that order). Your service will return.
[Verizon Samsung Galaxy S III] Wh1t3Rose:
I have the black keyboard. I have no gesture typing but its the gaaps package's fault Not ROM. I use a different gaaps. OK you guys won't believe the **** I had to deal with. So I'm picking up from last night. Last night I flashed the 20th build and I was all good. Then this morning I woke up and did a reboot. After the reboot I lost baseband and IMEI. So I was like well the 20th build shouldn't have the issue the latest 2 builds had so I had to have truly lost my IMEI this time. I thought no problem. I'll just go flash my nvbackup. After I did an nvrestore instant bootloop. Yay!! The is just Awesome!! I flashed myself to 0. Almost had a heart attack. So on a whim I reflashed ROM GAAPS and VZW Modem. I'm back up again and I have LTE. I don't know what to do though. I'm afraid to reboot Lol. Please get a build out soon that'll fix this.
[Verizon Samsung Galaxy S III] goldsmitht:
using a different gapps package MAY be your issues... but just my opinion. ???

:D
[Verizon Samsung Galaxy S III] Wh1t3Rose:
Its the one on the CM10 official thread I believe. Are u trolling?
[Verizon Samsung Galaxy S III] mastamoon:
Well I can confirm that the BMS kernel does not fix the candy crush blinking/flicker. Actually had candy crush crash totally. That never happened before.
[Verizon Samsung Galaxy S III] khymbote:
no just making sure you are using the proper gapps is all. (gapps-jb-20130820-signed)
[Verizon Samsung Galaxy S III] goldsmitht:
NO, not trolling, trying to help. IF He was using an inverted set of GAPPS, they have been known in the past to have caused problems, so was suggesting something that might be his issue.

---------- Post added at 01:23 PM ---------- Previous post was at 01:11 PM ----------

-+-+-+-+-+-+-+-+ IMPORTANT LINKS -+-+-+-+-+-+-+-+

Official download source: http://get.cm/?device=d2vzw

Latest Goo.im gapps (8/13/13): http://goo.im/gapps

Mastamoon's Fixed 8/20/13 gapps (fixes gmail wiping after dirty flashing a nightly):

-Dropbox mirror - http://goo.gl/AqHn5T

-Box mirror - http://goo.gl/PSCW6J

-Google Drive mirror - http://goo.gl/unBs8n

-Masta mirror - http://bit.ly/1eZY53h

MF1 Firmware: http://xdaforums.com/show....php?t=1788313 (click “Latest Firmware” link in the first post, then download “I535VRBMF1”)

IF you are using the 8/13, there were issues, probably not going to cause all the problems, but might... just saying... would suggest you try the 8/20 (IF you are NOT already) and see if that fixes your problem

:cyclops:
[Verizon Samsung Galaxy S III] Wh1t3Rose:
Oh OK thanks. Anybody no a gaaps package with black keyboard that doesn't have broken swype.
[Verizon Samsung Galaxy S III] GideonX:
Any chance it could be an app issue?
[Verizon Samsung Galaxy S III] mastamoon:
Its possible. Don't see much hollering on the interwebs and the issue also sprouts up at other times, playing words with friends and when doing stuff in gallery for example.

It seemed to be helped by changing the iommu heap size but that broke other things.
[Verizon Samsung Galaxy S III] Wh1t3Rose:
I already have all those files. Thanks. I'm going to go flash the 8/20 gaaps since I am using different ones
[Verizon Samsung Galaxy S III] Hybridnoob:
Look at the Betterbean theme from the Play Store. I'm not sure if that keyboard is themed, but it's a much safer route than flashing alternative GApps.
[Verizon Samsung Galaxy S III] BrianAllred:
That's really strange, I haven't had any issues in gallery or 3D games with BMS Kernel... Sorry for the false hope. :/
[Verizon Samsung Galaxy S III] NedDasty:
I can't log into my Cyanogenmod account; anyone else having this problem? I can either set the password on my phone, and log in on my phone (but then desktop tells me invalid password), or I can set the password on my desktop on the website and phone gives me invalid password.

Edit: figured it out, can't use numbers in your password, or maybe it was capitals. Maybe one login casts to lower/uppercase and the other is case sensitive?
[Verizon Samsung Galaxy S III] cornelious1212:
If we try focal, are we still suppised to reboot for fear of epic battery drain?
[Verizon Samsung Galaxy S III] goldsmitht:
Focal still wonky

tried Focal, and got stuck. couldn't take picture, couldn't take video and then camera was unavailable. wiped dalvick and cache and fixed permissions (don't know if that was required, but sounded good to do) and...

looks like all is back to normal. showed there was a video taken, but wouldn't play, and was just a dark screen.

so still wonky for me
[Verizon Samsung Galaxy S III] minnysota:
Could someone possibly recommend me a build? I would really appreciate it. It's been a little tough to keep up with Masta's changes to try and combat flickering (plus the whole RIL change forcing folks to lose data). FWIW I would rather have the best shot at working gallery/HD YouTube as opposed to games like Candy Crush.

Thanks in advance! :good:
[Verizon Samsung Galaxy S III] Wh1t3Rose:
OK I restored my Liquid Nandroid and rebooted twice. I still have data. So I'm staying away from CM10 until this RIL issue gets fixed. Like I said I tried Build 8/20 and I still had issues.
[Verizon Samsung Galaxy S III] BrianAllred:
Random thought, has anyone thought to check auto-brightness stuff? I never enabled that and when I did, I started getting random screen dimming and brightening in games and stuff. When I go into the lux settings, the lux meter jumps around a lot.
[Verizon Samsung Galaxy S III] mastamoon:
I just turned lux off and made sure auto brightness was off also. I'll do some more testing. I really hope that's not it. Lol
[Verizon Samsung Galaxy S III] goldsmitht:
well, that was weird; flashed BMS and totally lost all data and everything. went back to stock and alls well.

flashed BMS_34_d2vzw_d2usc_20130815 so think that is the correct version.

not getting any of the flashy-screeny things but was just curious to see what kind of battery i would get. I'll try again tonight when i'm at home and have more time

:confused:
[Verizon Samsung Galaxy S III] BrianAllred:
Happens sometimes. Quick fix is to flash the ROM then the kernel during the same recovery session, then reboot.
[Verizon Samsung Galaxy S III] mastamoon:
Well just had candy crush disappear on me again, but didn't see any flashing/flicker. It did start getting laggy and i guess the flicker must be a side effect of the lag. Meh.
[Verizon Samsung Galaxy S III] Chris123NT:
Candycrush clearly hates you Lol, I'll see if I have any issues over the weekend, I've been building with aeroevan's kernel repo

---------- Post added at 03:46 PM ---------- Previous post was at 03:31 PM ----------

Focal works for pics but I think its still wonky for video, and FFC is messed, but FFC is a kernel issue because of the iommu stuff, wish they would just disable iommu for d2
[Verizon Samsung Galaxy S III] goldsmitht:
Thanks, that did the trick!

:thumbup:
[Verizon Samsung Galaxy S III] GideonX:
This actually happens to all the kernels at this moment. I haven't had time to poke around and see why, but reflashing your rom, gapps, and then whatever kernel you want restores your data.
[Verizon Samsung Galaxy S III] airmaxx23:
The 8/23 KT747 kernel flashes fine by itself.
[Verizon Samsung Galaxy S III] AdMire:
Seems like 08-23 lost the notification sounds again. I went back to 08-22 and they work. Just seeing if I'm the only one.
[Verizon Samsung Galaxy S III] PerCompLLC:
They are working fine for me... I'm on 8/23 as well.
[Verizon Samsung Galaxy S III] airmaxx23:
Same here.
[Verizon Samsung Galaxy S III] V3TTOO:
So, I am thinking I am going to try PAC ROM. Anyone have any input on PAC vs CM/Mastamoon? Pros/Cons? Why I should stay?
[Verizon Samsung Galaxy S III] ugachris:
Hey masta, quick unrelated thought on the auto-brightness/brightness. It seems like the lowest brightness setting is still really bright. Can this be adjusted? This might help battery life. I've just noticed my phone, in the dark on lowest screen brightness, is eye-hurting bright.
[Verizon Samsung Galaxy S III] Chris123NT:
Can you test front facing camera in instagram and focal with that kernel? Curious if ktoonz fixed that, he had it fixed in 10.1 a couple months ago
[Verizon Samsung Galaxy S III] mastamoon:
It's always been that way and is why i bought Lux.
[Verizon Samsung Galaxy S III] ugachris:
Gotcha. Was just thinking that's controlled by an array somewhere.

Edit: Wow, hadn't heard of Lux. Looks much better. Thanks!
[Verizon Samsung Galaxy S III] khymbote:
Was looking real quick. Focal worked the first time I shot like 30 test photos. I tried again and it wouldn't do much.
[Verizon Samsung Galaxy S III] airmaxx23:
It freezes and force closes with the rear cam, it freezes to a black screen and the phone make a buzzing sound until I pull the battery with the FFC.
[Verizon Samsung Galaxy S III] cornelious1212:
Everyone's MMS is OK except mine I'm assuming since I haven't heard about it?
[Verizon Samsung Galaxy S III] mastamoon:
So after candy crush closed on me I didn't reset my phone. Watched a couple episodes of workaholics and then tried to play again. This time it closed on me within 15 seconds. After that any app I opened would close automagically within about 10 seconds. I grabbed a couple logs that I'll have to look at on Monday.

This has to be a memory/buffer issue.
[Verizon Samsung Galaxy S III] Hans5849:
What's the website for cyanogenmod accounts? Find it on my phone, but not my pc web browser.

Anyone having a problem with Swype not putting a word in, or jumping up a line when typing?
[Verizon Samsung Galaxy S III] GideonX:
https://account.cyanogenmod.org/login
[Verizon Samsung Galaxy S III] Hans5849:
Also I'm not getting notifications for text messages when the screen is off, I thought this was fixed. Today's rom.
[Verizon Samsung Galaxy S III] mastamoon:
Just text messages? You get other notifications with screen off? Make sure you SMS notification tone didn't get changed to none or unknown.