Hello all. I have HTC Surround from AT&T with updated 8107 firmware. I have spoted some strage bug (i don't know how else i could call it) and wanted to ask if thisone is possible and if i do think right. So i have this phone for about half a year and i'm pleased with it, nothing happened to it until now. Last week i was typing an SMS message and suddenly it just froze. I tried to restart it but the phone got stuck in the white HTC screen. My firmware then was 7720. I have done the hard reset and everything seemed to be ok but today the same thing happened with updated version too. I thought a bit and remembered that both times my phone was lying on top or near by wireless microphone receiver which was in working state. So can it be possible that some sord of electromagnetic waves is causing my phone to do this? Or it's just a coincidence?
as i'm a developer i didn't this it's a bug ithink it's accidentaly and you were at that place again like other time
But that's quite too big to be jusn an accident. I had this phone for half a year and nothing. Well i'll try this Friday not to put it on top of the receiver and will post what happened. This thing scared my quite big, i thought that mmc is broken but i have checked the bootloader (i don't know how the screen with 4 colors is called, i think it's bootloader) and it showed my mmc working perfectly. If it was not because of microphones what could then be the problem?
OK tried that this Friday too. Same think - phone near the receiver - phone dies and i must hard reset it to work again. How is this possible? Which part of the phone messes?
Very possible that a strong magnet could do this. Internally the surround uses a microsd (there are guides here for upgrading it but taking the phone apart). I imagine a strong enough field could corrupt a microsd pretty easily. When u say wireless mic do you mean bluetooth?
No no no, i mean microphones which are used on stages, i work as a sound engineer and my phone always is close to receivers, close to controlers and other stuf i use. So to avoid further coruptions i should put my phone further from all equipment right?
OK after this other few tries i have found out that it does indeed mess my phone, i have tried holding it near wireless microphone receiver and my phone have frozen and when i placed my phone further from receiver nothing happened. So look out for that
r0mka said:
Hello all. I have HTC Surround from AT&T with updated 8107 firmware. I have spoted some strage bug (i don't know how else i could call it) and wanted to ask if thisone is possible and if i do think right. So i have this phone for about half a year and i'm pleased with it, nothing happened to it until now. Last week i was typing an SMS message and suddenly it just froze. I tried to restart it but the phone got stuck in the white HTC screen. My firmware then was 7720. I have done the hard reset and everything seemed to be ok but today the same thing happened with updated version too. I thought a bit and remembered that both times my phone was lying on top or near by wireless microphone receiver which was in working state. So can it be possible that some sord of electromagnetic waves is causing my phone to do this? Or it's just a coincidence?
Click to expand...
Click to collapse
Is frozen screen? Still completely can't use? I feel a little bit like WM6 era's problems. After a certain amount to you. May is hardware have dark disease.
Related
Hi, everyone.
I searched for this and didn't find anything, but it's a little hard to know what to search for.
I use WunderRadio to listen to Internet radio. A few weeks ago, the Video Out (TV Out) screen started popping up at random times, usually when I was tapping something on the menu or on the screen. When it did, it was almost impossible to close and it really messed up my listening.
Some days it wasn't too bad. Sometimes, when it got really frustrating, a soft reset would stop it temporarily (or at least slow it down). When it was at its worst, though, nothing helped, and it was impossible to listen to WunderRadio.
It wasn't only in WunderRadio that this would happen--it would pop up occasionally in other applications, as well. But it was the most frustrating by far in WunderRadio.
I recently did a hard reset, so I only had a few applications installed. I first assumed that this was being caused by WunderRadio, so I uninstalled it. I still kept seeing that Video Out screen.
I selectively uninstalled applications and thought a couple of times that I had identified a program that was causing the problem. However, it kept coming back, seemingly regardless of what was installed or uninstalled.
A few days ago, this stopped happening. I haven't seen the Video Out screen a single time. I don't know if it has fixed itself (I doubt it) or whether it will suddenly reappear.
At this point, it seems like this could be due to faulty software, firmware, or hardware.
In July, I had a similar thing going on. I don't know if it was related to this or if this is just a coincidence. The phone all of sudden decided that it wanted to redial the last number called--over and over again! I would think I had it stopped, put the phone in my pocket, and get a call from a contact asking if I had called them. No, I hadn't, but my phone had!
As with the Video Out problem, sometimes a soft reset would help. Often, however, I ended up just having to turn the phone off for a few hours, then cross my fingers and try again.
With both of these problem, I was hesitant to send the phone in for warranty repair, because they were both so unpredictable that the repair shop would probably be unable to make either of these symptoms appear. My fears have since been borne out by the fact that both problems seem to have been solved--at least semi-permanently.
On the other hand, either or both of these problems could come back at any time!
Can anyone tell me what's going on here and what I can do about it?
Thanks in advance!
Are you using a wired headset? Maybe the pins are a little off and acting like the tvout cable USB pins and that's triggering it.
You should try to think if there is any correlation between a wire headset and this activity.
Also, do you actually use TV-out? You can just disable it entirely by a registry tweak so it won't be able to popup if that helps.
If you need anything further feel free to PM me since it's unlikely I'll find this post again
Good point! Yes, I am using a wired headset--most often when I'm listening to WunderRadio--which would explain why it happens most often when I'm listening.
I switched from headphones to earphones the other day, and that could very well be the reason it's no longer happening.
It's either the headphones or your USB port that's bad. But since you've said the problem has went away with new headphones, I'd say it's those. But it's a guaranteed hardware issue, although not necessarily the phone.
I had the same problem - TP would switch to TV Out mode randomly when mini usb was used (either charge or headphones). Mine needed a new usb socket, although I think theyyyyy jutssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssst swap the whole board. And I know it's off topic but can someone point me in the right direction to sort out my keyboard problem above?!
jjjacksonjjj said:
I had the same problem - TP would switch to TV Out mode randomly when mini usb was used (either charge or headphones). Mine needed a new usb socket, although I think theyyyyy jutssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssst swap the whole board. And I know it's off topic but can someone point me in the right direction to sort out my keyboard problem above?!
Click to expand...
Click to collapse
hehe does your keyboard repeat too quick? Settings - Personal - Buttons and reduce the repeat rates on 'up/down control'...on and stop eating so much candy while playing with your phone
Hello all:
I am on my first replacement phone, and am experiencing a recurring problem that I also had on my original phone. At times during the call, the person on the other end will not be able to hear me (a la 'mute'), but I can hear them. I have confirmed that the mute function is not activated (even turned it on then off), but no luck. My initial impression was just a faulty microphone/hardware, but given that my second phone is also experiencing then same problem, I wonder if it is something that I am doing. I can assure you that I am not in any way blocking the microphone hole at the bottom of the phone (experimented with that to see if it was the cause). I can also rule out network issues due to moving between cells - I have experienced this problem driving and sitting still at my desk.
This problem, more than the GPS issue, will be the deal breaker for me - this is a business phone and I spend a substantial amount of time every day on work related calls.
Thanks in advance.
Thomas
I have the same issue. My coworker had the same issue with his the replacement under warranty.
If I use the headset it works fine. If I mute the phone and un-mute it it starts working.
Something is fishy with the microphone of this model ...
Okay, now this is getting ridiculous. Either I have really bad luck, or I am doing something wrong. On my second replacement phone, and like the last two, I have problems with the microphone cutting out during the middle of calls. Am I completely alone, or am I just lucky in getting phones with bad mics?
I keep the phone in my pocket with a body glove case. The mic is not plugged up, and it seems random. Could there be a software issue (ie a piece of software interfering and taking over the soundstream from the mic)? Even though the person on the far end cannot hear me, I can hear them.
Thanks
T
@ banesong: I'm having similar issues. I've had my phone for a little more than 24 hours. last night i couldn't hear anything coming from my mic and obviously could not communicate from my end. taking the battery out and back in fixed it for me. but i look at this as only a temporary solution. hopefully this isn't a hardware issue
I am having the same issue. I've had my Captivate since the end of July and it is running stock 2.1 that came with it and unrooted. I can't remember when the issue first started. But it has been doing it a lot more lately. It seems to happen around 8 or 9 minutes after I am on the phone call. At first I would hang up and just call back. Then I discovered that the mic would start working again if I just turned the speakerphone on and then off again.
It is really starting to get annoying now. I am thinking about getting a warranty replacement. The only reason why I didn't get a warranty replacement sooner is because I don't feel like having to remember and reinstall all the apps that I have on my phone now.
Having the same issue here and I have an idea about the problem.
If you remove the lid on the back that covers the battery the microphone is disabled and no warning appears on the screen. This is the same behaviour we are all experiencing.
There are two round blank spots on the inside of the cover matching two contacts on the phone. My idea is that the 'lid open' detection checks if the lid connects these two contacts.
My microphone usually starts working when I squeeze the phone.
Not sure about a workaround yet but connecting the two connectors directly inside the phone should solve it permanently (but voids the warranty).
Hope that helps.
T
Sorry, please ignore my previous message. I couldn't reproduce it yesterday so it must have been coincidence.
However, I have the same microphone problem and would like to know if there is a fix for it.
Cheers
T
Possible fix
I know this is an old thread but I have one of these old phones and was having this problem. After fiddling with the settings a bit I found a setting under Call Settings->Voice Call->Noise suppression. I unchecked the box and the mic seems to be working - for now.
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.
Well I have been a owner of a LG Nexus 5 for the past (almost) 2 years now, in fact I am coming to the end of my contract very soon and will be able to either goto another company or get a new phone.
Anyways, sometime ago I experienced a problem with my microphone and external speakers not working, or at at least some of the time... After a bit of research online I found out my problem was related to a connection inside the phone that connected the bottom assembly to the main board at the top of the phone. It required me to remove the back panel and a few screws to remove the plastic cover, but the poster suggested putting some tape on top of that connection to hold it down more firmly to the socket it connected too. So I did this. I put some black tap (electrical tape cut to fit.) on top and then assembled the phone again. Viola, It worked!
Well, a short time after I decided that I wanted to update my phone from stock kitkat (4.4.4). Always been curious about custom ROMs and gave Cyanogenmod a try. Not only that I got bold and tried the nightly releases of the new marshmellow update. After some time I started experiencing things not working, like the camera, and a lot of freezing, hang ups and random reboots (not so much the reboots as the constant freezing). Often I couldn't get anything on the screen or the phone to respond from a locked state and when I did, often the phone would lag so much, that doing anything would take a long time and proved to be impossible.
I started thinking it was the nightly releases as the source of my problem and just kind of shrugged it off and figured "they will eventually fix the problem". I kept this thinking for quite some time. But it occurred too me one day that something else was causing the issue I was facing for the simple fact that the lag started showing up in the recovery mode (also custom) and a lot of times would continue to show up after I rebooted my phone. Hence, would rule out any 'software' issues I was facing.
I began to think that my problem was hardware. Maybe it was just time for a new phone. But still months away from the end of my contract, this meant I would have to pay off the 'problematic' phone first before getting a new one. I really didn't like that idea. So while looking into this problem, in a last ditch effort, I opened my phone again. Dunno why but I also decided to get rid of the tap on the connection I tried to fix before... I popped off the connection there and had a look at it. It didn't seem damaged in any way nor did the socket. Strange as it was I put that connect back in the socket and put the cover plate back on making sure not to torque the screws and assembled everything back up....
Now the mic and ext speakers work just fine and the phone is working like I just opened the box and took it out for the first time. And I have not once seen any problems... I understand what's happening here... still just wanted to share that for it was definitely weird or what?
https://drive.google.com/open?id=0B0pUNVcVRCJ7MThMc0NHLUNkSEU
Sorry about the link, only way I can upload an image.
Just so there is no confusion... an image of the effected area, inside the phone. The arrow points to the connector and more importantly the area of the connector that seems damaged. If I press lightly where the arrow is pointing on this image, the assemable at the bottom (speaker/mic) will work, indicating a loose connection. Although after visual inspection, I cannot see any damage to connector or the socket. I suppose the only way to really "fix" the issue is to order a new part. As stated previously, already tried tape on the socket to help hold it down, but that seem to cause just as many issues with the phone performance. Any other suggestions?
When ordering a replacement part, you need to be careful because there was another XDA member replaced the same part with a cheap 3rd party solution and the phone would not charge until he replaced it with an oem part.
http://forum.xda-developers.com/google-nexus-5/help/to-buy-usb-charging-port-flex-cable-t3314357
Does anyone else have issues with there ext. speaker and mic not working?
An update on the phone;
back to square one. My ext speaker and mic will not work. And that socket has something to do with the LCD connection on the screen as it will black out if just the right area on the back of the phone is pressed. Only way to revive the phone is to long-press the power button for a reboot. Then will come up fine but speaker and mic still do not work.
audit13 said:
When ordering a replacement part, you need to be careful because there was another XDA member replaced the same part with a cheap 3rd party solution and the phone would not charge until he replaced it with an oem part.
http://forum.xda-developers.com/google-nexus-5/help/to-buy-usb-charging-port-flex-cable-t3314357
Click to expand...
Click to collapse
Wow, that sounds pretty low level tactics of LG... just shameful really, but not hard to believe these days...
Quite honestly, I am just going to replace the phone. Think I got a pretty good run out of it and think its pretty well time for an upgrade. Anyway, for the reason I got the phone, it wont matter the speaker and mic don't work. Just going to use it for development and it will be a good test device.
Oh an this post is related to this thread so I thought I would link it for it may help someone else facing similar problems....
https://forum.cyanogenmod.org/topic/125227-nightly-cm13-releases-make-my-nexus-5-very-slow/
I'm not sure that LG had anything to do with the low-quality replacement parts.
If I were you, look for a n5 with a smashed screen that is suitable for parts.
audit13 said:
I'm not sure that LG had anything to do with the low-quality replacement parts.
If I were you, look for a n5 with a smashed screen that is suitable for parts.
Click to expand...
Click to collapse
Good idea, except the iphone is the most popular phone around here ... find it pretty hard to find one, been looking. But thanks.
I have seen quite a few busted n5 phones in Toronto. I have managed to get working phones with a smashed screen for as little as $30 which is rare for Toronto. Average I pay is $40 to $50. For this price, I either use the phone for parts in several phones or I get third part screen from Aliexpress for around $40 CAD.
I just want to update this as well...
I am fairly certain (now thinking about causes) its not really a design flaw, but more so because I frequently sat on my phone when it was in my back pocket...
audit13 said:
When ordering a replacement part, you need to be careful because there was another XDA member replaced the same part with a cheap 3rd party solution and the phone would not charge until he replaced it with an oem part.
http://forum.xda-developers.com/google-nexus-5/help/to-buy-usb-charging-port-flex-cable-t3314357
Click to expand...
Click to collapse
It was not me but I had that same experience. Replaced with a cheap oem and it didn't charge after that.
I found out why. The charger usb socket was not connected to anything ! Unbelievable! It lacked the black plastic backing for that part of the cable to connect to.
Owned the phone for about a month now. Phone was working perfectly fine for the majority of this time. I use 2 different sims and they were both working smoothly until recently.
A few days ago, I woke up and the phone wouldn't recognize the Sim cards anymore. I took out the Sim tray, cleaned the Sim cards and the tray as thoroughly as I could and they both started working again. A few days later, I restarted my phone and both of the Sims stopped working again.
This time nothing I would do would solve the matter, so for the next few days the phone wouldn't recognize either Sim. I have unlocked the bootloader and rooted, factory reset it and updated it none of which seems to solve the issue.
I use this phone for gaming so last night to my surprise one of the Sims started working (sim was in for a couple of days) and all connectivity was perfectly fine - I tried putting in my other Sim as well but again the phone wouldn't recognize them anymore. Tried putting in only one card on the Sim 1 slot but it made no difference. I don't understand what the issue could be.
Do you have a converted CN version or did you buy a global version? (just curious, as far as I know only CN -> WW versions faced this issue and I would like to know if this is a coincidence or an issue with these versions. But I could be wrong as well)
Nevertheless I would make use of warranty and send it back to Asus to get it repaired.
Yeah it's CN version > WW ROM. It's absurd how randomly it was hit with this issue. Again, the phone was reading a sim card perfectly fine out of the blue last night, then when I took out the Sim tray to insert another card, went back to square one and wouldn't recognize either.
I know.. If you had searched this forum or the rog reddit you would have noticed there are multiple topics like yours and all people explained the very same. Seems totally random.. sometimes it works, sometimes not. Unfortunately no one was ever able to post an accurate answer of why this is the case or how to fix it. At least there is none here, on reddit or the zentalk forums.
Since all device so far were CN -> WW version I don't know any successful case. Asus mostly rejects the support and redirects people to their sellers but those mostly refuse to do something. (they probably know that issue and it's cheaper to do nothing)
I wish you best of luck. Maybe you could try to contact Asus and report the outcome so we finally have a documented successful repair.
Edit: as said, that's only my knowledge, maybe there is a fix and someone found a way but they either didn't publish it or they posted it in a not so well known forum.
I wonder if the connections that touch the SIM are poorly designed. If it is such a widespread issue that randomly seems to come and go, it could be similar to the issue I had with the Kunai 3.
The pins on the side are designed to give a little when sliding the controller off and on the mount or charger. After moving them between the mount and charger twice, some pins fell off and others never popped back into place so they could make a connection. It turns out they never secured the pins well enough to handle it.
Hello, I had a similar issue.
My sim-cards wouldnt be recognized, sometimes only one of them, sometimes both. Additionally, my fingerprint-sensor wasnt working too. By checking pictures of a disassembled phone I could locate the problem inside. It has a connector on the lower end of the phone, which is for sim and FP-sensor. I can definitely and easily come loose.
Quick and dirty fix for me, was pressing with controlled but quite some force on the lower end of the LED-Rog logo while the phone laying flat on the table. I used my thumb, pushed and restarted the phone to check. Didnt work, pushed a bit harder and restarted again until it worked. The back glass has some flex to it, to make it possible to push the connector back in. Still, be careful to not break it, if you try it yourself.
When I found that solution, I've sent it in on warranty for proper fixing with this Information to ASUS. They replaced allegedly the mainboard. But I actually think, they just fixed the connector in place, because bending the phone to a certain degree "unfixed" it in my case again. I dont know, if its the same issue you have, but if it is, hope it helps everyone.
r0me5 said:
Hello, I had a similar issue.
My sim-cards wouldnt be recognized, sometimes only one of them, sometimes both. Additionally, my fingerprint-sensor wasnt working too. By checking pictures of a disassembled phone I could locate the problem inside. It has a connector on the lower end of the phone, which is for sim and FP-sensor. I can definitely and easily come loose.
Quick and dirty fix for me, was pressing with controlled but quite some force on the lower end of the LED-Rog logo while the phone laying flat on the table. I used my thumb, pushed and restarted the phone to check. Didnt work, pushed a bit harder and restarted again until it worked. The back glass has some flex to it, to make it possible to push the connector back in. Still, be careful to not break it, if you try it yourself.
When I found that solution, I've sent it in on warranty for proper fixing with this Information to ASUS. They replaced allegedly the mainboard. But I actually think, they just fixed the connector in place, because bending the phone to a certain degree "unfixed" it in my case again. I dont know, if its the same issue you have, but if it is, hope it helps everyone.
Click to expand...
Click to collapse
Good tip and glad it worked - this could help a few out there. Perhaps ASUS should have included some instructions explaining how to press/bend the device back in order when it happens ...
I had the same issue and quickly found a fix. I bought a OnePlus 9 Pro and relegated this glitchy piece of junk to my desk drawer. Good riddance.
nickdagriff said:
I had the same issue and quickly found a fix. I bought a OnePlus 9 Pro and relegated this glitchy piece of junk to my desk drawer. Good riddance.
Click to expand...
Click to collapse
Paying over $2,000 for a OnePlus 9 Pro seems like an expensive solution, but I am glad it worked out for you. Best of luck over there.
r0me5 said:
Hello, I had a similar issue.
My sim-cards wouldnt be recognized, sometimes only one of them, sometimes both. Additionally, my fingerprint-sensor wasnt working too. By checking pictures of a disassembled phone I could locate the problem inside. It has a connector on the lower end of the phone, which is for sim and FP-sensor. I can definitely and easily come loose.
Quick and dirty fix for me, was pressing with controlled but quite some force on the lower end of the LED-Rog logo while the phone laying flat on the table. I used my thumb, pushed and restarted the phone to check. Didnt work, pushed a bit harder and restarted again until it worked. The back glass has some flex to it, to make it possible to push the connector back in. Still, be careful to not break it, if you try it yourself.
When I found that solution, I've sent it in on warranty for proper fixing with this Information to ASUS. They replaced allegedly the mainboard. But I actually think, they just fixed the connector in place, because bending the phone to a certain degree "unfixed" it in my case again. I dont know, if its the same issue you have, but if it is, hope it helps everyone.
Click to expand...
Click to collapse
Works like a charm here! Congratz!
Omg worked here too, now I have a Poco F3 AND a revived ROG Phone 5...
.
You are the mvp. I love this phone and using it for almost a year. Suddenly sim no longer detected. I tried everything, unlocked bootloader, update firmware. Hour and hours of trying to revive it. I even called Asus and they said to call the Chinese warranty support. Then finally came across this thread. Pressed down hard on the lower end of the logo of the phone on its back. Restarted and now it's detecting the sim again. Thank you so much