Database Info

Random headphone mode and no vibration

I have a Touch Pro2 on Verizon that has recently started to put itself in headphone mode at random. Trying to push the pins down via stylus or plugging and unplugging the headphones hasn't worked at all. I did soft resets and left the battery out for a while.
It was at this point that I realized the phone had also ceased to vibrate.
I tried putting the phone on vibrate, but it acted as though it was on silent. I then finally flashed the ROM, which confirmed both issues to be due to hardware (which was already pretty obvious ...)
It's worth noting that sometimes when I select a Manila tab, I can hear the motor TRY to vibrate, making a single slight clicking noise. Normally, I wouldn't make too big a deal out of the vibrating issue, but that coupled with only hearing half of my notifications due to the headphone problem is maddening.
I hastily opened the phone to see if it was anything I could fix (which wasn't smart, but I guess I figured the dings on the phone coupled with the fact that I was using the latest MightyROM release was enough to forget the warranty.) Obviously, I got nowhere.
I'm out of ideas at this point, and am curious to hear what everyone here has to say. I'm nowhere near upgrade time, and don't feel like paying full retail for another phone.

flash the stock SPL, flash the stock ROM, tell verizon to fix it. Or get insurance and pay for a replacement phone.

Interesting note: Quickly inserting and removing headphones runs "Windows Media", and doing so twice redials the last number. Figured this post would at least be entertaining if nothing else.
I'm still trying to figure this out (since that's the kind of guy I am) but I'll probably end up getting a new phone altogether. Probably won't get another Touch Pro2, but it'll be hard to go back to any other QWERTY keypad after this one.

Rooted, Running Revolver, Screen Problem

So, I've rooted my TF and been running the latest Revolver ROM for about a week. Everything ran awesome with very few flaws. I also recently RMA'd my dock for the sleep issue and just got it back yesterday.
I hooked up the dock to my TF and it ran great all last night and this morning. Everything charged just fine. I packed it up to take to work, took it out at work and...nothing.
My TF would not wake from sleep. I thought maybe I had suddenly encountered the sleep of death issue that I had heard about but never experienced, so I held in the power button and restarted.
The TF restarted just fine. Booted past the first screen and the custom animation screen. But as soon as it was supposed to boot into the homescreen, it goes blank. The TF is on as I can hear email notifications and stuff, but there is nothing on the screen. I tried booting and re-booting with the same result.
So I wiped cache. Same result.
After getting an MD5 Checksum error from the one backup I had of my system through CWM, I wiped data/factory reset. I actually got past the boot animation and started setting up my TF again. However, the screen was set to auto-bright (I like it at fairly bright) so I started to adjust it. As soon as I touched the brightness controls, the screen went black. TF still on, just no screen.
I booted back into recovery again, wiped data/factory reset again and again it booted up just fine and took me to setup. Went to adjust brightness in the actual settings menu and as soon as my finger touched the brightness bar, the entire screen went black.
WTF? Has anyone else gotten similar experience with your TF, either rooted with a new ROM or not? Not a whole lot I can do with a tablet with no screen.
Here are the things it is not based on my observations:
1. It is not a dead screen. On boot up, the screen works. Animation plays well. I can access the CWM recovery menu.
2. It's not a dead touch screen. I can factory reset and go into the setup using the touchscreen.
Here are the things I suspect it COULD be:
1. Something up with the Revolver ROM. I had refrained from applying the 2.1.1 update as the update immediately after that just reverts it back to the version before the 2.1.1. update. However, I did apply the update after the second time of factory resetting.
2. Something up with my dock/dock software? I didn't have any of this issue before I received my dock back.
Please, can anyone help me out here? Sorry for the long post, but wanted to include as many details as possible.

Does the issue occur not docked? Can you use the dock brightness buttons to bring back the screen?

It happens both docked and undocked . Dock brightness buttons do nothing.
I left the tablet alone for about twenty minutes and when I came back the screen was on. Brightness was at max. But again as soon as I touched the brightness controls no screen.
Sent from my DROIDX using XDA App

Actually (after wiping and restarting yet again) I found that even the dock brightness buttons cause the screen ti go blank.
Sent from my DROIDX using XDA App

