My HDMI out is DEAD!!! (PLEASE HELP) - Verizon Droid Charge

I have flashed back to stock once again. I accepted the EE4 update and still I am without HDMI out.
Also when I try to set up the TV Out shortcut with Any Cut...every time I open it, it force closes saying that com.android.settings has unexpectedly quit.
It also happened with the SIM Toolkit.
I wiped this phone a hundred times and tried all various roms. What has been damaged?

Stay stock and go to the store, warranty replacement
Sent from my SCH-I510 using XDA App

The Droid Charge is covered under manufacturer's warranty for 1 year, correct?
My HDMI port hasn't been able to play audio, ever. I purchased a couple different adapters and cables while testing, nothing worked I'm thinking my best bet would be to take it to a Verizon store to get a new one?

WWWAAAAAA
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It's a software issue....it's gotta be!!!
The HDMI used to work fine. This is God punishing me. I like stock....I just wanted TW4 on my phone. I didn't wanna root it again, but they made me do it.
WWWAAAAAA

Rominucka said:
WWWAAAAAA
It's a software issue....it's gotta be!!!
The HDMI used to work fine. This is God punishing me. I like stock....I just wanted TW4 on my phone. I didn't wanna root it again, but they made me do it.
WWWAAAAAA
Click to expand...
Click to collapse
Could it be the cable? I bought a cheapo $6 hdmi cable and my kids kinked it; now it doesn't work.

I am such a *****.
It's either the cable or the TV.
I just checked with a new cable on a different TV and it worked.
I forgot to bring my cable to the store because I was a little preoccupied with the fact that my phone had no service and the stats showed no existing MEID or phone number when I woke up and I had to flash it back to ED1 yet again to fix that. What's odd, is that now my Device ID has been wiped from the VZW system (i'm a rep); it just shows my SIM, which (I was told) is all I really need.
I gotta stop ****ing with this thing. At least if I felt like I was learning something it would be OK, but I'm going around in circles here.
I'm still getting force closes on the TV Out hidden menu. I have an idea though.....open the Charge here at the store, load the TV Out shortcut and see if it quits. If it doesn't I'll be PISSED!!!

Rominucka, you ever get the TV Out forced closed issue resolved? I'm seeing the same behavior after rolling back to FE from GB (multiple ROMS, .pit wipes, EE1-EE4 upgrades, stock/3rd-part kernels, etc, etc, etc...). All FE builds give me a FC on TV Out (and at least one other, but I don't recall if it is the SIM Toolkit like yours or not).
As a side note, HDMI doesn't work (it recognizes the cable and the sound quits playing, but it does not mirror the image). I suspect it may be the cable (paid all of $2 for it) and will try a different cable&TV this weekend to see.

Related

Can't connect via usb to pc.

I'm just flashed to 1.7. Was on 1.6 and had this problem. I can't connect to any pc's over usb. I just bought a new cord because the original was sucked into a vacuum.
Anyways when I plug in the TF to a pc I get a bubble pop up that says "the connected usb device as malfunctioned"
Or on my wifes pc it tried to install the driver but it always fail. I have uninstalled and reinstalled the asus pc suite but it hasn't helped anything.
I'm getting worried its a hardware issue any help would be awesome!
Heres a shot of the error I'm getting.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any ideas out there?
Yeah i'm now getting the same problem. I'm using prime 1.9.1 and also i have re installed the suite/drivers. I would really like it if someone could give this question an answer. Also i have Windows x64
did you enable usb debugging on the tf?
Yah it sucks I never got mine working. Now the battery is draining over night if I leave it unplugged, thats with wifi off. But I can't even consider rma over the usb because it is rooted.
I'm also facing the same problem. Detection on my pc is like a hit & miss affair. Wonder if this got to do with a faulty usb/data cable?
greeny2010 said:
I'm also facing the same problem. Detection on my pc is like a hit & miss affair. Wonder if this got to do with a faulty usb/data cable?
Click to expand...
Click to collapse
I replaced mine with an asus cable. Not some knock off, and it didn't help anything.
I returned one not long after purchasing because of a similar issue. Tried on many PC's and different cables, made no difference. I think it is a hardware fault, reasonably common too. Can you not flash back to stock to RMA?
iGBH said:
I returned one not long after purchasing because of a similar issue. Tried on many PC's and different cables, made no difference. I think it is a hardware fault, reasonably common too. Can you not flash back to stock to RMA?
Click to expand...
Click to collapse
The problem is you need to plug it into a pc to reflash it. I had a thread going on this before, I think someone recomended a method for that had came out where you could flash without a pc. I'm a little nervous honestly to mess with it because it something goes wrong without the usb port working its done.

