DEAD wifi chip (DOA) on K1? - Shield Tablet Q&A, Help & Troubleshooting

I literally bought this less than 2hrs ago and the first thing that happened was no wifi showing or it working for that matter. Did a factory reset but to no avail. BT/tethering works at least so I could download some stuff. But other than that no other issues whatsoever. No updates avail either...
Now, whenever I press wifi it hangs and settings goes black and hangs. Kinda hard to log when it's not even working.. I've thought about rooting and going CM but hey, might as well just return it for a new one tomorrow.
Either my file system is corrupt, i.e file/driver corruption or the wifi chip is borked, though BT works which leaves me pondering.
PS: the stylus is awesome!

"PS: the stylus is awesome!"
The "new" model k1 cames without stylus.

You don't say?! And the moon really is made of cheese? Doesn't leave the fact that I bought the stylus separetly or not but I guess that doesn't exist in your world where sheep roam.

before you root it try doing a hard reset and see if wifi works. Could be a corrupt file it happens. I always hard reset a new device force of habit from my Windows Mobile days.
Sent from my SHIELD Tablet using Tapatalk

PixelVixen said:
I literally bought this less than 2hrs ago and the first thing that happened was no wifi showing or it working for that matter. Did a factory reset but to no avail. BT/tethering works at least so I could download some stuff. But other than that no other issues whatsoever. No updates avail either...
Now, whenever I press wifi it hangs and settings goes black and hangs. Kinda hard to log when it's not even working.. I've thought about rooting and going CM but hey, might as well just return it for a new one tomorrow.
Either my file system is corrupt, i.e file/driver corruption or the wifi chip is borked, though BT works which leaves me pondering.
PS: the stylus is awesome!
Click to expand...
Click to collapse
Just return it. No reason not to have one that works out of the box. It likely isn't something that would be easy to deal with.

I got my K1 back today all working. According to the guy on webhallen (where I bought it) it had a corrupt FW and needed to be reflashed, so I'm glad the RMA was solved in less than 48h!
Now I just wish I had these files as well since I hear K1 differs a bit compared to 1st gen.
Oh well ¯\_(ツ)_/¯

PixelVixen said:
I got my K1 back today all working. According to the guy on webhallen (where I bought it) it had a corrupt FW and needed to be reflashed, so I'm glad the RMA was solved in less than 48h!
Now I just wish I had these files as well since I hear K1 differs a bit compared to 1st gen.
Oh well ¯\_(ツ)_/¯
Click to expand...
Click to collapse
Only difference seems to be the stylus. Doesn't have the spot to hold it or sensor to tell if it was removed. Other than that it looks like it's just cosmetic differences.

Related

Questions

