yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] funkpod:
I am also curious about how to save photos onto sd.
[Verizon Samsung Galaxy S III] prdog1:
I just set it to storage>SD Card in camera Settings. Pics going to DCIM on external. Screenshots going to internal. Would have to be changed in code to get screenshots on external. :cool:

Edit. I see you want Google Camera to save to SD. Google wants to eliminate SD Cards. That would have to be done in code if no setting for it.

Edit: At this time we are unable to decompile the new Google apps to change code or theme. Most are locked down.
[Verizon Samsung Galaxy S III] droidxxxxx:
I was on 8/24, and just moved to the new spirit ROM, and the same problem of the person I'm talking to while I have the speakerphone on hears an echo... Leading me to believe something is tweaked with the sound. I'm pretty sure spirit is cyanogen as well.. Just wondering if anybody else has noticed that.
[Verizon Samsung Galaxy S III] prdog1:
Try turning off noise suppression in dialer settings. That is most common cause of echo and can be device specific. Won't do it on all phones.:cool: :cool:
[Verizon Samsung Galaxy S III] droidxxxxx:
Thanks for the advice, I gave that a try but the problem still exists. I am on the spirit ROM however. I will most likely try to flash the most recent version of this one again and see if it fixes the problem when I uncheck noise suppression. Apparently it sounds really bad on the other end while I'm on the speakerphone. Bluetooth or regular earpiece works fun. I do notice that at first when I put the speakerphone on and I'm calling someone it is ringing really loud and if they answer and I have not touched the volume buttons.. It echoes really really bad for the person I'm calling. When I try to adjust the volume down.. It gets really low.. And still echoes on the other end.. Lol
[Verizon Samsung Galaxy S III] rholm:
My battery life is excellent (+3 days) with the BMS kernel and "asswax" governor. Supposedly, "dancedance" is even better. Will try that this week. I have a ZeroLemon battery and that is better than AllianceROM.

Cheers,

Rich
[Verizon Samsung Galaxy S III] chowner:
No details?
[Verizon Samsung Galaxy S III] prdog1:
I already had on my phone before CM. If search this thread I think I posted a link. Just flash in recovery.

Sent from my SCH-I535 using Xparent Skyblue Tapatalk 2
[Verizon Samsung Galaxy S III] chowner:
Who else is running this on unlocked?
[Verizon Samsung Galaxy S III] RRF12:
Have been on the ne1 modem since it was released works fine. An I run cm 11 nightly an tw no problems.
[Verizon Samsung Galaxy S III] funkpod:
Anybody using 9/1, 9/2, or 9/3?
[Verizon Samsung Galaxy S III] rhcreed:
Just jumped on 9/2, still having issues answering bluetooth calls (placing calls is fine).

Only been on it a couple hours, nothing big to report yet.
[Verizon Samsung Galaxy S III] funkpod:
Keep us posted, thank you!
[Verizon Samsung Galaxy S III] prdog1:
I'm on 9/1. Haven't noticed any difference yet.

Sent from my SCH-I535 using Xparent Skyblue Tapatalk 2

---------- Post added at 03:36 PM ---------- Previous post was at 03:33 PM ----------

Only been 1 Bluetooth change in last week and had something to do with packets per changelog.

Sent from my SCH-I535 using Xparent Skyblue Tapatalk 2
[Verizon Samsung Galaxy S III] chowner:
Sweet I did it and my phone still appears to be working
[Verizon Samsung Galaxy S III] rhcreed:
It's %100 consistent that I cannot answer a call with a bluetooth device, but I can make calls no problem. I'll submit a log if someone will walk me though how to do it. Thanks!
[Verizon Samsung Galaxy S III] rholm:
Has your signal level changed?

Cheers,

Rich
[Verizon Samsung Galaxy S III] droidxxxxx:
I'd dirty flashed from 8/24.. Seems to be doing really good. Going to try and see if I still get echo when using the speakerphone. People on the other end say they echo when I use the external speaker..

---------- Post added at 06:43 PM ---------- Previous post was at 06:36 PM ----------

