yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] Fivecent:
I also wanted to report that I am unable to receive calls on 8.2, however I can make them.
[Verizon Samsung Galaxy S III] dpeeps74:
Yeah, I was able to make a call but couldn't hang up.
[Verizon Samsung Galaxy S III] Blaiser47:
I too can confirm that i cannot hang up calls. First I tried to dirty flash over 8.0 and couldn't hang up. Of course then I tested this on a clean flash. I did a full wipe and then simply flashed 8.2, latest full beta gapps, and did nothing but try to make a call. It went through but i could not hang up. Flashed back to 8.0 and it is still working flawlessly so thanks for that amazing build!
[Verizon Samsung Galaxy S III] Perseus:
Welcome back. I wondered.

All, please be kind and tell me your Baseband Version. Also be kind and tell me if it corresponds to Verizon's 4.2, 4.3 or 4.4 (Did you get 4.4 ?:p). I have T-Mo and have no clue of Verizon's version Numbers.
[Verizon Samsung Galaxy S III] gadgetguy08:
Using ML1. It is from early this year. I did read something about needing NE1 (from mid-year) for some reason but didn't pay too much attention. I guess maybe I should have.[emoji5]

I'll give that a shot later.

Thx
[Verizon Samsung Galaxy S III] dpeeps74:
Same, ML1. I did see something somewhere about CM and NE1. I haven't seen an NE1 modem zip but I haven't looked either.
[Verizon Samsung Galaxy S III] Perseus:
Please can you guys point me to the Link where this subject of needing a specific Modem for CM ? I'd assume it should not be the case. You don't have to update just because of this issue. we can resolve this even otherwise.

Sprint guys with 4.4.2 Modems have the same issue as you.
[Verizon Samsung Galaxy S III] gadgetguy08:
http://xdaforums.com/showthread.php?p=55765286
[Verizon Samsung Galaxy S III] Fivecent:
I'm currently on the BMB1 radio because I was running into the glitch where you can only send one SMS message without having to reset / cycle airplane mode.

Haven't tried to update to NE1 as every radio after BMB1 caused the error.

Edit: BMB1 is a very old radio. I think from 4.1.
[Verizon Samsung Galaxy S III] Perseus:
Thanks, Perhaps someone can try that Symlink work around

