Alright, so a while back, my loudspeaker started to cut in and out, and when i would fire up a game it would come through all distorted or muffled. Upon exiting the game, i could fire up play music, select a track, and it would play fine. But then back to any other application, and it would be muffled again. Notifications come through the earpiece, and eventually no sounds at all come through the loudspeaker. Then i reboot and its all fine again.
I factory reset, and it did not help. I plugged in headphones (and wheres where it gets interesting) the headphones output the same weird muffled quality of sound that the speaker was producing. So is it not the loudspeaker?
I tried to flash a different rom over, still didnt help it at all. Im not exactly sure whats going on, but nothing i am doing seems to be helping. Can anyone help me?
That doesn't sound like a software problem, that maybe the sound producing hardware ( amplifier ) that seems to be working intermittently, just happens to work when you change applications. Is your device rooted? If so, have you tried to go back to stock via Odin installed stock .tar OS ( kk 4.4.2 ) ?
jimzweb1 said:
That doesn't sound like a software problem, that maybe the sound producing hardware ( amplifier ) that seems to be working intermittently, just happens to work when you change applications. Is your device rooted? If so, have you tried to go back to stock via Odin installed stock .tar OS ( kk 4.4.2 ) ?
Click to expand...
Click to collapse
i have not tried that. do you think my device is okay?
aplacetorest said:
i have not tried that. do you think my device is okay?
Click to expand...
Click to collapse
I think that you should go back to stock or stock rooted, via a recovery backup, or installing a new OS. This would eliminate the possibility of a software problem. So if it works good on stock OS setup, great !!! Then you know its not a hardware problem. If doesn't work properly you will have to replace the device. Now assuming it does work correctly, you can reinstall the other rom that was giving you a sound problem and I would try installing a different kernel. The sound driver in a different kernel my work better.
Hope you can help me - I am desperate to halt the OTA update for my galaxy s4 -
based on everything I’ve read, Samsung did a really bad job on this update, 4.4.2, and they are currently rolling out 4.4.3 and 4.4.4, but of course, the s5 is getting it well before we are.
anyway,
I have been “happily” running 4.3 and just dealing with the bluetooth issues, found enough hacks/fixes for the wifi issue that i have been ok with it since getting 4.3 in November.
There are just too many unworkable issues of battery drain, overheating, losing apps, pics, etc etc etc for me to risk the update to 4.4.2.
HERE’S MY PROBLEM - Somehow, altho i'm fairly technical, the update finally got on my phone (after having kept it off for months) and for the past month or more, I've just been
dealing with the notification, putting it off for 24 hrs at a time.
I guess it finally decided not to allow me to do that any longer, and started the installation without permission. i stopped it by pulling the battery, but when i try to start in recovery mode just so i can clear cache and hopefully reboot without actually installing the new os, I cannot - it goes through (some of) the motions but when i let go of the power button as i should when it's running normally, and would get the options of factory reset, clear cache, et al, it just brings up the android bot and shows that it is continuing to install where it left off. I’ve done this numerous times.
Tried different methods of button-holding and other trouble-shooting based on massive searching, but always get the same result. and I can only pull the battery to stop it.
Am I stuck? Do I have to install now at this point?
I do not want to perform factory reset, guess I'd rather install the 4.4.2 s/w. (altho I can't even get to that option at this point)
Sincerely hope someone out there will respond – I've posted to multiple sites, and no one is responding - gonna have to turn my phone back on at some point soon...
Thanks in advance!!
Roxanne
rkohlin said:
Hope you can help me - I am desperate to halt the OTA update for my galaxy s4 -
based on everything I’ve read, Samsung did a really bad job on this update, 4.4.2, and they are currently rolling out 4.4.3 and 4.4.4, but of course, the s5 is getting it well before we are.
anyway,
I have been “happily” running 4.3 and just dealing with the bluetooth issues, found enough hacks/fixes for the wifi issue that i have been ok with it since getting 4.3 in November.
There are just too many unworkable issues of battery drain, overheating, losing apps, pics, etc etc etc for me to risk the update to 4.4.2.
HERE’S MY PROBLEM - Somehow, altho i'm fairly technical, the update finally got on my phone (after having kept it off for months) and for the past month or more, I've just been
dealing with the notification, putting it off for 24 hrs at a time.
I guess it finally decided not to allow me to do that any longer, and started the installation without permission. i stopped it by pulling the battery, but when i try to start in recovery mode just so i can clear cache and hopefully reboot without actually installing the new os, I cannot - it goes through (some of) the motions but when i let go of the power button as i should when it's running normally, and would get the options of factory reset, clear cache, et al, it just brings up the android bot and shows that it is continuing to install where it left off. I’ve done this numerous times.
Tried different methods of button-holding and other trouble-shooting based on massive searching, but always get the same result. and I can only pull the battery to stop it.
Am I stuck? Do I have to install now at this point?
I do not want to perform factory reset, guess I'd rather install the 4.4.2 s/w. (altho I can't even get to that option at this point)
Sincerely hope someone out there will respond – I've posted to multiple sites, and no one is responding - gonna have to turn my phone back on at some point soon...
Thanks in advance!!
Roxanne
Click to expand...
Click to collapse
Are you rooted?
SiVisPacemParaBellum
OderintDumMetuant
stvn2569 said:
Are you rooted?
SiVisPacemParaBellum
OderintDumMetuant
Click to expand...
Click to collapse
Thanks for responding stvn2569!
Nope, not rooted.
But based on all my searching I sure wish I was and likely will the next phone.
Stock Verizon Galaxy s4 - 32gb - model # SCH-I545
(Sorry, should have put this in orig message)
THis summarizes some of the reason I don't want to update the OS - -
ack - can't post links - will have to type it out if you are interested in all the bugs Samsung saddled us with -
(most egregious is the battery drain, but others are quite serious and hard to live with too)
www(dot)androidpit(dot)com(slash)samsung-galaxy-s4-update-to-android-4-4-2-littered-with-bugs
rkohlin said:
Thanks for responding stvn2569!
Nope, not rooted.
But based on all my searching I sure wish I was and likely will the next phone.
Stock Verizon Galaxy s4 - 32gb - model # SCH-I545
(Sorry, should have put this in orig message)
Click to expand...
Click to collapse
You'll need to root the phone to stop the OTA notifications, it's all very easy.
Go to settings > security > allow installations from unknown sources, check the box
Go to www.towelroot.com
Click on the lambda, download and install the towelroot.apk
Click on "make it ra1n", reboot
Download "SuperSU" from the play store
Upon opening the app, it will prompt you to "update binaries". Do this using the "normal" option
Then download "Root Explorer" from the play store
Navigate to the system and system-priv app folders
In one of those folders you'll find "FWupgrade,apk" and "SDM.apk"
Delete those apk's and no more OTA updates:good:
joshm.1219 said:
You'll need to root the phone to stop the OTA notifications, it's all very easy.
.......
:
Click to expand...
Click to collapse
Thanks, Josh, I appreciate your trying to help, but if you read the original post -
I CANNOT TURN ON THE PHONE, hence couldn't get to settings if I wanted to, BUT - -
It is not the notification that is the issue -
the phone has finally downloaded the OTA update and IS INSTALLING IT. (every time I turn it on)
I DO NOT WANT THIS UPDATE INSTALLED. (see prior post for the reason - it's terribly buggy update - worse than what I have)
I have to figure out how to halt it - when I try to start in "recovery mode", it doesn't give me the options
it normally would - I won't start in a normal recovery mode.
It continues the OS update.
I noted all this in the original post - I completely understand how to get rid of the update notifications.
One doesn't even have to root the phone to do this, you can just rename the SDM apk (like add .bak or something)
Do you have ideas how to stop the installation? How I can turn phone on in recovery mode?
(note the steps I've taken to do that are also in the original post)
I know there are many people out there smarter than me about this - hoping you guys can help...,
rkohlin said:
Thanks, Josh, I appreciate your trying to help, but if you read the original post -
I CANNOT TURN ON THE PHONE, hence couldn't get to settings if I wanted to, BUT - -
It is not the notification that is the issue -
the phone has finally downloaded the OTA update and IS INSTALLING IT. (every time I turn it on)
I DO NOT WANT THIS UPDATE INSTALLED. (see prior post for the reason - it's terribly buggy update - worse than what I have)
I have to figure out how to halt it - when I try to start in "recovery mode", it doesn't give me the options
it normally would - I won't start in a normal recovery mode.
It continues the OS update.
I noted all this in the original post - I completely understand how to get rid of the update notifications.
One doesn't even have to root the phone to do this, you can just rename the SDM apk (like add .bak or something)
Do you have ideas how to stop the installation? How I can turn phone on in recovery mode?
(note the steps I've taken to do that are also in the original post)
I know there are many people out there smarter than me about this - hoping you guys can help...,
Click to expand...
Click to collapse
My bad, I would suggest booting into download mode and flashing the mk2 tar file with odin (3.09 recommended).
I didn't suggest renaming the file because it doesn't always work. Told my brother to do that on his Note 3 (no root method at the time) and it start downloading an OTA upon reboot one day.
joshm.1219 said:
My bad, I would suggest booting into download mode and flashing the mk2 tar file with odin (3.09 recommended).
I didn't suggest renaming the file because it doesn't always work. Told my brother to do that on his Note 3 (no root method at the time) and it start downloading an OTA upon reboot one day.
Click to expand...
Click to collapse
Thanks, Josh!
When you say "boot into download mode" - you mean safe/recovery/download mode right?
(like when one holds (for this model) VolumeUpButton+PowerButton right?)
If that's the case, it doesn't allow me to boot that way. When I do that, it just skips right to
"Installing system update" (with the droid bot)
That's my problem.
Cannot access anything (without allowing the install). :crying:
Have also tried VolumeUpButton+PowerButton+HomeButton. Same.
Drat.
Looks like I may have to accept this OS.
Others I know that have deal with terrible battery drain issues (from 10 hrs heavy use on charge down to 2 hrs)
rkohlin said:
Thanks, Josh!
When you say "boot into download mode" - you mean safe/recovery/download mode right?
(like when one holds (for this model) VolumeUpButton+PowerButton right?)
If that's the case, it doesn't allow me to boot that way. When I do that, it just skips right to
"Installing system update" (with the droid bot)
That's my problem.
Cannot access anything (without allowing the install). :crying:
Have also tried VolumeUpButton+PowerButton+HomeButton. Same.
Drat.
Looks like I may have to accept this OS.
Others I know that have deal with terrible battery drain issues (from 10 hrs heavy use on charge down to 2 hrs)
Click to expand...
Click to collapse
It is Power button click and hold volume down....
rkohlin said:
Thanks, Josh!
When you say "boot into download mode" - you mean safe/recovery/download mode right?
(like when one holds (for this model) VolumeUpButton+PowerButton right?)
If that's the case, it doesn't allow me to boot that way. When I do that, it just skips right to
"Installing system update" (with the droid bot)
That's my problem.
Cannot access anything (without allowing the install). :crying:
Have also tried VolumeUpButton+PowerButton+HomeButton. Same.
Drat.
Looks like I may have to accept this OS.
Others I know that have deal with terrible battery drain issues (from 10 hrs heavy use on charge down to 2 hrs)
Click to expand...
Click to collapse
Like he said, download mode is Power+VolumeDown, press and hold.
UPDATE:
Well, never could get into download mode, so had to accept the OS update to KK 4.4.2
Guess I'm one of the lucky ones, (I do have a fairly new model S4) and I didn't lose apps or contacts.
however,
The Battery Life is TERRIBLE after the 4.4.2 update! Some WiFi issues too.
Seem to have fixed WiFi (for now anyway)
Been searching around and recalibrated my battery, am trying a battery life extender app,
turned off a huge bunch of Samsung and Google apps that evid constantly "ping" and use battery.
It's been a little better, but not a lot.
Hope for 4.4.4 to be available soon (heard 4.4.3 is not a good variant either)
I've Galaxy S4 Verizon - SCH1545 with 5.0.1 Lollipop and Baseband 1545VRUGOF1. Bought a month ago, it worked fine for 15 days but then sound went off. Also I was unable to play any video nor any application is working. Getting error of Unfortunately UI has stopped and(App) is not responding. Upon trying below steps, sound comes sometime and app works fine then but it doesn't stay long when again starts same behavior. I get it when start phone and it doesn't play the sound when shows Samsung logo.
1. Cleared the cache of Play Store, Google Framework and Google Play Services
2. Wiped cache partition and Factory Reseted
3. Rooted the device
4. Unable to install TWRP or CWM
5. Odin gives Nand write error
6. If phone stuck with "Use Verizon Software Repair Assistant...", able to bring it back by CF Auto JFLTEXX-GTI9505.tar.md5. Although Odin gives error but after error, I disconnect the USB cable and phone starts
7. Tried Verizon Software Repair Assistant and Samsung Kies to update the firmware but same issue
8. Can't find GooManager in Play Store. Installed by APK but GooManager doesn't find any list or unable to find Script (to install TWRP)
9. Rooted the phone. Confirmed by Root Checker but Flash Fire shows "are you rooted?"
will be very thankful for anyone who has idea or had same problem.
As far as I understand custom recoveries are only available for MDK. Your best bet is to odin your current build and start there.
Jalh said:
As far as I understand custom recoveries are only available for MDK. Your best bet is to odin your current build and start there.
Click to expand...
Click to collapse
I don't mind any rom or whatever settings are. Just want to solve sound and other issues I'm facing.
I tried Samsung Kies and Verizon Software Repair Assistant to reload the firmware but still the same issue of sound goes off, youtube, apps and videos don't play.
I know its not hardware problem because this all gets ok sometimes after maybe reset, wipe cache, clear play store/services storage or factory reset... then goes off again after some time.
thanks for the reply
noticed one more thing. If I keep it off for few hours, the sound come back. And again goes off after some time.
Hey,
so I recently got the P9000 and I am very happy with it in General. There is just one big Problem, I am very used to Cyanogenmod on all my devices so I tried installing it in this phone, everything worked fine except for the microphone and the Speaker, Calls go through but I cant talk neither hear anything. Everytime I Start the phone it also says AudioFX was shut down. I also Tried listening to music or any sound for that matter but nothing works. I then installed the Stock ROM and everything works like a charm so I can rule out a Hardware issue. But the Stock ROM is just not cutting it for me in terms oft usability and options and I would much rather switch back to CM. Tried it again yesterday, clean install and everything, Microphone and Speaker are not working.... Does anyone have any ideas how to fix this? Any help greatly appreciated.
Read the Thread
Felino41 said:
Hey,
so I recently got the P9000 and I am very happy with it in General. There is just one big Problem, I am very used to Cyanogenmod on all my devices so I tried installing it in this phone, everything worked fine except for the microphone and the Speaker, Calls go through but I cant talk neither hear anything. Everytime I Start the phone it also says AudioFX was shut down. I also Tried listening to music or any sound for that matter but nothing works. I then installed the Stock ROM and everything works like a charm so I can rule out a Hardware issue. But the Stock ROM is just not cutting it for me in terms oft usability and options and I would much rather switch back to CM. Tried it again yesterday, clean install and everything, Microphone and Speaker are not working.... Does anyone have any ideas how to fix this? Any help greatly appreciated.
Click to expand...
Click to collapse
Flash Final 3... this will work for you.
MaStErB_1984 said:
Flash Final 3... this will work for you.
Click to expand...
Click to collapse
First of all thank you for the tip, in the meantime I installed Android 7 beta to have a look at it. Is there any way to go back to Stock ROM on Android 6 so I can install CM13 Final Build 3? I have tried flashing Recovery and STOCK ROM via SP Flash but it won`t work. I click Download, connect the phone while pressing the Vol+ and it says Downloading, goes up to 100% but the red bar is still there, then nothing happens. Every Flash of Stock or CM Recovery I did before that worked just fine so I guess it has something to do with Android 7. If there is no way I guess I`ll stick with Android 7 for now but I´d rather switch to CM.
There is a way...it has to do with the Android...it changes the preloader and the boot partition. Take this file from deepflex: https://yadi.sk/d/40K4mWLauUddk and flash with sp-tools. Finally flash the TWRP-Recovery from Jonny with flashtools. At the end do a full wipe and install the cm13.1 (Final 3) and the opengaaps.
Got it to work, I used a slightly different approach but right now I am finally installing CM13 Final Build 3, lets see if it works out fine! Thanks again for your help :good::good:
Hello, so I changed my screen few weeks ago, and I started to notice that it won't work propelry, in menu or setting it's okay, but when I try to use apps, some of them wont work as it should. For example, i can't take photo in messenger, i can't send good game in Clash Royale. Screen seller sent my some files to update my phone, but I noticed that i can't get into recovery mode, only in factory mode, I tried to do factory reset, OTA update because mine is still 2016-06-08, but it won't update, I also tried flash those files without recovery mode(when you start downloading ant then turning off your phone), but it didn't work. Have any ideas, what it could be?
SliFaZ said:
Hello, so I changed my screen few weeks ago, and I started to notice that it won't work propelry, in menu or setting it's okay, but when I try to use apps, some of them wont work as it should. For example, i can't take photo in messenger, i can't send good game in Clash Royale. Screen seller sent my some files to update my phone, but I noticed that i can't get into recovery mode, only in factory mode, I tried to do factory reset, OTA update because mine is still 2016-06-08, but it won't update, I also tried flash those files without recovery mode(when you start downloading ant then turning off your phone), but it didn't work. Have any ideas, what it could be?
Click to expand...
Click to collapse
Did you replace the screen yourself or was it a kind of Elephone repair ? .. obviously changing a screen is a major kind of thing and (I would assume) it could cause issues if not done properly.
Have you tried to flash the 2016-06-08 Rom in Splash Tools (or a custom ROM) and checking to see if the issue still exists - Im sure if its your screen it would occur on whatever ROM you were using, as its a hardware fault. Thing is if its just a sioftware "glitch"... I would first flash TWRP in flashtools, then flash a ROM from within TWRP and check if the issue still persists.
Obvioulsy if the issue continues once youve tried this I guess your screen is faulty unfortunately
I would recommend using this TWRP version 3.0.2.8. here: https://www.androidfilehost.com/?fid=24727369092696060