[Q] HTC One Sound Gone - Verizon HTC One (M7)

Hey Everyone! I was running CM11 and I noticed my sound wasnt working on speaker or through headphones. Bluetooth still working fine though. So I restored a backup of my original sense rom and that didnt help. I really need it work for my alarm clock in the morning if nothing else. Any ideas? I'm thinking it might be time to go back to stock and do a warranty exchange. Any help is greatly appreciated.

Might have to do an ruu. Seems like people are having different issues with cm11.
Sent from my Nexus 7 using Tapatalk 4

When I'm running some cm11 Roms I'll loose sound in my lower speaker. I just flash back to a sense or gpe rom and the sound is back. Never lost sound altogether though.
Sent from my HTC One using xda app-developers app

push

Dark Jedi said:
Might have to do an ruu. Seems like people are having different issues with cm11.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
I did that, didn't fix my issue.
jax187 said:
When I'm running some cm11 Roms I'll loose sound in my lower speaker. I just flash back to a sense or gpe rom and the sound is back. Never lost sound altogether though.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
It was weird, ended up going back to stock and doing a warranty exchange.

Related

Camera Glitch?

My friend has a Droid Incredible 2, when she launches the camera app she gets multiple colors on the screen. Same result on Sense 3.6 leak and UKB Evolution Sense 4 ROM. Pictures come out just fine and even screenshots, it's just when shes trying to see what shes taking a picture of. Any help would be greatly appreciated,
First question would be what is her root method? Second, has she tried a stock Rom like bonestock?
Sent from my ViperDinc
brymaster5000 said:
First question would be what is her root method? Second, has she tried a stock Rom like bonestock?
Sent from my ViperDinc
Click to expand...
Click to collapse
She used the HTC Unlock method, and the Sense 3.6 was a Bonestock ROM I believe
Airo18 said:
She used the HTC Unlock method, and the Sense 3.6 was a Bonestock ROM I believe
Click to expand...
Click to collapse
Did she pull out the boot.img before flashing? Htc unlock has its hiccups and things can't be flashed the same.
Sent from my ViperDinc
brymaster5000 said:
Did she pull out the boot.img before flashing? Htc unlock has its hiccups and things can't be flashed the same.
Sent from my ViperDinc
Click to expand...
Click to collapse
Yep, I helped her flash everything so I know it was done right, but with both ROMs is what I don't get. Could it be a hardware issue?
Yeah, maybe the ROM or root isn't sitting right. Have you tried wiping the cache(s) or re-installing/downloading the ROM's? If those aren't the case then try and OEM lock the phone and re-root it again. If that doesn't work, then the camera might be funky.
Gonna see if that works, hopefully it does haha
Sent from my Nexus 7 using xda premium
Airo18 said:
She used the HTC Unlock method, and the Sense 3.6 was a Bonestock ROM I believe
Click to expand...
Click to collapse
A 3.6 ROM isn't going to be stock.
Have her try Nitsuj's StockM ROM.
Sent from my vivow using xda app-developers app
Quick update:
"Can you let them know that all of the stock videos came colored too, and when i play a youtube video, the entire app turns colored like the cam"
Sent from my Galaxy Nexus using xda premium
Airo18 said:
Quick update:
"Can you let them know that all of the stock videos came colored too, and when i play a youtube video, the entire app turns colored like the cam"
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Is there a settings that is on that is causing this? If not it could be a hardware issue.
I think one way of telling for sure is to get rid of the HTC unlock and fully root to see if it has to do with how the phone is handling the flashing of the ROM's. If it still occurs, then I would guess hardware.
I'm gonna see if running the RUU will the problem. That way I know if its a hardware issue or software
Sent from my Galaxy Nexus using xda premium

[Q] No sensors working after reboot.

