yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] aromig:
Hmm, time to poke around in the browser settings

Sent from my GS3 running CM11
[Verizon Samsung Galaxy S III] mastamoon:
If your using Chrome, turn off compression or data savings. Or just try another browser.
[Verizon Samsung Galaxy S III] Hybridnoob:
What firmware and modem are you running? GPS, Bluetooth (receiving and placing calls) and MMS working?
[Verizon Samsung Galaxy S III] ChiefIlliniwek5:
I did a clean install of m10 and I still have Bluetooth calling issues (can't speak thru Bluetooth when receiving calls). I also experienced a problem where the speakerphone has a volume issue (people on the other end are hard to hear when switching to speakerphone). Wakelock detecor also showed the phone being awake for 97% of the time with minimal use. Google play services is yet again the culprit. I'll be flashing back to m9 to see if things improve.
[Verizon Samsung Galaxy S III] anrichardson:
I installed m10 and so far very stable. I've had one reboot and Keep kept crashing. The only issue is not being able turn down the volume in a call. It stays the same, normally I never change it but was my mother in law and she was loud. Ended up just holding the phone away a little.
[Verizon Samsung Galaxy S III] jasonbtx:
Running 19 usb audio out borked. Charges but don't play
[Verizon Samsung Galaxy S III] Samsung.Galaxy.S3:
Same story here with bluetooth being borked (both incoming/outgoing). :crying: I'm reverting back to M8.
[Verizon Samsung Galaxy S III] chowner:
9/19 is way better than m8 every was IMO

Sorry I don't know about bluetooth though. I suppose I can try later as I always just use my work phone for that now.
[Verizon Samsung Galaxy S III] Samsung.Galaxy.S3:
I would like to stay on M10, but I need bluetooth to work. Maybe it'll be addressed in later builds. I'll keep checking.
[Verizon Samsung Galaxy S III] darklavalizard:
Why is bluetooth always the achilles heel? Hard to develop and code for? Just not a high priority?
[Verizon Samsung Galaxy S III] McDastardly:
NE1. All of the the above works for me.
[Verizon Samsung Galaxy S III] razz1:
Did Bluetooth calls work on M9 or do you have to go to M8? What is the last nightly it worked on?

M10 isn't working to well for me either.
[Verizon Samsung Galaxy S III] aromig:
Switched to Firefox and it downloaded first try. Not sure what Dolphin's issue with dropbox was. Xml worked like a charm though, nice work!

Sent from my GS3 running CM11
[Verizon Samsung Galaxy S III] Stealth111:
Also as far as GPS goes, even though mine doesn't seem to work with CM (but works 100% perfect on other roms), I did notice a bug with the settings. If I turn location ON, and set it to Device Only or Battery Saver, it will go right back to High Accuracy as soon as I switch location back off and then on again. It will not remember the selection I made. It seems to be defaulted every time to High Accuracy. Just an FYI....
[Verizon Samsung Galaxy S III] Casper34:
OK guys..... been away for awhile and I am itching for an update. I am currently running 11-20140402-NIGHTLY-d2lte with KT747 3.4.85 (build date of 4-3-2014) and MF1. What would be the best version to update to? What would be the best kernel? What would be the best modem?

All in opinions of course. I'm just looking for a trouble free update.

~~~EDIT~~~

I have read the last 40-50 posts this is why I am asking.

Also, am I too far out of date to update (meaning more than the usual amour of steps).
[Verizon Samsung Galaxy S III] Hybridnoob:
M9 and stock kernel is working really well (good battery life and all features work) on my other S3. It's still on MB1 firmware due to prior SMS issues.
[Verizon Samsung Galaxy S III] mastamoon:
Hey, check out one of the last posts in my thread. Another guy was having GPS issues, so he flashed back to stock then back to CM again and has working gps.
[Verizon Samsung Galaxy S III] XdrummerXboy:
I have an odd question...

I recently flashed a stock rooted 4.3 ROM (no Knox or OTAs) so that the display firmware would be flashed (I recently replaced my screen and had no touch), it was VRUCML1. I then clean installed CM11 after wiping cache, system, etc. But now my baseband version says its the MF1. Did the first/stock ROM not flash certain radios and stuff? Or does Cyanogenmod somehow include certain radios in the install which overwrote the others?
[Verizon Samsung Galaxy S III] prdog1:
Roms never flash modems/radios on Samsung anyway. You have to flash them separate. You have whichever radio you had before you flashed anything. :cool:
[Verizon Samsung Galaxy S III] XdrummerXboy:
Remove, post said it didn't go through
[Verizon Samsung Galaxy S III] XdrummerXboy:
Ahh, okay thanks!

the file was 900 some MB, so I thought for sure it included EVERYTHING, haha

I just got the NE1 from invisibleks page. That's the most current right?

And can anyone confirm if the latest nightly Works well? I tried one a couple nights ago that kept me stuck on the boot animation, as well as one of the M releases, don't remember which sorry.
[Verizon Samsung Galaxy S III] infsoul:
Help please

I have a straight talk Galaxy s3 sch-968c running slim Kat everything works but I want cm can anyone guide me post wise or inbox as to what will work for my phone it won't take forever just what to download and the best flashing process and way to get GPS DATA and mms and camera working thanks in advance
[Verizon Samsung Galaxy S III] ChiefIlliniwek5:
I flashed back to M9 from M10 after having big issues (see my most recent post) and so.far its working well. I haven't tested Bluetooth yet but battery is much better
[Verizon Samsung Galaxy S III] Zacharybinx34:
Why go back to m8 and not just m9?
[Verizon Samsung Galaxy S III] chowner:
I believe I remember reading that WiFi tethering is broken?

Mine is not working when I click the checkbox to turn it on it just states error.

Does anyone know if there is a work around?
[Verizon Samsung Galaxy S III] Casper34:
I just updated to M9 and mine works. I did dirty flash though from an older nightly.
[Verizon Samsung Galaxy S III] chowner:
I was on an older nightly and it wasn't working and I just updated to 9/22 and it's the same thing.
[Verizon Samsung Galaxy S III] Casper34:
Download and install SNAPSHOT M8.

Might want to install your last backup when it did work, then install M8.
[Verizon Samsung Galaxy S III] XdrummerXboy:
It looks hotspot its working for me, clean flashed 9-22 nightly, NE1 modem, etc
[Verizon Samsung Galaxy S III] rhcreed:
bluetooth calling

Does anyone know the last release that bluetooth call DID work? I'm on M9 and it does work, I'm afraid to try anything newer.

Any word on this getting fixed?

Thx!
[Verizon Samsung Galaxy S III] Casper34:
I was not the one having the issues.

But, since I have seen you have the NE1 modem, where can I get a list of modems that I can flash in recovery? I am running MF1. I just want to do some research on the modem in-between if any.

Thanks in advance!

Sent from my ghost white SGS3!
[Verizon Samsung Galaxy S III] capt730:
You can run MF1, ML1 or NE1. I have all 3 if you need them. Personally, I can only run MB1 AIO firmware due to sms/mms issues.
[Verizon Samsung Galaxy S III] Casper34:
Do you know where I can read about each one? Are they all recovery flashable? I saw that NE1 was oden.

Sent from my ghost white SGS3!
[Verizon Samsung Galaxy S III] prdog1:
There is nothing to read. They either work for you or they don't. They are all available as a flashable zip. :cool:
[Verizon Samsung Galaxy S III] Casper34:
Can you guys post up some links then so I can try?

Sent from my ghost white SGS3!
[Verizon Samsung Galaxy S III] capt730:
MB1 Firmware/modem https://mega.co.nz/#!UJBgCLZS!OKAInNGl8DdUAt_6E8vVRFGyNCQO5VpGAmjFH0o8ZCM

MF1 Firmware/modem https://mega.co.nz/#!RVAGHRDC!boUFGD-5jlMyBNNL9iMR5VOiu4wfQ_VjSUbwLvirGVU

ML1 Modem https://mega.co.nz/#!lQRwSAqD!W32nyEp1uVPCr5QJbYgt4AgAB4s77eEmK4kXE0w4Q-Q

NE1 Modem https://mega.co.nz/#!cIY2AKJC!yPboi6XkKxpwSM10eGLSE-JDYKIV34G5LeKzm81DUs4
[Verizon Samsung Galaxy S III] Casper34:
I do t see a download button, and the web address ends in preview.

Sent from my ghost white SGS3!
[Verizon Samsung Galaxy S III] capt730:
I uploaded from my pc and can download from my pc. Let me get you links from my mega.

**I updated my links in the post.....let me know if they are good.
[Verizon Samsung Galaxy S III] Casper34:
Had to install Mega but its downloading. Thanks!

Sent from my ghost white SGS3!

---------- Post added at 04:26 PM ---------- Previous post was at 04:18 PM ----------

Kinda off topic question here, but not really. With all the different cloud storage sites out there, examples, I have Google Drive, Dropbox, and now Mega (I'm sure I have more), is there a single app that I can use to manage the different cloud storages?

Sent from my ghost white SGS3!
[Verizon Samsung Galaxy S III] AndroidCrusader:
ES File Explorer
[Verizon Samsung Galaxy S III] XdrummerXboy:
If you request the desktop site it works as it normally would without having to download anything extra.

As a side note, I flashed NE1 two days ago and it doesn't get ANY service in one of my classrooms, and has really poor service at my home, only one bar (and I know there's a lot more to it than the number of bars, but too lazy to check the values in settings).

I'll be trying a different one to see if there are any improvements
[Verizon Samsung Galaxy S III] Casper34:
I downloaded X-Plore. Its a dual pane layout, so far I like it. Its very easy control.

Sent from my ghost white SGS3!

---------- Post added at 12:15 PM ---------- Previous post was at 12:12 PM ----------

Ya I have not installed any yet, I am out of town, so it's kinda useless foe me to test where I will be spending most of my time. I've heard the same thing all over about NE1, one bar and can't sent texts.

I will try all three over the next few days and report back.

Sent from my ghost white SGS3!
[Verizon Samsung Galaxy S III] XdrummerXboy:
Hmm I didn't hear about that, but I wasn't looking either, haha. I'm glad its not only me though!
[Verizon Samsung Galaxy S III] Casper34:
Ya people have been complaining about it in other forums. I'm still gonna try it, for some reason, my phone likes everything else people have been complaining about.

Sent from my ghost white SGS3!
[Verizon Samsung Galaxy S III] funkpod:
So...I am getting horrible battery life. I was on 9/4, and that seemed good at first , but not anymore. I need to update my modem? if I were you, I would update to the latest nightly and then flash this*http://mastamoon.truelinux.net/firmware/d2vzw_NE1_modem.zip

Here? And I need Bluetooth, cuz I just got the Moto 360. (Yay! )

M9? I would keep 9/4 cuz it was Super stable for me. Should I stay on 9/4?
[Verizon Samsung Galaxy S III] althornin:
No problem here with NE1 modem. . Texting is fine, signal strength is about the same wherever I go
[Verizon Samsung Galaxy S III] capt730:
No audio on incoming Bluetooth calls. Otherwise, everything is running pretty smooth.
[Verizon Samsung Galaxy S III] funkpod:
Which build you running?
[Verizon Samsung Galaxy S III] Casper34:
I have a question for the people that are on SNAPSHOT M9....... are you having issues charging??? I put my phone on charge last night at 14% around 11p and at 5a it was only at 92%. Usually its 100% by that time, with less % (say around 2-4%).

Sent from my ghost white SGS3!
[Verizon Samsung Galaxy S III] Shakes The AssClown:
Anyone having issues with it just hanging at the boot up screen. I formatted my data and system and then installed Snapshot 10...it just hangs at the boot screen. Any ideas on what to try or should I use a different snapshot or nightly?
[Verizon Samsung Galaxy S III] capt730:
9/23 nightly. None of September builds have it working.

---------- Post added at 12:40 PM ---------- Previous post was at 12:33 PM ----------

Liquid 3.2 has working BT on incoming. I wiped everything (data/system/cache/dalvik/internal) before installing.
[Verizon Samsung Galaxy S III] funkpod:
Thanks! I need bt, just got a Moto 360! I am on 9/4- Bluetooth seems to work ok except incoming.
[Verizon Samsung Galaxy S III] nmh5001:
On Snapshot M10 and this is happening (about 50/50) to YouTube videos. What's this all about? Tried the usual steps of cache wipe and an uninstall reinstall to no avail.
[Verizon Samsung Galaxy S III] darklavalizard:
Same thing happens to me on the 8/24 build, wiped the caches to no avail. If I put my phone in landscape mode, then it clears up after a few seconds.
[Verizon Samsung Galaxy S III] rholm:
I have seen this. I'm on the August 24th build.

Cheers,

Rich
[Verizon Samsung Galaxy S III] Casper34:
8-24......... do you happen to know what snapshot was released around that time?

Right now I am plugged into a 2a charger for my tablet and its charging like it's on 2 amps.

Sent from my ghost white SGS3!
[Verizon Samsung Galaxy S III] rholm:
Funny, that's how i fix it too. I have a tab pro 8.4. It charges normal when i use its charger. I do have a ZeroLemon battery, so i thought it had something to do with this issue.

Cheers,

Rich
[Verizon Samsung Galaxy S III] Casper34:
I had it on the 2a till it was another 75% and switched over to the 1a and it charged like it should. I will know more tomorrow when I will plug into the 1a for a charge. I will quote you and let you know the results.

Sent from my ghost white SGS3!
[Verizon Samsung Galaxy S III] Quacker:
Based on the last few pages I've read it looks like M10 has a lot of issues. Or does anyone find it to be stable? I'm still on an August nightly and I was waiting for M10. I also tried ML1 modem but find it MUCH worse than MF1... I have no LTE or 3G whatsoever at work. I'm hoping NE1 will fix things.
[Verizon Samsung Galaxy S III] XdrummerXboy:
I have been trying the NE1 for a few days, reception hasn't been great, and NO reception in one of my classrooms. I at least used to get some before. While in class I tried flashing ML1 and no result.

What's weird though is that I even flashed back to MF1 (I did have service with this before) but didn't have service this time. Maybe it needs to connect to the network before I go into the classroom.
[Verizon Samsung Galaxy S III] Casper34:
I just flashed NE1 and tried to send a text..... nothing. I came here to post this and look for the APN fix and it said failed could not connect to forum. I had to turn wifi back on. So, if anyone has the APN fix handy please could you post it up. In the mean time, switching back to ML1.

Thanks in advance.

Sent from my ghost white SGS3!
[Verizon Samsung Galaxy S III] mastamoon:
Try these apns.. http://mastamoon.truelinux.net/other/apns-conf.xml They are the stock, unbutchered ones from the last OTA.
[Verizon Samsung Galaxy S III] AndroidCrusader:
I am still looking for help with in-call volume control. Any ideas?

Running latest CM11 nightlies.
[Verizon Samsung Galaxy S III] darklavalizard:
Have you tried M9? I'm on the 8/24 and my in call volume is not adjustable, thinking about giving it a try.
[Verizon Samsung Galaxy S III] AndroidCrusader:
I skip the monthlies
[Verizon Samsung Galaxy S III] Zacharybinx34:
Today's build has awful battery life
[Verizon Samsung Galaxy S III] dmginc:
What do we do with these, Masta? Just replace the file on our phones w/ this one and reboot? Anything special that we need to do?
[Verizon Samsung Galaxy S III] mastamoon:
Just replace and set permissions if necessary then reboot.
[Verizon Samsung Galaxy S III] Casper34:
Error 500 internal.

Got it working but.... what do I do? I am on my phone, how do I save this. This is what I get.

Sent from my ghost white SGS3!
[Verizon Samsung Galaxy S III] mastamoon:
Ummm... Try this

https://www.dropbox.com/s/b9zatl31s5d6237/apns-conf.xml?dl=0
[Verizon Samsung Galaxy S III] Casper34:
Worked!! Had to go in there twice though, another error 500.

Forgive me, I have not messed with this phone in MONTHS, where do I put this? I know I have to fix permissions.

Sent from my ghost white SGS3!
[Verizon Samsung Galaxy S III] mastamoon:
/system/etc
[Verizon Samsung Galaxy S III] Casper34:
Sweet, thanks!!!

You building still, or just helping?

Sent from my ghost white SGS3!
[Verizon Samsung Galaxy S III] mastamoon:
Still building, but my days are numbered. Picking a new phone up soon.
[Verizon Samsung Galaxy S III] Casper34:
Ugh. What are you getting? I'm thinking about the note 4 or the one (m8).

Sent from my ghost white SGS3!
[Verizon Samsung Galaxy S III] mastamoon:
Waiting to see what the nexus looks like,... Hopefully it's awesome and worth leaving vzw for.
[Verizon Samsung Galaxy S III] Casper34:
I hear ya....... do you know who has a descent and updated kernel?

Sent from my ghost white SGS3!
[Verizon Samsung Galaxy S III] mastamoon:
No, I run stock cm.
[Verizon Samsung Galaxy S III] Casper34:
Cool, I miss having all the adjustments from KT. Oh well, thanks!

Sent from my ghost white SGS3!
[Verizon Samsung Galaxy S III] Samsung.Galaxy.S3:
Yep. I saw that same messed up Youtube app when I was on M9 and M10. Thus I reverted back to M8. Bluetooth, Youtube, etc. all working just fine on M8.
[Verizon Samsung Galaxy S III] XdrummerXboy:
Noticed that for the first time last night, also, some videos just won't play, I keep getting "server error" I think, I don't know if its related, and its not all videos.
[Verizon Samsung Galaxy S III] chowner:
Is it not going to be on Verizon now? Google promised Verizon customers big things this year.
[Verizon Samsung Galaxy S III] mastamoon:
Im going to guess there is no way in hell a nexus device will ever roll on VZW again.. but stranger things have happened. That would be pure win for me since I still have unlimited data on VZW :)
[Verizon Samsung Galaxy S III] Samsung.Galaxy.S3:
Just installed cm-11-20140926-NIGHTLY-d2lte and bluetooth (receiving and calling out) is working fine. The person on the other end can now hear me. Youtube is working without that strange issue. However I went a different route. I pulled the youtube.apk out from gapps and installed it via the Google Play store. Maybe I should have left it in gapps and see if it'll work with this nightly version.

