yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] tvl76:
Dirty flashed 8.9 from 8.0.

So far everything works for me, including GPS !!
[Verizon Samsung Galaxy S III] Perseus:
REEEEALY ? Are you Sure ? Please make sure you have set GPS to DEVICE ONLY and then reboot before rechecking. The "battery saving" triangulation via Wireless and Cell tower does work. The Device Only mode does not.
[Verizon Samsung Galaxy S III] MMag05:
Bluetooth Issues

Having difficulties reestablishing a connection to the stereo in my car. On the initial setup it works great but when the car is turned off the next trip bluetooth crashes when trying to reconnect. Only fix seems to be to delete and reestablish the connection on both the stereo and phone every trip I take. I really want to love this ROM, as everything else is amazing, but really buggy bluetooth is a deal breaker for me. This is the first non touchwiz ROM I've used on this phone and never had the issue before. On the log file the issue should start somewhere around 16:55 to 17:05. I'm running the Stable 7 build on a clean install any help would be appreciated. Thanks
[Verizon Samsung Galaxy S III] tvl76:
Sorry, I lied. I didn't think of switching to device only. Forgive me. Does not work as you stated.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Appreciate the heads up on this. I flashed 8.9 weekly around 2p and can confirm that I was not able to obtain a GPS lock on wifi or 3g/LTE nor was I able to send sms. I was initially on VRUDNE1 modem/VRBMF1 firmware combo and also just VRBMF1 firmware. GPS Test verified no GPS lock the entire time, even after clearing AGPS data and updating AGPS data. I'm going to try flashing again tomorrow night and trying it again.
[Verizon Samsung Galaxy S III] dpeeps74:
I'm on weekly 8.0 and no Bluetooth issues for me with my jvc. I'm also on the NE1 modem and using BMS kernel fwiw.
[Verizon Samsung Galaxy S III] MMag05:
Still Persisit

I appreciate the suggestion but unfortunately the problem still persist. I just did a clean install of 8.0 w/ BMS kernel and I already had the NE1 modem.
[Verizon Samsung Galaxy S III] Perseus:
You Log shows some Messaging app or your Stereo's Text read capabilities are competing with Spotify. Either that or the A2DP on the Stereo isn't playing nice with D2LTE's Modem.

First off Remove the pairing on phone. Remove all entries of your phone from the Stereo's saved devices. That done, reboot phone. Please turn off other capabilities over the bluetooth except audio. Then Pair both devices and then wait for any subsequent questions that will pop up including access requests by the Stereo to your Contacts and what not. When that's completed, turn off car and then reboot phone.
[Verizon Samsung Galaxy S III] msolaw:
I have the weirdest thing happening. I'm on stable 7 and have been for quite a while. It's worked perfectly until a couple days ago and now I can't send text messages out. I think I can receive OK. Just can't send out. I've even tried doing a clean install of this and other ROMs with same result. It gets more odd... After toying with it I can send only one text out. Just one to any person. But I can't send another unless I reboot or I think wait a few hours. Upon reboot I again can send only one text message out. And so on. I have no clue what could be happening. Any ideas?
[Verizon Samsung Galaxy S III] SotYPL:
Downgrade your modem to VRBMB1. It's working fine for me with 7.0 stable and had the same problem on VRUDNE1.
[Verizon Samsung Galaxy S III] msolaw:
I think the modem I am on is VRBMF1. Is that maybe what you meant? I'm not sure if you had a typo in your message or not.....
[Verizon Samsung Galaxy S III] SotYPL:
No, I meant VRBMB1. VRBMF1 was released later.
[Verizon Samsung Galaxy S III] msolaw:
Alright, thank you, I apologize for my confusion. Is there a link I could follow that would let me download the needed files and explain how to do it? I don't think I've done anything with modems or whatever, I'm pretty sure this is just what I've always had. I can do the flashing of ROMs and such obviously, but modems or whatever I'm a bit clueless on. I feel like maybe I did it once on my old phone, the incredible 2, but never with my s3. Help/suggestions? Thanks for any insight...
[Verizon Samsung Galaxy S III] SotYPL:
Google is your friend:

http://fs1.d-h.st/download/00114/sKj/VRBMB1.aio.zip

Just flash it in recovery as everything else.
[Verizon Samsung Galaxy S III] majixx11:
I'm on MF1 and stable 7.0 is fine. Been using this combo for 2 months with no issues if that helps anyone
[Verizon Samsung Galaxy S III] Perseus:
Please Can we get back on Track ? A quick Q&A is okey about the firmware. Let's not drag it please. there's always Verizon Galaxy S III General with a whole bunch of Firmware threads.
[Verizon Samsung Galaxy S III] Stealth111:
I just want to thank you for this awesome rom! For the first time in a LONG TIME, my phone works perfectly again!