adb root adb wait-for-device remount adb shell ln -s /firmware-mdm/image/modem.b05 /system/etc/firmware/modem.b05 adb reboot
[Verizon Samsung Galaxy S III] ryanstfl:
I'm on ML1 also, I don't know how to update to the other radios (I looked and I can't find them) but I tried this and it doesn't really do anything. I can still place calls(and unable to hang up) but I can't receive them. The symlink isn't helping.
[Verizon Samsung Galaxy S III] savagebunny:
I'm actually on NE1 and encountering the same issues as others. Both baseband and firmware is NE1 on my phone
[Verizon Samsung Galaxy S III] ryanstfl:
How did you get the NE1 baseband/firmware?
[Verizon Samsung Galaxy S III] savagebunny:
Downloading it off of here, and I think it was on rootzwiki, and flashed it

EDIT: I could be wrong, I think I'm on MF1 firmware
[Verizon Samsung Galaxy S III] Perseus:
Yes I tested another build overnight with that. I will check further.

I don't think this is related to the Modem. All modems should be okey.

http://www.invisiblek.org/firmware/d..._NE1_modem.zip (flash in your favorite recovery)

Remember I don't have D2VZW. So not particularly endorsing it. Do note, without correct baseband others had bricked while flashing modems on D2ATT. Check the General Section for details.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
You would be on VRBMF1 4.1.2 firmware at the latest, 4.3 firmware would lock you down. Only 4.3 modems are safe to flash. I'm on VRBMB1 firmware cuz I can't send texts on anything newer than that. I've been hoping the devs still supporting the S3 would fine a sure fire way to resolve that issue.
[Verizon Samsung Galaxy S III] Perseus:
Post that on Slim Gapps thread. there's a resolution to Hangouts issue.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
I just did a search in the Slim gapps thread for "sms" and there were only 3 posts in that thread with that included. Nothing pertinent when I searched for "text" either. I also uninstall Hangouts when I flash SlimKat.

My issue is the same one that's AOSP wide on the S3 but only some are experiencing. When using VRBMF1 firmware, ML1 modem, and or NE1 modem, I can send one text then all subsequent texts that I send fail instantly. If my texts all work properly after initial flash, they all start to fail again once I reboot. Only solution is to use VRBMB1 4.1.2 firmware on AOSP.
[Verizon Samsung Galaxy S III] savagebunny:
Yup no issues with my modem. Just the massive Gapps wakelock issue that just started recently. Last time I think it was Google causing it because I'm using the same gapps and rom flash and wakelocks are a bit crazy
[Verizon Samsung Galaxy S III] Fivecent:
Exact same problem I am experiencing. I didn't flash 8.0 so I didn't see any problems there, but I still cannot make calls on 8.2.

I've flashed back to 7.8 and everything seems to be functioning normally.

Really hope this doesn't turn in to EOL for the device.
[Verizon Samsung Galaxy S III] savagebunny:
Anyone have a idea what this wakelock is? Killed my phone overnight..

PKT_CNT_SAMPLE_INTERVAL_ELAPSED
[Verizon Samsung Galaxy S III] vmbray:
Is there a way to have the better nav bar setup? On the old slim you could tweak the nav bar - specifically having the edge menu button but now its the basic nav bar. Great ROM though running well!
[Verizon Samsung Galaxy S III] Perseus:
Typically when some app is counting down time to the next check. Post your BBS Log on BBS thread or here.

There is a workaround to this issue, the Symlink that makes it compatible with older modems. I am testing that in an intermediate build.

Not happening on my watch. I was offered a free Nexus 5. Turned down because I want to support this device.

Theme engine is on hold due to Android L.
[Verizon Samsung Galaxy S III] vmbray:
Okay thanks for the info!
[Verizon Samsung Galaxy S III] savagebunny:
Well here is the BBS log. Also pulled the logcat if needed.

https://drive.google.com/file/d/0B17ruQH_mzndQ1A0dkNrRDhfNGc/view?usp=sharing
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Hmm, that sounds promising! Definitely keep me updated on that.
[Verizon Samsung Galaxy S III] dodgem2012:
I've stayed on 7.6 because I've seen a few problems with the newer builds and I'm still back at VRBLK3 modem, and I do not have any problems with SMS, phone calls or texting.

Should I go with the newer modems or stick with what is working?

Is there any advantage with anything, network speed or LTE in going with the newer modems?
[Verizon Samsung Galaxy S III] gadgetguy08:
I would wait on the next weekly build. before messing with the modems. Devs are working on fixing the issues.
[Verizon Samsung Galaxy S III] dpeeps74:
While there can be potential improvements, in my own experience across 3 phones, many modems, and versions of Android, your signal/speed almost entirely depends on your location.
[Verizon Samsung Galaxy S III] Perseus:
Guys,

Please need a quick turn around on this. Typically I won't do this. But I need a quick test and result.

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

With this build, this issue of calls (not ending or not receiving and so on)should be resolved. Please test for that one issue only. Let me know what happens. It doesn't matter what modem you are on. If you still have issue, post if you are on latest modem or not. Don't upgrade your modem.

Unfortunately if I am to include the fix in next weekly, I need the result before 10-05-14 3 PM CST.
[Verizon Samsung Galaxy S III] ryanstfl:
It works. I upgraded to the newest modem NE1 before you released this build.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
I am on VRBMB1 4.1.2 firmware (this pre-dates VRBMF1 4.1.2 firmware), I was able to receive phone calls and call out each time over 8 calls to my home line and 8 from my cell. Then, I pulled my sim card reinserted it, and made 8 more from my cell and 8 more from my home line. For each call, I had my iPod playing music so I could verify on the line that some audio was coming out. I was able to hear out 28 of my 32 calls but on maybe 4 calls from my cell, my call was interrupted after the first dial by an automated response prompting to dial 3. No clue what that was about. I could not test with loud audio since its early morning in VA and I'm leaving for work soon. Good luck if anyone else tests this out!
[Verizon Samsung Galaxy S III] Perseus:
Thanks Guys. That's really priceless!!
[Verizon Samsung Galaxy S III] LegoFarmer:
So what is going on with the gapps wakelock stuff? Has it been fixed?
[Verizon Samsung Galaxy S III] NMEAGENT:
I can't seem to find the HDR mode in the stock Google Camera app
[Verizon Samsung Galaxy S III] savagebunny:
At least I'm not the only one having gapps wakelock issues

Also, I'm getting "Cannot connect to camera"

Use to work in 7.8, then I re flashed 7.8 and it's broke, also in 8.2 weekly and 10/04 build for me
[Verizon Samsung Galaxy S III] Perseus:
Please post in [GAPPS][4.4.x] Official Slim GApps TRDS (Slimkat) so that Dankoman can assess.

Are you talking about Camera App that comes with the Rom or Google Camera app from Play Store ?

Have you done clean flash and tested camera ? Typically this happens when you restore data to some app that uses camera.
[Verizon Samsung Galaxy S III] Cmotion:
Has anyone tried 8.4 yet? Has the phone/mms problem been fixed? I tried the test build that was posted on here the other day, and while it fixed my phone issues, it caused my Play Store to go completely wonky. It would just keep trying to load it, like it was looping, but could never actually open it. Tried clearing data in the app, rebooting, reflashing the ROM... Nothing seemed to fix it. However, Perseus said to test ONLY in regards to the phone issue, plus I dirty flashed, so could've been on my end. Anyway, have always loved Slim and am hoping to hop back on if the whole "not being able to use your phone as a phone" is fixed. ;) Not that I really even use it as a phone much...
[Verizon Samsung Galaxy S III] Perseus:
[MENTION=2719317]Cmotion[/MENTION]

To All

Please use the following as your Current Weekly 8.4

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

Just for this once, keep aside the 8.4 posted on Slim Website.
[Verizon Samsung Galaxy S III] Cmotion:
Is that the same test build you posted the other day?
[Verizon Samsung Galaxy S III] Perseus:
Yes it is.
[Verizon Samsung Galaxy S III] savagebunny:
Yes I've done a clean flash and not restore any old data. Wiped sdcard, system, cache, dalvik etc multiple times before I flashed a new build
[Verizon Samsung Galaxy S III] Perseus:
Time for you to go back to Stock and replace corrupted Camera Driver. Come back to the Rom after Stock firmware has taken a couple of pictures. While there, make sure you do take a GPS Location check.

Really ? Read the post above yours ?
[Verizon Samsung Galaxy S III] savagebunny:
Can i still make a nandroid backup of the current flash I have, then restore it once I'm done, or will I have to do another clean install of AOSP after I do this?
[Verizon Samsung Galaxy S III] Perseus:
No nandroid. Clean all the way.

You may take a Titanium backup and selectively restore certain Apps' data. No mass restoration. You *could* do an nandroid andthen use Nandroid Manager to selectively restore apps and their data out of it.
[Verizon Samsung Galaxy S III] savagebunny:
Well... I tried but my phone refuses to boot into the ROM I flashed over... and since I have a malfunctioned power button and I removed it.. I can only get into ODIN. Not sure how to get back into recovery without a power button
[Verizon Samsung Galaxy S III] Perseus:
After Stock you need to factory Reset before flashing new Rom. Use Quick Boot for Getting to Recovery without Power.
[Verizon Samsung Galaxy S III] savagebunny:
That's what I was going to do. I flashed a stock ROM to the phone, but i was failing to boot. So when I went to reboot, I couldn't get into recovery past that point. I was able to jump start it, trick it going into recovery and now I went back to Slim until I get it fixed again.

Since I'm NE1 baseband, what ROM should I flash, don't wanna get stuck in a bootloop again
[Verizon Samsung Galaxy S III] Perseus:
Flash Stock NE1 via Odin. Don't use the No-WIPE version in General forum.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
I sincerely hope that you did not flash 4.3+ in Odin! VRBMF1 4.1.2 is the most recent OTA that can be safely flashed via Odin then bootloader unlocked. Any and every update beginning with 4.3 has locked our bootloader permanently so you will be limited to TouchWiz dual booting via Safestrap. Idk if you have followed Perseus' advice as its been 3 hours since the last reply.

No! Do not do flash this at all!! See above.
[Verizon Samsung Galaxy S III] Perseus:
Thanks for letting me know. Guess downsides of having a T-Mo Variant.
[Verizon Samsung Galaxy S III] savagebunny:
Hey there, I did not go ahead and flash that route. I rarely ever use my Camera so it's not a big issue right now, I just wanted my phone working so I could make my texts/calls earlier so I went back to what I had before.
[Verizon Samsung Galaxy S III] infsoul:
Any one know why every

ROM I flash since 8.0 weekly leaves me with no data all other features of several latest ROMs work but no data on any help please
[Verizon Samsung Galaxy S III] capt730:
Slim, I had to be on MB1 like you for the longest time. Since the late September builds on CM and AICP I have been able to use the MF1 firmware and NE1 modem. So it very well may be the symlink change that has been the fix. Hopefully it works for this rom too.
[Verizon Samsung Galaxy S III] Perseus:
Does this happen with the build I posted yesterday ? Make sure to do clean flash and no custom kernels.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
I am definitely happy to hear that. I follow our CM threads and must have missed this being discussed/resolved. Hopefully the symlink change works here.

[MENTION=3639717]Perseus71[/MENTION],

Does the 0804 weekly that you posted in this thread last night contain the symlink change(s) that you were testing in your own time?
[Verizon Samsung Galaxy S III] infsoul:
It is happening on any ROM. / within the last so many weeks that have been coming out for several different groups after wiping everything except for my SD i first always make a backup so I can restore but everything works except for my data on for example gummy an du and liqsmt
[Verizon Samsung Galaxy S III] Perseus:
Yes it does. That Symlink is supposedly allowing older firmware users to use the Rom.

How about this old version ? I want to know the last known working version for you.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Could you post the commit that addresses this symlink? I was curious if there's something I am doing wrong. I flashed VRBMF1 firmware and my texts were working until I rebooted and pulled my sim. I'm curious if I need a specific modem in combo with VRBMF1.

Edit: Am I supposed to run this terminal command posted by Invisiblek to activate the symlink?
[Verizon Samsung Galaxy S III] Perseus:
http://review.cyanogenmod.org/#/c/72689/2/Android.mk

Don't believe you need to run that in Terminal. The commit is supposed to do the same. Review that entire page on Invisiblek's thread.
[Verizon Samsung Galaxy S III] capt730:
Once they fixed the bluetooth issue (audio on incoming calls), I flashed the MF1 AIO and then the NE1 modem while on Stock-Rooted MF1. Then flashed CM, I want to say around 9/25 or 9/26. Been working fine ever since.
[Verizon Samsung Galaxy S III] infsoul:
You flashed the modems how from recovery?
[Verizon Samsung Galaxy S III] capt730:
Yep. Just flash the modems in recovery

---------- Post added at 11:35 PM ---------- Previous post was at 11:31 PM ----------

Here is a link for the modems and and AIO if you need them.

http://xdaforums.com/showthread.php?p=55609728

[ROM][Official][4.4.4] CyanogenMod 11.0 Nightlies for the Verizon Galaxy S3
[Verizon Samsung Galaxy S III] lvgdgts:
Thanks for posting that link as I've been thinking about changing to the newest firmware/modem.

I know I'm being lazy, but is there anything special that needs to be done before flashing these in recovery? I'm not going to lock my phone, am I?
[Verizon Samsung Galaxy S III] Shakes The AssClown:
Yep me too...no issues either. :)
[Verizon Samsung Galaxy S III] msternig:
I am currently back a few versions of Slim4.4.2 build 4.1, on baseband MF1. In order to safely update my modem (hoping for better reception), are you saying that I should install the MF1 Firmware/modem (https://mega.co.nz/#!RVAGHRDC!boUFGD..._VjSUbwLvirGVU) and then install the NE1 Modem (https://mega.co.nz/#!cIY2AKJC!yPboi6...4G5LeKzm81DUs4)? Are these compatible with 4.4.2 or would I need to update Slim to one of the more recent versions (4.4.4 7.0 stable for example). Thanks!
[Verizon Samsung Galaxy S III] SlimSnoopOS:
If Settings/About Phone/Baseband states VRBMF1, then you're already using VRBMF1 firmware which includes modem, trust zone, rpm, bl1, and bl2. Just flash the VRUDNE1 modem, by itself, if you want. You will need to flash the VRBMF1 firmware if you have issues with VRUDNE1 modem.
[Verizon Samsung Galaxy S III] msternig:
Before I try to update the modem to NE1, I can't find any documentation on what advantages this version brings to the table (other than being new). Any insight or posts out there that I should read? Other posts referred to the NE1 modem causing people to lose root. It sounds like this would not be the case, but I thought I'd ask to be sure.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
I don't believe there's any info in one place, more like in various threads. You could start in Invisiblek's firmware thread then look at a few of the AOSP threads and search for VRUDNE1or NE1. Haven't heard about losing root when flashing the modem, just differing opinions on the quality of signal strength. I've only been using the VRUDNE1 modem for two days so I can't speak to it.
[Verizon Samsung Galaxy S III] dpeeps74:
I personally have never seen a newer modem provide any real benefit across multiple phones and carriers. That being said, at this point, the advantage seems to be the ability to update roms :)
[Verizon Samsung Galaxy S III] SlimSnoopOS:
I mean to be fair, I've been using every build of SlimKat with the VRBMB1 firmware just fine. I just prefer the latest firmware installed, VRBMF1, when I'm running roms. Thankfully, I can do so again!
[Verizon Samsung Galaxy S III] msternig:
Thanks for the input... I am thinking since there is no real advantage and my build is working fine, I'll leave well enough alone. At some point, I may update to a 4.4.4 build of Slim, but the more recent ones appear to have a few issues keeping them from being really "stable". Slim build 4.1 (4.4.2) is what I am on currently, unless anyone can suggest a solid 4.4.4 build... Anyone? Buhler?
[Verizon Samsung Galaxy S III] Perseus:
We are making Changes so that this whole issue with Calls is resolved.

