Hi
My MIA2 decided it wanted to go to headphones mode. But I never asked that. I didn't even use headphones once.
And you know what? THERE IS NO HEADPHONE JACK INPUT ON THAT DEVICE. WTF Xiaomi.
So, headphone mode is running as long as the phone is not charging. Please, how can I get rid of this?
edit - that phone has taken so much falls and damage that it could have died physically at least 50 times. i fell with all my weight on it. the screen cracked. the back camera has a hole in the glass you know what ? this ****er didnt even reboot and was still working flawlessly... and now i have this bug? cmon
- some software on the play store reroutes audio from headphones output to speaker output. it works but its a crappy workaround : if app is killed, its not working.
- i wont hard reset because i fear the process will trigger big mess with the root and i have no time nor want to do the flashing from zero cause i have a life.
-could I grill the usbc port with a charger for redmi note 9 pro
-issue -seems- solved with occult background electronic magic happening during the battery charging. or maybe just blowing in the usbc port like an idiot. have no clue how it triggered and what solved it. meh/10. I suspect Google assistant. I had a notification about headphones and assistant, didn't pay attention and killed the notification. Next time I looked at my phone there was that headphone icon and no sound. I wasn't messing with phone settings and kernel and stuff. Plain official rom + magisk as I need the calls and spent way too much time on installing random rooms & recoveries & obscure tweaking & also FIXING PROBLEMS I CREATED BY CHANGING ROMS (god, I wish no one knows the feeling when your brand new mi A1 is fried thanks to xiaomi software, and you have to redo A/B partition and when it reboots, its only to show you that IMEI is null and you'll waste countless hours fixing that ****) and I don't want to do that ever again .
What's ironic here is I got custom rom-like issues on a totally stock & legit A2 rom. You don't say
Related
I'm having a problem with my phone thinking and acting like a corded headset is plugged in. I started having the problem using ZenEXP-0.9.6OC and thought maybe it was a ROM problem then flashed over to fresh 2.1 to no avail. A reboot doesn't fix the problem and neither do the two other fixes on here. It does go away briefly when I plug in my USB cord but comes back shortly afterwards. Has anyone else had this problem? It's become annoying having to run out to my car to talk through the stereo.
Sounds like it is indeed a hardware issue. Sounds like perhaps some sort of short in the headphone circuit. I would suggest reflashing the 1.5 recovery image and bringing it to a store or trying to fix it yourself. I would try using a bright light to see if you can see whats causing it.
So I RUU'ed back to 1.5 and took it into Best Buy (Where I bought the phone.) The lady told me to jam a 3.5mm headphone plug into it and pull it out repeatedly. She said that that was all anyone could do. I attempted that and it fixed for about 45 seconds (Long enough to make a phone call) and then it cut back out again. I tried taking my phone apart to see if I could see anything and there were no obstructions. What I'm wondering now is if I could customize a ROM to allow me to disable the headphone port all together. I never use headphones with the phone anyways and it would allow me to keep this phone without running the risk of having to switch to 2.1 RUU.
i've got the same problem for long ,i solve it temply with toggleheadset.apk ,,but it doesn't work in android 2.2..
Hi, greetings from Colombia!
Mi Motorola Milestone (that I buy the last September after my lost Nokia 5800) on this days had one hardware problem, the power button failed (semms broken), so I take it to the warranty (using CyanogenMod 7 for Milestone Android 2.3.5) and the fixed it!! Weee... But...
I just enjoy my fixed phone for just 1 week, because another defect comes up, the digitizer begins to fail, first, become unresponsive from the right side (and the search button), and, after 3 days, all was OK, but in the afternoon the scren become "crazy", and sometimes the right side begins to fail again, so.. this Monday i has to return it to warranty (I'm hoping that they change my phone for a new one).
From my sight, I have a really bad luck, having two of the most commons problems of this Milestone/Droid phones.
Do you know another common failure of this phones?
The "bubbly" keyboard is quite likely to lose a few keys and the paint on the camera button comes off quite frequently.
I have experienced some of those hardwares problems with 2 Milestones. The camera button I guess its the most common.
Hardware problems that I had:
- Digitizer failing. Replaced on warranty, no problems since.
- Camera button paint came off.
- Bad headphone jack.
- Bubbly keyboard on one of the phones, went to RMA, problem persisted.
- Loose battery cover.
Most of the problems you can live with, except for the failing digitizer.
Sent from my Milestone using XDA Premium App
my digitizer went bad. bought a replacement on ebay. arrived in 9 days. it ain't so straightforward inside the milestone coz of the slider mech but all's good now
linuques said:
[...]
- Digitizer failing. Replaced on warranty, no problems since.
[...]
- Bad headphone jack.
[...]
Click to expand...
Click to collapse
Second that.
Lots of people report their screens going nuts or becoming unresponsive - due to moisture or general digitizer failure
My headphone jack was a pain at first - but the more often I use it the better it gets
Guys - I am expecting to receive my Milestone (1) on Monday. But I am just now seeing these hardware issues that you had. After how long did the hardware problems - especially the digitizer - show up? I'm wondering how long I will have to go before it starts calling for parts!
My digitizer died after 9 months (December -> August). At the beginning (first week before completely dead) right side of screen stops working. In second week I saw that digitizer is jumping over menus by itself, then screen stops working.
Everything else is working fine. I hope there will be no other problems with other parts of phone
adamz667 said:
My digitizer died after 9 months (December -> August). At the beginning (first week before completely dead) right side of screen stops working. In second week I saw that digitizer is jumping over menus by itself, then screen stops working.
Everything else is working fine. I hope there will be no other problems with other parts of phone
Click to expand...
Click to collapse
Same time for me, after 9/10 months my digitalizer started to fail, and the power button problem was 9 months after I got it, btw maybe my power buttons problems was caused by using this buttons to hang out calls (using CM7 settings), so my advice, don't use this function.
And, talking about my phone, the replace it . Now I have a new Milestone, wee...
I bought mine in May 2010 and haven't had any hardware problems.
But a friend of mine bought his' just a month earlier and his keyboard fell apart and the camera button lost its coating.
I guess it's just a matter of luck - and good care of course
The headphone jack has been the only problem I've run into, and it's an issue that apparently can be at least partially fixed by shimming it in one direction or another.
Thanks for the heads up. It seems I have nine months before sh!t starts happening then! Lol. I'm wondering if some of those hardware problems can be fixed or prevented by opening up the phone and giving it a periodic brush out / clean out? For example the headphone jack after becoming loose can probably be re-soldered, etc?
I don't think the solder connections are faulty on the headphone jack.
It just seems to be a little to loose for most 3,5mm plugs.
Some of my headphones give me a lot of trouble - others none at all.
And the more I use it - the less problems I get.
So I'm led to believe that it's more a problem of dust and corrosion that worsens the contact quality.
Talking about headphones, I use a wired BlackBerry headphones, seems ok for me, but sometimes when I move it in the jack, my music is paused (maybe this is related with the different standars of jacks?)
Even if you use a standard 3,5mm stereo connector with not 4th contact at all the phone's gonna interpret a slight loss of contact the same way it does pressing the media button on a media headset.
My Milestone sometimes started playing music when I was watching a movie or whatever.
But if your Phone is rootet you can use the app Autostarts to disable the phone reacting to the media button and therefore problems with loose contacts.
I'm really hoping someone can help with this, because it is driving me insane! I will try to keep this as brief as possible, but feel free to hit me with questions.
So 2nd hand Samsung Galaxy S I9000. I have had issues. At first the home button didn't work so I had to get the screen replaced. After this I installed DarkyRom v10.2.2 Extreme Edition TouchWiz4.
After I installed the Rom the sound went (can't remember if it was instantly after the install, it may have been, but I suspect not. It may have been after a day or 2. No longer). The sound worked through the headphone socket, but would not come out of the speakers. I figured that it thought that the headset was plugged in. I installed Cyanogen Mod (as it has the headphone indicator) and lo, there it was. Headset indicator was on, despite not being plugged in. Tried some fixes (compressed air into the headset socket, plugging in and removing headphones). No dice.
Took it to a repair centre, and they fixed it. BUT, when it came back, the LEDs lit up whenever the screenlock was engaged. They looked at it again and said that it was a problem with the mainboard and wasn't fixable. Got into quite an argument with them as the LED problem did not exist prior to taking the phone in, so they agreed the headset repair for free. I am not convinced of their honesty nor that they actually replaced anything.
Obviously quite annoyed at this point, as I basically now have a battery drain. Anyhow, decide to reflash it again, see if it fixes it, so I flash DarkRom 10.2 Resurrection Edition. OMG The LED problem is fixed. Sound still works at this stage.
I then flash DarkyRom v10.2.2 Extreme Edition TouchWiz4 again. Boots up. THE DAMN SOUND HAS STOPPED WORKING AGAIN! I have not plugged headphones into it, so it cannot be the jack socket. I have only just brought the phone home again.
I have reflashed back to DarkRom 10.2 Resurrection Edition and I still have no sound. I am now thinking this may be a problem with the TouchWiz4 Rom, as I am at a complete loss why the sound would have gone between the Resurrection to the Extreme edition. I haven't put Cyanogen back on, but I am pretty certain that it will tell me that the headset is plugged in.
Does anyone have any idea what I can do to get sound back on my phone, because I am basically back to having a useless brick? I have tried searching but cannot find anyone asking a similar question.
Many thanks, and apologies in advance if I have broken any n00b rules! If any further information is required, fire away.
Cheers
torz77
Ok. I have done nothing since posting this message and now the sound just works again. I'm not going to risk reflashing again, but if anyone has any ideas why I am having this issue then I would like to hear it, because I am not convinced that the problem is going to go away for good!
Hello again!
As I suspected, this problem has not gone away.
I still have not plugged anything into the headphone socket, so I think that can be ruled out as an issue.
The sound has gone on it twice now, since my post. The first time I took it out of vibrate mode and enabled sound. I noticed that the keypad wasn't clicking. Tested it, yep. Stuck in headset mode again.
I went to power down the phone, and noticed that when I hit reboot the keyboard click had returned. When it rebooted sound was back on.
The second time, I was playing the ultra-lame App ARShooter. Sound went off midway through playing it. Again, I heard the keyboard click comeback when I hit the reboot option when powering down.
Sound came back again.
There is clearly something wrong with this phone, and I would love to know how to fix it, or if it's even possible, or where I should even start looking. If anyone has any ideas of what is causing this problem, then please let me know.
Thanks again!
Flashing back to stock?
Hi there.After one and a half month i noticed that the one speaker of the headphone provided inside the i9000 package was not working.Also the i could barely hear what was the other person was saying.I tried a normal headphone with the simple 3.5 audio jack(no mic) and it worked fine.Also i used it in the car and stereo works fine,but if i put a 3way 3.5jack then it doesnt really worked.I flashed a 2.3.4 simple honey rom but it didnt work .I tried to go to the secret codes menu using *#*#197328640#*#* but the AUDIO directory is not opening!I tried pressing on it and typing {5} (it the number of the directory) but it doesnt open whatever i do.I tried voodoo and although it works wonderfull at playing music i still cant use the mic+headphones that came with samsung or another one i bought to check if the first is faulty.Now i want to revert back to stock so i can take it to the samsung shop for repair;What drivers do i need and what do i do to take it bac kto stock? stock rom that came with my phone was xwjvi 2.3.3
Thank you!
this happened a few hours ago and i've been runining around to find a solution.
i was going through my day enjoying my music on the SGT through my headphones. and suddenly, connected the headphones, and BAM sound is coming out to the left headphone ONLY. i know about pushing the jack all the way in.done that with 3 different headphones..nothing!!!i have overcome 4.1 on my SGT. tried installing the rom again, played around voodoo sound a bit..nothing.and here i am helpless and depressed!! if anyone please give me a hint on what to do !! and again..this happened out of no where all of a sudden!!
Sounds like a hardware issue. Maybe lost the physical connection for the contact to the right headphone, would have to re-solder if possible. Then again, this requires physically opening up your tab and checking everything going to the headphone jack. I advise against opening it if you don't know what you're doing.
bigz1981 said:
Sounds like a hardware issue. Maybe lost the physical connection for the contact to the right headphone, would have to re-solder if possible. Then again, this requires physically opening up your tab and checking everything going to the headphone jack. I advise against opening it if you don't know what you're doing.
Click to expand...
Click to collapse
damn. didnt want to hear that...but could this happen suddenly ? i mean the tab wasnt exposed to anything that would cause the jack to disconnect.no shocks no falls no water nothing !!
anything can go wrong at any time with electronics...sometimes it just happens. I've seen it working with computers for over 10 years. Something fails for no apparent reason and it can't be explained.
EDIT:
It's a long shot, but try taking out the battery for a few mins, then putting it back in. It's worked for weird glitches I've had on my phone...
Have you try another ear phone set?
Sent from my GT-P1000 using XDA
Bought my phone in November and until May it was working perfectly, I thoroughly enjoyed the phone.
During the installation of the April security patch my phone got stuck and I had to reboot it.
As a result, Android didnt work anymore. Even after hard resetting the phone was super slow and full of errors.
I sent it back to an official Moto service center; so they could reset the firmware.
When I finally received my phone back, I notice there were marks on the back-glass that werent there before.
the "repair paper" said that "broken parts have been replaced".
The phone works quick again, except that the loudspeaker cracks really bad on 80% volume... and when calling I can hear a very soft but subtle abnormality in the speaker as well.
I also notice a small delay with the fingerprint scanner, which wasn't there before.
When I look into the android recovery menu I can see that this phone has a different serial number than the one I sent to them.
- Do you also think they gave me someone elses phone? Because my loudspeaker didnt crack at all at high volume.
- Is this legal ?
Simply repairing android doesn't require opening up the phone to "replace the motherboard", right?
Seems like they had to replace mainboard. Which is logical, because Android errors might have been a result of damaged memory.
At least this would explain serial number change.
And the speaker problem might be a result of incorrect assembly after the repair. (this happened once to me, when I received my Lumia 930 after the repair, headphones jack was not working correctly. It did not react when headphones were connected - fortunately, when I started to move the plug in the socket, the socket "jumped in" into its place and it started to work again)
I'd return the phone and request them to fix the problems you described. I don't think much more can be done on the discussion forum