Okay so after searching high and low for others with this issue i found two unresolved threads. It seems to be a software problem that will not allow the backlight to go beyond 50% brightness when not plugged into the charger. I'm at work now so I can't test this for sure until I go home later this evening. If this is the case, then it could be a problem with my root and ROM installation. I will try the following things in order.
1. Restore from backup done right after I gained root access. This is basically my system with the original software. After gaining root, I did delete some things through Titanium Backup that I felt were bloatware. This might have had something to do with it so restoring the original backup should return these things to their normal state. The only problem with this is that when I tried to restore from recovery, the MD5 checksum gave me an error. I have found a thread that allows you to override using ADB and will try once I get home.
2. Unroot completely and flash back to stock. It worked when I was unrooted and stock, so theoretically it should work again.
3. If the above two methods don't work, I'll just RMA it back to ASUS. I already called in and got an RMA number for the issue. At least by doing the above two things I can ready the tablet to be within warrany specs in case it's just a dud and needs to be replaced.
Will update with results.

Results
1. When plugged into the charger (with or without the dock) I can up my tablet to full brightness just as the other couple of threads I read stated. Even with brightness up at full and running on battery (blank screen) there is still HDMI out. Wish I had realized this BEFORE I did a complete data wipe.
2. Had to use terminal emulator and the following link to recover the CWM backup with the checksum error: http://forums.androidcentral.com/epic-4g-rooting-roms-hacks/70519-md5-sum-mismatch.html
It worked awesomely to bring my precious tablet back to stock with all applications I ran previously. Still no change in the brightness issue though
Now on to try to unroot and see what I get...

sounds like you're taking the right steps.

I hope so Malandro2011.
Looks like I will have to RMA after all. I unrooted, went back to stock recovery and a completely new install of the most current firmware. No dice. The issue is still there.
My tablet's all packed up and ready to ship off to the god awful Texas facility for repair/replacement. Since they sent my dock back with a bend in the metal near the adapter port, I made sure to take pictures of the entire tablet before replacement as well as leaving a note to them under the RMA slip about the condition of the tablet when I shipped.
My biggest question is what triggered this to happen. Was it rooting and installing a new ROM? So many people have done this without incident it is hard to believe this was the problem. Was it whatever changes they made to my dock? I was running smoothly for a week before charging it in the dock overnight.

many people have rooted and your the first I've heard with this particular issue so i doubt these roms caused it...but could be wrong.
Seems power related since adjusting the brightness sends more power to the screen or less then the screen fails.
I reckon its just faulty...
I wonder if they'll replace it with the newer models that cant be rooted yet..

Yeah, I agree it seems power related. My unsubstantiated theory is that when they adjusted the I/O board in the dock, perhaps it changed some of the power settings and caused some sort of overload/short in my tablet when I used the dock.
Such a shame to send it back. It was one of the earliest models and beyond this was one with the fewest problems. No light bleed, no stuck pixels, no sleep of death, good QC on the hardware. Here's hoping that what I receive back will be just as good (and hopefully not one of the unrootable new models).

Update for anyone following this thread. Received my repaired TF two days ago. Total away time was around 2weeks. It looks like hey had to replace the entire screen. Looks nice with even less lightbleed than before but the screen has a faint yellow tint that I have heard is common with later model TFs. Not sure if I should send back again as I really don't want it gone for any longer time...

[Q] Sleep of Death

I'm looking for a magic solution to this.
My rooted (Prime 1.8) went into the sleep mode when connected to the dock. Never had any issues previous with this. Its been a great tablet.
I played about with it somewhat. Can go into APX mode, can see the internal flash etc. All works except screen won't come on.
I even reverted (nvflashed) back to stock in case of having to send it in.
After reading a few more posts this morning, someone mentioned about the backlight being the problem.
He was right. When holding up a flashlight to the screen, you can see the text on the screen. It is actually booting fine, just can't see it. It doesn't actually go to sleep.
Anybody know how to rectify this? I have a product replacement plan from the shop I bought it, I'm just concerned about getting one of the newer non rootable devices. Would rather try to fix this one first.
Thanks for any help.
Mike

Keeps going into car mode...

My M8 for the past week has been entering car mode for no apparent reason. Could it be there is something wrong with the USB port on the phone or something else?