When the Build Says Weekly, its not a Stable is it ? If you have issues with a Stable Release, then we can talk. When you flash a Weekly, you know those ARE expected to have Bugs. Ever Wonder why we did not release a 8.0 Stable ?
[Verizon Samsung Galaxy S III] msternig:
I understand the difference between the builds (weekly vs. stable), but I thought I recalled people having minor issues with the latest stable (7.0) and bluetooth which was fixed in weekly builds (7.6 i think). Would you recommend using 7.0 stable, or one of the more current weekly builds as a solid and updated daily driver? Otherwise, I may hang around for the next stable build to see what it has in store. Thanks!
[Verizon Samsung Galaxy S III] SlimSnoopOS:
[MENTION=3639717]Perseus71[/MENTION],

Consider me a fan of the sms symlink changes! Over the last 48 hours on your custom 8.4 weekly with the sms symlink changes, I have successfully been able to use sms and carry on hours of conversation through reboots and pulling my sim card. On all older builds, when using VRBMF1 firmware, texts would fail for me after one was sent. With VRBMF1 firmware and VRUDEN1 modem, I have rebooted multiple times and pulled my sim, heck even flashed a custom kernel and I'm still good. If an sms failed, I sent it again and it easily went through :highfive::good:
[Verizon Samsung Galaxy S III] capt730:
I am glad to finally use the newer firmware and modem. While I don't see a difference in coverage or reception, I have noticed a little better data speeds. Maybe it's just me or maybe it's the XLTE devices running on the XLTE instead of LTE.
[Verizon Samsung Galaxy S III] Perseus:
Use either 8.4 Weekly I linked earlier. (Not the one of Slim Website) Or use 7.4 if you have it.
[Verizon Samsung Galaxy S III] SkinnyT:
I used to be able to use Google wallet on my vzw sg3 but haven't used it in awhile. I tried today but it did not seem to work. I thought it was supposed to be working in all kitkat devices by now. Am I wrong?
[Verizon Samsung Galaxy S III] helobubba88:
I believe GW tap and pay only works on stock TW 4.4 ROMs.
[Verizon Samsung Galaxy S III] yamaha_wins:
I called Verizon today from my cell, I was told they could tell my phone was rooted.. Is this not illegal for them to remote into my phone or whatever they guy did without asking first?

