Sound problems - Samsung Galaxy S (4G Model)

Ok. Here's the skinny. About 3 weeks ago, my phone decided that it didn't want to charge anymore. Ok. I can deal with that. Then it decided about 3 days later that it didn't want to produce sound from the 3.5mm jack. Ok. I can deal with that too. Now, just recently, it decides that it doesn't want to produce sound from the rear speaker. Hmm. Actually. Ringtones and notification tones I can hear. But I can't hear the 'click' that you would normally hear when you make a selection. The feature is turned on in the settings menu. What really bothers me is that I can no longer hear music or any audio from games I play on the device. For a while, I was only able to hear audio from the rear speaker and that would be fine. But now its come to the point to where I can't hear anything but the notification tones and ringtones. I've tried wiping the phone and re-installing the OS. It fixs the problem for a few hours. Then it will revert back to the way it was. I also thought it might be a corrupted file inside the ROM itself on the SD card. So I replaced the ROM file on the card. Also fixed the problem for a little bit, but soon reverted back to old ways. I'm running Valhalla Final with no tweaks or new kernels, irreguardless of what my signature may say. My next step is to start over without using TB. Reinstall all the apps that I use one by one. When I reinstall the OS, I never reinstall the system apps, just so you know. I'm at a loss gang. If anyone has any kinds of suggestions, they would be greatly appreciated.

Flash back to stock with heimdall and flash Valhalla again.

One thing I forgot to mention about this problem. Since my phone no longer charges via the charge port, i'm unable to connect it for odin/heimdall. When I go into download mode, no matter how I hold the cable it won't recognize on the computer. However, i'm able to get it into mass storage mode if I hold it just right when i'm connected to the computer.

Just wanted to give everyone an update in case someone has the same issues. With great patients and a very steady hand, I was able to get my charging cable to stay connected to my phone for a brief time. Still, won't charge though. Oh well. Anyways. I ran Gremlin Remover on the phone and got back to stock. Fixed the sound problem. th3controller had mentioned to use Heimdall. Thx for the suggestion. Couldn't get my phone to connect long enough to run it. But the oneclick GR did the job. Also fixed the sound. So anyone who has this problem, flash back with GR to get all the crap out and load ur rom again. Mod can close this thread now.

Related

fuze video pop up issue

been flashing roms for a while now and everything was great until recently. i have this annoying video pop up problem that i cant seem to figure out if its the phone or what. what happens is randomly the tv/video out pops up and the screen turns to landscape mode. then all sound is lost. ive flashed original stock rom but the problem still happens even running stock. i cant figure out if its the phone and i need to do a warrenty exchange or if its something else. i am hard spld and security unlocked. if anybody else has this problem or had this problem and know of a solution id greatly appreciate it. i dont think its the way i flash roms. i flash with sd card thats formatted fat 32. sim card out and hard reset after first boot.
Sounds like you are describing the TVOUTPopup feature.
Usually, the TVOUTPopup only appears when the A/V Cable (extra cable) is physically connected to the device.
At first guess, I would be inclined towards a faulty USB connector.
yes it is the tv out pop feature. whats wierd is that its the new look from a different rom build. whatever rom i run (right now stock). when the screen comes up it turns landscape and has 4 colorful icons to choose from. internet,youtube,photos,and powerpoint office. once i hit the x button or hit close then it will keep repeating and keep the screen in landscape even though i havent slid out the keyboard. after multiple times closing the app it will stop doing it for a bit but then do it again few hours later.
Since you've tried different ROMs and are seeing the same behavior, I'm inclined to think it's hardware related. Assuming you have nothing connected to the device at the moment except for the SIM, examine the USB connector very closely for signs of damage.
If all looks ok, perform a hard reset and flash the Official HTC 5.05.405.1 ROM/Radio (should eliminate possibility of garbage in ROM) to the device and confirm that the behavior still occurs. If the problem persists, that would confirm it to be hardware.
HTH,
well i flashed the new att fuze rom. so far so good. no popup yet. this happened before though when i thought i fixed the problem. but after running a new rom for about 4 days it came back. if it is a hardware issue then my fuze needs to be exchanged right? thanks for all your help.
I have same issue with my FUZE (constant "Video Out" pop-up message, often switches to landscape mode, sound is off). Have you found any solution to this?
P.S. ...

[Q] Inspire thinks it's in a car dock with non-Inspire based kernels

