yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] Swatpro004:
I flashed ML1 from MF1 and seem to have reduced my reception further. From what I read in another d2vzw modem page this is common, though I was unable to ascertain the reason. I'm also not sure if flashing back to an older modem is a) possible, or b) worth the effort.
[Verizon Samsung Galaxy S III] darklavalizard:
You can flash back to an older modem for sure. I flashed to ML1 after installing CM11, and too have noticed degraded reception. The reason I flashed is I heard it helped with scaling back the number of random reboots you might get. Tonight I'm going to flash back to MF1 modem and see if that helps my reception at all.
[Verizon Samsung Galaxy S III] vforaci:
I have no lte service on m9. I had one navigation reboot, other than that it's been solid.
[Verizon Samsung Galaxy S III] tv31284:
I was hoping they solved it but the 8/12 build I was running rebooted while using navigation. At least it lasted almost a week without rebooting. I tried the 8/20 build and it rebooted during navigation too.

I attached logs to both crashes if anyone's interested in looking.
[Verizon Samsung Galaxy S III] prdog1:
May try older version maps if Google framework allows it. They have had same problem of navigation reboots on newer versions of Google Maps on Stock TW. :cool:
[Verizon Samsung Galaxy S III] betam4x:
Bluetooth phone calls screwed up on the 8/21 build.
[Verizon Samsung Galaxy S III] merdely:
What does that mean?
[Verizon Samsung Galaxy S III] betam4x:
Couldn't hear the person on the other end while on the phone in my car while on bluetooth.
[Verizon Samsung Galaxy S III] razz1:
Also has issues with pairing unless they fixed it.

EDIT: Here is a log for the pairing issue.

https://www.dropbox.com/s/bhu08fpvejx7w0m/2014-08-21_18.40.zip
[Verizon Samsung Galaxy S III] vforaci:
I have the same issue although not sure when it started. If you switch the sim card setting, toggle airplane mode, all in mobile settings i was able to get back although it didn't survive a reboot.

Edit: LTE issue was a bad SIM card. Swapped it out at Verizon and all is well.
[Verizon Samsung Galaxy S III] tv31284:
Stock TW based on 4.4? Because I haven't had the same issues with TW based on 4.3.

I've been debating going back to TW 4.3 but even the debloated ROMs are so bloated. And obviously I'd be a version behind, which, is kind of hard for me to swallow. The reboots on cm11 are getting frustrating though as I feel as if I can't rely on my phone. I suppose its just a give and take.
[Verizon Samsung Galaxy S III] esjames:
Anyone know what the 8/20 experimental build is about?:confused:
[Verizon Samsung Galaxy S III] mastamoon:
Carrier specific change.
[Verizon Samsung Galaxy S III] esjames:
Thanks.:good:
[Verizon Samsung Galaxy S III] samman82:
I've searched and discovered that I have a bug that's existed for a while. Anyone familiar with the wifi/mobile data toggle bug? My mobile data doesn't work with wifi on (no mms), and when I toggle the wifi off, my data comes on momentarily then turns off. Any fix? I'm digging this rom otherwise and don't want to flash another one.
[Verizon Samsung Galaxy S III] funkpod:
I am having this problem on 8/4 as well, with the phone resetting during navigation.

Do you mean like, uninstalling updates? How far back do I need to go?
[Verizon Samsung Galaxy S III] prdog1:
Seems like it was reported on Alliance Rom on the last 2 updates. So probably 3 back. Pretty sure it the app since it was reported on stock TW also. :cool:
[Verizon Samsung Galaxy S III] funkpod:
Hmm. I'm on 8.2.0.

There are no options to uninstall updates, only force stop and disable.

Is there a way to find old apks?
[Verizon Samsung Galaxy S III] prdog1:
Start here and go through archives. :cool:

http://www.androidpolice.com/page/2/?s=google+maps
[Verizon Samsung Galaxy S III] funkpod:
I can't seem to install any old versions, my phone won't let me. I tried 7.7 and 8.0
[Verizon Samsung Galaxy S III] prdog1:
May be because of Google sevices framework. Was afraid of that. Bug may only be device specific also. HTC Rezound had same problem a few yrs back. :cool:
[Verizon Samsung Galaxy S III] droidxxxxx:
Latest 8-24 nightly is the tits..working real good..GPS, voice texting.. All seems rock solid. Will continue my testing.. I'm on 1-5-14 gapps. None of my previous issues running kitkat are noticed.. Great work!
[Verizon Samsung Galaxy S III] prdog1:
I flashed 25 today. Everything seems good except video camera not recording. Nothing in gallery. Is there a trick to it. :cool:
[Verizon Samsung Galaxy S III] droidxxxxx:
Just tried my gallery and it seems everything is there. Fired up the camera and the video camera and they both seem to work, have not had a chance to actually take pictures though. On the 824 build still .
[Verizon Samsung Galaxy S III] prdog1:
Mine started crashing on phone calls. Don't know what's up with that.
[Verizon Samsung Galaxy S III] droidxxxxx:
Well, try the 824 build lol.. Been waiting for a fully functional by my standards anyway KitKat ROM and this seems to be the one for me so far.
[Verizon Samsung Galaxy S III] prdog1:
Dirty flashed and it fixed both issues. :cool:
[Verizon Samsung Galaxy S III] droidxxxxx:
The 8-24 version?
[Verizon Samsung Galaxy S III] prdog1:
8/25. :cool:
[Verizon Samsung Galaxy S III] droidxxxxx:
Cool..I'm scared to change..8-24 is kickin butt for me.
[Verizon Samsung Galaxy S III] prdog1:
Haven't found anything else yet. :cool:
[Verizon Samsung Galaxy S III] rholm:
How's the signal strength? I'm thinking of joining you guys over here.

Cheers,

Rich
[Verizon Samsung Galaxy S III] droidxxxxx:
Seems pretty good for me..drove 120 miles today down I-10..hit one 3g area..stays 4 g pretty good. I'm on mf1 radio BTW.
[Verizon Samsung Galaxy S III] prdog1:
My signal 107dBm. About same as always. I'm on NE1 modem. :cool:
[Verizon Samsung Galaxy S III] rudedog830:
How's battery life on 8/24?
[Verizon Samsung Galaxy S III] funkpod:
Hey, have you (or any other 8/24 users) done any navigation with google maps? Mine would crash several times in an hour and a half drive...
[Verizon Samsung Galaxy S III] droidxxxxx:
Been using waze, but will try Google Maps today.
[Verizon Samsung Galaxy S III] betam4x:
Still no luck with getting LTE back. Considering flashing back to stock, but i'm not quite sure how to go about doing that.
[Verizon Samsung Galaxy S III] droidxxxxx:
08/24 build Google Maps working flawless. I came from Eclipse 4.3 using the 1 /5 14 gapps package. Formatted data and did the appropriate wipes and this time around is working great for me been having issues with kit kat, but not this ROM version. On the MF 1 radio as well.
[Verizon Samsung Galaxy S III] thefuzz4:
Also on the 24 build and its great. I also noticed that the tap and pay learn more link works now and wallet setup tap and pay this morning do I'll have to give that a whirl next time I'm out. Anyone else try it?
[Verizon Samsung Galaxy S III] darklavalizard:
I'm on it as well, flashed from the M8 build. So far so good :D
[Verizon Samsung Galaxy S III] jasonbtx:
Can't write to sdcard1. Ran sdfix. No dice. Tried stock file explorer, root explorer, explorer, Usb cable to no avail. Wiped reflashed. Ideas? Help?
[Verizon Samsung Galaxy S III] funkpod:
Anyone notice on 8/24 the volume is really big? Speaker volume.

Also, in general, what happened to the mic button on the keyboard? For voice dictation while typing.
[Verizon Samsung Galaxy S III] prdog1:
I have mic button on 8/25. Everything seems to work so far. I'm happy with volumes as I'm old and usually use the 50% sound mod on TW. :cool:

.

Sent from my SCH-I535 using Xparent Skyblue Tapatalk 2
[Verizon Samsung Galaxy S III] bmeek:
My d2vzw's power button wore out a couple of weeks back (it's stuck in the depressed state and I could not find any inexpensive antidepressants for it), so I decided to retire the device and picked up a really clean HTC One M7 on swappa!

I noticed today that cm11 on the "m7vzw" has a feature that I always wanted with the d2lte CM builds: when you have an A2DP headset connected, the handset speaker still rings on an incoming call!

I often listen to news and other streaming audio via Bluetooth while walking around, and then take off the headset and put it in my shirt pocket or set it down without turning it off. From that point incoming calls went unnoticed if running cm10 or cm11 (TouchWiz ROMs still ring the handset).

So I came back here to say hello, and to ask if a recent build of cm11 added this same feature to the GS3? I'm just curious...

---------- Post added at 09:23 PM ---------- Previous post was at 09:13 PM ----------

Hey prdog, I'm not used to seeing you over here on the aosp threads. Mic button sounds interesting (no pun intended). Please elaborate, as I'm also old...

I searched the play store and didn't see anything that appears to be what you're referring to...
[Verizon Samsung Galaxy S III] prdog1:
Other poster was looking for the voice dictation mic symbol on CM keyboard. CM11 actually running pretty good for what I do on phone. Battery life not good at this point tho so still playing with it. :cool:
[Verizon Samsung Galaxy S III] bmeek:
Ah - for some reason I thought you were referring to a good volume boost utility... Silly me.

FWIW, I got better battery life with cm11 using decimalman's dkp kernel.
[Verizon Samsung Galaxy S III] prdog1:
Yea. First time ever for me to flash AOSP base but Samsung forced the issue. I refuse to lock my device down so gonna play with this and see what I can come up with. My Linux build environment getting dusty. :p:cool:
[Verizon Samsung Galaxy S III] ugachris:
How are you running the NE1 modem?
[Verizon Samsung Galaxy S III] prdog1:
Been running for a while. Didn't change it. :cool:
[Verizon Samsung Galaxy S III] ugachris:
Is it possible to flash this if you aren't already on NE1?
[Verizon Samsung Galaxy S III] prdog1:
Should be able to. It is on separate partition independent of rom. The modems either work or they don't. Apparently it works. :cool:

---------- Post added at 09:54 AM ---------- Previous post was at 09:45 AM ----------

https://www.dropbox.com/s/dim3p80ycwc06p4/d2vzw_NE1_modem.zip?dl=0
[Verizon Samsung Galaxy S III] rholm:
Is NE1 recommended on all roms? I'm still on Alliance and strongly considering cm 11. With SlimKat, my signal was very low with ML1.

Cheers,

Rich
[Verizon Samsung Galaxy S III] prdog1:
I always run latest modem on TW. Ran it on 4.3 base with no problems but I'm in a full 4G coverage area. Most that need older modems are in fringe or 3G areas with older towers. :cool:
[Verizon Samsung Galaxy S III] rholm:
I'm in the Chicago area, so I have full coverage too. My signal strength does vary with different roms, aosp vs. tw. Is that you experience too?

Cheers,

Rich
[Verizon Samsung Galaxy S III] funkpod:
I usually see you on Alliance ROM, right? What made you switch from TW?
[Verizon Samsung Galaxy S III] prdog1:
Don't run Alliance. Too much junk in the trunk on that one. Every mod not used is bloat. I build my own ROMs from base with only the mods I want hard coded. Since 4.4 kernel is locked down I am bored. Already built and fully themed 4.3. Have that backed up so just playing with 4.4 for a while. :cool:

Sent from my SCH-I535 using Xparent Skyblue Tapatalk 2

---------- Post added at 04:11 PM ---------- Previous post was at 04:04 PM ----------

This my first AOSP ROM. so far signal per meter is same as TW @ 107dBm. It will vary from ROM to ROM since RIL is home baked and who built it or which version is kanged to ROM. RIL has always been the biggest problem on any port. They seem to be getting closer. :cool:

Sent from my SCH-I535 using Xparent Skyblue Tapatalk 2
[Verizon Samsung Galaxy S III] tv31284:
I'm also on the 8/24 build. I've used navigation for over 3 hours nonconsecutively and no reboots so far. I'm at about 93 hours of uptime. Hopefully this keeps up. I might actually flash the next M build and stay there for awhile.
[Verizon Samsung Galaxy S III] TokedUp:
[MENTION=4538493]prdog1[/MENTION] running CM11? This really is the end of TW! Lol
[Verizon Samsung Galaxy S III] thefuzz4:
I'm on 24 still but still having the occasional random reboot might try a wipe of system to see what that does or a different kernel otherwise this build is amazing.
[Verizon Samsung Galaxy S III] prdog1:
LMAO. Never thought I would see it either. Now if I could just get battery life under control. :(:cool:

Sent from my SCH-I535 using Xparent Skyblue Tapatalk 2
[Verizon Samsung Galaxy S III] jasonbtx:
ZeroLemon Battery
[Verizon Samsung Galaxy S III] huskerpat:
Is anyone having trouble answering the phone? With the last few nightlies, I have to wait 3 or 4 rings before the screen turns on to answer the phone.
[Verizon Samsung Galaxy S III] rholm:
I have a zero lemon. How bad is the battery life? I can get 3 days on Alliance.

Cheers,

Rich
[Verizon Samsung Galaxy S III] esjames:
I must say, this device has one great support community and it's too bad Verizon locked it down tight as a wedge. It also forced my hand and I left big red for t-mobile. Went for the S5 which really doesnt have a good working CM11 build yet and I will miss it. :angel:
[Verizon Samsung Galaxy S III] annoyingduck:
PA gapps do not have the google dialer with search...

There are dialer zips floating around, but I've had nothing but issues with them, as that dialer is only optimized for the N5... I know banks has one, but I'd do some heavy research before flashing anything.
[Verizon Samsung Galaxy S III] AlphaXray:
Yeah maybe I'll just wait and hope we are able to have it successfully integrated in the future.
[Verizon Samsung Galaxy S III] Snypercell:
Awesome!! I've been waiting patiently for you to release one. Can't wait to give it a whirl!! Thanks for the hard work and dedication! Install in 3... 2... 1...
[Verizon Samsung Galaxy S III] sanjsrik:
I posted earlier about not having any WiFi with the 12/10 nightly. I dirty flashed the 12/11 nightly and while initially it fixed the WiFi, the minute I went into the subway and came back out. I had the same behavior of LTE trying to connect and disconnect every 3-4 seconds and the WiFi not finding any of my known networks.

After some hemming and hawing, I wiped factory reset and flashed 12/11 and rebooted. WiFi connected as soon as I gave it my password and no issues at all.

I wonder if there is an issue with dirty flashing 4.4.x?

I'll try dirty flashing the next nightly, if I run into issues, I'll clean flash one nightly and stay on it and only repeat flashing once a week.

AND, the device got REALLY hot and wouldn't charge either until I factory wiped and flashed. It would sit at whatever percentage it was before rebooting and not charge.

Now, it's charging fine.

Anyone else having issues like these? Suggestions as to what I might have done wrong most appreciated.
[Verizon Samsung Galaxy S III] 0331:
I've dialed *228 from my S3 several times because I was trying read the little message that pops up. it said 4G was activated on my sim and didn't need *228. I never had a negative issue from it.
[Verizon Samsung Galaxy S III] dvaderx:
I've also had issues with those zips/that dialer.

Bug report: speaker phone doesn't seem to work correctly, until you turn the volume all the way down and back up.

blue tooth on the phone and the device both need to be toggled on and off a few times to make them connect..

other than that, 12/11 is pretty solid.
[Verizon Samsung Galaxy S III] cuban11182:
I actually tried to help a friend with a bone stock phone with signal issues. His phone was not rooted. When I tried to do it, it wouldn't allow me to do it. I'm guessing with other roms that protection may not be available. In any case, it did destroy my SIM. I couldn't get 4g and odin'd to stock and went to the local Verizon store.
[Verizon Samsung Galaxy S III] caifan:
On 12/10 nightly...I've noticed that the "Connected as a media device" message remains in the drop down even after I unplug from computer. It only clears when I reboot phone. This has been happening since 12/8 nightly.
[Verizon Samsung Galaxy S III] lou1210:
FWIW:

I dirty flashed 12/11 this afternoon. Cleared system cache and dalvik and reinstalles the su update.

When I first rebooted, I did not have gmail and the play store would not open though I had internet both on LTE and wireless. I reinstalled gapps and play store access returned but I had to delete my gmail account from my phone, re-add it and resync everything. Been working fine since.

My other issue is that Bluetooth does not auto connect back if I've had it connected to my car. I've had to shut it off when I get out of the car and turn it back on and even then it toggles a few times. Its aosp ROMs though. I can live with it. This was more of an FYI.

Battery life hasn't been that good but I'm going to charge it fully again since the flash and see how it does.
[Verizon Samsung Galaxy S III] LudicrousPeed:
Let us know your results!

---------- Post added at 09:20 PM ---------- Previous post was at 09:14 PM ----------

So you tried that Dalvik patch? I was curious as to why it isn't already in the build. Maybe no one had heard of it is all. Any noticeable improvement for you? No issues created by it?
[Verizon Samsung Galaxy S III] ericsdeadinside:
No boot loops and seems smooth

---------- Post added at 11:44 PM ---------- Previous post was at 11:20 PM ----------

Yeah i flashed both. No issues
[Verizon Samsung Galaxy S III] bmeek:
Yes, most ROMs seem to either prevent the call or handshake in such a way that nothing bad happens... The message that the stock ROMs display even implies that initiating the *228 call had triggered the reading of configuration data from the SIM (in fact, I could almost swear I've had Verizon folks ask me to dial *228-something on the s3 during activation - although that doesn't mean it was the right thing to do).

My knowledge of these details is superficial enough that I was going on the assumption *228 was either useful or harmless on this phone until I tried it on a recent KitKat ROM. I heard the "please hold while your phone is being programmed..." music and then that my phone had been programmed successfully! From that point i got 3g data connections only. NEVER AGAIN WILL I DIAL*228 FROM AN LTE DEVICE.

Again, i was able to get LTE working with my original sim by deactivating the phone and then reactivating it with vzw. So apparently it's the proper activation that gets things working again, not the new sim.
[Verizon Samsung Galaxy S III] titanshadow:
I think the problem is with Verizon, I would guess that the SIM card was perhaps misconfigured initially prior to calling *228 but it worked anyway. Then when dialing *228 something the phone sends back to Verizon triggers Verizon to accept that the SIM card is not present, not needed, or something along those line and then programs the phone which would kill the SIM card. I do know that once a SIM card's programming is lost they seem to never reprogram it they just give you a new one, so I would speculate that this is Verizon's service misconfiguring or misreading a percentage of SIM cards that trashes their ID with Verizon making them unusable. Like changing the keys to your car before the lock smith gets in there to rekey it.
[Verizon Samsung Galaxy S III] Mystikalrush:
Nightly 12 really screwed with my phone...
[Verizon Samsung Galaxy S III] harry_seaward:
I've been on 1212 since it was put up on get.cm, and everything has been running perfectly.

Care to elaborate?
[Verizon Samsung Galaxy S III] Stealth111:
Details?

Sent using Tapatalk
[Verizon Samsung Galaxy S III] Mystikalrush:
Well I installed official CM11 for the first time. I came off from kangs unofficial cm11 which is a different version of android to begin with.

Ever since I installed this. It seems my twrp recovery has been messed up. I get an error every time I try to fully wipe my system, something with lost+found.

So this also doesn't allow me to revert back to any of my TW or CM nandroids. All I get are recovery errors... I'm basically locked to this ROM forever.

I could only get my phone back to bootable condition by flashing this ROM and gapps.

I really x10 hope this can be fixed via recovery update, unless you guys can come up with a solution. I'm basically screwed.
[Verizon Samsung Galaxy S III] harry_seaward:
You've tried flashing the latest version of CWM like the OP says is required?
[Verizon Samsung Galaxy S III] Hybridnoob:
TWRP isn't officially supported. Try switching to CWM recovery. You'll at least be able to flash other ROMs.
[Verizon Samsung Galaxy S III] podspi:
It's working for me as well. I think it isn't in the build because it is closed-source.

I've had this problem as well, and it probably is unrelated. It basically means your internal memory has become corrupted. This is what fixed it for me. As an aside, I don't think this has anything to do with TWRP. I don't have any issues using the newest TWRP w/ CM11.
[Verizon Samsung Galaxy S III] prdog1:
That defeats the purpose. Doesn't fix the problem. Just masks it. Just more battery and weight. :cool:

Sent from my SCH-I535 using Xparent Skyblue Tapatalk 2
[Verizon Samsung Galaxy S III] rhcreed:
odd problem

Since upgrading to 8/24 nightly cannot answer calls with bluetooth earpiece. Calls can be placed no problem, but when I answer a call, I cannot hear them and they cannot hear me. I tested the headset on another phone so I know it works. I was on an version from earlier in august, but everyone raved about 8/24 so I jumped to it. Have tried the nightlies since then and problem persists. Any suggestions? Any info I can provide to help troubleshoot? Thanks!
[Verizon Samsung Galaxy S III] jasonbtx:
No replacement for displacement.

---------- Post added at 01:43 PM ---------- Previous post was at 01:42 PM ----------

Any working fix for sdcard write?
[Verizon Samsung Galaxy S III] prdog1:
It looks like size for size you getting the same battery life as my 2yr old stock battery. :laugh: :cool:
[Verizon Samsung Galaxy S III] chowner:
NE1? Folks are running this with cyanogenmod and unlocked bootloader?
[Verizon Samsung Galaxy S III] razz1:
I guess provide a log if you get some time. I also have issues maintaining my headset paired. If I reboot the phone or turn Bluetooth off and back on again I will lose the paired data and will need to perform the pair processes again. I provided a log a page or two back. Hopefully the right people see it and can correct it.
[Verizon Samsung Galaxy S III] huskerpat:
Mine does this in my car. I can place calls with Bluetooth, but cannot receive. I have to use the phone.
[Verizon Samsung Galaxy S III] funkpod:
Bluetooth headsets for music and podcasts seem to work good. I listened continually for 2 hours on my run today.
[Verizon Samsung Galaxy S III] rholm:
I installed the 08/24 build last night. I have everything setup and running how i like it now. It went pretty well. Here are a few notes:

- The battery usage on the stock kernel was pretty bad initially. Switching to "PowerSave" instead of "Balanced" helped. I now have the BMS kernel installed with the asswax governor. I'll monitor it over the next few days. So far battery usage is ok. I tried LeanKernel, but my signal strength was very weak, using the ML1 modem. KT didn't work as I had no WIFI. Sounds like people are waiting on a fix.

- I couldn't restore my phone log, contacts, and texts until I modified the permissions of SMS Backup+ under Privacy Guard.

- My bluetooth headphones seem to work better than with AllianceROM 23. I kept having problems with the audio stopping in PocketCasts (it happened with regular wired headphones too). I also had problems pairing on AllianceROM that didn't occur with CM 11.

- I installed Better Battery Stats from TiBu. It didn't work until I reinstalled it from apk and made it a system app.

- I like the google camera. Anyone know how to configure it to save new photos to my SD card?

- Not sure I like the dialer. Anyone have suggestions on an alternative?

All in all, I'm very happy. The phone is much smoother. I run NovaLauncher and there is zero lag. I should have switched sooner, especially when it became clear we wouldn't get an unlocked TW 4.4.

A hearty thanks to all that made this possible!

Cheers,

Rich