It's the charger/cable you're using. My M8 does it as well with a cable (that's a power-only cable, no data pins) I use to charge my phone from my PC with. I've had 4 replacement M8s (all for separate hardware issues) and they all did the same thing on the same cable. It hasn't done it with any of the other several chargers I use at home. But when it does to it on that one cable, it only seems to do it when I try to use any demanding apps/games while plugged in. It won't do it if I'm just poking around the launcher or browser.

Mine is happening when not plugged in also.

sco77 said:
Mine is happening when not plugged in also.
Click to expand...
Click to collapse
Ahh, well then yeah, I would have to say there's definitely some hardware issue with your USB port then.

Yup, my phone is screwed its stuck in car mode, tried everything. Is there a way to edit a system file to completely disable it? Replacing phone is not an option for me.
Sent from my HTC One_M8 using XDA Free mobile app

sco77 said:
Yup, my phone is screwed its stuck in car mode, tried everything. Is there a way to edit a system file to completely disable it? Replacing phone is not an option for me.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
I've tried disabling/freezing anything with the word "car" in it in Titanium Backup to no avail on my M8, it still does it with that same cable. When it does it and the "Car Mode Enabled" notification shows up in the notification shade, I can long-press it and go to app info, where it takes me to "Android System", so it appears to have hooks deep into the Android OS and something you can't really disable. This Xposed module may have some options to disable it or at least keep it from being so invasive if you're rooted.
But I guarantee you that you can get the phone replaced under warranty, even if you have it S-Off'd/unlocked, because I have done it. Unless your phone is physically damaged..? But even then, they may not charge to repair the USB port or motherboard if that's the only issue. Can't hurt to ask HTC.

I seem to have "fixed" it by plugging it in about 20-30 times and violently yanking out the cable... Not sure how long this fix will last since looking into the port I seen nothing wrong with any of the pins or any contaminants in there, also high pressure air didn't work.

sco77 said:
I seem to have "fixed" it by plugging it in about 20-30 times and violently yanking out the cable... Not sure how long this fix will last since looking into the port I seen nothing wrong with any of the pins or any contaminants in there, also high pressure air didn't work.
Click to expand...
Click to collapse
I had exact same issue. It is debris stuck in the port. Get some computer duster or air compressor and it will clear it up

Nice
Hey you guys need to go to app manager then swipe to (all) under that you should disable dock mode and car mode then reboot. Should fix problem for live. Some magnets and other objects will toy with the sensors in your phone expecially the ones by the USB connector

I've been having this problem too. The Car app and Daydream would randomly open and close. I've just performed a hard reset and it appears to have fixed the problem.
----------UPDATE 3 DAYS LATER.....
So a hard reset has not fixed this. The car app did not open for a couple of days but I have had the loud speaker turning on every time I answer a call. I've just used my earphones with the phone for the first time since I performed the hard reset and now the car app is opening again. I've tried to clean out the 3.5mm socket but its not making a difference. It seems strange that the hard reset did kind of fix it until the earphone socket was used. Now I really don't know if it's a hardware or software issue!

I had the same issue with my M8 unlocked version. Also had the problem where the speakerphone would go on and off during calls and some other issues but now since updating to the newest HTC build with Android 5.0 I haven't noticed anything.
Could it be that HTC were aware of these issues and have now fixed them?
Have any of you had progress with the new update or are the issues still apparent?
Will update later when I have had more time to test the new software out but as of now it looks like its fixed.

Mine just started doing this tonight too.. no matter what kind of cable gets plugged in to it, it goes into car/ docked mode and turns my wifi on, and rotates all around when I don't want it to. It's VERY annoying. I tried doing a factory reset on it and it's still doing it when I plug a charger in. It also is doing it just randomly when no cable is plugged in.
I'm wondering if a lot of people are having this issue recently, if it was something in one of the recent updates to the HTC service pack sent out by HTC via the Play Store. Anyone know???

Well, so much for that update...
After almost exactly a week without any problems it started acting up again this morning. In and out of carnode. Guess I'll just make use of my warranty and send it in for service.

yep.. me too. Did a reset and was working fine for about a week and just started doing it again today. WTF.

This was happening to me back in the fall. IIRC, my fix was to clean out the charging port. Look for how-to on web. I think the problem is some crossed pins with dirt making the phone think it's plugged in to dock.
Sent from my Gunmetal Grey M8

My phone just started doing this on the 5th.
It also rotates when it's not supposed to? It is so annoying and idk what to do. Is this a. HTC issue or what?

littleames said:
My phone just started doing this on the 5th.
It also rotates when it's not supposed to? It is so annoying and idk what to do. Is this a. HTC issue or what?
Click to expand...
Click to collapse
I had my phone sent in for service and it turned out to be a faulty speaker. They swapped it and I haven't encountered any of the problems I had prior to sending it in.
How the speaker was interfering with the operating system I have no idea, my best guess it was shorting out something but it's just a theory.

phone keeps entering car mode
I have had this issue and completely fixed it, on your phone find car mode, scroll down to a hidden settings menu, in settings disable auto dock mode, auto connect, in fact disable everything, then exit car mode using the exit button. Restart your phone and hopefully it never enters car mode again and charges normally.
I had this issue for months and bought a new phone that I didn't like so came back to the HTC and eventually fixed it.

This is the flex USB cable. They go bad and cause car mode / dock mode like this. The cable itself is $14 and you likely will be replacing the sticker speaker grills which are $11. I have personally repaired this and it is the only permanent fix. Not disabling an app. Not removing an app. This failure is due to hardware and hardware only.
BTW.... way to dig up an old thread lol.
Sent from my Nexus 6 using Tapatalk

I have this issue since three days and it's driving me mad.
Tried all the suggested solutions and nothing worked so far.
I've ordered a new USB flex cable with charge dock pcb. I'll be sure to post my experiences with that, hope it fixes this annoying issue as Dottar suggested

Car Mode / Charge Port Issues

I'm about to go insane over this issue.
FYI im running DH's GPE 8-3-15
Something seems to be wrong with either my software or the charge port hardware. The phone gets put into "car mode" randomly, sometimes unplugged but more often plugged in. Some charge cords seem to do it more than others but sometimes and on some cords i can't reproduce the problem no matter how hard i try and no matter how much i move the connector around, then sporadically sitting on the desk it goes into car mode!
I've tried cleaning the port with a dental pick and canned air with what i thought was success for about a day but then back to car more it goes. I've tried removing or disabling anything related to car mode or sense. When going into car mode it will sometimes display the car mode notification icon and it will usually turn on an ambient display/clock.
Does anyone know how to kill car mode in regard to how android is getting a signal from the charge port to go into care mode?
does anyone know how the charge port does this electrically? i read some place that the charge port might have some sort of magnetic sensor that car docks use.
I'm very familiar with troubleshooting technical issues and not being able to reliably reproduce the issue but then having it be so bad that i can barely use the phone make me go insane!
Edit: just found a very interesting post on cyanogen forum from 2011: http://forum.cyanogenmod.org/topic/26505-disable-dock-modes-entirely/
it sounds like it can be disabled in the kernel and that the kernel module from that app might be able to be loaded without the app, i tried the app demo just for the hell of it but no dice with my Elite GPE kernel

jmclaren7 said:
I'm about to go insane over this issue.
FYI im running DH's GPE 8-3-15
Something seems to be wrong with either my software or the charge port hardware. The phone gets put into "car mode" randomly, sometimes unplugged but more often plugged in. Some charge cords seem to do it more than others but sometimes and on some cords i can't reproduce the problem no matter how hard i try and no matter how much i move the connector around, then sporadically sitting on the desk it goes into car mode!
I've tried cleaning the port with a dental pick and canned air with what i thought was success for about a day but then back to car more it goes. I've tried removing or disabling anything related to car mode or sense. When going into car mode it will sometimes display the car mode notification icon and it will usually turn on an ambient display/clock.
Does anyone know how to kill car mode in regard to how android is getting a signal from the charge port to go into care mode?
does anyone know how the charge port does this electrically? i read some place that the charge port might have some sort of magnetic sensor that car docks use.
I'm very familiar with troubleshooting technical issues and not being able to reliably reproduce the issue but then having it be so bad that i can barely use the phone make me go insane!
Edit: just found a very interesting post on cyanogen forum from 2011: http://forum.cyanogenmod.org/topic/26505-disable-dock-modes-entirely/
it sounds like it can be disabled in the kernel and that the kernel module from that app might be able to be loaded without the app, i tried the app demo just for the hell of it but no dice with my Elite GPE kernel
Click to expand...
Click to collapse
Yeah man. Had this with one of my m8. In end it was fixed with $14 part and $11 in new speaker grill stickers. The problem is that the usb flex cables go bad.
Sent from my Nexus 6 using Tapatalk