Hi, Im currently on the stock JB with a CID 001. My problem is that once I flash a rom none of my sensors work, after a few times holding the power button for a reboot they will start to work again. Im able to calibrate the G sensor in settings while they work but if I turn off my phone they will stop working.
This started happening after I updated to JB, I have tried using ARHD and Maximus with no difference. Each time I flash a rom they work but after they phone turns off they stop working, not just a few its all of them.
Any suiggestions please?
Just in the middle of updating my hboot to 1.39 so hopefully this helps
EDIT: after re flashing with maXimus 11 and hboot 1.39 the sensors didn't work. I restarted the phone holding the power button but that didn't help, done it again only holding the up button when the htc screen appearing when rebooting.
Any suggestions would be greatly appreciated. Thanks
Also im going to install the two OTA updates here and see if the sensors will still work after these.
Installed the first update and the sensors stopped working and then installed the second and they started working again. I think once I turn off the phone I won't be able to get them to work again. Sorry about all the posts but I'm trying to give as much information as possible.
Sent from my HTC One X using xda app-developers app
My phone ran out of battery there for the first time since I flashed the rom so was the first time the phone has been rebooted since the updates. Now the sensors have stopped working again. I have tried rebooting several times, Killing all tasks using the task manager then rebooting but nothing. The only way to get them going again is to re flash the rom. Any help please?
Sent from my HTC One X using xda app-developers app
Any help at all? I haven't had any sensors since the last update which is pretty annoying. Thanks
Sent from my HTC One X using xda app-developers app
Karl. said:
Any help at all? I haven't had any sensors since the last update which is pretty annoying. Thanks
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
I lost my gyro/compass/orientation at one point a few months ago... I tried several full wipes and different ROMs, nothing changed. However, what did fix 'em was when I relocked and flashed a stock O2 RUU to return it via my operator. Its been fine since.
So your saying the only thing to do is to send the phone back to O2 for a replacement? I opened my phone so I take it that's my warranty void anyways? But suppose I could always try. Thanks, also just compared my loud speaker to my brother phone and mine is awful compared to his
Sent from my HTC One X using xda app-developers app
So after booting the phone into recovery and wiping the two caches and fixing permissions I was able to get the proximity sensor working after two reboots but after another it stopped working again. Any idea's?
Sent from my HTC One X using xda app-developers app
Karl. said:
So your saying the only thing to do is to send the phone back to O2 for a replacement? I opened my phone so I take it that's my warranty void anyways? But suppose I could always try. Thanks, also just compared my loud speaker to my brother phone and mine is awful compared to his
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
No, sorry - I didn't send it back to O2, I flashed the RUU with the intent of doing so and that's what fixed it! Sorry for being confusing!
System problem,don't mention that.Flash another rom .That will be fixed.
JohnYang1997 said:
System problem,don't mention that.Flash another rom .That will be fixed.
Click to expand...
Click to collapse
I have already tried the European standard ruu along with maximus and arhd so unless I try the branded O2 stock rom. I will do this tomorrow. Thanks
Sent from my HTC One X using xda app-developers app
Has any body any more ideas? This is getting very annoying. Thanks
Sent from my HTC One X using xda app-developers app
If flashing an actual o2 RUU didn't work (I was a bit confused by your previous posts as you can't flash an unbranded RUU on a branded handset...) If that didn't work then its a hardware fault. Or at least a software fault that can't be fixed without the software they use in an hTC service centre.
My phone isn't branded but I got it of O2. I might just re lock it and send it back as I don't seem to be getting anywhere with this. Thanks for all your help but.
Sent from my HTC One X using xda app-developers app
So after I rebooted my phone tonight all my sensors have started to work. I don't know what's happening here at all and I don't want to reboot or let my battery die incase they stop working again. I also noticed compared to my brothers one x his screen is alot brighter than mine?
Sent from my HTC One X using xda app-developers app
So I flashed the stock RUU and sent it away for repair and they just sent it back saying there was physical damage, Im assuming this is just that I have opened the phone. So there still isnt any sensors working, any ideas please?
I am experiencing the same problem with the sensors... still didnt find a permanent solution. I rebooted like 100 times, eventually they worked, then after a reboot they didnt.
I came across this topic, maybe it will help
http://forum.xda-developers.com/showthread.php?t=2420209

Problem with notification sound