[Q] Browser screen sensitivty issue and Bluetooth pairing/connecting issue

I originally posted this in the SynergyROM section as that is current rom I am running, however I have experienced these same 2 problems on a couple other roms too so I do not believe they are rom-specific issues.
1. I cannot get my Pioneer (model DEH-6400BT) car stereo to pair or connect with my S3. When I try it says would you like to pair and I say ok and it says confirm the 6 digit pin on your device matches the pin on the stereo but it does not show any pin on either and then says Unable to Pair. I also tried wiping data and installing CleanRom and also MeanLeanJellyBean on my phone to see if it would pair on that rom, but it again failed. I had ZERO problems pairing/connecting with my HTC Thunderbolt so I don't know what the hell the deal is?? Should also mention that my SIII pairs and connects to my bluetooth headset just fine....
2. I use the browser A LOT for work and always have a long list of checkboxes to check off (see attached pic to see what I mean, volume slider on there cause i accidentally bumped it when doing screenshot so ignore that). I have found a few browsers that better display what boxes are checked, but when I go thru to check/uncheck boxes I find the screen sensitivity is TERRIBLE. Almost every single time it takes 3-6 attempts to check or uncheck a box. I have tried every major browser in the Play Store. Again, I had ZERO problems with this on my HTC Thunderbolt, always worked the first time, if it didn't check or uncheck it's because I just plain missed the box with my finger. How do I solve this? I use this everyday for work and don't have time to be spending that many attempts just to check a damn box, it's absolutely ridiculous. It blows my mind I am having this problem with such a high-end device as the SIII.
Thank you and Merry Christmas.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
1) Did you try the other way around and sync the phone to radio instead of the radio to the phone? or vice versa. My friends Pioneer deck did the same thing and switching which one was in discovery mode worked.
2) Dolphin browser is dumb, try zooming in a little then go down the line and check the boxes. Maybe try Chrome or my favorite, Boat Browser.?
x714x said:
1) Did you try the other way around and sync the phone to radio instead of the radio to the phone? or vice versa. My friends Pioneer deck did the same thing and switching which one was in discovery mode worked.
2) Dolphin browser is dumb, try zooming in a little then go down the line and check the boxes. Maybe try Chrome or my favorite, Boat Browser.?
Click to expand...
Click to collapse
No I didn't... Have my doubts butI ill try.
Sent from my SCH-I535 using xda app-developers app

[Q] Huawei H866C Question

Hello everyone!
I seem to have a big problem with my phone that I cannot figure out. I'm fairly good with phones and very good with PC, but this problem eludes me.
My Huawei H866C was working just fine yesterday until boom, system freeze. This happened numerous times and most of the time, all I was doing was looking around in the settings etc. My first gut reaction was to factory reset it.
So I did.
When it was done, the phone rebooted like it should, and there I found the "tutorial" screen.
I tap the green android and it proceeds to the next screen which has only one button labeled "Begin"
When I press begin, it immediately throws this error; The application SetupWizardEx (process com.huawei.setupwizardex) has stopped unexpectedly. Please try again.
Well, needless to say, I've many dozens of times with no success.
I recall a similar incident with my sisters motorola droid bionic, in which after a reset the phone wanted some carrier info before it would load the home screen and let you use the phone. With that incident, I was able to bypass it by touching all 4 corners of the touchscreen. I can't find anything like that to bypass this tutorial nonsense.
I know that the phone isn't bricked, because I never rooted it. Furthermore, I can still bring up swype keyboard settings by holding the menu softkey. From there, I can click a web link in swype help and open the browser with no wifi connectivity. I can go through browser settings, and swype settings. When I first turn the phone back on, I can even use the slide-down menu briefly before it takes away my access.
I was really starting to like this phone until now.
Is there any way to bypass this annoying tutorial so I can use the phone? Otherwise, I'm afraid my money was wasted.
I have included some fairly low quality pictures to try and illustrate my problem.
ANY help at all would be greatly appreciated.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Well admins, you may as well delete this thread. It's helped no one, including myself. I'm just going to return the phone and get my money back..
HuaweiTurk said:
Well admins, you may as well delete this thread. It's helped no one, including myself. I'm just going to return the phone and get my money back..
Click to expand...
Click to collapse
And that's exactly what I did. My best advice? STAY AWAY FROM TRACFONE/NET10/Straight Talk at ALL costs! Sure, they give you cheap unlimited everything, but the phones are pure garbage. :good:
BYOP
Sent from my HUAWEI Y536A1 using XDA Free mobile app