Ok just tried it. I have noise suppression unchecked. The people on the other end still hear them self echoing when I have it on speaker phone. That's the only thing I can find wrong so far. Everything else seems to be very stable.

---------- Post added at 06:43 PM ---------- Previous post was at 06:43 PM ----------

Never had a problem with speaker phone before.
[Verizon Samsung Galaxy S III] prdog1:
Only other thing in settings is the privacy one. They have been playing with CAF and it can mess with the sound. It is used in call recording. On Skvalex's call recorder app we can adjust the volume and bit rate. :cool:
[Verizon Samsung Galaxy S III] droidxxxxx:
OK will give that a shot..thanks
[Verizon Samsung Galaxy S III] chowner:
Maybe slightly. I was hoping this would help battery life, but no dice.
[Verizon Samsung Galaxy S III] buschbarber:
I have asked this question before with no Reply. Ever since I have been using this Rom on my i535, I notice that the Font Size varies greatly, between one Reply and the next, in this forum as well as others that I participate in. This is only true on my phone and not on my PC. I am constantly having to Zoom in to read one reply and Zoom out for the next. It is time consuming and forces me to scroll to the right or left when zooming in on the smaller fonts in a Reply.

Is there a fix for this or does anyone else have this issue?
[Verizon Samsung Galaxy S III] vforaci:
I did have that issue, currently running m9 and font size is consistent.
[Verizon Samsung Galaxy S III] rholm:
What kernel are you running? I am using BMS with the asswax CPU governor and seeing great battery life. I have a ZeroLemon. On stock, I was getting 3 days. I am getting nearly 4 days now.

Cheers,

Rich
[Verizon Samsung Galaxy S III] bill3508:
WiFi broke on latest 9/2.

Sent from my SCH-I535 using Xparent BlueTapatalk 2
[Verizon Samsung Galaxy S III] prdog1:
Working on 9/3. Didn't run 9/2. :cool:
[Verizon Samsung Galaxy S III] droidxxxxx:
Wondering if anyone has used Skype. The newest version from the Play Store. Tried using it today on the way home skyping with my kids and it kept force closing itself about 2 minutes into the conversation. And it did not want to let me use Bluetooth either. If somebody uses Skype please try to confirm a conversation with someone if possible Thanks.
[Verizon Samsung Galaxy S III] chowner:
worked fine for me
[Verizon Samsung Galaxy S III] buschbarber:
Same here.
[Verizon Samsung Galaxy S III] chowner:
Google Voice does not work with 9/4 for me.
[Verizon Samsung Galaxy S III] Samsung.Galaxy.S3:
WiFi good here also. :good:
[Verizon Samsung Galaxy S III] prdog1:
Look out for 9/5. Looks like major GPS and RIL updates. [MENTION=4877921]droidxxxxx[/MENTION] . Speakerphone volume decrease. That could be what is causing the echo. :cool:
[Verizon Samsung Galaxy S III] jimwick:
Kernal suggestions

............. coming from a TW ROMs, what kernal with this ROM do you guys suggest?
[Verizon Samsung Galaxy S III] MartyMacGyver:
Ditto! You posted that after I checked here to see if anyone was complaining about the 9/4 build... and so I installed it, to my regret. :-/

In addition, the radio seems a bit wonky (had trouble getting to LTE mode while in transit) and good luck if you decide to downgrade - whereas with other builds you could step back a week or two to a more stable nightly, any attempt to downgrade even to the last one I flashed (8/25) caused several system processes to crash and eventually reboot the phone, over and over again.

Fortunately, other than some radio weirdness and the very unfortunate Google Voice fail, the rest of the build seems "ok"... not bad enough to merit spending hours re-flashing the whole phone back to 8/25, but definitely a bad idea to upgrade to if you are on a working build currently.

UPDATE: I just grabbed the 9/5 build which came out a little while ago and Google Voice is working again! Not sure how the rest of the build is working but that's a plus.
[Verizon Samsung Galaxy S III] Reznor7:
The RIL update may explain why I lost all cell broadcast functionality. I've switch preferred networks, etc., and the AP points option crashes. Anyone else having service problems with 9/5?
[Verizon Samsung Galaxy S III] prdog1:
Yea. It broke mine also. :cool:
[Verizon Samsung Galaxy S III] Stealth111:
Super Fail Sauce on 09/05