EDIT: spoke too soon. BT is now not working. Strange.
[Verizon Samsung Galaxy S III] Casper34:
Can anyone confirm that superuser does not allow you to hit the allow option on M8?

I've tried to install a few different font installers and I cannot click the allow button. I've tried installing superuser, supersu, and something else. Non will allow me to hit allow.

Sent from my ghost white SGS3!
[Verizon Samsung Galaxy S III] capt730:
I just downloaded it....going to try it out too. I didn't try it out after the 9/25 update, so hopefully this works.

** Still no audio on incoming bluetooth. Using Stock or Liquid, BT works fine.
[Verizon Samsung Galaxy S III] jasonbtx:
Can anyone confirm that superuser does not allow you to hit the allow option on M8?<br />

<br />

I've tried to install a few different font installers and I cannot click the allow button. I've tried installing superuser, supersu, and something else. Non will allow me to hit allow. <br />

<br />

Sent from my ghost white SGS3!<br/>

Set option in SU to auto allow worked for me.
[Verizon Samsung Galaxy S III] aromig:
This problem can happen if you are running an app that overrides screen brightness/color settings. For example, with Lux, I have to put it into speep mode (temporarily disabling it) to allow root access permission for an app. Lux also used to create issues with sideloading apps, but newer versions of it automatically temporarily sleep during an installation.

