I've had my Skyrocket (I727-R) for little over a year now. Bought it used. For the first seven or so months everything seemed to work fine. I had no issues and was flashing ROMs fine. Around November last year, I attempted listening to music only to realize that I couldn't hear anything from my earbuds. At first I thought it may have been my crappy old earbuds so I tried playing music without the earbuds and making a call. The other side could hear me but I could not hear anything. Since then, I've taken it back to the place I bought it from and they have been co-operative. Usually they charge for diagnostics and such but since I was a recurring customer they did it for free. Anyways, at first, it seemed like they had fixed it by replacing the speaker. They also wiped my SD, flashed the phone back to GB and told me not to root or update the software. I didn't see why it would be an issue however so I used Odin to update to stock JB and root, flashed some ROMs, etc. The audio worked for a day and stopped again while listening to music the next day. I took it back to them and they said it was a motherboard defect and would cost as much as a new phone to replace the motherboard.
I am currently running Dirty Unicorns 4.4.2, 20140331-0105, radio is T989UVMC6 (I'm on Mobilicity's network)
My question is, is there anyway I can be 100% sure it is a motherboard issue? And if it isn't, how can i fix the audio? If it is in fact the motherboard, what is the recommended course of action?
Thanks.
Related
Is/has anyone experiencing/ed issues with their AT&T HTC One X's Bluetooth A2DP capability when streaming music and/or playing any types of audio?
Mine is a new phone, and it makes a continuous crackling / jitter noise when audio is being streamed to the car's BT stereo. I have also tried this on my computer's BT headset, and it does the same thing. It sounds like the white noise you get from an old TV when you do not get a signal, only the frequency of that noise is less frequent. Using my LG Optimus S right on the side, I do not get any disruptions in my audio stream, so it doesn't seem like it is an environmental interference problem.
Unfortunately I rooted and flashed my phone to Noctural Dirty ROM before I got a chance to try anything out on the stock ROM, so I am not quite sure if this behavior is limited to the ROM (software issue) or if there is actually something wrong with the phone (hardware issue) that I should go get a replacement.
Searching through the forums I am getting mixed feedbacks (some folks are saying that they are getting replacements, while some say that the issue comes and goes).
Any thoughts on this?
Thanks!
Well, for the heck of it I flashed the stock RUU back and lo' and behold, the problem vanished. Crystal clear sound... How can this happen?
As soon as I root the device and flash to a custom ROM, this problem again resurfaces...
Perhaps I am doing this wrong?
From stock:
1) Unlock bootloader
2) Flash recovery
3) Flash boot.img
4) Wipe system, cache, davlik-cache
5) Install rom
6) Reboot
7) Install streaming app + BT pairing
This seemed to happen on all the ROMs I have tried so far - ViperXL, Noctural, CleanROM, Calkulin...
Maybe I also need to flash the radio or something?
Any ideas?
Thanks.
Does anyone have any ideas on this? I tried it on the latest CM10 and it's still having the same issues... The only thing that worked is stock... very disappointing
Sorry, it sounds like possibly hardware.
I'm on Cleanrom, and stream to my truck and use a old Jawbone for voice, both work well enough.
WR
Sent by WR's O/C'd One-XL on CR-V
I guess no one knew anything about this or has this problem.
Anyhow, I exchanged my device for another one and it seemed to have resolved the issue.
What remains curious was, why did the original phone not have any problems on stock ROMs but problems on almost all other rooted ROMs? Perhaps the Bluetooth stack was different or there was some kind of settings difference between these? Ummm...
I have the same issue with my Rogers One X.
However, it does not go away if I revert to stock with the RUU, though it does become much less intense than with AOSP ROMs.
I spoke with HTC tech support on a couple occasions and after several diagnostic steps they concluded it was a hardware problem and issued an RMA. I made it perfectly clear with them that my device's bootloader had been previously unlocked, which did not seem to be a concern since this was hardware-related.
However, after sending my device to their authorized repair center here in Canada, it was returned to me untouched with the mention "Unlocked phone - Return without repair". At the time of sending it in, the bootloader had been relocked and the device was 100% stock.
I called HTC back again, asking why they'd issue an RMA number after I mentioned upfront that I had unlocked the bootloader if the device would just be sent back to me, and they said that there was nothing they could do. They disagreed with this policy but it was that of their service provider called FutureTel here in Canada...
In short: I don't think this issue can be fixed, it is probably a defective motherboard.
I guess I am lucky that AT&T doesn't have the same policy, at least as not as I know of... heh
HTC One X bluetooth problem
I have the same issue with my One X. Bluetooth audio sets static and garbled when the phone is in my left pocket. Tried resetting phone and a replacement, but same problem. I tried several different new headsets with same results. Definitely hardware problem. ATT device support center gave me an S3 replacement, but I dont care for the interface, so I may just live with it or send it in to HTC for repair. S3 is way better hardware, but the interface kills it for me.
Hey guys,
It's Sachin here. A new member or the forum. Currently I'm running Android 4.0.4 with CleanROM 5.1 Early yesterday I was doing some tests with my guitar and I wanted to see what would happen if I plugged in my aux cable into my phone. If it would record it or not. I tried doing the same thing but plugged in my phone to laptop and wanted to see if it would pick up sound as well. Well anyways, it was either that or something else that triggered an audio problem. Now I can only hear out of my right earphone. The weird thing is, when I reboot the phone it works perfectly for a 20-30 seconds. Afterwards, the left earphone buzzes out and I'm only able to hear the right one (I have tried multiple earphones and every single one does the same thing). Moving on, I called A.T.T. and the guy walked me through a restoration of the phone (Still on CleanROM, he didn't know obviously). He said I would have to bring it in to an A.T.T. center and that they would have to look at it or replace it for me (still in the 90 day fixing period). I'm scared they won't look at my phone knowing that I do have a custom rom on there. Plus it being rooted. If someone could help me PLEASE figure out how to get to this thing unrooted and back on stock, I would appreciate it soooooo much!
Running TWRP Recovery
Too Loooong Did Not Read Version:
-Left headphone starts buzzing, tried different headphones still didn't work
-Might be a software issue as it works temporary then doesn't
-Called A.T.T. and the gave me an adress where I could go get it fixed
-Have to flash back to stock so they don't refuse service but don't know how
Thanks for taking the time to read through this thread.
Sachin192 said:
Hey guys,
It's Sachin here. A new member or the forum. Currently I'm running Android 4.0.4 with CleanROM 5.1 Early yesterday I was doing some tests with my guitar and I wanted to see what would happen if I plugged in my aux cable into my phone. If it would record it or not. I tried doing the same thing but plugged in my phone to laptop and wanted to see if it would pick up sound as well. Well anyways, it was either that or something else that triggered an audio problem. Now I can only hear out of my right earphone. The weird thing is, when I reboot the phone it works perfectly for a 20-30 seconds. Afterwards, the left earphone buzzes out and I'm only able to hear the right one (I have tried multiple earphones and every single one does the same thing). Moving on, I called A.T.T. and the guy walked me through a restoration of the phone (Still on CleanROM, he didn't know obviously). He said I would have to bring it in to an A.T.T. center and that they would have to look at it or replace it for me (still in the 90 day fixing period). I'm scared they won't look at my phone knowing that I do have a custom rom on there. Plus it being rooted. If someone could help me PLEASE figure out how to get to this thing unrooted and back on stock, I would appreciate it soooooo much!
Running TWRP Recovery
Too Loooong Did Not Read Version:
-Left headphone starts buzzing, tried different headphones still didn't work
-Might be a software issue as it works temporary then doesn't
-Called A.T.T. and the gave me an adress where I could go get it fixed
-Have to flash back to stock so they don't refuse service but don't know how
Thanks for taking the time to read through this thread.
Click to expand...
Click to collapse
Need to lock your bootloader again in fastboot then use evita rom for your phone, you might need at&t one. This process will wipe your phone including photos/videos.
They will see if they are looking that it is relocked in fastboot.
Good luck
So I rooted my Skyrocket last week and I screwed something up and since than I've had problems with the audio on the phone part. So I'm running Odin and even after double and triple checking I managed to screw it up by not having Auto Reboot checked. In a panic (and after waiting a long time) I unplugged the phone and powered it down. I booted into Recovery and did a wipe and installed CM 10.1.2 and I swear it worked fine for a week but all of a sudden I started having this weird issue with the phone audio. I'll call a number up and I won't be able to hear anything but I can put it on Speaker and it comes through fine or if I use my Bluetooth Headset it works fine.
I reloaded CM 10.1.2 and still nothing. I tried a nightly, I tried 10.1, I tried Beanstalk, and I now I'm back to stock and no luck on the phone audio. I have no idea what to do. I've tried Google searching and I'm coming up with a bunch of things but not what I'm looking for. I've even found some people having similar problems but they got no answer as well and I'm waiting to hear back from them (I found at least three people reporting the problem over on Cyanogenmod's Skyrocket Forum). I found some reference to it possibly being a Kernel problem. Thoughts?? I'll do some reading up on that tonight.
As a last resort I'm looking into buying a used Skyrocket to replace this one because I'm still 6 or 7 months till I'm eligible for an upgrade. HELP!
Edit, sounds like a hardware problem.
Have you tried to odin back to stock?
jd1639 said:
Edit, sounds like a hardware problem.
Have you tried to odin back to stock?
Click to expand...
Click to collapse
Well I wondered about the hardware problem myself but it was working fine before I flashed everything and was working fine for a while afterwards. But I do have an issue with hardware. A few months ago I ran over the tip of my headphones at work with my chair and broke it off. Without thinking about it I put the tip back and reinserted it back on the phone again. I immediately realized what I had done and when I pulled the headphone jack out the tip remained inside the phone. I'm pretty sure it's caused some odd issues with my phone when trying to play audio using the speaker as sometimes it would play and other times I would hear anything unless I played it through Bluetooth. I took the phone apart thinking I could get to the tip that's inserted in there but it really can't be reached.
With the new phone audio problem I didn't think it was related because it was working fine before and for a little while afterwards. Plus I've seen other people post on the Cyanogenmod Forum about having the same problem so I'm not sure.
So no thoughts on it being a Kernel issue or some other software problem?
jd1639 said:
Edit, sounds like a hardware problem.
Have you tried to odin back to stock?
Click to expand...
Click to collapse
Oh and yes I've tried back to stock with no luck.
dfwjose said:
Oh and yes I've tried back to stock with no luck.
Click to expand...
Click to collapse
Seems like you have your answer then. If the problem persists regardless of which ROM or kernel you're using then logically it would seem that it can't really be software related, right?
Brought to you but time and relative dimensions in space.
dfwjose said:
Well I wondered about the hardware problem myself but it was working fine before I flashed everything and was working fine for a while afterwards. But I do have an issue with hardware. A few months ago I ran over the tip of my headphones at work with my chair and broke it off. Without thinking about it I put the tip back and reinserted it back on the phone again. I immediately realized what I had done and when I pulled the headphone jack out the tip remained inside the phone. I'm pretty sure it's caused some odd issues with my phone when trying to play audio using the speaker as sometimes it would play and other times I would hear anything unless I played it through Bluetooth. I took the phone apart thinking I could get to the tip that's inserted in there but it really can't be reached.
With the new phone audio problem I didn't think it was related because it was working fine before and for a little while afterwards. Plus I've seen other people post on the Cyanogenmod Forum about having the same problem so I'm not sure.
So no thoughts on it being a Kernel issue or some other software problem?
Click to expand...
Click to collapse
You have to get the piece out dude. It's making contact intermittently and killing the audio.
Sent from my HTC One using Tapatalk 4
And just like that I'm up and running again and my phone works. I had given up and was having problems with a CM nightly so I did another wipe and loaded a stockish AT&T ROM that I've installed before and no my phone is working fine. I'm going to leave this thing alone until I pick up a spare phone!!
xcrazydx said:
You have to get the piece out dude. It's making contact intermittently and killing the audio.
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
I'm sure it is and that's why I took the phone apart to see if I could get to it. I tried all kinds of things to get that tip out before tearing the phone down and I had no luck. I should have taken some pictures but I've tried tweezers (everything I had was to big or to weak to pull it out) and even glue before resorting to taking the phone apart. Unfortunately with the design it's enclosed all the way around with no way to really get to it. I even thought about replacing it but that piece looks to be soldered on.
In the end, I might just send it back to Samsung and see if they will fix it. Not sure if it's worth it but I never got serious about it because I didn't have a spare smart phone other than my work iPhone.
I shouldn't have spoken so soon. Rebooted the phone and it's locking up now. I give up. I can't find anything that will work. I either have sound with a phone that locks up or have to live with Speakerphone/Bluetooth and be able to reboot.
My wife's Galaxy S6 has developed a problem where the earpiece speaker on the phone is pretty much unusable. She said it started sometime after the last system update. Software issue or do I need to check into a repair/replace. Phone's only a few months old. Got it just after Mother's Day.
Might have something to do with advanced calling. Make an hour long call to verizon for testing. Or just try turning it off all together and try.
Did a full factory reset...no joy. Sent in under manufacturer's warranty. Mods Can delete thread.
I so I'm not really sure what the deal is but I've used viper for Android on all of my devices it worked great on all of them all so I installed it on this Moto G7 power retail us version the the - 5 xt1955-5 but for some reason after using a viper on there for about a week now my speaker sound like crap complete garbage I installed all the extra mods through matches cuz well to make it work with Spotify and YouTube and all that and I found it doesn't matter if I have Ivory installed it I've uninstalled it Ivory flash back to stock nothing works the same thing happened with the last one I actually return the last one and then relock the bootloader and they sent me a brand new phone so I don't know what's going on but I think these phones have a faulty speakers in them and I think Motorola may be ignoring that so I just want to give people a fair warning I would probably not use viper on this device unless you're looking to have a blown speaker I can barely even hear phone calls now it's that bad I'm probably going to have to try to RMA this one also for the same reason what sucks but anyway definitely definitely seems to be no fix for that I can find if anybody has any ideas of something I could try let me know and I'll give it a shot otherwise I'm just going to have to send this one back and try to get another new one it only took a few days cuz I'm in Arkansas and they came from it comes from Texas but I believe they have faulty speakers. Also I didn't have my boost like maxed out although in other devices I boosted it all the way and it didn't affect it at all I mean the speaker doesn't sound blown like it's not a blown sound is just very low so if anybody's got an idea of what I could do to maybe fix it would be awesome.otherwise I'll just send it back for another one but I'm going to wait and see if I get any answers or ideas first for a few days and then if if I don't hear anything then I'm sitting in the sucker back to along with a note that I'm pissed off and that they're they need to just upgrade me to the plus or something.
Also I'm on stock latest build with February security patch.
toxinburn said:
Also I'm on stock latest build with February security patch.
Click to expand...
Click to collapse
You might have blown out your speakers. It's not that hard to do. They're tiny and can't handle as much as Viper can throw at them. As a general rule, if you hear any sort of drops or crackles, you're pushing the hardware way to far.
It's entirely possible that Viper or another audio mod you installed borked your sound configs. Viper was bugged about a week or so ago, and it literally just got fixed, so it might be worth it to try installing the latest again. I was having the same issue for about a week or 2. I use zackptg's builds. (Current version is 2.7.1.6) Barring that, I'd try reflashing stock. If none of that works, I'd say your speaker is blown.