Sent using Tapatalk
[Verizon Samsung Galaxy S III] rhcreed:
gapps?

I'm leaning toward moving to this rom from another rom I use on my S3, can I still use these gapps?

http://xdaforums.com/showthread.php?t=2397942

Or do I have to use a certain set?

Thanks!
[Verizon Samsung Galaxy S III] Perseus:
You certainly can use the Gapps you want. Please note, the TRDS Toggle won't be applicable to the Gapps that you will use. It only applies to Slim Gapps.
[Verizon Samsung Galaxy S III] MI95SHO:
Perseus71, any luck with getting GPS and the other bugs working in 8.10? Still running 7.9 and due for an upgrade :D

Thanks for all your hard work
[Verizon Samsung Galaxy S III] Perseus:
Its a long and hard journey but our knight in Shining Armor, [MENTION=4408910]nicklovell23[/MENTION] is untiring. Its kind of a friendly competition between us 2. And I think he's going to win!

We are testing a fix. I might Re-Host a test build later today if anyone is interested. I am particularly interested with this variant as you guys have been hit badly with LTE, MMS and other issues.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
I'll be at work until late tonight but I wouldn't mind testing this out starting tomorrow. Count me in :highfive:
[Verizon Samsung Galaxy S III] Perseus:
OK so here goes.

https://www.androidfilehost.com/?fid=95784891001606615

GPS should work. Data is already working. Oh and do tell me if Making and Receiving calls are okey with it. So too Bluetooth. I do not anticipate problems but it would be good to have someone confirm.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Freshly downloaded and about to flash in an hour. I'll test this one out tomorrow! Thanks for the test build.
[Verizon Samsung Galaxy S III] tvl76:
By gumm, I think we have it. Flashed this AM and have GPS lock. Thanks man !!

Edit 1: I think YOU have it, not WE.
[Verizon Samsung Galaxy S III] AdMire:
I flashed 8.10 last night and so far, no issues!

Although does any see a very slight delay when waking the phone up?
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Same here! GPS locked super quick on WiFi and fast enough on LTE after a reboot. GPS Test finds me within 20 feet as well.
[Verizon Samsung Galaxy S III] dpeeps74:
Thank you! I just flashed this as well. I can make/receive calls AND hang up from them, I get lte, I can use device only in location settings and find myself on maps. I've only had it going for about 10 minutes but I'm off and running with it. I'm running the NE1 modem fwiw and wiped system and caches only from build 8 in case anyone sees different than we are.

Send/receive MMS works fine as well!
[Verizon Samsung Galaxy S III] matt_man:
Just clean flashed the latest unofficial nightly on my sch-s968c. I can now place and end phone calls but I still don't have data or GPS. I can provide a log file if that would be helpful.
[Verizon Samsung Galaxy S III] Perseus:
Please do
[Verizon Samsung Galaxy S III] matt_man:
PM'd you.
[Verizon Samsung Galaxy S III] Perseus:
Got it. Seems like its looking for an APN that's not there. Can you tell me what APNs are available ?
[Verizon Samsung Galaxy S III] matt_man:
If you are asking for APNs available in the system settings there are none listed. If it would be helpful I could send you my stock apn-config.XML file.
[Verizon Samsung Galaxy S III] Perseus:
Yeah that's what I suspected. Please tell me you do have your IMEI intact on the Settings >About screen right ?

Think we have a fix. Another user on ATT has similar issue. Please stay tuned.

Completely different question, do any of you see a large wakeups from A Data-Stall alarm of com.android.phone ? typically you'd see this on BBS.

I am sorry if you don't know what I am talking about, then you'd need to visit BBS thread to get basic concepts.
[Verizon Samsung Galaxy S III] Droid316:
All working good here so far, it's been about ten hours
[Verizon Samsung Galaxy S III] matt_man:
Yes IMEI is intact.

Thanks for working on this.
[Verizon Samsung Galaxy S III] matt_man:
I could have been wrong about GPS not working. I just tried GPS on stock and didn't get a lock until I went outside. O didn't try GPS outside with Slim installed.
[Verizon Samsung Galaxy S III] Perseus:
Yep. Happened to me too initially. The Satellites are finicky.

EDIT - If you see flaky LTE, please check your Preferred Network Type. Make sure its set to LTE.
[Verizon Samsung Galaxy S III] AdMire:
So is anyone else not able to connect to Play/Email, etc? I get:

I actually don't even see the Play Store app/icon. I re-flashed the latest Slim ROM and Gapps and still nothing.

Even if I try and flash the play store (from Gun) it's not there.
[Verizon Samsung Galaxy S III] thelangosta:
I had play store and gmail working but couldn't get calendar sync to work at all.
[Verizon Samsung Galaxy S III] AdMire:
But you have the play store icon? I don't have it and can't get it. More-so I just wanna see if I'm the only one with this problem. I flashed the new Slim on Monday and swear it was all good then...

---------- Post added at 07:30 AM ---------- Previous post was at 07:27 AM ----------

So after further review, I went to the play store thru the browser and under settings>devices my current "device" says MODEL:SCH-I353 and then under CARRIER it says "No Carrier" while underneath that, it says Verizon Wireless for the rest of the Carrier's down that column.

AND under my account on my phone, it says "Sync is currently experiencing problems. It will be back shortly."

So if Sync is down, would it remove my play store app?
[Verizon Samsung Galaxy S III] dpeeps74:
In my experience, I usually see those kind of problems when I don't wipe data. My guess is because between my flashes there were updates to play services or other apps and so there's some sort of mismatches occurring. In the slim gapps forum I think the OP has some steps that sometimes resolve it. I also once stopped having issues simply after rebooting. Beyond that, I used the latest beta gapps and wiped system and caches and I'm not seeing any issues.
[Verizon Samsung Galaxy S III] AdMire:
I clean flash all the time. The only thing I can think is I was originally using gapps by banks from like August but never had an issue. I'm going to clean flash/wipe data right now and reflash it all, see what happens using SlimGapps this time.

Edit: I'm good for now, thanks all. The clean flash did do the trick. I wonder if Banks old ass Gapps was conflicting somewhere in my phone which was causing that error.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
I'm seeing this same issue as well. GPS works after a reboot but later on it does not. Also, GPS Test fails to get a lock at all but Google Maps appears to get a lock once I'm outside after several minutes. I'll be out and about tomorrow so I'll see how GPS behaves then.
[Verizon Samsung Galaxy S III] Perseus:
Here's the thing, The new code is directly accessing the GPS Receiver chip directly on the motherboard. This bypasses the Library layer Rom had before on top of the Kernel. The advantage is that your positioning is more accurate and reliable.

Unfortunately it forces you to go get a clear line of sight to at least 3 Satellites. Previously, the Libraries used to make an approximate Guess using Google Location Libraries. That guessing did not need 3 satellites. One was good enough.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Hmm, interesting. I have been stuck in the house the last few days so I wasn't sure how much GPS was affected until I read y'all posts. Your explanation does make sense. Everything else has been working fine to my knowledge, LTE (well, 3g since I live in low signal area lol), sms, and calls.
[Verizon Samsung Galaxy S III] tvl76:
I'm in Cornville, AZ right now. Switched to device only, cause there is no WiFi or strong mobile network out here, and the satellite s see me just fine.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] millwood:
I thought I was losing my mind this weekend with the GPS issue. I usually never have problems and go figure it happens when we were leaving out of town and need directions. I just downloaded the test ROM. I will give it a shot and thanks for all the hard work.
[Verizon Samsung Galaxy S III] Perseus:
To All:

Please note, in the upcoming Weekly, there are 2 Changes of note. So you may want to observe in your current setup before flashing. Dirty flash is okey.

For those of us on LTE, you may see a small change in network speed. Hopefully higher. So might want to do speed test before flashing.

One of the Alarms caused by com.internal.telephony, AKA the phone app, is quieted down. Hopefully this saves a little battery for you. You can see for yourself on BBS Alarm Section before and after.
[Verizon Samsung Galaxy S III] SkinnyT:
I'm running 8.10 with the latest alpha gapps and no issues in the past two days. Gps is a little slow to connect but everything else is ok. The only issue I'm having is that Google Wallet crashes before I can open in. Any ideas on what that may be?
[Verizon Samsung Galaxy S III] SotYPL:
Latest weekly having problems with camera. Switching to video is working fine but after switching back to photos camera hangs and after relaunching is says "Can't connect to the camera". Also WiFi is not working correctly. It connects to ap with normal speed (108Mbps) but after some time it goes down to 5Mbps only.
[Verizon Samsung Galaxy S III] Perseus:
Please ask Dankoman in [GAPPS][4.4.x] Official Slim GApps TRDS (Slimkat)