Yeah, all is broke on this build as far as cell functionality goes. Gps doesn't work either. Wifi will not get correct address as well....Steer clear of this one, see attached pics!

Yikes!!
[Verizon Samsung Galaxy S III] rholm:
I've been using BMS with asswax CPU governor. No issues and tremendously great battery life... +4 days with a ZeroLemon battery.

Cheers,

Rich
[Verizon Samsung Galaxy S III] prdog1:
Tried backing up but a lot of FCs so just wiped and installed 9/04. :cool:
[Verizon Samsung Galaxy S III] chowner:
Should have came here first.. Yikes.

However WiFi is good for me.

UGH had to wipe. Installing 9/4 didn't work :(
[Verizon Samsung Galaxy S III] Stealth111:
I just nandroided back to last weeks build (I usually take a backup once a week!)...

All is well again!
[Verizon Samsung Galaxy S III] jasonbtx:
Any luck on writing to sd?
[Verizon Samsung Galaxy S III] knldge:
9/5 build has resolved the GV fc, Still having speakerphone and bluetooth pickup issues. Experiencing the same fc when rolling back to a build from 10 or say days ago.

Additionally, calls now take longer to even connect on dial out, and at other times I get a complete silence.
[Verizon Samsung Galaxy S III] althornin:
If you flashed 9/5, had no data, and so flashed and older build and are getting the constant android.process.acore has stopped messages, no need to wipe:

Try going to settings>applications>running>all and scroll to "contacts" open it and choose "clear data" - then go back to "contacts storage" and do the same thing.

After flashing back to 9/4 and doing the above, everything is fine.
[Verizon Samsung Galaxy S III] jimwick:
...... thks for the info on using asswax, asswax :D ............... sorry, long day........
[Verizon Samsung Galaxy S III] Nomad1600:
Hi folks, I am using AICP on my D2LTE (Verizon GS3) which I believe is built on CM11. Seems the last few nightlies we've had problems with Bluetooth (can make outgoing calls, but any incoming call through a bluetooth device loses all audio). Checking to see if folks here are having the same problem and hoping a workaround or fix has been found.
[Verizon Samsung Galaxy S III] rhcreed:
this...