Sent from my GS3 running CM11
[Verizon Samsung Galaxy S III] Casper34:
Wow!!! I am running lux and I forced stopped it and had no issues. That's weird.

Thanks for the info!!!

Sent from my ghost white SGS3!
[Verizon Samsung Galaxy S III] mastamoon:
http://review.cyanogenmod.org/#/c/68643/ looks like this is the cause.. Im reverting this in my builds for now. Ive been wondering for a long time why I cant accept new SU requests. Didnt realize LUX was the culprit.
[Verizon Samsung Galaxy S III] aromig:
Interesting, makes sense why they implemented this limitation though. Wouldn't want apps installing themselves and giving themselves root privilege. Shenanigans. However, Björn Lundén is incorrect about CM's brightness settings having essentialy the same features. When CM allows subzero settings, I might consider it. As is, the cave troll that I am finds zero too bright in many situations. Thanks for the link.

Sent from my GS3 running CM11
[Verizon Samsung Galaxy S III] mastamoon:
Yeah I get it.. but I generally dont install any odd apps that I would have to worry about clickjacking. Ive had my SU set to auto allow SU requests since I couldnt hit allow anymore.. Im sure that is MUCH MORE RISKY! :silly:
[Verizon Samsung Galaxy S III] aromig:
What's that about the road to hell again? I agree, needs to be a better solution.

