Develop Bugs

[Q] home button and lower left screen no longer works

I am running miui 12.11.1, stock kernel. My droid incredible as the AMOLED screen. My home button and the lower left part of the screen no longer respond to touch input. I have to rotate the screen to use parts of my screen now or I can't type in the "a" on the keyboards, or pull down the menu in landscape mode. I've wiped cache, and full wipe, but it has made no difference. I also cannot mount the internal sd card but that is a known issue with this rom I believe.
I've also tried going to a completely different rom CM 6.1 stable. but I have the same issue.
Ideas or assistance would be appreciated.

this sounds like a hardware issue and is most likely unrelated to ROM/kernel/recovery

Sounds like the digitizer screen. Same thing happened to me. Look on Ebay for a new one.

this happens with certian Dinc's. i bought a new screen to fix my home button issue because they are linked, i ended finding out it was a loose cable but according to HTC its a rare problem and was isolated to a few phones

eh. . that is ok. If it is a hardware issue than I'm just unluckly. I guess I just need to remember to rotate the screen left instead of right. Is there an easy way to map the home button to the search hard button?
I guess if it is really annoying I'll sell it to one of the devs here who could put it to good use.

Doubt its a hardware issue so test it before listening to anyone on here. I have miui as well and I have the same problem then I did a nand and flashed a new rom and it worked but I restored and the nand and the problem was back. I thought it was kernel but I flashed different ones but that isn't it...i flashed the zip for data throttling instead of editing it myself but I doubt that is the prob...so I have no cle right now I was just going to give up because now I don't even get any calls so make sure you test to rule out a hardware issue because I doubt it is bc I have the same issue and they keep getting worse until I flash a new rom. I'll try to figure it out. Ley me know on recent changes you made so that I can have some help trying to figure it out.

Well, Like I said, I wiped, factory, reset and flashed a completely different rom (went from MIUI to CM Stable) and one side of the screen was unresponsive. I turned off the phone to put in a battery and now I have all my buttons and everything seems to be working again.

vincent_price said:
Well, Like I said, I wiped, factory, reset and flashed a completely different rom (went from MIUI to CM Stable) and one side of the screen was unresponsive. I turned off the phone to put in a battery and now I have all my buttons and everything seems to be working again.
Click to expand...
Click to collapse
I've heard of issues with extended batteries where the pressure distorts the screen so it doesn't work...
Could that've been the case?

I doubt it was the battery, I had the original battery in there when it was not working and I'm using the extended battery now and it is working, both batteries have identical physical dimensions. It may very well be a hardware issue, I noticed that when I was having problems, I could not mount my sdcard on my pc. The cable was plugged in, the phone asked if I wanted to sync with the PC but it never showed up in windows. I did it just now (running CM6) and it works. The usb cable/port is underneath the home button so maybe that port is just fragile and causing issues? I never liked the location of that port, it should be on top of the phone or underneath, away from screen as much as possible.

[Not Solved] Car Home (car mode) acting like a virus! Need Help!

Even after uninstalling it with titanium backup,root explorer and native android in menu it keeps popping up in notification bar with these ill-effects:
It closes out any apps or programs I was using!
It automatically puts me on speaker when I make or receive calls
Screen orientation cannot be disabled
Screen lock cannot be disabled
Volume is lowered when playing music
stays at the same volume and cannot be adjusted.
Some suggestions were to disable automatic startup and bluetooth in Car Home's menus when it pops up, I did not see such option. Now the menu does not pop up anymore, only the steering wheel icon pops up in notification bar to let me know its here to make my day a living hell again. Everyday, Every Hour, Every minute. I've done full wipe,cache,dalvik, and reinstall of cm6 6.1.2 and it just wont GO AWAY! Please HELP!
Posting in general forum because I'm not getting any help in Q/A!