Yes, I've been having the same problem for a while, had to roll back to M9 to find one that is working. Would love to see it get fixed, Thanks!
[Verizon Samsung Galaxy S III] trevoryour:
Can I ask where you found M9? I looked and I don't see any milestone builds listed. This bluetooth issue is a bit of a deal breaker since I'm in and out of my car all day.
[Verizon Samsung Galaxy S III] prdog1:
http://download.cyanogenmod.org/?device=d2lte&type=snapshot
[Verizon Samsung Galaxy S III] trevoryour:
Ah. that would explain it. It isn't a milestone build. Its a snapshot.
[Verizon Samsung Galaxy S III] Hybridnoob:
Check CMUpdater and change the update type to all releases. You should see it there. Bear in mind, M10 is due any day now.
[Verizon Samsung Galaxy S III] MartyMacGyver:
Are the "milestone" builds actually better than the snapshots? (Still missing the ability to rate/comment on a specific build, e.g., one-stop shopping (even if just on the builds page) so one can see if a given build is worth installing...)
[Verizon Samsung Galaxy S III] tv31284:
I was using the new NE1 modem and lost data when I flashed the 9/5 build. Went back to the modem before that and everything works fine.
[Verizon Samsung Galaxy S III] Reznor7:
Can confirm. Went back to ML1 modem and and all is well again on 9/6.
[Verizon Samsung Galaxy S III] Nomad1600:
When you say "all is well" does that include you are able to take calls via bluetooth?
[Verizon Samsung Galaxy S III] Reznor7:
Unfortunately, no. Cell functionality is restored, but when receiving a call via Bluetooth I still can't hear the caller.
[Verizon Samsung Galaxy S III] conquesoextra:
¿CM also contains modem? I did not understand.
[Verizon Samsung Galaxy S III] Milly7:
No. CM does not contain the modem. You have to flash that separately.
[Verizon Samsung Galaxy S III] bmeek:
Has Google stated this directly? I can see advantage to their cloud-storage business model, but I would think they would maintain neutrality in public. I expect it's happening anyway, with hardware companies motivated to eliminate manufacturing costs on removable SD cards (and batteries).
[Verizon Samsung Galaxy S III] prdog1:
Google actually dropped (new) SD support a long time ago. They are trying to force to the cloud and improve security. That is why no Nexus devices have SD slots. OEMs add back if want SD slot. :cool:
[Verizon Samsung Galaxy S III] bmeek:
Well, kudos to Samsung for continuing with replaceable batteries and SD card slots... I guess i avoided a Samsung when my trusty d2vzw died, and I wanted a nice phone with an unlockable bootloader. Samsung has done such a good job supporting vzw's lock-it-down requests that they've lost my business. I picked up a used HTC one m7, because i could unlock it. It has a sealed battery and no SD slot, but that's not a deal breaker for me and the solid case construction is pretty slick...
[Verizon Samsung Galaxy S III] prdog1:
And HTC added SD back with M8. :cool:
[Verizon Samsung Galaxy S III] dmginc:
Is there a thread for the NE1 modem somewhere that I can't find?
[Verizon Samsung Galaxy S III] BadUsername:
Doesn't exist.
[Verizon Samsung Galaxy S III] semdoc:
[MENTION=2385005]invisiblek[/MENTION]

Guys.. You are doing awesome job..

I don't use CM, but I'm d2lte maintainer for my ROM..

All ROM's - AOKP, SlimRom, my ROM - are building with device and kernel trees provided by CM...

Please take a look into BT incall audio issues... After big cleanup done by [MENTION=1815755]intervigil[/MENTION], all ROM's suffer from this issue...

If you want we can provide a logcats...

I'm ready for any cooperation :)

CHEERZ :)
[Verizon Samsung Galaxy S III] chowner:
Have the problems that came about with 09/04 been fixed?
[Verizon Samsung Galaxy S III] prdog1:
ML1 modem fixed signal problem. Incoming Bluetooth calls still not working.
[Verizon Samsung Galaxy S III] Harb67:
Does anyone have alternative links for the files in the Install CM for d2vzw post linked in the OP (Link is in Step 2: Install a compatible Recovery)? All of the http://cmw.cmfs.me/ links seem to be broken, and the link for the CWM image is also broken.

Alternatively, if that page is out of date and there is something better out there, I'd really appreciate a link to it. I'm really rusty on modding and my phone is using an ancient build of CM - I'd like to get back up to speed and have the newest CM11...whatever the most up-to-date "how-to" resource is would probably be helpful.
[Verizon Samsung Galaxy S III] vforaci:
It's now a unified build, d2lte.
[Verizon Samsung Galaxy S III] MartyMacGyver:
Since I updated to 9/5 from 8/25 YouTube has been acting very strangely on my S3 - videos almost always start out like a contestant for /r/glitch_art... is anyone else seeing this effect lately?

