Hello,
First I apologize for opening a new thread instead of posting in the CM11 thread, but till now I don't have write privileges there.
I recently unlocked and permrooted my Desire HD then installed Mustaavalkosta's CM11, but as a newbie, I have some issues I require assistance with. To note that I did an extensive reading before I did any rooting and installing a new rom.
1- I find myself not hearing anything during calls. It's sort of like my internal speaker got muted somehow after installing CM11. I tried multiple apps to no avail. I read somewhere that if u fail to flash the boot.img in the rom u might get this issue, but thing is I did flash the boot.img after I installed the rom and the recovery and wiped the cache. I can hear the calls with the external speaker turned on and with the headphone, so I think it's not a hardware issue but a software one. Any fix to this?
2- After each restart, the UI somehow resets itself. I mean many of the settings and widgets I use either get reset or vanish like the sleep option in seetings for example (I put the screen to turn off after a 1 min and it resets to 15 sec after each reboot which is annoying as hell). Also, many apps like Dolphin and GoSMSPro shortcuts vanish from the home screen after each reboot, while whatsapp for example doesn't. I'm not able to figure why some app shortcuts vanish while others don't.
3- I tried to use ART instead of dalvik, but yet again after each reboot, dalvik is back. So effectively, I can't benefit from ART.
4- other minor bugs which I will not mention for now till I solve the 3 main ones.
If someone can provide some assistance (mainly for the first issue which is the major one), I will be very grateful. It's becoming increasingly annoying and embarrassing to turn the speaker on every time I receive a call, bc most of the times I am in a room with other individuals or in a meeting, and I am forced to have them hear the conversations bc not always I can excuse myself.
No one has any input on this?
After wiping data, dalvik cache, android secure, etc... and reinstalling the stock rooted 2.3.5 Rom, I still had the same internal speaker issue on calls. The heaphone icon was on even though there were no headphones plugged. I installed 2 widgets (togggleheadset 2 and headphone fix) and the issue was fixed. To note I had this problem back on my unrooted stock Desire HD before I rooted it and upgraded to CM11 BR3 thinking the new rom will fix this problem.
So after I made the calls work on Gingerbread stock rooted rom, I did a clean wipe once more and installed CM11 BR4. The problem reemerged. And the 2 widgets couldn't be redownloaded bc they are not compatible with kitkat. The other issues mentioned in the OP disappeared, only the incall volume issue remained.
I need to mention that many Desire HD owners have had this problem on their Froyo and Gingerbread stock builds, and usually the 2 widgets I mentioned above helped fix the issue. On 4.4.2, it seems some android users have complained of in-speaker audio volume being very low, so maybe this worsens the issue I had instead of fixing it.
I'm leaning to think that it's mostly a software/code issue, otherwise why would the widgets fix the problem on an earlier version if it's hardware related? hence, there could be a workaround for it on Kitkat if someone knowledgeable cares to look at it. Maybe the code turns off the internal speaker or lowers the volume so much it becomes unhearable. The headphone and external speaker are just fine, I can hear the other person in the call without any problem. It's when I rely on the internal speaker that I hear nothing.
Hope someone can offer some assistance here.
Related
This is a post I found after searching for my issue regarding headphones volume problems. I couldn't find anything anywhere on the XDA Forums. Please see my response at the bottom, and any help would be gratefully appreciated.
Ok so I went ahead and upgraded my mobile with the OTA update that has showing on my mobile. I wanted to upgrade ASAP due to the fact that I have run out of space for apps on the internal memory and this upgrade will resolve it (apps can be moved to the SD card).
However I think I may have jumped the gun as now whenever I use headphones the volume is stuck at max and even when the phone software says the volume is silent it’s still blasting out! Unfortunately spotify doesn’t have an internal volume control at all so it’s a no go there too.
I’ve had a search on Google and it looks like people are not experiencing the exact same issue, however there are a lot with issues with the volume in some way or another.
Hopefully this will be fixed pretty quickly as it now makes the phone unusable as a media player and I have to go back to using my iPod.
UPDATE: After searching for a resolution to this and not coming across anything much I managed to find someone saying recessed headphone jacks are quite problematic. The Desire doesn’t actually have a recessed jack but I do use a silicon case that makes the jack a bit recessed. This has not been a problem before, but I thought I’d give it a go without the case. Low and behold the volume buttons seemed to be working fine. I thought this was a bit strange so out the case back on and what’s even stranger is that is still worked fine. Now I have no idea why this happened and to me it seems a bit strange that this would even cause it in the first place (I would assume that it would be lower in volume or only one channel). Unless of course I came across a bug that has a 1 in 1,000,000 chance of hitting. Anyway I’m glad it’s working now!!
My reply:
Hi, I'm having the exact same problem after doing the froyo update. I too searched everywhere but found nothing until now. Unfortunately removing my case doesn't resolve the issue. I thought it may have been ROM related issue, but after trying several different ones the problem still exists. The strange thing is this has only started happening over the last week but I've had froyo for 4 weeks now! Can anyone out there help me ???
I had the exact same issue on the OpenDesire ROM after I flashed a file. The headphone volume was deafening every time it was on with no way to turn it down. But my issue clearly started when I flashed the DSP Manager file floating around. When I switched back to a clean ROM, the issue was no longer there.
I also experienced the issue when I moved between ROMs and updates of ROMs without full wipes. Even when I moved from stock T-Mobile to stock HTC, I experienced the issue. The resolve was simply doing a full wipe.
On HTC 2.2 I don't have this issue at all, thankfully.
-----------------------------------
- HTC Desire via XDA App -
Now you come to mention it I did the DSM Flash Zip about a week ago after flashing LeeDrOiD V2.1a, so it looks like thats the cause. Is there a quick way around this ? i.e. uninstalling the DSM flash or will I have to Full Wipe? Many thanks BTW
I've tried my best with the search tool and google. But I cant find anything regarding my problem, thus I'm asking here (I keep finding questions from people who want random ringtone apps etc)
My phone has begun to randomly change my sounds for incoming calls, notifications etc. I usually note that it happen when someone calls and all of a sudden a random sound is played instead of the one I selected.
I've investigated a bit and found out that if I change the incoming call sound then just wait a hour or so. Then when I go back into settings again another sound is shown. And no, I haven't had the phone connected to my PC or anything like that (which I understand blocks the SD card and prevent sounds from the SD to play while connected). The sound change happens no matter how I set the sounds (via settings or via Sense/Personalize).
This just started to happen out of the blue. I've tried a full wipe of the phone while on ARHD 6.1.2. The problem was still there, did another full wipe and upgraded to ARHD 6.3.1, and its still there.
Did you try another ROM then ARHD (Such as MIUI for example) to see if it's still happening?
I havent had the time yet. But I will try. Though the problem began after a few month on ARHD 6.1.2, so my first thought was that it might not be the ROMs fault. But then again I could be wrong, will try another ROM and come back with my findings.
And I just found someone else with a similar problem; http://forum.xda-developers.com/showpost.php?p=21541054&postcount=62550
I've started getting this problem on a stock ROM after the latest OTA. Very annoying...
i have been having issues with no sound coming from the LG nitro , all of a sudden it cut out yesterday and have hard reset numerous times and 1 out of 4 or 5 reboots the sound comes in but if you power off then on the sound disappears .. this is a stock phone with only root , anybody have any ideas or similiar issues ?
This is not any kind of development related topic but I'd suggest that you bring it in for repair or replacement as that sounds like a hardware issue. Maybe try flashing another rom.
Sent from my LG-P930 using XDA App
moved to general
I had a similar issue and ended up returning the phone to bell for a new one.
Here is the long story just in case it helps some one. Like all good Android users I started by rooting my phone, installing ROM Manager and making a nandroid backup. Once this was done I ran rooted stock for a few days. All was well.
Then I started to debloat my phone. After which everything seamed good. Then installed and played with RAM Manager and SD Speed Increase. TBH i did not notice any particular increase in speed on my phone but that might be due to the following issue.
After all this I decided to run a few test by using the phone into the ground. Added a bluetooth headset, while using navigation and making several calls. It was all running very well until I rebooted. Once rebooted whenever I connect my bluetooth headset I was no longer able to make calls. The phone dialer would completely lag out until I de-activated bluetooth. The the 10 or so test calls I tried making would all go through at once. This wasn't the end of the word for me so I continued to use the phone as everything else was working fine. The things started degrading by which time I was on the new CM9 nightly build. The phone had started being really sluggish. I finally decided to return my phone after it would no longer play any sound and whenever it called to any sound related function would lag out and/or reboot. The same behavior happen in stock, cm9 and NO! NO! ROMs. I tried flashing a few roms in a last ditch effort.
I could be wrong by my conclusion is that the audio portion of the snapdargon chip fried and since these phone are basically just 1 chip the phone simply degraded from there.
I would like to know of anyone else has had similar issue or if I just got a lemon and also your take on the cause of the issue.
Hope this can help someone.
Thanks!
Edit: Returned my phone for a new one and I've been flashing CM9 since the first release and no issues. I'm actually really happy with the replacement and would recommend the phone as long as you don't get a lemon ;-)
Well before deciding to root, my phone was freezing when making a call. Sometimes the system would allow a conversation, then all of a sudden I would get a ringing sound followed by frozen software, I read, researched and tried not to bug any of you. I found possible issue with the proximity and light sensor. Also read on a reputable Android website, that Sprint had follied some of the PRLs OTA. So I decided to change the possible hardware flaws and Root. Low and behold it resolved the ringing that followed the freezing, but not the freezing. Was going good with Wicked Sensation 5.0, but could not stand the constant update request. That beloved Rom eventually did the same. So changed to 5 different roms and went from TWRP to Phils recovery since then. I am currently on Static 4.3, all roms worked great until I sent/recieved a call. As soon as I hit talk phone freezes and all audio ceases to function. Sometimes itll tease me after a dalvik wipe, but always after hitting "Talk," everything regarding S3 audio or sound, stops functioning.
Does anybody know about the issue I am describing? I switched the audio components so can this Handset Issue MB related? It is hard for me to rule out software due to the audio coming back after each newly installed rom. Before its demise, Audio sounds great. The audio disappears after a call. Just concerned about going to a Sprint repair center for the wait. If this is software related it highly likely my issues will come back. Not a pro, but well versed in the rooting process. As a ExSprint employee I went through all of Sam's rooted and never been stumped on a "Hardware vs Software" problem like this. If I find out its Knox Im taking a Google Nexus to record me throwin my S3 on the wall and sending it to Samsung....jk lol. (For reals though, the increasing challenges to root for every update pisses me off cause the Samsung always got better hardware then the others, but WTF Sammy?)
Hi all,
Hoping someone brighter than me can figure this sound issue out.
THE PROBLEM:
Half of my sounds don't work, rendering my phone useless in the current state. As the title says, Ring, Notification, & Alarm sounds do not work. You know, as in the important stuff that makes your phone, a phone? And makes you wake up in the morning? None of these respective sliders under Sound & Vibration settings make any noise when making adjustments. By contrast, my Media and Call volume sliders DO make noise when adjusting. And sure enough, once on a phone call, I hear things just fine (Call). And YouTube, Spotify, et al. (Media) also work just fine.
Because some sounds work but others don't, this has to be a software issue, right? This would be easy if it was hardware and 0% of sounds worked, but nope, it's partial.
BACKGROUND:
This pixel 3 xl is relatively new to me, but has ran A10 and A11 with a few different ROMs with 100% of sound working flawlessly. But out of nowhere, sounds suddenly stopped working correctly as described above. And it didn't occur immediately or shortly after a new rom flash or update or anything like that. Just stopped working, months into a well-running ROM.
I've tried a couple different ROMs now to fix the issue from a completely clean install (/format data + flash latest google factory image as 1st step) but none have fixed the issue. Specifically, pixeldust (A11) and evolutionX (A11) were my latest troubleshooting attempts with no avail. Pixeldust was the ROM that was formerly working and then after months of 100% sounds working, suddenly stopped.
It's odd that searching throughout the ROM threads that no one else seems to be having this issue. Again, this would be easy if it was a hardware failure. But that doesn't explain how it works for Youtube/Spotify but not for other things, so it has to be software.... I think?
I figured I'd start a thread here rather than start posting in each and every ROM I've tried to troubleshoot this. Thank you!
This might not be relevant because I'm using stock Android on a Pixel 4a but my notifications have gone silent and this report was the only similar search result I found. I tried changing the notification tone and none of them played a short snippet so I'm wondering if the problem is there.
I have not found a solution for this issue.
One thing I noticed recently is that when I'm on a call using the regular "earpiece" or whatever it's called (which works fine), if I switch to speaker phone, I can't hear anything. I have to switch back to the non-speaker ear mode and I can hear the call again.
xdateddybear said:
This might not be relevant because I'm using stock Android on a Pixel 4a but my notifications have gone silent and this report was the only similar search result I found. I tried changing the notification tone and none of them played a short snippet so I'm wondering if the problem is there.
Click to expand...
Click to collapse
ManImCool said:
I have not found a solution for this issue.
One thing I noticed recently is that when I'm on a call using the regular "earpiece" or whatever it's called (which works fine), if I switch to speaker phone, I can't hear anything. I have to switch back to the non-speaker ear mode and I can hear the call again.
Click to expand...
Click to collapse
I think I may have finally found the solution!! Sometimes it's the simple things in life that work, rather than reflashing a billion different ways that finally gets things working again.
In this case, I simply cleared the cache and storage for the 'Sounds' apps under Settings -> Apps & notifications -> See all apps -> Click 3 dots in upper right corner -> Show system. Then, I deleted cache and storage for TWO apps, both called 'Sounds' with 2 different icons. I'm not sure which is the system app and which is not nor do I know if clearing only one of them was necessary, but this is what has worked for me and has survived several restarts thus far. Good luck!