Clean Flash ?
[Verizon Samsung Galaxy S III] SotYPL:
Yes. But you can discard comment about wifi. I went back to 7.0 stable and it's the same so either something is physically wrong with my phone or slimkat is acting weird for long time. I didn't notice it before but my stock Tab S is connected to same wifi at stable 108-150Mbps and doing 6MB/s. Phone connects with same speed but goes down to 5Mbps and 400KB/s as soon as I start to download/upload something. I have to check if it's doing the same at home, maybe it's not working fine with ap at work.

edit: it's definitely something wrong with phone or slimkat. I just created separate SSID for 5GHz at work's ap and phone connects to it at 150Mbps but after starting some transfer it goes down to 13Mbps and doing only 400KB/s. I will try to go stock TW to test it further.

edit2: That' weirdest thing ever. Going back to TW didn't help so I did some more testing. I have Peplink Balance One router at work and phone is having slow speed using built-in ap. I temporary installed some cheap 54Mbps ap and phone was doing 2.5MB/s so it was normal for 802.11g on cheap ap. My friend from work has S3 also (from t-mobile, completely stock) so I asked him to do some testing. Same thing happened on his phone, it goes down to 6Mbps and 400KB/s rate. For whatever reason S3 wifi is not compatible with Peplink ap. Tab S and iphone is working fine. I didn't notice it before beacuse I just switched to this Peplink equipment like 3 weeks ago and was using different access points before. I will double check that at home using Asus RT-N66U router.
[Verizon Samsung Galaxy S III] SkinnyT:
Everything is working fine now on 8.12
[Verizon Samsung Galaxy S III] SotYPL:
Did you check camera? Does switching to video and then back to photo work for you?
[Verizon Samsung Galaxy S III] SkinnyT:
I did. Everything works fine so far.
[Verizon Samsung Galaxy S III] SotYPL:
That's weird. Am I the only one who has problems with camera on this build?
[Verizon Samsung Galaxy S III] Perseus:
Please elaborate details of the issue.
[Verizon Samsung Galaxy S III] SotYPL:
I think I gave all details in my original post. Opening camera works fine and switching to video recording also. But switching back to photo taking is not working. Camera hangs after that and when try to relaunch it it says "Can't connect to the camera". Same thing with any other 3rd party camera app. I don't have logcat cause I went back to 7.0 nandroid. It was clean flash and no data restore was made before testing camera. Just some basic apps downloaded from play store.
[Verizon Samsung Galaxy S III] millwood:
I don't see any updates in the channel log for this device, unless I missed it somehow. Have there been updates to the GPS like were in the unofficial 8.10 release? Might only have this device couple more days, but still love it.
[Verizon Samsung Galaxy S III] Perseus:
Tried it. Just now. No issues on my d2. Do a one time. Trip to stock firmware.

Yes. There are updates.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
I tried this a few times and I was having no issues until I realized that you forgot to add "Take a video, then switch to take photos." I took a video, stopped it after 5 seconds, then tried switching to photo mode and the camera refused to open and force closed on me. All subsequent attempts to open it resulted in the "Camera failed to open" dialog and did not go away until I rebooted.

[MENTION=3639717]Perseus[/MENTION], attached is my logcat on SlimKat 12.01 weekly of the camera fail described above. I had to compress it due to file size limits on xda. I always do a clean install of each weekly and this was after a fresh reboot so nothing was in RAM.

Edit: This is with VRBMF1 firmware and VRUDNE1 modem.
[Verizon Samsung Galaxy S III] SotYPL:
I didn't even have to start recording. Switching to video was enough to kill camera for me.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Hmm. I wasn't seeing that at all until I recorded a clip. Either way, I should have it all recorded in my logcat
[Verizon Samsung Galaxy S III] Perseus:
Ok. Let me see. I do Ass-u-me :p you are talking about Slim Camera and not Google Camera right ?
[Verizon Samsung Galaxy S III] SotYPL:
Yes, I used stock camera first and after seeing this problem I downloaded google camera and got same error. Reboot was fixing it till next switch to video.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
haha yes, Slim camera that's included in the rom.
[Verizon Samsung Galaxy S III] Perseus:
Media Scanner borked. Dunno what's the circumstances.

11-14 08:57:55.907 1196 1918 W MediaScanner: Error opening directory '/storage/sdcard1/.android_secure/', skipping: Permission denied.

