- Apr 29, 2015
- 43
- 0
- 0
Hey guys, this is in regards to the Cricket version of the Galaxy S6. It currently has Baseband version G920AZTUU4CPF2.
Since getting the upgrade to Marshmallow a few days ago my volume has been extremely low in almost every regard. Ringtone, notifications, system volume. I'm not sure whether media playback volume is lower but it is adequate. Phone call volume seems lower though it is not unacceptably low.
I've cleared the cache partition but have no idea what else to try. I did a Google search and found a few others having this problem and none seem to have found a solution. The volume is almost inaudible when my phone is in my pocket and I miss most notifications. The lock/unlock screen sound is almost inaudible when holding the phone a few feet from my face.
Has anybody else had this problem? I almost feel like this is something that does not have a resolution that I can affect. Perhaps this will be resolved in a software update eventually. A couple friends with the Galaxy S6 (AT&T) don't have this issue, so with Cricket constantly being behind in updates I think I may have to just wait it out. If anybody has any ideas until then I'd appreciate it.
Since getting the upgrade to Marshmallow a few days ago my volume has been extremely low in almost every regard. Ringtone, notifications, system volume. I'm not sure whether media playback volume is lower but it is adequate. Phone call volume seems lower though it is not unacceptably low.
I've cleared the cache partition but have no idea what else to try. I did a Google search and found a few others having this problem and none seem to have found a solution. The volume is almost inaudible when my phone is in my pocket and I miss most notifications. The lock/unlock screen sound is almost inaudible when holding the phone a few feet from my face.
Has anybody else had this problem? I almost feel like this is something that does not have a resolution that I can affect. Perhaps this will be resolved in a software update eventually. A couple friends with the Galaxy S6 (AT&T) don't have this issue, so with Cricket constantly being behind in updates I think I may have to just wait it out. If anybody has any ideas until then I'd appreciate it.