Now, from what I can gather, this problem stems from a faulty or dirty Micro-USB port. I tried compressed air, but it did nothing for me.
I decided to do a complete unroot, S-ON, factory restore and call HTC to see if I could get it fixed. To my surprise, the problem vanished. Thinking I had lucked out and that fixed it, I re-rooted the phone and the problem still didn't reappear.
Then, thinking I would start small, I flashed a Sense kernel. As soon as I rebooted it went straight to Car Home and began answering in speakerphone. For laughs I went ahead and flashed MIUI then CM7, both of which exhibited the same behavior.
After all of this, I got to wondering just why the stock ROM and kernel worked but nothing third party would. Then it hit me that all the 3rd party stuff I had been using were DHD ports, and not based off the Inspire. I downloaded and flashed ClearDroid, which has an Inspire base, and the problem is once again dormant.
The only sense I can make from it is that HTC has implemented some kind of fix for shoddy USB ports in the Inspire kernel.
So now here's the question: Does anybody know anything about this, and would it be possible to implement said fix in, say, and AOSP kernel?
When you flash a Rom there is a folder created called data on the root of your phone. This contains many files that control various settings on your phone. There is a file in particular where cardock settings get synced in data/data/Com.android.providers.settings/databases/settings.db. When you sign in with your google account some of these settings get restored to the mode in which you had it in when you wiped your phone. This is what causes some people to think that parts of their old Rom are bugging out their phone, I guess in a way it is, but its googles fault. The car dock is getting resynced to being on even though you haven't done anything. In order to fix it you must use SQL editor to open the database and look for the carmode or dock settings and set them back to 0. Once you do this it the next time the phone autosyncs it will save your newer settings.
Also Im pretty sure when your rooted this setting will take effect as to where a nonrooted phone doesn't allow the permission to execute the command.
Gizmoe said:
When you flash a Rom there is a folder created called data on the root of your phone. This contains many files that control various settings on your phone. There is a file in particular where cardock settings get synced in data/data/Com.android.providers.settings/databases/settings.db. When you sign in with your google account some of these settings get restored to the mode in which you had it in when you wiped your phone. This is what causes some people to think that parts of their old Rom are bugging out their phone, I guess in a way it is, but its googles fault. The car dock is getting resynced to being on even though you haven't done anything. In order to fix it you must use SQL editor to open the database and look for the carmode or dock settings and set them back to 0. Once you do this it the next time the phone autosyncs it will save your newer settings.
Click to expand...
Click to collapse
I'll try that, but I can completely wipe my phone (cache, system, data, d-cache), flash CM 7.1.0, and without even logging into my Google account it happens.
After searching it seems this is a common problem with the phone. Some people where able to fix it and some where not. Even when it does go away for a while it will re emerge and get worse.
Some of the fixes are
1. turning airplane mode on for 10 min and then shutting it off
2. Changing chargers(dont ask me)
3. Blowing out port which you said you tried.
I am still not 100% its not some internal issue but why even bother if the hardware is malfunctioning.
I would start the warranty process and get it replaced.
Backing up to the beginning.....Are you flashing ROMs or kernels? Seems to me you are flashing ROMs but keep using the word kernel.
Why not just remove the car dock app from the ROM or use Titanium Backup to freeze it?
Agoattamer said:
Backing up to the beginning.....Are you flashing ROMs or kernels? Seems to me you are flashing ROMs but keep using the word kernel.
Why not just remove the car dock app from the ROM or use Titanium Backup to freeze it?
Click to expand...
Click to collapse
Both.
With the stock ROM and kernel, everything is fine. With the stock ROM and a DHD-based kernel it happens. With any AOSP ROM it happens.
Removing the Car Dock app keeps it from launching, but the phone still defaults to speakerphone for all calls (incoming and outgoing).
Gizmoe said:
After searching it seems this is a common problem with the phone. Some people where able to fix it and some where not. Even when it does go away for a while it will re emerge and get worse.
Some of the fixes are
1. turning airplane mode on for 10 min and then shutting it off
2. Changing chargers(dont ask me)
3. Blowing out port which you said you tried.
I am still not 100% its not some internal issue but why even bother if the hardware is malfunctioning.
I would start the warranty process and get it replaced.
Click to expand...
Click to collapse
The problem about warrantying it is when it's in a stock state, it works fine.
I've never dealt with HTC, but I can't exactly see it going over well if I call up and say "My phone acts funky when I run CyanogenMod".
The airplane mode fix is something I haven't heard before. I guess I'll give it a go.