But really all he wanted to do was keep reminding me that both of my unlimited data lines are due for a upgrade..
[Verizon Samsung Galaxy S III] Mystique:
Social engineering..

You answered things he asked in a way that gave him more information than you thought..

Sent from my GT-I9505G
[Verizon Samsung Galaxy S III] yamaha_wins:
That isn't true. He ran Mobile diagnostics on my phone without asking. Then remote into my phone somehow, he knew what apps I had on my phone. All I did was ask if my phone was still covered under warranty. He said no being its showing as being rooted.. Of course I denied it.
[Verizon Samsung Galaxy S III] markapowell:
Just updated to 8.4 weekly and I can't receive calls. I can make them. Did a full wipe before install.

Rebooted. I can use spotify and send and receive messages. So the network is there. Just can't get calls.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
See below for the proper 8.4 download. Calls been working fine for me over the last week of use.
[Verizon Samsung Galaxy S III] markapowell:
Am I just installing or am I doing a full wipe? Now my only concern is there is still a 7.0 stable. Did we jump to the 8.0 on the betas without an 8.0 stable?
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Full wipe. There is an 8.0 release, but its placed on the weeklies page. Based on that, I don't believe 8.0 was viewed as stable for us. That's more of a question that Perseus would have to answer. It ran fine for me, so did 8.2 as well.
[Verizon Samsung Galaxy S III] Perseus:
I believe this is due to the Extensive CSC Data collection VZW does via their apps. I believe there's a good deal of discussion about CSC and privacy in General Section.