Sent from my GS3 running CM11
[Verizon Samsung Galaxy S III] rhcreed:
Anyone else try this version and give a yeah or nay to bluetooth? Thx!
[Verizon Samsung Galaxy S III] daruiner:
Help?

Hey all, the past few M releases have given me odd behavior with call volume, and volume in general. I'm on VRBMF1 baseband if that makes a difference; I don't think that's been upgraded since I went to CM well over a year ago.

A couple releases back the phone call volume was extremely quiet and I could never get it to turn up to a reasonable level. It got a little better, maybe around M8 or M9, but now I'm on M10 and everything is obnoxiously loud. When I'm on a phone call, even with the volume all the way down, it sounds like I'm on speaker phone; people 10 feet away can hear my conversations. If I turn the volume all the way up then back down, it reduces somewhat, but it doesn't seem to be as granular as I would expect. Same thing on speakerphone... I wipe cache and davlik when I upgrade, and just did it again for good measure, but it hasn't seemed to help at all. Is there a properties file somewhere on the filesystem that I can modify manually to adjust the ratio of volume adjustment granularity?

In addition to this, when using Chrome and trying to watch videos embedded in webpages, I get thrown back to the home screen, devoid of icons or the ability to pull down the menu or hit the home button. All I can do is power off my phone by long-pressing the power button or pulling the battery.

Needless to say, I'm a bit frustrated and at a loss of what to try. Is there some log gathering I could do to provide something useful? Is there other specific information I can provide? I apologize for being so vague, but I simply don't have the time in the day to read through 300+ pages on a forum to find all the tricks of the trade :(

I'm honestly considering just reverting back to stock, but I'm not even sure what the best way to do that would be at this point. I don't flash my devices all the time, other than just using the built-in CM updater, so every time I want to do so I end up having to browse through threads for hours upon end to find what I'm looking for. At this point, though, I haven't found anything recent on reverting to stock. I'm on VRBMF1 and CyanogenMod 11 M10. Can I simply get a stock rom and flash it from Recovery, or do I need to get Odin and put this into download mode to do it right? I downloaded Kies but when I plug the phone in I get a dialog box that says "The connected device is not supported by Kies 3." Do I need to download Odin and go into download mode and nuke it all?

I'm apprehensive to do much other than take the M releases at this point and keep updating and hope it just gets better. I don't have any other backup phone so I can't afford to brick this, even a soft brick for a few hours since I'm on call this week and next. Can anyone throw me a life line? I'd really appreciate it.