HELP! SGS4G Multiple issues: no sound in calls, music, and screen remains on in call!

I have been experiencing some issues with my phone recently. I have flashed multiple roms and everything was working fine for the past 3 months or so. Last week I flashed Hebrew Valhalla, it worked fine for a few days then all hell broke lose! I started experiencing the following issues with the phone:
1. In calls, people can hear me but I cannot hear them through the front speaker. I have to either put it on speakerphone or use my headphones.
2. Whenever I cannot hear people in calls (issue #1 above) then there is also no sound coming from the back speaker when I play music. It only works with headphones.
3. Sometimes when I play music, sound only comes from the phone's speaker. Yes the tables literally turn! Even if I plug in headphones, it keeps playing through the phone's speaker. I use stock music player no mods nothing and yes my headphones and their jacks are good I tried multiple ones.
4. The screen does not turn off while in calls. I used 2 apps to test the proximity sensor and it is working fine. Sometimes when on a call the screen randomly turns on and off but most of the time it remains on.
5. Although the vibration intensity is set to max, when typing, the intensity is random. Sometimes it is strong, other times it is weak. Completely random and it is only for typing. It works fine for notifications and pressing back button or whatever. The keyboard is swype and it used to work fine before.
SOMETIMES when I reboot the phone, Issues #1,2 and 3 fixes themselves; I can hear people in calls, music works fine both in speaker and headphones when necessary, but issue #4 is persistent.
The phone has not taken any falls/hits or anything, so I doubt it can he hardware related? So I assumed it is software related, I went to flash other roms, including the ones I used previously that was working fine and still nothing!!! I even flashed Heimdall one click and started from scratch, and still the same problems in the stock rom.
I have spent days searching all over to no avail. Please if anyone knows the solution or workaround to any of the issues above it will be greatly appreciated!!!!!
How old is the phone? If I were you and it's still under warranty I would consider a handset exchange through your phone provider, and if you choose that method make sure you go back to stock an unroot first before you send
Sent from my SGH-T959V using XDA
Cannot do
The warranty has long expired, so that's not an option.
Look for the Gremlin Remover in the Dev section.
Trying
I have been trying for the past 5 hours to get the GR to connect to the phone but it just is not working. I have tried installing and uninstalling all drivers rebooting phone, pc, remove battery everything and it just does not work!!!
The only time GR connects to the phone is when it is starting up, or when the os has loaded up fully. whenever I reboot to download mode it disconnects and never connects back to odin when in download mode. What am i doing wrong? I used the drivers in the GR file but it does not work.
Can anyone link to the drivers that will make odin see the phone while in download mode?
Look at the guide in the second link of my signature. Read the notes about drivers, odin and heimdall. You need to completely, thoroughly and patiently make sure you remove them all.
Go to the wiki for the samsung drivers or use kies mini to install the drivers. ODIN is a samsung software and they use the same drivers.
Still not working
So I found the right drivers and just finished flashing GR twice and the problems are still there. after flashing GR the second time I just flashed Hebrew Valhalla and the problems are still there
I really dont think there is anything else I can do?
Did you do ALL of the steps that Thomas posted? Not just the flashing GR.
Yes I did all the steps: 1, 2 then 3, not the "Filesystem Cleaner" part.
You have nothing to lose doing all the steps.
Ok I will do the Filesystem Cleaner part now and update in a while
EDIT:
I installed the android SDK to connect to adb. Thomas's instructions says to go to recovery mode, but the pc only see's the phone as adb when the phone is booted up in normal mode, not when it is in recovery mode.
I used the universal driver installer, is there specific adb drivers for recovery mode?
So before I got the adb to work I kept rebooting the phone and pushed and removed the headphones in the headphone jack multiple times and I was suprised everything started working. I could how hear people in calls, the screen turned off fine during a call, music worked fine. Rebooted again and everything still worked fine! My memory card was formatted so I copied back some of the files that were on it (music, pictures and apk installers for certain apps, and titanium backup folder). I went to install my apps from the apk's not titanium backup, so I did not restore any data just fresh install the apk's....
.....Rebooted the phone and all the problems came back!!!! I tried uninstalling the apps and reboot multiple times but the problems remained, so I said I will try the entire process again.
Ok so I found the drivers and completed ALL the steps now including the adb stuff and the filesystem cleaner. The status was already clean but I still ran the cleaner just to be safe. Then I flashed Gremlin Remover again and the problems still exist. I flashed Octane 3, problems still exist. flashed Hebrew Valhalla and the problems were still there...rebooted multiple times and the incall volume is working FOR NOW, but the screen does not turn off anymore.
I pushed the headphones in and out many times as it worked the first time but it made no difference now. I really do not know what more is there to do
How are calls just using your phone? No headphones. If things were fine before restoring your sd card shouldn't that tell you there is a good chance something on your sd card is messing with your phone?
You should start over again. Be thorough. Do all the Gremlin Remover steps. Leave your sd card fresh after format. Install apps one at a time with time between from the playstore. Don't mess with your headphones yet. And see what state your phone is in.
It could be your phone. An app. Your sd card or some data on it. Or your headphones. Process of elimination.
Do you have accidental damage insurance? Hammer anyone?lol
Seriously though, with using the gremlin remover and system cleaner processes, everything bad should have been removed. However, you stated that the problems reoccoured after restoring your sdcard. My guess would be either a virus (yes it is possible to get a virus or malicious file on our phones) or a corrupt file/files that is contained in your files that you restored to your sdcard. As much of a pain in the ass it may be, you should restore each file one by one and test. Once the issue reoccours, then you know what is the cause. there are some directories/files you should not restore:
Code:
.android_secure
.cache
Android
CachedImages
data
gps
LOST.DIR
temp
tmp
Voodoo
and any folders that pertain directly to any apps you use like 360launcher, goweather, etc.
As lumin said, everything worked fine until you restored your sdcard...
lumin30 said:
How are calls just using your phone? No headphones. If things were fine before restoring your sd card shouldn't that tell you there is a good chance something on your sd card is messing with your phone?
You should start over again. Be thorough. Do all the Gremlin Remover steps. Leave your sd card fresh after format. Install apps one at a time with time between from the playstore. Don't mess with your headphones yet. And see what state your phone is in.
It could be your phone. An app. Your sd card or some data on it. Or your headphones. Process of elimination.
Click to expand...
Click to collapse
Sadly, this is where I am right now. I did start all over again, formatted the card and only put Hebrew, Octane and Anton's kernel. This is all that is on the card, when I installed them some of the default folders were created. I am yet to put anything else on the memory card, and at the time of this typing I only have basic market apps installed, nothing from transferring from pc to memory card or anything.
1. I have fully cleaned the system using all the steps in GR so I doubt the problem can be with the software on the phone.
2. I doubt it can be an app causing it because even after restoring the official rom just after GR it still does not work.
3. I am not sure if it can be the memory card, since I formatted it so many times, if it had a virus shouldn't it be gone by now? Not sure, just asking. I have some other memory cards handy I will format them and start back from square one again to see how it goes.
4. As for the headphones, I tried different headphones all the same thing. If anything then the problem about the incall sound might be with the headphone port itself. Maybe the phone's hardware or something in that port got stuck or something just something that is making the phone detect a headphone when there is actually none, maybe that's why...that's the most plausible thing I can think of relating to the incall and music volume. Now since I pushed it and out multiple times that maybe fixed it? Not sure..
As for the screen not going off I have no idea; so I will do everything again using a new memory card, not restoring anything, only install market apps one at a time and let you know how it goes.
I followed all the instructions down to the last letter. Did everything over. Removed battery left for some time. Formatted new memory card and only put the cleaner, one mp3 song for testing, Octane and Anton's kernel on it. Did the adb cleaning. Flashed Gremlin Remover. Left for 15 min. Flashed Octane and then Anton's kernel. Reboot and waited 15 min. Did not install anything whatsoever. First thing I did: make a call and play the mp3 file and suprise!! All the problems were still there. Nothing changed. Screen still remained on, no sound in call, no sound from music player; only through headphones like in square 1. Pissed off to the max.
I quit.
sherman619 said:
I followed all the instructions down to the last letter. Did everything over. Removed battery left for some time. Formatted new memory card and only put the cleaner, one mp3 song for testing, Octane and Anton's kernel on it. Did the adb cleaning. Flashed Gremlin Remover. Left for 15 min. Flashed Octane and then Anton's kernel. Reboot and waited 15 min. Did not install anything whatsoever. First thing I did: make a call and play the mp3 file and suprise!! All the problems were still there. Nothing changed. Screen still remained on, no sound in call, no sound from music player; only through headphones like in square 1. Pissed off to the max.
I quit.
Click to expand...
Click to collapse
Honestly, if you did all that, your device should be running it's best ever... You may have some sort of hardware malfunction. Even after trying different ROMs you still have the same issues correct?
I can tell you, I started experiencing some really bad things (not near as bad as yours) after I flashed a ROM WIP, and it took me several flashes to get my phone up and working again. But the only thing that was even remotely hardware related was the mis-calibration of the screen... I have to say, your problem is one of a kind...
However, have you tried pulling a logcat to see if by some chance there was something in there?
thomas.raines said:
Honestly, if you did all that, your device should be running it's best ever... You may have some sort of hardware malfunction. Even after trying different ROMs you still have the same issues correct?
I can tell you, I started experiencing some really bad things (not near as bad as yours) after I flashed a ROM WIP, and it took me several flashes to get my phone up and working again. But the only thing that was even remotely hardware related was the mis-calibration of the screen... I have to say, your problem is one of a kind...
However, have you tried pulling a logcat to see if by some chance there was something in there?
Click to expand...
Click to collapse
I don't know anything about logcat and how to interpret it. I see nearly 20k lines of text when I did it, what exactly should I look for?
I added it to my dropbox account if it is going to be helpful, here is the link:
This is the logcat I saved from my phone. Click it
I'm almost positive that it's some mechanical/electrical problem with the headphone jack. Something is stuck there, or it's dirty, so the controller erroneously detects like something is always plugged in. Hint: you said earlier that it suddenly started working when you were actively plugging-unplugging headphones.
AntonX said:
I'm almost positive that it's some mechanical/electrical problem with the headphone jack. Something is stuck there, or it's dirty, so the controller erroneously detects like something is always plugged in. Hint: you said earlier that it suddenly started working when you were actively plugging-unplugging headphones.
Click to expand...
Click to collapse
Yes I believe so too. I will try to open the phone to see what I can find concerning the headphone issue.
What about the screen not going off? Any suggestions?

[Q] Ideas on JellyBam issue?

Hi, everyone. First I want to thank everyone who takes their time to come and help people like me who mess with things we don't know anything about - such as rooting phones, etc
I installed JellyBam 4.0.0 on my (US T-Mobile) HTC One S S4 earlier this evening. Everything so far seems to be working fine except there is no external audio - no ringtone sound, no radio or music file sound, no notification sound, etc. However, the headphones work fine. I'm not great with tech things, but I'm not a complete idiot, either. I've searched for similar issues and can't find one posted, don't see any settings that may be causing the issue... I'm at a loss.
JellyBam was installed on TWRP recovery and the boot.img was flashed immediately after installation via fastboot. I'm trying to think of what other information from me would prove helpful, but I can't come up with anything else.
So, can anyone offer any ideas as to what the problem (and solution!) may be? I will add that immediately prior to beginning the flash of the ROM and boot.img, I updated the HTC drivers through HTC Sync/Windows 7.
Thanks for any insight or ideas.
david251 said:
Hi, everyone. First I want to thank everyone who takes their time to come and help people like me who mess with things we don't know anything about - such as rooting phones, etc
I installed JellyBam 4.0.0 on my (US T-Mobile) HTC One S S4 earlier this evening. Everything so far seems to be working fine except there is no external audio - no ringtone sound, no radio or music file sound, no notification sound, etc. However, the headphones work fine. I'm not great with tech things, but I'm not a complete idiot, either. I've searched for similar issues and can't find one posted, don't see any settings that may be causing the issue... I'm at a loss.
JellyBam was installed on TWRP recovery and the boot.img was flashed immediately after installation via fastboot. I'm trying to think of what other information from me would prove helpful, but I can't come up with anything else.
So, can anyone offer any ideas as to what the problem (and solution!) may be? I will add that immediately prior to beginning the flash of the ROM and boot.img, I updated the HTC drivers through HTC Sync/Windows 7.
Thanks for any insight or ideas.
Click to expand...
Click to collapse
Change the ring volume and it should kick in.
Darknites said:
Change the ring volume and it should kick in.
Click to expand...
Click to collapse
Thank you. I just tried that and there's no change. Also went into the sound menu, turned everything down (volume settings) then opened it again and turned everything back up. No change.
I suppose I could walk around everywhere with me headphones on I love this ROM.
david251 said:
Thank you. I just tried that and there's no change. Also went into the sound menu, turned everything down (volume settings) then opened it again and turned everything back up. No change.
I suppose I could walk around everywhere with me headphones on I love this ROM.
Click to expand...
Click to collapse
Are you doing this with the headphones still plugged in?
No, I didn't. But after your question I did - still no change
david251 said:
No, I didn't. But after your question I did - still no change
Click to expand...
Click to collapse
Hmm not sure then other then doing a wipe and try the volume when it first boots.
Ok. Thanks for the time. I'll try that.
Sent from my HTC One S using Tapatalk 2
Darknites said:
Hmm not sure then other then doing a wipe and try the volume when it first boots.
Click to expand...
Click to collapse
Do you think he might have to do what I did for the sd card, maybe that will kick in what he is missing plus doing the full wipe and re-flashing the ROM just wondering?
TheCrow1372 said:
Do you think he might have to do what I did for the sd card, maybe that will kick in what he is missing plus doing the full wipe and re-flashing the ROM just wondering?
Click to expand...
Click to collapse
No its an old bug that's been there for as long I can remember lol but changing the volume should fix it.
Darknites said:
No its an old bug that's been there for as long I can remember lol but changing the volume should fix it.
Click to expand...
Click to collapse
Just to make sure I understand (because I am technology-challenged), when you say changing the volume - I assume you're talking about either using the volume rocker on the side of the phone or simply going into Settings > Sound and changing the volume sliders there.
Correct?
david251 said:
Just to make sure I understand (because I am technology-challenged), when you say changing the volume - I assume you're talking about either using the volume rocker on the side of the phone or simply going into Settings > Sound and changing the volume sliders there.
Correct?
Click to expand...
Click to collapse
Ya I mean the first but both ways should work but do it without the headphones.
---------- Post added at 04:13 PM ---------- Previous post was at 04:11 PM ----------
Oh just popped in the head but try having music playing and do it.
I did. Tried it when searching ring tones, then tried it with Google Music playing a track, tried it with local radio playing and tried it with nothing at all playing.
So let me ask you this - can I make a backup (Titanium Backup) of all my current settings so that when I wipe/reinstall, I don't have to redownload all my apps and redo everything?
Lol - I gotta say, though, as irritating as it is to have only this one issue... I love this ROM and the way my phone works with it. It's worth the hassle if I can get it fixed. (Especially considering I almost bricked it yesterday before finally finding this ROM.)
I should really not mess with stuff I know nothing about. But I just can't help it.
david251 said:
I did. Tried it when searching ring tones, then tried it with Google Music playing a track, tried it with local radio playing and tried it with nothing at all playing.
So let me ask you this - can I make a backup (Titanium Backup) of all my current settings so that when I wipe/reinstall, I don't have to redownload all my apps and redo everything?
Lol - I gotta say, though, as irritating as it is to have only this one issue... I love this ROM and the way my phone works with it. It's worth the hassle if I can get it fixed. (Especially considering I almost bricked it yesterday before finally finding this ROM.)
I should really not mess with stuff I know nothing about. But I just can't help it.
Click to expand...
Click to collapse
Load TWRP and do a backup there, then still in TWRP do factory reset and reboot and skip over the signing in stuff and then try playing with volume without plugging in the headphones and if this still don't work you could try in TWRP factory reset and then system and them reflash the rom and if this still some how don't work you can restore the backup in TWRP.
Ok, I'll do that now - but first, one more stupid question. After this, I'll leave you alone.
When I first installed this ROM, I went through Fastboot to flash the boot.img. Do I have to do that again if reflashing the ROM, or can I skip that step?
Thanks for all your guidance. Seriously.
Update on thread
So I followed the instructions above.
Went into TWRP, did a factory reset and rebooted. Played with volume. Still no external audio.
Went back into TWRP, factory reset, wiped system, reflashed ROM (did NOT manually reflash boot.img in Fastboot) then rebooted. Played with volume. Still no external audio.
Went back into TWRP and restored the backup - so I'm still left with a killer phone with no external audio, ringtone, etc.
Hmmm.... hope nobody calls when I can't hear/feel the vibrate or have my headphones in
That's strange though - I find no other threads mentioning a glitch like this and, except for this one issue, the phone/ROM works flawlessly. It even fixed the wifi connection problem that always existed with the stock phone/ROM and I know a lot of people with this phone have had that problem. With the stock, the wifi always had a problem (from the first day) connecting to my home wifi. Sometimes it would connect but normally it would take a long time (an hour or more) before finally connecting and still other times it wouldn't connect at all. Now if I leave the house, it connects as soon as I pull up in the driveway and if I power down/reboot, it connects instantly upon reloading.
Just before installing the ROM (the first time) I connected with HTC Sync via my pc/usb and made sure drivers were up to date, which is why I'm thinking it's not a driver issue. Would you agree?
david251 said:
So I followed the instructions above.
Went into TWRP, did a factory reset and rebooted. Played with volume. Still no external audio.
Went back into TWRP, factory reset, wiped system, reflashed ROM (did NOT manually reflash boot.img in Fastboot) then rebooted. Played with volume. Still no external audio.
Went back into TWRP and restored the backup - so I'm still left with a killer phone with no external audio, ringtone, etc.
Hmmm.... hope nobody calls when I can't hear/feel the vibrate or have my headphones in
That's strange though - I find no other threads mentioning a glitch like this and, except for this one issue, the phone/ROM works flawlessly. It even fixed the wifi connection problem that always existed with the stock phone/ROM and I know a lot of people with this phone have had that problem. With the stock, the wifi always had a problem (from the first day) connecting to my home wifi. Sometimes it would connect but normally it would take a long time (an hour or more) before finally connecting and still other times it wouldn't connect at all. Now if I leave the house, it connects as soon as I pull up in the driveway and if I power down/reboot, it connects instantly upon reloading.
Just before installing the ROM (the first time) I connected with HTC Sync via my pc/usb and made sure drivers were up to date, which is why I'm thinking it's not a driver issue. Would you agree?
Click to expand...
Click to collapse
Ya not sure what's up if you still got your backup you could try another rom like CM10 to see if its the same. The wifi confused me, everybody else find AOSP not as good at wifi, for me Sense let me set the router how ever I want but on AOSP I have to have it at default settings.
Final update on this thread
Earlier, I wiped everything (through hboot) and reflashed JellyBam. Once rebooted, not only did I still not have audio, but the wifi connection went back to normal - it would connect, but not without difficulty/delays. Strange,
Since I can't feasibly go without a ringtone/alarm/notifications (I use my phone for my business) I rewiped everything from TWRP and installed Dark Jelly v23 to include the Fusion Ultimate kernel. On first boot, still no sound but the notes here mention that may be an issue until it's rebooted a second time. So I set everything up, played around with the same ideas we were using earlier in this thread (to no avail) and then rebooted.
Wifi is the same as it always has been (with the exception of the glorious several hours when it worked like a champ on JellyBam). That's no big deal - I'm used to it and know it's an HTC One S quirk.
But....
Sound is back :good:
david251 said:
Earlier, I wiped everything (through hboot) and reflashed JellyBam. Once rebooted, not only did I still not have audio, but the wifi connection went back to normal - it would connect, but not without difficulty/delays. Strange,
Since I can't feasibly go without a ringtone/alarm/notifications (I use my phone for my business) I rewiped everything from TWRP and installed Dark Jelly v23 to include the Fusion Ultimate kernel. On first boot, still no sound but the notes here mention that may be an issue until it's rebooted a second time. So I set everything up, played around with the same ideas we were using earlier in this thread (to no avail) and then rebooted.
Wifi is the same as it always has been (with the exception of the glorious several hours when it worked like a champ on JellyBam). That's no big deal - I'm used to it and know it's an HTC One S quirk.
But....
Sound is back :good:
Click to expand...
Click to collapse
Lol the phone does love to be picky.

Getting an OTA update after installing TWRP and rooting OR use RUU?

I have an HTC One E8... I know, it's ancient... But... It's been a good phone until this past year when it really started dragging. Takes forever to do anything. A year ago, the main camera (is that the front or back camera) stopped working (phone doesn't even recognize that it's there -- flash doesn't work either with a flashlight app). Before that, phone dialing using my Bluetooth earpiece stopped working. Maybe related, but the phone doesn't work as a phone (holding it to your ear). If I'm not using the Bluetooth earpiece, it will only work on Speaker-phone mode (voice command apps such as Google Assistant and song recognition apps like Sound Hound don't 'hear' anything). Lastly, the Bluetooth has been disconnecting for no apparent reason. My earpiece will say 'Phone 1 disconnected', but when I look at the Bluetooth icon on the phone, it still thinks it's connected. Tapping the icon to turn off Bluetooth and then tapping again 'fixes' the problem and it connects again. It's just annoying when it does this in the middle of a conversation (and because, when it happens, the other party doesn't hear me yelling at them to wait because my Bluetooth disconnected because the phone doesn't know that anything is wrong). I had read ones that the Bluetooth drivers for this phone were sketchy. It's strange, though, this this problem has really gotten worse over the past couple of months without me making any changes to the phone. Lastly, the battery has really gone downhill. The phone will unexpectedly shut off around 30% battery. (I even tried the HTC battery recalibration technique -- no joy.) I chalked all of this up (except for the battery issue) to software. I thought maybe a good ol' factory reset (wipe) would fix the issues. For years (literally) it's been nagging me about a system update (Android 6.0). I never did it because the phone was already running slow and it's always screaming about being out of storage space. It hovers around 500MB free most of the time. I don't have that much installed on it. Any apps that will allow it, have been moved to the SD card.
That's the back-story to give you some insight as to what's going on with the phone. I included all of that 'other' stuff (camera and voice dialing issues) in case someone has seen them before and can offer any suggestions there.
So here's where I'm at. I decided to try to do a factory reset to 'refresh' the OS (remove all the patches and updates) and start over. Afterwards, I wanted to run Link2SD with a 64GB SD card so I wouldn't have the space limitations that I'm experiencing now after all of the apps have updated. The other night, after backing up the internal memory and the SD card, I started the process. (BTW, I have another SD card that I'm going to use that I've already partitioned per the Link2SD instructions.) After much trial and error, dead download links, incompatible versions of adb.exe and fastboot.exe I finally managed to get TWRP recovery installed. Then there was the issue of getting a working SuperSU installed. Finally did that. The phone booted and started walking me through the process of setting up my Google account. Everything seemed to go well. The phone was just as speedy as the day I got it. I was even able to restore my 15000 text messages and it was still zippy. It was wonderful! Unfortunately, the camera still doesn't work. Seems like voice dialing isn't working at the moment either. The Bluetooth issue seems to have gone away. Since the camera still isn't working, it looks like I'm gonna have to bite the bullet and get a new phone. This one will just become a 'toy' or a temporary backup phone in the event something tragic happens to the new phone. I'll just use this one on Wi-Fi only to check the weather and maybe play some games (which I had pretty much stopped doing because it was so slow and always out of storage). I would also use it as my portable media device for listening to downloaded podcasts and music while I'm running or riding my bike. It could also (maybe without mobile data) track my runs and rides, etc. As long as it doesn't get slow like it was before, I think it'll do just fine in its re-purposed life. (It was so slow I could barely play music from Google Music and have Google Fit tracking my run at the same time. It would take forever to switch screens!)
Ah, what's this?! Oh, there's that software update again. I guess I'll go ahead and do it before I start setting up a bunch of apps and tweaking the phone to my preferences. Nope! It downloads the OTA update into the Downloads folder and starts the process, but when it reboots, it reboots in Recovery mode into TWRP. I'm now finding that you can't easily do an OTA update after you've rooted your phone and put a custom recovery on it. I've seen lengthy instructions on how to put get a stock recovery.img out of the OTA zip file in the Downloads folder. I've moved it to my PC and pulled the firmware.zip file out. When I try to open the firmware.zip file to get to the recovery.img file, Windows is saying it's corrupted. I also see something about using an RUU.exe or RUU.zip file to restore the phone to stock. I've downloaded the correct RUU .exe file for my Sprint e8 in case I decide to go that route.
Here's my question... I know, finally! Since I don't have really anything on this phone since I did the reset and root, would it just be simpler to use the RUU method to blow it away and start over instead of trying to resolve the corrupt firmware.zip file issue and all of the other steps that follow? That's question #1. Question #2 is this... Will this RUU that I downloaded actually take the phone straight to Marshmallow before it starts walking me through setting up my Google account? If so, that's great! I'm all for the ease of that. I noticed that OTA download was about 250MB, while the RUU download is 1.5GB. Why such a difference? Is it because the RUU is the full-blown deal and not just the patches? I'm fine doing the RUU and then reinstalling and rooting the phone afterwards if that'll work. I still have all the files that I previously downloaded.
Sorry for the novel, but I wanted to be as thorough as possible to eliminate the back and forth "Did you try this?" "Did you try that?" However, if there is anything that I left out that would help with your answer/advice, please don't hesitate to ask. Thanks in advance for any guidance you can give a noob.
lrbarrios

Categories

Resources