OTG and USB port not functioning

So I was having battery issues when I noticed my OTG had stopped working. But what's worse was the USB port was not either, so now I have no way to use fastboot and RSD Lite. Not good. So I installed a new OEM battery and USB port. The battery would not even take a charge and phone just bootlooped instantly. Reinstalled original battery, which now seemed to be charging much better for some reason. But the USB port still did not work, although it will now register as a unrecognizable device on Windows 8. A pop-up says there's an unknown issue with the device and to try again. Drivers are fine. I really want to restore the phone to original factory settings, meaning the original boot kernel, etc. I had upgraded the fastboot, radio, and recovery to a material look and I doubt that is related, but I still want it factory so that it will take OTA updates and I can sell it to someone who just wants a phone which does what your average owner needs it to do, lol. So anyone have any ideas? Is the main board toast?
Delete the drivers and reinstall.
Already done. No help but ty.
I forgot to say that I have 2 Nexus 5's, I upgraded to the 32Gb when my original 16Gb started having battery issues, which, I might add, I resolved this morning by booting into bootloader and allowing it to charge in that state, so it stopped looping the "dead battery loop" as I called it, and charged up to 95% by the time I rebooted into the OS. Seems to be working fine now, will check battery drain soon, but focusing on the OTG/USB port issue. I'm thinking the battery issue is related. I think I somehow connected it to too much amperage and cooked the main board's USB infrastructure, if that makes sense. So it might explain the battery issues also. Now it has a new battery, and all is well there at least. Oh, and I get a screen I have no idea where it came from. It comes up only when the charger is connected but the phone is off. I will try to get it up on here.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
https://www.dropbox.com/s/mc3lakd26parpdd/IMG_20151129_134355.jpg?dl=0
Idk if that first try came out ok cuz I don't see it on my phone, so I put up a link, does anyone have any idea why that is coming up when plugged in and not turned on? Weird.
And does anyone want a N5 16Gb w/ unlocked BL, MultiROM flashed and stock, rooted Android 6.0 and CM 12.1 installed? Cheap money? It just can't be connected via USB except to charge. But battery is brand new, ? Great as a dev device, should keep getting ROMs and official updates for years to come, look at the N4, still getting love, and the N5 is far more popular.
Oh, and screen is mint condition, and casing is good but for a couple little flaws, but it's a great functioning phone but for the OTG and fastboot problem. But no matter, it can be worked around, just don't fully wipe it, lol

Phone Randomly Dies

Hello everyone. It's been a minute since I've posted anything on this site. In January this year I decided to upgrade from my aging Blackberry Priv to one of these phones. I've been using it without any issues until early this morning when I tried to look at my notifications and the screen wouldn't light up. It was working fine all throughout the day, and I don't recall the battery being below 50%. It is unresponsive when I plug it into the wall adapter or my PC, however the PC seems to pick it up as a device called "QUSB__BULK."
The phone is running stock Android, and I only charge it with the wall adapter it came with and occasionally my PC. I only have a few social media and email apps on it. I had the Open Camera app on it, and I'm a little sus of it since there have been times where I would wake the phone up and the camera would just randomly open. It seems like it would bog the phone down a bit when this would happen. I installed the app because I didn't like the way the stock app processed audio while recording videos. The app gave me the ability to record raw audio which worked fine aside from slightly lower volume.
Does anyone have any ideas on what could have caused this?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Figured I'd bump this for an update. I contacted the company shortly after I made this post about the phone. The phone was covered under warranty, and they told me to ship it to them for repairs. I shipped it in June and have contacted them a few times since. I'm suspecting that there was some kind of defect in the motherboard since I'm apparently not the only one who has had this issue. I found a post on another forum dating back to last year from someone with the same experience as me where their phone just randomly said "ight, Imma head out." It's been quite a while since I sent it off, which adds to my suspicion that it was a board issue given the whole chip shortage we're going through. I'll update this post if anything comes up in the future. I miss that phone. Been using an iPhone since I sent it off. It's okay I guess, but man do I miss that keyboard.
Update on the phone - I was contacted by F(X) Tec about four days ago. My phone has been repaired and shipped to the US. I should be getting it back by Wednesday. They did not specify what actually caused the issue with it. Hopefully, once I get it back it won't have any further issues.

Categories

Resources