(It might well be the app... I'm seeing a comment there blaming their 8/27 update, which I applied pretty quickly... but it didn't act up like this until after I updated the OS on 9/5 so maybe the commenter was using CM11 as well... thus I figured I'd ask here.)
[Verizon Samsung Galaxy S III] prdog1:
Mine seems to be ok but I'm using KlearKat Theme and TBO clear version of youtube. I did see one version acting up the other day where got white band across the bottom. :cool:
[Verizon Samsung Galaxy S III] Harb67:
Wow, those few words answered so many questions. Thank you! I was wondering why the CM website wasn't showing any nightlies newer than February...

Is d2lte specific to any certain firmware/bootloader versions? I've been following these instructions and have finally gathered all the files needed and have Heimdall working - can I flash that stuff, then CWM 6.0.5.0, then flash a d2lte build? I'm currently running 4.3.1 on VRBLK3 firmware with CWM 6.0.1.2. Don't know what bootloader version, don't know how to find out :\
[Verizon Samsung Galaxy S III] prdog1:
If you are already unlocked you don't need all that. Just need the MF1 firmware, ML1 modem and latest recovery. :cool:
[Verizon Samsung Galaxy S III] Harb67:
Downloaded those two things, flashed everything and all is up and running on the first go. Thanks a lot!
[Verizon Samsung Galaxy S III] dewhashish:
Google wallet working yet?
[Verizon Samsung Galaxy S III] thefuzz4:
My wallet app says it's ready to go just haven't been to arbys lately to try it out
[Verizon Samsung Galaxy S III] dewhashish:
I haven't been able to get Tap and Pay working anywhere
[Verizon Samsung Galaxy S III] razz1:
Hey just created an app for this rom and roms based off CM to control gamma.

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

[app] gs3 gamma control
[Verizon Samsung Galaxy S III] invisiblek:
Suddenly..a wild baseband appears! http://www.invisiblek.org/firmware/d2/d2vzw_NE1_modem.zip (flash in your favorite recovery)

RIL works with the latest baseband (NE1, above) as of the 20140910 nightly (correct, as of this post that build is not yet available)

Manual fix to use NE1 baseband on older than 20140910 builds:

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] thefuzz4:
Anyone else still having their phone run hot? Just got my new zero lemon and still chewing through batteries I am on the 8/24 build
[Verizon Samsung Galaxy S III] prdog1:
Kewl. My signal was better with NE1 before the RIL fix around 9/4. :cool:
[Verizon Samsung Galaxy S III] Nomad1600:
Any progress with solving the problem with Bluetooth and incoming calls/audio?
[Verizon Samsung Galaxy S III] rholm:
I had the same issue. Turn in power save mode. I also switched to the asswax cpu governor. I get 4 days now on a zero lemon.

Cheers,

Rich
[Verizon Samsung Galaxy S III] thefuzz4:
Yeah I keep setting it that way but when I reboot the phone the settings go back so I just have to remind myself to go reset them. I even checked the box to set at boot.
[Verizon Samsung Galaxy S III] ugachris:
I am. It's been doing it for several weeks for me, even after several clean flashes to make sure everything got cleared out. I noticed my phone getting hot even when just playing locally stored music over bluetooth with the screen off. I installed the BMS kernel last night to see if that would make a difference.

---------- Post added at 08:33 AM ---------- Previous post was at 08:32 AM ----------

You can add a toggle to the Quick Settings drop down for this.
[Verizon Samsung Galaxy S III] thefuzz4:
I will have to do that, I didn't know :) Thank you. I installed the BMS kernel that does seem to help I should've added that to my original post.
[Verizon Samsung Galaxy S III] j555:
Do you think this modem update could cause sms sending issues like some of us saw before or should we be ok?
[Verizon Samsung Galaxy S III] rholm:
Yes, i am experiencing this too. I need to set it correctly after each reboot.

Cheers,

Rich
[Verizon Samsung Galaxy S III] bamaredwingsfan:
Can we get a md5 for the new radio file?
[Verizon Samsung Galaxy S III] mastamoon:
It self checks during flash.
[Verizon Samsung Galaxy S III] prdog1:
+1 [MENTION=2385005]invisiblek[/MENTION] has always included the sha1 checksum in all modems. :cool:

sha1_check(read_file("/tmp/NON-HLOS.bin")) == "0125252007a2b746d7314d294a2377526f20ff1f"

then
[Verizon Samsung Galaxy S III] mastamoon:
http://imgur.com/ZdYTxwX
[Verizon Samsung Galaxy S III] merdely:
I had the SMS problems with the ML1 modem. I just did a test and was able to send 3 SMS messages. Before, I could only send 1 before having to toggle 3g/lte, airplane mode, or reboot.