Continued looking........
[Verizon Samsung Galaxy S III] Blaiser47:
Also had this issue on clean flash. Plus, had a real hard time getting a GPS fix. I can provide a log later if need but maybe slimsnoopos is enough.
[Verizon Samsung Galaxy S III] sidthekid28:
if someone could please answer this.... if i am currently running 4.1.2 successfully on the mf1 firmware and ne1 radio and i upgrade to slim rom 4.4.4 here... will i be able to go back to my 4.1.2 rom just by restoring the backup i just made if i happen to be disappointed? or will i have to odin back to stock first and all that good stuff? thanks in advance...
[Verizon Samsung Galaxy S III] SlimSnoopOS:
You'll be fine to move between 4.1.2<>4.4.4. The problem is, once on JB 4.3+, your internal storage is moved to /0 so when you downgrade to JB 4.1.2 your rom will not have access to any data unless you manually move it back with a file manager. That's standard across ANY rom on JB 4.3+.
[Verizon Samsung Galaxy S III] sidthekid28:
thank you very much :)
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Not a problem Sid!
[Verizon Samsung Galaxy S III] samsgun357:
I'm having some weird issues. Like mentioned before camera fails (can not connect to camera) after using video. Also I can not play music. Google music, player pro, Pandora and another random music player all fail to work. Here's why this is so weird, I'm on stable 8.0, have been for awhile. The only thing I've updated is gapps so I have to assume its something in gapps causing these problems.

Stock kernel and MB1 firmware/baseband etc.

Watch, as I combine all the juice from my mind...
[Verizon Samsung Galaxy S III] Magicman500:
There was no 8.0 stable for d2vzw. The 8.0 weekly is far from stable.
[Verizon Samsung Galaxy S III] Perseus:
[MENTION=3576831]SlimSnoopOS[/MENTION] [MENTION=3537590]SotYPL[/MENTION] All.

Test this for me please

https://www.androidfilehost.com/?fid=95784891001611810

Think it'll resolve the Camera trouble. Consider this as the unofficial nightly for everyone else. The official nightly will have Camera trouble probably.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Appreciate it. I'll try this out this afternoon.
[Verizon Samsung Galaxy S III] Perseus:
Remember Do a clean flash only. Otherwise the problem will definitely repeat. Also you may want to make a trip to Stock firmware just in case Camera firmware is corrupted.
[Verizon Samsung Galaxy S III] SotYPL:
Same thing. Recording video works fine but after that I can't go back to taking photos. Camera hangs and after relaunching it says "Can't connect to camera". Clean flash and went back to tw AllianceROM before. Here is diagnostic report:

https://www.dropbox.com/s/hq45oifr7qpc6eb/bugreport.zip?dl=0
[Verizon Samsung Galaxy S III] Perseus:
Ok. Will look after work. Can't see now due to firewall.

EDIT - Please see CM's complaints http://xdaforums.com/showthread.php?t=2558946&page=80
[Verizon Samsung Galaxy S III] Perseus:
Those with Camera issue -

Would you care to test

https://www.androidfilehost.com/?fid=95784891001613033
[Verizon Samsung Galaxy S III] SotYPL:
Nothing changed. I even don't have to start recording video. Just opened camera, switched storage to sd card, switched to video and tried go back to photos. Camera hanged and not able to start it again without reboot.
[Verizon Samsung Galaxy S III] Perseus:
What happens when you don't switch to SD Card ?

Also I assume that was clean flash right ?

EDIT -

Oh By the way, came across this.

﻿

Thanks to

https://plus.google.com/104478942030...ts/5RmKn55eJjk
[Verizon Samsung Galaxy S III] SotYPL:
Same thing. Yes it was clean flash. I even tried to move all existing photos/videos to different folder, delete both DCIM folders (internal/external) and reboot as someone suggested in CM thread. It didn't help either.

edit: do you think that flashing TW based AllianceRom 23 is enough to check camera firmware issue or do I have to go to complete stock verizon rom? Anyway I don't think that in my case camera firmware is an issue because 7.0 stable is working flawless after restoring nandroid image.
[Verizon Samsung Galaxy S III] Perseus:
If restoring Nandroid works, then no need to go for Stock. Your firmware should be okey. The issue is with Camera Wrapper CM's using. Since we have a dependency, no way to revert without ripping out a lot of stuff.
[Verizon Samsung Galaxy S III] Droid316:
I went from slimkat to alliance Rom then back to slimkat now my camera won't save the pictures to my phone but a camera app from the play store will save the pictures why is that.plus my browser won't download files at all unless I use chrome browser instead of next browser.
[Verizon Samsung Galaxy S III] helobubba88:
Did you do a clean flash back to SK? You might want to do a factory reset after backing up your data.
[Verizon Samsung Galaxy S III] samsgun357:
I also tried a camera from the playstore. Initially it failed, I launched it again and it worked. Now suddenly both stock and google camera are working again, its very strange. I don't know why next browser won't work. My only suggestion would be wiping data for next browser and reboot.

Watch, as I combine all the juice from my mind...