You know what, my phone started exactly the same thing yesterday lunchtime and it's bloody annoying.
One thing that bugs me is that the headphone volume is now jammed at "very loud" with no way to adjust it.
Likely cause: pins 4 & 5 of the USB port shorted out. I would recommend carefully cleaning the USB port on the phone to see if that helps (it didn't for me).
Unless anyone has a magic solution, mine is going back to stock today and then back to HTC for repair.

Had the exact same issue a while back so I just took it to Sprint and got a new one.

perhaps its my google account cuz i notice after fresh install and before i sync my market there car home is no where to be found. so im thinking theres probably an issue with my google account and apps. even thiugh it does not have car home as one of ny apps ive installed.

issue temporarily fixed by going to both car apps in applications and force stop/clearing data but then it came back again, defiantly sometime to do with usb port

My phone started having the same problem, it would come up for no reason at all. Just now I plugged it into my car charger and it magically stopped. I was wondering if the usb cable I got from HTC could be bad.

Its a provlem with your micro usb. I had the same problem on multiple
roms. Getting a new usb cable cleared it up for me.
Sent from my PC36100 using XDA App

I had the same problem, and it turned out that it was a 3rd party charger that I bought on ebay that caused it. I bought a charger from Sprint, and it cleared up for me.

Don't mean to dig up an old thread, but figured would be better than starting a new one.
My Evo just started doing similar things just two days ago. Pretty sure mine was a moisture issue- put it in my pocket while swim suit was still wet, I've read similar reports on other forums.
My issue is Car Home will launch whenever it wants (seems to be purely random.) It will 'dock' then 'undock' (indicated by the chime it plays) two or three times in a row before it finally just runs in the background. If you are in an application while this happens it will either crash the program, or refresh everything, losing what ever state you were on.
Any got a software fix for this yet? I've tried uninstalling it, freezing it, reinstalling it, deleting the apk with root explorer... nothing. Not only is it god awful annoying it's killing my battery life. From what I am understanding this issue is rooted in hardware problems, but there has to be a way of stopping a program from auto loading.
I even went as far as to delete EVERY file that root explorer found the words 'car' and 'home' in with it's search function. Tried installing apps that supposedly blocked it from auto loading like NoDock, did nothing.
If all else fails I guess i could do a full wipe and reload CM7, but I've read reports that that doesn't even fix it. Is there anyway to confirm it's a USB problem, and not a short in the magnetic sensor? I attempted to take a cat log, think it was throwing a Java error, need to read up on how to post said log.
If there is a more complete thread or resolution page, please link it, I have no issues reading up on it myself if only I can find it.
Thanks for any input!

This problem is caused by the liquid damage... Everytime I have one come in with this issue.. I have signs of liquid damage to the board, especially around the charging port...

I hear ya, but there has to be a way of removing carhome completely. My phone operates fantastic for 80% of the day, so it's not like it's a catastrophic error or anything.

Same thing happening here on my Evo with Cyanogenmod 7.1RC1. Really odd behavior. I just uninstalled car home using Titanium and I'm waiting to see if that fixes it.

I downloaded nodock (trial) and pretty much solved the issue. I still have problems on start up but once I am able to enable the app. I might just end up buying the app because of no other choice.

I fixed this issue by getting a new phone. Its a hardware issue, something something usb port dying glitching, thinks its docking with car dock

I would totally do the same thing if I wasn't living in fear of the new ota

crakerjaks said:
I fixed this issue by getting a new phone. Its a hardware issue, something something usb port dying glitching, thinks its docking with car dock
Click to expand...
Click to collapse
This.
It's a hardware issue, not software. The tech at my local Sprint store said they see this a lot with people that use car chargers, especially during the winter. The end of the cable falls on the floor and gets dirt, salt, and other crap in it then gets picked up and plugged into the phone and screws up the USB port. Sometimes it just needs to be cleaned, but sometimes it actually gets damaged.
Sent from my HTC EVO 4G with Tapatalk

I cleaned my charging port with rubbing alcohol and it seems to be fixed.
Sent from my PC36100 using XDA App

has anyone found a solution to this issue, im currently experiencing it on my inspire.... from what i have read its a hardware issue, but isn't there anyway to make a patch of something that can block car home from launching?? it randomly starts up on my phone and causes my speaker phone to always be on when receiving calls or making one, until i manually turn it off but still its pretty annoying... help!! lol

water damage or generic charger
I had this problem I was using a cheap stand charger when I switched back to the stock charger it solved the problem after a few days.... but that evo broke and my next evo had it again plus HDMI wasn't working. Took it in and it had all kinds of corrosion from water damage causing the problem. So take it in or take it apart and clean it hope that helps

[Q] Weird input problems

Hi,
so I am finally at that point where I'm about to jump off a bridge.
My beloved HTC Desire has got weird problems and I really have no more idea, what I can do.
So here's the problem:
Sometimes (turning screen off sometimes helps), my phone registers an input (at a certain horizontal line, I will clarify that later) when I'm actually not touching that zone at all.
So (if you have the keyboard open), it always thinks it is touched at a horizontal line which is about there, where the 'a' is on the qwerty-keyboard. (I have a swiping keyboard on my phone, that always gives a nice blue line from 'a' to 'l'...).
The really weird thing about that is, that I don't actually have to TOUCH the screen. I can move that blue line on my keyboard (or change homescreens for that matter) while I am about 1-2 cm ABOVE the screen and I DON'T EVEN TOUCH IT. That really drives me crazy, as I don't even know whether that's physically possible...
That behaviour is totally random, sometimes I don't see it for 1-2 days, sometimes it won't go away for a couple hours.
Additionally, sometimes the Screen won't recognize my touches at all (only at lockscreen, turning on and off helps).
So I tried restoring various Nandroid backups from when I didn't have that problem, I tried flashing a new radio, a new rom, data, factory etc. wipe and nothing helps.
Pulling the battery when it's off and leaving it off for about 10min also won't help.
If you don't understand what I'm trying to say (I know it's difficult and I appreciate any efforts to help) I will try to record a video of it.
It is also difficult returning the phone as that failure is not reproducible.
I am running MIUI 1.5.20 on my S-OFF'ed HTC Desire with SLCD Screen.
I would be so thankful for any help,
Don

Maybe just an issue with the screen in general. You ever throught about contacting HTC or your carrier? See if getting a new screen would be better and stop these problems. Just be prepared to use an RUU though.

thanks Meaple,
anyone else got an idea?
:/

Camera black screen of death - HW Fault?

I've got a HTC Desire which has been rooted and Im running Sandvold's ICS. I needed to reboot my phone the other day and after the reboot my camera shows a black screen of death. I first thought it might be a corrupted OS - I reinstall, restores a previous working backing, factory reset - none of them helped which leads me to believe its a hardware fault.
When I run the camera I get a black screen and sometimes a popup that says camera is not responding.
I download a flashlight app and the camera LED doesn't appear to work either - it also says flashlight is not responding.
I though replacing the camera module might do the trick but the flashlight is not part of the module? Anyone has any similar problems?

When you say black screen of death (widely known among windows OS users as KSOD), do you then mean a black screen followed by a system crash which is resolved by pulling out the battery or a black screen followed by system reboot?

try a non ICS rom... think camera is pretty unstable on ICS rom

Thanks - I'll try and go back to stock and see.
I just get a black screen - no OS crash. I can go back and everything is still working fine - no reboots.
Update: Ok - it must be a hardware problem.
I've gone back to CM7 - factory reset/new SD card. Still the same problem.
Update2: Ok - its fixed. Let hope this helps someone else. I opened the phone up and removed the top board and then saw one of the ribbon cables was loose (the one on the left) I reseated it and now camera and flash work perfectly again! Woo hoo!!

flexi cable loose connection to the lower board (the board with the SIM reader)
many thanks !
after disassembling the phone, the connector , the one on the left was not very well connected to the board, so i removed both boards, upper one with the camera and lower one with the sim card reader
plugging it back, and assembling everything made it all work
in my case, the following was not working:
camera
flash
mic jack
now it is all working perfect !!
to see how to disassemble it: check youtube desire disassemble
kl1k said:
Thanks - I'll try and go back to stock and see.
I just get a black screen - no OS crash. I can go back and everything is still working fine - no reboots.
Update: Ok - it must be a hardware problem.
I've gone back to CM7 - factory reset/new SD card. Still the same problem.
Update2: Ok - its fixed. Let hope this helps someone else. I opened the phone up and removed the top board and then saw one of the ribbon cables was loose (the one on the left) I reseated it and now camera and flash work perfectly again! Woo hoo!!
Click to expand...
Click to collapse

Xperia z1 compact Touchscreen falsely registers input

Hi,
Had my phone a couple of years, no problems, but recently cracked the screen.
Bought three replacement screens and fitted them in phone:
* 1st one touchscreen digitiser worked perfectly all the time but LCD was broken (had lines/artifacts on it) - sent it back.
* 2nd one, same supplier as first, LCD worked, but digitiser works intermittently - it always works immediately after phone reboot, but after the screen locks for the first time, it then has a problem where it registers an input when I'm not giving any, so the screen goes haywire and I can't even enter my pin or restart phone (Have to use red button in sim card bay). Occasionally and randomly when I try it, it sometimes works so I can enter my pin, and then use the phone until the next time the screen locks....but basically phone is rendered unusable, because this is totally random. Sent this one back too.
* 3rd one bought from a different supplier - AFAIK this one is a genuine Sony part (it at least has the Sony logo on it), but have the same digitiser problem as the second. Time has passed to send this back.
Due to the above description I am sure it is not a problem with the phone (1st one digitser worked perfectly & original cracked screen digitser worked for half the screen where it wasn't cracked). I'm also sure it's a software issue, since it works everytime following a phone reset but before the screen is locked. Behaviour seems to be the same at different temperatures. Also inspected the flex connector and ribbon components under microscope at work, and saw no problems.
One think I noticed is that all 3 screens I bought have no insualting backing on the back of the LCD, so the metal back touches the metal shield below - I did not see any screens to buy with the insulating backing - I wondered if this could be affecting the EMC behaviour of the screen (some capacitivie coupling with the digitiser or some type of grounding issue) - but then why would the digitiser of 1st screen work ok, and work for >1hour following a reset but then not after a screen lock?
Tried turning glove mode on/off - no difference in behaviour. Tried using screen while it is not fitted in phone housing (not touching metal shield), same behaviour.
I saw a couple of threads from a while back, but don't know if they are up to date, or if a solution to this problem is now known:
https://forum.xda-developers.com/showthread.php?t=2691849
This one gives a solution, but then says at the top of the thread DON'T TRY THIS FIX, IT IS A HARDWARE ISSUE NOT SOFTWARE.....so I'm worried to try it.
https://forum.xda-developers.com/showthread.php?t=2662457
This one is to adjust the touchscreen sensitivity, but even though I have root access, I get an error message relating to the mount commandwhen trying to copy the edited idc file back to the system\usr\idc directory, "operation not permitted'.
Does anyone know a reliable fix that works? Or how I can get write access to idc folder to try editing the clearpad file? I don't have an SD card for my phone, but not sure it is essential for these methods?
Thanks

Nabla_x said:
Hi,
Does anyone know a reliable fix that works? Or how I can get write access to idc folder to try editing the clearpad file? I don't have an SD card for my phone, but not sure it is essential for these methods?
Thanks
Click to expand...
Click to collapse
Assuming you're on LP 5.1... System rw access is disabled by default, even with root. Flashing dual recovery by NUT is easiest way to get it. Then you should be able to move files in boot or in recovery.