So, it feels good so far.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Do they still send just fine after you have rebooted? I have been enduring the 1 sms issue on AOSP as well but using VRBMB1 firmware resolved my issues.
[Verizon Samsung Galaxy S III] merdely:
I should have been more clear. I had the well know problem of only being able to send one SMS with the ML1 firmware. Switching back to the MB1 firmware cleared up the problem for me.

I just now switched to the NE1 firmware and don't have the "one SMS" problem.

Does that answer your question?
[Verizon Samsung Galaxy S III] rhcreed:
update op?

Any chance we can get the OP updated with current instructions and links?

I'm really not clear on what firmware/radio/rom combination we should be using.

I got this phone about a year ago and rooted/romed it then, have been on CM ever since. Have not messed with firmware or radio at all.

Would love to know the most stable combo I should be using (hopefully better signal and battery life as well).

Big thanks to the guys working on this, we really appreciate your work!
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Mostly, yes. I noticed for me, that I could send sms/mms fine after a flash of VRBMF1 firmware but the moment I rebooted, for any reason, I was met with immediate sending fails until I downgraded to VRBMB1 just like you.
[Verizon Samsung Galaxy S III] merdely:
OK. My test involved this:

1. Update to today's nightly.

2. Update PA-Gapps

3. Install NE1 firmware

4. Reboot

5. Power Off

6. Boot

7. Send 3 texts to my wife with 3 respnoses.

The time between 6 & 7 was less than 3 minutes. So, it was "immediate" after boot.
[Verizon Samsung Galaxy S III] Hybridnoob:
Thanks for the info. I'm still on the MB1 firmware and modem and on an older nightly. As far as I know, the NE1 file is just the modem. Did you update your firmware too? I think MF1 is the newest firmware that we can flash to our phones without locking the bootloader.
[Verizon Samsung Galaxy S III] Samsung.Galaxy.S3:
NE1 modem? Where?
[Verizon Samsung Galaxy S III] darklavalizard:
http://xdaforums.com/showpost.php?p=55350746&postcount=3306
[Verizon Samsung Galaxy S III] merdely:
I referred to this:

http://xdaforums.com/showpost.php?p=55350746&postcount=3306

I'm running last night's nightly (20140911)
[Verizon Samsung Galaxy S III] martopoulos:
So, not to jinx it, but I had been experiencing the "one SMS per reboot/airplane mode toggle" issue since March. I updated to latest nightly (0911) and NE1 modem. Sent about 20 messages, no problem. Whether this will work fine tomorrow, I don't know, but I haven't gotten this far since it started happening. *fingers crossed*
[Verizon Samsung Galaxy S III] Hybridnoob:
Same here, except staying on MB1 firmware and modem fixed texting and MMS for me. I'm now on MF1 firmware and NE1 modem and can send SMS, but not MMS (9/11 nightly). Anyone else?
[Verizon Samsung Galaxy S III] prdog1:
I'm getting the same with MF1 and NE1. No MMS. Also ML1 now no signal like NE1 was with MF1. :cool:
[Verizon Samsung Galaxy S III] Hybridnoob:
In case you want to fix it and need a solution, this works:

1. Backup current ROM (CM11 in my case)

2. In Terminal Emulator - su (enter) reboot nvrestore - if you previously completed nvbackup.

2a. If you didn't have a backup, but want/need to install a previous nightly, simply format system in CWM recovery, then install the older similar ROM and gapps. Your data will remain in tact. (You can also follow this process if you ever have a bootloop after updating your ROM.)

3. Battery pull once process completes, as it will bootloop.

4. Boot into recovery, restore nandroid and flash MB1 firmware. I immediately or upon reboot have had issues on all newer firmware versions.

5. Reboot system and profit. No SMS/MMS issues since.
[Verizon Samsung Galaxy S III] prdog1:
Need the MB1 firmware. Used to keep them all but got rid of them after MF1. :cool:
[Verizon Samsung Galaxy S III] Hybridnoob:
https://share.tresorit.com/?0018n2o...80HNCTJfrNM=&STUzNVZSQk1CMV9maXJtd2FyZS56aXA=

Please let me know if that doesn't work.