I don't know why this started but it is very annoying. My speaker works because I played music while my phone didn't make any noise and it worked.
But when pressing the volume keys, the little "boop" doesn't sound and when I restart the phone, the animation and sound turning off doesn't sound but the boot animation sound works and everything is normal, at least for awhile anyway.
Basically its like all software sounds just don't work except playing music thru the speaker.
Is there any way to fix this?
Oh I'm all stock, no flashing or ROMs, anything.
Sent from my LG-LS970 using xda app-developers app
I'm seeing this as well. Seems to happen on any kernel I try, and only since the JB update. BTW, I am using stock JB rom, rooted/unlocked.
roach7676 said:
I'm seeing this as well. Seems to happen on any kernel I try, and only since the JB update. BTW, I am using stock JB rom, rooted/unlocked.
Click to expand...
Click to collapse
Yea I'm on JB. But it started awhile ago. Like 3 days.
Sent from my LG-LS970 using xda app-developers app
Bump.
No one as any solution? Besides getting my phone diagnosed at Sprint (which I don't wanna do)
Sent from my LG-LS970 using xda app-developers app

[Q] Inline Mic no longer works [CM 10.1]

Is anyone having a problem with an inline mic not working at all on their GSIII?
Ever since approx CM 10.1 beta 4 the mic on a couple pairs of headphone no longer works. The mic no longer receives sound during calls and pushing the single button has no effect in music players like it used to. Headphone ear buds still play sound just fine.
I updated to the most recent nightly and problem still persists.
I'm just not 100% sure it its a problem with the ROM or if coincidentally for some reason my headphone jack has failed and is no longer receiving mic signals.
Anyone else having this problem or know a fix for it?
Odin back to stock and test. Then you will have your answer.
Sent from my SGH-T999 using xda premium
I doubt it is CM.
Sent from my SAMSUNG-SGH-T999 using xda premium
I've had lots of random issues in the past where Poweramp wouldn't respond to the buttons on the earbuds (never used one with a mic). Would work fine for a while, then stop. Poweramp is almost never updated. So that has to be a CM problem.
Also, Tasker was no longer reading my notifications to me while my earbuds where plugged in. Worked fine for months on every nightly up to a certain point. No longer works. I think headset plugged isn't being registered within the OS anymore.
My money is on CM bug.
Weird definitely. I figured there being no talk of it it wasn't an issue, only person to ask this lol... Hopefully it is a bug within cm only though. Someone pull system/usr/keychars|key layout/general file and compare them, I fixed this issue with LiquidSmooth 2.2 release which in turn fixed Carbon's exact issue. Maybe they changed something and/broke something.
Sent from my SAMSUNG-SGH-T999 using xda premium
DocHoliday77 said:
Odin back to stock and test. Then you will have your answer.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
yea I thought about that but I didn't particularly want to go through that trouble if it was already a confirmed CM bug that other people were having.
CoBfan1987 said:
yea I thought about that but I didn't particularly want to go through that trouble if it was already a confirmed CM bug that other people were having.
Click to expand...
Click to collapse
Like mt3g its the first I've ever heard about it. Just nandroid backup. Odin root 66. Test. Restore nandroid.
At least for me its not too much to do to be certain. Your call though, of course.
Sent from my SGH-T999 using xda premium
I have actually noticed this myself. Inline mic doesn't work at all, buttons do nothing... But I can hear fine. Also, beyond pod dropped one channel so sound only happens in one side.
Sent from my SGH-T999 using xda premium
No one try my fix yet?
Sent from my SAMSUNG-SGH-T999 using xda premium
mt3g said:
No one try my fix yet?
Sent from my SAMSUNG-SGH-T999 using xda premium
Click to expand...
Click to collapse
You mean comparing the two files?
What am I look for a difference in?
Yes compare the "general" in system/usr/keylayout & keychars... I just put them side by side in notepad and scroll and check to see I'd they're different in any way at all. Better yet you can just push them, remove the current ones and replace them with new ones and then reboot.... That's how I fixed the issue with Liquid a while back surprisingly lol.
Sent from my SAMSUNG-SGH-T999 using xda premium
mt3g said:
Yes compare the "general" in system/usr/keylayout & keychars... I just put them side by side in notepad and scroll and check to see I'd they're different in any way at all. Better yet you can just push them, remove the current ones and replace them with new ones and then reboot.... That's how I fixed the issue with Liquid a while back surprisingly lol.
Sent from my SAMSUNG-SGH-T999 using xda premium
Click to expand...
Click to collapse
Well I'm flashing stock root66 right now so we'll see if the problem persists there or not first. If not then I'll load CM back in and see what happens and try your idea out.
Cool beans hombre
Sent from my SAMSUNG-SGH-T999 using xda premium
Really looking forward to hearing how this works... If I had more time these days, I'd have a look at the commit history, but the wife and kids are making more demands on my time than I can handle and still have as many hobbies as I'd like. This thread is subscribed, though. Thanks everyone for having more free time than I do.
Sent from my SGH-T999 using xda premium
Well the news is in.
Running stock Touchwiz rom the inline mic worked perfectly with calls and controlling music.
But back on CM 10.1 latest nightly and it no longer works again.
on a side note I'm pretty pissed. Some how between the odin flashing of stock and cwm flash of CM 10.1 half the **** on my sd card including my titaniumbackups and my nandroid backs up are no where to be found. My music and several other old app folders are still on the card but not the actual important stuff I needed to restore. Whats weird is my SD card still shows the same amount of data on the card but I can't find any of it anywhere.
Always keep a backup of internal stuff, people complain too much for their own mistakes.
Sent from 'Murica
mt3g said:
Always keep a backup of internal stuff, people complain too much for their own mistakes.
Sent from 'Murica
Click to expand...
Click to collapse
I thought it was all backed up. Anyways I'm not complaining about that, is my issue and I'll live with it.
But this obviously shows that it is a CM bug right?
Yup
Sent from 'Murica
Yes, it seems to be a cm bug.
Look at the sdcard from recovery. Ill bet everything is still there, but is subject to the /0/0/0 file structure issues tons of people have.
Sent from my SGH-T999 using xda premium
If not there mnt/shell click in all of them and if found move outside the /0 folder or in some other spot you're comfortable with...
Sent from my SGH-T999 using xda premium

Annoying audio issues with 4.3 ROMs

The problem I'm having with every 4.3 ROM I've tried is that when I switch back to sound from vibrate, my notification sounds, ringtones, and alarms don't work. Only thing that fixes it is a reboot, but after toggling from sound to vibrate, then back to sound, it starts again. Any help? Thoughts? Ideas?
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
90+ views, and judging by the huge number of responses, I'm going to guess I'm the ONLY one with this issue on 4.3 ROMs. Really?
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
mbrian27 said:
90+ views, and judging by the huge number of responses, I'm going to guess I'm the ONLY one with this issue on 4.3 ROMs. Really?
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hasn't happened to me on any 4.3 ROM that I've flashed...
mbrian27 said:
The problem I'm having with every 4.3 ROM I've tried is that when I switch back to sound from vibrate, my notification sounds, ringtones, and alarms don't work. Only thing that fixes it is a reboot, but after toggling from sound to vibrate, then back to sound, it starts again. Any help? Thoughts? Ideas?
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm having this issue on my GF's GS3, not sure what to do about it either. She was on 10.1 and all was fine, wnt to the latest nightlies last weekend and been having this issue ever since. grr
chillware said:
I'm having this issue on my GF's GS3, not sure what to do about it either. She was on 10.1 and all was fine, wnt to the latest nightlies last weekend and been having this issue ever since. grr
Click to expand...
Click to collapse
If you dirty flashed CM 10.2 on top of CM 10.1. that could be what's causing the errors. It's alway recommended to clean flash whenever there's a .1 Android update.
drx895 said:
If you dirty flashed CM 10.2 on top of CM 10.1. that could be what's causing the errors. It's alway recommended to clean flash whenever there's a .1 Android update.
Click to expand...
Click to collapse
One of the first things I did when I started noticing problems was reflashed, so that wouldn't be the issue.. I have V4A installed, and thought maybe it was causing problems so I didn't install it when I reflashed, but that didn't help either. I'm puzzled.
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
drx895 said:
If you dirty flashed CM 10.2 on top of CM 10.1. that could be what's causing the errors. It's alway recommended to clean flash whenever there's a .1 Android update.
Click to expand...
Click to collapse
Was clean, even tried it a second time with another full clean wipe.
mbrian27 said:
One of the first things I did when I started noticing problems was reflashed, so that wouldn't be the issue.. I have V4A installed, and thought maybe it was causing problems so I didn't install it when I reflashed, but that didn't help either. I'm puzzled.
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
chillware said:
Was clean, even tried it a second time with another full clean wipe.
Click to expand...
Click to collapse
Hmm, then I'm clueless. Has anyone tried re-flashing stock through Odin?
Did that about a week ago, or else I would try
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app

Categories

Resources