+1. 8.0 was not released as stable due to Call issues for some of us.
[Verizon Samsung Galaxy S III] AdMire:
What's the word on 8.6? Good to go?
[Verizon Samsung Galaxy S III] dpeeps74:
No data for me on 8.6. I wiped system/dalvik/cache. Stock kernel. I'm on MF1 firmware with NE1 modem. On the last build posted here by [MENTION=3639717]Perseus71[/MENTION] (10-04) everything seems to work fine.

* I lied and remember why I was on 8.0 before. The 10-04 build I can't send MMS but data works fine and I can receive MMS . On 8.0 everything works flawless for me.
[Verizon Samsung Galaxy S III] motocrossmann:
No mobile signal at all for me on 8.6. The indicator just shows blank. MF1 firmware, NE1 modem.
[Verizon Samsung Galaxy S III] dpeeps74:
For what it's worth, I tried it with ML1 modem on 8.6 and no data there either.
[Verizon Samsung Galaxy S III] AdMire:
Damn.

Question, though: when you flash the ROM, in order to get the NE1 modem, do you flash the MF1 firmware AIO THEN the NE1 modem or just flash the NE1 modem after the ROM and Gapps? Right now I just flash the ROM and Gapps, that's it. Could I flash the ROM, Gapps, then the NE1 or do you need the MF! AIO, first?