So I got my XT720 a few days ago and am loving it. Two things though:
1) I've had to do a quick reset (take out battery) about 4-5 times in the same amount of days. What happens is sometimes the screen will go blank (or when I press the on button all that will happen is the 4 buttons at bottom of phone will light up). Screen/phone becomes unresponsive and only way to get back to normal is to take out battery. I'm pretty sure that every time this has happened has been right (or shortly) after me downloading something on my phone (i.e. putting on a new wallpaper, or a song). Anyone have this happen to them?
2) I don't want to root or put on Dexter's ROM just yet. The reason for this is because a) I just got my phone and I don't want to void the warranty until I know everything works with no issues b) I'd rather wait for the complete/fully polished version of the ROM - I'm in no hurry right now, this phone is a big big upgrade from my previous phone even without 2.2.
Anyways, the point is, I'm pretty sure my phone isn't running with the 720MHz update right now and is running at 550. I want to put on that update to make my phone faster while I wait to root. However, whenever I go to - about phone - check for system updates - and click on that, it always tells me "Server unavailable. Try again later.". Been trying for the past few days and no luck. How can I get the 720MHz update (without rooting - at this point)?
Thanks
If the screen doesn't come on when you turn on the phone, you may have a defective one. My first XT720 was a dud right out of the box. I had to take it back to the Cincinnati Bell store and get it exchanged. I've heard of other people having similar experiences with the phone not turning on. Take it back. If they give you any crap about it, just tell them that the Motorola tech from their forums told you to take it back. This adds a bit of validity to the problem and may make it an easier transaction.
Nah, it works fine for the most part. Turns on and off and runs just fine normally. But my issue is I've just had it basically freeze up 4-5 times in the past week (noticing a possible connection to me downloading things).
I would think your phone is running at 720mhz. I believe the European / Asian versions were originally 550mhz & had an ota udate to the 720 level. You could download Android System Info or Elixer to check it out though.
I would also agree with reverendkjr, it the phone is acting funky take it back & get a replacement.
The XT720 from Wind is 720mhz with stock firmware, the only 550mhz was Korean version AFAIK, maybe some Euro versions.
As for the screen, you may want to try doing a factory reset on your phone. If it persists after that take it back to Wind for a replacement, had my wife's XT720 replaced due to a microphone problem.
R-D said:
The XT720 from Wind is 720mhz with stock firmware, the only 550mhz was Korean version AFAIK, maybe some Euro versions.
Click to expand...
Click to collapse
Oh? I figured it might be at 550 since going back to homescreen - it reloads pretty often (thought 720 wouldn't do that), though it does run snappy enough in all other areas.
As for the screen, you may want to try doing a factory reset on your phone. If it persists after that take it back to Wind for a replacement, had my wife's XT720 replaced due to a microphone problem.
Click to expand...
Click to collapse
Be a bit of a pain to factory reset at this point. The problem isn't terribly disruptive at this point. Doesn't happen often enough to really bother me and restarting is quick. If it does continue and become frustrating I may consider factory reset. I just was wondering if anyone else experienced this.
WIND would give me a replacement at any time (within the year) if I told them about this issue? (Kind of hard to prove since it happens at it's own whim. Don't want to seek a replacement just yet anyways - not unless it continues and is an annoyance)
Just put a call into support so they have a record of the problems, explain to them you cant reproduce the problem, but it is a brand new phone and should not be doing this regardless.
They will suggest the reset to see if the issue persists, but you can decline at this time and at least get the issue logged so you have a better chance of replacement in the future.
Keep in mind though, within 14 days they will replace with a new phone, beyond that you may get a used one.
I can't imagine just ignoring a problem with a new phone like that. Especially since you have the ability to have it replaced for free.
Heck, I took a phone back once because it had ONE dead pixel on the screen. When the girl looked at me and said "Really?" I said "Hell yes, I just bought this damn thing and I want it to be PERFECT!"
you need to setup the APN to connect to 3G to get your 720 upgrade from OTA (if purchased unlocked Euro or Asia models)
if it's a Wind XT720 it should already be on 720
reverendkjr said:
I can't imagine just ignoring a problem with a new phone like that. Especially since you have the ability to have it replaced for free.
Heck, I took a phone back once because it had ONE dead pixel on the screen. When the girl looked at me and said "Really?" I said "Hell yes, I just bought this damn thing and I want it to be PERFECT!"
Click to expand...
Click to collapse
Yeah, I suppose that's true. If it happens again I'll look into getting it replaced.
Thanks for the help guys.
my XT711 has done the "blank screen a few times also and I have to remove the battery to reset it. Very strange thing, but I have had the phone for only a few days so im gonna see what its gonna do first cause sending it back to china is a pain in th butt.

More Transfomer Touch Screen issues...

Just got my new TF700. Major, major touchscreen issues. But these are weird... At first it looked very much like hardware fault but the more I try and use it the more I think its software.
First off, the left hand side not as good as the right hand side. Its first turn on was not usable and its been getting little better as the hours go by. 2 days in now. Done the normal re format, drain battery and also got it warmed right up with a good turn off also. ( Elec Blanket worked great for this controlled warmup ) Nothing has made a direct impact as some others have claimed on the whole Transformer range.
Ive had to take a video of what's happening. I've turned the developer options on to indicate when the digitizer detects the touch and also the indicator when the system responses to this touch. There is clearly a delay in when the system reacts to my touch. But sadly not as clean cut as this as sometimes the digilazer doesn't even sense my touch. Notice the left hand side not as good but still does work sometimes.
http://youtu.be/aslnYafGLf0
To me there is clearly a software issue with this delay. The system response times vary's heaps especially with 10 point touches. But at other moments its not detecting my finger at all... Ive read a lot of TF101 firmware upgades have created touches not to get detected also. Still software going on here ?
My issues with Asus and repair .... I brought this from USA and brought it to New Zealand over night. Big risk yes but it does have the Asus international warranty. 2 days after the invoice date NZ has to say it can be a repair only. I understand NZ doesnt have this yet but this is a huge kick for me as the turn around time is 5 to 8 weeks to repair my 2 day old product. They will import a new screen in but not DOA on receipt date. That hurts Asus but what if its your firmware ? Could it be fixed by the firmware first ? Its nice having a RMA number already as the NZ guys are great but I dont want to be their first TF700 to pull apart as it will never be the same.
I dont feel I can root it to test it some more as they might run away from warranty. Im stuck.... My first Asus product not been a motherboard and not happy with the evidence in front of me guys, please help me out.
Holy crap, that is ridiculous! Dunno what it might be, but I would try PM-ing that vid link to one of the Asus guys on XDA.
Kezzainc said:
Just got my new TF700. Major, major touchscreen issues. But these are weird... At first it looked very much like hardware fault but the more I try and use it the more I think its software.
First off, the left hand side not as good as the right hand side. Its first turn on was not usable and its been getting little better as the hours go by. 2 days in now. Done the normal re format, drain battery and also got it warmed right up with a good turn off also. ( Elec Blanket worked great for this controlled warmup ) Nothing has made a direct impact as some others have claimed on the whole Transformer range.
Ive had to take a video of what's happening. I've turned the developer options on to indicate when the digitizer detects the touch and also the indicator when the system responses to this touch. There is clearly a delay in when the system reacts to my touch. But sadly not as clean cut as this as sometimes the digilazer doesn't even sense my touch. Notice the left hand side not as good but still does work sometimes.
http://youtu.be/aslnYafGLf0
To me there is clearly a software issue with this delay. The system response times vary's heaps especially with 10 point touches. But at other moments its not detecting my finger at all... Ive read a lot of TF101 firmware upgades have created touches not to get detected also. Still software going on here ?
My issues with Asus and repair .... I brought this from USA and brought it to New Zealand over night. Big risk yes but it does have the Asus international warranty. 2 days after the invoice date NZ has to say it can be a repair only. I understand NZ doesnt have this yet but this is a huge kick for me as the turn around time is 5 to 8 weeks to repair my 2 day old product. They will import a new screen in but not DOA on receipt date. That hurts Asus but what if its your firmware ? Could it be fixed by the firmware first ? Its nice having a RMA number already as the NZ guys are great but I dont want to be their first TF700 to pull apart as it will never be the same.
I dont feel I can root it to test it some more as they might run away from warranty. Im stuck.... My first Asus product not been a motherboard and not happy with the evidence in front of me guys, please help me out.
Click to expand...
Click to collapse
The touch indicator has always been laggy. In actual usage, touches register pretty well.
Sent from my FHD porn machine.
jdeoxys said:
The touch indicator has always been laggy. In actual usage, touches register pretty well.
Sent from my FHD porn machine.
Click to expand...
Click to collapse
At times its not laggy at all on this tablet. Cheers,
Kezzainc said:
At times its not laggy at all on this tablet. Cheers,
Click to expand...
Click to collapse
What? I thought it was always laggy. (By touch indicator I mean the line drawing thing you enable in dev settings)
This sounds as nothing a good custom ROM shouldn't be able to fix. (Unlocked bootloader has been released today! )
My HTC One X 4.1.1 never has any lag at all. Asus TF300 has a little but not inconsistent like this. The very edge of the screen is the hardest to even work and pushing to maximise finger area helps. But its the not even seeing touches and a long swipes does not work as it cant stay locked on.... Pinch to zoom very crazy because of this.
But its looking like I am the only one which is saying hardware ?
**** Update : Wow this is a huge epic fail from Asus. My patience is fully coming to an end. Asus have not done a single thing for me on this fault that makes it unusable.
I have a software issue. Its very clear it is now. Lastnight I did another hardreset to try and get this .26 update. For the first time ever it worked, 100% worked on its first boot up. I had a really really happy half hour with it and man it felt good knowing I didnt buy the most expecince tablet dud on the market. But, I did a standby power once and Boom, back to its crap unusable old ways.
So 100% working after reset then one power down resets it to its old ways. When it did work for that 30mins its was 100% working.
Gary and Tien from Asus. These guys have both repied to me. They are not the big Asus people at all, they are just USA Asus. They havnt even done anything for me at all. A huge let down as they make themselves sound like they can help. My unit is a USA unit. They have not asked me to do any tests, offer me a test firmware or even a better video. Or ask what hardware versions I have, simple nothing and taking the piss of what they are offering to this advance community here. Not even an email saying the new update is coming out that may help.
The really bad part about this is its quite clear that the .26 update talks about upgrading the touch FW. Tien emailed me this morning saying they cant even give me a copy of this public released FW for me to fix my problems.
EPIC EPIC FAIL FROM ASUS.
What should I do everyone as im starting to think about getting on a hill a shouting this out to more than just this forum.
( first 'bad' forum post in my life like this )
Kezzainc said:
**** Update : Wow this is a huge epic fail from Asus. My patience is fully coming to an end. Asus have not done a single thing for me on this fault that makes it unusable.
I have a software issue. Its very clear it is now. Lastnight I did another hardreset to try and get this .26 update. For the first time ever it worked, 100% worked on its first boot up. I had a really really happy half hour with it and man it felt good knowing I didnt buy the most expecince tablet dud on the market. But, I did a standby power once and Boom, back to its crap unusable old ways.
So 100% working after reset then one power down resets it to its old ways. When it did work for that 30mins its was 100% working.
Gary and Tien from Asus. These guys have both repied to me. They are not the big Asus people at all, they are just USA Asus. They havnt even done anything for me at all. A huge let down as they make themselves sound like they can help. My unit is a USA unit. They have not asked me to do any tests, offer me a test firmware or even a better video. Or ask what hardware versions I have, simple nothing and taking the piss of what they are offering to this advance community here. Not even an email saying the new update is coming out that may help.
The really bad part about this is its quite clear that the .26 update talks about upgrading the touch FW. Tien emailed me this morning saying they cant even give me a copy of this public released FW for me to fix my problems.
EPIC EPIC FAIL FROM ASUS.
What should I do everyone as im starting to think about getting on a hill a shouting this out to more than just this forum.
( first 'bad' forum post in my life like this )
Click to expand...
Click to collapse
I've downloaded several touch screen test apps and I'm not seeing the issues you're experiencing. I have noticed that some apps perform better than others, but that's about it. I'm thinking that you just got a bad unit.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Dude, just return it for a new one if you still can.
Hey guys, dont want to bring this post up again but think I need to to close it off.
I have a fully working unit now. The .26 software update has fixed it completely.
I am pleased I stuck to my feeling of what it was. Fully credit to XDA again with getting this update as that really was weird it not on Asus's website for the guys who really did need it. I waited for the XDA Asus guys but sadly ended with no reply on my email asking for a copy of the update.
Kezzainc said:
Hey guys, dont want to bring this post up again but think I need to to close it off.
I have a fully working unit now. The .26 software update has fixed it completely.
I am pleased I stuck to my feeling of what it was. Fully credit to XDA again with getting this update as that really was weird it not on Asus's website for the guys who really did need it. I waited for the XDA Asus guys but sadly ended with no reply on my email asking for a copy of the update.
Click to expand...
Click to collapse
Hey, it's always nice to hear that a case actually went over to the "Resolved" bin for a change (and all that on a stock ROM update instead of the custom ROM I had put my stake on, hehe). I'd rather have threads like these revived for messages like these than the dozens of useless threads that are cropping up on XDA re-chewing regurgitated (and partly decomposed) matters.
I'm glad it worked out so well for you, and wish you all the best and a happy forum forum presence and participation in the coming future.
Sent from my ASUS Transformer Pad TF700T
The help that XDA provides is what led me to it in the first place. XDA is teh bestest. I'm thinking about a manual infinity update myself.
There should be a motto for XDA like "XDA: Where the awesome happens!"
Hi All,
I live in Australia and received my TF700 from the US yesterday. I charged it up and then attempted to do the initial configuration where it asks you to choose a language. However the touch screen does not appear to be working – it is not responding anywhere I touch so cannot continue past this screen. Have tried cold booting (power and volume down key) multiple times but no change. I am guessing it is DOA – or is there a chance it is firmware related? I am reluctant to send back to the US as it is going to cost a fair bit...
I am going to borrow a mates keyboard dock and see if I can continue past this screen with that and then hopefully install latest firmware. It is the only thing I can think of...
Does anyone have any suggestions?
Thanks
I've recently noticed another touchscreen "issue". Apparently, the digitizer is either incompatible with the screen resolution or just a software bug. When you scroll really really slowly, you can tell it's jumping by a few pixels at a time. When you fling though, it is completely smooth. This does not affect actual usage whatsoever but I do think its an interesting thing to point out.
le rustle face
Keion said:
I've recently noticed another touchscreen "issue". Apparently, the digitizer is either incompatible with the screen resolution or just a software bug. When you scroll really really slowly, you can tell it's jumping by a few pixels at a time. When you fling though, it is completely smooth. This does not affect actual usage whatsoever but I do think its an interesting thing to point out.
le rustle face
Click to expand...
Click to collapse
I can't reproduce that effect. Can you explain a bit more?
Mines seems to be too sensitive. I put my finger as close as I can put it to the screen and it activates whatever icon is under my finger. Doesn't annoy me only when I get near the bottom right of the screen and the panel pops up.
Sent from my LG-P999 using xda premium
Eroc162 said:
Mines seems to be too sensitive. I put my finger as close as I can put it to the screen and it activates whatever icon is under my finger. Doesn't annoy me only when I get near the bottom right of the screen and the panel pops up.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
Good capacitive screen. You are electric, lol.
Hi Guys - thanks for the advice I appreciate it - however I decided to bite the bullet as I was dreading sending this thing back to the US etc... Anyway - so my touch screen was not working at all - so I borrowed a keyboard dock from a friend (lucky I had this option), and could then proceed to configure the device (using the keyboard of course). I then manually downloaded and installed the .26 firmware and hey presto it's a miracle - the touch screen now works perfectly! So it was a risk but I am glad I had a crack anyway. So hopefully no-one has the same issue as me but if so then this might be worth a try.
Thanks again for any feedback.
okantomi said:
I can't reproduce that effect. Can you explain a bit more?
Click to expand...
Click to collapse
1. Open up chrome.
2. Swipe down without lifting finger off.
3. Scrutinize the motions extremely closely while moving your finger as slow as you can.
You should notice multipixel (2 or 3) jumps.

[Q] C/Would this cause my digitizer to stop responding?

I posted this almost verbatim to my G+ stream. It says it all, basically, and I don't have time (at work right now) to give a lot of detail but I wanted to get this out there...
----
I received three text messages this morning at 7:25 EDT.
They appeared to be random characters, like when an OS is trying to display characters from a language that requires a codepage it doesn't have installed. They are as follows:
<sisa:68571244:1:1:199:41970681>ezG7k3jzC7mFo6SSm7KUIg
<sisa:65471246:1:1:199:43800551>HE85MqRY33Xf0qmVbaCjyQ
<sisa:65471245:1:1:199:43799818>SpxSbHILo1mHG/EjkMAF2g
All three received at 7:25. I was able to use my phone up to this point because I was able to view the messages normally. Now, suddenly I have no digitizer response. None whatsoever. To use my phone, I have to pull the battery and boot to safe mode then use my trackpad and menu buttons to access certain features.
Now, it seems to me, the first part is like an address packet, maybe including a sequence number. The second part is like what I see when e.g. viewing the output of 'cat somefile.binary' in Linux. At first I thought it was spam from a foreign country, but now I'm wondering if this was some binary code received and interpreted by my phone. I wonder if this is possibly an android virus/remote hack? Is that possible?
I may wind up wiping the phone when I get home and have ability to back stuff up, but this is annoying, to say the very least.
-----------
Now, I did a little googling and it appears that it may just be that T-Mobile was trying to send an update to the phone (maybe the fact I'm on a custom ROM is why it borked). But has anyone had this or anything like it happen to them?
Thanks much in advance,
CJ
Update
It appears the digitizer fouling *may* have been a coincidence. Very odd how coincidences seem to keep happening to my electronics. Anyway, I'm about to wipe and reflash, see if it persists. If it was a software bork, it should be 100% resolved with a reflash. If hardware, it'll still be borky.
It is now intermittent, and I tapped the screen pretty firmly a bit ago and it started working almost reliably again. Sounds like a loose connection. Very odd coincidence.
Will update when decided for sure the cause.
cj chitwood said:
It appears the digitizer fouling *may* have been a coincidence. Very odd how coincidences seem to keep happening to my electronics. Anyway, I'm about to wipe and reflash, see if it persists. If it was a software bork, it should be 100% resolved with a reflash. If hardware, it'll still be borky.
It is now intermittent, and I tapped the screen pretty firmly a bit ago and it started working almost reliably again. Sounds like a loose connection. Very odd coincidence.
Will update when decided for sure the cause.
Click to expand...
Click to collapse
My evo **** needs a good smack every now and then when the kb gets opened because it has a bad flex cable. since I'm not with sprint and only test roms on that phone I don't need the kb anymore but sometimes the little one opens it
Sent from my myTouch_4G_Slide using Tapatalk 2
Yep, I'm not so lucky. I need the touchscreen more than the keyboard
Still, was on the phone for 45 minutes today talking with two different reps, and my replacement phone (another MT4GS in Khaki) is scheduled to arrive in three days.
Time to see if I can return it to stock. It's a hardware problem, so what ROM is on it shouldn't matter, but I don't want to give them any reason to balk.

[Q] TF300 glitches? Advice please

My mother in law has a TF300 that has been really glitchy, so much so that it was basically unusable (the 4.2 update seems to have made it better, but still not perfect).
Her biggest issue has been sporadic touchscreen non-responsiveness. She thinks that this might be worse when connected to the internet (some app working in the background/updating?). Today she also had it where she couldn't use the screen while connected to the keyboard, but when she disconnected the keyboard it started working again, but that may have been a fluke.
In addition, there are times when it will act as if you've pressed an on screen button, even though your hand was nowhere near said button (almost like a ghosting effect on a keyboard, when the computer is running slow)
I've got the tablet with me for a few hours and I'd like to help her get it to the point where it's working normal again. Any thoughts or advice would be appreciated.
Almost as soon as I mentioned the on screen buttons, it started acting up.
Sent from my YP-G70 using xda app-developers app
Did it just start or has it been doing it since day 1? Go to settings, then Backup & Reset under Language & Input and do a Factory data reset.
That's the fist step in finding the problem. Bad side she will loose all saved data so save it to a pc.
4.2.1 update rolling out
hmm is that a galaxy player 5.0
I can't remember how long it's been giving her issues, but it has been a while. Multiple factory resets haven't fixed it. In the time I've been tinkering with it I've disabled some of the bloatware and turned off Auto Updates from the Play Store, so we'll see if those help in any way.
I've also noticed that the notification bar keeps getting stuck (either up or down). It looks like rotating it helps fix that, but still that's less than ideal...
Ah, the joys of being tech support :silly:
I've got it hooked up to my laptop in an attempt to use LogCat to help debug, but I'm not sure if I'm seeing anything consistent enough to label it as the cause of her troubles. Still, a resource available if anyone knows what I should be looking for there.
R3Z4545 said:
hmm is that a galaxy player 5.0
Click to expand...
Click to collapse
Yes, yes it is
If it's under warranty then send it back. Hopefully she hasn't had it over a year.
If it were mine it would've already been in the mail. Since its not unlocked and factory reset aren't working there's not much else that can be done without voiding the warranty.
Sent from my LG-LG855 using Xparent SkyBlue Tapatalk 2
is there a screen protector on it?
My TF300 always the same thing whenever there was background IO, even with Android 4.1.
Turning off the useless syncing and auto Play Store updates do help.
Also check to see if the storage has been filled. IO performance is also decreased by having a relatively filled flash.
So having disabled the Auto Updates from Google Play seems to have made a world of difference. I'm surprised background IO took so much out of the tablet, since it's running on a quad core, but oh well. Thanks for the suggestions everyone!

No phone audio after rooting and new ROM

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.

Categories

Resources